From 525fe6c2cbeb68614b6ec3879962767c20b29a5a Mon Sep 17 00:00:00 2001 From: Adrian A Date: Mon, 7 Oct 2019 23:16:41 +0200 Subject: [PATCH 001/290] Correction of small syntax error --- xsd/siri_model/siri_situationReasons-v2.0.xsd | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/xsd/siri_model/siri_situationReasons-v2.0.xsd b/xsd/siri_model/siri_situationReasons-v2.0.xsd index adfddca6..927f83cd 100644 --- a/xsd/siri_model/siri_situationReasons-v2.0.xsd +++ b/xsd/siri_model/siri_situationReasons-v2.0.xsd @@ -1975,10 +1975,11 @@ Rail transport, Roads and road transport TPEG Pti22_2 rough sea. - - - TPEG Pti22_3 heavy snow fall. - + + + TPEG Pti22_3 heavy snow fall. + + drifting snow - Alias to TPEG Pti22_3 heavySnowFall. From 25568d72f2630770853e142085cc5ac895f5f901 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 8 Oct 2019 01:01:26 +0200 Subject: [PATCH 002/290] Small correction of mix-up --- .../exd_allServices_capabilitiesResponse.xml | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/examples/siri_exu_capability/exd_allServices_capabilitiesResponse.xml b/examples/siri_exu_capability/exd_allServices_capabilitiesResponse.xml index 6cf1027c..767ce6a7 100644 --- a/examples/siri_exu_capability/exd_allServices_capabilitiesResponse.xml +++ b/examples/siri_exu_capability/exd_allServices_capabilitiesResponse.xml @@ -476,7 +476,7 @@ en WGS84 - true + true true @@ -488,8 +488,6 @@ false - true - true From 65d7e43a5d071db649c30ffcc159487bbc80342a Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 6 Nov 2019 14:26:26 +0100 Subject: [PATCH 003/290] CR008: add SubscriptionRenewal element --- xsd/siri/siri_requests-v2.0.xsd | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/xsd/siri/siri_requests-v2.0.xsd b/xsd/siri/siri_requests-v2.0.xsd index 16774d53..f7ef5dce 100644 --- a/xsd/siri/siri_requests-v2.0.xsd +++ b/xsd/siri/siri_requests-v2.0.xsd @@ -287,6 +287,11 @@ Rail transport, Roads and road transport Requested end time for subscription. + + + By using this element, the subscriber informs the data provider that no data is requested but only an extension of the InitialTerminationTime of the subscription. It is therefore not necessary to transmit any journey or interchange information (corresponding to the subscription) in the next response. Only the data triggered by hysteresis / ChangeBeforeUpdate, PreviewInterval etc. needs to be sent. If SubscriptionRenewal is omitted, all data corresponding to the SubscriptionRequest must be sent in the initial response (or a portion of the data if MoreData is set to 'true'). + + From 5bb5f043523d0d566fd50a488a4792774e5bff68 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 6 Nov 2019 16:21:21 +0100 Subject: [PATCH 004/290] CR065: add JourneyEndNamesGroup to DatedVehicleJ. --- xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd | 1 + 1 file changed, 1 insertion(+) diff --git a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd index f0b4f821..d7997c19 100644 --- a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd @@ -114,6 +114,7 @@ Rail transport, Roads and road transport + From 1f45ffef02bbd07683b52bc85668b09658186d73 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 6 Nov 2019 16:05:06 +0100 Subject: [PATCH 005/290] CR017: add GTFS-R enums to Occupancy --- xsd/siri_model/siri_reference-v2.0.xsd | 31 ++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) diff --git a/xsd/siri_model/siri_reference-v2.0.xsd b/xsd/siri_model/siri_reference-v2.0.xsd index be7bb3ae..46223232 100644 --- a/xsd/siri_model/siri_reference-v2.0.xsd +++ b/xsd/siri_model/siri_reference-v2.0.xsd @@ -632,6 +632,37 @@ Values for these elements can be specified on an annual schedule and will be inh + + + + The vehicle is considered empty by most measures, and has few or no passengers onboard, but is still accepting passengers. + + + + + The vehicle has a large percentage of seats available. What percentage of free seats out of the total seats available is to be considered large enough to fall into this category is determined at the discretion of the producer. + + + + + The vehicle has a small percentage of seats available. What percentage of free seats out of the total seats available is to be considered small enough to fall into this category is determined at the discretion of the producer. + + + + + The vehicle can currently accommodate only standing passengers. + + + + + The vehicle can currently accommodate only standing passengers and has limited space for them. + + + + + The vehicle cannot accept passengers. + + From 81e7fed3a3bde9b0a12b95e71e283ae7d7488bd7 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 6 Nov 2019 15:48:43 +0100 Subject: [PATCH 006/290] CR014: add xxxStopAssignment to RecordedCall --- .../siri_estimatedVehicleJourney-v2.0.xsd | 18 ++++++++++++++---- 1 file changed, 14 insertions(+), 4 deletions(-) diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index ce2d84ee..ff258f06 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -107,7 +107,7 @@ Rail transport, Roads and road transport Reference to a dated VEHICLE JOURNEY. This will be 'framed' ie be with the data context of the ESTIMATED Timetable. -DEPRECATED from SRI 2.0 +DEPRECATED from SIRI 2.0 @@ -119,7 +119,7 @@ DEPRECATED from SRI 2.0 If this is the first message about an extra unplanned VEHICLE JOURNEY, a new and unique code must be given for it. ExtraJourney should be set to 'true'. -DEPRECATED from SRI 2.0 +DEPRECATED from SIRI 2.0 @@ -296,7 +296,7 @@ the original journey and the nature of the difference. - Observed call tmes for that art of teh journey that has already been completed. (+ SIRI 2..0) + Observed call times for that art of teh journey that has already been completed. (+ SIRI 2..0) @@ -306,7 +306,7 @@ the original journey and the nature of the difference. - Estimated call tmes for journey + Estimated call times for journey @@ -393,6 +393,11 @@ the original journey and the nature of the difference. (iii) any departure platform name on any related dated timetable CALL. + + + Assignment of arrival of Scheduled STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure +SIRI v2.0. + + Target departure time of VEHICLE according to latest working timetable. @@ -413,6 +418,11 @@ the original journey and the nature of the difference. Estimated time of departure of VEHICLE. + + + Assignments of departure platfiorm for Scheduled STOP POINT to a physical QUAY. +SIRI v2.0. + + From 07cd64c8362d77f3e3db0cc5848e20aa51664fa1 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 6 Nov 2019 15:31:03 +0100 Subject: [PATCH 007/290] CR005: add JourneyPartViewGroup for indirect refs --- .../siri_monitoredVehicleJourney-v2.0.xsd | 28 +++++++++++++++++++ 1 file changed, 28 insertions(+) diff --git a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd index 69804342..dadccd54 100644 --- a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd @@ -322,8 +322,36 @@ For SIRI-VM this is the most recent stop visited by the VEHICLE.Operator of JOURNEY PART. +SIRI v2.0 + + + + JourneyPart information instead of or in addition to the JourneyPartRef. +SIRI v2.0 + + + + + Reference to the SCHEDULED STOP POINT at which the related JOURNEY PART begins. + + + + + Reference to the SCHEDULED STOP POINT at which the related JOURNEY PART ends. + + + + + Time at which the related JOURNEY PART begins. + + + + + Time at which the related JOURNEY PART ends. + + + + From 4f8f9969143a4506a7d82461c455233e168d3465 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 6 Nov 2019 15:31:46 +0100 Subject: [PATCH 008/290] CR005: add JourneyRelation struc. to Journey model --- xsd/siri_model/siri_journey-v2.0.xsd | 74 ++++++++++++++++++++++++++++ 1 file changed, 74 insertions(+) diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index b95675a7..38e93d58 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -897,5 +897,79 @@ Rail transport, Roads and road transport For frequency based services, observed interval between vehicles at stop. + + + + Provides information about relations to other journeys. + + + + + + + + + + Specifies the type of the relation, e.g., joining, splitting, replacement etc. + + + + + + + + + Specifies which CALL or JOURNEY PART of the JOURNEY has a JOURNEY RELATION. + + + + + + Information about the stop at which the JOURNEY is related to another JOURNEY. + + + + + Information about the JOURNEY PART for which the JOURNEY has a JOURNEY RELATION. + + + + + + + + The JOURNEY RELATION refers to this CALL. + + + + + + + + + + + + + The JOURNEY RELATION refers to this JOURNEY PART. + + + + + + + + Refers to the JOURNEY to which the current JOURNEY is related. + + + + + + + + + + + From 02fd551025433434027c65f61f9b25c7a6c773d4 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 6 Nov 2019 15:33:53 +0100 Subject: [PATCH 009/290] CR005: add JourneyRelations in PT at journey level --- xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd index f0b4f821..d0415321 100644 --- a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd @@ -129,6 +129,11 @@ Rail transport, Roads and road transport + + + Relations of the journey with other journeys, e.g., in case a joining/splitting takes place or the journey substitutes for another one etc. + + From ccdb5e4c133a7b6e776a88442013316d60405dcf Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 6 Nov 2019 15:34:16 +0100 Subject: [PATCH 010/290] CR005: add JourneyRelations in ET at journey level --- xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index ce2d84ee..f2dd100a 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -320,6 +320,11 @@ the original journey and the nature of the difference. + + + Relations of the journey with other journeys, e.g., in case a joining/splitting takes place or the journey substitutes for another one etc. + + From 0794961eeec83b93584eba337cb14ee4ddaae56a Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 6 Nov 2019 15:38:15 +0100 Subject: [PATCH 011/290] CR005: update ConnectingJourneyRef and add enum --- xsd/siri_model/siri_journey_support-v2.0.xsd | 68 ++++++++++++++++++++ 1 file changed, 68 insertions(+) diff --git a/xsd/siri_model/siri_journey_support-v2.0.xsd b/xsd/siri_model/siri_journey_support-v2.0.xsd index 82a01de7..cdbced28 100644 --- a/xsd/siri_model/siri_journey_support-v2.0.xsd +++ b/xsd/siri_model/siri_journey_support-v2.0.xsd @@ -192,6 +192,16 @@ Rail transport, Roads and road transport LINE Reference. + + + TRAIN NUMBER Reference. + + + + + OPERATOR Reference. + + @@ -573,4 +583,62 @@ Corresponds to NeTEX TYPE OF SERVICe. + + + + Allowed types of relation between JOURNEYs. + + + + + VDV "FortfuehrungVonFahrt": The journey is a continuation of the specified RelatedJourney (VDV "BeziehungZuFahrt") at the stop point given in CallInfo (VDV "StreckenBezug/Halt"). Passengers don't need to change vehicles. The new journey is not communicated as an interchange. + + + + + VDV "FortfuehrungDurchFahrt": The journey is continued by the specified RelatedJourney (VDV "BeziehungZuFahrt") at the stop point given in CallInfo (VDV "StreckenBezug/Halt"). Passengers don't need to change vehicles. The new journey is not communicated as an interchange. + + + + + VDV "TrennungVonFahrtIn": The journey splits into multiple RelatedJourneys (VDV "BeziehungZuFahrt") at the stop point given in CallInfo (VDV "StreckenBezug/Halt"). + + + + + VDV "FortfuehrungVonGetrennterFahrt": The journey is a continuation of a single RelatedJourney (VDV "BeziehungZuFahrt") splitting into multiple journeys at the stop point given in CallInfo (VDV "StreckenBezug/Halt"). + + + + + VDV "ZusammenfuehrungVonFahrt": The journey is the continuation of multiple RelatedJourneys (VDV "BeziehungZuFahrt") joining together at the stop point given in CallInfo (VDV "StreckenBezug/Halt"). + + + + + VDV "FortfuehrungDurchZusammengefuehrteFahrt": The journey is continued by a single RelatedJourney (VDV "BeziehungZuFahrt") after joining other journeys at the stop point given in CallInfo (VDV "StreckenBezug/Halt"). + + + + + VDV "ErsatzVonFahrt": The journey replaces one or more partially or fully cancelled RelatedJourneys (VDV "BeziehungZuFahrt") during the JourneyPart defined or referenced in JourneyPartInfo (VDV "FahrtAbschnitt"). + + + + + VDV "ErsatzDurchFahrt": The partially or fully cancelled journey is replaced by one or more RelatedJourneys (VDV "BeziehungZuFahrt") during the JourneyPart defined or referenced in JourneyPartInfo (VDV "FahrtAbschnitt"). + + + + + VDV "EntlastungVonFahrt": The journey partially or fully supports one or more RelatedJourneys (VDV "BeziehungZuFahrt") during the JourneyPart defined or referenced in JourneyPartInfo (VDV "FahrtAbschnitt"). + + + + + VDV "EntlastungDurchFahrt": The journey is partially or fully supported by one or more RelatedJourneys (VDV "BeziehungZuFahrt") during the JourneyPart defined or referenced in JourneyPartInfo (VDV "FahrtAbschnitt"). + + + + From c6a685fc9bc82db90ca7e2d98e213bcf61e7a691 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 6 Nov 2019 16:28:07 +0100 Subject: [PATCH 012/290] CR056: add Branding to JourneyPatternInfoGroup --- xsd/siri_model/siri_reference-v2.0.xsd | 46 ++++++++++++++++++++++++++ 1 file changed, 46 insertions(+) diff --git a/xsd/siri_model/siri_reference-v2.0.xsd b/xsd/siri_model/siri_reference-v2.0.xsd index be7bb3ae..aa63f11e 100644 --- a/xsd/siri_model/siri_reference-v2.0.xsd +++ b/xsd/siri_model/siri_reference-v2.0.xsd @@ -426,6 +426,18 @@ Values for these elements can be specified on an annual schedule and will be inh Alternative identifier of LINE that an external system may associate with journey. + + + + Reference to a BRANDING. + + + + + An arbitrary marketing classification. + + + @@ -680,4 +692,38 @@ Values for these elements can be specified on an annual schedule and will be inh + + + Type for identifier of a BRANDING. + + + + + + Type for reference to a BRANDING. + + + + + + + + An arbitrary marketing classification. + + + + + + + Identity of object from which this BRANDING was derived. + + + + + + Type for identifier of BRANDING. + + + + From 9f713e9cad21463b429d7d8761e89373148d1491 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 6 Nov 2019 16:30:20 +0100 Subject: [PATCH 013/290] CR052: change Country type to ifopt CountryRef --- xsd/siri_model/siri_situation-v2.0.xsd | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/xsd/siri_model/siri_situation-v2.0.xsd b/xsd/siri_model/siri_situation-v2.0.xsd index 905ed0e0..12442698 100644 --- a/xsd/siri_model/siri_situation-v2.0.xsd +++ b/xsd/siri_model/siri_situation-v2.0.xsd @@ -5,6 +5,7 @@ + @@ -472,7 +473,7 @@ Rail transport, Roads and road transport Type for a source, i.e. provider of information. - + Country of origin of source element. From e86c9bf98451ff1642d2a65647cff6f15855f6f9 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 6 Nov 2019 16:31:13 +0100 Subject: [PATCH 014/290] CR051: fix typo in RailSubmodesOfTransportEnum --- xsd/siri_model/siri_modes-v1.1.xsd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xsd/siri_model/siri_modes-v1.1.xsd b/xsd/siri_model/siri_modes-v1.1.xsd index 75c7e136..e5d15d22 100644 --- a/xsd/siri_model/siri_modes-v1.1.xsd +++ b/xsd/siri_model/siri_modes-v1.1.xsd @@ -280,7 +280,7 @@ Rail transport, Roads and road transport - + From 5bda3c63e86481e4ad4118660394c9de892cdf72 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 6 Nov 2019 17:04:45 +0100 Subject: [PATCH 015/290] CR054: add ExtraCall and Cancellation to DatedCall --- xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd index f0b4f821..d2efbb97 100644 --- a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd @@ -492,6 +492,18 @@ Rail transport, Roads and road transport + + + + This DATED CALL is additional and unplanned. If omitted: CALL is planned. + + + + + This DATED CALL is a cancellation of a previously announced call. + + + From 8b32bb3aaa6e2533aa8381d3e9a41ceb6d8a5469 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 6 Nov 2019 17:19:25 +0100 Subject: [PATCH 016/290] CR013: add KeyList and TypesOfValue structures --- xsd/siri_utility/siri_utility-v1.1.xsd | 213 ++++++++++++++++++++++++- 1 file changed, 212 insertions(+), 1 deletion(-) diff --git a/xsd/siri_utility/siri_utility-v1.1.xsd b/xsd/siri_utility/siri_utility-v1.1.xsd index aa4bf7a6..a96b6713 100644 --- a/xsd/siri_utility/siri_utility-v1.1.xsd +++ b/xsd/siri_utility/siri_utility-v1.1.xsd @@ -1,6 +1,6 @@ - + @@ -80,4 +80,215 @@ Rail transport, Roads and road transport + + + + A list of alternative Key values for an element. + + + + Every Key Value Pair must be unique. + + + + + + + + + Type for a Key List. + + + + + Key value pair for Entity. + + + + + + + Type for a Key List. + + + + + Identifier of value e.g. System. + + + + + Value for alternative key. + + + + + + Identifier of type of key. + + + + + + + VALUE SETs and TYPE OF VALUEs in frame. + + + + + Type for containment in frame of TYPE OF VALUEs. + + + + + + + + + A code value from an extensible set, i.e. which may be added to by user applications and is used to validate the properties of Entities. + + + + + + + + + + + + + + + Type for a TYPE OF VALUE. Abstract supertype used to define open classifications of value types. + + + + + + + + + + Elements for TYPE OF VALUE. + + + + + Name of TYPE OF VALUE. + + + + + Short Name for TYPE OF VALUE. + + + + + Description of TYPE OF VALUE. + + + + + Default image for TYPE OF VALUE. + + + + + Default URL for TYPE OF VALUE. + + + + + + + + An extensible set of code values which may be added to by user applications and is used to validate the properties of Entities. + + + + + + + + + + + + + + + + + + + + + + + Type for a VALUE SET. Abstract supertype used to define open classifications of value types. + + + + + + + + Name of Class of Values in Set. + + + + + + Elements for VALUE SET. + + + + + Name of Value. + + + + + Values in Set. + + + + + + + Type for a list of TYPEs OF VALUE. + + + + + + + + + Type for identifier of a TYPE OF VALUE. + + + + + + Type for identifier of a VALUE SET. + + + + + + + Abstract Type for identifier of a SIRI Object. + + + + + + + Name of class of which TypeOfValue is an instance. Used for reflection. + + + + From 6abd068de729ecf3bfb1fee752e8ec789fbbfe6f Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 6 Nov 2019 17:51:26 +0100 Subject: [PATCH 017/290] CR050: add indirect journeyRef as choice to framed --- .../siri_estimatedVehicleJourney-v2.0.xsd | 21 ++++++++++++------- 1 file changed, 14 insertions(+), 7 deletions(-) diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index ce2d84ee..38fa4c9b 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -99,14 +99,21 @@ Rail transport, Roads and road transport - - - Identifer of a VEHICLE JOURNEY within data Horizon of a service. - - + + + + Identifer of a VEHICLE JOURNEY within data Horizon of a service. + + + + + If no VEHICLE JOURNEY reference is available, identify it by origin and destination and the scheduled times at these stops. + + + - Reference to a dated VEHICLE JOURNEY. This will be 'framed' ie be with the data context of the ESTIMATED Timetable. + Reference to a dated VEHICLE JOURNEY. This will be 'framed' i.e. be with the data context of the ESTIMATED Timetable. DEPRECATED from SRI 2.0 @@ -118,7 +125,7 @@ DEPRECATED from SRI 2.0 - 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'. + If this is the first message for an unplanned 'extra' VEHICLE JOURNEY, a new and unique code must be given for it. ExtraJourney should be set to 'true'. DEPRECATED from SRI 2.0 From f79c773fd1297f4a253a02d1130c84347a3ff19b Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 6 Nov 2019 17:28:44 +0100 Subject: [PATCH 018/290] CR028: add StopOrder to PT ServiceJourneyInterch. --- .../siri_datedVehicleJourney-v2.0.xsd | 40 +++++++++++++++++++ 1 file changed, 40 insertions(+) diff --git a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd index f0b4f821..fa8c14ae 100644 --- a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd @@ -237,6 +237,11 @@ Rail transport, Roads and road transport Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. + + Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 @@ -252,6 +257,11 @@ Rail transport, Roads and road transport Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. + + @@ -290,6 +300,11 @@ Rail transport, Roads and road transport Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. + + Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 @@ -305,6 +320,11 @@ Rail transport, Roads and road transport Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. + + @@ -345,6 +365,11 @@ Rail transport, Roads and road transport Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. + + Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 @@ -360,6 +385,11 @@ Rail transport, Roads and road transport Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. + + @@ -400,6 +430,11 @@ Rail transport, Roads and road transport Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. + + Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 @@ -415,6 +450,11 @@ Rail transport, Roads and road transport Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. + + From 7df489ac251e2bca5bc1a2e72d8697312b9a4c32 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 6 Nov 2019 19:24:10 +0100 Subject: [PATCH 019/290] CR017: all enum values to lowercase --- xsd/siri_model/siri_reference-v2.0.xsd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xsd/siri_model/siri_reference-v2.0.xsd b/xsd/siri_model/siri_reference-v2.0.xsd index 46223232..2f7c256b 100644 --- a/xsd/siri_model/siri_reference-v2.0.xsd +++ b/xsd/siri_model/siri_reference-v2.0.xsd @@ -653,12 +653,12 @@ Values for these elements can be specified on an annual schedule and will be inh The vehicle can currently accommodate only standing passengers. - + The vehicle can currently accommodate only standing passengers and has limited space for them. - + The vehicle cannot accept passengers. From 11d81889d33cfd040b85a3423ad39d44b5ae9693 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Thu, 7 Nov 2019 12:53:09 +0100 Subject: [PATCH 020/290] correct lang attr. in examples and empty struct. --- .../exs_stopMonitoring_response_complex.xml | 18 +++++++++--------- .../exd_allServices_capabilitiesResponse.xml | 3 +-- 2 files changed, 10 insertions(+), 11 deletions(-) diff --git a/examples/siri_exm_SM/exs_stopMonitoring_response_complex.xml b/examples/siri_exm_SM/exs_stopMonitoring_response_complex.xml index d3a54f8f..4b48f27c 100644 --- a/examples/siri_exm_SM/exs_stopMonitoring_response_complex.xml +++ b/examples/siri_exm_SM/exs_stopMonitoring_response_complex.xml @@ -24,8 +24,8 @@ 2004-12-17T09:30:47-05:00 PT3M HLTST011 - British Museum Stop A - Musee Britannique Halte A + British Museum Stop A + Musee Britannique Halte A 2004-12-17T09:25:46-05:00 @@ -58,8 +58,8 @@ Roman Road PLACE45 - Paradise Park - Parc du Paradis + Paradise Park + Parc du Paradis Boris Special Kensall Green @@ -95,8 +95,8 @@ HLT0010 2 - Town Hall - Hotel de Ville + Town Hall + Hotel de Ville false 2004-12-17T09:32:43-05:00 2004-12-17T09:32:43-05:00 @@ -125,8 +125,8 @@ HLTST012 4 - Church - Eglise + Church + Eglise false 2004-12-17T09:30:56-05:00 2004-12-17T09:30:56-05:00 @@ -267,7 +267,7 @@ 2004-12-17T09:55:47-05:00 onTime - Approaching stop + Approaching stop 2 PT10M PT11M diff --git a/examples/siri_exu_capability/exd_allServices_capabilitiesResponse.xml b/examples/siri_exu_capability/exd_allServices_capabilitiesResponse.xml index 767ce6a7..74143dac 100644 --- a/examples/siri_exu_capability/exd_allServices_capabilitiesResponse.xml +++ b/examples/siri_exu_capability/exd_allServices_capabilitiesResponse.xml @@ -487,8 +487,7 @@ false false - - + From d095acff120e44a8e30fa5d1b3acfecae81dd72d Mon Sep 17 00:00:00 2001 From: Adrian A Date: Thu, 7 Nov 2019 13:25:35 +0100 Subject: [PATCH 021/290] CR051: add old value again and mark it deprecated --- xsd/siri_model/siri_modes-v1.1.xsd | 3 +++ 1 file changed, 3 insertions(+) diff --git a/xsd/siri_model/siri_modes-v1.1.xsd b/xsd/siri_model/siri_modes-v1.1.xsd index e5d15d22..23951c67 100644 --- a/xsd/siri_model/siri_modes-v1.1.xsd +++ b/xsd/siri_model/siri_modes-v1.1.xsd @@ -281,6 +281,9 @@ Rail transport, Roads and road transport + + + From 9f0d858ca46a6638ea440072bb1fd2ca5eed24a2 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Thu, 7 Nov 2019 13:26:15 +0100 Subject: [PATCH 022/290] CR056: rename the new Branding simpleType --- xsd/siri_model/siri_reference-v2.0.xsd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xsd/siri_model/siri_reference-v2.0.xsd b/xsd/siri_model/siri_reference-v2.0.xsd index aa63f11e..d1a959e9 100644 --- a/xsd/siri_model/siri_reference-v2.0.xsd +++ b/xsd/siri_model/siri_reference-v2.0.xsd @@ -692,7 +692,7 @@ Values for these elements can be specified on an annual schedule and will be inh - + Type for identifier of a BRANDING. @@ -703,7 +703,7 @@ Values for these elements can be specified on an annual schedule and will be inh Type for reference to a BRANDING. - + From 15698c715bb4743f82726fe1740b9d48c2e51331 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Thu, 7 Nov 2019 13:59:57 +0100 Subject: [PATCH 023/290] CR056: add missing import for the TypeOfValue dep. --- xsd/siri_model/siri_reference-v2.0.xsd | 1 + 1 file changed, 1 insertion(+) diff --git a/xsd/siri_model/siri_reference-v2.0.xsd b/xsd/siri_model/siri_reference-v2.0.xsd index d1a959e9..db96b91b 100644 --- a/xsd/siri_model/siri_reference-v2.0.xsd +++ b/xsd/siri_model/siri_reference-v2.0.xsd @@ -89,6 +89,7 @@ Rail transport, Roads and road transport + From 2a12b3dfe08fbc819fd57429c076805f594fd86f Mon Sep 17 00:00:00 2001 From: Adrian A Date: Thu, 7 Nov 2019 16:56:32 +0100 Subject: [PATCH 024/290] CR018: add xxxBoardingActivity to RecordedCall --- xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index ff258f06..38daf407 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -393,6 +393,11 @@ the original journey and the nature of the difference. (iii) any departure platform name on any related dated timetable CALL. + + + Type of boarding and alighting at stop, e.g. alighting, noAlighting or passThru. + + Assignment of arrival of Scheduled STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure +SIRI v2.0. @@ -418,6 +423,11 @@ the original journey and the nature of the difference. Estimated time of departure of VEHICLE. + + + Nature of boarding at stop, e.g. boarding, noBoarding or passThru. + + Assignments of departure platfiorm for Scheduled STOP POINT to a physical QUAY. +SIRI v2.0. From 71dad244ee4124b2d78c1682591f30423ece937f Mon Sep 17 00:00:00 2001 From: Adrian A Date: Thu, 7 Nov 2019 16:58:01 +0100 Subject: [PATCH 025/290] CR044: add xxxStatus to RecordedCall --- xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index 38daf407..96b15594 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -385,6 +385,11 @@ the original journey and the nature of the difference. + + + Classification of the timeliness of the visit according to a fixed list of values. If not specified, same as DepartureStatus. + + Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicel to arrive at.Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is @@ -423,6 +428,11 @@ the original journey and the nature of the difference. Estimated time of departure of VEHICLE. + + + 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. + + Nature of boarding at stop, e.g. boarding, noBoarding or passThru. From 5cb33620fad145d5796a55d2273aa3011842a2fb Mon Sep 17 00:00:00 2001 From: Adrian A Date: Thu, 7 Nov 2019 17:51:24 +0100 Subject: [PATCH 026/290] CR023: add indirect ref to ConnectingJourneyRef --- xsd/siri_model/siri_journey_support-v2.0.xsd | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/xsd/siri_model/siri_journey_support-v2.0.xsd b/xsd/siri_model/siri_journey_support-v2.0.xsd index 82a01de7..bf4bba73 100644 --- a/xsd/siri_model/siri_journey_support-v2.0.xsd +++ b/xsd/siri_model/siri_journey_support-v2.0.xsd @@ -182,11 +182,16 @@ Rail transport, Roads and road transport Type for a reference to a connecting journey. - + A reference to the DATE VEHICLE JOURNEY that the VEHICLE is making, unique with the data horizon of the service. + + + Optionally identify the VEHICLE JOURNEY indirectly by origin and destination and the scheduled times at these stops. + + LINE Reference. From 7db77c0e24b1c560e6181d72594697d0e2f3eb66 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Thu, 7 Nov 2019 17:51:57 +0100 Subject: [PATCH 027/290] CR023: restore optional flag of Framed..JourneyRef --- xsd/siri_model/siri_journey_support-v2.0.xsd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xsd/siri_model/siri_journey_support-v2.0.xsd b/xsd/siri_model/siri_journey_support-v2.0.xsd index bf4bba73..26e7182a 100644 --- a/xsd/siri_model/siri_journey_support-v2.0.xsd +++ b/xsd/siri_model/siri_journey_support-v2.0.xsd @@ -182,7 +182,7 @@ Rail transport, Roads and road transport Type for a reference to a connecting journey. - + A reference to the DATE VEHICLE JOURNEY that the VEHICLE is making, unique with the data horizon of the service. From d17524bd7ed3fa6a383ef210b1c4f664a844cdb8 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Sun, 10 Nov 2019 22:57:12 +0100 Subject: [PATCH 028/290] CR022: extend EstimatedServiceJourneyInterchange --- .../siri_estimatedVehicleJourney-v2.0.xsd | 72 ++++++++++++++++--- 1 file changed, 62 insertions(+), 10 deletions(-) diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index ce2d84ee..530ce93a 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -86,6 +86,8 @@ Rail transport, Roads and road transport + + @@ -202,7 +204,7 @@ DEPRECATED from SRI 2.0 - A VEHICLE JOURNEY taking place on a particular date that will be managed by an AVMs. + A real-time SERVICE JOURNEY INTERCHANGE that may be made between the stops of two monitored journeys. It includes the current real-time predicted transfer and wait times. +SIRI v2.0 @@ -215,7 +217,20 @@ DEPRECATED from SRI 2.0 - Reference to a connecting distributor VEHICLE JOURNEY. +SIRI v2.0 + Reference to a connecting feeder VEHICLE JOURNEY. +SIRI v2.0 + + + + + SCHEDULED STOP POINT at which feeder journey arrives. +Assuming, for example, that the feeder is redirected to another QUAY by a dispositive measure in order to shorten the transfer time, +how do we communicate this change in the interchange? If the STOP POINTs are modelled QUAY accurate, FeederArrivalStopRef should always +reference the STOP POINT of the new/expected QUAY (which was transmitted in the ESTIMATED VEHICLE JOURNEY). +SIRI v2.1 + + + + + Planned time at which feeder VEHICLE is scheduled to arrive. SIRI v2.1 @@ -223,20 +238,42 @@ DEPRECATED from SRI 2.0 Reference to a connecting distributor VEHICLE JOURNEY. +SIRI v2.0 + + + SCHEDULED STOP POINT at which distributor journey departs. +Assuming that the distributor is directed to another QUAY (and that STOP POINTs are modelled QUAY accurate), DistributorDepartureStopRef +should always reference the STOP POINT of the new/expected QUAY (which was transmitted in the ESTIMATED VEHICLE JOURNEY). +SIRI v2.1 + + + + + Planned time at which distributor VEHICLE is scheduled to depart. SIRI v2.1 + + + + + Whether this interchange is planned, updated, additional or cancelled. +SIRI v2.1 + + - Distributor will not wait (i.e. connection broken) SIRI w.0 + Distributor will not wait, i.e., connection is not guaranteed or broken. SIRI 2.0 - Nature of wait that distributer will make. +SIRI v2.0 + Details about how (long) the distributor services may be held in order to guarantee the connection. +SIRI v2.0 + + + Time at which feeder VEHICLE is expected to arrive. +SIRI v2.1 + + Time at which distributor VEHICLE is expected to depart. +SIRI v2.0 @@ -244,9 +281,16 @@ DEPRECATED from SRI 2.0 - Whether connection monitoring is active or not for this connection +SIRI v2.0 + Whether connection monitoring is active or not for this connection. +SIRI v2.0 + + + Contains various types of transfer and wait times. +Implementation Note: what happens if, for example, the interchange times and a QUAY change in xxxStopAssignment of the ESTIMATED VEHICLE JOURNEY suggest contradictory transfer/wait times? +In case of doubt, the interchange times are to be favoured because they are transmitted explicitly. +SIRI v2.1 + + @@ -259,11 +303,19 @@ DEPRECATED from SRI 2.0 Time up until which the distributor will wait. +SIRI v2.0 - - - Whether an acknowledgement has been received that the driver will wait. +SIRI v2.0 - - + + + + Whether an acknowledgement has been received that the driver will wait. +DEPRECATED since SIRI v2.1 + + + + + Whether an acknowledgement has been received that the driver will wait. +SIRI v2.1 + + + From 680f086671ac7ee92eb630e38b12feb6f4941eac Mon Sep 17 00:00:00 2001 From: Adrian A Date: Sun, 10 Nov 2019 22:57:26 +0100 Subject: [PATCH 029/290] CR022: extend InterchangeStatusEnum by CM values --- .../siri_situationServiceTypes-v1.0.xsd | 51 ++++++++++++++++++- 1 file changed, 49 insertions(+), 2 deletions(-) diff --git a/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd b/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd index f3c5c463..88a45920 100644 --- a/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd +++ b/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd @@ -110,7 +110,7 @@ Rail transport, Roads and road transport - Status of a SERVICE JOURNEY INTERCHANGE Status TPEG cross reference pti31. + Status of a SERVICE JOURNEY INTERCHANGE / Status TPEG cross reference pti31. @@ -118,8 +118,55 @@ Rail transport, Roads and road transport Values for Interchange Status TPEG cross reference pti_table 31. + + + Interchange is planned. + + + + + Interchange is planned but was updated as a result of changes in the QUAYs or arrival/departure times. + + + + + An important function of connection protection is the ability to hold back a distributor VEHICLE (i.e. prolonged waiting) +to allow passengers to transfer from delayed feeders. To achieve this a distributorWaitProlonged status shall be communicated back to the feeder VEHICLEs to inform +the passengers about the new departure time of the distributor or even a willWait guarantee. + + + + + Interchange is planned but was updated as a result of changes in the QUAYs or arrival/departure times. + + + + + Interchange is an addition to the plan. + + + + + Interchange is a cancellation of an interchange in the plan. + + + + + Loss of the inbound connection indicates the cancellation of the visit (of the FeederJourney) to the FeederArrivalStop, or a severely delayed arrival. +This can lead to the distributor VEHICLE abandoning the connection. There are several possible reasons for the loss of a feeder, e.g. loss/cancellation of the feeder VEHICLE, diversion of the feeder LINE/DIRECTION, disruption of a LINE section etc. + + + + + Indicates the loss of an outbound connection, i.e., is used to signal the cancellation of the onward connection to the passengers in the feeder VEHICLEs. + + + + + There is no data available on the interchange status. + + - From 08a2df639c5c5e37d714769107deb477b1dbcccc Mon Sep 17 00:00:00 2001 From: Adrian A Date: Mon, 11 Nov 2019 14:06:38 +0100 Subject: [PATCH 030/290] CR044: add missing attrib. minOccurs to new fields --- xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index 96b15594..4d3e470e 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -385,7 +385,7 @@ the original journey and the nature of the difference. - + Classification of the timeliness of the visit according to a fixed list of values. If not specified, same as DepartureStatus. @@ -428,7 +428,7 @@ the original journey and the nature of the difference. Estimated time of departure of VEHICLE. - + 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. From 4b62ada51c5b00969240c8bc188f4bc17a7928ba Mon Sep 17 00:00:00 2001 From: Adrian A Date: Mon, 11 Nov 2019 16:55:17 +0100 Subject: [PATCH 031/290] CR051: replace deprecated comment with annotation --- xsd/siri_model/siri_modes-v1.1.xsd | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/xsd/siri_model/siri_modes-v1.1.xsd b/xsd/siri_model/siri_modes-v1.1.xsd index 23951c67..e3f876c2 100644 --- a/xsd/siri_model/siri_modes-v1.1.xsd +++ b/xsd/siri_model/siri_modes-v1.1.xsd @@ -281,9 +281,11 @@ Rail transport, Roads and road transport - - - + + + DEPRECATED since SIRI 2.1 + + From 1cdf34f243a07b4a1e3ada1babcde0c39a450501 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Fri, 20 Dec 2019 13:33:41 +0100 Subject: [PATCH 032/290] CR013: correct typo in ValueSetIdType and indent. --- xsd/siri_utility/siri_utility-v1.1.xsd | 52 +++++++++++++------------- 1 file changed, 26 insertions(+), 26 deletions(-) diff --git a/xsd/siri_utility/siri_utility-v1.1.xsd b/xsd/siri_utility/siri_utility-v1.1.xsd index a96b6713..792101cd 100644 --- a/xsd/siri_utility/siri_utility-v1.1.xsd +++ b/xsd/siri_utility/siri_utility-v1.1.xsd @@ -102,7 +102,7 @@ Rail transport, Roads and road transport Key value pair for Entity. - + @@ -113,8 +113,8 @@ Rail transport, Roads and road transport - Identifier of value e.g. System. - + Identifier of value e.g. System. + @@ -175,28 +175,28 @@ Rail transport, Roads and road transport - Name of TYPE OF VALUE. - + Name of TYPE OF VALUE. + - Short Name for TYPE OF VALUE. - + Short Name for TYPE OF VALUE. + - - Description of TYPE OF VALUE. - + + Description of TYPE OF VALUE. + - - Default image for TYPE OF VALUE. - + + Default image for TYPE OF VALUE. + - - Default URL for TYPE OF VALUE. - + + Default URL for TYPE OF VALUE. + @@ -208,11 +208,11 @@ Rail transport, Roads and road transport - - - - - + + + + + @@ -231,7 +231,7 @@ Rail transport, Roads and road transport - + Name of Class of Values in Set. @@ -245,12 +245,12 @@ Rail transport, Roads and road transport - Name of Value. - + Name of Value. + - Values in Set. + Values in Set. @@ -270,7 +270,7 @@ Rail transport, Roads and road transport - + Type for identifier of a VALUE SET. From 85f1f03ac45314d1335e30bb9a1b1e74d313c6f8 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Fri, 20 Dec 2019 13:47:10 +0100 Subject: [PATCH 033/290] CR005: change JourneyPartInfo and update annot. --- xsd/siri_model/siri_journey-v2.0.xsd | 51 ++++++++++++++++------------ 1 file changed, 30 insertions(+), 21 deletions(-) diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index 38e93d58..dfbd4106 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -900,7 +900,7 @@ Rail transport, Roads and road transport - Provides information about relations to other journeys. + Provides information about relations to other journeys. +SIRI v2.1 @@ -910,8 +910,8 @@ Rail transport, Roads and road transport - Specifies the type of the relation, e.g., joining, splitting, replacement etc. - + Specifies the type of the relation, e.g., joining, splitting, replacement etc. +SIRI v2.1 + @@ -919,39 +919,48 @@ Rail transport, Roads and road transport - Specifies which CALL or JOURNEY PART of the JOURNEY has a JOURNEY RELATION. + Specifies which CALL or JOURNEY PART of the JOURNEY has a JOURNEY RELATION. +SIRI v2.1 - - Information about the stop at which the JOURNEY is related to another JOURNEY. - - - - - Information about the JOURNEY PART for which the JOURNEY has a JOURNEY RELATION. - - + + Information about the stop at which the JOURNEY is related to another JOURNEY. +SIRI v2.1 + + + + + Information about the JOURNEY PARTs for which the JOURNEY has a JOURNEY RELATION. +SIRI v2.1 + + + + + + Information about related parts of JOURNEY. +SIRI v2.1 + + + + + - The JOURNEY RELATION refers to this CALL. + The JOURNEY RELATION refers to this CALL. +SIRI v2.1 - - - + + + - The JOURNEY RELATION refers to this JOURNEY PART. + The JOURNEY RELATION refers to this JOURNEY PART. +SIRI v2.1 @@ -959,15 +968,15 @@ Rail transport, Roads and road transport - Refers to the JOURNEY to which the current JOURNEY is related. + Refers to the JOURNEY to which the current JOURNEY is related. +SIRI v2.1 - - + + From acbc82f54aa85529069d9fbc69798b2df4ad4724 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Fri, 20 Dec 2019 13:50:03 +0100 Subject: [PATCH 034/290] CR005: make JourneyPartRef optional and fix annot. --- .../siri_monitoredVehicleJourney-v2.0.xsd | 50 +++++++++---------- 1 file changed, 25 insertions(+), 25 deletions(-) diff --git a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd index dadccd54..7106f7f3 100644 --- a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd @@ -304,12 +304,12 @@ For SIRI-VM this is the most recent stop visited by the VEHICLE. - Type for a refernces to JOURNEY PARTs. +SIRI v2.0 + Type for a reference to JOURNEY PART. +SIRI v2.0 - + - Refrence to a JOURNEY part. +SIRI v2.0 + Reference to a JOURNEY part. +SIRI v2.0 @@ -322,34 +322,34 @@ For SIRI-VM this is the most recent stop visited by the VEHICLE.Operator of JOURNEY PART. +SIRI v2.0 - + - JourneyPart information instead of or in addition to the JourneyPartRef. +SIRI v2.0 + JourneyPart information instead of or in addition to the JourneyPartRef. +SIRI v2.1 - - - Reference to the SCHEDULED STOP POINT at which the related JOURNEY PART begins. - - - - - Reference to the SCHEDULED STOP POINT at which the related JOURNEY PART ends. - - - - - Time at which the related JOURNEY PART begins. - - - - - Time at which the related JOURNEY PART ends. - - + + + Reference to the SCHEDULED STOP POINT at which the related JOURNEY PART begins. + + + + + Reference to the SCHEDULED STOP POINT at which the related JOURNEY PART ends. + + + + + Time at which the related JOURNEY PART begins. + + + + + Time at which the related JOURNEY PART ends. + + From 6beeee95cf668e2427e253ab421a2dfd5af2ec68 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Fri, 20 Dec 2019 13:59:26 +0100 Subject: [PATCH 035/290] CR022: harmonize ET Interchange with PT --- .../siri_estimatedVehicleJourney-v2.0.xsd | 41 ++++++++++++++++++- 1 file changed, 39 insertions(+), 2 deletions(-) diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index 530ce93a..c5b6b983 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -215,6 +215,11 @@ DEPRECATED from SRI 2.0 + + + Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY INTERCHANGE takes place. +SIRI v2.0 + + Reference to a connecting feeder VEHICLE JOURNEY. +SIRI v2.0 @@ -227,6 +232,18 @@ Assuming, for example, that the feeder is redirected to another QUAY by a dispos how do we communicate this change in the interchange? If the STOP POINTs are modelled QUAY accurate, FeederArrivalStopRef should always reference the STOP POINT of the new/expected QUAY (which was transmitted in the ESTIMATED VEHICLE JOURNEY). +SIRI v2.1 + + + + Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. + + + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, +ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of +despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 + @@ -244,6 +261,18 @@ reference the STOP POINT of the new/expected QUAY (which was transmitted in the Assuming that the distributor is directed to another QUAY (and that STOP POINTs are modelled QUAY accurate), DistributorDepartureStopRef should always reference the STOP POINT of the new/expected QUAY (which was transmitted in the ESTIMATED VEHICLE JOURNEY). +SIRI v2.1 + + + + Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. + + + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, +ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of +despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 + @@ -252,6 +281,13 @@ should always reference the STOP POINT of the new/expected QUAY (which was trans + + + Properties of SERVICE JOURNEY INTERCHANGE. It is important to note that the InterchangePropertyGroup displays planning data whereas, for example, +InterchangeStatus or Will(Not)Wait contain the real-time data. A SERVICE JOURNEY INTERCHANGE may be transmitted with "Guaranteed=true", but also WillNotWait due to major despatching alterations. +However, Will(Not)Wait will always take precedence over the property Guaranteed, which means that WillNotWait breaks the connection regardless of whether Guarateed was transmitted. +SIRI v2.1 + + Whether this interchange is planned, updated, additional or cancelled. +SIRI v2.1 @@ -284,13 +320,14 @@ should always reference the STOP POINT of the new/expected QUAY (which was trans Whether connection monitoring is active or not for this connection. +SIRI v2.0 - + - Contains various types of transfer and wait times. + Contains various types of transfer and wait times of a SERVICE JOURNEY INTERCHANGE. Implementation Note: what happens if, for example, the interchange times and a QUAY change in xxxStopAssignment of the ESTIMATED VEHICLE JOURNEY suggest contradictory transfer/wait times? In case of doubt, the interchange times are to be favoured because they are transmitted explicitly. +SIRI v2.1 + From c8d593cfb04deba2861e47b31374db2cab85b9b9 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Fri, 20 Dec 2019 14:13:11 +0100 Subject: [PATCH 036/290] CR008: change annotation of SubscriptionRenewal --- xsd/siri/siri_requests-v2.0.xsd | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/xsd/siri/siri_requests-v2.0.xsd b/xsd/siri/siri_requests-v2.0.xsd index f7ef5dce..e1ed5605 100644 --- a/xsd/siri/siri_requests-v2.0.xsd +++ b/xsd/siri/siri_requests-v2.0.xsd @@ -289,8 +289,10 @@ Rail transport, Roads and road transport - By using this element, the subscriber informs the data provider that no data is requested but only an extension of the InitialTerminationTime of the subscription. It is therefore not necessary to transmit any journey or interchange information (corresponding to the subscription) in the next response. Only the data triggered by hysteresis / ChangeBeforeUpdate, PreviewInterval etc. needs to be sent. If SubscriptionRenewal is omitted, all data corresponding to the SubscriptionRequest must be sent in the initial response (or a portion of the data if MoreData is set to 'true'). - + By using this element, the subscriber asks the data provider for an extension of the InitialTerminationTime of the subscription. +If SubscriptionRenewal is omitted, this request is to be treated as a re-subscription and therefore all data corresponding to the SubscriptionRequest must +be sent in the initial response (or a portion of the data if MoreData is set to 'true'). +SIRI v2.1 + From 2acd95b69cce31e732a78cd1ff122c7a244c6274 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 8 Jan 2020 14:13:15 +0100 Subject: [PATCH 037/290] CR024: add aimed times to interchange feed./distr. --- .../siri_datedVehicleJourney-v2.0.xsd | 80 +++++++++++++++++++ 1 file changed, 80 insertions(+) diff --git a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd index f0b4f821..91a8b2a1 100644 --- a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd @@ -237,6 +237,16 @@ Rail transport, Roads and road transport Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 + + + + + Planned time at which feeder VEHICLE is scheduled to arrive. SIRI v2.1 + + Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 @@ -252,6 +262,16 @@ Rail transport, Roads and road transport Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 + + + + + Planned time at which distributor VEHICLE is scheduled to depart. SIRI v2.1 + + @@ -290,6 +310,16 @@ Rail transport, Roads and road transport Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 + + + + + Planned time at which feeder VEHICLE is scheduled to arrive. SIRI v2.1 + + Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 @@ -305,6 +335,16 @@ Rail transport, Roads and road transport Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 + + + + + Planned time at which distributor VEHICLE is scheduled to depart. SIRI v2.1 + + @@ -345,6 +385,16 @@ Rail transport, Roads and road transport Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 + + + + + Planned time at which feeder VEHICLE is scheduled to arrive. SIRI v2.1 + + Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 @@ -360,6 +410,16 @@ Rail transport, Roads and road transport Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 + + + + + Planned time at which distributor VEHICLE is scheduled to depart. SIRI v2.1 + + @@ -400,6 +460,16 @@ Rail transport, Roads and road transport Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 + + + + + Planned time at which feeder VEHICLE is scheduled to arrive. SIRI v2.1 + + Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 @@ -415,6 +485,16 @@ Rail transport, Roads and road transport Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 + + + + + Planned time at which distributor VEHICLE is scheduled to depart. SIRI v2.1 + + From 885176d92f2a9727aab57d9df653c859e1b89757 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 8 Jan 2020 15:17:37 +0100 Subject: [PATCH 038/290] CR022: add InterchangeCode option / move PropGroup --- .../siri_estimatedVehicleJourney-v2.0.xsd | 25 +++++++++++-------- 1 file changed, 15 insertions(+), 10 deletions(-) diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index c5b6b983..07f4d819 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -215,7 +215,12 @@ DEPRECATED from SRI 2.0 - + + + Identifier of ESTIMATED SERVICE JOURNEY INTERCHANGE in case it is an addition to the plan. +SIRI v2.1 + + + Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY INTERCHANGE takes place. +SIRI v2.0 @@ -233,7 +238,7 @@ how do we communicate this change in the interchange? If the STOP POINTs are mod reference the STOP POINT of the new/expected QUAY (which was transmitted in the ESTIMATED VEHICLE JOURNEY). +SIRI v2.1 - + Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. @@ -262,7 +267,7 @@ Assuming that the distributor is directed to another QUAY (and that STOP POINTs should always reference the STOP POINT of the new/expected QUAY (which was transmitted in the ESTIMATED VEHICLE JOURNEY). +SIRI v2.1 - + Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. @@ -279,15 +284,15 @@ despatching alterations. Because such an extra CALL may have the same VisitNumbe Planned time at which distributor VEHICLE is scheduled to depart. SIRI v2.1 - - - - - Properties of SERVICE JOURNEY INTERCHANGE. It is important to note that the InterchangePropertyGroup displays planning data whereas, for example, + + + Properties of SERVICE JOURNEY INTERCHANGE. It is important to note that the InterchangePropertyGroup displays planning data whereas, for example, InterchangeStatus or Will(Not)Wait contain the real-time data. A SERVICE JOURNEY INTERCHANGE may be transmitted with "Guaranteed=true", but also WillNotWait due to major despatching alterations. However, Will(Not)Wait will always take precedence over the property Guaranteed, which means that WillNotWait breaks the connection regardless of whether Guarateed was transmitted. +SIRI v2.1 - - + + + + Whether this interchange is planned, updated, additional or cancelled. +SIRI v2.1 From c08b15a12f0b953aba173ac79ac8253ad6c9a8c7 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Sat, 11 Jan 2020 00:16:30 +0100 Subject: [PATCH 039/290] CR056: update BrandingStructure (NeTEx ID -> Code) --- xsd/siri_model/siri_reference-v2.0.xsd | 28 ++++++++++---------------- 1 file changed, 11 insertions(+), 17 deletions(-) diff --git a/xsd/siri_model/siri_reference-v2.0.xsd b/xsd/siri_model/siri_reference-v2.0.xsd index db96b91b..91cf0896 100644 --- a/xsd/siri_model/siri_reference-v2.0.xsd +++ b/xsd/siri_model/siri_reference-v2.0.xsd @@ -430,12 +430,12 @@ Values for these elements can be specified on an annual schedule and will be inh - Reference to a BRANDING. + Reference to a BRANDING. +SIRI v2.1 - An arbitrary marketing classification. + An arbitrary marketing classification. +SIRI v2.1 @@ -695,13 +695,13 @@ Values for these elements can be specified on an annual schedule and will be inh - Type for identifier of a BRANDING. + Type for identifier of a BRANDING. +SIRI v2.1 - Type for reference to a BRANDING. + Type for reference to a BRANDING. +SIRI v2.1 @@ -709,22 +709,16 @@ Values for these elements can be specified on an annual schedule and will be inh - An arbitrary marketing classification. + An arbitrary marketing classification. +SIRI v2.1 - + + + Identity of BRANDING. + + + - - - Identity of object from which this BRANDING was derived. - - - - - Type for identifier of BRANDING. - - - From 3c4b7aa1dbdf58c315dfcd2cba99cb3d65a82baf Mon Sep 17 00:00:00 2001 From: Adrian A Date: Sat, 11 Jan 2020 00:17:13 +0100 Subject: [PATCH 040/290] CR013: revise TypeOfValue model (remove NeTEx IDs) --- xsd/siri_utility/siri_utility-v1.1.xsd | 160 +++++++++++++++---------- 1 file changed, 97 insertions(+), 63 deletions(-) diff --git a/xsd/siri_utility/siri_utility-v1.1.xsd b/xsd/siri_utility/siri_utility-v1.1.xsd index 792101cd..5ea49501 100644 --- a/xsd/siri_utility/siri_utility-v1.1.xsd +++ b/xsd/siri_utility/siri_utility-v1.1.xsd @@ -83,9 +83,9 @@ Rail transport, Roads and road transport - A list of alternative Key values for an element. + A list of alternative Key values for an element. +SIRI v2.1 - + Every Key Value Pair must be unique. @@ -96,7 +96,7 @@ Rail transport, Roads and road transport - Type for a Key List. + Type for a Key List. +SIRI v2.1 @@ -108,7 +108,7 @@ Rail transport, Roads and road transport - Type for a Key List. + Type for a Key List. +SIRI v2.1 @@ -121,22 +121,31 @@ Rail transport, Roads and road transport Value for alternative key. + + + Identifier of type of key. + + - - - Identifier of type of key. - - - VALUE SETs and TYPE OF VALUEs in frame. + VALUE SETs and TYPE OF VALUEs as part of the SIRI extension model. +TYPES OF VALUE can be used to exchange metadata for validation or collection of data, +such as the description and allowed values for codes. +SIRI v2.1 + + + VALUE SETs must be unique. + + + + - Type for containment in frame of TYPE OF VALUEs. + Type for containment of VALUE SETs and/or TYPE OF VALUEs. +SIRI v2.1 @@ -145,32 +154,30 @@ Rail transport, Roads and road transport - A code value from an extensible set, i.e. which may be added to by user applications and is used to validate the properties of Entities. + A code value from an extensible set which may be added to by user applications, and is used to classify other SIRI entities. +SIRI v2.1 - - - - - - - - - - - + - Type for a TYPE OF VALUE. Abstract supertype used to define open classifications of value types. + Type for a TYPE OF VALUE. Used to define open classifications of value types. +SIRI v2.1 + + + Identifier of a TYPE OF VALUE. + + + + + Name of class of which TypeOfValue is an instance. + + - - - Elements for TYPE OF VALUE. + Elements for TYPE OF VALUE. +SIRI v2.1 @@ -198,97 +205,124 @@ Rail transport, Roads and road transport Default URL for TYPE OF VALUE. - + + + Arbitrary code (usually the technical part of the identifier). + + - An extensible set of code values which may be added to by user applications and is used to validate the properties of Entities. + An extensible set of code values which may be added to by user applications and is used to validate the properties of entities. +Contains TYPE OF VALUEs that are an instance of the same class. +SIRI v2.1 + + + Identifier of VALUE SET. + + + + + Name of Class of values in set. + + - - - - + + + TYPE OF VALUEs of the set must be unique. + + + - - - - - Type for a VALUE SET. Abstract supertype used to define open classifications of value types. + Type for a VALUE SET. Used to define open classifications of value types. +SIRI v2.1 + + + Identifier of VALUE SET. + + + + + Name of Class of values in set. + + - - - - Name of Class of Values in Set. - - - Elements for VALUE SET. + Elements for VALUE SET. +SIRI v2.1 - Name of Value. + Name of set. - + - Values in Set. + Values in set. - Type for a list of TYPEs OF VALUE. + Type for a list of TYPE OF VALUEs. +SIRI v2.1 - + - Type for identifier of a TYPE OF VALUE. + Type for identifier of a TYPE OF VALUE. +SIRI v2.1 - + - + - Type for identifier of a VALUE SET. + Type for reference to a TYPE OF VALUE. +SIRI v2.1 - - - - + + + + + - Abstract Type for identifier of a SIRI Object. + Type for identifier of a VALUE SET. +SIRI v2.1 - + - - + - Name of class of which TypeOfValue is an instance. Used for reflection. + Name of class of which TypeOfValue is an instance. Used for reflection. +SIRI v2.1 + + + A Classification of reasons for non-availability of real-time data. Serves as an example for the usefulness of the TYPE OF VALUEs extension. Possible TypeOfMonitoringError codes could include 'NoError', 'GpsLocalisation' or 'RadioConnection'. + + + + + + + From b3781288f9382d10b00f8a30deb5ebef35b1c735 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Sat, 11 Jan 2020 00:29:59 +0100 Subject: [PATCH 041/290] CR028: update annotations of xxxStopOrder --- xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd index fa8c14ae..cb6c4b44 100644 --- a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd @@ -239,7 +239,7 @@ Rail transport, Roads and road transport - For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 @@ -259,7 +259,7 @@ Rail transport, Roads and road transport - For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 @@ -302,7 +302,7 @@ Rail transport, Roads and road transport - For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 @@ -322,7 +322,7 @@ Rail transport, Roads and road transport - For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 @@ -367,7 +367,7 @@ Rail transport, Roads and road transport - For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 @@ -387,7 +387,7 @@ Rail transport, Roads and road transport - For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 @@ -432,7 +432,7 @@ Rail transport, Roads and road transport - For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 @@ -452,7 +452,7 @@ Rail transport, Roads and road transport - For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 From a45cf6607b6e650edd201ce8febc98290823da8a Mon Sep 17 00:00:00 2001 From: Adrian A Date: Sat, 11 Jan 2020 00:34:07 +0100 Subject: [PATCH 042/290] CR014: update annotations of the new elements --- xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index ff258f06..f0bfab47 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -395,7 +395,7 @@ the original journey and the nature of the difference. - Assignment of arrival of Scheduled STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure +SIRI v2.0. + Assignment of arrival of Scheduled STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. +SIRI v2.1 @@ -420,7 +420,7 @@ the original journey and the nature of the difference. - Assignments of departure platfiorm for Scheduled STOP POINT to a physical QUAY. +SIRI v2.0. + Assignments of departure platfiorm for Scheduled STOP POINT to a physical QUAY. +SIRI v2.1 From 5379632553a3bac57b10c6b5bcbcb08291058296 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Sat, 11 Jan 2020 00:36:07 +0100 Subject: [PATCH 043/290] CR018: update annotations of the new elements --- xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index 38daf407..0c13f036 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -395,7 +395,7 @@ the original journey and the nature of the difference. - Type of boarding and alighting at stop, e.g. alighting, noAlighting or passThru. + Type of boarding and alighting at stop, e.g. alighting, noAlighting or passThru. +SIRI v2.1 @@ -425,7 +425,7 @@ the original journey and the nature of the difference. - Nature of boarding at stop, e.g. boarding, noBoarding or passThru. + Nature of boarding at stop, e.g. boarding, noBoarding or passThru. +SIRI v2.1 From dfca7233383c124502d57491efffb712bc7226bd Mon Sep 17 00:00:00 2001 From: Adrian A Date: Sat, 11 Jan 2020 00:39:40 +0100 Subject: [PATCH 044/290] CR044: add xCancellationReason to RecordedCall --- xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index 4d3e470e..7022da67 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -390,6 +390,11 @@ the original journey and the nature of the difference. Classification of the timeliness of the visit according to a fixed list of values. If not specified, same as DepartureStatus. + + + Text annotation to be used in cases where ArrivalStatus is set to 'cancelled'. +SIRI v2.1 + + Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicel to arrive at.Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is @@ -433,6 +438,11 @@ the original journey and the nature of the difference. Classification of the timeliness of the departure part of the CALL, according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are still classified as on-time. Applications may use this to guide their own presentation of times. + + + Text annotation to be used in cases where DepartureStatus is set to 'cancelled'. +SIRI v2.1 + + Nature of boarding at stop, e.g. boarding, noBoarding or passThru. From 54cd97269e46f15638727fbb399b21d50637ce42 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Sat, 11 Jan 2020 00:40:14 +0100 Subject: [PATCH 045/290] CR044: add xCancellationReason to OnwardCallGroup --- xsd/siri_model/siri_journey-v2.0.xsd | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index b95675a7..23132593 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -455,6 +455,7 @@ Rail transport, Roads and road transport + @@ -487,6 +488,7 @@ Rail transport, Roads and road transport + @@ -755,6 +757,11 @@ Rail transport, Roads and road transport Classification of the timeliness of the visit according to a fixed list of values. If not specified, same as DepartureStatus. + + + Text annotation to be used in cases where ArrivalStatus is set to 'cancelled'. +SIRI v2.1 + + Arbitrary text string to show to indicate the status of the departure of the VEHICLE for example, “Enroute”, “5 Km”, “Approaching”. May depend on the policy of the OPERATOR, for example show “Approaching” if less than 200metres away from stop. +SIRI v2.0 @@ -825,6 +832,11 @@ Rail transport, Roads and road transport Classification of the timeliness of the departure part of the CALL, according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are still classified as on-time. Applications may use this to guide their own presentation of times. + + + Text annotation to be used in cases where DepartureStatus is set to 'cancelled'. +SIRI v2.1 + + Arbitrary text string to show to indicate the status of the departure of the vehicle, for example, “Boarding”, “GatesClosed”. +SIRI v2.0 From 27c280e943ce7420f278f8a136af4f687151d113 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Sat, 11 Jan 2020 00:40:59 +0100 Subject: [PATCH 046/290] CR044: update annot. of xxxStatus in RecordedCall --- xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index 7022da67..42de7d2d 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -387,7 +387,7 @@ the original journey and the nature of the difference. - Classification of the timeliness of the visit according to a fixed list of values. If not specified, same as DepartureStatus. + Classification of the timeliness of the visit according to a fixed list of values. If not specified, same as DepartureStatus. +SIRI v2.1 @@ -435,7 +435,7 @@ the original journey and the nature of the difference. - 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. + 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. +SIRI v2.1 From ab494af3bf09a82fedcf5964b5a9fa18c4f7d31d Mon Sep 17 00:00:00 2001 From: Adrian A Date: Sat, 11 Jan 2020 00:42:23 +0100 Subject: [PATCH 047/290] correct annotations in RecordedCallGroup --- xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index 42de7d2d..9c7306e9 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -397,7 +397,7 @@ the original journey and the nature of the difference. - Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicel to arrive at.Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is + Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicle to arrive at. Inheritable property. Can be omitted if the same as the DeparturePlatformName. If there is 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. @@ -425,7 +425,7 @@ the original journey and the nature of the difference. - Departure QUAY ( Bay or platform) name. Defaulted taken from from planned timetable.. + Bay or platform (QUAY) name from which VEHICLE will depart. Inherited property. From 94f4ce2cc77f333293559d1d0050a816de4f6b0b Mon Sep 17 00:00:00 2001 From: Adrian A Date: Sat, 11 Jan 2020 00:45:24 +0100 Subject: [PATCH 048/290] Some typo fixes in comments and text additions --- .../siri_estimatedVehicleJourney-v2.0.xsd | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index f0bfab47..499634d3 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -296,7 +296,7 @@ the original journey and the nature of the difference. - Observed call times for that art of teh journey that has already been completed. (+ SIRI 2..0) + Complete sequence of stops already visited along the route path, in calling order. Only used if observed stop data is being recorded. (SIRI 2.0) @@ -306,7 +306,7 @@ the original journey and the nature of the difference. - Estimated call times for journey + Complete sequence of stops along the route path, in calling order. Normally this is only the onwards stops from the vehicle's current position. @@ -325,12 +325,12 @@ the original journey and the nature of the difference. - Ordered sequence of SCHEDULED STOP POINTs called at by the VEHICLE JOURNEY If IsCompleteStopSequence is false, may be just those stops that are altered. + Ordered sequence of SCHEDULED STOP POINTs called at by the VEHICLE JOURNEY. If IsCompleteStopSequence is false, may be just those stops that are altered. - Type for Rea-ltime info about a VEHICLE JOURNEY Stop. + Type for real-time info about a VEHICLE JOURNEY Stop. @@ -374,7 +374,7 @@ the original journey and the nature of the difference. - Ordered sequence of SCHEDULED STOP POINTs called at by the VEHICLE JOURNEY If IsCompleteStopSequence is false, may be just those stops that are altered. + Ordered sequence of SCHEDULED STOP POINTs called at by the VEHICLE JOURNEY. Only used if observed stop data is being recorded. (SIRI 2.0) @@ -387,7 +387,7 @@ the original journey and the nature of the difference. - Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicel to arrive at.Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is + Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicle to arrive at. Inheritable property. Can be omitted if the same as the DeparturePlatformName. If there is 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. @@ -395,7 +395,7 @@ the original journey and the nature of the difference. - Assignment of arrival of Scheduled STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. +SIRI v2.1 + Assignment of arrival of Scheduled STOP POINT to a physical QUAY (platform). If not given, assume same as for departure. +SIRI v2.1 @@ -410,7 +410,7 @@ the original journey and the nature of the difference. - Departure QUAY ( Bay or platform) name. Defaulted taken from from planned timetable.. + Bay or platform (QUAY) name from which VEHICLE will depart. Inherited property. @@ -420,7 +420,7 @@ the original journey and the nature of the difference. - Assignments of departure platfiorm for Scheduled STOP POINT to a physical QUAY. +SIRI v2.1 + Assignments of departure platform for Scheduled STOP POINT to a physical QUAY. +SIRI v2.1 From 521a8b67623f4382b62266df7a761771064d2362 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Sat, 11 Jan 2020 00:52:31 +0100 Subject: [PATCH 049/290] Some typo fixes in comments and text additions --- .../siri_estimatedVehicleJourney-v2.0.xsd | 30 +++++++++---------- 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index 9c7306e9..50a46c0a 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -106,7 +106,7 @@ Rail transport, Roads and road transport - Reference to a dated VEHICLE JOURNEY. This will be 'framed' ie be with the data context of the ESTIMATED Timetable. + Reference to a dated VEHICLE JOURNEY. This will be 'framed' i.e. be with the data context of the ESTIMATED Timetable. DEPRECATED from SIRI 2.0 @@ -118,7 +118,7 @@ DEPRECATED from SIRI 2.0 - 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'. + If this is the first message for an unplanned 'extra' VEHICLE JOURNEY, a new and unique code must be given for it. ExtraJourney should be set to 'true'. DEPRECATED from SIRI 2.0 @@ -202,7 +202,7 @@ DEPRECATED from SIRI 2.0 - A VEHICLE JOURNEY taking place on a particular date that will be managed by an AVMs. + A real-time SERVICE JOURNEY INTERCHANGE that may be made between the stops of two monitored journeys. It includes the current real-time predicted transfer and wait times. +SIRI v2.0 @@ -228,12 +228,12 @@ DEPRECATED from SIRI 2.0 - Distributor will not wait (i.e. connection broken) SIRI w.0 + Distributor will not wait, i.e., connection is not guaranteed or broken. SIRI 2.0 - Nature of wait that distributer will make. +SIRI v2.0 + Details about how (long) the distributor services may be held in order to guarantee the connection. +SIRI v2.0 @@ -244,7 +244,7 @@ DEPRECATED from SIRI 2.0 - Whether connection monitoring is active or not for this connection +SIRI v2.0 + Whether connection monitoring is active or not for this connection. +SIRI v2.0 @@ -296,7 +296,7 @@ the original journey and the nature of the difference. - Observed call times for that art of teh journey that has already been completed. (+ SIRI 2..0) + Complete sequence of stops already visited along the route path, in calling order. Only used if observed stop data is being recorded. (SIRI 2.0) @@ -306,7 +306,7 @@ the original journey and the nature of the difference. - Estimated call times for journey + Complete sequence of stops along the route path, in calling order. Normally this is only the onwards stops from the vehicle's current position. @@ -325,12 +325,12 @@ the original journey and the nature of the difference. - Ordered sequence of SCHEDULED STOP POINTs called at by the VEHICLE JOURNEY If IsCompleteStopSequence is false, may be just those stops that are altered. + Ordered sequence of SCHEDULED STOP POINTs called at by the VEHICLE JOURNEY. If IsCompleteStopSequence is false, may be just those stops that are altered. - Type for Rea-ltime info about a VEHICLE JOURNEY Stop. + Type for real-time info about a VEHICLE JOURNEY Stop. @@ -374,7 +374,7 @@ the original journey and the nature of the difference. - Ordered sequence of SCHEDULED STOP POINTs called at by the VEHICLE JOURNEY If IsCompleteStopSequence is false, may be just those stops that are altered. + Ordered sequence of SCHEDULED STOP POINTs called at by the VEHICLE JOURNEY. Only used if observed stop data is being recorded. (SIRI 2.0) @@ -405,12 +405,12 @@ the original journey and the nature of the difference. - Type of boarding and alighting at stop, e.g. alighting, noAlighting or passThru. + Type of boarding and alighting at stop, e.g. alighting, noAlighting or passThru. +SIRI v2.1 - Assignment of arrival of Scheduled STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure +SIRI v2.0. + Assignment of arrival of Scheduled STOP POINT to a physical QUAY (platform). If not given, assume same as for departure. +SIRI v2.1 @@ -445,12 +445,12 @@ the original journey and the nature of the difference. - Nature of boarding at stop, e.g. boarding, noBoarding or passThru. + Nature of boarding at stop, e.g. boarding, noBoarding or passThru. +SIRI v2.1 - Assignments of departure platfiorm for Scheduled STOP POINT to a physical QUAY. +SIRI v2.0. + Assignments of departure platform for Scheduled STOP POINT to a physical QUAY. +SIRI v2.1 From c3976459f998afefbb627366f047009dbf47e156 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Sat, 11 Jan 2020 00:57:21 +0100 Subject: [PATCH 050/290] Some typo fixes in comments and text additions --- .../siri_estimatedVehicleJourney-v2.0.xsd | 30 +++++++++---------- 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index 0c13f036..28d4b53f 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -106,7 +106,7 @@ Rail transport, Roads and road transport - Reference to a dated VEHICLE JOURNEY. This will be 'framed' ie be with the data context of the ESTIMATED Timetable. + Reference to a dated VEHICLE JOURNEY. This will be 'framed' i.e. be with the data context of the ESTIMATED Timetable. DEPRECATED from SIRI 2.0 @@ -118,7 +118,7 @@ DEPRECATED from SIRI 2.0 - 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'. + If this is the first message for an unplanned 'extra' VEHICLE JOURNEY, a new and unique code must be given for it. ExtraJourney should be set to 'true'. DEPRECATED from SIRI 2.0 @@ -202,7 +202,7 @@ DEPRECATED from SIRI 2.0 - A VEHICLE JOURNEY taking place on a particular date that will be managed by an AVMs. + A real-time SERVICE JOURNEY INTERCHANGE that may be made between the stops of two monitored journeys. It includes the current real-time predicted transfer and wait times. +SIRI v2.0 @@ -228,12 +228,12 @@ DEPRECATED from SIRI 2.0 - Distributor will not wait (i.e. connection broken) SIRI w.0 + Distributor will not wait, i.e., connection is not guaranteed or broken. SIRI 2.0 - Nature of wait that distributer will make. +SIRI v2.0 + Details about how (long) the distributor services may be held in order to guarantee the connection. +SIRI v2.0 @@ -244,7 +244,7 @@ DEPRECATED from SIRI 2.0 - Whether connection monitoring is active or not for this connection +SIRI v2.0 + Whether connection monitoring is active or not for this connection. +SIRI v2.0 @@ -296,7 +296,7 @@ the original journey and the nature of the difference. - Observed call times for that art of teh journey that has already been completed. (+ SIRI 2..0) + Complete sequence of stops already visited along the route path, in calling order. Only used if observed stop data is being recorded. (SIRI 2.0) @@ -306,7 +306,7 @@ the original journey and the nature of the difference. - Estimated call times for journey + Complete sequence of stops along the route path, in calling order. Normally this is only the onwards stops from the vehicle's current position. @@ -325,12 +325,12 @@ the original journey and the nature of the difference. - Ordered sequence of SCHEDULED STOP POINTs called at by the VEHICLE JOURNEY If IsCompleteStopSequence is false, may be just those stops that are altered. + Ordered sequence of SCHEDULED STOP POINTs called at by the VEHICLE JOURNEY. If IsCompleteStopSequence is false, may be just those stops that are altered. - Type for Rea-ltime info about a VEHICLE JOURNEY Stop. + Type for real-time info about a VEHICLE JOURNEY Stop. @@ -374,7 +374,7 @@ the original journey and the nature of the difference. - Ordered sequence of SCHEDULED STOP POINTs called at by the VEHICLE JOURNEY If IsCompleteStopSequence is false, may be just those stops that are altered. + Ordered sequence of SCHEDULED STOP POINTs called at by the VEHICLE JOURNEY. Only used if observed stop data is being recorded. (SIRI 2.0) @@ -387,7 +387,7 @@ the original journey and the nature of the difference. - Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicel to arrive at.Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is + Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicle to arrive at. Inheritable property. Can be omitted if the same as the DeparturePlatformName. If there is 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. @@ -400,7 +400,7 @@ the original journey and the nature of the difference. - Assignment of arrival of Scheduled STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure +SIRI v2.0. + Assignment of arrival of Scheduled STOP POINT to a physical QUAY (platform). If not given, assume same as for departure. +SIRI v2.1 @@ -415,7 +415,7 @@ the original journey and the nature of the difference. - Departure QUAY ( Bay or platform) name. Defaulted taken from from planned timetable.. + Bay or platform (QUAY) name from which VEHICLE will depart. Inherited property. @@ -430,7 +430,7 @@ the original journey and the nature of the difference. - Assignments of departure platfiorm for Scheduled STOP POINT to a physical QUAY. +SIRI v2.0. + Assignments of departure platform for Scheduled STOP POINT to a physical QUAY. +SIRI v2.1 From 77a5dc7547977d2999c83b5b58fe9c4e2f21e156 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Stephan=20Gro=C3=9Fberndt?= Date: Mon, 13 Jan 2020 09:31:34 +0100 Subject: [PATCH 051/290] Allow specifying multiple languages in requests Set maxOccurs="unbounded" for language in RequestPolicyGroups in order to allow specifying multiple languages in requests --- xsd/siri/siri_common_services-v2.0.xsd | 4 ++-- xsd/siri_connectionMonitoring_service.xsd | 4 ++-- xsd/siri_connectionTimetable_service.xsd | 4 ++-- xsd/siri_discovery.xsd | 24 +++++++++++------------ xsd/siri_estimatedTimetable_service.xsd | 4 ++-- xsd/siri_facilityMonitoring_service.xsd | 4 ++-- xsd/siri_generalMessage_service.xsd | 4 ++-- xsd/siri_productionTimetable_service.xsd | 4 ++-- xsd/siri_situationExchange_service.xsd | 4 ++-- xsd/siri_stopMonitoring_service.xsd | 4 ++-- xsd/siri_stopTimetable_service.xsd | 4 ++-- xsd/siri_vehicleMonitoring_service.xsd | 4 ++-- 12 files changed, 34 insertions(+), 34 deletions(-) diff --git a/xsd/siri/siri_common_services-v2.0.xsd b/xsd/siri/siri_common_services-v2.0.xsd index bf0bd548..167b350f 100644 --- a/xsd/siri/siri_common_services-v2.0.xsd +++ b/xsd/siri/siri_common_services-v2.0.xsd @@ -324,9 +324,9 @@ Rail transport, Roads and road transport Default names pace used to scope data identifiers. - + - Preferred language in which to return text values. + Preferred languages in which to return text values. diff --git a/xsd/siri_connectionMonitoring_service.xsd b/xsd/siri_connectionMonitoring_service.xsd index 572bc51e..3af80faf 100644 --- a/xsd/siri_connectionMonitoring_service.xsd +++ b/xsd/siri_connectionMonitoring_service.xsd @@ -177,9 +177,9 @@ Rail transport, Roads and road transport Parameters that affect the request processing. - + - Preferred language in which to return text values. + Preferred languages in which to return text values. diff --git a/xsd/siri_connectionTimetable_service.xsd b/xsd/siri_connectionTimetable_service.xsd index 4247ea78..c2f247fb 100644 --- a/xsd/siri_connectionTimetable_service.xsd +++ b/xsd/siri_connectionTimetable_service.xsd @@ -163,9 +163,9 @@ Rail transport, Roads and road transport Parameters that affect the request processing. - + - Preferred language in which to return text values. + Preferred languages in which to return text values. diff --git a/xsd/siri_discovery.xsd b/xsd/siri_discovery.xsd index 4e53f271..913823d8 100644 --- a/xsd/siri_discovery.xsd +++ b/xsd/siri_discovery.xsd @@ -229,9 +229,9 @@ Rail transport, Roads and road transport Parameters that affect the request processing. Mostly act to reduce the number of stops returned. +SIRI v2.0 - + - Preferred language in which to return text values. +SIRI v2.0 + Preferred languages in which to return text values. +SIRI v2.0 @@ -356,9 +356,9 @@ Rail transport, Roads and road transport Parameters that affect the request processing. Mostly act to reduce the number of Linesreturned. +SIRI v2.0 - + - Preferred language in which to return text values. +SIRI v2.0 + Preferred languages in which to return text values. +SIRI v2.0 @@ -446,9 +446,9 @@ Rail transport, Roads and road transport Parameters that affect the request processing. Mostly act to reduce the number of Facilities returned. +SIRI v2.0 - + - Preferred language in which to return text values. +SIRI v2.0 + Preferred languages in which to return text values. +SIRI v2.0 @@ -508,9 +508,9 @@ Rail transport, Roads and road transport Parameters that affect the request processing. Mostly act to reduce the number of Facilities returned. +SIRI v2.0 - + - Preferred language in which to return text values. +SIRI v2.0 + Preferred languages in which to return text values. +SIRI v2.0 @@ -649,9 +649,9 @@ Rail transport, Roads and road transport Parameters that affect the request processing. Mostly act to reduce the number of Facilities returned. +SIRI v2.0 - + - Preferred language in which to return text values. +SIRI v2.0 + Preferred languages in which to return text values. +SIRI v2.0 @@ -832,9 +832,9 @@ Rail transport, Roads and road transport Parameters that affect the request processing. Mostly act to reduce the number of ConnectionLinks returned. +SIRI v2.0 - + - Preferred language in which to return text values. +SIRI v2.0 + Preferred languages in which to return text values. +SIRI v2.0 diff --git a/xsd/siri_estimatedTimetable_service.xsd b/xsd/siri_estimatedTimetable_service.xsd index 22d7ca87..a3420e93 100644 --- a/xsd/siri_estimatedTimetable_service.xsd +++ b/xsd/siri_estimatedTimetable_service.xsd @@ -175,9 +175,9 @@ Rail transport, Roads and road transport Parameters that affect the request processing. Mostly act to reduce the number of messages exchanged. - + - Preferred language in which to return text values. + Preferred languages in which to return text values. diff --git a/xsd/siri_facilityMonitoring_service.xsd b/xsd/siri_facilityMonitoring_service.xsd index 256f1263..8e70d606 100644 --- a/xsd/siri_facilityMonitoring_service.xsd +++ b/xsd/siri_facilityMonitoring_service.xsd @@ -206,9 +206,9 @@ Rail transport, Roads and road transport Parameters that affect the request processing. - + - Preferred language in which to return text values. + Preferred languages in which to return text values. diff --git a/xsd/siri_generalMessage_service.xsd b/xsd/siri_generalMessage_service.xsd index 647befa6..a109673d 100644 --- a/xsd/siri_generalMessage_service.xsd +++ b/xsd/siri_generalMessage_service.xsd @@ -143,9 +143,9 @@ Rail transport, Roads and road transport Parameters that affect the request processing. - + - Preferred language in which to return text values. + Preferred languages in which to return text values. diff --git a/xsd/siri_productionTimetable_service.xsd b/xsd/siri_productionTimetable_service.xsd index e5395994..249a3ea3 100644 --- a/xsd/siri_productionTimetable_service.xsd +++ b/xsd/siri_productionTimetable_service.xsd @@ -179,9 +179,9 @@ Rail transport, Roads and road transport Parameters that affect the request processing. Mostly act to reduce the number of messages exchanged. - + - Preferred language in which to return text values. + Preferred languages in which to return text values. diff --git a/xsd/siri_situationExchange_service.xsd b/xsd/siri_situationExchange_service.xsd index bb398243..d36fd25a 100644 --- a/xsd/siri_situationExchange_service.xsd +++ b/xsd/siri_situationExchange_service.xsd @@ -406,9 +406,9 @@ Rail transport, Roads and road transport Parameters that affect the request processing. - + - Preferred language in which to return text values. + Preferred languages in which to return text values. diff --git a/xsd/siri_stopMonitoring_service.xsd b/xsd/siri_stopMonitoring_service.xsd index 1bdd2709..5225ed65 100644 --- a/xsd/siri_stopMonitoring_service.xsd +++ b/xsd/siri_stopMonitoring_service.xsd @@ -195,9 +195,9 @@ Rail transport, Roads and road transport Parameters that affect the request processing. Mostly act to reduce the number of stops returned. - + - Preferred language in which to return text values. + Preferred languages in which to return text values. diff --git a/xsd/siri_stopTimetable_service.xsd b/xsd/siri_stopTimetable_service.xsd index b362c860..677297c7 100644 --- a/xsd/siri_stopTimetable_service.xsd +++ b/xsd/siri_stopTimetable_service.xsd @@ -163,9 +163,9 @@ Rail transport, Roads and road transport Parameters that affect the request processing. Mostly act to reduce the number of stops returned. - + - Preferred language in which to return text values. + Preferred languages in which to return text values. diff --git a/xsd/siri_vehicleMonitoring_service.xsd b/xsd/siri_vehicleMonitoring_service.xsd index 9e5f48fa..2d0a2c00 100644 --- a/xsd/siri_vehicleMonitoring_service.xsd +++ b/xsd/siri_vehicleMonitoring_service.xsd @@ -200,9 +200,9 @@ Rail transport, Roads and road transport Parameters that affect the request processing. - + - Preferred language in which to return text values. + Preferred languages in which to return text values. From 14123d033274e722b87eff5e0266331a3680ce7d Mon Sep 17 00:00:00 2001 From: Adrian A Date: Mon, 13 Jan 2020 15:39:27 +0100 Subject: [PATCH 052/290] CR013: simplify TypeOfValue / remove abstract true --- xsd/siri_utility/siri_utility-v1.1.xsd | 33 ++------------------------ 1 file changed, 2 insertions(+), 31 deletions(-) diff --git a/xsd/siri_utility/siri_utility-v1.1.xsd b/xsd/siri_utility/siri_utility-v1.1.xsd index 5ea49501..4029f65f 100644 --- a/xsd/siri_utility/siri_utility-v1.1.xsd +++ b/xsd/siri_utility/siri_utility-v1.1.xsd @@ -152,7 +152,7 @@ such as the description and allowed values for codes. +SIRI v2.1 - + A code value from an extensible set which may be added to by user applications, and is used to classify other SIRI entities. +SIRI v2.1 @@ -212,30 +212,11 @@ such as the description and allowed values for codes. +SIRI v2.1 - + An extensible set of code values which may be added to by user applications and is used to validate the properties of entities. Contains TYPE OF VALUEs that are an instance of the same class. +SIRI v2.1 - - - - - - - Identifier of VALUE SET. - - - - - Name of Class of values in set. - - - - - - - TYPE OF VALUEs of the set must be unique. @@ -315,14 +296,4 @@ Contains TYPE OF VALUEs that are an instance of the same class. +SIRI v2.1 - - - A Classification of reasons for non-availability of real-time data. Serves as an example for the usefulness of the TYPE OF VALUEs extension. Possible TypeOfMonitoringError codes could include 'NoError', 'GpsLocalisation' or 'RadioConnection'. - - - - - - - From 7c5338543ad40b833ae682b9c7096362271e219d Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 14 Jan 2020 19:38:20 +0100 Subject: [PATCH 053/290] CR001: add Inaccu.Reason to Progr.DataQualityGroup --- xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd index 69804342..cf14dead 100644 --- a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd @@ -158,6 +158,11 @@ Rail transport, Roads and road transport Whether the prediction should be judged as inaccurate. + + + Can be used to inform the passenger about the reason for a change of the prediction (in)accuracy in case PredictionInaccurate is set to 'true'. +SIRI v2.1 + + System originating real-time data. Can be used to make judgements of relative quality and accuracy compared to other feeds. From fba112222f84254b740df8a13f26822de32afec7 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 14 Jan 2020 19:38:45 +0100 Subject: [PATCH 054/290] CR001: add InaccurateReason to xxRealtimeInfoGroup --- xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index ce2d84ee..2f80956c 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -165,6 +165,11 @@ DEPRECATED from SRI 2.0 Whether the prediction for the journey is considered to be of a useful accuracy or not. Default is 'false'. + + + Can be used to inform the passenger about the reason for a change of the prediction (in)accuracy in case PredictionInaccurate is set to 'true'. +SIRI v2.1 + + How full the bus is. If omitted: Passenger load is unknown. @@ -364,6 +369,11 @@ the original journey and the nature of the difference. 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] + + + Can be used to inform the passenger about the reason for a change of the prediction (in)accuracy in case PredictionInaccurate is set to 'true'. +SIRI v2.1 + + How full the bus is at the stop. If omitted: Passenger load is unknown. From e27c828cb8db8676ac7f4240c85decd867842149 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 14 Jan 2020 19:43:58 +0100 Subject: [PATCH 055/290] CR001: add new Enum for PredictionInaccurateReason --- xsd/siri_model/siri_journey_support-v2.0.xsd | 33 ++++++++++++++++++++ 1 file changed, 33 insertions(+) diff --git a/xsd/siri_model/siri_journey_support-v2.0.xsd b/xsd/siri_model/siri_journey_support-v2.0.xsd index 82a01de7..41d7c172 100644 --- a/xsd/siri_model/siri_journey_support-v2.0.xsd +++ b/xsd/siri_model/siri_journey_support-v2.0.xsd @@ -573,4 +573,37 @@ Corresponds to NeTEX TYPE OF SERVICe. + + + + Allowed values for PredictionInaccurateReason, i.e., possible reasons for a change in prediction (in)accuracy. + + + + + Prediction is inaccurate because of a traffic jam. + + + + + Prediction is inaccurate because of technical problems. + + + + + Prediction is inaccurate because of a despatching alteration. + + + + + Prediction is inaccurate because communication errors have prevented any updates. + + + + + Prediction is inaccurate but the reason for an inaccurate prediction is unknown. + + + + From 664f189b212087d09c02f83c7621c2e14d979f7e Mon Sep 17 00:00:00 2001 From: Adrian A Date: Thu, 16 Jan 2020 00:44:44 +0100 Subject: [PATCH 056/290] CR007: add new FilterByXX elements to capabilities --- xsd/siri_model/siri_modelPermissions-v2.0.xsd | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/xsd/siri_model/siri_modelPermissions-v2.0.xsd b/xsd/siri_model/siri_modelPermissions-v2.0.xsd index 4aafa6d5..7162963d 100644 --- a/xsd/siri_model/siri_modelPermissions-v2.0.xsd +++ b/xsd/siri_model/siri_modelPermissions-v2.0.xsd @@ -251,6 +251,16 @@ Rail transport, Roads and road transport Whether results can be filtered by Facility (EQUIPMENT). Default is 'true'. + + + Whether results can be filtered by VEHICLE MODE. Default is 'true'. +SIRI v2.1 + + + + + Whether results can be filtered by PRODUCT CATEGORY. Default is 'true'. +SIRI v2.1 + + From faaa72e876486ce2768a607f50ac29606ea072a2 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Thu, 16 Jan 2020 00:45:10 +0100 Subject: [PATCH 057/290] CR007: add new FilterByXX to PT capabilities --- xsd/siri_productionTimetable_service.xsd | 3 +++ 1 file changed, 3 insertions(+) diff --git a/xsd/siri_productionTimetable_service.xsd b/xsd/siri_productionTimetable_service.xsd index e5395994..836346ed 100644 --- a/xsd/siri_productionTimetable_service.xsd +++ b/xsd/siri_productionTimetable_service.xsd @@ -389,6 +389,9 @@ If false each subscription response will contain the full information as specifi + + + Whether results can be filtered by TIMETABLE VERSION Default is 'true'. From 94d4759627d053ee42636663609ef87fbf4e7824 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Thu, 16 Jan 2020 00:45:42 +0100 Subject: [PATCH 058/290] CR007: add new FilterByXX to ET capabilities --- xsd/siri_estimatedTimetable_service.xsd | 3 +++ 1 file changed, 3 insertions(+) diff --git a/xsd/siri_estimatedTimetable_service.xsd b/xsd/siri_estimatedTimetable_service.xsd index 22d7ca87..e1ad3a94 100644 --- a/xsd/siri_estimatedTimetable_service.xsd +++ b/xsd/siri_estimatedTimetable_service.xsd @@ -395,6 +395,9 @@ If false each subscription response will contain the full information as specifi + + + Whether results can be filtered by TIMETABLE VERSION Default is 'true'. From f481e6dea59b92b001b5581aa762e09060d8d368 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Thu, 16 Jan 2020 00:46:19 +0100 Subject: [PATCH 059/290] CR007: add new policy parameters to request struc. --- xsd/siri/siri_request_support-v2.0.xsd | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/xsd/siri/siri_request_support-v2.0.xsd b/xsd/siri/siri_request_support-v2.0.xsd index 1c33edf3..61632df1 100644 --- a/xsd/siri/siri_request_support-v2.0.xsd +++ b/xsd/siri/siri_request_support-v2.0.xsd @@ -143,10 +143,19 @@ Rail transport, Roads and road transport Whether additional translations of text names are to be included in elements. If false, then only one element should be returned. Default is false. - Where multiple values are returned The first element returned ill be used as the default value. + + + Whether SERVICE JOURNEY INTERCHANGE data is to be transmitted or not. Default is true. +SIRI v2.1 + + + + + Whether JOURNEY RELATION data is to be transmitted or not. Default is true. +SIRI v2.1 + + From eaa6c73c943cea100f2ee8dbf6e4725b18ef7921 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Thu, 16 Jan 2020 00:46:44 +0100 Subject: [PATCH 060/290] CR007: add new topic parameters to ET request --- xsd/siri_estimatedTimetable_service.xsd | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/xsd/siri_estimatedTimetable_service.xsd b/xsd/siri_estimatedTimetable_service.xsd index e1ad3a94..b1e01113 100644 --- a/xsd/siri_estimatedTimetable_service.xsd +++ b/xsd/siri_estimatedTimetable_service.xsd @@ -168,6 +168,21 @@ Rail transport, Roads and road transport + + + Filter the results to include only journeys of the specified VEHICLE MODE. +SIRI v2.1 + + + + + Filter the results to include only journeys of the specified TYPE OF PRODUCT CATEGORY. +SIRI v2.1 + + + + + Filter the results to include only journeys with a CALL at the specified STOP POINT. +SIRI v2.1 + + From f50f89cf1960dab29af3759fc92ddbe8e5993748 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Thu, 16 Jan 2020 00:47:21 +0100 Subject: [PATCH 061/290] CR007: add new topic parameters to PT request --- xsd/siri_productionTimetable_service.xsd | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/xsd/siri_productionTimetable_service.xsd b/xsd/siri_productionTimetable_service.xsd index 836346ed..9a4776d9 100644 --- a/xsd/siri_productionTimetable_service.xsd +++ b/xsd/siri_productionTimetable_service.xsd @@ -172,6 +172,21 @@ Rail transport, Roads and road transport + + + Filter the results to include only journeys of the specified VEHICLE MODE. +SIRI v2.1 + + + + + Filter the results to include only journeys of the specified TYPE OF PRODUCT CATEGORY. +SIRI v2.1 + + + + + Filter the results to include only journeys with a CALL at the specified STOP POINT. +SIRI v2.1 + + From 42f4be8974540168579267987425a42e5f0623e7 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Thu, 16 Jan 2020 00:47:44 +0100 Subject: [PATCH 062/290] CR007: add new policy parameters to ET request --- xsd/siri_estimatedTimetable_service.xsd | 2 ++ 1 file changed, 2 insertions(+) diff --git a/xsd/siri_estimatedTimetable_service.xsd b/xsd/siri_estimatedTimetable_service.xsd index b1e01113..a0121093 100644 --- a/xsd/siri_estimatedTimetable_service.xsd +++ b/xsd/siri_estimatedTimetable_service.xsd @@ -196,6 +196,8 @@ Rail transport, Roads and road transport + + Level of detail to include in response. Default is 'normal'. (SIRI 2.0) From 06d7e89e8580b6f5e0c8d8c52d005b21e6b7ae73 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Thu, 16 Jan 2020 00:48:15 +0100 Subject: [PATCH 063/290] CR007: add new policy parameters to PT request --- xsd/siri_productionTimetable_service.xsd | 2 ++ 1 file changed, 2 insertions(+) diff --git a/xsd/siri_productionTimetable_service.xsd b/xsd/siri_productionTimetable_service.xsd index 9a4776d9..04f88b21 100644 --- a/xsd/siri_productionTimetable_service.xsd +++ b/xsd/siri_productionTimetable_service.xsd @@ -200,6 +200,8 @@ Rail transport, Roads and road transport + + Whether to return the whole timetable, or just differences from the inidicated version. Default is 'false'. From a2a0b43c6e02de923fb936d5845ea597f194fa0f Mon Sep 17 00:00:00 2001 From: Adrian A Date: Thu, 16 Jan 2020 11:22:35 +0100 Subject: [PATCH 064/290] CR007: make new ET filters optional --- xsd/siri_estimatedTimetable_service.xsd | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/xsd/siri_estimatedTimetable_service.xsd b/xsd/siri_estimatedTimetable_service.xsd index a0121093..9fecd4ad 100644 --- a/xsd/siri_estimatedTimetable_service.xsd +++ b/xsd/siri_estimatedTimetable_service.xsd @@ -412,9 +412,9 @@ If false each subscription response will contain the full information as specifi - - - + + + Whether results can be filtered by TIMETABLE VERSION Default is 'true'. From c3434f2b0783ad71ecdd6e700fad06566e7af763 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Thu, 16 Jan 2020 11:23:37 +0100 Subject: [PATCH 065/290] CR007: make new PT filters optional --- xsd/siri_productionTimetable_service.xsd | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/xsd/siri_productionTimetable_service.xsd b/xsd/siri_productionTimetable_service.xsd index 04f88b21..22c0650f 100644 --- a/xsd/siri_productionTimetable_service.xsd +++ b/xsd/siri_productionTimetable_service.xsd @@ -406,9 +406,9 @@ If false each subscription response will contain the full information as specifi - - - + + + Whether results can be filtered by TIMETABLE VERSION Default is 'true'. From f9ae8694e6479e16be5ed9ee3d53f5dbe860b9de Mon Sep 17 00:00:00 2001 From: Adrian A Date: Thu, 16 Jan 2020 12:52:46 +0100 Subject: [PATCH 066/290] add TravisCI scripts and clean-up --- .travis.yml | 7 +- .travis/travis-ci_git-commit.sh | 64 ++ .travis/xmllint-check.sh | 4 + LICENSE | 675 ------------------ .../SIRI_XML-2.0q_changes.txt | 0 5 files changed, 73 insertions(+), 677 deletions(-) create mode 100644 .travis/travis-ci_git-commit.sh create mode 100644 .travis/xmllint-check.sh delete mode 100644 LICENSE rename SIRI_XML-2.0q_changes.txt => release-notes/SIRI_XML-2.0q_changes.txt (100%) diff --git a/.travis.yml b/.travis.yml index 6d20b16d..7db6ea77 100644 --- a/.travis.yml +++ b/.travis.yml @@ -1,7 +1,10 @@ -language: c +language: minimal before_script: - sudo apt-get install -qq libxml2-utils script: - - "xmllint --noout --schema xsd/siri.xsd examples/siri_exa_framework/*xml examples/siri_exm_CM/*xml examples/siri_exm_CT/*xml examples/siri_exm_ET/*xml examples/siri_exm_FM/*xml examples/siri_exm_GM/*xml examples/siri_exm_PT/*xml examples/siri_exm_SM/*xml examples/siri_exm_ST/*xml examples/siri_exm_SX/*xml examples/siri_exm_VM/*xml examples/siri_exu_capability/*xml examples/siri_exu_discovery/*xml" + - bash .travis/xmllint-check.sh + +after_script: + - bash .travis/travis-ci_git-commit.sh diff --git a/.travis/travis-ci_git-commit.sh b/.travis/travis-ci_git-commit.sh new file mode 100644 index 00000000..a68b02f7 --- /dev/null +++ b/.travis/travis-ci_git-commit.sh @@ -0,0 +1,64 @@ +#!/bin/bash +# function to make a commit on a branch in a Travis CI build +# be sure to avoid creating a Travis CI fork bomb +# see https://gist.github.com/mitchellkrogza/a296ab5102d7e7142cc3599fca634203 and https://github.com/travis-ci/travis-ci/issues/1701 +function travis-branch-commit() { + local head_ref branch_ref + head_ref=$(git rev-parse HEAD) + if [[ $? -ne 0 || ! $head_ref ]]; then + err "failed to get HEAD reference" + return 1 + fi + branch_ref=$(git rev-parse "$TRAVIS_BRANCH") + if [[ $? -ne 0 || ! $branch_ref ]]; then + err "failed to get $TRAVIS_BRANCH reference" + return 1 + fi + if [[ $head_ref != $branch_ref ]]; then + msg "HEAD ref ($head_ref) does not match $TRAVIS_BRANCH ref ($branch_ref)" + msg "Someone may have pushed new commits before this build cloned the repo" + return 0 + fi + if ! git checkout "$TRAVIS_BRANCH"; then + err "failed to checkout $TRAVIS_BRANCH" + return 1 + fi + + if ! git add --all .; then + err "failed to add modified files to git index" + return 1 + fi + # make Travis CI skip this build + if ! git commit -m "Travis CI update [skip ci]"; then + err "failed to commit updates" + return 1 + fi + # add to your .travis.yml: `branches\n except:\n - "/\\+travis\\d+$/"\n` + local git_tag=SOME_TAG_TRAVIS_WILL_NOT_BUILD+travis$TRAVIS_BUILD_NUMBER + if ! git tag "$git_tag" -m "Generated tag from Travis CI build $TRAVIS_BUILD_NUMBER"; then + err "failed to create git tag: $git_tag" + return 1 + fi + local remote=origin + if [[ $GH_TOKEN ]]; then + remote=https://$GH_TOKEN@github.com/$GH_REPO + fi + if [[ $TRAVIS_BRANCH != development ]] && [[ $TRAVIS_BRANCH != integration ]]; then + msg "not pushing updates to branch $TRAVIS_BRANCH" + return 0 + fi + if ! git push --quiet --follow-tags "$remote" "$TRAVIS_BRANCH" > /dev/null 2>&1; then + err "failed to push git changes" + return 1 + fi +} + +function msg() { + echo "travis-commit: $*" +} + +function err() { + msg "$*" 1>&2 +} + +travis-branch-commit \ No newline at end of file diff --git a/.travis/xmllint-check.sh b/.travis/xmllint-check.sh new file mode 100644 index 00000000..c87b7cd8 --- /dev/null +++ b/.travis/xmllint-check.sh @@ -0,0 +1,4 @@ +#!/bin/bash +/usr/bin/find . -name "*.xsd" -type f | while read i; do XMLLINT_INDENT=" " xmllint --pretty 1 "$i" > "$i.pretty"; mv "$i.pretty" "$i"; done; /usr/bin/find . -name "*.xml" -type f | while read i; do XMLLINT_INDENT=" " xmllint --pretty 1 "$i" > "$i.pretty"; mv "$i.pretty" "$i"; done; /usr/bin/find . -name "*.wsdl" -type f | while read i; do XMLLINT_INDENT=" " xmllint --pretty 1 "$i" > "$i.pretty"; mv "$i.pretty" "$i"; done; +echo "finished formatting" +xmllint --noout --schema xsd/siri.xsd examples/siri_exa_framework/*xml examples/siri_exm_CM/*xml examples/siri_exm_CT/*xml examples/siri_exm_ET/*xml examples/siri_exm_FM/*xml examples/siri_exm_GM/*xml examples/siri_exm_PT/*xml examples/siri_exm_SM/*xml examples/siri_exm_ST/*xml examples/siri_exm_SX/*xml examples/siri_exm_VM/*xml examples/siri_exu_capability/*xml examples/siri_exu_discovery/*xml diff --git a/LICENSE b/LICENSE deleted file mode 100644 index 10926e87..00000000 --- a/LICENSE +++ /dev/null @@ -1,675 +0,0 @@ - GNU GENERAL PUBLIC LICENSE - Version 3, 29 June 2007 - - Copyright (C) 2007 Free Software Foundation, Inc. - Everyone is permitted to copy and distribute verbatim copies - of this license document, but changing it is not allowed. - - Preamble - - The GNU General Public License is a free, copyleft license for -software and other kinds of works. - - The licenses for most software and other practical works are designed -to take away your freedom to share and change the works. By contrast, -the GNU General Public License is intended to guarantee your freedom to -share and change all versions of a program--to make sure it remains free -software for all its users. We, the Free Software Foundation, use the -GNU General Public License for most of our software; it applies also to -any other work released this way by its authors. You can apply it to -your programs, too. - - When we speak of free software, we are referring to freedom, not -price. Our General Public Licenses are designed to make sure that you -have the freedom to distribute copies of free software (and charge for -them if you wish), that you receive source code or can get it if you -want it, that you can change the software or use pieces of it in new -free programs, and that you know you can do these things. - - To protect your rights, we need to prevent others from denying you -these rights or asking you to surrender the rights. Therefore, you have -certain responsibilities if you distribute copies of the software, or if -you modify it: responsibilities to respect the freedom of others. - - For example, if you distribute copies of such a program, whether -gratis or for a fee, you must pass on to the recipients the same -freedoms that you received. You must make sure that they, too, receive -or can get the source code. And you must show them these terms so they -know their rights. - - Developers that use the GNU GPL protect your rights with two steps: -(1) assert copyright on the software, and (2) offer you this License -giving you legal permission to copy, distribute and/or modify it. - - For the developers' and authors' protection, the GPL clearly explains -that there is no warranty for this free software. For both users' and -authors' sake, the GPL requires that modified versions be marked as -changed, so that their problems will not be attributed erroneously to -authors of previous versions. - - Some devices are designed to deny users access to install or run -modified versions of the software inside them, although the manufacturer -can do so. This is fundamentally incompatible with the aim of -protecting users' freedom to change the software. The systematic -pattern of such abuse occurs in the area of products for individuals to -use, which is precisely where it is most unacceptable. Therefore, we -have designed this version of the GPL to prohibit the practice for those -products. If such problems arise substantially in other domains, we -stand ready to extend this provision to those domains in future versions -of the GPL, as needed to protect the freedom of users. - - Finally, every program is threatened constantly by software patents. -States should not allow patents to restrict development and use of -software on general-purpose computers, but in those that do, we wish to -avoid the special danger that patents applied to a free program could -make it effectively proprietary. To prevent this, the GPL assures that -patents cannot be used to render the program non-free. - - The precise terms and conditions for copying, distribution and -modification follow. - - TERMS AND CONDITIONS - - 0. Definitions. - - "This License" refers to version 3 of the GNU General Public License. - - "Copyright" also means copyright-like laws that apply to other kinds of -works, such as semiconductor masks. - - "The Program" refers to any copyrightable work licensed under this -License. Each licensee is addressed as "you". "Licensees" and -"recipients" may be individuals or organizations. - - To "modify" a work means to copy from or adapt all or part of the work -in a fashion requiring copyright permission, other than the making of an -exact copy. The resulting work is called a "modified version" of the -earlier work or a work "based on" the earlier work. - - A "covered work" means either the unmodified Program or a work based -on the Program. - - To "propagate" a work means to do anything with it that, without -permission, would make you directly or secondarily liable for -infringement under applicable copyright law, except executing it on a -computer or modifying a private copy. Propagation includes copying, -distribution (with or without modification), making available to the -public, and in some countries other activities as well. - - To "convey" a work means any kind of propagation that enables other -parties to make or receive copies. Mere interaction with a user through -a computer network, with no transfer of a copy, is not conveying. - - An interactive user interface displays "Appropriate Legal Notices" -to the extent that it includes a convenient and prominently visible -feature that (1) displays an appropriate copyright notice, and (2) -tells the user that there is no warranty for the work (except to the -extent that warranties are provided), that licensees may convey the -work under this License, and how to view a copy of this License. If -the interface presents a list of user commands or options, such as a -menu, a prominent item in the list meets this criterion. - - 1. Source Code. - - The "source code" for a work means the preferred form of the work -for making modifications to it. "Object code" means any non-source -form of a work. - - A "Standard Interface" means an interface that either is an official -standard defined by a recognized standards body, or, in the case of -interfaces specified for a particular programming language, one that -is widely used among developers working in that language. - - The "System Libraries" of an executable work include anything, other -than the work as a whole, that (a) is included in the normal form of -packaging a Major Component, but which is not part of that Major -Component, and (b) serves only to enable use of the work with that -Major Component, or to implement a Standard Interface for which an -implementation is available to the public in source code form. A -"Major Component", in this context, means a major essential component -(kernel, window system, and so on) of the specific operating system -(if any) on which the executable work runs, or a compiler used to -produce the work, or an object code interpreter used to run it. - - The "Corresponding Source" for a work in object code form means all -the source code needed to generate, install, and (for an executable -work) run the object code and to modify the work, including scripts to -control those activities. However, it does not include the work's -System Libraries, or general-purpose tools or generally available free -programs which are used unmodified in performing those activities but -which are not part of the work. For example, Corresponding Source -includes interface definition files associated with source files for -the work, and the source code for shared libraries and dynamically -linked subprograms that the work is specifically designed to require, -such as by intimate data communication or control flow between those -subprograms and other parts of the work. - - The Corresponding Source need not include anything that users -can regenerate automatically from other parts of the Corresponding -Source. - - The Corresponding Source for a work in source code form is that -same work. - - 2. Basic Permissions. - - All rights granted under this License are granted for the term of -copyright on the Program, and are irrevocable provided the stated -conditions are met. This License explicitly affirms your unlimited -permission to run the unmodified Program. The output from running a -covered work is covered by this License only if the output, given its -content, constitutes a covered work. This License acknowledges your -rights of fair use or other equivalent, as provided by copyright law. - - You may make, run and propagate covered works that you do not -convey, without conditions so long as your license otherwise remains -in force. You may convey covered works to others for the sole purpose -of having them make modifications exclusively for you, or provide you -with facilities for running those works, provided that you comply with -the terms of this License in conveying all material for which you do -not control copyright. Those thus making or running the covered works -for you must do so exclusively on your behalf, under your direction -and control, on terms that prohibit them from making any copies of -your copyrighted material outside their relationship with you. - - Conveying under any other circumstances is permitted solely under -the conditions stated below. Sublicensing is not allowed; section 10 -makes it unnecessary. - - 3. Protecting Users' Legal Rights From Anti-Circumvention Law. - - No covered work shall be deemed part of an effective technological -measure under any applicable law fulfilling obligations under article -11 of the WIPO copyright treaty adopted on 20 December 1996, or -similar laws prohibiting or restricting circumvention of such -measures. - - When you convey a covered work, you waive any legal power to forbid -circumvention of technological measures to the extent such circumvention -is effected by exercising rights under this License with respect to -the covered work, and you disclaim any intention to limit operation or -modification of the work as a means of enforcing, against the work's -users, your or third parties' legal rights to forbid circumvention of -technological measures. - - 4. Conveying Verbatim Copies. - - You may convey verbatim copies of the Program's source code as you -receive it, in any medium, provided that you conspicuously and -appropriately publish on each copy an appropriate copyright notice; -keep intact all notices stating that this License and any -non-permissive terms added in accord with section 7 apply to the code; -keep intact all notices of the absence of any warranty; and give all -recipients a copy of this License along with the Program. - - You may charge any price or no price for each copy that you convey, -and you may offer support or warranty protection for a fee. - - 5. Conveying Modified Source Versions. - - You may convey a work based on the Program, or the modifications to -produce it from the Program, in the form of source code under the -terms of section 4, provided that you also meet all of these conditions: - - a) The work must carry prominent notices stating that you modified - it, and giving a relevant date. - - b) The work must carry prominent notices stating that it is - released under this License and any conditions added under section - 7. This requirement modifies the requirement in section 4 to - "keep intact all notices". - - c) You must license the entire work, as a whole, under this - License to anyone who comes into possession of a copy. This - License will therefore apply, along with any applicable section 7 - additional terms, to the whole of the work, and all its parts, - regardless of how they are packaged. This License gives no - permission to license the work in any other way, but it does not - invalidate such permission if you have separately received it. - - d) If the work has interactive user interfaces, each must display - Appropriate Legal Notices; however, if the Program has interactive - interfaces that do not display Appropriate Legal Notices, your - work need not make them do so. - - A compilation of a covered work with other separate and independent -works, which are not by their nature extensions of the covered work, -and which are not combined with it such as to form a larger program, -in or on a volume of a storage or distribution medium, is called an -"aggregate" if the compilation and its resulting copyright are not -used to limit the access or legal rights of the compilation's users -beyond what the individual works permit. Inclusion of a covered work -in an aggregate does not cause this License to apply to the other -parts of the aggregate. - - 6. Conveying Non-Source Forms. - - You may convey a covered work in object code form under the terms -of sections 4 and 5, provided that you also convey the -machine-readable Corresponding Source under the terms of this License, -in one of these ways: - - a) Convey the object code in, or embodied in, a physical product - (including a physical distribution medium), accompanied by the - Corresponding Source fixed on a durable physical medium - customarily used for software interchange. - - b) Convey the object code in, or embodied in, a physical product - (including a physical distribution medium), accompanied by a - written offer, valid for at least three years and valid for as - long as you offer spare parts or customer support for that product - model, to give anyone who possesses the object code either (1) a - copy of the Corresponding Source for all the software in the - product that is covered by this License, on a durable physical - medium customarily used for software interchange, for a price no - more than your reasonable cost of physically performing this - conveying of source, or (2) access to copy the - Corresponding Source from a network server at no charge. - - c) Convey individual copies of the object code with a copy of the - written offer to provide the Corresponding Source. This - alternative is allowed only occasionally and noncommercially, and - only if you received the object code with such an offer, in accord - with subsection 6b. - - d) Convey the object code by offering access from a designated - place (gratis or for a charge), and offer equivalent access to the - Corresponding Source in the same way through the same place at no - further charge. You need not require recipients to copy the - Corresponding Source along with the object code. If the place to - copy the object code is a network server, the Corresponding Source - may be on a different server (operated by you or a third party) - that supports equivalent copying facilities, provided you maintain - clear directions next to the object code saying where to find the - Corresponding Source. Regardless of what server hosts the - Corresponding Source, you remain obligated to ensure that it is - available for as long as needed to satisfy these requirements. - - e) Convey the object code using peer-to-peer transmission, provided - you inform other peers where the object code and Corresponding - Source of the work are being offered to the general public at no - charge under subsection 6d. - - A separable portion of the object code, whose source code is excluded -from the Corresponding Source as a System Library, need not be -included in conveying the object code work. - - A "User Product" is either (1) a "consumer product", which means any -tangible personal property which is normally used for personal, family, -or household purposes, or (2) anything designed or sold for incorporation -into a dwelling. In determining whether a product is a consumer product, -doubtful cases shall be resolved in favor of coverage. For a particular -product received by a particular user, "normally used" refers to a -typical or common use of that class of product, regardless of the status -of the particular user or of the way in which the particular user -actually uses, or expects or is expected to use, the product. A product -is a consumer product regardless of whether the product has substantial -commercial, industrial or non-consumer uses, unless such uses represent -the only significant mode of use of the product. - - "Installation Information" for a User Product means any methods, -procedures, authorization keys, or other information required to install -and execute modified versions of a covered work in that User Product from -a modified version of its Corresponding Source. The information must -suffice to ensure that the continued functioning of the modified object -code is in no case prevented or interfered with solely because -modification has been made. - - If you convey an object code work under this section in, or with, or -specifically for use in, a User Product, and the conveying occurs as -part of a transaction in which the right of possession and use of the -User Product is transferred to the recipient in perpetuity or for a -fixed term (regardless of how the transaction is characterized), the -Corresponding Source conveyed under this section must be accompanied -by the Installation Information. But this requirement does not apply -if neither you nor any third party retains the ability to install -modified object code on the User Product (for example, the work has -been installed in ROM). - - The requirement to provide Installation Information does not include a -requirement to continue to provide support service, warranty, or updates -for a work that has been modified or installed by the recipient, or for -the User Product in which it has been modified or installed. Access to a -network may be denied when the modification itself materially and -adversely affects the operation of the network or violates the rules and -protocols for communication across the network. - - Corresponding Source conveyed, and Installation Information provided, -in accord with this section must be in a format that is publicly -documented (and with an implementation available to the public in -source code form), and must require no special password or key for -unpacking, reading or copying. - - 7. Additional Terms. - - "Additional permissions" are terms that supplement the terms of this -License by making exceptions from one or more of its conditions. -Additional permissions that are applicable to the entire Program shall -be treated as though they were included in this License, to the extent -that they are valid under applicable law. If additional permissions -apply only to part of the Program, that part may be used separately -under those permissions, but the entire Program remains governed by -this License without regard to the additional permissions. - - When you convey a copy of a covered work, you may at your option -remove any additional permissions from that copy, or from any part of -it. (Additional permissions may be written to require their own -removal in certain cases when you modify the work.) You may place -additional permissions on material, added by you to a covered work, -for which you have or can give appropriate copyright permission. - - Notwithstanding any other provision of this License, for material you -add to a covered work, you may (if authorized by the copyright holders of -that material) supplement the terms of this License with terms: - - a) Disclaiming warranty or limiting liability differently from the - terms of sections 15 and 16 of this License; or - - b) Requiring preservation of specified reasonable legal notices or - author attributions in that material or in the Appropriate Legal - Notices displayed by works containing it; or - - c) Prohibiting misrepresentation of the origin of that material, or - requiring that modified versions of such material be marked in - reasonable ways as different from the original version; or - - d) Limiting the use for publicity purposes of names of licensors or - authors of the material; or - - e) Declining to grant rights under trademark law for use of some - trade names, trademarks, or service marks; or - - f) Requiring indemnification of licensors and authors of that - material by anyone who conveys the material (or modified versions of - it) with contractual assumptions of liability to the recipient, for - any liability that these contractual assumptions directly impose on - those licensors and authors. - - All other non-permissive additional terms are considered "further -restrictions" within the meaning of section 10. If the Program as you -received it, or any part of it, contains a notice stating that it is -governed by this License along with a term that is a further -restriction, you may remove that term. If a license document contains -a further restriction but permits relicensing or conveying under this -License, you may add to a covered work material governed by the terms -of that license document, provided that the further restriction does -not survive such relicensing or conveying. - - If you add terms to a covered work in accord with this section, you -must place, in the relevant source files, a statement of the -additional terms that apply to those files, or a notice indicating -where to find the applicable terms. - - Additional terms, permissive or non-permissive, may be stated in the -form of a separately written license, or stated as exceptions; -the above requirements apply either way. - - 8. Termination. - - You may not propagate or modify a covered work except as expressly -provided under this License. Any attempt otherwise to propagate or -modify it is void, and will automatically terminate your rights under -this License (including any patent licenses granted under the third -paragraph of section 11). - - However, if you cease all violation of this License, then your -license from a particular copyright holder is reinstated (a) -provisionally, unless and until the copyright holder explicitly and -finally terminates your license, and (b) permanently, if the copyright -holder fails to notify you of the violation by some reasonable means -prior to 60 days after the cessation. - - Moreover, your license from a particular copyright holder is -reinstated permanently if the copyright holder notifies you of the -violation by some reasonable means, this is the first time you have -received notice of violation of this License (for any work) from that -copyright holder, and you cure the violation prior to 30 days after -your receipt of the notice. - - Termination of your rights under this section does not terminate the -licenses of parties who have received copies or rights from you under -this License. If your rights have been terminated and not permanently -reinstated, you do not qualify to receive new licenses for the same -material under section 10. - - 9. Acceptance Not Required for Having Copies. - - You are not required to accept this License in order to receive or -run a copy of the Program. Ancillary propagation of a covered work -occurring solely as a consequence of using peer-to-peer transmission -to receive a copy likewise does not require acceptance. However, -nothing other than this License grants you permission to propagate or -modify any covered work. These actions infringe copyright if you do -not accept this License. Therefore, by modifying or propagating a -covered work, you indicate your acceptance of this License to do so. - - 10. Automatic Licensing of Downstream Recipients. - - Each time you convey a covered work, the recipient automatically -receives a license from the original licensors, to run, modify and -propagate that work, subject to this License. You are not responsible -for enforcing compliance by third parties with this License. - - An "entity transaction" is a transaction transferring control of an -organization, or substantially all assets of one, or subdividing an -organization, or merging organizations. If propagation of a covered -work results from an entity transaction, each party to that -transaction who receives a copy of the work also receives whatever -licenses to the work the party's predecessor in interest had or could -give under the previous paragraph, plus a right to possession of the -Corresponding Source of the work from the predecessor in interest, if -the predecessor has it or can get it with reasonable efforts. - - You may not impose any further restrictions on the exercise of the -rights granted or affirmed under this License. For example, you may -not impose a license fee, royalty, or other charge for exercise of -rights granted under this License, and you may not initiate litigation -(including a cross-claim or counterclaim in a lawsuit) alleging that -any patent claim is infringed by making, using, selling, offering for -sale, or importing the Program or any portion of it. - - 11. Patents. - - A "contributor" is a copyright holder who authorizes use under this -License of the Program or a work on which the Program is based. The -work thus licensed is called the contributor's "contributor version". - - A contributor's "essential patent claims" are all patent claims -owned or controlled by the contributor, whether already acquired or -hereafter acquired, that would be infringed by some manner, permitted -by this License, of making, using, or selling its contributor version, -but do not include claims that would be infringed only as a -consequence of further modification of the contributor version. For -purposes of this definition, "control" includes the right to grant -patent sublicenses in a manner consistent with the requirements of -this License. - - Each contributor grants you a non-exclusive, worldwide, royalty-free -patent license under the contributor's essential patent claims, to -make, use, sell, offer for sale, import and otherwise run, modify and -propagate the contents of its contributor version. - - In the following three paragraphs, a "patent license" is any express -agreement or commitment, however denominated, not to enforce a patent -(such as an express permission to practice a patent or covenant not to -sue for patent infringement). To "grant" such a patent license to a -party means to make such an agreement or commitment not to enforce a -patent against the party. - - If you convey a covered work, knowingly relying on a patent license, -and the Corresponding Source of the work is not available for anyone -to copy, free of charge and under the terms of this License, through a -publicly available network server or other readily accessible means, -then you must either (1) cause the Corresponding Source to be so -available, or (2) arrange to deprive yourself of the benefit of the -patent license for this particular work, or (3) arrange, in a manner -consistent with the requirements of this License, to extend the patent -license to downstream recipients. "Knowingly relying" means you have -actual knowledge that, but for the patent license, your conveying the -covered work in a country, or your recipient's use of the covered work -in a country, would infringe one or more identifiable patents in that -country that you have reason to believe are valid. - - If, pursuant to or in connection with a single transaction or -arrangement, you convey, or propagate by procuring conveyance of, a -covered work, and grant a patent license to some of the parties -receiving the covered work authorizing them to use, propagate, modify -or convey a specific copy of the covered work, then the patent license -you grant is automatically extended to all recipients of the covered -work and works based on it. - - A patent license is "discriminatory" if it does not include within -the scope of its coverage, prohibits the exercise of, or is -conditioned on the non-exercise of one or more of the rights that are -specifically granted under this License. You may not convey a covered -work if you are a party to an arrangement with a third party that is -in the business of distributing software, under which you make payment -to the third party based on the extent of your activity of conveying -the work, and under which the third party grants, to any of the -parties who would receive the covered work from you, a discriminatory -patent license (a) in connection with copies of the covered work -conveyed by you (or copies made from those copies), or (b) primarily -for and in connection with specific products or compilations that -contain the covered work, unless you entered into that arrangement, -or that patent license was granted, prior to 28 March 2007. - - Nothing in this License shall be construed as excluding or limiting -any implied license or other defenses to infringement that may -otherwise be available to you under applicable patent law. - - 12. No Surrender of Others' Freedom. - - If conditions are imposed on you (whether by court order, agreement or -otherwise) that contradict the conditions of this License, they do not -excuse you from the conditions of this License. If you cannot convey a -covered work so as to satisfy simultaneously your obligations under this -License and any other pertinent obligations, then as a consequence you may -not convey it at all. For example, if you agree to terms that obligate you -to collect a royalty for further conveying from those to whom you convey -the Program, the only way you could satisfy both those terms and this -License would be to refrain entirely from conveying the Program. - - 13. Use with the GNU Affero General Public License. - - Notwithstanding any other provision of this License, you have -permission to link or combine any covered work with a work licensed -under version 3 of the GNU Affero General Public License into a single -combined work, and to convey the resulting work. The terms of this -License will continue to apply to the part which is the covered work, -but the special requirements of the GNU Affero General Public License, -section 13, concerning interaction through a network will apply to the -combination as such. - - 14. Revised Versions of this License. - - The Free Software Foundation may publish revised and/or new versions of -the GNU General Public License from time to time. Such new versions will -be similar in spirit to the present version, but may differ in detail to -address new problems or concerns. - - Each version is given a distinguishing version number. If the -Program specifies that a certain numbered version of the GNU General -Public License "or any later version" applies to it, you have the -option of following the terms and conditions either of that numbered -version or of any later version published by the Free Software -Foundation. If the Program does not specify a version number of the -GNU General Public License, you may choose any version ever published -by the Free Software Foundation. - - If the Program specifies that a proxy can decide which future -versions of the GNU General Public License can be used, that proxy's -public statement of acceptance of a version permanently authorizes you -to choose that version for the Program. - - Later license versions may give you additional or different -permissions. However, no additional obligations are imposed on any -author or copyright holder as a result of your choosing to follow a -later version. - - 15. Disclaimer of Warranty. - - THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY -APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT -HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY -OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, -THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR -PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM -IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF -ALL NECESSARY SERVICING, REPAIR OR CORRECTION. - - 16. Limitation of Liability. - - IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING -WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS -THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY -GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE -USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF -DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD -PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), -EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF -SUCH DAMAGES. - - 17. Interpretation of Sections 15 and 16. - - If the disclaimer of warranty and limitation of liability provided -above cannot be given local legal effect according to their terms, -reviewing courts shall apply local law that most closely approximates -an absolute waiver of all civil liability in connection with the -Program, unless a warranty or assumption of liability accompanies a -copy of the Program in return for a fee. - - END OF TERMS AND CONDITIONS - - How to Apply These Terms to Your New Programs - - If you develop a new program, and you want it to be of the greatest -possible use to the public, the best way to achieve this is to make it -free software which everyone can redistribute and change under these terms. - - To do so, attach the following notices to the program. It is safest -to attach them to the start of each source file to most effectively -state the exclusion of warranty; and each file should have at least -the "copyright" line and a pointer to where the full notice is found. - - - Copyright (C) - - This program is free software: you can redistribute it and/or modify - it under the terms of the GNU General Public License as published by - the Free Software Foundation, either version 3 of the License, or - (at your option) any later version. - - This program is distributed in the hope that it will be useful, - but WITHOUT ANY WARRANTY; without even the implied warranty of - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the - GNU General Public License for more details. - - You should have received a copy of the GNU General Public License - along with this program. If not, see . - -Also add information on how to contact you by electronic and paper mail. - - If the program does terminal interaction, make it output a short -notice like this when it starts in an interactive mode: - - Copyright (C) - This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. - This is free software, and you are welcome to redistribute it - under certain conditions; type `show c' for details. - -The hypothetical commands `show w' and `show c' should show the appropriate -parts of the General Public License. Of course, your program's commands -might be different; for a GUI interface, you would use an "about box". - - You should also get your employer (if you work as a programmer) or school, -if any, to sign a "copyright disclaimer" for the program, if necessary. -For more information on this, and how to apply and follow the GNU GPL, see -. - - The GNU General Public License does not permit incorporating your program -into proprietary programs. If your program is a subroutine library, you -may consider it more useful to permit linking proprietary applications with -the library. If this is what you want to do, use the GNU Lesser General -Public License instead of this License. But first, please read -. - diff --git a/SIRI_XML-2.0q_changes.txt b/release-notes/SIRI_XML-2.0q_changes.txt similarity index 100% rename from SIRI_XML-2.0q_changes.txt rename to release-notes/SIRI_XML-2.0q_changes.txt From 2e919a714d16e161bf9fcdf05e36522b2be0dcad Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 28 Jan 2020 15:56:48 +0100 Subject: [PATCH 067/290] CR047: add ValidityP. and Short.PCycle to PT Frame --- xsd/siri_productionTimetable_service.xsd | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/xsd/siri_productionTimetable_service.xsd b/xsd/siri_productionTimetable_service.xsd index e5395994..c7bcceb3 100644 --- a/xsd/siri_productionTimetable_service.xsd +++ b/xsd/siri_productionTimetable_service.xsd @@ -285,6 +285,20 @@ If false each subscription response will contain the full information as specifi Timetable Version. + + + Start and end of timetable validity (time window) of journeys for which schedules are returned. +Refers to the departure time at the first stop of each VEHICLE JOURNEY If blank the configured data horizon will be used. +The data producer will cover the VALIDITY PERIOD requested by the subscriber as completely as possible, and is encouraged +to include the actually covered time frame in the delivery message in each of the DATED TIMETABLE VERSION FRAMEs. However, +the VALIDITY PERIOD delivered in the response must not exceed the VALIDITY PERIOD requested by the subscriber. +SIRI v2.1 + + + + + Minimum interval at which updates for this DATED TIMETABLE VERSION FRAME can be sent. +SIRI v2.1 + + From 3a1176a44aaf0f6847a8db76910a973c8bc43f96 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 28 Jan 2020 15:58:08 +0100 Subject: [PATCH 068/290] CR032: add SkipRecCallUpdates to ET SubsriptPolicy --- xsd/siri_estimatedTimetable_service.xsd | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/xsd/siri_estimatedTimetable_service.xsd b/xsd/siri_estimatedTimetable_service.xsd index 22d7ca87..620368b8 100644 --- a/xsd/siri_estimatedTimetable_service.xsd +++ b/xsd/siri_estimatedTimetable_service.xsd @@ -242,6 +242,16 @@ If false each subscription response will contain the full information as specifi The amount of change to the arrival or departure time that can happen before an update is sent (i.e. if ChangeBeforeUpdate is set to 2 minutes, the subscriber will not be told that a timetable is changed by 30 seconds - an update will only be sent when the timetable is changed by at least least 2 minutes. (OPtional from SIRI 2.0) + + + Indicates whether actual arrival-/departure times should be delivered as incremental updates, i.e. whether RECORDED CALL updates are transmitted immediately after an event occurs. +SIRI v2.1 +- 'true': Specifies that the data producer should transmit RECORDED CALL data, in particular actual arrival-/departure information as an incremental update immediately after an event occurs (with hysteresis taken into account). +The server will automatically proceed with 'false' if capability is not supported. +- 'false': Can be requested if the data traffic is to be reduced and an immediate transmissions is not required in any of the consumer systems. +'false' specifies that the data producer should skip RECORDED CALL updates (if capability is supported after all), i.e., deliver them with the next update instead. +No specification: Default value 'false' applies (don't skip updates of recorded data). + + From 0877fc11dc1030a3fbff856c90d44b654c7720c0 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 28 Jan 2020 16:03:33 +0100 Subject: [PATCH 069/290] CR002: include the new JourneyFormationGroup in PT --- xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd | 1 + 1 file changed, 1 insertion(+) diff --git a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd index f0b4f821..12c4d200 100644 --- a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd @@ -119,6 +119,7 @@ Rail transport, Roads and road transport + Complete sequence of stops along the route path, in calling order. From 13c9e39bd6923003663ffe114a8c5dc370f38c24 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 28 Jan 2020 16:04:26 +0100 Subject: [PATCH 070/290] CR002: include new types for train formation data --- xsd/siri_utility/siri_types-v2.0.xsd | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/xsd/siri_utility/siri_types-v2.0.xsd b/xsd/siri_utility/siri_types-v2.0.xsd index 050223dd..14e6968c 100644 --- a/xsd/siri_utility/siri_types-v2.0.xsd +++ b/xsd/siri_utility/siri_types-v2.0.xsd @@ -135,4 +135,22 @@ A string containing a phrase in a natural language name that requires at least o + + + Length type for short distances. System for Units can be specified on frame. Normally (metres) as defined by http://www.ordnancesurvey.co.uk/xml/resource/units.xml#metres. + + + + + + Weight type for mass. System for Units can be specified on Frame. Normal default is (kilos) as defined by http://www.ordnancesurvey.co.uk/xml/resource/units.xml#metres. + + + + + + Number of passengers - capacity. + + + From 2a44c402846433d7060cc849e11bd611ba3da7be Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 28 Jan 2020 16:04:56 +0100 Subject: [PATCH 071/290] CR002: include new types/enums for TRAIN model --- xsd/siri_model/siri_journey_support-v2.0.xsd | 203 +++++++++++++++++++ 1 file changed, 203 insertions(+) diff --git a/xsd/siri_model/siri_journey_support-v2.0.xsd b/xsd/siri_model/siri_journey_support-v2.0.xsd index 82a01de7..99cb6524 100644 --- a/xsd/siri_model/siri_journey_support-v2.0.xsd +++ b/xsd/siri_model/siri_journey_support-v2.0.xsd @@ -320,6 +320,101 @@ Rail transport, Roads and road transport + + + Type for identifier of a TRAIN ELEMENT. An elementary component of a TRAIN (e.g. wagon, locomotive etc.). +SIRI v2.1 + + + + + + Type for reference to a TRAIN ELEMENT. +SIRI v2.1 + + + + + + + + Reference to a TRAIN ELEMENT. +SIRI v2.1 + + + + + Type for identifier of a TRAIN COMPONENT. A TRAIN ELEMENT with a specific order in a TRAIN. +SIRI v2.1 + + + + + + Type for reference to a TRAIN COMPONENT. +SIRI v2.1 + + + + + + + + Reference to a TRAIN COMPONENT. +SIRI v2.1 + + + + + Type for identifier of a TRAIN. An ordered sequence of TRAIN ELEMENTs or TRAIN COMPONENTs respectively. +SIRI v2.1 + + + + + + Type for reference to a TRAIN. +SIRI v2.1 + + + + + + + + Reference to a TRAIN. +SIRI v2.1 + + + + + Type for identifier of a COMPOUND TRAIN. An ordered sequence of TRAINs. A journey does always have one or more JOURNEY PARTs in which the TRAIN composition remains unchanged. +SIRI v2.1 + + + + + + Type for reference to a COMPOUND TRAIN. +SIRI v2.1 + + + + + + + + Reference to a COMPOUND TRAIN. +SIRI v2.1 + + + + + Type for identifier of a TRAIN IN COMPOUND TRAIN. A TRAIN with a specific order in a COMPOUND TRAIN (the train formation as a whole). +SIRI v2.1 + + + + + + Type for reference to a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 + + + + + + + + Reference to a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 + + @@ -573,4 +668,112 @@ Corresponds to NeTEX TYPE OF SERVICe. + + + + Allowed values for TYPE OF TRAIIN ELEMENT. +SIRI v2.1 + + + + + + + + + + + + + + + + Allowed values for TYPE OF TRAIN ELEMENT. +SIRI v2.1 + + + + + + + + + + Allowed values for type of fuel. +SIRI v2.1 + + + + + + + + + + + + + + Classification of FARE CLASSes. +SIRI v2.1 + + + + + List of FARE CLASSes. +SIRI v2.1 + + + + + List of values for FARE CLASSes. +SIRI v2.1 + + + + + + Values for Fare Class Facility. +SIRI v2.1 + + + + + pti23_0 + + + + + pti23_6 + + + + + pti23_7 + + + + + pti23_8 + + + + + + pti23_6_1 + + + + + Busienss Class - pti23_10 + + + + + Standard class Add pti23_7 + + + + + + pti23_9 + + + + + + From cd33212c9c51fbdf5b844ca18b92f0df1b6dceda Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 28 Jan 2020 16:06:57 +0100 Subject: [PATCH 072/290] CR002: add Refs for new train formation model --- xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd index 69804342..1fbbf7af 100644 --- a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd @@ -322,6 +322,13 @@ For SIRI-VM this is the most recent stop visited by the VEHICLE.Operator of JOURNEY PART. +SIRI v2.0 + + + Reference to a COMPOUND TRAIN which represents the train formation/composition as a whole. +A journey (with VEHICLE TYPE 'rail') does always have one or more JOURNEY PARTs in which the train composition remains unchanged. +SIRI v2.1 + + + @@ -386,6 +393,7 @@ For SIRI-VM this is the most recent stop visited by the VEHICLE. + From c03da130b406cfd5c4d43c069ac6671c7a311485 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 28 Jan 2020 16:08:23 +0100 Subject: [PATCH 073/290] CR002: add structure for new train formation model --- xsd/siri_model/siri_journey-v2.0.xsd | 589 ++++++++++++++++++++++++++- 1 file changed, 588 insertions(+), 1 deletion(-) diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index b95675a7..1b3eaff9 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -714,6 +714,7 @@ Rail transport, Roads and road transport Physical QUAY actually used. +SIRI v2.0 + @@ -732,6 +733,7 @@ Rail transport, Roads and road transport Scheduled Platform name. +SIRI v2.0 + @@ -897,5 +899,590 @@ Rail transport, Roads and road transport For frequency based services, observed interval between vehicles at stop. - + + + + + + + + + + + + xxx. +SIRI v2.1 + + + + + xxx. +SIRI v2.1. + + + + + + + + + + + xxx. +SIRI v2.1 + + + + + + + + + + + xxx. +SIRI v2.1 + + + + + + + + + + + + + + + + + xxx. +SIRI v2.1 + + + + + xxx. +SIRI v2.1 + + + + + Orientation of a vehicle or vehicle formation/composition relative to a QUAY. Possible values might include 'towardsStartOfQuay', 'towardsEndOfQuay' or 'towards0'. +The latter example would implicate that the vehicle will depart towards the reference point of the QUAY (reference for measurements such as the VehicleStoppingPosition of SectorPositionAssignments). +SIRI v2.1 + + + + + xxx. +SIRI v2.1 + + + + + + + + + xxx. +SIRI v2.1 + + + + + xxx. +SIRI v2.1 + + + + + xxx. +SIRI v2.1 + + + + + xxx. +SIRI v2.1 + + + + + + + xxx. +SIRI v2.1 + + + + + + xxx. +SIRI v2.1 + + + + + + + + + + + xxx. +SIRI v2.1 + + + + + xxx. +SIRI v2.1 + + + + + + + xxx. +SIRI v2.1 + + + + + + + + Capacity for a VEHICLE TYPE and fare class. +SIRI v2.1 + + + + + Capacity for a VEHICLE TYPE and fare class. +SIRI v2.1 + + + + + Fare class in VEHICLE for which capacity is specified. + + + + + How occupied or full the VEHICLE is. This is an approximate figure. The PassengerCapacityGroup provides more accurate data. + + + + + + + + Elements for a PASSENGER CAPACITY REQUIREMENT. relevant for passenger systems. +SIRI v2.1 + + + + + The total capacity of vehicles of the type. For a requirement this is the minimum needed. + + + + + The seating capacity of vehicles of the type. For a requirement this is the minimum needed. + + + + + The standing capacity of vehicles of the type. For a requirement this is the minimum needed. + + + + + The number of special places on vehicles of the type, e.g. seats for the disabled. For a requirement this is the minimum needed. + + + + + The number of push chair places on vehicles of the type. For a requirement this is the minimum needed. + + + + + The number of wheelchairs places on vehicles of the type. For a requirement this is the minimum needed. + + + + + + + + + A vehicle composed of TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 + + + + + A vehicle composed of TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 + + + + + Identifier for TRAIN ELEMENT. + + + + + + + + + + Elements for a TRAIN ELEMENT. +SIRI v2.1 + + + + + Name of TRAIN ELEMENT. + + + + + Description of TRAIN ELEMENT. + + + + + Type of TRAIN ELEMENT. + + + + + + Break down of Capacities by FARE CLASS (number of passengers that TRAIN ELEMENT can carry). + + + + + + + + + + The length of a TRAIN ELEMENT. + + + + + The width of a TRAIN ELEMENT. + + + + + Facilities of element. + + + + + Actual EQUIPMENT on element. + + + + + + + + A vehicle composed of TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 + + + + + A vehicle composed of TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 + + + + + Identifier for TRAIN COMPONENT. + + + + + Order of TRAIN ELEMENT within TRAIN. + + + + + + + + + Elements for a TRAIN COMPONENT. +SIRI v2.1 + + + + + Label for TRAIN COMPONENT. + + + + + Description of TRAIN COMPONENT. + + + + + + + + + + + + + A vehicle composed of TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 + + + + + A vehicle composed of TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 + + + + + Label for TRAIN COMPONENT. + + + + + + + + + + + Elements for TRAIN. +SIRI v2.1 + + + + + Number of cars needed in TRAIN. + + + + + Nature of Train Size., Short, long, normal. Default is normal. + + + + + Ordered collection of TRAIN COMPONENTs making up TRAIN. + + + + + + + + + + + + + + + + A vehicle composed of COMPOUND TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 + + + + + A vehicle composed of COMPOUND TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 + + + + + Ordered collection of TRAIN in COMPOUND TRAINs making up COMPOUND TRAIN. Each references a TRAIN. + + + + + + Ordered collection of TRAINs making up a COMPOUND TRAIN. Each references a TRAIN. + + + + + + + + + + + + + + A vehicle composed of COMPOUND TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 + + + + + + Type for a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 + + + + + Order of TRAIN IN COMPOUND TRAIN within TRAIN. + + + + + Elements for a TRAIN IN COMPOUND TRAIN. + + + + + + + + Elements for a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 + + + + + Description of TRAIN IN COMPOUND TRAIN. + + + + + + Reference to a TRAIN. +SIRI v2.1 + + + + + + + Whether the component order of the TRAIN IN COMPOUND TRAIN is reversed compared to the order in the TRAIN. + + + + + Label for TRAIN IN COMPOUND TRAIN. + + + + + + + + + + + Elements for a VEHICLE. TYPE. +SIRI v2.1 + + + + + Name of VEHICLE TYPE. + + + + + Short Name of VEHICLE TYPE. + + + + + Description of VEHICLE TYPE. + + + + + + + Facilities of VEHICLE. + + + + + + + Prooprty Elements for a VEHICLE. TYPE. +SIRI v2.1 + + + + + Whether vehicles of the type have a reversing direction. + + + + + Whether vehicles of the type are self-propelled. + + + + + The type of fuel used by a vehicle of the type. + + + + + Euroclass of the vehicle type. + + + + + Total Number of passengers that VEHICLE TYPE. can carry. + + + + + Break down of Capacities by FARE CLASS. + + + + + + + + + + + + + + Dimension elements for a VEHICLE TYPE. +SIRI v2.1 + + + + + The length of a VEHICLE of the type. + + + + + The width of a VEHICLE of the type. + + + + + The length of a VEHICLE of the type. + + + + + The weight of a VEHICLE of the type. + + + + + + + Elements specifying Requirement properties of VEHICLE TYPE. Vehicle should satisfy these requirements. +SIRI v2.1 + + + + + Whether Vehicle is low floor to facilitate access by the mobility impaired. + + + + + Whether vehicle has lift or ramp to facilitate wheelchair access. + + + + + Whether vehicle has hoist for wheelchair access. + + + + + + + + From fcfa88c7c45cb031f0b4e19502f25f85051c63fd Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 28 Jan 2020 16:12:35 +0100 Subject: [PATCH 074/290] CR002: add formation filter to PT and ET requests --- xsd/siri/siri_request_support-v2.0.xsd | 15 +++++++++++++++ xsd/siri_estimatedTimetable_service.xsd | 3 +++ xsd/siri_productionTimetable_service.xsd | 3 +++ 3 files changed, 21 insertions(+) diff --git a/xsd/siri/siri_request_support-v2.0.xsd b/xsd/siri/siri_request_support-v2.0.xsd index 1c33edf3..623beb8d 100644 --- a/xsd/siri/siri_request_support-v2.0.xsd +++ b/xsd/siri/siri_request_support-v2.0.xsd @@ -147,6 +147,21 @@ Rail transport, Roads and road transport Where multiple values are returned The first element returned ill be used as the default value. + + + Whether SERVICE JOURNEY INTERCHANGE data is to be transmitted or not. Default is true. +SIRI v2.1 + + + + + Whether JOURNEY RELATION data is to be transmitted or not. Default is true. +SIRI v2.1 + + + + + Whether TRAIN, SECTOR POSITION ASSIGNMENT and TRAIN STOP ASSIGNMENT data is to be transmitted or not. Default is false. +SIRI v2.1 + + diff --git a/xsd/siri_estimatedTimetable_service.xsd b/xsd/siri_estimatedTimetable_service.xsd index 22d7ca87..3d081c8f 100644 --- a/xsd/siri_estimatedTimetable_service.xsd +++ b/xsd/siri_estimatedTimetable_service.xsd @@ -181,6 +181,9 @@ Rail transport, Roads and road transport + + + Level of detail to include in response. Default is 'normal'. (SIRI 2.0) diff --git a/xsd/siri_productionTimetable_service.xsd b/xsd/siri_productionTimetable_service.xsd index e5395994..b0ff985f 100644 --- a/xsd/siri_productionTimetable_service.xsd +++ b/xsd/siri_productionTimetable_service.xsd @@ -185,6 +185,9 @@ Rail transport, Roads and road transport + + + Whether to return the whole timetable, or just differences from the inidicated version. Default is 'false'. From d58a514f3385b842575c2005b9219ed2e4df6eca Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 28 Jan 2020 16:18:48 +0100 Subject: [PATCH 075/290] CR002: annot. updates and fix Capacity occurance --- xsd/siri_model/siri_journey-v2.0.xsd | 1146 +++++++++++++------------- 1 file changed, 564 insertions(+), 582 deletions(-) diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index 1b3eaff9..51b82e00 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -900,589 +900,571 @@ Rail transport, Roads and road transport - - - - - - - - + - - xxx. +SIRI v2.1 - - - - - xxx. +SIRI v2.1. - - - - - - - - - - - xxx. +SIRI v2.1 - - - - - - - - - - - xxx. +SIRI v2.1 - - - - - - - - - - - - - - + + xxx. +SIRI v2.1 + + + + + xxx. +SIRI v2.1. + + + + + + + + + + + xxx. +SIRI v2.1 + + + + + + + + + + + xxx. +SIRI v2.1 + + + + + + + + + + + - - xxx. +SIRI v2.1 - - - - - xxx. +SIRI v2.1 - - - - - Orientation of a vehicle or vehicle formation/composition relative to a QUAY. Possible values might include 'towardsStartOfQuay', 'towardsEndOfQuay' or 'towards0'. -The latter example would implicate that the vehicle will depart towards the reference point of the QUAY (reference for measurements such as the VehicleStoppingPosition of SectorPositionAssignments). +SIRI v2.1 - - - - - xxx. +SIRI v2.1 - - - - - - - - - xxx. +SIRI v2.1 - - - - - xxx. +SIRI v2.1 - - - - - xxx. +SIRI v2.1 - - - - - xxx. +SIRI v2.1 - - - - - - - xxx. +SIRI v2.1 - - - - - - xxx. +SIRI v2.1 - - - - - - - - - - - xxx. +SIRI v2.1 - - - - - xxx. +SIRI v2.1 - - - - - - - xxx. +SIRI v2.1 - - - - - - - - Capacity for a VEHICLE TYPE and fare class. +SIRI v2.1 - - - - - Capacity for a VEHICLE TYPE and fare class. +SIRI v2.1 - - - - - Fare class in VEHICLE for which capacity is specified. - - - - - How occupied or full the VEHICLE is. This is an approximate figure. The PassengerCapacityGroup provides more accurate data. - - - - - - - - Elements for a PASSENGER CAPACITY REQUIREMENT. relevant for passenger systems. +SIRI v2.1 - - - - - The total capacity of vehicles of the type. For a requirement this is the minimum needed. - - - - - The seating capacity of vehicles of the type. For a requirement this is the minimum needed. - - - - - The standing capacity of vehicles of the type. For a requirement this is the minimum needed. - - - - - The number of special places on vehicles of the type, e.g. seats for the disabled. For a requirement this is the minimum needed. - - - - - The number of push chair places on vehicles of the type. For a requirement this is the minimum needed. - - - - - The number of wheelchairs places on vehicles of the type. For a requirement this is the minimum needed. - - - - - - - - - A vehicle composed of TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 - - - - - A vehicle composed of TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 - - - - - Identifier for TRAIN ELEMENT. - - - - - - - - - - Elements for a TRAIN ELEMENT. +SIRI v2.1 - - - - - Name of TRAIN ELEMENT. - - - - - Description of TRAIN ELEMENT. - - - - - Type of TRAIN ELEMENT. - - - - - - Break down of Capacities by FARE CLASS (number of passengers that TRAIN ELEMENT can carry). - - - - - - - - - - The length of a TRAIN ELEMENT. - - - - - The width of a TRAIN ELEMENT. - - - - - Facilities of element. - - - - - Actual EQUIPMENT on element. - - - - - - - - A vehicle composed of TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 - - - - - A vehicle composed of TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 - - - - - Identifier for TRAIN COMPONENT. - - - - - Order of TRAIN ELEMENT within TRAIN. - - - - - - - - - Elements for a TRAIN COMPONENT. +SIRI v2.1 - - - - - Label for TRAIN COMPONENT. - - - - - Description of TRAIN COMPONENT. - - - - - - - - - - - - - A vehicle composed of TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 - - - - - A vehicle composed of TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 - - - - - Label for TRAIN COMPONENT. - - - - - - - - - - - Elements for TRAIN. +SIRI v2.1 - - - - - Number of cars needed in TRAIN. - - - - - Nature of Train Size., Short, long, normal. Default is normal. - - - - - Ordered collection of TRAIN COMPONENTs making up TRAIN. - - - - - - - - - - - - - - - - A vehicle composed of COMPOUND TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 - - - - - A vehicle composed of COMPOUND TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 - - - - - Ordered collection of TRAIN in COMPOUND TRAINs making up COMPOUND TRAIN. Each references a TRAIN. - - - - - - Ordered collection of TRAINs making up a COMPOUND TRAIN. Each references a TRAIN. - - - - - - - - - - - - - - A vehicle composed of COMPOUND TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 - + + xxx. +SIRI v2.1 + + + + + xxx. +SIRI v2.1 + - - - - Type for a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 - - - - - Order of TRAIN IN COMPOUND TRAIN within TRAIN. - - - - - Elements for a TRAIN IN COMPOUND TRAIN. - - - - - - - - Elements for a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 - - - - - Description of TRAIN IN COMPOUND TRAIN. - - - - - - Reference to a TRAIN. +SIRI v2.1 - - - - - - - Whether the component order of the TRAIN IN COMPOUND TRAIN is reversed compared to the order in the TRAIN. - - - - - Label for TRAIN IN COMPOUND TRAIN. - - - - - - - - - - - Elements for a VEHICLE. TYPE. +SIRI v2.1 - - - - - Name of VEHICLE TYPE. - - - - - Short Name of VEHICLE TYPE. - - - - - Description of VEHICLE TYPE. - - - - - - - Facilities of VEHICLE. - - - - - - - Prooprty Elements for a VEHICLE. TYPE. +SIRI v2.1 - - - - - Whether vehicles of the type have a reversing direction. - - - - - Whether vehicles of the type are self-propelled. - - - - - The type of fuel used by a vehicle of the type. - - - - - Euroclass of the vehicle type. - - - - - Total Number of passengers that VEHICLE TYPE. can carry. - - - - - Break down of Capacities by FARE CLASS. - - - - - - - - - - - - - - Dimension elements for a VEHICLE TYPE. +SIRI v2.1 - - - - - The length of a VEHICLE of the type. - - - - - The width of a VEHICLE of the type. - - - - - The length of a VEHICLE of the type. - - - - - The weight of a VEHICLE of the type. - - - - - - - Elements specifying Requirement properties of VEHICLE TYPE. Vehicle should satisfy these requirements. +SIRI v2.1 - - - - - Whether Vehicle is low floor to facilitate access by the mobility impaired. - - - - - Whether vehicle has lift or ramp to facilitate wheelchair access. - - - - - Whether vehicle has hoist for wheelchair access. - - - - - - - - + + + Orientation of a vehicle or vehicle formation/composition relative to a QUAY. Possible values might include 'towardsStartOfQuay', 'towardsEndOfQuay' or 'towards0'. +The latter example would implicate that the vehicle will depart towards the reference point of the QUAY (reference for measurements such as the VehicleStoppingPosition of SectorPositionAssignments). +SIRI v2.1 + + + + + xxx. +SIRI v2.1 + + + + + + + xxx. +SIRI v2.1 + + + + + xxx. +SIRI v2.1 + + + + + xxx. +SIRI v2.1 + + + + + xxx. +SIRI v2.1 + + + + + + + xxx. +SIRI v2.1 + + + + + + xxx. +SIRI v2.1 + + + + + + + + + + + xxx. +SIRI v2.1 + + + + + xxx. +SIRI v2.1 + + + + + Break down of Capacities by FARE CLASS (number of passengers that TRAIN ELEMENT can carry). + + + + + + + + + + + xxx. +SIRI v2.1 + + + + + + + + Capacity for a VEHICLE TYPE and fare class. +SIRI v2.1 + + + + + Capacity for a VEHICLE TYPE and fare class. +SIRI v2.1 + + + + + Fare class in VEHICLE for which capacity is specified. + + + + + How occupied or full the VEHICLE is. This is an approximate figure. The PassengerCapacityGroup provides more accurate data. + + + + + + + + Elements for a PASSENGER CAPACITY REQUIREMENT. relevant for passenger systems. +SIRI v2.1 + + + + + The total capacity of vehicles of the type. For a requirement this is the minimum needed. + + + + + The seating capacity of vehicles of the type. For a requirement this is the minimum needed. + + + + + The standing capacity of vehicles of the type. For a requirement this is the minimum needed. + + + + + The number of special places on vehicles of the type, e.g. seats for the disabled. For a requirement this is the minimum needed. + + + + + The number of push chair places on vehicles of the type. For a requirement this is the minimum needed. + + + + + The number of wheelchairs places on vehicles of the type. For a requirement this is the minimum needed. + + + + + + + + A vehicle composed of TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 + + + + + A vehicle composed of TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 + + + + + Identifier for TRAIN ELEMENT. + + + + + + + + Elements for a TRAIN ELEMENT. +SIRI v2.1 + + + + + Name of TRAIN ELEMENT. + + + + + Description of TRAIN ELEMENT. + + + + + Type of TRAIN ELEMENT. + + + + + + Break down of Capacities by FARE CLASS (number of passengers that TRAIN ELEMENT can carry). + + + + + + + + + + The length of a TRAIN ELEMENT. + + + + + The width of a TRAIN ELEMENT. + + + + + + Facilities of element. + + + + + + Actual EQUIPMENT on element. + + + + + + + + A vehicle composed of TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 + + + + + A vehicle composed of TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 + + + + + Identifier for TRAIN COMPONENT. + + + + + Order of TRAIN ELEMENT within TRAIN. + + + + + + + + Elements for a TRAIN COMPONENT. +SIRI v2.1 + + + + + Label for TRAIN COMPONENT. + + + + + Description of TRAIN COMPONENT. + + + + + + + + + + + + A vehicle composed of TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 + + + + + A vehicle composed of TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 + + + + + Label for TRAIN COMPONENT. + + + + + + + + + Elements for TRAIN. +SIRI v2.1 + + + + + Number of cars needed in TRAIN. + + + + + Nature of Train Size., Short, long, normal. Default is normal. + + + + + Ordered collection of TRAIN COMPONENTs making up TRAIN. + + + + + + + + + + + + + + A vehicle composed of COMPOUND TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 + + + + + A vehicle composed of COMPOUND TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 + + + + + Ordered collection of TRAIN in COMPOUND TRAINs making up COMPOUND TRAIN. Each references a TRAIN. + + + + + + Ordered collection of TRAINs making up a COMPOUND TRAIN. Each references a TRAIN. + + + + + + + + + + + + + A vehicle composed of COMPOUND TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 + + + + + Type for a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 + + + + + Order of TRAIN IN COMPOUND TRAIN within TRAIN. + + + + + Elements for a TRAIN IN COMPOUND TRAIN. + + + + + + + Elements for a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 + + + + + Description of TRAIN IN COMPOUND TRAIN. + + + + + + Reference to a TRAIN. +SIRI v2.1 + + + + + + + Whether the component order of the TRAIN IN COMPOUND TRAIN is reversed compared to the order in the TRAIN. + + + + + Label for TRAIN IN COMPOUND TRAIN. + + + + + + + + Elements for a VEHICLE. TYPE. +SIRI v2.1 + + + + + Name of VEHICLE TYPE. + + + + + Short Name of VEHICLE TYPE. + + + + + Description of VEHICLE TYPE. + + + + + + + + Facilities of VEHICLE. + + + + + + + Prooprty Elements for a VEHICLE. TYPE. +SIRI v2.1 + + + + + Whether vehicles of the type have a reversing direction. + + + + + Whether vehicles of the type are self-propelled. + + + + + The type of fuel used by a vehicle of the type. + + + + + Euroclass of the vehicle type. + + + + + Total Number of passengers that VEHICLE TYPE. can carry. + + + + + Break down of Capacities by FARE CLASS. + + + + + + + + + + + + + + Dimension elements for a VEHICLE TYPE. +SIRI v2.1 + + + + + The length of a VEHICLE of the type. + + + + + The width of a VEHICLE of the type. + + + + + The length of a VEHICLE of the type. + + + + + The weight of a VEHICLE of the type. + + + + + + + Elements specifying Requirement properties of VEHICLE TYPE. Vehicle should satisfy these requirements. +SIRI v2.1 + + + + + Whether Vehicle is low floor to facilitate access by the mobility impaired. + + + + + Whether vehicle has lift or ramp to facilitate wheelchair access. + + + + + Whether vehicle has hoist for wheelchair access. + + + + + From fcd4116e92d1516fd2d0a3026ff9f90e0e89fce0 Mon Sep 17 00:00:00 2001 From: "Willering HW (Henno)" Date: Wed, 29 Jan 2020 12:02:18 +0100 Subject: [PATCH 076/290] CR15: Harmonizing enums with TPEG2 PTS tables --- ...EXIISchema_2_0RC1_2_0 with definitions.xsd | 74 +- xsd/datex2/DATEXIISchema_2_0RC1_2_0.xsd | 16 +- xsd/siri_model/siri_reference-v2.0.xsd | 112 +- xsd/siri_model/siri_situation-v2.0.xsd | 335 ++- xsd/siri_model/siri_situationAffects-v2.0.xsd | 179 +- .../siri_situationClassifiers-v1.1.xsd | 301 ++- xsd/siri_model/siri_situationReasons-v2.0.xsd | 1943 +++++------------ .../siri_situationServiceTypes-v1.0.xsd | 612 ++++-- xsd/siri_model/siri_time-v2.0.xsd | 194 +- 9 files changed, 1916 insertions(+), 1850 deletions(-) diff --git a/xsd/datex2/DATEXIISchema_2_0RC1_2_0 with definitions.xsd b/xsd/datex2/DATEXIISchema_2_0RC1_2_0 with definitions.xsd index a69f18f4..fc4da495 100644 --- a/xsd/datex2/DATEXIISchema_2_0RC1_2_0 with definitions.xsd +++ b/xsd/datex2/DATEXIISchema_2_0RC1_2_0 with definitions.xsd @@ -6731,9 +6731,14 @@ - Types of public events. + Type of public event (Datex2 PublicEventTypeEnum and PublicEventType2Enum combined) + + + Unknown + + Agricultural show or event which could disrupt traffic. @@ -6744,19 +6749,19 @@ Air show or other aeronautical event which could disrupt traffic. - + - Athletics event that could disrupt traffic. + Art event that could disrupt traffic. - + - Commercial event which could disrupt traffic. + Athletics event that could disrupt traffic. - + - Cultural event which could disrupt traffic. + Beer festival that could disrupt traffic. @@ -6804,6 +6809,11 @@ Formal or religious act, rite or ceremony that could disrupt traffic. + + + Commercial event which could disrupt traffic. + + Concert event that could disrupt traffic. @@ -6814,6 +6824,11 @@ Cricket match that could disrupt traffic. + + + Cultural event which could disrupt traffic. + + Major display or trade show which could disrupt traffic. @@ -6829,11 +6844,31 @@ Celebratory event or series of events which could disrupt traffic. + + + Film festival that could disrupt traffic. + + Film or TV making event which could disrupt traffic. + + + Fireworks display that could disrupt traffic. + + + + + Flower event that could disrupt traffic. + + + + + Food festival that could disrupt traffic. + + Football match that could disrupt traffic. @@ -6899,6 +6934,11 @@ Motor sport race meeting that could disrupt traffic. + + + Open air concert that could disrupt traffic. + + Formal display or organised procession which could disrupt traffic. @@ -6934,6 +6974,11 @@ Horse showing jumping and tournament event that could disrupt traffic. + + + Sound and light show that could disrupt traffic. + + Sports event of unspecified type that could disrupt traffic. @@ -6944,11 +6989,21 @@ Public ceremony or visit of national or international significance which could disrupt traffic. + + + Street festival that could disrupt traffic. + + Tennis tournament that could disrupt traffic. + + + Theatrical event that could disrupt traffic. + + Sporting event or series of events of unspecified type lasting more than one day which could disrupt traffic. @@ -6964,6 +7019,11 @@ Water sports meeting that could disrupt traffic. + + + Wine festival that could disrupt traffic. + + Winter sports meeting or event (e.g. skiing, ski jumping, skating) that could disrupt traffic. diff --git a/xsd/datex2/DATEXIISchema_2_0RC1_2_0.xsd b/xsd/datex2/DATEXIISchema_2_0RC1_2_0.xsd index 5819bc03..31807f20 100644 --- a/xsd/datex2/DATEXIISchema_2_0RC1_2_0.xsd +++ b/xsd/datex2/DATEXIISchema_2_0RC1_2_0.xsd @@ -2171,26 +2171,33 @@ + + - - + + + + + + + @@ -2204,6 +2211,7 @@ + @@ -2211,12 +2219,16 @@ + + + + diff --git a/xsd/siri_model/siri_reference-v2.0.xsd b/xsd/siri_model/siri_reference-v2.0.xsd index be7bb3ae..fcca935e 100644 --- a/xsd/siri_model/siri_reference-v2.0.xsd +++ b/xsd/siri_model/siri_reference-v2.0.xsd @@ -29,24 +29,36 @@ 2007-03-29 - 2012-03-22 - SIRI 2.0 - Refactor Monitoring code - Add QUAY Ref - - 2012-06-22 - SIRI 2.0 - Add Group of Lines to JourneyPatternInfoGroup - [CH] Set explicit default value for VehicleAtStop to be false - [DE] Add Driver Ref - - 2013-02-11 - Correction: PlaceName unbounded to allow multiple languages - - 2018-11-08 - [vdv] "PublishedLineName" inside "PublishedLineGroup" changed to "unbounded" to allow multiple definitions for different languages due to the xml:lang-Attribute + + 2012-03-22 + + + + 2012-06-22 + + + + 2013-02-11 + + + + 2018-11-08 + + + 2020-01-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.

@@ -63,14 +75,14 @@ http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types-v2.0.xsd Unclassified - CEN, VDV, RTIG 2004-2012 - + CEN, VDV, RTIG 2004-2020 +
  • Derived from the VDV, RTIG CML and Trident standards.
- Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -626,12 +638,64 @@ Values for these elements can be specified on an annual schedule and will be inh - Passenger load status of a VEHICLE. + Passenger load status of a VEHICLE - GTFS-R / TPEG Pts045 - - - + + + TPEG Pts45_0, unknown + + + + + GTFS-R "EMPTY" + + + + + GTFS-R "MANY_SEATS_AVAILABLE" / TPEG Pts45_1, many seats available + + + + + GTFS-R "FEW_SEATS_AVAILABLE" / TPEG Pts45_2, few seats available + + + + + GTFS-R "STANDING_ROOM_ONLY" / TPEG Pts45_4, standing room only (and TPEG Pts45_3, no seats available) + + + + + GTFS-R "CRUSHED_STANDING_ROOM_ONLY" + + + + + GTFS-R "FULL" / TPEG Pts45_5, full + + + + + GTFS-R "NOT_ACCEPTING_PASSENGERS" + + + + + TPEG Pts45_255, undefined occupancy + + + + + (SIRI 2.1) deprecated - use a more specific value + + + + + (SIRI 2.1) deprecated - use a more specific value + + diff --git a/xsd/siri_model/siri_situation-v2.0.xsd b/xsd/siri_model/siri_situation-v2.0.xsd index 905ed0e0..22baaad9 100644 --- a/xsd/siri_model/siri_situation-v2.0.xsd +++ b/xsd/siri_model/siri_situation-v2.0.xsd @@ -20,7 +20,7 @@ e-service developers Waldemar Isajkin (INIT GmbH) Europe - >Drafted for version 1.0 Kizoom SITUATION Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk + Drafted for version 1.0 Kizoom SITUATION Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk 2004-09-29 @@ -30,41 +30,54 @@ 2007-05-14 - 2008-07-05 - - correct data tupe to be particpant ref not participant pair - - add missing scopeType to classifier - - 2011-04-18 - - AffectedVehicleJourney should allow multiple journeys. Brian Ferris onebusaway.org - - 2012-03-23 - +SIRI v2.0 - Use revised 2.0 definitions - Update to use DATEXII V 2.0 schema - Namespace changed from http://datex2.eu/schema/1_0/1_0 to http://datex2.eu/schema/2_0RC1/2_0 - - - D2LogicalModel:ReferencePointLinear has been renamed to D2LogicalModel:ReferencePointLinear - - DelayCodeENum renamed to DelayBandEnum - - - InformationUsageOverride / D2LogicalModel:InformationUsage dropped for D2 - - D2LogicalModel:SourceInformation renamed to D2LogicalModel:Source - - - D2LogicalModel:SourceInformation values wrapped in valuse tag - - D2LogicalModel:Advcie dropped. - - D2LogicalModel:Imppact ImpactDetails wrapper tag dropped. - - D2 trafficResstrictionType renamed to trafficConstrictionType - Correct type on easementref to normalized string. - Allow transalatiobs of NLString elements - - 2013-02-11 - Correction: Certain elements of DescriptionGroup unbounded. - - 2013-10-01 - - [VDV] Added TpegSubReasonGroup to the ReasonGroup as described in the SX Documentation - - 2014-06-20 - - [fr] Add additional small delay bands - + + 2008-07-05 + + + + 2011-04-18 + + + + 2012-03-23 + + + + 2013-02-11 + + + + 2013-10-01 + + + + 2014-06-20 + + + + 2019-09-01 + +

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

@@ -75,22 +88,21 @@ {http://www.siri.org.uk/schema/2.0/xsd/}siri_model/siri_situation-v2.0.xsd [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD + CEN http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_stop-v0.2.xsd http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modes-v1.1.xsd http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd Unclassified - - Kizoom 2000-2005, CEN 2009-2012 - + Kizoom 2000-2005, CEN 2009-2020 +
  • Schema Derived from the Kizoom XTIS schema
- Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -99,7 +111,7 @@ Public transport, Bus services, Coach services, Bus stops and stations, Rail transport, Railway stations and track, Train services, Underground trains, Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, Rail transport, Roads and road transport - + CEN TC278 WG3 SG7 SIRI-SX Xml Schema for PT SITUATIONs. Common element subschema @@ -661,7 +673,7 @@ Rail transport, Roads and road transport - Structured Classification Elements. Corresponds to TPEG 18 Event Reason. + Structured Classification Elements using TPEG Pts038 AlertCause. @@ -702,13 +714,13 @@ Rail transport, Roads and road transport - additioanl reasons. + Additional reasons - Reason. + Reason @@ -727,10 +739,14 @@ Rail transport, Roads and road transport - + + + Deprecated (SIRI 2.1) - use only TpegReasonGroup and PublicEventReason. + + - Classifier of Pub;ic Event. + Classifier of Public Event. @@ -779,24 +795,109 @@ Rail transport, Roads and road transport - Values for ScopeType. + Values for ScopeType - TPEG Pts36, AlertForType with additional values - - - - - - - - - - - - - - - + + + TPEG Pts36_0, unknown + + + + + TPEG Pts36_1, stop place + + + + + TPEG Pts36_2, line + + + + + TPEG Pts36_3, route + + + + + TPEG Pts36_4, individual PT service + + + + + TPEG Pts36_5, operator + + + + + TPEG Pts36_6, city + + + + + TPEG Pts36_7, area + + + + + TPEG Pts36_8, stop point + + + + + stop place component + + + + + place + + + + + network + + + + + vehicle journey + + + + + dated vehicle journey + + + + + connection link + + + + + interchange + + + + + TPEG Pts36_0, unknown + + + + + general + + + + + road + + + + + TPEG Pts36_255, undefined + + @@ -1124,7 +1225,7 @@ Rail transport, Roads and road transport Period of effect of disruption, if different from that of SITUATION. - + Severity of disruption if different from that of SITUATION. TPEG pti26 @@ -1178,6 +1279,14 @@ Rail transport, Roads and road transport + + + Structured Condition Elements. + + + + + Type for boarding restrictions. @@ -1202,9 +1311,10 @@ Rail transport, Roads and road transport - Reference to a standardis advisory NOTICE to be given to passengers if a particular condition arises . + Reference to a standard advisory NOTICE to be given to passengers if a particular condition arises. + Further Textual advice to passengers. (Unbounded since SIRI 2.0) @@ -1212,6 +1322,99 @@ Rail transport, Roads and road transport + + + Values for TPEG Pts039 - AdviceType, with some additional values + + + + + TPEG Pts39_0, unknown + + + + + TPEG Pts39_1, use replacement bus + + + + + TPEG Pts39_2, use replacement train + + + + + TPEG Pts39_3, use the alternative route + + + + + TPEG Pts39_4, go on foot + + + + + TPEG Pts39_5, please leave the station! Danger! + + + + + TPEG Pts39_6, no means of travel + + + + + TPEG Pts39_7, use different stops + + + + + TPEG Pts39_8, use alternative stop + + + + + TPEG Pts39_9, do not leave vehicle! Danger! + + + + + TPEG Pts39_10, take advice from announcements + + + + + TPEG Pts39_11, take advice from personnel + + + + + TPEG Pts39_12, obey advice from police + + + + + use other PT services + + + + + use interchange + + + + + no advice + + + + + TPEG Pts39_255, undefined advice + + + + + Type for blocking. @@ -1254,7 +1457,7 @@ Rail transport, Roads and road transport - Type for allwoed values of DelayBand. Based on Datex2 + Type for allowed values of DelayBand. Based on Datex2, with some additional values. diff --git a/xsd/siri_model/siri_situationAffects-v2.0.xsd b/xsd/siri_model/siri_situationAffects-v2.0.xsd index 8eca886d..9ef12c3a 100644 --- a/xsd/siri_model/siri_situationAffects-v2.0.xsd +++ b/xsd/siri_model/siri_situationAffects-v2.0.xsd @@ -22,7 +22,7 @@ e-service developers Waldemar Isajkin (INIT GmbH) Europe - >Drafted for version 1.0 Kizoom Incident Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk + Drafted for version 1.0 Kizoom Incident Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk 2007-09-29 @@ -33,25 +33,37 @@ 2008-07-05 - 2013-10-10 - [vdv] Added Service Condition to the AffectedVehicleJourney + + 2013-10-10 + + + + 2014-06-20 + + + + 2018-11-08 + + + + 2020-01-28 + +

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

@@ -69,15 +81,14 @@ http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey-v2.0.xsd Unclassified - - Kizoom 2000-2007, CEN 2009-2012 - + Kizoom 2000-2007, CEN 2009-2020 +
  • Schema derived Derived from the Kizoom XTIS schema
- Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -184,19 +195,6 @@ Rail transport, Roads and road transport - - - - Values for Area Of Interest. - - - - - - - - - @@ -806,7 +804,7 @@ Rail transport, Roads and road transport - enum Status of service for this Vehicle Journey - TPEG value. Multiple Condtions can be valid at the same time. (+SIRI 2.0) + enum Status of service for this Vehicle Journey - TPEG value. Multiple Conditions can be valid at the same time. (+SIRI 2.0) @@ -1069,7 +1067,7 @@ Rail transport, Roads and road transport Name of stop place. (Unbounded since SIRI 2.0) - + Type of Stop Place. @@ -1186,5 +1184,122 @@ Rail transport, Roads and road transport + + + Values for STOP PLACE types - TPEG Pts041 and IFOPT + + + + + TPEG Pts41_0, unknown + + + + + TPEG Pts41_1, railway station + + + + + TPEG Pts41_2, underground station + + + + + IFOPT, TPEG Pts41_3, tram station + + + + + IFOPT, TPEG Pts41_4, bus station + + + + + IFOPT, TPEG Pts41_5, airport + + + + + TPEG Pts41_6, pier + + + + + IFOPT, TPEG Pts41_7, harbour port + + + + + ,IFOPT, TPEG Pts41_8, ferry stop + + + + + TPEG Pts41_9, light railway station + + + + + TPEG Pts41_10, cogwheel station + + + + + TPEG Pts41_11, funicular station + + + + + TPEG Pts41_12, ropeway station + + + + + IFOPT, coach station + + + + + IFOPT, ferry port + + + + + IFOPT, on-street bus stop + + + + + IFOPT, on-street tram stop + + + + + IFOPT, ski lift + + + + + IFOPT, other + + + + + TPEG Pts41_255, undefined stop place type + + + + + IFOPT, deprecated (SIRI 2.1), use railwayStation + + + + + IFOPT, deprecated (SIRI 2.1), use undergroundStation + + + + diff --git a/xsd/siri_model/siri_situationClassifiers-v1.1.xsd b/xsd/siri_model/siri_situationClassifiers-v1.1.xsd index fbd0cbf1..8b5ee21c 100644 --- a/xsd/siri_model/siri_situationClassifiers-v1.1.xsd +++ b/xsd/siri_model/siri_situationClassifiers-v1.1.xsd @@ -7,7 +7,7 @@ e-service developers Add names Europe - >Drafted for version 1.0 Kizoom Incident Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk + Drafted for version 1.0 Kizoom Incident Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk 2008-07-05 @@ -18,6 +18,14 @@ 2008-10-01 + + 2019-09-01 + +

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

@@ -28,20 +36,18 @@ {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}/siri_situationClassifiers-v1.1.xsd [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - - + CEN + Unclassified - Kizoom 2000-2007, CEN 2009-2012 - + Kizoom 2000-2007, CEN 2009-2020 +
  • Schema derived Derived from the Kizoom XTIS schema
  • Derived from the TPEG Categories schema
- Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -50,7 +56,7 @@ Public transport, Bus services, Coach services, Bus stops and stations, Rail transport, Railway stations and track, Train services, Underground trains, Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, Rail transport, Roads and road transport - + CEN TC278 WG3 SG7 SIRI-SX Xml Schema for PT Incidents. Classifier subschema @@ -63,60 +69,52 @@ Rail transport, Roads and road transport - Severity of Incident. Corresponds to TPEG Pti26 severities. Defautl is 'normal'. + Severity of Incident - TPEG Pti26. Default is 'normal'. - Values for Severity. Correspond to TPEG Pti26 Severity values. + Values for TPEG Pti26 - Severity - - TPEG Pti26_0: unknown. + TPEG Pti26_0, unknown - - TPEG Pti26_1: very slight. + TPEG Pti26_1, very slight - - TPEG Pti26_2: slight. + TPEG Pti26_2, slight - - TPEG Pti26_3: normal. + TPEG Pti26_3, normal - - TPEG Pti26_4: severe. + TPEG Pti26_4, severe - - TPEG Pti26_5: verySevere. + TPEG Pti26_5, very severe - - TPEG Pti26_6: noImpact. + TPEG Pti26_6, no impact - - TPEG Pti26_255: undefined. + TPEG Pti26_255, undefined @@ -124,138 +122,247 @@ Rail transport, Roads and road transport - Classification of effect on service. TPEG Pti13 Service Condition values. + Classification of effect on service - TPEG Pts43 - Values for Service Condition. Corresponds to TPEG Pti13 Service Condition values. + Values for TPEG Pts43 ServiceStatus, with additional values from Pti013 - - TPEG Pti13_unknown. + TPEG Pts43_0, unknown - - + - TPEG Pti13_altered. + TPEG Pts43_1, delay - - + - TPEG Pti13_cancelled. + TPEG Pts43_2, minor delays - - + + + TPEG Pts43_3, major delays + + + + + TPEG Pts43_4, operation time extension + + + + + TPEG Pts43_5, on time + + + + + TPEG Pts43_6, disturbance rectified + + + + + TPEG Pts43_7, change of platform + + + + + TPEG Pts43_8, line cancellation + + + + + TPEG Pts43_9, trip cancellation + + + + + TPEG Pts43_10, boarding + + + + + TPEG Pts43_11, go to gate + + + + + TPEG Pts43_12, stop cancelled + + + + + TPEG Pts43_13, stop moved + + + + + TPEG Pts43_14, stop on demand + + + - TPEG Pti13_delayed. + TPEG Pts43_15, additional stop + + + + + TPEG Pts43_16, substituted stop - - TPEG Pti13_diverted. + TPEG Pts43_17, diverted + + + + + TPEG Pts43_18, disruption + + + + + TPEG Pts43_19, limited operation + + + + + TPEG Pts43_20, discontinued operation + + + + + TPEG Pts43_21, irregular traffic + + + + + TPEG Pts43_22, wagon order changed + + + + + TPEG Pts43_23, train shortened + + + + + TPEG Pts43_24, additional ride + + + + + TPEG Pts43_25, replacement ride + + + + + TPEG Pts43_26, temporarily non-stopping + + + + + TPEG Pts43_27, temporary stopplace + + + + + TPEG Pts43_255, undefined status + + + + + TPEG Pti13_1, deprecated (SIRI 2.1) + + + + + TPEG Pti13_2, deprecated (SIRI 2.1) + + + + + TPEG Pti13_3, deprecated (SIRI 2.1) - - TPEG Pti13_no service. + TPEG Pti13_5, deprecated (SIRI 2.1) - - TPEG Pti13_disrupted. + TPEG Pti13_6, deprecated (SIRI 2.1) - - TPEG Pti13_additional service. + TPEG Pti13_7, deprecated (SIRI 2.1) - - TPEG Pti13_special service. - - - - - - TPEG Pti13_on time. + TPEG Pti13_8, deprecated (SIRI 2.1) - - TPEG Pti13_normal service. + TPEG Pti13_10, deprecated (SIRI 2.1) - - TPEG Pti13_intermittent service. + TPEG Pti13_11, deprecated (SIRI 2.1) - - TPEG Pti13_short formed service. + TPEG Pti13_12, deprecated (SIRI 2.1) - - TPEG Pti13_full length service. + TPEG Pti13_13, deprecated (SIRI 2.1) - - TPEG Pti13_extended service. + TPEG Pti13_14, deprecated (SIRI 2.1) - - TPEG Pti13_splitting train. + TPEG Pti13_15, deprecated (SIRI 2.1) - - TPEG Pti13_replacement transport. + TPEG Pti13_16, deprecated (SIRI 2.1) - - TPEG Pti13_arrives early. + TPEG Pti13_17, deprecated (SIRI 2.1) - - TPEG Pti13_shuttle service. + TPEG Pti13_18, deprecated (SIRI 2.1) - - TPEG Pti13_replacement service. + TPEG Pti13_19, deprecated (SIRI 2.1) - - TPEG Pti13_Undefined service information. + TPEG Pti13_255, deprecated (SIRI 2.1) @@ -263,7 +370,7 @@ Rail transport, Roads and road transport - Classification of verification status TPEG Pti13 Service Condition values. + Classification of verification status - TPEG Pti032 @@ -271,16 +378,34 @@ Rail transport, Roads and road transport - Values for Verification Status Corresponds to TPEG pti_table 32. + Values for TPEG Pti032 - VerificationStatus - - - - - - - + + + TPEG Pti32_0, unknown + + + + + TPEG Pti32_1, unverified + + + + + TPEG Pti32_?, verified + + + + + TPEG Pti32_?, verifiedAsDuplicate + + + + + TPEG Pti32_255 ? + + @@ -289,7 +414,7 @@ Rail transport, Roads and road transport Classification of Predictability status. - + diff --git a/xsd/siri_model/siri_situationReasons-v2.0.xsd b/xsd/siri_model/siri_situationReasons-v2.0.xsd index 927f83cd..70e9f006 100644 --- a/xsd/siri_model/siri_situationReasons-v2.0.xsd +++ b/xsd/siri_model/siri_situationReasons-v2.0.xsd @@ -7,7 +7,7 @@ e-service developers Add names Europe - >Drafted for version 1.0 Kizoom Incident Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk + Drafted for version 1.0 Kizoom Incident Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk 2004-09-29 @@ -20,65 +20,76 @@ 2007-05-14 - 2008-07-05 - split out classifiers - - 2009-03-31 - add subreason elements - - 2018-11-13 - [vdv] MiscellaneousReasonEnumeration TPEC-code of "altercation" changed from pti19_1_Alias_6 to pti19_1_Alias_7 because TPEC-code pti19_1_Alias_6 was wrongly doubled in use for "emergencyServicesCall" and "altercation" - [vdv] MiscellaneousReasonEnumeration TPEC-code of "illVehicleOccupants" changed from pti19_1_Alias_7 to pti19_1_Alias_8 - [vdv] MiscellaneousReasonEnumeration TPEC-code of "undefinedProblem" changed from pti19_27 to pti19_255 - [vdv] MiscellaneousSubReasonEnumeration TPEC-code value "assault" added according to recommendation document and Datex2 - [vdv] EquipmentReasonEnumeration TPEC-code pti21_6_Alias_2 "defectiveTrain" added according to recommendation document - [vdv] EquipmentReasonEnumeration TPEC-code pti21_8_Alias_10 "leveCrossingFailure" changed to "levelCrossingFailure" according to recommendation document - [vdv] EquipmentReasonEnumeration TPEC-code pti21_8_Alias_11 "trafficManagementSystemFailure" added according to recommendation document - [vdv] EquipmentReasonEnumeration TPEC-code pti21_12_Alias_1 value changed from "oveheadWireFailure" to "overheadWireFailure" according to recommendation document - [vdv] EquipmentSubReasonEnumeration TPEC-code value "defectiveTrain" added according to recommendation document - [vdv] EquipmentSubReasonEnumeration TPEC-code value "leveCrossingFailure" changed to "levelCrossingFailure" according to recommendation document - [vdv] EquipmentSubReasonEnumeration TPEC-code value "trafficManagementSystemFailure" added according to recommendation document - [vdv] EquipmentSubReasonEnumeration TPEC-code value "oveheadWireFailure" changed to "overheadWireFailure" according to recommendation document - [vdv] EnvironmentReasonEnumeration TPEC-code pti22_13_Alias_1 "flashFloods" added according to recommendation document - [vdv] EnvironmentReasonEnumeration TPEC-code pti22_19_Alias_1 "mudslide" added according to recommendation document - [vdv] EnvironmentReasonEnumeration TPEC-code pti22_19_Alias_2 "rockfalls" added according to recommendation document - [vdv] EnvironmentReasonEnumeration TPEC-code pti22_19_Alias_3 "subsidence" added according to recommendation document - [vdv] EnvironmentReasonEnumeration TPEC-code pti22_19_Alias_4 "earthquakeDamage" added according to recommendation document - [vdv] EnvironmentReasonEnumeration TPEC-code pti22_3_Alias_3 "avalanches" added according to TPEG document - [vdv] EnvironmentReasonEnumeration TPEC-code pti22_13_Alias_1 "flashFloods" added according to recommendation document - [vdv] EnvironmentSubReasonEnumeration TPEC-code value "lighteningStrike" changed to "lightningStrike" according to recommendation document - [vdv] EnvironmentSubReasonEnumeration TPEC-code value "mudslip" changed to "mudslide" according to recommendation document and Datex2 - - 2014-06-23 - +SIRI v2.0 - add Holiday and PoliceActivity rsubeasons to Miscellaneous - Correct Reason codes to match spec. - + + 2008-07-05 + + + + 2009-03-31 + + + + 2018-11-13 + + + + 2014-06-23 + + + + 2019-09-01 + + -

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

+

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

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri_model}/siri_situationReasons-v1.0.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri_model}/siri_situationReasons-v2.0.xsd [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - + CEN + Unclassified - - Kizoom 2000-2007, CEN 2009-2012 - + Kizoom 2000-2007, CEN 2009-2020 +
    -
  • Schema derived Derived from the Kizoom XTIS schema
    • -
  • Derived from the TPEG Categories schema
    • +
  • Schema derived from the Kizoom XTIS schema
    • +
  • Derived from the TPEG2 AlertCause schema
- Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -87,7 +98,7 @@ Public transport, Bus services, Coach services, Bus stops and stations, Rail transport, Railway stations and track, Train services, Underground trains, Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, Rail transport, Roads and road transport - + CEN TC278 WG3 SG7 SIRI-SX Xml Schema for PT Incidents. Reasons subschema @@ -98,20 +109,33 @@ Rail transport, Roads and road transport - Structured Classification Elements. Corresponds to TPEG 18 Event Reason. + Structured Classification Elements. - + + + Classification corresponding to TPEG Pts38 - AlertCause + + + + + Deprecated (SIRI 2.1) - use only TpegReason. + + - Personnel reason. + Deprecated (SIRI 2.1) - use only TpegReason. + + + + + Deprecated (SIRI 2.1) - use only TpegReason. - - Environment reason. + Deprecated (SIRI 2.1) - use only TpegReason. @@ -119,2044 +143,1195 @@ Rail transport, Roads and road transport - Structured Classification Elements. Corresponds to TPEG 18 Event Reason. + Deprecated (SIRI 2.1) - use only TpegReasonGroup. - - - Personnel reason. - - + - - - Environment reason. - - + - TPEG Pti18_0/TPEG unknown event reason. + TPEG Pts38_0, unknown alert cause + + + + + + TPEG Pts38_255, undefined alert cause - + - TPEG Pti18_1/TPEG Pti_19 miscellaneous event reason. + TPEG Pts38 - AlertCause - + + - Values for Miscellaneous incident reason types TPEG Pti18_1/TPEG Pti_19. + Values for TPEG Pts38 - AlertCause, plus additional values from TPEG Pti19/20/21/22 - - TPEG Pti_19_0 unknown. + TPEG Pts38_0, unknown - - + - 19:0_1 Previous disturbances - alias to TPEG Pti_19_0 unknown + TPEG Pts38_1, security alert - - + - TPEG Pti_19_1 incident. + TPEG Pts38_2, emergency services call - - + - Near Miss - alias to TPEG Pti_19_1 incident. + TPEG Pts38_3, police activity - - + - Near Miss - alias to TPEG Pti_19_1 incident. + TPEG Pts38_4, police order - - + - Signal passed at danger - alias to TPEG Pti_19_1 incident. + TPEG Pts38_5, fire - - + - Station overrun - alias to TPEG Pti_19_1 incident. + TPEG Pts38_6, cable fire - - + - trainDoor- alias to TPEG Pti_19_1 incident. + TPEG Pts38_7, smoke detected on vehicle - - + - Unspecified emergency service visit. Alias to pti19 + TPEG Pts38_8, fire at the station - - + - TPEG Pti_19_2 bomb explosion. + TPEG Pts38_9, fire run - - + - TPEG Pti_19_3 security alert. + TPEG Pts38_10, fire brigade order - - + - pti19_3_1 request of the police Alias to TPEG Pti_19_3 security alert. + TPEG Pts38_11, explosion - - + - pti19_3_2 fire brigade safety checksAlias to TPEG Pti_19_3 security alert. + TPEG Pts38_12, explosion hazard - - + - pti19_3_3 an unattended bag Talias to PEG Pti_19_3 security alert. + TPEG Pts38_13, bomb disposal - - + - telephoned threat TPEG Pti_19_3 security alert. + TPEG Pts38_14, emergency medical services - - + - telephoned threat TPEG Pti_19_3 security alert. + TPEG Pts38_15, emergency brake - - + - civilEmergency alias to TPEG Pti_19_3 security alert. + TPEG Pts38_16, vandalism - - + - civilEmergency alias to TPEG Pti_19_3 security alert. + TPEG Pts38_17, cable theft - - - - sabotage alias to TPEG Pti_19_3 security alert. - - - - - - - - - - - - - - - - - - - - - - - - + - TPEG Pti_19_4 fire. + TPEG Pts38_18, signal passed at danger - - + - linesideFire alias to TPEG Pti_19_4 fire. + TPEG Pts38_19, station overrun - - + - TPEG Pti_19_5 vandalism. + TPEG Pts38_20, passengers blocking doors - - + - passengerActionAlias to pti19 + TPEG Pts38_21, defective security system - - + - Assault on stafft.Alias to pti19 + TPEG Pts38_22, overcrowded - - + - Railway Crime Alias to pti19 + TPEG Pts38_23, border control - - + - Assault Alias to pti19 + TPEG Pts38_24, unattended bag - - + - Theft Alias to pti19 + TPEG Pts38_25, telephoned threat - - + - altercation . Alias to pti19 + TPEG Pts38_26, suspect vehicle - - + - illVehicleOccupants . Alias to pti19 + TPEG Pts38_27, evacuation - - + - TPEG Pti_19_6 accident. + TPEG Pts38_28, terrorist incident - - + - fatality alias to TPEG Pti_19_6 accident. + TPEG Pts38_29, public disturbance - - + - a person under a train - alias to TPEG Pti_19_6 accident. + TPEG Pts38_30, technical problem - - + - a person hit by a train - alias to TPEG Pti_19_6 accident. + TPEG Pts38_31, vehicle failure - - + - person ill On Vehicle -Alias to pti19_6 + TPEG Pts38_32, service disruption - - + - emergencyServices - alias to TPEG Pti_19_6 accident. + TPEG Pts38_33, door failure - - + - Collision - Alias to pti19_6 + TPEG Pts38_34, lighting failure - - + - TPEG Pti_19_7 overcrowded. + TPEG Pts38_35, points problem - - + - TPEG Pti_19_8 insufficient demand. + TPEG Pts38_36, points failure - - + - TPEG Pti_19_9 lighting failure. + TPEG Pts38_37, signal problem - - + - TPEG Pti_19_10 leader board failure. + TPEG Pts38_38, signal failure - - + - TPEG Pti_19_11 service indicator failure. + TPEG Pts38_39, overhead wire failure - - + - TPEG Pti_19_12 service failure. + TPEG Pts38_40, level crossing failure - - + - TPEG Pti_19_13 OPERATOR ceased trading. + TPEG Pts38_41, traffic management system failure - - + - TPEG Pti_19_14 OPERATOR suspended. + TPEG Pts38_42, engine failure - - + - TPEG Pti_19_15 congestion. + TPEG Pts38_43, break down - - + - TPEG Pti_19_16 route blockage. + TPEG Pts38_44, repair work - - + - TPEG Pti_19_17 person on the line. + TPEG Pts38_45, construction work - - + - TPEG Pti_19_18 VEHICLE on the line. + TPEG Pts38_46, maintenance work - - + - Level Crossing Incident - alias to TPEG Pti_19_18 VEHICLE on the line. + TPEG Pts38_47, power problem - - + - TPEG Pti_19_19 object on the line. + TPEG Pts38_48, track circuit - - + - fallen tree on line- alias to TPEG Pti_19_19 object on the line. + TPEG Pts38_49, swing bridge failure - - + - vegetation - alias to TPEG Pti_19_19 object on the line. + TPEG Pts38_50, escalator failure - - + - Train struck animal alias to TPEG Pti_19_19 object on the line. + TPEG Pts38_51, lift failure - - + - Train struck object alias to TPEG Pti_19_19 object on the line. + TPEG Pts38_52, gangway problem - - + - TPEG Pti_19_20 animal on the line. + TPEG Pts38_53, defective vehicle - - + - TPEG Pti_19_21 route diversion. + TPEG Pts38_54, broken rail - - + - TPEG Pti_19_22 road closed. + TPEG Pts38_55, poor rail conditions - - + - TPEG Pti_19_23 roadworks. + TPEG Pts38_56, de-icing work - - + - 19:23_1 sewerageMaintenance - alias to TPEG Pti_19_23 roadworks.. + TPEG Pts38_57, wheel problem - - + - 19:23_2 roadMaintenance - alias to TPEG Pti_19_23 roadworks.. + TPEG Pts38_58, route blockage - - + - 19:23_3 asphalting - alias to TPEG Pti_19_23 roadworks.. + TPEG Pts38_59, congestion - - + - 19:23_4 paving - alias to TPEG Pti_19_23 roadworks.. + TPEG Pts38_60, heavy traffic - - - - TPEG Pti_19_24 special event. - - - - - - - - - - - - - - - - - - + - TPEG Pti_19_25 bridge strike. + TPEG Pts38_61, route diversion - - + - 19:25_1 viaductFailure - alias to TPEG Pti_19_24 bridgeStrike + TPEG Pts38_62, roadworks - - + - TPEG Pti_19_26 overhead obstruction. + TPEG Pts38_63, unscheduled construction work - - + - TPEG Pti_19_255 undefined problem. + TPEG Pts38_64, level crossing incident - - - - - - + - 19:255_1 speedRestrictions alias to TPEG Pti_19_15 unknown + TPEG Pts38_65, sewerageMaintenance - - + - 19:255_2 logisticProblems alias to TPEG Pti_19_15 unknown + TPEG Pts38_66, road closed - - - - - - - Additional refinements TPEG miscellaneous event reason. - - - - - Values for Miscellaneous incident sub reason types. - - - + - TPEG Pti_19_0 unknown + TPEG Pts38_67, roadway damage - + - 19:0_1 Previous disturbances - alias to TPEG Pti_19_0 unknown + TPEG Pts38_68, bridge damage - + - TPEG Pti_19_1 incident. + TPEG Pts38_69, person on the line - + - 19:1_1 Near Miss - alias to TPEG Pti_19_1 incident. + TPEG Pts38_70, object on the line - + - 19:1_2 Near Miss - alias to TPEG Pti_19_1 incident. + TPEG Pts38_71, vehicle on the line - + - 19:1_3 Signal passed at danger - alias to TPEG Pti_19_1 incident. + TPEG Pts38_72, animal on the line - + - 19:1_4 Station overrun - alias to TPEG Pti_19_1 incident. + TPEG Pts38_73, fallen tree on the line - + - 19:1_5 trainDoor- alias to TPEG Pti_19_1 incident. + TPEG Pts38_74, vegetation - + - TPEG Pti_19_2 bomb explosion. + TPEG Pts38_75, speed restrictions - + - TPEG Pti_19_3 security alert. + TPEG Pts38_76, preceding vehicle - + - 19:1_6 Unspecified emergency service visit. Alias to pti19 + TPEG Pts38_77, accident - + - 19:3_1 Request of the police Alias to TPEG Pti_19_3 security alert. + TPEG Pts38_78, near miss - + - 19:3_2 Fire brigade safety checksAlias to TPEG Pti_19_3 security alert. + TPEG Pts38_79, person hit by vehicle - + - 19:3_3 An unattended bag TPEG Pti_19_3 security alert. + TPEG Pts38_80, vehicle struck object - + - 19:3_4 Telephoned threat TPEG Pti_19_3 security alert. + TPEG Pts38_81, vehicle struck animal - + - 19:3_5 telephoned threat TPEG Pti_19_3 security alert. + TPEG Pts38_82, derailment - + - 19:3_6 Civil Emergency Pti_19_3 security alert + TPEG Pts38_83, collision - + - 19:3_7 Air Raid Pti_19_3 security alert + TPEG Pts38_84, level crossing accident - + - 19:3_8 Sabotage Pti_19_3 security alert + TPEG Pts38_85, poor weather - + - 19:3_9 Bomb alert Pti_19_3 security alert + TPEG Pts38_86, fog - + - 19:3_10 Attack Pti_19_3 security alert + TPEG Pts38_87, heavy snowfall - + - 19:3_11 EvacuationPti_19_3 security alert + TPEG Pts38_88, heavy rain - + - 19:3_12 terrorist Incident Pti_19_3 security alert + TPEG Pts38_89, strong winds - - + - 19:3_14 Explosion Pti_19_3 security alert + TPEG Pts38_90, ice - + - 19:3_15 explosion Hazard Pti_19_3 security alert + TPEG Pts38_91, hail - + - 19:3_16 security Incident Pti_19_3 security alert + TPEG Pts38_92, high temperatures - + - 19:3_17 terrorist Incident Pti_19_3 security alert + TPEG Pts38_93, flooding - + - 19:3_18 terrorist Incident Pti_19_3 security alert + TPEG Pts38_94, low water level - + - TPEG Pti_19_4 fire + TPEG Pts38_95, risk of flooding - + - linesideFire alias to TPEG Pti_19_4 fire. + TPEG Pts38_96, high water level - + - TPEG Pti_19_5 vandalism + TPEG Pts38_97, fallen leaves - + - 19:5_1 passengerActionAlias to pti19_5 vandalism + TPEG Pts38_98, fallen tree - + - 19:5_2 Assault on staft.Alias to pti19_5 vandalism + TPEG Pts38_99, landslide - + - 19:5_3 Railway Crime Alias to pti19_5 vandalism + TPEG Pts38_100, risk of landslide - + - 19:5_4 assault Alias to pti19_5 vandalism + TPEG Pts38_101, drifting snow - + - 19:5_5 theft to pti19_5 vandalism + TPEG Pts38_102, blizzard conditions - + - 19:1_7 Railway Crime Alias to pti19_1 incident + TPEG Pts38_103, storm damage - + - 19:1_8 Railway Crime Alias to pti19_1 incident + TPEG Pts38_104, lightning strike - + - PEG Pti_19_6 accident + TPEG Pts38_105, rough sea - + - 19:6_1 fatality alias to TPEG Pti_19_6 accident. + TPEG Pts38_106, high tide - + - 19:6_2 a person under a train - alias to TPEG Pti_19_6 accident. + TPEG Pts38_107, low tide - + - 19:6_3 a person hit by a train - alias to TPEG Pti_19_6 accident. + TPEG Pts38_108, ice drift - + - 19:6_4 person ill On Vehicle -Alias to pti19_6 accident. + TPEG Pts38_109, avalanches - + - 19:6_5 emergencyServices - alias to TPEG Pti_19_6 accident. + TPEG Pts38_110, risk of avalanches - + - 19:6_6 Collision - Alias to pti19_6 accident. + TPEG Pts38_111, flash floods - + - TPEG Pti_19_07 overcrowded + TPEG Pts38_112, mudslide - + - TPEG Pti_19_08 insufficientDemand + TPEG Pts38_113, rockfalls - + - TPEG Pti_19_09 lightingFailure + TPEG Pts38_114, subsidence - + - TPEG Pti_19_10 leaderBoardFailure + TPEG Pts38_115, earthquake damage - + - TPEG Pti_19_11 serviceIndicatorFailure + TPEG Pts38_116, grass fire - + - TPEG Pti_19_12 serviceFailure + TPEG Pts38_117, wildland fire - + - TPEG Pti_19_13 operatorCeasedTrading + TPEG Pts38_118, ice on railway - + - TPEG Pti_19_14 operatorSuspended + TPEG Pts38_119, ice on carriages - + - TPEG Pti_19_15 congestion + TPEG Pts38_120, special event - + - TPEG Pti_19_16 routeBlockage + TPEG Pts38_121, procession - + - TPEG Pti_19_17 personOnTheLine + TPEG Pts38_122, demonstration - + - TPEG Pti_19_18 vehicleOnTheLine + TPEG Pts38_123, industrial action - + - TPEG Pti_19_19 objectOnTheLine + TPEG Pts38_124, staff sickness - + - 19:19_1 fallen tree on line- alias to TPEG Pti_19_19 object on the line. + TPEG Pts38_125, staff absence - - - 19:19_2 Vegetation - alias to TPEG Pti_19_19 object on the line. - - - + - 19:19_3 Train struck animal alias to TPEG Pti_19_19 object on the line. + TPEG Pts38_126, operator ceased trading - + - 19:19_4 Train struck object alias to TPEG Pti_19_19 object on the line. + TPEG Pts38_127, previous disturbances - + - 19:18_1 Level Crossing Incident - alias to TPEG Pti_19_18 VEHICLE on the line. + TPEG Pts38_128, vehicle blocking track - + - TPEG Pti_19_20 animal on the line. + TPEG Pts38_129, foreign disturbances - + - TPEG Pti_19_21 route diversion. + TPEG Pts38_130, awaiting shuttle - + - TPEG Pti_19_22 road closed. + TPEG Pts38_131, change in carriages - + - TPEG Pti_19_23 roadworks. + TPEG Pts38_132, train coupling - + - 19:23_1 sewerageMaintenance - alias to TPEG Pti_19_23 roadworks.. + TPEG Pts38_133, boarding delay - + - 19:23_2 roadMaintenance - alias to TPEG Pti_19_23 roadworks.. + TPEG Pts38_134, awaiting approach - + - 19:23_3 asphalting - alias to TPEG Pti_19_23 roadworks.. + TPEG Pts38_135, overtaking - + - 19:23_4 paving - alias to TPEG Pti_19_23 roadworks.. + TPEG Pts38_136, provision delay - + - TPEG Pti_19_24 special event. + TPEG Pts38_137, miscellaneous - + - 19:24_1 march - alias to TPEG Pti_19_24 specialEvent + TPEG Pts38_255, undefined alert cause - + - 19:24_2 procession - alias to TPEG Pti_19_24 specialEvent + TPEG Pti19_1, deprecated (SIRI 2.1) - + - 19:24_3 demonstration - alias to TPEG Pti_19_24 specialEvent + TPEG Pti19_1_2, deprecated (SIRI 2.1) - + - 19:24_4 publicDisturbance - alias to TPEG Pti_19_24 specialEvent + TPEG Pti19_1_5, deprecated (SIRI 2.1) - replaced by Pts38_33, door failure - + - 19:24_5 filterBlockade - alias to TPEG Pti_19_24 specialEvent + TPEG Pti19_1_7, deprecated (SIRI 2.1) - + - 19:24_6 sightseersObstructingAccess - alias to TPEG Pti_19_24 specialEvent + TPEG Pti19_1_8, deprecated (SIRI 2.1) - + - 19:24_7 sightseersObstructingAccess - alias to TPEG Pti_19_24 specialEvent + TPEG Pti19_1_12, deprecated (SIRI 2.1) - replaced by Pts38_32, service disruption - + - TPEG Pti_19_25 bridge strike. + TPEG Pti19_2, deprecated (SIRI 2.1) - + - 19:25_1 viaductFailure - alias to TPEG Pti_19_24 bridgeStrike + TPEG Pti19_3_2, deprecated (SIRI 2.1) - + - TPEG Pti_19_26 overhead obstruction. + TPEG Pti19_3_6, deprecated (SIRI 2.1) - + - TPEG Pti_19_255 undefined problem. + TPEG Pti19_3_7, deprecated (SIRI 2.1) - + - 19:15_1 problemsAtBorderPost - alias to TPEG Pti_19_15 congestion. + TPEG Pti19_3_8, deprecated (SIRI 2.1) - + - 19:15_2 problemsAtCustomsPost alias to TPEG Pti_19_15 congestion. + TPEG Pti19_3_9, deprecated (SIRI 2.1) - + - 19:15_3 problemsOnLocalRoad alias to TPEG Pti_19_15 congestion. + TPEG Pti19_3_10, deprecated (SIRI 2.1) - + - 19:255_1 speedRestrictions alias to TPEG Pti_19_15 unknown + TPEG Pti19_3_13, deprecated (SIRI 2.1) - - - 19:255_2 logisticProblems alias to TPEG Pti_19_15 unknown - - - - - - - - - - - - - - - - - - - - - - - - - - TPEG Pti18_2/TPEG Pti_20 personnel event reason. - - - - - Values for Personnel incident reason types TPEG Pti18_2/TPEG Pti_20. - - - - + - TPEG Pti20_0 unknown. + TPEG Pti19_3_16, deprecated (SIRI 2.1) - - + - TPEG Pti20_1 staff sickness. + TPEG Pti19_4_1, deprecated (SIRI 2.1) - - + - staff injury alias to TPEG Pti20_1 staff sickness. + TPEG Pti19_5_1, deprecated (SIRI 2.1) - - + - contractor staff injury alias to TPEG Pti20_1 staff sickness. + TPEG Pti19_5_2, deprecated (SIRI 2.1) - - + - TPEG Pti20_2 staff absence. + TPEG Pti19_5_3, deprecated (SIRI 2.1) - - + - TPEG Pti20_3 staff in wrong place. + TPEG Pti19_5_4, deprecated (SIRI 2.1) - - + - TPEG Pti20_4 staff shortage. + TPEG Pti19_5_5, deprecated (SIRI 2.1) - - + - TPEG Pti20_5 industrial action. + TPEG Pti19_6_1, deprecated (SIRI 2.1) - - + - Unofffical action - alias to TPEG Pti20_5 industrial action. + TPEG Pti19_6_2, deprecated (SIRI 2.1) - - + - TPEG Pti20_6 work to rule. + TPEG Pti19_6_3, deprecated (SIRI 2.1) - replaced by Pts38_79, person hit by vehicle - - + - TPEG Pti20_255 undefined personnel problem. + TPEG Pti19_6_4, deprecated (SIRI 2.1) - - - - - Additional refinements TPEG Personnelevent reason. - - - - - Values for Personnel incident sub reason types. - - - - + - TPEG Pti20_0 unknown. + TPEG Pti19_6_5, deprecated (SIRI 2.1) - replaced by Pts38_14, emergency medical services - - + - contractor staff injury alias to TPEG Pti20_1 staff sickness. + TPEG Pti19_8, deprecated (SIRI 2.1) - + - TPEG Pti20_2 staff absence. + TPEG Pti19_10, deprecated (SIRI 2.1) - + - TPEG Pti20_3 staff in wrong place. + TPEG Pti19_11, deprecated (SIRI 2.1) - + - TPEG Pti20_4 staff shortage. + TPEG Pti19_14, deprecated (SIRI 2.1) - + - TPEG Pti20_5 industrial action. + TPEG Pti19_15_1, deprecated (SIRI 2.1) - replaced by Pts38_23, border control - - + - TPEG Pti20_6 work to rule. + TPEG Pti19_15_2, deprecated (SIRI 2.1) - + - TPEG Pti20_255 undefined personnel problem. + TPEG Pti19_18_1, deprecated (SIRI 2.1) - replaced by Pts38_64, level crossing blocked - - - - - - 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 Pti19_19_3, deprecated (SIRI 2.1) - replaced by Pts38_81, vehicle struck animal - - + - TPEG Pti21_1 points problem. + TPEG Pti19_19_4, deprecated (SIRI 2.1) - replaced by Pts38_80, vehicle struck object - - + - TPEG Pti21_2 points failure. + TPEG Pti19_23_2, deprecated (SIRI 2.1) - - + - TPEG Pti21_3 signal problem. + TPEG Pti19_23_3, deprecated (SIRI 2.1) - - + - Train warning system eg TPWSAlias to TPEG Pti21_3 signal problem. + TPEG Pti19_23_4, deprecated (SIRI 2.1) - - + - Track circuit alias to TPEG Pti21_3 signal problem. + TPEG Pti19_24_1, deprecated (SIRI 2.1) - - + - TPEG Pti21_4 signal failure. + TPEG Pti19_24_5, deprecated (SIRI 2.1) - - + - TPEG Pti21_4 signal failure. + TPEG Pti19_24_6, deprecated (SIRI 2.1) - - + - TPEG Pti21_5 derailment. + TPEG Pti19_24_7, deprecated (SIRI 2.1) - - + - TPEG Pti21_6 engine failure. + TPEG Pti19_25, deprecated (SIRI 2.1) - replaced by Pts38_68, bridge damage - - + - traction failure alais to TPEG Pti21_6 engine failure. + TPEG Pti19_25_1, deprecated (SIRI 2.1) - - + - defective train alais to TPEG Pti21_6 engine failure. + TPEG Pti19_26, deprecated (SIRI 2.1) - - + - TPEG Pti21_7 break down. + TPEG Pti19_255, deprecated (SIRI 2.1) - - + - TPEG Pti21_8 technical problem. + TPEG Pti19_255_1, deprecated (SIRI 2.1) - - + - Broken rail - alias to TPEG Pti21_8 technical problem. + TPEG Pti19_255_2, deprecated (SIRI 2.1) - - + - poor rail conditions - alias to TPEG Pti21_8 technical problem. + TPEG Pti19_255, deprecated (SIRI 2.1) - replaced by Pts38_255, undefined alert cause - - + - Wheel Impact Load detectedi by trackside equipment alias to TPEG Pti21_8 technical problem. + TPEG Pti20_1_1, deprecated (SIRI 2.1) - - + - late lack of operational stock - alias to TPEG Pti21_8 technical problem. + TPEG Pti20_1_2, deprecated (SIRI 2.1) - - + - defective fire alarm equipment - alias to TPEG Pti21_8 technical problem. + TPEG Pti20_3, deprecated (SIRI 2.1) - - + - defective PEDs (platform edge doors) - alias to TPEG Pti21_8 technical problem. + TPEG Pti20_4, deprecated (SIRI 2.1) - - + - defective CCTV - alias to TPEG Pti21_8 technical problem. + TPEG Pti20_5_1, deprecated (SIRI 2.1) - - + - defective PA - alias to TPEG Pti21_8 technical problem. + TPEG Pti20_6, deprecated (SIRI 2.1) - - + - ticketing facility unavailable - alias to TPEG Pti21_8 technical problem. + TPEG Pti20_255, deprecated (SIRI 2.1) - replaced by Pts38_255, undefined alert cause - - + - ticketing facility unavailable - alias to TPEG Pti21_8 technical problem. + TPEG Pti21_3_1, deprecated (SIRI 2.1) - - + - traffic management system failure - alias to TPEG Pti21_8 technical problem. + TPEG Pti21_4_1, deprecated (SIRI 2.1) - - + - TPEG Pti21_9 repair work. + TPEG Pti21_6_1, deprecated (SIRI 2.1) - - + - TPEG Pti21_10 construction work. + TPEG Pti21_6_2, deprecated (SIRI 2.1) - replaced by Pts38_53, defective vehicle - - + - TPEG Pti21_11 maintenance work. + TPEG Pti21_8_3, deprecated (SIRI 2.1) - - + - emergency engineering work - alias to TPEG Pti21_11 maintenance work. + TPEG Pti21_8_4, deprecated (SIRI 2.1) - - + - late finish to engineering work - alias to TPEG Pti21_11 maintenance work. + TPEG Pti21_8_5, deprecated (SIRI 2.1) - - + - TPEG Pti21_12 power problem. + TPEG Pti21_8_6, deprecated (SIRI 2.1) - - + - TPEG Pti21_12 power problem. + TPEG Pti21_8_7, deprecated (SIRI 2.1) - - + - TPEG Pti21_13 fuel problem. + TPEG Pti21_8_8, deprecated (SIRI 2.1) - - + - TPEG Pti21_14 swing bridge failure. + TPEG Pti21_8_9, deprecated (SIRI 2.1) - - + - TPEG Pti21_15 escalator failure. + TPEG Pti21_11_1, deprecated (SIRI 2.1) - - + - TPEG Pti21_16 lift failure. + TPEG Pti21_11_2, deprecated (SIRI 2.1) - - + - TPEG Pti21_17 gangway problem. + TPEG Pti21_13, deprecated (SIRI 2.1) - - TPEG Pti21_18 closed for maintenance. + TPEG Pti21_18, deprecated (SIRI 2.1) - - TPEG Pti21_19 fuel shortage. - - - - - - TPEG Pti21_20 de-icing work. - - - - - - TPEG Pti21_21 wheel problem. + TPEG Pti21_19, deprecated (SIRI 2.1) - - TPEG Pti21_21 wheel problem. + TPEG Pti21_21_1, deprecated (SIRI 2.1) - - TPEG Pti21_22 luggage carousel problem. + TPEG Pti21_22, deprecated (SIRI 2.1) - - TPEG Pti21_255 undefined equipment problem. - - - - - - - Additional refinements TPEG Equipment event reason. - - - - - Values for Equipment incident sub reason types. - - - - - TPEG Pti21_0 unknown. - - - - - TPEG Pti21_1 points problem. - - - - - TPEG Pti21_2 points failure. - - - - - TPEG Pti21_3 signal problem. - - - - - Train warning system eg TPWS Alias to TPEG Pti21_3 signal problem. - - - - - Track circuit alias to TPEG Pti21_3 signal problem. - - - - - TPEG Pti21_4 signal failure. - - - - - TPEG Pti21_4 signal failure. - - - - - TPEG Pti21_5 derailment. + TPEG Pti21_255, deprecated (SIRI 2.1) - replaced by Pts38_255, undefined alert cause - + - TPEG Pti21_6 engine failure. + TPEG Pti22_5_1, deprecated (SIRI 2.1) - + - traction failure alais to TPEG Pti21_6 engine failure. + TPEG Pti22_6, deprecated (SIRI 2.1) - + - defective train alais to TPEG Pti21_6 engine failure. + TPEG Pti22_9_1, deprecated (SIRI 2.1) - + - TPEG Pti21_7 break down. + TPEG Pti22_9_3, deprecated (SIRI 2.1) - + - TPEG Pti21_8 technical problem. + TPEG Pti22_10, deprecated (SIRI 2.1) - + - Broken rail - alias to TPEG Pti21_8 technical problem. + TPEG Pti22_11_1, deprecated (SIRI 2.1) - + - poor rail conditions - alias to TPEG Pti21_8 technical problem. + TPEG Pti22_14, deprecated (SIRI 2.1) - + - Wheel Impact Load detectedi by trackside equipment alias to TPEG Pti21_8 technical problem. + TPEG Pti22_255_2, deprecated (SIRI 2.1) - + - late lack of operational stock - alias to TPEG Pti21_8 technical problem. - - - - - defective fire alarm equipment - alias to TPEG Pti21_8 technical problem. - - - - - defective PEDs (platform edge doors) - alias to TPEG Pti21_8 technical problem. - - - - - defective CCTV - alias to TPEG Pti21_8 technical problem. - - - - - defective PA - alias to TPEG Pti21_8 technical problem. - - - - - ticketing facility unavailable - alias to TPEG Pti21_8 technical problem. - - - - - ticketing facility unavailable - alias to TPEG Pti21_8 technical problem. - - - - - traffic management system failure - alias to TPEG Pti21_8 technical problem. - - - - - TPEG Pti21_9 repair work. - - - - - TPEG Pti21_10 construction work. - - - - - TPEG Pti21_11 maintenance work. - - - - - emergency engineering work - alias to TPEG Pti21_11 maintenance work. - - - - - late finish to engineering work - alias to TPEG Pti21_11 maintenance work. - - - - - TPEG Pti21_12 power problem. - - - - - TPEG Pti21_12 power problem. - - - - - TPEG Pti21_13 fuel problem. - - - - - TPEG Pti21_14 swing bridge failure. - - - - - TPEG Pti21_15 escalator failure. - - - - - TPEG Pti21_16 lift failure. - - - - - TPEG Pti21_17 gangway problem. - - - - - TPEG Pti21_18 closed for maintenance. - - - - - TPEG Pti21_19 fuel shortage. - - - - - TPEG Pti21_20 de-icing work. - - - - - TPEG Pti21_21 wheel problem. - - - - - TPEG Pti21_21 wheel problem. - - - - - TPEG Pti21_22 luggage carousel problem. - - - - - TPEG Pti21_255 undefined equipment problem. + TPEG Pti22_255, deprecated (SIRI 2.1) - replaced by Pts38_255, undefined alert cause - - + + - TPEG Pti18_4/TPEG Pti_22 environment event reason. + Deprecated (TPEG Pti19 - Miscellaneous Event Reason) - + - Values for Environment incident reason types TPEG Pti18_4/TPEG Pti_22. + Deprecated (TPEG Pti19 - Miscellaneous Event Reason) - - - - - TPEG Pti22_0 unknown. - - - - - - TPEG Pti22_1 fog. - - - - - - TPEG Pti22_2 rough sea. - - - - - - TPEG Pti22_3 heavy snow fall. - - - - - - drifting snow - Alias to TPEG Pti22_3 heavySnowFall. - - - - - - Blizzard Conditions - Alias to TPEG Pti22_3 heavySnowFall. - - - - - - TPEG Pti22_4 heavy rain. - - - - - - TPEG Pti22_5 strong winds. - - - - - - stormConditions alias to TPEG Pti22_5 strong winds. - - - - - - storm damage alias to TPEG Pti22_5 strong winds. - - - - - - TPEG Pti22_6 tidal restrictions. - - - - - - TPEG Pti22_7 high tide. - - - - - - TPEG Pti22_8 low tide. - - - - - - TPEG Pti22_9 ice. - - - - - - TPEG Pti22_9 ice. - - - - - - TPEG Pti22_9 ice. - - - - - - TPEG Pti22_9 ice. - - - - - - TPEG Pti22_10 frozen. - - - - - - TPEG Pti22_11 hail. - - - - - - Sleet Alias to TPEG Pti22_11 hail. - - - - - - TPEG Pti22_12 high temperatures. - - - - - - TPEG Pti22_13 flooding. - - - - - - flash floods alias to 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. - - - - - - mudslide alias to TPEG Pti22_19 landslide. - - - - - - rockfalls alias to TPEG Pti22_19 landslide. - - - - - - subsidence alias to TPEG Pti22_19 landslide. - - - - - - earthquake damage alias to TPEG Pti22_19 landslide. - - - - - - TPEG Pti22_255 undefined environmental problem. - - - - - - lightningStrike alias to TPEG Pti22_255 undefined environmental problem. - - - - - - - - - + + - Additional refinements TPEG Environmentevent reason. + Deprecated (TPEG Pti20 - Personnel Event Reason) - + - Values for Environment incident subreason types. + Deprecated (TPEG Pti20 - Personnel Event Reason) - - - - 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. - - - - - avalanches - Alias to TPEG Pti22_3 heavySnowFall. - - - - - TPEG Pti22_4 heavy rain. - - - - - TPEG Pti22_5 strong winds. - - - - - storm conditions - 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. - - - - - slipperiness - Alias to TPEG Pti22_9 ice. - - - - - ice drift - Alias to TPEG Pti22_9 ice. - - - - - glazed frost - Alias to 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. - - - - - flash floods - Alias to 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. - - - - - mudslide - Alias to TPEG Pti22_19 landslide. - - - - - rockfalls - Alias to TPEG Pti22_19 landslide. - - - - - subsidence - Alias to TPEG Pti22_19 landslide. - - - - - earthquake damage - Alias to TPEG Pti22_19 landslide. - - - - - TPEG Pti22_255 undefined environmental problem. - - - - - lightning strike - Alias to TPEG Pti22_255 undefined environmental problem. - - - - - sewer overflow - Alias to TPEG Pti22_255 undefined environmental problem. - - - - - grass fire - Alias to TPEG Pti22_255 undefined environmental problem. - - - - - - + + + + Deprecated (TPEG Pti21 - Equipment Event Reason) + + + + + Deprecated (TPEG Pti21 - Equipment Event Reason) + + + + + Deprecated (TPEG Pti22 - Environment Event Reason) + + + - TPEG Pti18_255/TPEG Pti_22 undefined event reason. + Deprecated (TPEG Pti22 - Environment Event Reason) - diff --git a/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd b/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd index f3c5c463..90cc6f0f 100644 --- a/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd +++ b/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd @@ -7,7 +7,7 @@ e-service developers Add names Europe - >Drafted for version 1.0 Kizoom Incident Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk + Drafted for version 1.0 Kizoom Incident Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk 2004-09-29 @@ -17,12 +17,21 @@ 2007-05-14 - 2007-05-14 - [vdv] ReportTypeEnumeration TPEC-code "2_27_1_Alias_2" changed to "27_1_Alias_2" according to recommendation document + + 2007-05-14 + + + + 2020-01-10 + + -

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

+

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

 text/xml @@ -31,37 +40,28 @@ {http://www.siri.org.uk/standards/siri/schema/2.0/xsd/siri_model/}siri_situationServiceTypes-v1.0.xsd [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD + CEN - Unclassified - - Kizoom 2000-2007, CEN 2009-2012 - + Kizoom 2000-2007, CEN 2009-2020 +
  • Schema derived Derived from the Kizoom XTIS schema
    • -
  • Derived from the TPEG Categories schema
    • +
  • Derived from the TPEG2 PTS schemas
- Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, - Air transport, Airports, - Ports and maritime transport, Ferries (marine), - Public transport, Bus services, Coach services, Bus stops and stations, - Rail transport, Railway stations and track, Train services, Underground trains, - Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, - Rail transport, Roads and road transport - - + CEN TC278 WG3 SG7 Xml Schema for PT Incidents. Service subschema @@ -70,247 +70,485 @@ Rail transport, Roads and road transport - + - Scope of incident - Tpeg Report Type pti27. + Scope of incident - TPEG Pti27 ReportType - Values for Report Type TPEG pti_table 27. + Values for TPEG Pti27 - ReportType - - - - - - - - - - - - - - - - - - - - - - - - + + + TPEG Pti27_0, unknown + + + + + TPEG Pti27_1, incident + + + + + TPEG Pti27_1_1, general + + + + + TPEG Pti27_1_2, operator + + + + + TPEG Pti27_1_3, network + + + + + TPEG Pti27_2, station terminal + + + + + TPEG Pti27_2_1, stoppoint + + + + + TPEG Pti27_2_2, connection link + + + + + TPEG Pti27_2_3, point + + + + + TPEG Pti27_3, route + + + + + TPEG Pti27_4, individual service + + + + + TPEG Pti27_255, undefined type + + - Status of a SERVICE JOURNEY INTERCHANGE Status TPEG cross reference pti31. + Status of a SERVICE JOURNEY INTERCHANGE - TPEG Pti31 InterchangeStatus - Values for Interchange Status TPEG cross reference pti_table 31. + Values for TPEG Pti31 - InterchangeStatus - - - - - - - - - - - - - - - - + + + TPEG Pti31_0, unknown + + + + + TPEG Pti31_1, connection + + + + + TPEG Pti31_2, replacement + + + + + TPEG Pti31_3, alternative + + + + + TPEG Pti31_4, connection not held + + + + + TPEG Pti31_5, connection held + + + + + TPEG Pti31_6, status of connection undecided + + + + + TPEG Pti31_255, undefined cross reference information + + + + + deprecated (SIRI 2.1) - use statusOfConnectionUndecided + + - Ticket restrictions - Tpeg Report Type pti25. + Ticket restrictions - TPEG Pti025 - Values for TicketRestrictionTypeTPEG pti_table 25. + Values for TPEG Pti025 - TicketRestrictionType - - - - - - - - - - - - - - - - - - - - - - - - + + + TPEG Pti25_0, unknown + + + + + TPEG Pti25_1, all ticket classes valid + + + + + TPEG Pti25_2, full fare only + + + + + TPEG Pti25_3, certain tickets only + + + + + TPEG Pti25_4, ticket with reservation + + + + + TPEG Pti25_5, special fare + + + + + TPEG Pti25_6, only tickets of specified operator + + + + + TPEG Pti25_7, no restrictions + + + + + TPEG Pti25_8, no off-peak tickets + + + + + TPEG Pti25_9, no weekend return tickets + + + + + TPEG Pti25_10, no reduced fare tickets + + + + + TPEG Pti25_255, unknown ticket restriction + + - Booking Status - Tpeg Report Type pti24. + Booking Status - TPEG Pti024. - Values for TBookingStatus TPEG pti_table 24. + Values for Values for TPEG Pti024 - BookingStatus - - - - - - - - - - - - - - - - - - - - + + + TPEG Pti24_0, unknown + + + + + TPEG Pti24_1, available + + + + + TPEG Pti24_2, limited + + + + + TPEG Pti24_3, very limited + + + + + TPEG Pti24_4, full + + + + + TPEG Pti24_5, waiting list + + + + + TPEG Pti24_6, no booking required + + + + + TPEG Pti24_7, booking is required + + + + + TPEG Pti24_8, booking is optional + + + + + TPEG Pti24_255, undefined booking information + + - STOP POINT type Tpeg Report Type pti17. + STOP POINT type - TPEG Pts017, ServiceDeliveryPointType - Values for TBookingStatus TPEG pti_table17. + Values for TPEG Pts017 - ServiceDeliveryPointType - - - - - - - - - - - - - - - - + + + TPEG Pts17_0, unknown + + + + + TPEG Pts17_1, platform number + + + + + TPEG Pts17_2, terminal gate + + + + + TPEG Pts17_3, ferry berth + + + + + TPEG Pts17_4, harbour pier + + + + + TPEG Pts17_5, unknown + + + + + TPEG Pts17_6, bus stop + + + + + TPEG Pts17_255, undefined service delivery point type + + + + + deprecated (SIRI 2.1) - use undefinedStopPointType + + - Route point type Tpeg Report Type pti15. + ROUTE POINT type - TPEG Pti015 - route_point_type TPEG pti_table15. + Values for TPEG Pti015 - RoutePointType - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + TPEG Pti15_0, unknown + + + + + TPEG Pti15_1, start point + + + + + TPEG Pti15_2, destination + + + + + TPEG Pti15_3, stop + + + + + TPEG Pti15_4, via + + + + + TPEG Pti15_5, not-stopping + + + + + TPEG Pti15_6, temporary stop + + + + + TPEG Pti15_7, temporarily not-stopping + + + + + TPEG Pti15_8, exceptional stop + + + + + TPEG Pti15_9, additional stop + + + + + TPEG Pti15_10, request stop + + + + + TPEG Pti15_11, front train destination + + + + + TPEG Pti15_12, rear train destination + + + + + TPEG Pti15_13, through service destination + + + + + TPEG Pti15_14, not via + + + + + TPEG Pti15_15, altered start point + + + + + TPEG Pti15_16, altered destination + + + + + TPEG Pti15_255, undefined route point + + - Timetable type - Tpeg pti33. + Timetable type - TPEG Pti033. - Values for timetable type TPEG pti_table 33. + Values for TPEG Pti033 - TimetableType - - - - - - - - - - - - - - - - + + + TPEG Pti33_0, unknown + + + + + TPEG Pti33_1, winter + + + + + TPEG Pti33_2, spring + + + + + TPEG Pti33_3, summer + + + + + TPEG Pti33_4, autumn + + + + + TPEG Pti33_5, special + + + + + TPEG Pti33_6, emergency + + + + + TPEG Pti33_255, undefined timetable type + + diff --git a/xsd/siri_model/siri_time-v2.0.xsd b/xsd/siri_model/siri_time-v2.0.xsd index 260e2508..1255b857 100644 --- a/xsd/siri_model/siri_time-v2.0.xsd +++ b/xsd/siri_model/siri_time-v2.0.xsd @@ -19,13 +19,22 @@ 2007-03-29 - 2008-11-10 - refine day types - - 2014-06-20 - * [se] Add end time precision to halfopen time rangefor input a siri_time-v2.0.xsd. - * [se] Add end time status to halfopen time range output siri_time-v2.0.xsd. - + + 2008-11-10 + + + + 2014-06-20 + + + + 2020-01-24 + +

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

 @@ -34,19 +43,18 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_time-v1.2.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_time-v2.0.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified - - CEN, VDV, RTIG 2004-2012 - + CEN, VDV, RTIG 2004-2020 +
  • Derived from the VDV, RTIG CML and Trident standards.
- Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -189,63 +197,129 @@ Rail transport, Roads and road transport - Tpeg DAY TYPE pti_table 34 + Day on which a SITUATION may apply - TPEG Pti34 DayType - Values for Day Type TPEG pti_table 34 + Values for TPEG Pti34 - DayType - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + TPEG Pti34_0, unknown + + + + + TPEG Pti34_1, Monday + + + + + TPEG Pti34_2, Tuesday + + + + + TPEG Pti34_3, Wednesday + + + + + TPEG Pti34_4, Thusrday + + + + + TPEG Pti34_5, Friday + + + + + TPEG Pti34_6, Saturday + + + + + TPEG Pti34_7, Sunday + + + + + TPEG Pti34_8, weekdays + + + + + TPEG Pti34_9, weekends + + + + + TPEG Pti34_10, holiday + + + + + TPEG Pti34_11, public holiday + + + + + TPEG Pti34_12, religious holiday + + + + + TPEG Pti34_13, federal holiday + + + + + TPEG Pti34_14, regional holiday + + + + + TPEG Pti34_15, national holiday + + + + + TPEG Pti34_16, Monday to Friday + + + + + TPEG Pti34_17, Monday to Saturday + + + + + TPEG Pti34_18, Sundays and public holidays + + + + + TPEG Pti34_19, school days + + + + + TPEG Pti34_20, every day + + + + + TPEG Pti34_255, undefined day type + + - Values for Day Type TPEG pti_table 34 + Subset of TPEG Pti34 - DayType @@ -264,7 +338,7 @@ Rail transport, Roads and road transport - Values for Day Type TPEG pti_table 34 + Subset of TPEG Pti34 - DayType From ded68cdd2d976b779481616b22ce22c139217977 Mon Sep 17 00:00:00 2001 From: "Willering HW (Henno)" Date: Wed, 29 Jan 2020 12:43:47 +0100 Subject: [PATCH 077/290] Update siri_situationAffects-v2.0.xsd --- xsd/siri_model/siri_situationAffects-v2.0.xsd | 114 ++++++++++++++++-- 1 file changed, 106 insertions(+), 8 deletions(-) diff --git a/xsd/siri_model/siri_situationAffects-v2.0.xsd b/xsd/siri_model/siri_situationAffects-v2.0.xsd index 9ef12c3a..ac9344c4 100644 --- a/xsd/siri_model/siri_situationAffects-v2.0.xsd +++ b/xsd/siri_model/siri_situationAffects-v2.0.xsd @@ -59,9 +59,10 @@ --> - 2020-01-28 + 2020-01-29 @@ -76,7 +77,7 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_situationServiceTypes-v1.2.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modes-v1.1.xsd http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey-v2.0.xsd @@ -109,7 +110,7 @@ Rail transport, Roads and road transport - Type for an SCHEDUELD STOP POINT affected by a SITUATION. + Type for an SCHEDULED STOP POINT affected by a SITUATION. @@ -120,7 +121,7 @@ Rail transport, Roads and road transport - Name of SCHEDULED STOP POIHT. (Unbounded since SIRI 2.0) + Name of SCHEDULED STOP POINT. (Unbounded since SIRI 2.0) @@ -140,7 +141,7 @@ Rail transport, Roads and road transport - Refernce to a SITE or TOPOGRAPHIC PLACE affected by the Locality of stop (In UK NPtg Locality Code). Derivable from StopRef. + Reference to a SITE or TOPOGRAPHIC PLACE affected by the Locality of stop (In UK NPtg Locality Code). Derivable from StopRef. @@ -150,7 +151,7 @@ Rail transport, Roads and road transport - Assesment of current ACCESSIBILITY of the STOP POINT as affected by the SITUATION. + Assessment of current ACCESSIBILITY of the STOP POINT as affected by the SITUATION. @@ -288,7 +289,7 @@ Rail transport, Roads and road transport Description of Link. (Unbounded since SIRI 2.0) - + Nature of CONNECTION link. @@ -1301,5 +1302,102 @@ Rail transport, Roads and road transport + + + Values for AccessibilityFeature - TPEG Pts040 and IFOPT + + + + + IFOPT, TPEG Pts40_0, unknown + + + + + TPEG Pts40_1, single step + + + + + IFOPT, TPEG Pts40_2, stairs + + + + + IFOPT, TPEG Pts40_3, escalator + + + + + IFOPT, TPEG Pts40_4, travelator / moving walkway + + + + + IFOPT, TPEG Pts40_5, lift / elevator + + + + + IFOPT, TPEG Pts40_6, ramp + + + + + TPEG Pts40_7, mind the gap + + + + + TPEG Pts40_8, tactile paving + + + + + IFOPT, series of stairs + + + + + IFOPT, shuttle + + + + + IFOPT, barrier + + + + + IFOPT, narrow entrance + + + + + IFOPT, confined space + + + + + IFOPT, queue management + + + + + IFOPT, none + + + + + IFOPT, other + + + + + TPEG Pts40_255, undefined accessibility feature type + + + + From 80cd1ebb8f6e4cf4cbae914bbcf6e450c8a40575 Mon Sep 17 00:00:00 2001 From: "Willering HW (Henno)" Date: Wed, 29 Jan 2020 14:11:16 +0100 Subject: [PATCH 078/290] examples and bug in siri_reference-v2.0.xsd --- examples/siri_exm_SX/exx_situationExchangeResponse.xml | 8 ++++---- examples/siri_exm_SX/exx_situationExchange_ATOC.xml | 6 +++--- examples/siri_exm_SX/exx_situationExchange_Pt.xml | 2 +- examples/siri_exm_SX/exx_situationExchange_response.xml | 8 ++++---- examples/siri_exm_SX/exx_situationExchange_road.xml | 2 +- xsd/siri_model/siri_reference-v2.0.xsd | 1 + 6 files changed, 14 insertions(+), 13 deletions(-) diff --git a/examples/siri_exm_SX/exx_situationExchangeResponse.xml b/examples/siri_exm_SX/exx_situationExchangeResponse.xml index f7dafe95..1ceed531 100644 --- a/examples/siri_exm_SX/exx_situationExchangeResponse.xml +++ b/examples/siri_exm_SX/exx_situationExchangeResponse.xml @@ -50,7 +50,7 @@ BAAR0003 Barchester Station - pti17_0 + unknown -180 -90 @@ -75,8 +75,8 @@ 2001-12-17T09:30:47.0Z - pti13_0 - pti26_0 + unknown + unknown true true @@ -144,7 +144,7 @@ BAAR0003 Barchester Station - pti17_0 + unknown -180 -90 diff --git a/examples/siri_exm_SX/exx_situationExchange_ATOC.xml b/examples/siri_exm_SX/exx_situationExchange_ATOC.xml index dbd63c82..f73ea239 100644 --- a/examples/siri_exm_SX/exx_situationExchange_ATOC.xml +++ b/examples/siri_exm_SX/exx_situationExchange_ATOC.xml @@ -30,7 +30,7 @@ public point Bomb at Barchester station - Building evacuated. AVoid station untile furtehr notice + Building evacuated. AVoid station untile further notice @@ -39,7 +39,7 @@ BAAR0003 Barchester Station - pti17_0 + unknown -180 -90 @@ -53,7 +53,7 @@ BAR00021 - Platfrom 3 + Platform 3 diff --git a/examples/siri_exm_SX/exx_situationExchange_Pt.xml b/examples/siri_exm_SX/exx_situationExchange_Pt.xml index dbd63c82..7732c3d3 100644 --- a/examples/siri_exm_SX/exx_situationExchange_Pt.xml +++ b/examples/siri_exm_SX/exx_situationExchange_Pt.xml @@ -39,7 +39,7 @@ BAAR0003 Barchester Station - pti17_0 + unknown -180 -90 diff --git a/examples/siri_exm_SX/exx_situationExchange_response.xml b/examples/siri_exm_SX/exx_situationExchange_response.xml index add226ce..570b3653 100644 --- a/examples/siri_exm_SX/exx_situationExchange_response.xml +++ b/examples/siri_exm_SX/exx_situationExchange_response.xml @@ -50,7 +50,7 @@ BAAR0003 Barchester Station - pti17_0 + unknown -180 -90 @@ -75,8 +75,8 @@ 2001-12-17T09:30:47.0Z - pti13_0 - pti26_0 + unknown + unknown true true @@ -144,7 +144,7 @@ BAAR0003 Barchester Station - pti17_0 + unknown -180 -90 diff --git a/examples/siri_exm_SX/exx_situationExchange_road.xml b/examples/siri_exm_SX/exx_situationExchange_road.xml index f48c5b6f..310218a5 100644 --- a/examples/siri_exm_SX/exx_situationExchange_road.xml +++ b/examples/siri_exm_SX/exx_situationExchange_road.xml @@ -39,7 +39,7 @@ BAAR0003 Barchester Station - pti17_0 + unknown -180 -90 diff --git a/xsd/siri_model/siri_reference-v2.0.xsd b/xsd/siri_model/siri_reference-v2.0.xsd index fcca935e..2bd02145 100644 --- a/xsd/siri_model/siri_reference-v2.0.xsd +++ b/xsd/siri_model/siri_reference-v2.0.xsd @@ -54,6 +54,7 @@ [vdv] "DestinationName" inside "PublishedLineGroup" changed to "unbounded" to allow multiple definitions for different languages due to the xml:lang-Attribute --> + 2020-01-29 @@ -19,3 +19,5 @@ + + \ No newline at end of file From 4d27580251012b30ca3b930d9cc02b1132e20f0b Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 11 Feb 2020 12:08:19 +0100 Subject: [PATCH 081/290] CR029: add new element xxxPredictionUnknown --- xsd/siri_model/siri_journey-v2.0.xsd | 82 +++++++++++++++++++--------- 1 file changed, 56 insertions(+), 26 deletions(-) diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index b95675a7..6fcc53d9 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -593,12 +593,27 @@ Rail transport, Roads and road transport - - - - Prediction quality, either as approximate level, or more quantitayive percentile range of predictions will fall within a given range of times. +SIRI v2.0 - - + + + + + + Prediction quality, either as approximate level, or more quantitative percentile range of predictions that will fall within a given range of times. +SIRI v2.0 + + + + + + If the producer is (temporarily) not able to deliver real-time predictions (e.g. because of a connection loss), he has various options to inform the consumer: +(i) set Monitored to 'false' +(ii) transmit ExpectedTime together with "PredictionInaccurate=true" +(iii) drop/omit ExpectedTimes +(iv) set ArrivalStatus to 'noReport' +However, option (iii) might introduce ambiguity: one consumer might interpret it as "on time" and another one as "indefinite delay". +To avoid this, the producer should transmit xxxPredictionUnknown instead of any ExpectedTimes. +SIRI v2.1 + + + @@ -611,26 +626,41 @@ Rail transport, Roads and road transport Target departure time of VEHICLE according to latest working timetable. - - - Estimated time of departure of VEHICLE, most likely taking into account all control actions such as waiting. - - - - - Expected departure time of VEHICLE without waiting time due to operational actions. For people at stop this would normally be shown if different from Expected departure time. So if servcie decides not to wait may leave earler than expected departure time +SIRI v2.0. - - - - - Earliest time at which VEHICLE may leave the stop. Used to secure connections. Used for passenger announcements. Passengers must be at boarding point by this time to be sure of catching VEHICLE. i.e. "Vehicle will not leave before this time" - may be revised from original aimed time. +SIRI v2.0 - - - - - Prediction quality, either as approximate level, or more quantitayive percentile range of predictions will fall within a given range of times. +SIRI v2.0 - - + + + + + Estimated time of departure of VEHICLE, most likely taking into account all control actions such as waiting. + + + + + Expected departure time of VEHICLE without waiting time due to operational actions. For people at stop this would normally be shown if different from Expected departure time. So if servcie decides not to wait may leave earler than expected departure time +SIRI v2.0. + + + + + Earliest time at which VEHICLE may leave the stop. Used to secure connections. Used for passenger announcements. Passengers must be at boarding point by this time to be sure of catching VEHICLE. i.e. "Vehicle will not leave before this time" - may be revised from original aimed time. +SIRI v2.0 + + + + + Prediction quality, either as approximate level, or more quantitative percentile range of predictions that will fall within a given range of times. +SIRI v2.0 + + + + + + If the producer is (temporarily) not able to deliver real-time predictions (e.g. because of a connection loss), he has various options to inform the consumer: +(i) set Monitored to 'false' +(ii) transmit ExpectedTime together with "PredictionInaccurate=true" +(iii) drop/omit ExpectedTimes +(iv) set ArrivalStatus to 'noReport' +However, option (iii) might introduce ambiguity: one consumer might interpret it as "on time" and another one as "indefinite delay". +To avoid this, the producer should transmit xxxPredictionUnknown instead of any ExpectedTimes. +SIRI v2.1 + + + From e777f95d107ccfe1bce8065bd096f937ca3cd558 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 11 Feb 2020 16:12:40 +0100 Subject: [PATCH 082/290] CR050: fix choice error (move outer indirect ref) --- .../siri_estimatedVehicleJourney-v2.0.xsd | 26 ++++++++++--------- 1 file changed, 14 insertions(+), 12 deletions(-) diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index 38fa4c9b..8fac7582 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -107,22 +107,24 @@ Rail transport, Roads and road transport - If no VEHICLE JOURNEY reference is available, identify it by origin and destination and the scheduled times at these stops. + Additionally, identify the VEHICLE JOURNEY by origin and destination and the scheduled times at these stops. + + + + + + + Reference to a dated VEHICLE JOURNEY. This will be 'framed' i.e. be with the data context of the ESTIMATED Timetable. +DEPRECATED from SIRI 2.0 + + + + + Additionally, identify the VEHICLE JOURNEY by origin and destination and the scheduled times at these stops. - - - Reference to a dated VEHICLE JOURNEY. This will be 'framed' i.e. be with the data context of the ESTIMATED Timetable. -DEPRECATED from SRI 2.0 - - - - - If no VEHICLE JOURNEY reference is available, identify it by origin and destination and the scheduled times at these stops. - - If this is the first message for an unplanned 'extra' VEHICLE JOURNEY, a new and unique code must be given for it. ExtraJourney should be set to 'true'. From 855efcdf4ce36b0b410ca583130311ba96a04601 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 11 Feb 2020 18:22:49 +0100 Subject: [PATCH 083/290] CR050: clean-up of EstimatedTimetableAlterationGrp --- .../siri_estimatedVehicleJourney-v2.0.xsd | 25 +++++++------------ 1 file changed, 9 insertions(+), 16 deletions(-) diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index 8fac7582..b1bbcfb1 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -98,33 +98,26 @@ Rail transport, Roads and road transport - - + + Identifer of a VEHICLE JOURNEY within data Horizon of a service. - - - Additionally, identify the VEHICLE JOURNEY by origin and destination and the scheduled times at these stops. - - - - Reference to a dated VEHICLE JOURNEY. This will be 'framed' i.e. be with the data context of the ESTIMATED Timetable. DEPRECATED from SIRI 2.0 - - - Additionally, identify the VEHICLE JOURNEY by origin and destination and the scheduled times at these stops. - - - - + + + + Additionally, identify the VEHICLE JOURNEY by origin and destination and the scheduled times at these stops. + + + If this is the first message for an unplanned 'extra' VEHICLE JOURNEY, a new and unique code must be given for it. ExtraJourney should be set to 'true'. From 862491e5f4d99fa6d7b43c47b3e85074a4b86e45 Mon Sep 17 00:00:00 2001 From: Christophe Duquesne Date: Wed, 26 Feb 2020 14:08:43 +0100 Subject: [PATCH 084/290] Update siri_facility-v2.0.xsd Change Request to add counting monitoring to FacilityMonitoring (multiple usage including NewModes with available place/vehicles in Parkings). This CR aims to fulfill the need of the European regulation. See documentation in the basecamp: NewModes Dynamic CR71 v1.docx Note that this CR require also CR13 (use of TypeOfValue). --- xsd/siri_model/siri_facility-v2.0.xsd | 137 +++++++++++++++++++++++++- 1 file changed, 135 insertions(+), 2 deletions(-) diff --git a/xsd/siri_model/siri_facility-v2.0.xsd b/xsd/siri_model/siri_facility-v2.0.xsd index 6f33d2b8..fe8c833b 100644 --- a/xsd/siri_model/siri_facility-v2.0.xsd +++ b/xsd/siri_model/siri_facility-v2.0.xsd @@ -74,6 +74,7 @@ Rail transport, Roads and road transport SIRi Facility model elemenys + @@ -238,9 +239,14 @@ Rail transport, Roads and road transport + + + + + @@ -286,6 +292,71 @@ Rail transport, Roads and road transport + + + Allowed values for TypeOfCounting. + + + + + + + + + + + + + Allowed values for trend of a counting. + + + + + + + + + + + + + + + Allowed values for units of what is counted + bay: Parking bay for cars, bicycle, scooter, etc + otherSpaces: any other kind of spaces: lockers, stading spaces, toilets, etc. + devices: electronic devices (audio guide, headphones, etc.) and physical devices (walking stick, wheel chair, etc.) + vehicles: any type of vehicles (cycle, car, scooter, overboard, motorbyke, etc.) + kW (kiloWatt) or kWh (kiloWatt per hour): means that an available (ore consummed) power is measured + litres and cubeMeters: means that a volume is measured + squareMeters: means that a surface is measured + meters: means that a distance is measured + kg (kilogram): means that a mass is measured + A (Amper): means that an electric intensity is measured + C (degree Celsius): means that a temperature is measured + other: use of "other" requires the additional open ended TypeOfCountedFeature (monitoredCountingStructure) to be filled + + + + + + + + + + + + + + + + + + + + + + Descriprion of the status of a MONITORED FACILITY. @@ -327,6 +398,56 @@ Rail transport, Roads and road transport + + + Monitored counted values. + + + + + Nature of what is counted. + + + + + Unit of type for what is being counted + + + + + Open ended type or refined classification of what is counted (complement to the infomation coming from the facility type itself) + + + + + + Counted value + + + + + Value as a percentage (0.0 to 1.0) + + + + + + Trend of the count + + + + + Accuracy of the count, as a percentage (0.0 to 1.0) + + + + + Description of what is counted + + + + + @@ -344,13 +465,25 @@ Rail transport, Roads and road transport Facility affected by condition. - + + + Reference to a Facility (may refer an Equipment, Local Service, Site or Vehicle). + + Status of Facility. + + + + + + + + @@ -364,7 +497,7 @@ Rail transport, Roads and road transport - Period (duration) of the status change for the facility. + Period (duration) of the status change for the facility (validity period of the FacilityCondition). From b626887d6c7e3b83539a76c008ad639d85099d5f Mon Sep 17 00:00:00 2001 From: tim-rivett <56296031+tim-rivett@users.noreply.github.com> Date: Mon, 2 Mar 2020 12:31:27 +0000 Subject: [PATCH 085/290] Update siri_situationAffects-v2.0.xsd --- xsd/siri_model/siri_situationAffects-v2.0.xsd | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/xsd/siri_model/siri_situationAffects-v2.0.xsd b/xsd/siri_model/siri_situationAffects-v2.0.xsd index ac9344c4..7392094f 100644 --- a/xsd/siri_model/siri_situationAffects-v2.0.xsd +++ b/xsd/siri_model/siri_situationAffects-v2.0.xsd @@ -1107,7 +1107,7 @@ Rail transport, Roads and road transport - + @@ -1123,7 +1123,7 @@ Rail transport, Roads and road transport - + Reference to a Stop Place. @@ -1133,7 +1133,7 @@ Rail transport, Roads and road transport Name of component. (Unbounded since SIRI 2.0) - + Type of Component. @@ -1144,7 +1144,7 @@ Rail transport, Roads and road transport Further qualifcation of affected part of Link projection, - + Type of AccessFeature (+SIRI.20) From 4141a91b0b813adeecb309331672b0d36d3e02ec Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 4 Mar 2020 00:47:38 +0100 Subject: [PATCH 086/290] CR002: revise Capacity and flatten Assign.Structs --- xsd/siri_model/siri_journey-v2.0.xsd | 200 +++++++++++++++++++-------- 1 file changed, 144 insertions(+), 56 deletions(-) diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index 51b82e00..d7a765d9 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -469,11 +469,21 @@ Rail transport, Roads and road transport Nature of boarding and alighting allowed at stop. Default is 'Alighting'. - + Assignment of arrival of Scheduled STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure +SIRI v2.0. + + + Assignments of a TRAIN formation to a physical QUAY. +SIRI v2.1 + + + + + xxx. +SIRI v2.1 + + OPERATORs of of servcie up until arrival.. May change for departure. +SIRI v2.0. @@ -494,11 +504,21 @@ Rail transport, Roads and road transport - + Assignments of departure platfiorm for Scheduled STOP POINT to a physical QUAY. +SIRI v2.0. + + + Assignments of a TRAIN formation to a physical QUAY. +SIRI v2.1 + + + + + xxx. +SIRI v2.1 + + OPERATORs of of service for departure and onwards.. May change from that for arrival. +SIRI v2.0. @@ -714,7 +734,11 @@ Rail transport, Roads and road transport Physical QUAY actually used. +SIRI v2.0 - + + + xxx. +SIRI v2.1 + + @@ -942,7 +966,9 @@ Rail transport, Roads and road transport - + + + xxx. +SIRI v2.1 @@ -958,13 +984,17 @@ Rail transport, Roads and road transport The latter example would implicate that the vehicle will depart towards the reference point of the QUAY (reference for measurements such as the VehicleStoppingPosition of SectorPositionAssignments). +SIRI v2.1 - + xxx. +SIRI v2.1 + + + + xxx. +SIRI v2.1 @@ -987,7 +1017,7 @@ The latter example would implicate that the vehicle will depart towards the refe - + xxx. +SIRI v2.1 @@ -999,11 +1029,20 @@ The latter example would implicate that the vehicle will depart towards the refe - - - + + + + Relative position of TRAIN ELEMENT. + + + + + xxx. +SIRI v2.1 + + + xxx. +SIRI v2.1 @@ -1024,6 +1063,8 @@ The latter example would implicate that the vehicle will depart towards the refe + + @@ -1032,7 +1073,72 @@ The latter example would implicate that the vehicle will depart towards the refe + + + + Elements for a PASSENGER CAPACITY. Used to indicate the capacities of a TRAIN ELEMENT, i.e., provide the estimated or actual number of passengers. +SIRI v2.1 + + + + + The total capacity of vehicles of the type. + + + + + The seating capacity of vehicles of the type. + + + + + The standing capacity of vehicles of the type. + + + + + The number of special places on vehicles of the type, e.g. seats for the disabled. + + + + + The number of push chair places on vehicles of the type. + + + + + The number of wheelchairs places on vehicles of the type. + + + + + + + The intersection of supplied elements describes the extent that the Occupancy values applies to. + + + + + + + Adult, child, wheelchair etc. + + + + + + + Occupancy values applying to indicated scope. + + + + + + + + + + Capacity for a VEHICLE TYPE and fare class. +SIRI v2.1 @@ -1056,44 +1162,24 @@ The latter example would implicate that the vehicle will depart towards the refe - - - Elements for a PASSENGER CAPACITY REQUIREMENT. relevant for passenger systems. +SIRI v2.1 - - - - - The total capacity of vehicles of the type. For a requirement this is the minimum needed. - - - - - The seating capacity of vehicles of the type. For a requirement this is the minimum needed. - - - - - The standing capacity of vehicles of the type. For a requirement this is the minimum needed. - - - - - The number of special places on vehicles of the type, e.g. seats for the disabled. For a requirement this is the minimum needed. - - - - - The number of push chair places on vehicles of the type. For a requirement this is the minimum needed. - - - - - The number of wheelchairs places on vehicles of the type. For a requirement this is the minimum needed. - - - - + + + + + + + Goups together the relevant references needed in a formation. +Either the smallest part of a formation, a TRAIN COMPONENT, is referenced or the TRAIN itself. +If the formation consists of multiple coupled TRAINs, a reference to the COMPOUND TRAIN is possible too. + + + + + + + + A vehicle composed of TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 @@ -1225,7 +1311,7 @@ The latter example would implicate that the vehicle will depart towards the refe - Label for TRAIN COMPONENT. + Identifier for TRAIN. @@ -1263,23 +1349,23 @@ The latter example would implicate that the vehicle will depart towards the refe - A vehicle composed of COMPOUND TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 + .... +SIRI v2.1 - A vehicle composed of COMPOUND TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 + xxx. +SIRI v2.1 - Ordered collection of TRAIN in COMPOUND TRAINs making up COMPOUND TRAIN. Each references a TRAIN. + Identifier for COMPOUND TRAIN. - Ordered collection of TRAINs making up a COMPOUND TRAIN. Each references a TRAIN. + Ordered collection of TRAINs making up a COMPOUND TRAIN. Each of those components is or references a TRAIN. @@ -1292,7 +1378,7 @@ The latter example would implicate that the vehicle will depart towards the refe - A vehicle composed of COMPOUND TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 + xxx. +SIRI v2.1 @@ -1300,15 +1386,17 @@ The latter example would implicate that the vehicle will depart towards the refe Type for a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 - + - Order of TRAIN IN COMPOUND TRAIN within TRAIN. + Identifier for TRAIN IN COMPOUND TRAIN. - + - Elements for a TRAIN IN COMPOUND TRAIN. + Order of TRAIN within COMPOUND TRAIN. + + From 9e1d2de09b3e0675a39ae2343ef81d3ae87198f2 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 4 Mar 2020 00:51:31 +0100 Subject: [PATCH 087/290] CR002: add new formation structs to RecordedCall --- .../siri_estimatedVehicleJourney-v2.0.xsd | 50 +++++++++++++++++++ 1 file changed, 50 insertions(+) diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index ce2d84ee..7f6a55ce 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -393,6 +393,26 @@ the original journey and the nature of the difference. (iii) any departure platform name on any related dated timetable CALL. + + + Type of boarding and alighting at stop, e.g. alighting, noAlighting or passThru. +SIRI v2.1 + + + + + Assignment of arrival of Scheduled STOP POINT to a physical QUAY (platform). If not given, assume same as for departure. +SIRI v2.1 + + + + + Assignments of a TRAIN formation to a physical QUAY. +SIRI v2.1 + + + + + xxx. +SIRI v2.1 + + Target departure time of VEHICLE according to latest working timetable. @@ -413,6 +433,36 @@ the original journey and the nature of the difference. Estimated time of departure of VEHICLE. + + + 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. +SIRI v2.1 + + + + + Text annotation to be used in cases where DepartureStatus is set to 'cancelled'. +SIRI v2.1 + + + + + Nature of boarding at stop, e.g. boarding, noBoarding or passThru. +SIRI v2.1 + + + + + Assignments of departure platform for Scheduled STOP POINT to a physical QUAY. +SIRI v2.1 + + + + + Assignments of a TRAIN formation to a physical QUAY. +SIRI v2.1 + + + + + xxx. +SIRI v2.1 + + From cd0c727fcb2c81623e36f07821c7d6dc94c52162 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Fri, 31 Jan 2020 17:14:23 +0100 Subject: [PATCH 088/290] CR002: fix ref mistake in OccupancyScopeFilterGrp. --- xsd/siri_model/siri_journey-v2.0.xsd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index d7a765d9..8b70182d 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -1117,7 +1117,7 @@ The latter example would implicate that the vehicle will depart towards the refe The intersection of supplied elements describes the extent that the Occupancy values applies to. - + From 8bed74849ad981be0ef460b23c71638192c1c285 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Fri, 31 Jan 2020 17:16:46 +0100 Subject: [PATCH 089/290] CR002: xmllint corrections and name/ref fix --- xsd/siri_model/siri_journey-v2.0.xsd | 151 ++++++++++++--------------- 1 file changed, 69 insertions(+), 82 deletions(-) diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index 8b70182d..ad452390 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -966,7 +966,6 @@ Rail transport, Roads and road transport - @@ -992,9 +991,6 @@ The latter example would implicate that the vehicle will depart towards the refe - - - xxx. +SIRI v2.1 @@ -1064,7 +1060,6 @@ The latter example would implicate that the vehicle will depart towards the refe - @@ -1073,71 +1068,67 @@ The latter example would implicate that the vehicle will depart towards the refe - - - - Elements for a PASSENGER CAPACITY. Used to indicate the capacities of a TRAIN ELEMENT, i.e., provide the estimated or actual number of passengers. +SIRI v2.1 - - - - - The total capacity of vehicles of the type. - - - - - The seating capacity of vehicles of the type. - - - - - The standing capacity of vehicles of the type. - - - - - The number of special places on vehicles of the type, e.g. seats for the disabled. - - - - - The number of push chair places on vehicles of the type. - - - - - The number of wheelchairs places on vehicles of the type. - - - - - - - The intersection of supplied elements describes the extent that the Occupancy values applies to. - - - - - - - Adult, child, wheelchair etc. - - - - - - - Occupancy values applying to indicated scope. - - - - - - - - - + + + Elements for a PASSENGER CAPACITY. Used to indicate the capacities of a TRAIN ELEMENT, i.e., provide the estimated or actual number of passengers. +SIRI v2.1 + + + + + The total capacity of vehicles of the type. + + + + + The seating capacity of vehicles of the type. + + + + + The standing capacity of vehicles of the type. + + + + + The number of special places on vehicles of the type, e.g. seats for the disabled. + + + + + The number of push chair places on vehicles of the type. + + + + + The number of wheelchairs places on vehicles of the type. + + + + + + + The intersection of supplied elements describes the extent that the Occupancy values applies to. + + + + + + + Adult, child, wheelchair etc. + + + + + + + Occupancy values applying to indicated scope. + + + + + + @@ -1162,24 +1153,20 @@ The latter example would implicate that the vehicle will depart towards the refe - - - - + - - Goups together the relevant references needed in a formation. + + Goups together the relevant references needed in a formation. Either the smallest part of a formation, a TRAIN COMPONENT, is referenced or the TRAIN itself. If the formation consists of multiple coupled TRAINs, a reference to the COMPOUND TRAIN is possible too. - - - - - - + + + + + + - A vehicle composed of TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 From 0d89524c48f35b7d4121b663695e5b80f1423d5b Mon Sep 17 00:00:00 2001 From: Adrian A Date: Fri, 31 Jan 2020 17:20:34 +0100 Subject: [PATCH 090/290] CR002: remove old ref after CallFormationGrp update --- xsd/siri_model/siri_journey-v2.0.xsd | 1 - 1 file changed, 1 deletion(-) diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index ad452390..827b1558 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -757,7 +757,6 @@ Rail transport, Roads and road transport Scheduled Platform name. +SIRI v2.0 - From c69e1e91a08c77d39e3f5d7cbb40b8bfb68875bd Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 4 Feb 2020 18:05:58 +0100 Subject: [PATCH 091/290] CR002: add type for occupancy percentages --- xsd/siri_utility/siri_types-v2.0.xsd | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/xsd/siri_utility/siri_types-v2.0.xsd b/xsd/siri_utility/siri_types-v2.0.xsd index 14e6968c..396c91ad 100644 --- a/xsd/siri_utility/siri_types-v2.0.xsd +++ b/xsd/siri_utility/siri_types-v2.0.xsd @@ -153,4 +153,13 @@ A string containing a phrase in a natural language name that requires at least o + + + Specifies a percentage from 0 to 100. + + + + + + From 631d4f08a0516af40eb20997f065f924b7cf0c81 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 4 Feb 2020 21:21:22 +0100 Subject: [PATCH 092/290] add QuayType (CR072) and extend Occupancy model --- xsd/siri_model/siri_journey-v2.0.xsd | 209 ++++++++++++++++++++------- 1 file changed, 158 insertions(+), 51 deletions(-) diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index 827b1558..1e6e1490 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -757,6 +757,11 @@ Rail transport, Roads and road transport Scheduled Platform name. +SIRI v2.0 + + + xxx. +SIRI v2.1 + + @@ -1037,7 +1042,7 @@ The latter example would implicate that the vehicle will depart towards the refe xxx. +SIRI v2.1 - + + + - Break down of Capacities by FARE CLASS (number of passengers that TRAIN ELEMENT can carry). + xxx. +SIRI v2.1 - - - - - - - - + xxx. +SIRI v2.1 @@ -1070,49 +1075,63 @@ The latter example would implicate that the vehicle will depart towards the refe - Elements for a PASSENGER CAPACITY. Used to indicate the capacities of a TRAIN ELEMENT, i.e., provide the estimated or actual number of passengers. +SIRI v2.1 + Elements for a PASSENGER CAPACITY. Used to indicate the maximum capacities of a TRAIN ELEMENT or the estimated/recorded capacities of a TRAIN ELEMENT at a specific stop (in number of passengers). +SIRI v2.1 - + + + The total capacity of the vehicle in number of passengers. + + + - The total capacity of vehicles of the type. + The seating capacity of the vehicle in number of passengers. - + - The seating capacity of vehicles of the type. + The standing capacity of the vehicle in number of passengers. - + - The standing capacity of vehicles of the type. + The number of special places on the vehicle, e.g. seats for the disabled. - + - The number of special places on vehicles of the type, e.g. seats for the disabled. + The number of push chair places on the vehicle. - + - The number of push chair places on vehicles of the type. + The number of wheelchair places on the vehicle. - + - The number of wheelchairs places on vehicles of the type. + The number of places on the vehicle that are suitable for prams. + + + + + The number of bicycle racks on the vehicle. - The intersection of supplied elements describes the extent that the Occupancy values applies to. + The intersection of supplied elements describes the extent that the Occupancy values applies to. +SIRI v2.1 - - + + + Fare class in VEHICLE for which occupancy and capacities are specified. + + + Adult, child, wheelchair etc. @@ -1121,39 +1140,121 @@ The latter example would implicate that the vehicle will depart towards the refe - Occupancy values applying to indicated scope. + Occupancy values applying to indicated scope. +SIRI v2.1 - - + + + An approximate figure of how occupied or full the VEHICLE is, e.g. manySeatsAvailable or standingRoomOnly. +More accurate data can be provided by the individual occupancies or capacities below. + + + + + Utilised percentage of maximum payload after departing the STOP POINT. + + + + + Provides occupancy information relevant for the used occupancy scope filter. + + + + + + Total number of alighting passengers for this vehicle journey at this STOP POINT. + + + + + Total number of boarding passengers for this vehicle journey at this STOP POINT. + + + + + Total number of passengers on-board after departing the STOP POINT. + + + + + Total number of wheelchairs on-board after departing the STOP POINT. + + + + + Total number of prams on-board after departing the STOP POINT. + + + + + Total number of bicycles on-board, i.e., number of bicycle racks that are occupied after departing the STOP POINT. + + + + + - - + - Capacity for a VEHICLE TYPE and fare class. +SIRI v2.1 + Used to specify that a travel group has booked a section of the vehicle for a part of the journey, and if so under what name. +SIRI v2.1 - - + + + + Name for which the travel group has made the reservation. + + + + + Number of seats that the group has booked. + + + + + + - Capacity for a VEHICLE TYPE and fare class. +SIRI v2.1 + Occupancies and real-time capacities of a vehicle (by fare classes) after departing a given STOP POINT. +SIRI v2.1 - + + + - Fare class in VEHICLE for which capacity is specified. + Provides capacity information relevant for the used occupancy scope filter. + + + + + - + + - How occupied or full the VEHICLE is. This is an approximate figure. The PassengerCapacityGroup provides more accurate data. + Reservations of travel groups, i.e., name of group and number of seats booked. + + + + + + Maximum capacities of a vehicle, e.g. TRAIN ELEMENT, by its fare classes. +SIRI v2.1 + + + + + + Maximum number of passengers that can be carried by a vehicle of given type. + + - Goups together the relevant references needed in a formation. @@ -1166,6 +1267,7 @@ If the formation consists of multiple coupled TRAINs, a reference to the COMPOUN + A vehicle composed of TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 @@ -1204,10 +1306,20 @@ If the formation consists of multiple coupled TRAINs, a reference to the COMPOUN Type of TRAIN ELEMENT. + + + Denotes the official "registration number" of the vehicle. Mainly for production purposes. + + + + + Advertised serial number of the vehicle for seat reservations and passenger orientation. + + - + - Break down of Capacities by FARE CLASS (number of passengers that TRAIN ELEMENT can carry). + Break down of capacities by FARE CLASS (number of passengers that TRAIN ELEMENT can carry). @@ -1372,7 +1484,7 @@ If the formation consists of multiple coupled TRAINs, a reference to the COMPOUN Type for a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 - + Identifier for TRAIN IN COMPOUND TRAIN. @@ -1472,14 +1584,9 @@ If the formation consists of multiple coupled TRAINs, a reference to the COMPOUN Euroclass of the vehicle type. - - - Total Number of passengers that VEHICLE TYPE. can carry. - - - + - Break down of Capacities by FARE CLASS. + Break down of total capacities by FARE CLASS. From 3310cbcbc2b376d4db9c6bf793c4ca3e42d5b77f Mon Sep 17 00:00:00 2001 From: Adrian A Date: Mon, 10 Feb 2020 16:47:57 +0100 Subject: [PATCH 093/290] CR002: update Occupancy and Facility structures --- xsd/siri_model/siri_journey-v2.0.xsd | 179 ++++++++++----------------- 1 file changed, 62 insertions(+), 117 deletions(-) diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index 1e6e1490..6b813c32 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -1154,44 +1154,35 @@ More accurate data can be provided by the individual occupancies or capacities b Utilised percentage of maximum payload after departing the STOP POINT. - + - Provides occupancy information relevant for the used occupancy scope filter. + Total number of alighting passengers for this vehicle journey at this STOP POINT. + + + + + Total number of boarding passengers for this vehicle journey at this STOP POINT. + + + + + Total number of passengers on-board after departing the STOP POINT. + + + + + Total number of wheelchairs on-board after departing the STOP POINT. + + + + + Total number of prams on-board after departing the STOP POINT. + + + + + Total number of bicycles on-board, i.e., number of bicycle racks that are occupied after departing the STOP POINT. - - - - - Total number of alighting passengers for this vehicle journey at this STOP POINT. - - - - - Total number of boarding passengers for this vehicle journey at this STOP POINT. - - - - - Total number of passengers on-board after departing the STOP POINT. - - - - - Total number of wheelchairs on-board after departing the STOP POINT. - - - - - Total number of prams on-board after departing the STOP POINT. - - - - - Total number of bicycles on-board, i.e., number of bicycle racks that are occupied after departing the STOP POINT. - - - - @@ -1249,24 +1240,11 @@ More accurate data can be provided by the individual occupancies or capacities b - + Maximum number of passengers that can be carried by a vehicle of given type. - - - - Goups together the relevant references needed in a formation. -Either the smallest part of a formation, a TRAIN COMPONENT, is referenced or the TRAIN itself. -If the formation consists of multiple coupled TRAINs, a reference to the COMPOUND TRAIN is possible too. - - - - - - - @@ -1283,6 +1261,7 @@ If the formation consists of multiple coupled TRAINs, a reference to the COMPOUN Identifier for TRAIN ELEMENT. + @@ -1291,16 +1270,6 @@ If the formation consists of multiple coupled TRAINs, a reference to the COMPOUN Elements for a TRAIN ELEMENT. +SIRI v2.1 - - - Name of TRAIN ELEMENT. - - - - - Description of TRAIN ELEMENT. - - Type of TRAIN ELEMENT. @@ -1317,38 +1286,6 @@ If the formation consists of multiple coupled TRAINs, a reference to the COMPOUN - - - Break down of capacities by FARE CLASS (number of passengers that TRAIN ELEMENT can carry). - - - - - - - - - - The length of a TRAIN ELEMENT. - - - - - The width of a TRAIN ELEMENT. - - - - - - Facilities of element. - - - - - - Actual EQUIPMENT on element. - - @@ -1551,11 +1488,19 @@ If the formation consists of multiple coupled TRAINs, a reference to the COMPOUN - - + - Facilities of VEHICLE. + Facilities of TRAIN ELEMENT. + + + + + + + + + @@ -1586,7 +1531,7 @@ If the formation consists of multiple coupled TRAINs, a reference to the COMPOUN - Break down of total capacities by FARE CLASS. + Break down of capacities by FARE CLASS (number of passengers that TRAIN ELEMENT can carry). @@ -1598,51 +1543,51 @@ If the formation consists of multiple coupled TRAINs, a reference to the COMPOUN - + - Dimension elements for a VEHICLE TYPE. +SIRI v2.1 + Elements specifying Requirement properties of VEHICLE TYPE. Vehicle should satisfy these requirements. +SIRI v2.1 - - - The length of a VEHICLE of the type. - - - + - The width of a VEHICLE of the type. + Whether Vehicle is low floor to facilitate access by the mobility impaired. - + - The length of a VEHICLE of the type. + Whether vehicle has lift or ramp to facilitate wheelchair access. - + - The weight of a VEHICLE of the type. + Whether vehicle has hoist for wheelchair access. - + - Elements specifying Requirement properties of VEHICLE TYPE. Vehicle should satisfy these requirements. +SIRI v2.1 + Dimension elements for a VEHICLE TYPE. +SIRI v2.1 - + - Whether Vehicle is low floor to facilitate access by the mobility impaired. + The length of a VEHICLE of the type. - + - Whether vehicle has lift or ramp to facilitate wheelchair access. + The width of a VEHICLE of the type. - + - Whether vehicle has hoist for wheelchair access. + The length of a VEHICLE of the type. + + + + + The weight of a VEHICLE of the type. From 32af9eb0b4d71f708f0b14309c87543346dd15d5 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Mon, 10 Feb 2020 16:42:49 +0100 Subject: [PATCH 094/290] CR002: add FormationRefs to FacilityCond. model --- xsd/siri_model/siri_facility-v2.0.xsd | 3 +++ 1 file changed, 3 insertions(+) diff --git a/xsd/siri_model/siri_facility-v2.0.xsd b/xsd/siri_model/siri_facility-v2.0.xsd index 6f33d2b8..961f88b4 100644 --- a/xsd/siri_model/siri_facility-v2.0.xsd +++ b/xsd/siri_model/siri_facility-v2.0.xsd @@ -177,6 +177,9 @@ Rail transport, Roads and road transport + + + From b70a615146fc7be41e123a0daac8b06fe03a9e1e Mon Sep 17 00:00:00 2001 From: Adrian A Date: Thu, 13 Feb 2020 19:07:52 +0100 Subject: [PATCH 095/290] CR002: add new enum for TrainComponentGroup --- xsd/siri_model/siri_journey_support-v2.0.xsd | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/xsd/siri_model/siri_journey_support-v2.0.xsd b/xsd/siri_model/siri_journey_support-v2.0.xsd index 99cb6524..e48dcb9c 100644 --- a/xsd/siri_model/siri_journey_support-v2.0.xsd +++ b/xsd/siri_model/siri_journey_support-v2.0.xsd @@ -776,4 +776,14 @@ Corresponds to NeTEX TYPE OF SERVICe. + + + Allowed values for orientation of TRAIN ELEMENT. +SIRI v2.1 + + + + + + + From ca067b476e7ab8f9c8e04bcfa0501ab7aa14758d Mon Sep 17 00:00:00 2001 From: Adrian A Date: Thu, 13 Feb 2020 19:09:33 +0100 Subject: [PATCH 096/290] CR002: update Train model / new PassageStructure --- xsd/siri_model/siri_journey-v2.0.xsd | 58 ++++++++++++++++++++++------ 1 file changed, 46 insertions(+), 12 deletions(-) diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index 6b813c32..e248b6a1 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -1060,7 +1060,7 @@ The latter example would implicate that the vehicle will depart towards the refe 2) VehicleStatus entspricht FoZustand und kann für jedes Fahrzeug innerhalb der Formation angegeben werden. Da wir uns ja aber für unbounded xxxFormationAssignment entschieden haben, können diese Stati evtl. auch einfach auf beiden (flat) vorhanden sein. Oder man mach ein eigenes Element dafür: xxxFormationStatus (unbounded) mit Referenzen auf die TRAINs und TRAIN ELEMENTs etc. --> - + xxx. +SIRI v2.1 @@ -1256,13 +1256,13 @@ More accurate data can be provided by the individual occupancies or capacities b A vehicle composed of TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 - + Identifier for TRAIN ELEMENT. - + @@ -1331,6 +1331,11 @@ More accurate data can be provided by the individual occupancies or capacities b + + + Orientation of TRAIN ELEMENT within TRAIN, e.g. 'forwards' or 'backwards'. + + @@ -1368,6 +1373,7 @@ More accurate data can be provided by the individual occupancies or capacities b Nature of Train Size., Short, long, normal. Default is normal. + Ordered collection of TRAIN COMPONENTs making up TRAIN. @@ -1409,6 +1415,11 @@ More accurate data can be provided by the individual occupancies or capacities b + + + xxx. + + @@ -1431,8 +1442,7 @@ More accurate data can be provided by the individual occupancies or capacities b Order of TRAIN within COMPOUND TRAIN. - - + @@ -1440,17 +1450,18 @@ More accurate data can be provided by the individual occupancies or capacities b Elements for a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 + + + Label for TRAIN IN COMPOUND TRAIN. + + Description of TRAIN IN COMPOUND TRAIN. - - - Reference to a TRAIN. +SIRI v2.1 - - + @@ -1458,13 +1469,36 @@ More accurate data can be provided by the individual occupancies or capacities b Whether the component order of the TRAIN IN COMPOUND TRAIN is reversed compared to the order in the TRAIN. - + - Label for TRAIN IN COMPOUND TRAIN. + xxx. + + + + + + + + + + xxx. + + + xxx. +SIRI v2.1 + + + + + + xxx. + + + + From a04431b4617c2e384a1d766c8f902860eaffa529 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Sat, 15 Feb 2020 18:21:38 +0100 Subject: [PATCH 097/290] CR002: add enums for formation status codes --- xsd/siri_model/siri_journey_support-v2.0.xsd | 32 ++++++++++++++++++++ 1 file changed, 32 insertions(+) diff --git a/xsd/siri_model/siri_journey_support-v2.0.xsd b/xsd/siri_model/siri_journey_support-v2.0.xsd index e48dcb9c..0ed7559b 100644 --- a/xsd/siri_model/siri_journey_support-v2.0.xsd +++ b/xsd/siri_model/siri_journey_support-v2.0.xsd @@ -786,4 +786,36 @@ Corresponds to NeTEX TYPE OF SERVICe. + + + Allowed values for VEHICLE STATUS CODE. +SIRI v2.1 + + + + + + + + + + + + + Allowed values for FORMATION UPDATE CODE. +SIRI v2.1 + + + + + + + + + + + + + + + + From 215e2f6be9dee07296307dd0588f196193c8cd47 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 18 Feb 2020 16:04:14 +0100 Subject: [PATCH 098/290] CR002: add new FormationCondition structure --- xsd/siri_model/siri_journey-v2.0.xsd | 167 ++++++++++++++++----------- 1 file changed, 99 insertions(+), 68 deletions(-) diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index e248b6a1..a7a13602 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -1,6 +1,6 @@ - + @@ -114,8 +114,14 @@ Rail transport, Roads and road transport SIRI Common Journey Model. + + + + + + @@ -479,6 +485,7 @@ Rail transport, Roads and road transport Assignments of a TRAIN formation to a physical QUAY. +SIRI v2.1 + xxx. +SIRI v2.1 @@ -514,6 +521,7 @@ Rail transport, Roads and road transport Assignments of a TRAIN formation to a physical QUAY. +SIRI v2.1 + xxx. +SIRI v2.1 @@ -970,106 +978,139 @@ Rail transport, Roads and road transport - - + - xxx. +SIRI v2.1 + Indication of the direction of travel of the vehicle or formation (e.g. TRAIN composition ) with respect to the platform or QUAY. For example "towards A", which means that the vehicle departs towards sector "A" of the QUAY. +SIRI v2.1 - - - - xxx. +SIRI v2.1 - - - - - Orientation of a vehicle or vehicle formation/composition relative to a QUAY. Possible values might include 'towardsStartOfQuay', 'towardsEndOfQuay' or 'towards0'. -The latter example would implicate that the vehicle will depart towards the reference point of the QUAY (reference for measurements such as the VehicleStoppingPosition of SectorPositionAssignments). +SIRI v2.1 - - - - - xxx. +SIRI v2.1 - - - - - - + + + + + xxx. +SIRI v2.1 - + + + + xxx. +SIRI v2.1 + + + + + + + - xxx. +SIRI v2.1 + Relative position of TRAIN ELEMENT. - + xxx. +SIRI v2.1 - + xxx. +SIRI v2.1 - + + + + Information about a change of the formation (e.g. TRAIN composition) or changes of vehicles within the formation. +SIRI v2.1 + + + xxx. +SIRI v2.1 + - + - xxx. +SIRI v2.1 + Status of formation. + + + + + Status of a vehicle within formation. - - - - + + - Relative position of TRAIN ELEMENT. + Information on recommendations for passengers on how to deal with the formation change. - + + + + + + Description of the status of a monitored formation. + + + - xxx. +SIRI v2.1 + Status of the formation. - - - + - xxx. +SIRI v2.1 + Accessibility of the formation or a vehicle within the formation. + + + + + + + + Description of the recommended action for passengers on how to deal with changes, for example of the TRAIN formation. + + + + + Type of the recommendation, e.g. 'unknown', 'replacement' or 'otherRoute'. - + - xxx. +SIRI v2.1 + Description of the recommended action in natural language. + @@ -1261,8 +1302,8 @@ More accurate data can be provided by the individual occupancies or capacities b Identifier for TRAIN ELEMENT. - + @@ -1415,11 +1456,6 @@ More accurate data can be provided by the individual occupancies or capacities b - - - xxx. - - @@ -1475,18 +1511,13 @@ More accurate data can be provided by the individual occupancies or capacities b - + - - - xxx. - - - + xxx. +SIRI v2.1 From 7c1e3e0b16b6b844e5b8fcf2b19f28d9174d45f7 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 18 Feb 2020 16:05:30 +0100 Subject: [PATCH 099/290] CR002: add new enums for FormationCondition strc. --- xsd/siri_model/siri_journey_support-v2.0.xsd | 29 ++++++++++++++++---- 1 file changed, 24 insertions(+), 5 deletions(-) diff --git a/xsd/siri_model/siri_journey_support-v2.0.xsd b/xsd/siri_model/siri_journey_support-v2.0.xsd index 0ed7559b..ba5a51f1 100644 --- a/xsd/siri_model/siri_journey_support-v2.0.xsd +++ b/xsd/siri_model/siri_journey_support-v2.0.xsd @@ -415,6 +415,19 @@ Rail transport, Roads and road transport Reference to a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 + + + + Goups together the relevant references needed in a formation. +Either the smallest part of a formation, a TRAIN COMPONENT, is referenced or the TRAIN itself. +If the formation consists of multiple coupled TRAINs, a reference to the COMPOUND TRAIN is possible too. + + + + + + + @@ -786,11 +799,17 @@ Corresponds to NeTEX TYPE OF SERVICe. - + - Allowed values for VEHICLE STATUS CODE. +SIRI v2.1 + Allowed values for VEHICLE IN FORMATION STATUS CODE. +SIRI v2.1 - + + + + + + + @@ -799,9 +818,9 @@ Corresponds to NeTEX TYPE OF SERVICe. - + - Allowed values for FORMATION UPDATE CODE. +SIRI v2.1 + Allowed values for FORMATION CHANGE CODE. +SIRI v2.1 From 62ee37fd27fba6faf691cf7b77d4be2e61af0e35 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 18 Feb 2020 16:09:54 +0100 Subject: [PATCH 100/290] CR002: include FormationCondition in JourneyPart --- xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd index 1fbbf7af..7a6bbf20 100644 --- a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd @@ -328,6 +328,11 @@ For SIRI-VM this is the most recent stop visited by the VEHICLE. + + + Information about a change of the formation (e.g. TRAIN composition) or changes of vehicles within the formation. +SIRI v2.1 + + From 7ce85446a8cd6128cc0051f57277b3a2215f6d71 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 18 Feb 2020 16:11:48 +0100 Subject: [PATCH 101/290] CR002: include FormationCondition in DisruptionGrp --- xsd/siri_model/siri_facility-v2.0.xsd | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/xsd/siri_model/siri_facility-v2.0.xsd b/xsd/siri_model/siri_facility-v2.0.xsd index 961f88b4..7447e281 100644 --- a/xsd/siri_model/siri_facility-v2.0.xsd +++ b/xsd/siri_model/siri_facility-v2.0.xsd @@ -75,6 +75,7 @@ Rail transport, Roads and road transport + @@ -562,9 +563,14 @@ Rail transport, Roads and road transport Elements describing nature of disruption. + + + Information about a change of the formation (e.g. TRAIN composition) or changes of vehicles within the formation. +SIRI v2.1 + + - Information about a change of Equipment availabilti at stop or on vehicle that may affect access or use. + Information about a change of Equipment availabilty at stop or on vehicle that may affect access or use. From e83f8afda109dd38af379d6d9cd0498166dda453 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 3 Mar 2020 23:34:16 +0100 Subject: [PATCH 102/290] CR002: add JrnyParts, JrnyFormationGroup... to PT --- xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd index 12c4d200..abf310d8 100644 --- a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd @@ -118,8 +118,7 @@ Rail transport, Roads and road transport - - + Complete sequence of stops along the route path, in calling order. From 0ef6253aa7408187d58b3061d64910dfa32b313f Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 3 Mar 2020 23:38:19 +0100 Subject: [PATCH 103/290] CR002: clean-up of docs and change of certain refs --- xsd/siri_model/siri_journey-v2.0.xsd | 144 +++++++++++-------- xsd/siri_model/siri_journey_support-v2.0.xsd | 10 -- 2 files changed, 82 insertions(+), 72 deletions(-) diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index a7a13602..0192664b 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -354,6 +354,15 @@ Rail transport, Roads and road transport + + + Operational information about the monitored VEHICLE JOURNEY. + + + + + + Operational information about the monitored VEHICLE JOURNEY. @@ -418,9 +427,14 @@ Rail transport, Roads and road transport - + + + Assignment of arrival of Scheduled STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. +SIRI v2.0. + + + - Assignment of arrival of Scheduled STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure +SIRI v2.0. + Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). If not given, assume same as for departure. +SIRI v2.1 @@ -438,7 +452,12 @@ Rail transport, Roads and road transport - + + + + Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). +SIRI v2.1 + + OPERATORs of of service for departure and onwards.. May change from that for arrival. +SIRI v2.0. @@ -477,18 +496,18 @@ Rail transport, Roads and road transport - Assignment of arrival of Scheduled STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure +SIRI v2.0. + Assignment of arrival of Scheduled STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. +SIRI v2.0. - Assignments of a TRAIN formation to a physical QUAY. +SIRI v2.1 + Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). If not given, assume same as for departure. +SIRI v2.1 - xxx. +SIRI v2.1 + Real-time occupancies and capacities of a vehicle (by fare classes) when arriving at a given STOP POINT. +SIRI v2.1 @@ -513,18 +532,18 @@ Rail transport, Roads and road transport - Assignments of departure platfiorm for Scheduled STOP POINT to a physical QUAY. +SIRI v2.0. + Assignment of departure platfiorm for Scheduled STOP POINT to a physical QUAY. +SIRI v2.0. - Assignments of a TRAIN formation to a physical QUAY. +SIRI v2.1 + Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). +SIRI v2.1 - xxx. +SIRI v2.1 + Real-time occupancies and capacities of a vehicle (by fare classes) after departing at a given STOP POINT. +SIRI v2.1 @@ -742,11 +761,7 @@ Rail transport, Roads and road transport Physical QUAY actually used. +SIRI v2.0 - - - xxx. +SIRI v2.1 - - + @@ -765,11 +780,7 @@ Rail transport, Roads and road transport Scheduled Platform name. +SIRI v2.0 - - - xxx. +SIRI v2.1 - - + @@ -919,6 +930,13 @@ Rail transport, Roads and road transport + + + + Indicates the type of the referenced QUAY. In case of detailed STOP PLACE models, a QUAY may be a nested structure. +A QUAY may be part of a group of QUAYs, or may be divided into sectors, i.e., smaller sub-QUAYs. +SIRI v2.1 + + @@ -936,16 +954,14 @@ Rail transport, Roads and road transport - - xxx. +SIRI v2.1 + Groups relevant elements of the formation model that are used on JOURNEY level. +The TRAIN Conceptual represents VEHICLE TYPE properties that are peculiar to TRAINs. A TRAIN may comprise not just a single VEHICLE but a chain of carriages, TRAIN ELEMENTS, assembled as TRAIN COMPONENTs. +Groups of carriages may be managed as sections by composing TRAINs into a COMPOUND TRAIN made up of multiple TRAIN IN COMPOUND TRAIN, for example in a train that joins or splits. +SIRI v2.1 - - xxx. +SIRI v2.1. - @@ -954,9 +970,6 @@ Rail transport, Roads and road transport - - xxx. +SIRI v2.1 - @@ -965,9 +978,6 @@ Rail transport, Roads and road transport - - xxx. +SIRI v2.1 - @@ -980,7 +990,8 @@ Rail transport, Roads and road transport - Indication of the direction of travel of the vehicle or formation (e.g. TRAIN composition ) with respect to the platform or QUAY. For example "towards A", which means that the vehicle departs towards sector "A" of the QUAY. +SIRI v2.1 + Indication of the direction of travel of the vehicle or formation (e.g. TRAIN composition ) with respect to the platform, or more precisely the QUAY. +For example "towards A", which means that the vehicle departs towards sector "A" of the QUAY. It is advised to specify a reference point that is meaningful for passengers on location. +SIRI v2.1 @@ -988,17 +999,13 @@ Rail transport, Roads and road transport - xxx. +SIRI v2.1 + Assignment of the arrival/departure of a VEHICLE within a formation, e.g. carriage in a TRAIN composition, to a physical QUAY or nested QUAY (i.e. platform or sector of a platform). +SIRI v2.1 - - - xxx. +SIRI v2.1 - - + - + @@ -1008,12 +1015,13 @@ Rail transport, Roads and road transport - xxx. +SIRI v2.1 + Reference to the QUAY on which the particular VEHICLE of the formation arrives or departs from. +If a QUAY is divided into sectors (with the help of STOP ASSIGNMENTs), and a VEHICLE stops in two sectors of the QUAY, the FORMATION ASSIGNMENT must reference both. +SIRI v2.1 - xxx. +SIRI v2.1 + Information about a change of a VEHICLE within the formation, e.g., whether a VEHICLE is open, booked or has defective doors. +SIRI v2.1 @@ -1026,7 +1034,7 @@ Rail transport, Roads and road transport - xxx. +SIRI v2.1 + Type for FORMATION CONDITION. +SIRI v2.1 @@ -1079,7 +1087,7 @@ Rail transport, Roads and road transport - xxx. +SIRI v2.1 + Elements for FormationStatus that further describe the status of the formation, e.g. whether the accessibility has changed. +SIRI v2.1 @@ -1210,6 +1218,16 @@ More accurate data can be provided by the individual occupancies or capacities b Total number of passengers on-board after departing the STOP POINT. + + + Total number of special places, e.g. seats for the disabled, that are occupied after departing the STOP POINT. + + + + + Total number of pushchairs on-board after departing the STOP POINT. + + Total number of wheelchairs on-board after departing the STOP POINT. @@ -1294,7 +1312,7 @@ More accurate data can be provided by the individual occupancies or capacities b - A vehicle composed of TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 + Type for TRAIN ELEMENT. +SIRI v2.1 @@ -1337,7 +1355,7 @@ More accurate data can be provided by the individual occupancies or capacities b - A vehicle composed of TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 + Type for TRAIN COMPONENT. +SIRI v2.1 @@ -1372,9 +1390,9 @@ More accurate data can be provided by the individual occupancies or capacities b - + - Orientation of TRAIN ELEMENT within TRAIN, e.g. 'forwards' or 'backwards'. + Whether orientation of TRAIN ELEMENT within TRAIN is reversed or not. Default is 'false', i.e., they have the same orientation (usually forward in the direction of travel). @@ -1387,7 +1405,7 @@ More accurate data can be provided by the individual occupancies or capacities b - A vehicle composed of TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 + Type for TRAIN. +SIRI v2.1 @@ -1414,7 +1432,6 @@ More accurate data can be provided by the individual occupancies or capacities b Nature of Train Size., Short, long, normal. Default is normal. - Ordered collection of TRAIN COMPONENTs making up TRAIN. @@ -1431,12 +1448,12 @@ More accurate data can be provided by the individual occupancies or capacities b - .... +SIRI v2.1 + Groups of carriages may be managed as sections by composing TRAINs into a COMPOUND TRAIN, for example in a train that joins or splits. +SIRI v2.1 - xxx. +SIRI v2.1 + Type for COMPOUND TRAIN. +SIRI v2.1 @@ -1460,7 +1477,7 @@ More accurate data can be provided by the individual occupancies or capacities b - xxx. +SIRI v2.1 + An instance of a TRAIN (that has a certain position within the formation) making up a COMPOUND TRAIN. +SIRI v2.1 @@ -1500,34 +1517,37 @@ More accurate data can be provided by the individual occupancies or capacities b + - Whether the component order of the TRAIN IN COMPOUND TRAIN is reversed compared to the order in the TRAIN. + Whether orientation of TRAIN within COMPOUND TRAIN is reversed or not. Default is 'false', i.e., they have the same orientation (usually forward in the direction of travel). - xxx. + Specifies whether a passage from/to an adjacent VEHICLE is possible for passengers. - + - + - xxx. +SIRI v2.1 + Indicates whether passengers have access to adjacent VEHICLEs or carriages, i.e., whether passage between those VEHICLES is possible. +SIRI v2.1 - - - - xxx. - - + + + + + + + + diff --git a/xsd/siri_model/siri_journey_support-v2.0.xsd b/xsd/siri_model/siri_journey_support-v2.0.xsd index ba5a51f1..8404b9ed 100644 --- a/xsd/siri_model/siri_journey_support-v2.0.xsd +++ b/xsd/siri_model/siri_journey_support-v2.0.xsd @@ -789,16 +789,6 @@ Corresponds to NeTEX TYPE OF SERVICe. - - - Allowed values for orientation of TRAIN ELEMENT. +SIRI v2.1 - - - - - - - Allowed values for VEHICLE IN FORMATION STATUS CODE. +SIRI v2.1 From b889346233f898543e16811d32084601cfda4f95 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 3 Mar 2020 23:41:00 +0100 Subject: [PATCH 104/290] CR002: add DisrupGroup to JrnyPart / add PT Groups --- .../siri_monitoredVehicleJourney-v2.0.xsd | 77 +++++++++++++++++-- 1 file changed, 72 insertions(+), 5 deletions(-) diff --git a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd index 7a6bbf20..f8253986 100644 --- a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd @@ -304,12 +304,12 @@ For SIRI-VM this is the most recent stop visited by the VEHICLE. - Type for a refernces to JOURNEY PARTs. +SIRI v2.0 + Type for a reference to JOURNEY PART. +SIRI v2.0 - Refrence to a JOURNEY part. +SIRI v2.0 + Reference to a JOURNEY part. +SIRI v2.0 @@ -319,7 +319,7 @@ For SIRI-VM this is the most recent stop visited by the VEHICLE. - Operator of JOURNEY PART. +SIRI v2.0 + Operator of JOURNEY PART. +SIRI v2.0 @@ -328,9 +328,34 @@ For SIRI-VM this is the most recent stop visited by the VEHICLE. - + + + + + + + Type for a reference to JOURNEY PART. +SIRI v2.1 + + + + + Reference to a JOURNEY part. + + + + + Train Number for JOURNEY PART. + + + - Information about a change of the formation (e.g. TRAIN composition) or changes of vehicles within the formation. +SIRI v2.1 + Operator of JOURNEY PART. + + + + + Reference to a COMPOUND TRAIN which represents the train formation/composition as a whole. +A journey (with VEHICLE TYPE 'rail') does always have one or more JOURNEY PARTs in which the train composition remains unchanged. @@ -401,6 +426,48 @@ A journey (with VEHICLE TYPE 'rail') does always have one or more JOURNEY PARTs + + + Operational information about the monitored VEHICLE JOURNEY. + + + + + If a VEHICLE JOURNEY is a coupled journey, i.e. comprises several coupled BLOCKparts, there will be a separate delivery for each BLOCKp art and this element will indicate the vehicles that the journey part uses. + + + + + + TRAIN NUMBERs for journey. +SIRI v2.0 + + + + + + TRAIN NUMBER assigned to VEHICLE JOURNEY. +SIRI 2.0 + + + + + + + + JOURNEY PARTs making up JOURNEY +SIRIv2.0 e. + + + + + + Information about Parts of JOURNEY +SIRI v2.0 + + + + + + + + From 718d702a2aa07d44020cdca0614a2b722002b172 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 3 Mar 2020 23:41:26 +0100 Subject: [PATCH 105/290] CR002: clean-up of docs --- xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index 7f6a55ce..b2705cda 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -405,12 +405,12 @@ the original journey and the nature of the difference. - Assignments of a TRAIN formation to a physical QUAY. +SIRI v2.1 + Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). If not given, assume same as for departure. +SIRI v2.1 - xxx. +SIRI v2.1 + Recorded occupancies and capacities of a vehicle (by fare classes) after departing at a given STOP POINT. +SIRI v2.1 @@ -450,17 +450,17 @@ the original journey and the nature of the difference. - Assignments of departure platform for Scheduled STOP POINT to a physical QUAY. +SIRI v2.1 + Assignment of departure platform for Scheduled STOP POINT to a physical QUAY. +SIRI v2.1 - Assignments of a TRAIN formation to a physical QUAY. +SIRI v2.1 + Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). +SIRI v2.1 - xxx. +SIRI v2.1 + Recorded occupancies and capacities of a vehicle (by fare classes) after departing at a given STOP POINT. +SIRI v2.1 From 0139963fe224ac36b7c56a39238c9d92b19e119a Mon Sep 17 00:00:00 2001 From: Adrian A Date: Mon, 10 Feb 2020 16:44:48 +0100 Subject: [PATCH 106/290] CR072: add QuayTypeEnum --- xsd/siri_model/siri_journey_support-v2.0.xsd | 62 +++++++++++++++----- 1 file changed, 48 insertions(+), 14 deletions(-) diff --git a/xsd/siri_model/siri_journey_support-v2.0.xsd b/xsd/siri_model/siri_journey_support-v2.0.xsd index 8404b9ed..2b7accb3 100644 --- a/xsd/siri_model/siri_journey_support-v2.0.xsd +++ b/xsd/siri_model/siri_journey_support-v2.0.xsd @@ -681,22 +681,56 @@ Corresponds to NeTEX TYPE OF SERVICe. + + + + Allowed values for QuayType which is used to characterise the STOP ASSIGNMENTs. +SIRI v2.1 + + + + + A type of QUAY that consists of multiple QUAYs of type 'platform'. Examples of such groups would be the lower and upper level of a station. + + + + + A type of QUAY that consists of at least two child QUAYs of type 'platformEdge'. + + + + + A type of QUAY which allows direct access to a VEHICLE, e.g. an on-street bus stop, or consists of multiple child QUAYs of type 'platformSector'. + + + + + A QUAY of type 'platformEdge' may be divided into multiple sectors, e.g. "A", "B", "C" etc., to help passengers find a specific part of a vehicle. +The first class carriage of a TRAIN might, for example, be assigned to sector "A" of a QUAY. + + + + + A location within a QUAY from which passengers may directly board, or onto which passengers may directly alight from a VEHICLE. + + + + - - Allowed values for TYPE OF TRAIIN ELEMENT. +SIRI v2.1 - - - - - - - - - - - - + + Allowed values for TYPE OF TRAIN ELEMENT. +SIRI v2.1 + + + + + + + + + + + + From 373517e1325a2956ad520c3c2672219421764b52 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 6 Nov 2019 15:31:03 +0100 Subject: [PATCH 107/290] CR005: add JourneyPartViewGroup for indirect refs # Conflicts: # xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd --- .../siri_monitoredVehicleJourney-v2.0.xsd | 27 +++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd index f8253986..1c7b1a7b 100644 --- a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd @@ -361,6 +361,33 @@ A journey (with VEHICLE TYPE 'rail') does always have one or more JOURNEY PARTs + + + JourneyPart information instead of or in addition to the JourneyPartRef. +SIRI v2.0 + + + + + Reference to the SCHEDULED STOP POINT at which the related JOURNEY PART begins. + + + + + Reference to the SCHEDULED STOP POINT at which the related JOURNEY PART ends. + + + + + Time at which the related JOURNEY PART begins. + + + + + Time at which the related JOURNEY PART ends. + + + + From dac8e486dd056456847dfe2ed74e3c2fb14da5b1 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 4 Dec 2019 03:25:16 +0100 Subject: [PATCH 108/290] CR005: make JourneyPartRef optional and fix annot. # Conflicts: # xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd --- xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd index 1c7b1a7b..1d2d2e84 100644 --- a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd @@ -307,7 +307,7 @@ For SIRI-VM this is the most recent stop visited by the VEHICLE.Type for a reference to JOURNEY PART. +SIRI v2.0 - + Reference to a JOURNEY part. +SIRI v2.0 From 33a3f543f4c1ffd4776451c706c10c81789cfda9 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 4 Mar 2020 11:57:18 +0100 Subject: [PATCH 109/290] CR017: add GTFS-R enums to Occupancy --- xsd/siri_model/siri_reference-v2.0.xsd | 31 ++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) diff --git a/xsd/siri_model/siri_reference-v2.0.xsd b/xsd/siri_model/siri_reference-v2.0.xsd index be7bb3ae..2f7c256b 100644 --- a/xsd/siri_model/siri_reference-v2.0.xsd +++ b/xsd/siri_model/siri_reference-v2.0.xsd @@ -632,6 +632,37 @@ Values for these elements can be specified on an annual schedule and will be inh + + + + The vehicle is considered empty by most measures, and has few or no passengers onboard, but is still accepting passengers. + + + + + The vehicle has a large percentage of seats available. What percentage of free seats out of the total seats available is to be considered large enough to fall into this category is determined at the discretion of the producer. + + + + + The vehicle has a small percentage of seats available. What percentage of free seats out of the total seats available is to be considered small enough to fall into this category is determined at the discretion of the producer. + + + + + The vehicle can currently accommodate only standing passengers. + + + + + The vehicle can currently accommodate only standing passengers and has limited space for them. + + + + + The vehicle cannot accept passengers. + + From 7edab55f0f3d70404193edc16c15a543b8d22ef3 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 4 Mar 2020 12:42:29 +0100 Subject: [PATCH 110/290] remove artifact from other CR --- xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd | 5 ----- 1 file changed, 5 deletions(-) diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index b2705cda..81f2f19d 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -438,11 +438,6 @@ the original journey and the nature of the difference. 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. +SIRI v2.1 - - - Text annotation to be used in cases where DepartureStatus is set to 'cancelled'. +SIRI v2.1 - - Nature of boarding at stop, e.g. boarding, noBoarding or passThru. +SIRI v2.1 From 2d89d3240ca8cdf44d85ca80096f69005aaeba49 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 4 Mar 2020 12:45:39 +0100 Subject: [PATCH 111/290] add CR013 because TypeOfValue is needed for CR002 --- xsd/siri_utility/siri_utility-v1.1.xsd | 218 ++++++++++++++++++++++++- 1 file changed, 217 insertions(+), 1 deletion(-) diff --git a/xsd/siri_utility/siri_utility-v1.1.xsd b/xsd/siri_utility/siri_utility-v1.1.xsd index aa4bf7a6..4029f65f 100644 --- a/xsd/siri_utility/siri_utility-v1.1.xsd +++ b/xsd/siri_utility/siri_utility-v1.1.xsd @@ -1,6 +1,6 @@ - + @@ -80,4 +80,220 @@ Rail transport, Roads and road transport + + + + A list of alternative Key values for an element. +SIRI v2.1 + + + + Every Key Value Pair must be unique. + + + + + + + + + Type for a Key List. +SIRI v2.1 + + + + + Key value pair for Entity. + + + + + + + Type for a Key List. +SIRI v2.1 + + + + + Identifier of value e.g. System. + + + + + Value for alternative key. + + + + + Identifier of type of key. + + + + + + + + VALUE SETs and TYPE OF VALUEs as part of the SIRI extension model. +TYPES OF VALUE can be used to exchange metadata for validation or collection of data, +such as the description and allowed values for codes. +SIRI v2.1 + + + + VALUE SETs must be unique. + + + + + + + + Type for containment of VALUE SETs and/or TYPE OF VALUEs. +SIRI v2.1 + + + + + + + + + A code value from an extensible set which may be added to by user applications, and is used to classify other SIRI entities. +SIRI v2.1 + + + + + Type for a TYPE OF VALUE. Used to define open classifications of value types. +SIRI v2.1 + + + + + Identifier of a TYPE OF VALUE. + + + + + Name of class of which TypeOfValue is an instance. + + + + + + + + Elements for TYPE OF VALUE. +SIRI v2.1 + + + + + Name of TYPE OF VALUE. + + + + + Short Name for TYPE OF VALUE. + + + + + Description of TYPE OF VALUE. + + + + + Default image for TYPE OF VALUE. + + + + + Default URL for TYPE OF VALUE. + + + + + Arbitrary code (usually the technical part of the identifier). + + + + + + + An extensible set of code values which may be added to by user applications and is used to validate the properties of entities. +Contains TYPE OF VALUEs that are an instance of the same class. +SIRI v2.1 + + + + TYPE OF VALUEs of the set must be unique. + + + + + + + + Type for a VALUE SET. Used to define open classifications of value types. +SIRI v2.1 + + + + + Identifier of VALUE SET. + + + + + Name of Class of values in set. + + + + + + + + Elements for VALUE SET. +SIRI v2.1 + + + + + Name of set. + + + + + Values in set. + + + + + + + Type for a list of TYPE OF VALUEs. +SIRI v2.1 + + + + + + + + + Type for identifier of a TYPE OF VALUE. +SIRI v2.1 + + + + + + Type for reference to a TYPE OF VALUE. +SIRI v2.1 + + + + + + + + Type for identifier of a VALUE SET. +SIRI v2.1 + + + + + + Name of class of which TypeOfValue is an instance. Used for reflection. +SIRI v2.1 + + + + From ea0c865fe72ac40f163da53d2dceb4c248b36d13 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Fri, 11 Oct 2019 00:00:58 +0200 Subject: [PATCH 112/290] CR054: add ExtraCall and Cancellation to DatedCall --- xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd index f0b4f821..d2efbb97 100644 --- a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd @@ -492,6 +492,18 @@ Rail transport, Roads and road transport + + + + This DATED CALL is additional and unplanned. If omitted: CALL is planned. + + + + + This DATED CALL is a cancellation of a previously announced call. + + + From b0b56a2fa3d0a82d969648e06ba99a019f60ec4a Mon Sep 17 00:00:00 2001 From: Adrian A Date: Mon, 9 Mar 2020 16:57:11 +0100 Subject: [PATCH 113/290] CR070: add RemovedXX elements in DatedVersionFrame --- xsd/siri_productionTimetable_service.xsd | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/xsd/siri_productionTimetable_service.xsd b/xsd/siri_productionTimetable_service.xsd index e5395994..3d77f591 100644 --- a/xsd/siri_productionTimetable_service.xsd +++ b/xsd/siri_productionTimetable_service.xsd @@ -294,11 +294,27 @@ If false each subscription response will contain the full information as specifi Complete list of all planned VEHICLE JOURNEYs for this LINE and DIRECTION. + + + + List of all removed VEHICLE JOURNEYs for this LINE and DIRECTION. +A data producer may silently remove a journey from the plan if it was previously provided in error. Careful: Removal is different from Cancellation. +Minimal information, or no information at all, of a RemovedDatedVehicleJourney or the removal itself must be communicated to the passengers, i.e., it is "silently" removed. A Cancellation, on the other hand, is possibly the most important information to provide to the passengers. +It is strongly advised to only use this feature in cases where a journey was sent in error and it can be assumed that as few passengers as possible have seen the erroneous information to avoid confusion. +SIRI v2.1 + Connection paramters for a SERVICE JOURNEY INTERCHANGE between a feeder and distributor journey. SIRI 2.0 + + + + List of all removed SERVICE JOURNEY INTERCHANGEs. +A data producer may silently remove an interchange from the plan if it was previously provided in error. Careful: Removal is different from Cancellation. +Minimal information, or no information at all, of a RemovedServiceJourneyInterchange or the removal itself must be communicated to the passengers, i.e., it is "silently" removed. A Cancellation, on the other hand, is possibly the most important information to provide to the passengers. +It is strongly advised to only use this feature in cases where an interchange was sent in error and it can be assumed that as few passengers as possible have seen the erroneous information to avoid confusion. +SIRI v2.1 + From dad3c259cfbf8b136a86e6041e1e892802e87db8 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 7 Jan 2020 17:31:54 +0100 Subject: [PATCH 114/290] CR024: add aimed times to interchange feed./distr. --- .../siri_datedVehicleJourney-v2.0.xsd | 80 +++++++++++++++++++ 1 file changed, 80 insertions(+) diff --git a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd index d2efbb97..9cc7a50e 100644 --- a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd @@ -237,6 +237,16 @@ Rail transport, Roads and road transport Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 + + + + + Planned time at which feeder VEHICLE is scheduled to arrive. SIRI v2.1 + + Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 @@ -252,6 +262,16 @@ Rail transport, Roads and road transport Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 + + + + + Planned time at which distributor VEHICLE is scheduled to depart. SIRI v2.1 + + @@ -290,6 +310,16 @@ Rail transport, Roads and road transport Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 + + + + + Planned time at which feeder VEHICLE is scheduled to arrive. SIRI v2.1 + + Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 @@ -305,6 +335,16 @@ Rail transport, Roads and road transport Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 + + + + + Planned time at which distributor VEHICLE is scheduled to depart. SIRI v2.1 + + @@ -345,6 +385,16 @@ Rail transport, Roads and road transport Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 + + + + + Planned time at which feeder VEHICLE is scheduled to arrive. SIRI v2.1 + + Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 @@ -360,6 +410,16 @@ Rail transport, Roads and road transport Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 + + + + + Planned time at which distributor VEHICLE is scheduled to depart. SIRI v2.1 + + @@ -400,6 +460,16 @@ Rail transport, Roads and road transport Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 + + + + + Planned time at which feeder VEHICLE is scheduled to arrive. SIRI v2.1 + + Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 @@ -415,6 +485,16 @@ Rail transport, Roads and road transport Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 + + + + + Planned time at which distributor VEHICLE is scheduled to depart. SIRI v2.1 + + From ab5754a0c42abf3088ea48573e168cc3c39a2d1e Mon Sep 17 00:00:00 2001 From: Adrian A Date: Mon, 9 Mar 2020 16:55:25 +0100 Subject: [PATCH 115/290] CR070: add RemovedX and harmonize InterchangeStruc --- .../siri_datedVehicleJourney-v2.0.xsd | 512 ++++++++---------- 1 file changed, 237 insertions(+), 275 deletions(-) diff --git a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd index 9cc7a50e..68d12c1b 100644 --- a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd @@ -132,6 +132,46 @@ Rail transport, Roads and road transport + + + Type for previously planned VEHICLE JOURNEY that is removed from the data producer when using incremental updates. +SIRI v2.1 + + + + + A reference to the dated VEHICLE JOURNEY (from a previous delivery) that is removed by the data producer. + + + + + The data producer must provide a reason, e.g. type of error and description, in case he wants to silently remove (instead of cancel) a journey from the plan. +SIRI v2.1 + + + + + + + + + + + + Complete sequence of stops along the route path, in calling order. + + + + + + + + + + Relations of the journey with other journeys, e.g., in case a joining/splitting takes place or the journey substitutes for another one etc. + + + + + General info elements that apply to all journeys of timetable version unless overriden. @@ -183,7 +223,7 @@ Rail transport, Roads and road transport - Whether this journey is a deletion of a journey in the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': Journey is not a deletion. + Whether this journey is a cancellation of a journey in the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the journey is not cancelled. @@ -212,66 +252,26 @@ Rail transport, Roads and road transport A planned SERVICE JOURNEY INTERCHANGE between two journeys. +SIRI v2.0 - - - Identifier of SERVICE JOURNEY INTERCHANGE. +SIRI v2.0 - - - - - Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY INTERCHANGE takes place. +SIRI v2.0 - - - - - Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 - - - - - SCHEDULED STOP POINT at which feeder journey arrives. +SIRI v2.0 - - - - - Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. - - - - - For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 - - - - - Planned time at which feeder VEHICLE is scheduled to arrive. SIRI v2.1 - - - - - Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 - - - - - SCHEDULED STOP POINT at which distributor journet departs. +SIRI v2.0 - - - - - Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. - - - - - For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 - - - - - Planned time at which distributor VEHICLE is scheduled to depart. SIRI v2.1 - - + + + + + + + + + + + + + + + + + + + + @@ -285,66 +285,18 @@ Rail transport, Roads and road transport - - - Identifier of SERVICE JOURNEY INTERCHANGE. +SIRI v2.0 - - - - - Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY INTERCHANGE takes place. +SIRI v2.0 - - - - - Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 - - - - - SCHEDULED STOP POINT at which feeder journey arrives. +SIRI v2.0 - - - - - Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. - - - - - For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 - - - - - Planned time at which feeder VEHICLE is scheduled to arrive. SIRI v2.1 - - - - - Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 - - - - - SCHEDULED STOP POINT at which distributor journet departs. +SIRI v2.0 - - - - - Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. - - - - - For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 - - - - - Planned time at which distributor VEHICLE is scheduled to depart. SIRI v2.1 - - + + + + + + + + + + + + @@ -360,66 +312,18 @@ Rail transport, Roads and road transport - - - Identifier of SERVICE JOURNEY INTERCHANGE. +SIRI v2.0 - - - - - Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY INTERCHANGE takes place. +SIRI v2.0 - - - - - Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 - - - - - SCHEDULED STOP POINT at which feeder journey arrives. +SIRI v2.0 - - - - - Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. - - - - - For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 - - - - - Planned time at which feeder VEHICLE is scheduled to arrive. SIRI v2.1 - - - - - Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 - - - - - SCHEDULED STOP POINT at which distributor journet departs. +SIRI v2.0 - - - - - Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. - - - - - For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 - - - - - Planned time at which distributor VEHICLE is scheduled to depart. SIRI v2.1 - - + + + + + + + + + + + + @@ -435,66 +339,50 @@ Rail transport, Roads and road transport - - - Identifier of SERVICE JOURNEY INTERCHANGE. +SIRI v2.0 - - - - - Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY INTERCHANGE takes place. +SIRI v2.0 - - - - - Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 - - - - - SCHEDULED STOP POINT at which feeder journey arrives. +SIRI v2.0 - - - - - Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. - - - - - For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 - - - - - Planned time at which feeder VEHICLE is scheduled to arrive. SIRI v2.1 - - - - - Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 - - - - - SCHEDULED STOP POINT at which distributor journet departs. +SIRI v2.0 - - - - - Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. - - - - - For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 - - - - - Planned time at which distributor VEHICLE is scheduled to depart. SIRI v2.1 - - + + + + + + + + + + + + + + + + + + + + + + + + + + + Type for a previously planned SERVICE JOURNEY INTERCHANGE that a data producer wants to silently remove from the plan (because it is erroneous data). Careful: Removal is different from Cancellation. +SIRI v2.1 + + + + + + + + + + + + + + + + + @@ -573,14 +461,14 @@ Rail transport, Roads and road transport - + - This DATED CALL is additional and unplanned. If omitted: CALL is planned. + Whether this DATED CALL is an addition to the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to false: the journey is not an addition. - + - This DATED CALL is a cancellation of a previously announced call. + Whether this DATED CALL is a cancellation of a previously announced call (or planned according to the long-term timetable). Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the journey is not cancelled. @@ -620,39 +508,15 @@ Rail transport, Roads and road transport - - - Identifier of SERVICE JOURNEY INTERCHANGE. - - - - - Reference to a (dated) distributor VEHICLE JOURNEY. - - + + - - - Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY 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. - - + + @@ -748,5 +612,103 @@ Rail transport, Roads and road transport + + + + Identifier of SERVICE JOURNEY INTERCHANGE. +SIRI v2.0 + + + + + Reference to a SERVICE JOURNEY INTERCHANGE from a previous PT message or the long-term timetable. +SIRI v2.1 + + + + + Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY INTERCHANGE takes place. +SIRI v2.0 + + + + + Whether this interchange is an addition to the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the interchange is not an addition. +SIRI v2.1 + + + + + Whether this interchange is a cancellation of a previously announced interchange (or planned according to the long-term timetable. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the interchange is not cancelled. +SIRI v2.1 + + + + + The data producer must provide a reason, e.g. type of error and description, in case he wants to silently remove (instead of cancel) an interchange from the plan. +SIRI v2.1 + + + + + Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 + + + + + SCHEDULED STOP POINT at which feeder journey arrives. +SIRI v2.0 + + + + + Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. + + + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. +ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 + + + + + Planned time at which feeder VEHICLE is scheduled to arrive. SIRI v2.1 + + + + + Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 + + + + + SCHEDULED STOP POINT at which distributor journet departs. +SIRI v2.0 + + + + + Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. + + + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. +ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 + + + + + Planned time at which distributor VEHICLE is scheduled to depart. SIRI v2.1 + + + + + Reference to a (dated) distributor VEHICLE JOURNEY. + + + + + Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY 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. + + From 16516e72224d0b544614854b9032411d3b75843f Mon Sep 17 00:00:00 2001 From: Adrian A Date: Mon, 9 Mar 2020 17:29:57 +0100 Subject: [PATCH 116/290] remove useless comment --- xsd/siri_model/siri_all_journeyModel-v2.0.xsd | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/xsd/siri_model/siri_all_journeyModel-v2.0.xsd b/xsd/siri_model/siri_all_journeyModel-v2.0.xsd index ba58b576..c7bf5428 100644 --- a/xsd/siri_model/siri_all_journeyModel-v2.0.xsd +++ b/xsd/siri_model/siri_all_journeyModel-v2.0.xsd @@ -18,6 +18,4 @@ - - - \ No newline at end of file + \ No newline at end of file From 9cd3ed322b33a9b995fba30e73c138111a80409c Mon Sep 17 00:00:00 2001 From: Adrian A Date: Mon, 9 Mar 2020 18:00:36 +0100 Subject: [PATCH 117/290] CR070:cleanup refs after interchange harmonization --- .../siri_datedVehicleJourney-v2.0.xsd | 152 +++++++++--------- xsd/siri_productionTimetable_service.xsd | 4 +- 2 files changed, 78 insertions(+), 78 deletions(-) diff --git a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd index 68d12c1b..dbb3d245 100644 --- a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd @@ -144,7 +144,7 @@ Rail transport, Roads and road transport - The data producer must provide a reason, e.g. type of error and description, in case he wants to silently remove (instead of cancel) a journey from the plan. +SIRI v2.1 + The data producer must provide a reason, e.g. type of error and description, in case he wants to silently remove (instead of cancel) a journey from the plan. +SIRI v2.1 @@ -253,25 +253,25 @@ Rail transport, Roads and road transport - - + + - + - - + + - - - - - - - - - - - + + + + + + + + + + + @@ -285,18 +285,18 @@ Rail transport, Roads and road transport - - - - - - - - - - - - + + + + + + + + + + + + @@ -312,18 +312,18 @@ Rail transport, Roads and road transport - - - - - - - - - - - - + + + + + + + + + + + + @@ -339,22 +339,22 @@ Rail transport, Roads and road transport - - - - - + + + + + - - - - - - - - - - + + + + + + + + + + @@ -370,19 +370,19 @@ Rail transport, Roads and road transport - - - - - - - - - - - - - + + + + + + + + + + + + + @@ -508,15 +508,15 @@ Rail transport, Roads and road transport - - + + - - + + - - + + @@ -640,7 +640,7 @@ Rail transport, Roads and road transport - The data producer must provide a reason, e.g. type of error and description, in case he wants to silently remove (instead of cancel) an interchange from the plan. +SIRI v2.1 + The data producer must provide a reason, e.g. type of error and description, in case he wants to silently remove (instead of cancel) an interchange from the plan. +SIRI v2.1 diff --git a/xsd/siri_productionTimetable_service.xsd b/xsd/siri_productionTimetable_service.xsd index 3d77f591..caaabf60 100644 --- a/xsd/siri_productionTimetable_service.xsd +++ b/xsd/siri_productionTimetable_service.xsd @@ -295,7 +295,7 @@ If false each subscription response will contain the full information as specifi Complete list of all planned VEHICLE JOURNEYs for this LINE and DIRECTION. - + List of all removed VEHICLE JOURNEYs for this LINE and DIRECTION. A data producer may silently remove a journey from the plan if it was previously provided in error. Careful: Removal is different from Cancellation. @@ -308,7 +308,7 @@ It is strongly advised to only use this feature in cases where a journey was sen Connection paramters for a SERVICE JOURNEY INTERCHANGE between a feeder and distributor journey. SIRI 2.0 - + List of all removed SERVICE JOURNEY INTERCHANGEs. A data producer may silently remove an interchange from the plan if it was previously provided in error. Careful: Removal is different from Cancellation. From ef4e737c0da203286769660dfa1c51177ec782aa Mon Sep 17 00:00:00 2001 From: Adrian A Date: Mon, 9 Mar 2020 18:07:11 +0100 Subject: [PATCH 118/290] CR070: small correction in RemovedDatedVehicleJrny --- xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd index dbb3d245..ccca02f8 100644 --- a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd @@ -137,9 +137,9 @@ Rail transport, Roads and road transport Type for previously planned VEHICLE JOURNEY that is removed from the data producer when using incremental updates. +SIRI v2.1 - + - A reference to the dated VEHICLE JOURNEY (from a previous delivery) that is removed by the data producer. + A reference to the dated VEHICLE JOURNEY from a previous PT delivery that is removed by the data producer. From 085fa601f6793531f0f8ab33420dbf14674a67c6 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Mon, 9 Mar 2020 18:25:40 +0100 Subject: [PATCH 119/290] CR070: clean-up TargetedInterchangeStructure --- .../siri_datedVehicleJourney-v2.0.xsd | 49 ++++++++----------- 1 file changed, 20 insertions(+), 29 deletions(-) diff --git a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd index ccca02f8..3d002d33 100644 --- a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd @@ -509,14 +509,30 @@ Rail transport, Roads and road transport - + + + Reference to a (dated) distributor VEHICLE JOURNEY. + + - - + + + Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY 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. + + - + + + 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. + + @@ -618,16 +634,6 @@ Rail transport, Roads and road transport Identifier of SERVICE JOURNEY INTERCHANGE. +SIRI v2.0 - - - Reference to a SERVICE JOURNEY INTERCHANGE from a previous PT message or the long-term timetable. +SIRI v2.1 - - - - - Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY INTERCHANGE takes place. +SIRI v2.0 - - Whether this interchange is an addition to the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the interchange is not an addition. +SIRI v2.1 @@ -695,20 +701,5 @@ ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL i Planned time at which distributor VEHICLE is scheduled to depart. SIRI v2.1 - - - Reference to a (dated) distributor VEHICLE JOURNEY. - - - - - Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY 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. - - From f7ff1376e1c80b99339b68762d74ec971d4901e8 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Thu, 12 Mar 2020 11:47:58 +0100 Subject: [PATCH 120/290] CR074: add LatestExpectedArrivalTime to ETCall --- xsd/siri_model/siri_journey-v2.0.xsd | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index b95675a7..4cef0f6e 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -594,9 +594,14 @@ Rail transport, Roads and road transport + + + Latest time at which a VEHICLE will arrive at stop. +SIRI v2.1 + + - Prediction quality, either as approximate level, or more quantitayive percentile range of predictions will fall within a given range of times. +SIRI v2.0 + Prediction quality, either as approximate level, or more quantitative percentile range of predictions that will fall within a given range of times. +SIRI v2.0 From f850c100f5eae4eea9747e40e5b75887cb76a20a Mon Sep 17 00:00:00 2001 From: Adrian A Date: Thu, 12 Mar 2020 13:34:55 +0100 Subject: [PATCH 121/290] CR032: add new flag IncludeOnlyRecordedCallUpdates --- xsd/siri_estimatedTimetable_service.xsd | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/xsd/siri_estimatedTimetable_service.xsd b/xsd/siri_estimatedTimetable_service.xsd index 8bf2e7de..9cec4b8e 100644 --- a/xsd/siri_estimatedTimetable_service.xsd +++ b/xsd/siri_estimatedTimetable_service.xsd @@ -245,11 +245,21 @@ If false each subscription response will contain the full information as specifi Indicates whether actual arrival-/departure times should be delivered as incremental updates, i.e. whether RECORDED CALL updates are transmitted immediately after an event occurs. +SIRI v2.1 -- 'false': Specifies that the data producer should transmit RECORDED CALL data, in particular actual arrival-/departure information as an incremental update immediately after an event occurs (with hysteresis taken into account). +- 'false': Specifies that the data producer should transmit RECORDED CALL data, in particular actual arrival-/departure information as an incremental update immediately after an event occurs (with hysteresis taken into account) as it is generally the case. The server will automatically proceed with 'false' if capability is not supported. - 'true': Can be requested if the data traffic is to be reduced and an immediate transmissions is not required in any of the consumer systems. -'false' specifies that the data producer should skip RECORDED CALL updates (if capability is supported after all), i.e., deliver them with the next update instead. -No specification: Default value 'false' applies (don't skip updates of recorded data). +'true' specifies that the data producer should skip RECORDED CALL updates (if capability is supported after all), i.e., deliver them with the next update instead. +- No specification: Default value 'false' applies (don't skip updates of recorded data). + + + + + Indicates whether ONLY actual arrival-/departure times should be delivered. In other words, whether all updates related to ESTIMATED CALL should be skipped. +SIRI v2.1 +- 'false': Specifies that the data producer should transmit ESTIMATED and RECORDED CALL data as an incremental update immediately after an event occurs (with hysteresis taken into account) as it is generally the case. +The server will automatically proceed with 'false' if capability is not supported. +- 'true': Can be requested if a consumer system is only interested in the actual times / recorded events because it only wants to check the performance for example. +'true' specifies that the data producer should only deliver RECORDED CALL udpates and skip ESTIMATED CALL updates (if capability is supported after all), i.e., deliver ESTIMATED CALL updates only with the next RECORDED CALL update. +- No specification: Default value 'false' applies (don't skip updates of estimated data). From 0eb474fd98e97f1ab5cb5b8235d21c5a16cd4e3d Mon Sep 17 00:00:00 2001 From: Korbinian Grimme Date: Thu, 12 Mar 2020 14:17:32 +0100 Subject: [PATCH 122/290] PublicationWindows is unbounded in SIRI documentation, now the XSD also reflects this --- xsd/siri_model/siri_situation-v2.0.xsd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xsd/siri_model/siri_situation-v2.0.xsd b/xsd/siri_model/siri_situation-v2.0.xsd index 905ed0e0..591415b6 100644 --- a/xsd/siri_model/siri_situation-v2.0.xsd +++ b/xsd/siri_model/siri_situation-v2.0.xsd @@ -651,7 +651,7 @@ Rail transport, Roads and road transport - + Publication Window for SITUATION if different from validity period. From 398c12f6773e3c3042cf12c5c129eefc1183a000 Mon Sep 17 00:00:00 2001 From: Korbinian Grimme Date: Thu, 12 Mar 2020 14:18:14 +0100 Subject: [PATCH 123/290] Period is unbounded in SIRI documentation, now the XSD also reflects this --- xsd/siri_model/siri_situation-v2.0.xsd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xsd/siri_model/siri_situation-v2.0.xsd b/xsd/siri_model/siri_situation-v2.0.xsd index 591415b6..d5e774ae 100644 --- a/xsd/siri_model/siri_situation-v2.0.xsd +++ b/xsd/siri_model/siri_situation-v2.0.xsd @@ -1119,7 +1119,7 @@ Rail transport, Roads and road transport Type for disruption. - + Period of effect of disruption, if different from that of SITUATION. From 0ef110167b135e7ac97ed37dfa7017e2631262b9 Mon Sep 17 00:00:00 2001 From: Korbinian Grimme Date: Thu, 12 Mar 2020 14:20:25 +0100 Subject: [PATCH 124/290] DeparturePlatformName is unbounded in SIRI documentation, now the XSD also reflects this --- xsd/siri_model/siri_situationAffects-v2.0.xsd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xsd/siri_model/siri_situationAffects-v2.0.xsd b/xsd/siri_model/siri_situationAffects-v2.0.xsd index 8eca886d..5d445c09 100644 --- a/xsd/siri_model/siri_situationAffects-v2.0.xsd +++ b/xsd/siri_model/siri_situationAffects-v2.0.xsd @@ -962,7 +962,7 @@ Rail transport, Roads and road transport - + From 30671c5e46158b76e3bf7f0153a0fc758cb35615 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Mon, 16 Mar 2020 13:18:10 +0100 Subject: [PATCH 125/290] CR029: change annotations of XXXPredictionUnknown --- xsd/siri_model/siri_journey-v2.0.xsd | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index 6fcc53d9..901705d5 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -602,15 +602,15 @@ Rail transport, Roads and road transport - - - If the producer is (temporarily) not able to deliver real-time predictions (e.g. because of a connection loss), he has various options to inform the consumer: + + + If the producer is (temporarily) not able to deliver real-time predictions (e.g. because of a connection loss), he has various options (and combinations of them) to inform the consumer: (i) set Monitored to 'false' -(ii) transmit ExpectedTime together with "PredictionInaccurate=true" -(iii) drop/omit ExpectedTimes +(ii) transmit ExpectedArrivalTime together with "PredictionInaccurate=true" +(iii) drop/omit ExpectedArrivalTime (iv) set ArrivalStatus to 'noReport' -However, option (iii) might introduce ambiguity: one consumer might interpret it as "on time" and another one as "indefinite delay". -To avoid this, the producer should transmit xxxPredictionUnknown instead of any ExpectedTimes. +SIRI v2.1 +However, this might introduce ambiguity: e.g. option (iii) might be interpreted as "on time" by one consumer, but also as "indefinite delay" by another consumer. +To avoid this, the producer should transmit xxxPredictionUnknown instead of any expected times. +SIRI v2.1 @@ -651,13 +651,13 @@ To avoid this, the producer should transmit xxxPredictionUnknown instead of any - If the producer is (temporarily) not able to deliver real-time predictions (e.g. because of a connection loss), he has various options to inform the consumer: + If the producer is (temporarily) not able to deliver real-time predictions (e.g. because of a connection loss), he has various options (and combinations of them) to inform the consumer: (i) set Monitored to 'false' -(ii) transmit ExpectedTime together with "PredictionInaccurate=true" -(iii) drop/omit ExpectedTimes -(iv) set ArrivalStatus to 'noReport' -However, option (iii) might introduce ambiguity: one consumer might interpret it as "on time" and another one as "indefinite delay". -To avoid this, the producer should transmit xxxPredictionUnknown instead of any ExpectedTimes. +SIRI v2.1 +(ii) transmit ExpectedDepartureTime together with "PredictionInaccurate=true" +(iii) drop/omit ExpectedDepartureTime +(iv) set DepartureStatus to 'noReport' +However, this might introduce ambiguity: e.g. option (iii) might be interpreted as "on time" by one consumer, but also as "indefinite delay" by another consumer. +To avoid this, the producer should transmit xxxPredictionUnknown instead of any expected times. +SIRI v2.1 From 58aae66047aa63c86ee3acd30f5a78182388ad01 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Mon, 16 Mar 2020 20:13:42 +0100 Subject: [PATCH 126/290] CR002: correct var. annotations of formation model --- .../siri_estimatedVehicleJourney-v2.0.xsd | 4 +- xsd/siri_model/siri_facility-v2.0.xsd | 2 +- xsd/siri_model/siri_journey-v2.0.xsd | 44 ++++++++++++------- xsd/siri_model/siri_journey_support-v2.0.xsd | 9 ++-- 4 files changed, 36 insertions(+), 23 deletions(-) diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index 81f2f19d..9b2013b0 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -410,7 +410,7 @@ the original journey and the nature of the difference. - Recorded occupancies and capacities of a vehicle (by fare classes) after departing at a given STOP POINT. +SIRI v2.1 + Recorded occupancies and capacities of a vehicle (by fare classes) when arriving at a given STOP POINT. +SIRI v2.1 @@ -455,7 +455,7 @@ the original journey and the nature of the difference. - Recorded occupancies and capacities of a vehicle (by fare classes) after departing at a given STOP POINT. +SIRI v2.1 + Recorded occupancies and capacities of a vehicle (by fare classes) when departing at a given STOP POINT. +SIRI v2.1 diff --git a/xsd/siri_model/siri_facility-v2.0.xsd b/xsd/siri_model/siri_facility-v2.0.xsd index 3b16c4bc..076142ad 100644 --- a/xsd/siri_model/siri_facility-v2.0.xsd +++ b/xsd/siri_model/siri_facility-v2.0.xsd @@ -703,7 +703,7 @@ Rail transport, Roads and road transport - Information about a change of Equipment availabilty at stop or on vehicle that may affect access or use. + Information about a change of Equipment availability at stop or on vehicle that may affect access or use. diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index 0192664b..ddabba72 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -504,7 +504,13 @@ Rail transport, Roads and road transport Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). If not given, assume same as for departure. +SIRI v2.1 - + + + Indication of the direction of travel of the vehicle or formation (e.g. TRAIN composition ) with respect to the platform, or more precisely the QUAY. +For example "towards A", which means that the vehicle departs towards sector "A" of the QUAY. It is advised to specify a reference point that is meaningful for passengers on location. +Unbounded to allow multiple languages. +SIRI v2.1 + + Real-time occupancies and capacities of a vehicle (by fare classes) when arriving at a given STOP POINT. +SIRI v2.1 @@ -526,7 +532,7 @@ Rail transport, Roads and road transport - Departure QUAY ( Bay or platform) name. Defaulted taken from from planned timetable.. + Departure QUAY (Bay or platform) name. Default taken from planned timetable.. @@ -540,10 +546,16 @@ Rail transport, Roads and road transport Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). +SIRI v2.1 - + + + Indication of the direction of travel of the vehicle or formation (e.g. TRAIN composition ) with respect to the platform, or more precisely the QUAY. +For example "towards A", which means that the vehicle departs towards sector "A" of the QUAY. It is advised to specify a reference point that is meaningful for passengers on location. +Unbounded to allow multiple languages. +SIRI v2.1 + + - Real-time occupancies and capacities of a vehicle (by fare classes) after departing at a given STOP POINT. +SIRI v2.1 + Real-time occupancies and capacities of a vehicle (by fare classes) when departing at a given STOP POINT. +SIRI v2.1 @@ -957,7 +969,7 @@ A QUAY may be part of a group of QUAYs, or may be divided into sectors, i.e., sm Groups relevant elements of the formation model that are used on JOURNEY level. -The TRAIN Conceptual represents VEHICLE TYPE properties that are peculiar to TRAINs. A TRAIN may comprise not just a single VEHICLE but a chain of carriages, TRAIN ELEMENTS, assembled as TRAIN COMPONENTs. +The TRAIN conceptual model represents VEHICLE TYPE properties that are peculiar to TRAINs. A TRAIN may comprise not just a single VEHICLE but a chain of carriages, TRAIN ELEMENTS, assembled as TRAIN COMPONENTs. Groups of carriages may be managed as sections by composing TRAINs into a COMPOUND TRAIN made up of multiple TRAIN IN COMPOUND TRAIN, for example in a train that joins or splits. +SIRI v2.1 @@ -1233,12 +1245,12 @@ More accurate data can be provided by the individual occupancies or capacities b Total number of wheelchairs on-board after departing the STOP POINT. - + Total number of prams on-board after departing the STOP POINT. - + Total number of bicycles on-board, i.e., number of bicycle racks that are occupied after departing the STOP POINT. @@ -1265,7 +1277,7 @@ More accurate data can be provided by the individual occupancies or capacities b - Occupancies and real-time capacities of a vehicle (by fare classes) after departing a given STOP POINT. +SIRI v2.1 + Occupancies and real-time capacities of a vehicle (by fare classes). +SIRI v2.1 @@ -1307,7 +1319,7 @@ More accurate data can be provided by the individual occupancies or capacities b - A vehicle composed of TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 + An elementary component of a TRAIN, e.g. wagon or locomotive. +SIRI v2.1 @@ -1350,7 +1362,7 @@ More accurate data can be provided by the individual occupancies or capacities b - A vehicle composed of TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 + An assembled TRAIN ELEMENT as part of a TRAIN, i.e., a TRAIN ELEMENT with a certain position or order within a TRAIN. +SIRI v2.1 @@ -1365,7 +1377,7 @@ More accurate data can be provided by the individual occupancies or capacities b - Order of TRAIN ELEMENT within TRAIN. + Order of the TRAIN COMPONENT (or more precisely the referenced TRAIN ELEMENT) within the TRAIN. @@ -1400,7 +1412,7 @@ More accurate data can be provided by the individual occupancies or capacities b - A vehicle composed of TRAIN ELEMENTs in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 + A vehicle composed of TRAIN ELEMENTs assembled in a certain order (so called TRAIN COMPONENTs), i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 @@ -1448,7 +1460,7 @@ More accurate data can be provided by the individual occupancies or capacities b - Groups of carriages may be managed as sections by composing TRAINs into a COMPOUND TRAIN, for example in a train that joins or splits. +SIRI v2.1 + Groups of carriages may be managed as sections by composing TRAINs into a COMPOUND TRAIN, for example if a train joins (or splits from) another train. +SIRI v2.1 @@ -1553,7 +1565,7 @@ More accurate data can be provided by the individual occupancies or capacities b - Elements for a VEHICLE. TYPE. +SIRI v2.1 + Elements for a VEHICLE TYPE. +SIRI v2.1 @@ -1575,7 +1587,7 @@ More accurate data can be provided by the individual occupancies or capacities b - Facilities of TRAIN ELEMENT. + Facilities of VEHICLE TYPE. @@ -1591,7 +1603,7 @@ More accurate data can be provided by the individual occupancies or capacities b - Prooprty Elements for a VEHICLE. TYPE. +SIRI v2.1 + Property elements for the abstract VEHICLE TYPE. +SIRI v2.1 diff --git a/xsd/siri_model/siri_journey_support-v2.0.xsd b/xsd/siri_model/siri_journey_support-v2.0.xsd index 2b7accb3..3da3fe58 100644 --- a/xsd/siri_model/siri_journey_support-v2.0.xsd +++ b/xsd/siri_model/siri_journey_support-v2.0.xsd @@ -418,7 +418,7 @@ Rail transport, Roads and road transport - Goups together the relevant references needed in a formation. + Groups together the relevant references needed in a formation. Either the smallest part of a formation, a TRAIN COMPONENT, is referenced or the TRAIN itself. If the formation consists of multiple coupled TRAINs, a reference to the COMPOUND TRAIN is possible too. @@ -734,7 +734,7 @@ The first class carriage of a TRAIN might, for example, be assigned to sector "A - Allowed values for TYPE OF TRAIN ELEMENT. +SIRI v2.1 + Allowed values for TRAIN SIZE. +SIRI v2.1 @@ -744,7 +744,7 @@ The first class carriage of a TRAIN might, for example, be assigned to sector "A - Allowed values for type of fuel. +SIRI v2.1 + Allowed values for TYPE OF FUEL. +SIRI v2.1 @@ -752,6 +752,7 @@ The first class carriage of a TRAIN might, for example, be assigned to sector "A + @@ -805,7 +806,7 @@ The first class carriage of a TRAIN might, for example, be assigned to sector "A - Busienss Class - pti23_10 + Business Class - pti23_10 From 74c32575effb88c8b5772ad473331e7c29c42de4 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 17 Mar 2020 15:40:51 +0100 Subject: [PATCH 127/290] CR022: harmonize InterchangeStatusEnum with CR015 --- .../siri_situationServiceTypes-v1.0.xsd | 87 +++++++++++-------- 1 file changed, 53 insertions(+), 34 deletions(-) diff --git a/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd b/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd index 88a45920..93d97383 100644 --- a/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd +++ b/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd @@ -118,69 +118,88 @@ Rail transport, Roads and road transport Values for Interchange Status TPEG cross reference pti_table 31. - + + + TPEG Pti31_0, unknown + + + - Interchange is planned. + TPEG Pti31_1, connection - + - Interchange is planned but was updated as a result of changes in the QUAYs or arrival/departure times. + TPEG Pti31_2, replacement + + + + + TPEG Pti31_3, alternative + + + + + TPEG Pti31_4, connection not held + + + + + TPEG Pti31_5, connection held + + + + + TPEG Pti31_6, status of connection undecided + + + + + TPEG Pti31_255, undefined cross reference information + + + + + deprecated (SIRI 2.1) - use statusOfConnectionUndecided + + + + + Interchange is planned but was updated as a result of changes in the QUAYs or arrival/departure times. Can be used if the status is a combination of the other values. +SIRI v2.1 - An important function of connection protection is the ability to hold back a distributor VEHICLE (i.e. prolonged waiting) -to allow passengers to transfer from delayed feeders. To achieve this a distributorWaitProlonged status shall be communicated back to the feeder VEHICLEs to inform -the passengers about the new departure time of the distributor or even a willWait guarantee. + An important function of connection protection is the ability to hold back a distributor VEHICLE (i.e. prolonged waiting) to allow passengers to transfer from delayed feeders. +To achieve this a distributorWaitProlonged status shall be communicated back to the feeder VEHICLEs to inform the passengers about the new departure time of the distributor or even a willWait guarantee. +SIRI v2.1 - Interchange is planned but was updated as a result of changes in the QUAYs or arrival/departure times. + Used to provide the passengers with information about a new departure platform of the distributor VEHICLE if the distributor changes its planned stopping position. +SIRI v2.1 - + - Interchange is an addition to the plan. + Interchange is an addition to the plan. +SIRI v2.1 - Interchange is a cancellation of an interchange in the plan. + Interchange is a cancellation of an interchange in the plan. +SIRI v2.1 - Loss of the inbound connection indicates the cancellation of the visit (of the FeederJourney) to the FeederArrivalStop, or a severely delayed arrival. -This can lead to the distributor VEHICLE abandoning the connection. There are several possible reasons for the loss of a feeder, e.g. loss/cancellation of the feeder VEHICLE, diversion of the feeder LINE/DIRECTION, disruption of a LINE section etc. + Loss of the inbound connection indicates the cancellation of the visit (of the FeederJourney) to the FeederArrivalStop, or a severely delayed arrival. This can lead to the distributor VEHICLE abandoning the connection. +There are several possible reasons for the loss of a feeder, e.g. loss/cancellation of the feeder VEHICLE, diversion of the feeder LINE/DIRECTION, disruption of a LINE section etc. +SIRI v2.1 - Indicates the loss of an outbound connection, i.e., is used to signal the cancellation of the onward connection to the passengers in the feeder VEHICLEs. - - - - - There is no data available on the interchange status. + Indicates the loss of an outbound connection, i.e., is used to signal the cancellation of the onward connection to the passengers in the feeder VEHICLEs. +SIRI v2.1 - - - - - - - - - - - - - - - From 73bdc055e5f59e4c60b38e18c94f6c0bb82a2e81 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 17 Mar 2020 15:42:49 +0100 Subject: [PATCH 128/290] CR013: include schema for generic types --- xsd/siri_utility/siri_utility-v1.1.xsd | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/xsd/siri_utility/siri_utility-v1.1.xsd b/xsd/siri_utility/siri_utility-v1.1.xsd index 4029f65f..ec11acbd 100644 --- a/xsd/siri_utility/siri_utility-v1.1.xsd +++ b/xsd/siri_utility/siri_utility-v1.1.xsd @@ -54,6 +54,8 @@ Rail transport, Roads and road transport SIRI Framework Utility Types. + + A type with no allowed content, used when simply the presence of an element is significant. @@ -111,12 +113,12 @@ Rail transport, Roads and road transport Type for a Key List. +SIRI v2.1 - + Identifier of value e.g. System. - + Value for alternative key. @@ -167,7 +169,7 @@ such as the description and allowed values for codes. +SIRI v2.1Identifier of a TYPE OF VALUE. - + Name of class of which TypeOfValue is an instance. From 5c2904a889cb9f8383920ec0d4046b8a3f71e89f Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 17 Mar 2020 15:56:39 +0100 Subject: [PATCH 129/290] CR005: remove VDV references from RelationTypeEnum --- xsd/siri_model/siri_journey_support-v2.0.xsd | 104 ++++++++++--------- 1 file changed, 53 insertions(+), 51 deletions(-) diff --git a/xsd/siri_model/siri_journey_support-v2.0.xsd b/xsd/siri_model/siri_journey_support-v2.0.xsd index cdbced28..54ea8ab1 100644 --- a/xsd/siri_model/siri_journey_support-v2.0.xsd +++ b/xsd/siri_model/siri_journey_support-v2.0.xsd @@ -589,56 +589,58 @@ Corresponds to NeTEX TYPE OF SERVICe. Allowed types of relation between JOURNEYs. - - - VDV "FortfuehrungVonFahrt": The journey is a continuation of the specified RelatedJourney (VDV "BeziehungZuFahrt") at the stop point given in CallInfo (VDV "StreckenBezug/Halt"). Passengers don't need to change vehicles. The new journey is not communicated as an interchange. - - - - - VDV "FortfuehrungDurchFahrt": The journey is continued by the specified RelatedJourney (VDV "BeziehungZuFahrt") at the stop point given in CallInfo (VDV "StreckenBezug/Halt"). Passengers don't need to change vehicles. The new journey is not communicated as an interchange. - - - - - VDV "TrennungVonFahrtIn": The journey splits into multiple RelatedJourneys (VDV "BeziehungZuFahrt") at the stop point given in CallInfo (VDV "StreckenBezug/Halt"). - - - - - VDV "FortfuehrungVonGetrennterFahrt": The journey is a continuation of a single RelatedJourney (VDV "BeziehungZuFahrt") splitting into multiple journeys at the stop point given in CallInfo (VDV "StreckenBezug/Halt"). - - - - - VDV "ZusammenfuehrungVonFahrt": The journey is the continuation of multiple RelatedJourneys (VDV "BeziehungZuFahrt") joining together at the stop point given in CallInfo (VDV "StreckenBezug/Halt"). - - - - - VDV "FortfuehrungDurchZusammengefuehrteFahrt": The journey is continued by a single RelatedJourney (VDV "BeziehungZuFahrt") after joining other journeys at the stop point given in CallInfo (VDV "StreckenBezug/Halt"). - - - - - VDV "ErsatzVonFahrt": The journey replaces one or more partially or fully cancelled RelatedJourneys (VDV "BeziehungZuFahrt") during the JourneyPart defined or referenced in JourneyPartInfo (VDV "FahrtAbschnitt"). - - - - - VDV "ErsatzDurchFahrt": The partially or fully cancelled journey is replaced by one or more RelatedJourneys (VDV "BeziehungZuFahrt") during the JourneyPart defined or referenced in JourneyPartInfo (VDV "FahrtAbschnitt"). - - - - - VDV "EntlastungVonFahrt": The journey partially or fully supports one or more RelatedJourneys (VDV "BeziehungZuFahrt") during the JourneyPart defined or referenced in JourneyPartInfo (VDV "FahrtAbschnitt"). - - - - - VDV "EntlastungDurchFahrt": The journey is partially or fully supported by one or more RelatedJourneys (VDV "BeziehungZuFahrt") during the JourneyPart defined or referenced in JourneyPartInfo (VDV "FahrtAbschnitt"). - - - + + + The journey is a continuation of the specified RelatedJourney at the stop point given in CallInfo. +Passengers don't need to change vehicles. The new journey is not communicated as an interchange. + + + + + The journey is continued by the specified RelatedJourney at the stop point given in CallInfo. +Passengers don't need to change vehicles. The new journey is not communicated as an interchange. + + + + + The journey splits into multiple RelatedJourneys at the stop point given in CallInfo. + + + + + The journey is a continuation of a single RelatedJourney splitting into multiple journeys at the stop point given in CallInfo. + + + + + The journey is the continuation of multiple RelatedJourneys joining together at the stop point given in CallInfo. + + + + + The journey is continued by a single RelatedJourney after joining other journeys at the stop point given in CallInfo. + + + + + The journey replaces one or more partially or fully cancelled RelatedJourneys during the JourneyPart defined or referenced in JourneyPartInfo. + + + + + The partially or fully cancelled journey is replaced by one or more RelatedJourneys during the JourneyPart defined or referenced in JourneyPartInfo. + + + + + The journey partially or fully supports one or more RelatedJourneys during the JourneyPart defined or referenced in JourneyPartInfo. + + + + + The journey is partially or fully supported by one or more RelatedJourneys during the JourneyPart defined or referenced in JourneyPartInfo. + + + From 29acc6285b32dbdbd4f6c2b31dcd228eeef1f779 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 17 Mar 2020 21:02:11 +0100 Subject: [PATCH 130/290] CR070: simplify RemovedDatedVehicleJourneyStruct. --- .../siri_datedVehicleJourney-v2.0.xsd | 34 +++++++------------ xsd/siri_model/siri_journey_support-v2.0.xsd | 2 +- 2 files changed, 13 insertions(+), 23 deletions(-) diff --git a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd index 3d002d33..29475dc0 100644 --- a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd @@ -139,37 +139,29 @@ Rail transport, Roads and road transport - A reference to the dated VEHICLE JOURNEY from a previous PT delivery that is removed by the data producer. + A reference to the DATED VEHICLE JOURNEY from a previous PT delivery that is removed by the data producer. - + - The data producer must provide a reason, e.g. type of error and description, in case he wants to silently remove (instead of cancel) a journey from the plan. +SIRI v2.1 + Optionally identify the VEHICLE JOURNEY indirectly by origin and destination and the scheduled times at these stops. - - - - - - - - + - Complete sequence of stops along the route path, in calling order. + TRAIN NUMBERs for journey. - + + + TRAIN NUMBER assigned to VEHICLE JOURNEY. + + - - - Relations of the journey with other journeys, e.g., in case a joining/splitting takes place or the journey substitutes for another one etc. - - - + @@ -383,8 +375,6 @@ Rail transport, Roads and road transport - - @@ -646,7 +636,7 @@ Rail transport, Roads and road transport - The data producer must provide a reason, e.g. type of error and description, in case he wants to silently remove (instead of cancel) an interchange from the plan. +SIRI v2.1 + The data producer must provide a reason, e.g. type of error and description, in case he wants to silently remove (instead of cancel) a journey or an interchange from the plan. +SIRI v2.1 diff --git a/xsd/siri_model/siri_journey_support-v2.0.xsd b/xsd/siri_model/siri_journey_support-v2.0.xsd index 82a01de7..876a57f4 100644 --- a/xsd/siri_model/siri_journey_support-v2.0.xsd +++ b/xsd/siri_model/siri_journey_support-v2.0.xsd @@ -189,7 +189,7 @@ Rail transport, Roads and road transport - LINE Reference. + Reference to LINE. From 423c527603853124a7a888aef3002e008e7345d7 Mon Sep 17 00:00:00 2001 From: hennoit Date: Thu, 19 Mar 2020 14:46:45 +0100 Subject: [PATCH 131/290] Comments by Tim Rivett processed. But also undid the earlier change by Tim (i.e. replaced ifopt namespace in a few elements), because the types in question are still in the ifopt include file. --- xsd/siri_model/siri_situationAffects-v2.0.xsd | 10 +++++----- xsd/siri_model/siri_time-v2.0.xsd | 10 +++++----- 2 files changed, 10 insertions(+), 10 deletions(-) diff --git a/xsd/siri_model/siri_situationAffects-v2.0.xsd b/xsd/siri_model/siri_situationAffects-v2.0.xsd index 7392094f..747ac04e 100644 --- a/xsd/siri_model/siri_situationAffects-v2.0.xsd +++ b/xsd/siri_model/siri_situationAffects-v2.0.xsd @@ -75,7 +75,7 @@ {http://www.siri.org.uk/schema/2.0/xsd/}siri_model/siri_situationAffects-v2.0.xsd [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD + CEN http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modes-v1.1.xsd @@ -1107,7 +1107,7 @@ Rail transport, Roads and road transport - + @@ -1123,7 +1123,7 @@ Rail transport, Roads and road transport - + Reference to a Stop Place. @@ -1133,7 +1133,7 @@ Rail transport, Roads and road transport Name of component. (Unbounded since SIRI 2.0) - + Type of Component. @@ -1157,7 +1157,7 @@ Rail transport, Roads and road transport - Facililitiy available for VEHICLE JOURNEY (+SIRI 2.0) + Facility available for VEHICLE JOURNEY (+SIRI 2.0) diff --git a/xsd/siri_model/siri_time-v2.0.xsd b/xsd/siri_model/siri_time-v2.0.xsd index 1255b857..10652a4b 100644 --- a/xsd/siri_model/siri_time-v2.0.xsd +++ b/xsd/siri_model/siri_time-v2.0.xsd @@ -1,5 +1,5 @@ - + @@ -36,7 +36,7 @@ --> -

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

+

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

 text/xml @@ -45,7 +45,7 @@ {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_time-v2.0.xsd [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD + CEN Unclassified CEN, VDV, RTIG 2004-2020 @@ -168,7 +168,7 @@ Rail transport, Roads and road transport - If end time not provided, whethhr to interpret range as long, term, short term or unknown length of situation. Default is unknown. (Siri 2.0++) + If end time not provided, whethhr to interpret range as long, term, short term or unknown length of situation. Default is unknown. (Siri 2.0++) @@ -227,7 +227,7 @@ Rail transport, Roads and road transport - TPEG Pti34_4, Thusrday + TPEG Pti34_4, Thursday From 4f3f48ecd8359c40dddcd2878bb346113d6fe02e Mon Sep 17 00:00:00 2001 From: hennoit Date: Thu, 19 Mar 2020 16:43:57 +0100 Subject: [PATCH 132/290] merge changes from CR17 and CR22 --- xsd/siri_model/siri_reference-v2.0.xsd | 20 ++++++---- .../siri_situationServiceTypes-v1.0.xsd | 39 ++++++++++++++++++- 2 files changed, 51 insertions(+), 8 deletions(-) diff --git a/xsd/siri_model/siri_reference-v2.0.xsd b/xsd/siri_model/siri_reference-v2.0.xsd index 2bd02145..ebffb1cd 100644 --- a/xsd/siri_model/siri_reference-v2.0.xsd +++ b/xsd/siri_model/siri_reference-v2.0.xsd @@ -54,7 +54,7 @@ [vdv] "DestinationName" inside "PublishedLineGroup" changed to "unbounded" to allow multiple definitions for different languages due to the xml:lang-Attribute --> - + 2020-01-29 + + + 2011-04-18 + + + + 2012-03-23 + + + + 2013-02-11 + + + + 2013-10-01 + + + + 2014-06-20 + +

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

@@ -75,7 +93,7 @@ {http://www.siri.org.uk/schema/2.0/xsd/}siri_model/siri_situation-v2.0.xsd [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD + CEN http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_stop-v0.2.xsd http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modes-v1.1.xsd @@ -83,14 +101,14 @@ Unclassified - Kizoom 2000-2005, CEN 2009-2012 - + Kizoom 2000-2005, CEN 2009-2020 +
    -
  • Schema Derived from the Kizoom XTIS schema
    • +
  • Schema Derived from the Kizoom XTIS schema
- Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -723,19 +741,28 @@ Rail transport, Roads and road transport - StructuredReason Elements. + Structured Reason elements. The TpegReason and/or PublicEventReason enumerated values can be used to create standardized messages describing the SITUATION. If no enumerated values are given, ReasonName is used instead. +Note: this means that ReasonName is NOT a complete message, but only a (few) word(s) to be included in the message! - - + + + Structured explanation of SITUATION reason, from which a standardized message can be created. + + + + + Deprecated (SIRI 2.1) + + - Classifier of Pub;ic Event. + Structured classifier of Public Event, from which a standardized message can be created. - Text explanation of SITUATION reason. Not normally needed. (Unbounded since SIRI 2.0) + Text description of SITUATION reason, from which a standardized message can be created. Not normally needed, except when TpegReason and PublicEventReason are absent. (Unbounded since SIRI 2.0) @@ -1124,7 +1151,11 @@ Rail transport, Roads and road transport Period of effect of disruption, if different from that of SITUATION. - + + + Condition(s) of effect of disruptione. + + Severity of disruption if different from that of SITUATION. TPEG pti26 @@ -1178,6 +1209,24 @@ Rail transport, Roads and road transport + + + Structured elements of a SITUATION condition. The Condition enumerated value(s) can be used to create standardized messages describing the SITUATION. If no enumerated values are given, ConditionName is used instead. +Note: this means that ConditionName is NOT a complete message, but only a (few) word(s) to be included in the message! + + + + + Structured Condition(s) of the SITUATION, from which a standardized message can be created. + + + + + Text description of advice, from which a standardized message can be created. Not normally needed, except when Condition is absent. + + + + Type for boarding restrictions. @@ -1197,12 +1246,25 @@ Rail transport, Roads and road transport - Type for advice. + Type for (structured) advice. The AdviceType enumerated value can be used to create standardized messages describing the SITUATION. If no enumerated value is given, AdviceName is used instead. +Note: this means that AdviceName is NOT a complete message, but only a (few) word(s) to be included in the message! +Alternatively, AdviceRef van be used to reference a (complete) standardised advisory message. + - Reference to a standardis advisory NOTICE to be given to passengers if a particular condition arises . + Reference to a standard advisory NOTICE to be given to passengers if a particular condition arises. + + + + + Structured advice for passengers in the given SITUATION, from which a standardized message can be created. + + + + + Text description of advice, from which a standardized message can be created. Not normally needed, except when AdviceType is absent. @@ -1212,6 +1274,98 @@ Rail transport, Roads and road transport + + + Values for TPEG Pts039 - AdviceType, with some additional values + + + + + TPEG Pts39_0, unknown + + + + + TPEG Pts39_1, use replacement bus + + + + + TPEG Pts39_2, use replacement train + + + + + TPEG Pts39_3, use the alternative route + + + + + TPEG Pts39_4, go on foot + + + + + TPEG Pts39_5, please leave the station! Danger! + + + + + TPEG Pts39_6, no means of travel + + + + + TPEG Pts39_7, use different stops + + + + + TPEG Pts39_8, use alternative stop + + + + + TPEG Pts39_9, do not leave vehicle! Danger! + + + + + TPEG Pts39_10, take advice from announcements + + + + + TPEG Pts39_11, take advice from personnel + + + + + TPEG Pts39_12, obey advice from police + + + + + use other PT services + + + + + use interchange + + + + + no advice + + + + + TPEG Pts39_255, undefined advice + + + + Type for blocking. From 646d0aa0669a02c53c1cea865b29395422ee4876 Mon Sep 17 00:00:00 2001 From: hennoit Date: Fri, 20 Mar 2020 18:10:16 +0100 Subject: [PATCH 134/290] CR55: structured Reason, Effect, Advice --- xsd/siri_model/siri_situation-v2.0.xsd | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/xsd/siri_model/siri_situation-v2.0.xsd b/xsd/siri_model/siri_situation-v2.0.xsd index b6b23920..2a82faad 100644 --- a/xsd/siri_model/siri_situation-v2.0.xsd +++ b/xsd/siri_model/siri_situation-v2.0.xsd @@ -741,13 +741,13 @@ Rail transport, Roads and road transport - Structured Reason elements. The TpegReason and/or PublicEventReason enumerated values can be used to create standardized messages describing the SITUATION. If no enumerated values are given, ReasonName is used instead. + Structured Reason elements. The TpegReason and/or PublicEventReason enumerated values can be used to generate standardized messages describing the SITUATION. If no enumerated values are given, ReasonName is used instead. Note: this means that ReasonName is NOT a complete message, but only a (few) word(s) to be included in the message! - Structured explanation of SITUATION reason, from which a standardized message can be created. + Structured classifier of nature of SITUATION, from which a standardized message can be generated. @@ -757,12 +757,12 @@ Note: this means that ReasonName is NOT a complete message, but only a (few) wor - Structured classifier of Public Event, from which a standardized message can be created. + Structured classifier of Public Event, from which a standardized message can be generated. - Text description of SITUATION reason, from which a standardized message can be created. Not normally needed, except when TpegReason and PublicEventReason are absent. (Unbounded since SIRI 2.0) + Text explanation of nature of SITUATION, from which a standardized message can be generated. Not normally needed, except when TpegReason and PublicEventReason are absent. (Unbounded since SIRI 2.0) @@ -1211,18 +1211,18 @@ Note: this means that ReasonName is NOT a complete message, but only a (few) wor - Structured elements of a SITUATION condition. The Condition enumerated value(s) can be used to create standardized messages describing the SITUATION. If no enumerated values are given, ConditionName is used instead. + Structured elements of a SITUATION condition. The Condition enumerated value(s) can be used to generate standardized messages describing the SITUATION. If no enumerated values are given, ConditionName is used instead. Note: this means that ConditionName is NOT a complete message, but only a (few) word(s) to be included in the message! - Structured Condition(s) of the SITUATION, from which a standardized message can be created. + Structured classification(s) of effect on service, from which a standardized message can be generated. - Text description of advice, from which a standardized message can be created. Not normally needed, except when Condition is absent. + Text classification of effect on service, from which a standardized message can be generated. Not normally needed, except when Condition is absent. @@ -1246,7 +1246,7 @@ Note: this means that ConditionName is NOT a complete message, but only a (few) - Type for (structured) advice. The AdviceType enumerated value can be used to create standardized messages describing the SITUATION. If no enumerated value is given, AdviceName is used instead. + Type for (structured) advice. The AdviceType enumerated value can be used to generate standardized messages describing the SITUATION. If no enumerated value is given, AdviceName is used instead. Note: this means that AdviceName is NOT a complete message, but only a (few) word(s) to be included in the message! Alternatively, AdviceRef van be used to reference a (complete) standardised advisory message. @@ -1259,12 +1259,12 @@ Alternatively, AdviceRef van be used to reference a (complete) standardised advi - Structured advice for passengers in the given SITUATION, from which a standardized message can be created. + Structured advice for passengers in the given SITUATION, from which a standardized message can be generated. - Text description of advice, from which a standardized message can be created. Not normally needed, except when AdviceType is absent. + Text description of advice, from which a standardized message can be generated. Not normally needed, except when AdviceType is absent. From 63b2b7142cf9c31a2ac05449b31ce2ad4c7fd463 Mon Sep 17 00:00:00 2001 From: Christophe Duquesne Date: Mon, 23 Mar 2020 15:40:19 +0100 Subject: [PATCH 135/290] Revert "Update siri_facility-v2.0.xsd" This reverts commit 862491e5f4d99fa6d7b43c47b3e85074a4b86e45. --- xsd/siri_model/siri_facility-v2.0.xsd | 137 +------------------------- 1 file changed, 2 insertions(+), 135 deletions(-) diff --git a/xsd/siri_model/siri_facility-v2.0.xsd b/xsd/siri_model/siri_facility-v2.0.xsd index fe8c833b..6f33d2b8 100644 --- a/xsd/siri_model/siri_facility-v2.0.xsd +++ b/xsd/siri_model/siri_facility-v2.0.xsd @@ -74,7 +74,6 @@ Rail transport, Roads and road transport SIRi Facility model elemenys - @@ -239,14 +238,9 @@ Rail transport, Roads and road transport - - - - - @@ -292,71 +286,6 @@ Rail transport, Roads and road transport - - - Allowed values for TypeOfCounting. - - - - - - - - - - - - - Allowed values for trend of a counting. - - - - - - - - - - - - - - - Allowed values for units of what is counted - bay: Parking bay for cars, bicycle, scooter, etc - otherSpaces: any other kind of spaces: lockers, stading spaces, toilets, etc. - devices: electronic devices (audio guide, headphones, etc.) and physical devices (walking stick, wheel chair, etc.) - vehicles: any type of vehicles (cycle, car, scooter, overboard, motorbyke, etc.) - kW (kiloWatt) or kWh (kiloWatt per hour): means that an available (ore consummed) power is measured - litres and cubeMeters: means that a volume is measured - squareMeters: means that a surface is measured - meters: means that a distance is measured - kg (kilogram): means that a mass is measured - A (Amper): means that an electric intensity is measured - C (degree Celsius): means that a temperature is measured - other: use of "other" requires the additional open ended TypeOfCountedFeature (monitoredCountingStructure) to be filled - - - - - - - - - - - - - - - - - - - - - - Descriprion of the status of a MONITORED FACILITY. @@ -398,56 +327,6 @@ Rail transport, Roads and road transport - - - Monitored counted values. - - - - - Nature of what is counted. - - - - - Unit of type for what is being counted - - - - - Open ended type or refined classification of what is counted (complement to the infomation coming from the facility type itself) - - - - - - Counted value - - - - - Value as a percentage (0.0 to 1.0) - - - - - - Trend of the count - - - - - Accuracy of the count, as a percentage (0.0 to 1.0) - - - - - Description of what is counted - - - - - @@ -465,25 +344,13 @@ Rail transport, Roads and road transport Facility affected by condition. - - - Reference to a Facility (may refer an Equipment, Local Service, Site or Vehicle). - - + Status of Facility. - - - - - - - - @@ -497,7 +364,7 @@ Rail transport, Roads and road transport - Period (duration) of the status change for the facility (validity period of the FacilityCondition). + Period (duration) of the status change for the facility. From ad1b18b7dadc4abc815d30ecbf803eabfec997c1 Mon Sep 17 00:00:00 2001 From: Christophe Duquesne Date: Mon, 23 Mar 2020 18:42:19 +0100 Subject: [PATCH 136/290] Update siri_facility-v2.0.xsd --- xsd/siri_model/siri_facility-v2.0.xsd | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/xsd/siri_model/siri_facility-v2.0.xsd b/xsd/siri_model/siri_facility-v2.0.xsd index fe8c833b..0bbc4516 100644 --- a/xsd/siri_model/siri_facility-v2.0.xsd +++ b/xsd/siri_model/siri_facility-v2.0.xsd @@ -326,13 +326,13 @@ Rail transport, Roads and road transport bay: Parking bay for cars, bicycle, scooter, etc otherSpaces: any other kind of spaces: lockers, stading spaces, toilets, etc. devices: electronic devices (audio guide, headphones, etc.) and physical devices (walking stick, wheel chair, etc.) - vehicles: any type of vehicles (cycle, car, scooter, overboard, motorbyke, etc.) - kW (kiloWatt) or kWh (kiloWatt per hour): means that an available (ore consummed) power is measured - litres and cubeMeters: means that a volume is measured + vehicles: any type of vehicles (cycle, car, scooter, hoverboard, motorbike, etc.) + kW (kiloWatt) or kWh (kiloWatt per hour): means that an available (or consumed) power is measured + litres and cubicMeters: means that a volume is measured squareMeters: means that a surface is measured meters: means that a distance is measured kg (kilogram): means that a mass is measured - A (Amper): means that an electric intensity is measured + A (Ampere): means that an electric intensity is measured C (degree Celsius): means that a temperature is measured other: use of "other" requires the additional open ended TypeOfCountedFeature (monitoredCountingStructure) to be filled @@ -346,8 +346,8 @@ Rail transport, Roads and road transport - - + + @@ -677,7 +677,7 @@ Rail transport, Roads and road transport - Whether stop or service is accessible to mobility impaired users. This may be further qualified by one ore more MobilityFacility instances to specify which types of mobility access are available (true) or not available (false). For example suitableForWheelChair, or 'tepFreeAccess. + Whether stop or service is accessible to mobility impaired users. This may be further qualified by one or more MobilityFacility instances to specify which types of mobility access are available (true) or not available (false). For example suitableForWheelChair, or 'tepFreeAccess. From 2dffbdbbc9a273281880b4e5bd836b190e58c4bd Mon Sep 17 00:00:00 2001 From: "Willering HW (Henno)" Date: Tue, 12 May 2020 10:15:42 +0200 Subject: [PATCH 137/290] changed TpegAdvice to AdviceType --- xsd/siri_model/siri_situation-v2.0.xsd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xsd/siri_model/siri_situation-v2.0.xsd b/xsd/siri_model/siri_situation-v2.0.xsd index 22baaad9..a2b59e72 100644 --- a/xsd/siri_model/siri_situation-v2.0.xsd +++ b/xsd/siri_model/siri_situation-v2.0.xsd @@ -57,7 +57,7 @@ D2 trafficResstrictionType renamed to trafficConstrictionType Correct type on easementref to normalized string. Allow transalatiobs of NLString elements - --> + --> 2013-02-11 @@ -1314,7 +1314,7 @@ Rail transport, Roads and road transport Reference to a standard advisory NOTICE to be given to passengers if a particular condition arises. - + Further Textual advice to passengers. (Unbounded since SIRI 2.0) From 345006bae8777d60292ebdc1776884c7943b44a3 Mon Sep 17 00:00:00 2001 From: Christophe Duquesne Date: Tue, 12 May 2020 16:12:12 +0200 Subject: [PATCH 138/290] Update siri_facility-v2.0.xsd Perencentage are nos 0-100 and of type PercentageType. associated comments are more detailed. --- xsd/siri_model/siri_facility-v2.0.xsd | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/xsd/siri_model/siri_facility-v2.0.xsd b/xsd/siri_model/siri_facility-v2.0.xsd index 0bbc4516..76939927 100644 --- a/xsd/siri_model/siri_facility-v2.0.xsd +++ b/xsd/siri_model/siri_facility-v2.0.xsd @@ -424,9 +424,9 @@ Rail transport, Roads and road transport Counted value - + - Value as a percentage (0.0 to 1.0) + Value as a percentage (0.0 to 100.0) of the maximum possible value @@ -435,9 +435,9 @@ Rail transport, Roads and road transport Trend of the count - + - Accuracy of the count, as a percentage (0.0 to 1.0) + Accuracy of the count, as a percentage (0.0 to 100.0), the percentage being a + or - maximum deviation from the provided value From af37816163aa30d8ced71d522338cee37d0a2037 Mon Sep 17 00:00:00 2001 From: Christophe Duquesne Date: Fri, 15 May 2020 16:16:36 +0200 Subject: [PATCH 139/290] Includes all updates and corrections from Henno Includes all updates and corrections from Henno --- xsd/siri_model/siri_facility-v2.0.xsd | 79 +++++++++++++++------------ 1 file changed, 43 insertions(+), 36 deletions(-) diff --git a/xsd/siri_model/siri_facility-v2.0.xsd b/xsd/siri_model/siri_facility-v2.0.xsd index 76939927..6c6fa1fb 100644 --- a/xsd/siri_model/siri_facility-v2.0.xsd +++ b/xsd/siri_model/siri_facility-v2.0.xsd @@ -20,18 +20,21 @@ 2008-01-11 - 2008-07-05 - USe Accessibility assessment from ifopt - - 2011-01-19 - TidyUp empty ValidtyConditionGroup - - 2012-03-23 - +SIRI v2.0 - remove unecesasry dependencies - + + 2008-07-05 + + + + 2011-01-19 + + + + 2012-03-23 + + + -

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

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

 @@ -48,14 +51,14 @@ Unclassified - CEN, VDV, RTIG 2004-2012 - + CEN, VDV, RTIG 2004-2020 +
  • Derived from TransModel and Trident standards.
- Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -109,7 +112,7 @@ Rail transport, Roads and road transport - Type for sescription the MONITORED FACILITY itself. + Type for description of the MONITORED FACILITY itself. @@ -234,7 +237,7 @@ Rail transport, Roads and road transport - Generic catégory of a facility. + Generic category of a facility. @@ -252,7 +255,7 @@ Rail transport, Roads and road transport - Summary information about Facility. Used in DISCOVERY used + Summary information about Facility. Used in DISCOVERY. @@ -305,7 +308,7 @@ Rail transport, Roads and road transport - + Allowed values for trend of a counting. @@ -323,16 +326,16 @@ Rail transport, Roads and road transport Allowed values for units of what is counted - bay: Parking bay for cars, bicycle, scooter, etc - otherSpaces: any other kind of spaces: lockers, stading spaces, toilets, etc. - devices: electronic devices (audio guide, headphones, etc.) and physical devices (walking stick, wheel chair, etc.) + bay: parking bay for cars, bicycle, scooter, etc + otherSpaces: any other kind of spaces: lockers, standing spaces, toilets, etc. + devices: electronic devices (audio guide, headphones, etc.) and physical devices (walking stick, wheelchair, etc.) vehicles: any type of vehicles (cycle, car, scooter, hoverboard, motorbike, etc.) - kW (kiloWatt) or kWh (kiloWatt per hour): means that an available (or consumed) power is measured + kW (kiloWatt) or kWh (kiloWatt-hour): means that an available or consumed power is measured litres and cubicMeters: means that a volume is measured squareMeters: means that a surface is measured meters: means that a distance is measured kg (kilogram): means that a mass is measured - A (Ampere): means that an electric intensity is measured + A (Ampere): means that an electric current is measured C (degree Celsius): means that a temperature is measured other: use of "other" requires the additional open ended TypeOfCountedFeature (monitoredCountingStructure) to be filled @@ -344,7 +347,7 @@ Rail transport, Roads and road transport - + @@ -359,7 +362,7 @@ Rail transport, Roads and road transport - Descriprion of the status of a MONITORED FACILITY. + Description of the status of a MONITORED FACILITY. @@ -415,7 +418,7 @@ Rail transport, Roads and road transport - Open ended type or refined classification of what is counted (complement to the infomation coming from the facility type itself) + Open ended type or refined classification of what is counted (complement to the information coming from the facility type itself) @@ -456,7 +459,7 @@ Rail transport, Roads and road transport - Description of any change concerning a MONITORED FACILITY New structure defined in SIRI XSD 1.1 for Faclities Management. + Description of any change concerning a MONITORED FACILITY New structure defined in SIRI XSD 1.1 for Facilities Management. @@ -483,7 +486,11 @@ Rail transport, Roads and road transport - + + + New position of the Facility referenced by the FacilityRef or described in the FacilityStructure + + @@ -506,7 +513,7 @@ Rail transport, Roads and road transport - Allowed values for actions to remedy a faclity change. + Allowed values for actions to remedy a facility change. @@ -539,7 +546,7 @@ Rail transport, Roads and road transport - Allowed values for the monitoring conditions (frequency of mesurement, etc): an automatic monitoring of the satus of a lift with pushed alert in case of incident is very different from a daily manual/visual check. + Allowed values for the monitoring conditions (frequency of measurement, etc): an automatic monitoring of the status of a lift with pushed alert in case of incident is very different from a daily manual/visual check. @@ -549,7 +556,7 @@ Rail transport, Roads and road transport - How monitoring is automatic, manual, etc.. + How monitoring is automatic, manual, etc. @@ -562,7 +569,7 @@ Rail transport, Roads and road transport - Allowed values for the types of monitoring: automatic or manual - describing the hardware transducer (video, GPS/Radio, in-road sensors, etc.) doesn't seeme useful for SIRi. + Allowed values for the types of monitoring: automatic or manual - describing the hardware transducer (video, GPS/Radio, in-road sensors, etc.) doesn't seeme useful for SIRI. @@ -572,7 +579,7 @@ Rail transport, Roads and road transport - Allowed values for the type for Description of the monitoring conditions (frequency of mesurement, etc): an automatic monitoring of the satus of a lift with pushed alert in case of incident is very different from a daily manual/visual check. + Allowed values for the type for Description of the monitoring conditions (frequency of mesurement, etc): an automatic monitoring of the status of a lift with pushed alert in case of incident is very different from a daily manual/visual check. @@ -620,7 +627,7 @@ Rail transport, Roads and road transport - Reference to a TYPE OF EQUIPMENT.r. + Reference to a TYPE OF EQUIPMENT. @@ -677,7 +684,7 @@ Rail transport, Roads and road transport - Whether stop or service is accessible to mobility impaired users. This may be further qualified by one or more MobilityFacility instances to specify which types of mobility access are available (true) or not available (false). For example suitableForWheelChair, or 'tepFreeAccess. + Whether stop or service is accessible to mobility impaired users. This may be further qualified by one or more MobilityFacility instances to specify which types of mobility access are available (true) or not available (false). For example suitableForWheelChair, or stepFreeAccess. @@ -694,7 +701,7 @@ Rail transport, Roads and road transport - Information about a change of Equipment availabilti at stop or on vehicle that may affect access or use. + Information about a change of Equipment availability at stop or on vehicle that may affect access or use. From 56ab03206a2b7de49c3b91da80caa158d6192d6a Mon Sep 17 00:00:00 2001 From: Christophe Duquesne Date: Fri, 15 May 2020 16:25:01 +0200 Subject: [PATCH 140/290] "unknown" addition in CountingTrendEnumeration "unknown" is added in order to be explicit. However, not providing the trend most probably means "unknown" (rather than "stable", in order to be consistent with other similar situations in SIRI, but that would be a small difference from VDV default behaviour). --- xsd/siri_model/siri_facility-v2.0.xsd | 1 + 1 file changed, 1 insertion(+) diff --git a/xsd/siri_model/siri_facility-v2.0.xsd b/xsd/siri_model/siri_facility-v2.0.xsd index 6c6fa1fb..2a3eda51 100644 --- a/xsd/siri_model/siri_facility-v2.0.xsd +++ b/xsd/siri_model/siri_facility-v2.0.xsd @@ -321,6 +321,7 @@ Rail transport, Roads and road transport + From 393e41aadb2e7cc6da96920d7678a1ff2aad4555 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Mon, 8 Jun 2020 15:34:20 +0200 Subject: [PATCH 141/290] activate git push for all branches except master --- .travis/travis-ci_git-commit.sh | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/.travis/travis-ci_git-commit.sh b/.travis/travis-ci_git-commit.sh index a68b02f7..896660f6 100644 --- a/.travis/travis-ci_git-commit.sh +++ b/.travis/travis-ci_git-commit.sh @@ -6,49 +6,49 @@ function travis-branch-commit() { local head_ref branch_ref head_ref=$(git rev-parse HEAD) if [[ $? -ne 0 || ! $head_ref ]]; then - err "failed to get HEAD reference" + err "Failed to get HEAD reference" return 1 fi branch_ref=$(git rev-parse "$TRAVIS_BRANCH") if [[ $? -ne 0 || ! $branch_ref ]]; then - err "failed to get $TRAVIS_BRANCH reference" + err "Failed to get $TRAVIS_BRANCH reference" return 1 fi if [[ $head_ref != $branch_ref ]]; then msg "HEAD ref ($head_ref) does not match $TRAVIS_BRANCH ref ($branch_ref)" msg "Someone may have pushed new commits before this build cloned the repo" - return 0 + return 1 fi if ! git checkout "$TRAVIS_BRANCH"; then - err "failed to checkout $TRAVIS_BRANCH" + err "Failed to checkout $TRAVIS_BRANCH" return 1 fi if ! git add --all .; then - err "failed to add modified files to git index" + err "Failed to add modified files to git index" return 1 fi # make Travis CI skip this build if ! git commit -m "Travis CI update [skip ci]"; then - err "failed to commit updates" + err "Failed to commit updates" return 1 fi - # add to your .travis.yml: `branches\n except:\n - "/\\+travis\\d+$/"\n` - local git_tag=SOME_TAG_TRAVIS_WILL_NOT_BUILD+travis$TRAVIS_BUILD_NUMBER + # add to your .travis.yml: `branches\n except:\n - "/travis_build-\\d+/"\n` + local git_tag=travis_build-$TRAVIS_BUILD_NUMBER if ! git tag "$git_tag" -m "Generated tag from Travis CI build $TRAVIS_BUILD_NUMBER"; then - err "failed to create git tag: $git_tag" + err "Failed to create git tag: $git_tag" return 1 fi local remote=origin if [[ $GH_TOKEN ]]; then remote=https://$GH_TOKEN@github.com/$GH_REPO fi - if [[ $TRAVIS_BRANCH != development ]] && [[ $TRAVIS_BRANCH != integration ]]; then - msg "not pushing updates to branch $TRAVIS_BRANCH" + if [[ $TRAVIS_BRANCH == master ]]; then + msg "Not pushing updates to branch $TRAVIS_BRANCH" return 0 fi if ! git push --quiet --follow-tags "$remote" "$TRAVIS_BRANCH" > /dev/null 2>&1; then - err "failed to push git changes" + err "Failed to push git changes" return 1 fi } From 1e3e4de2bb31858a996e41ccc89d758f7259070a Mon Sep 17 00:00:00 2001 From: Travis CI User Date: Mon, 8 Jun 2020 13:48:03 +0000 Subject: [PATCH 142/290] Travis CI update [skip ci] --- xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd | 6 +++--- xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd | 6 +++--- xsd/siri_model/siri_journey-v2.0.xsd | 2 +- xsd/siri_model/siri_journey_support-v2.0.xsd | 12 ++++++------ 4 files changed, 13 insertions(+), 13 deletions(-) diff --git a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd index d0415321..95b79e38 100644 --- a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd @@ -130,9 +130,9 @@ Rail transport, Roads and road transport - - Relations of the journey with other journeys, e.g., in case a joining/splitting takes place or the journey substitutes for another one etc. - + + Relations of the journey with other journeys, e.g., in case a joining/splitting takes place or the journey substitutes for another one etc. + diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index f2dd100a..50f9fa73 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -321,9 +321,9 @@ the original journey and the nature of the difference. - - Relations of the journey with other journeys, e.g., in case a joining/splitting takes place or the journey substitutes for another one etc. - + + Relations of the journey with other journeys, e.g., in case a joining/splitting takes place or the journey substitutes for another one etc. + diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index dfbd4106..4c486e0c 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -932,7 +932,7 @@ Rail transport, Roads and road transport Information about the JOURNEY PARTs for which the JOURNEY has a JOURNEY RELATION. +SIRI v2.1 - + diff --git a/xsd/siri_model/siri_journey_support-v2.0.xsd b/xsd/siri_model/siri_journey_support-v2.0.xsd index 54ea8ab1..49606652 100644 --- a/xsd/siri_model/siri_journey_support-v2.0.xsd +++ b/xsd/siri_model/siri_journey_support-v2.0.xsd @@ -193,14 +193,14 @@ Rail transport, Roads and road transport - - TRAIN NUMBER Reference. - + + TRAIN NUMBER Reference. + - - OPERATOR Reference. - + + OPERATOR Reference. + From e0d0f5a85dc0d94ee130ed43187428e4f0e3cfab Mon Sep 17 00:00:00 2001 From: Travis CI User Date: Mon, 8 Jun 2020 15:29:14 +0000 Subject: [PATCH 143/290] Travis CI update [skip ci] --- xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index b63274e4..88b3cdbb 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -99,7 +99,7 @@ Rail transport, Roads and road transport - + Identifer of a VEHICLE JOURNEY within data Horizon of a service. @@ -112,12 +112,12 @@ DEPRECATED from SIRI 2.0 - + Additionally, identify the VEHICLE JOURNEY by origin and destination and the scheduled times at these stops. - + If this is the first message for an unplanned 'extra' VEHICLE JOURNEY, a new and unique code must be given for it. ExtraJourney should be set to 'true'. From 052b65ec92e63367353317a2127663eddece296f Mon Sep 17 00:00:00 2001 From: Travis CI User Date: Wed, 10 Jun 2020 18:43:01 +0000 Subject: [PATCH 144/290] Travis CI update [skip ci] --- xsd/siri_model/siri_all_journeyModel-v2.0.xsd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xsd/siri_model/siri_all_journeyModel-v2.0.xsd b/xsd/siri_model/siri_all_journeyModel-v2.0.xsd index c7bf5428..665b5b9a 100644 --- a/xsd/siri_model/siri_all_journeyModel-v2.0.xsd +++ b/xsd/siri_model/siri_all_journeyModel-v2.0.xsd @@ -18,4 +18,4 @@ - \ No newline at end of file + From 9e02241b104885a2f9ed3a2b9734134ba290038e Mon Sep 17 00:00:00 2001 From: Travis CI User Date: Thu, 11 Jun 2020 13:51:42 +0000 Subject: [PATCH 145/290] Travis CI update [skip ci] --- xsd/siri_model/siri_journey-v2.0.xsd | 2 +- xsd/siri_model/siri_situation-v2.0.xsd | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index 4cf17f11..2ffbee92 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -656,7 +656,7 @@ To avoid this, the producer should transmit xxxPredictionUnknown instead of any - + If the producer is (temporarily) not able to deliver real-time predictions (e.g. because of a connection loss), he has various options (and combinations of them) to inform the consumer: (i) set Monitored to 'false' diff --git a/xsd/siri_model/siri_situation-v2.0.xsd b/xsd/siri_model/siri_situation-v2.0.xsd index 7aadd682..2cd86325 100644 --- a/xsd/siri_model/siri_situation-v2.0.xsd +++ b/xsd/siri_model/siri_situation-v2.0.xsd @@ -33,7 +33,7 @@ 2008-07-05 - From 8b138634fddbf048ba7c037c70d4555604233b80 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Thu, 11 Jun 2020 16:59:51 +0200 Subject: [PATCH 146/290] update PercentageType to allow values beyond 100 --- xsd/siri_utility/siri_types-v2.0.xsd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xsd/siri_utility/siri_types-v2.0.xsd b/xsd/siri_utility/siri_types-v2.0.xsd index 396c91ad..93df23d2 100644 --- a/xsd/siri_utility/siri_types-v2.0.xsd +++ b/xsd/siri_utility/siri_types-v2.0.xsd @@ -155,11 +155,11 @@ A string containing a phrase in a natural language name that requires at least o - Specifies a percentage from 0 to 100. + Specifies a percentage from 0 to 100. +The value range is normally 0-100, but could in some circumstances go beyond 100%, e.g. when representing the OccupancyPercentage of an over-crowded vehicle or in similar cases. - From 06687f1404ddcacf6318265678ebe8bec0d86cb9 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Thu, 11 Jun 2020 22:22:56 +0200 Subject: [PATCH 147/290] CR002: change annot. of XOrientationRelativeToQuay --- .../siri_estimatedVehicleJourney-v2.0.xsd | 2 +- xsd/siri_model/siri_journey-v2.0.xsd | 22 ++++++++++++------- 2 files changed, 15 insertions(+), 9 deletions(-) diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index 9b2013b0..771cbd94 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -395,7 +395,7 @@ the original journey and the nature of the difference. - Type of boarding and alighting at stop, e.g. alighting, noAlighting or passThru. +SIRI v2.1 + Type of alighting at stop, e.g. alighting, noAlighting or passThru. +SIRI v2.1 diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index ddabba72..1c36e3f6 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -506,11 +506,14 @@ Rail transport, Roads and road transport - Indication of the direction of travel of the vehicle or formation (e.g. TRAIN composition ) with respect to the platform, or more precisely the QUAY. -For example "towards A", which means that the vehicle departs towards sector "A" of the QUAY. It is advised to specify a reference point that is meaningful for passengers on location. -Unbounded to allow multiple languages. +SIRI v2.1 - - + Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. +SIRI v2.1 +Examples: +- "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle arriving at sector A first when approaching the QUAY with sectors A-B-C-D. If the arriving vehicle is represented as an arrow, "towards A" would be abstracted as "=> A-B-C-D". +- "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle arriving at this reference point first when approaching the QUAY. If the arriving vehicle is represented as an arrow, "towards 0" would be abstracted as "=> 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). +It is advised to specify a reference point that is meaningful for passengers on location. + + + Real-time occupancies and capacities of a vehicle (by fare classes) when arriving at a given STOP POINT. +SIRI v2.1 @@ -548,9 +551,12 @@ Unbounded to allow multiple languages. +SIRI v2.1 - Indication of the direction of travel of the vehicle or formation (e.g. TRAIN composition ) with respect to the platform, or more precisely the QUAY. -For example "towards A", which means that the vehicle departs towards sector "A" of the QUAY. It is advised to specify a reference point that is meaningful for passengers on location. -Unbounded to allow multiple languages. +SIRI v2.1 + Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. +SIRI v2.1 +Examples: +- "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle departing in the direction of sector A on a QUAY with sectors A-B-C-D. If the departing vehicle is represented as an arrow, "towards A" would be abstracted as "<= A-B-C-D". +- "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle departing in the direction of this reference point. If the arriving vehicle is represented as an arrow, "towards 0" would be abstracted as "<= 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). +It is advised to specify a reference point that is meaningful for passengers on location. + From b3fb0dd7eca838c07202e5838ab616915b71d240 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 24 Jun 2020 14:41:51 +0200 Subject: [PATCH 148/290] DepartureOrientationRelativeToQuay annot. update --- xsd/siri_model/siri_journey-v2.0.xsd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index 1c36e3f6..262adfc7 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -554,7 +554,7 @@ It is advised to specify a reference point that is meaningful for passengers on Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. +SIRI v2.1 Examples: - "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle departing in the direction of sector A on a QUAY with sectors A-B-C-D. If the departing vehicle is represented as an arrow, "towards A" would be abstracted as "<= A-B-C-D". -- "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle departing in the direction of this reference point. If the arriving vehicle is represented as an arrow, "towards 0" would be abstracted as "<= 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). +- "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle departing in the direction of this reference point. If the departing vehicle is represented as an arrow, "towards 0" would be abstracted as "<= 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). It is advised to specify a reference point that is meaningful for passengers on location. From fbe7cf393faaf38fe0c9c5c429c594772df2f232 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 1 Jul 2020 16:57:34 +0200 Subject: [PATCH 149/290] CR002: remove previously added DisruptionGroup --- xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd | 1 - 1 file changed, 1 deletion(-) diff --git a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd index 1d2d2e84..908f5ed8 100644 --- a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd @@ -328,7 +328,6 @@ For SIRI-VM this is the most recent stop visited by the VEHICLE. - From 201d4c6891fc92f582680e72a176e4fd7d6da597 Mon Sep 17 00:00:00 2001 From: "Willering HW (Henno)" Date: Thu, 2 Jul 2020 13:16:54 +0200 Subject: [PATCH 150/290] Update annotations for xxxName elements --- xsd/siri_model/siri_situation-v2.0.xsd | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/xsd/siri_model/siri_situation-v2.0.xsd b/xsd/siri_model/siri_situation-v2.0.xsd index f14cdd9e..12e8f076 100644 --- a/xsd/siri_model/siri_situation-v2.0.xsd +++ b/xsd/siri_model/siri_situation-v2.0.xsd @@ -743,7 +743,7 @@ Note: this means that ReasonName is NOT a complete message, but only a (few) wor - Structured classifier of nature of SITUATION, from which a standardized message can be generated. + Structured classification of nature of SITUATION, from which a standardized message can be generated. @@ -753,12 +753,12 @@ Note: this means that ReasonName is NOT a complete message, but only a (few) wor - Structured classifier of Public Event, from which a standardized message can be generated. + Structured classification of Public Event, from which a standardized message can be generated. - Text explanation of nature of SITUATION, from which a standardized message can be generated. Not normally needed, except when TpegReason and PublicEventReason are absent. (Unbounded since SIRI 2.0) + Textual classification of nature of SITUATION, from which a standardized message can be generated. Not normally needed, except when TpegReason and PublicEventReason are absent. (Unbounded since SIRI 2.0) @@ -1303,7 +1303,7 @@ Note: this means that ConditionName is NOT a complete message, but only a (few) - Text classification of effect on service, from which a standardized message can be generated. Not normally needed, except when Condition is absent. + Textual classification of effect on service, from which a standardized message can be generated. Not normally needed, except when Condition is absent. @@ -1329,7 +1329,7 @@ Note: this means that ConditionName is NOT a complete message, but only a (few) Type for (structured) advice. The AdviceType enumerated value can be used to generate standardized messages describing the SITUATION. If no enumerated value is given, AdviceName is used instead. Note: this means that AdviceName is NOT a complete message, but only a (few) word(s) to be included in the message! -Alternatively, AdviceRef van be used to reference a (complete) standardised advisory message. +Alternatively, AdviceRef can be used to reference a (complete) standardised advisory message. @@ -1340,17 +1340,17 @@ Alternatively, AdviceRef van be used to reference a (complete) standardised advi - Structured advice for passengers in the given SITUATION, from which a standardized message can be generated. + Structured classification of advice for passengers in the given SITUATION, from which a standardized message can be generated. - Text description of advice, from which a standardized message can be generated. Not normally needed, except when AdviceType is absent. + Textual classification of advice, from which a standardized message can be generated. Not normally needed, except when AdviceType is absent. - Further Textual advice to passengers. (Unbounded since SIRI 2.0) + Further textual advice to passengers. (Unbounded since SIRI 2.0) From 304a6ec1520b2a3bbb045e00c2c66344a240d25b Mon Sep 17 00:00:00 2001 From: Adrian A Date: Sat, 4 Jul 2020 01:13:48 +0200 Subject: [PATCH 151/290] CR002: add VehicleEntrance / update FormationRefs --- xsd/siri_model/siri_journey_support-v2.0.xsd | 37 ++++++++++++++++---- 1 file changed, 30 insertions(+), 7 deletions(-) diff --git a/xsd/siri_model/siri_journey_support-v2.0.xsd b/xsd/siri_model/siri_journey_support-v2.0.xsd index 3da3fe58..190c8e39 100644 --- a/xsd/siri_model/siri_journey_support-v2.0.xsd +++ b/xsd/siri_model/siri_journey_support-v2.0.xsd @@ -341,7 +341,7 @@ Rail transport, Roads and road transport - Type for identifier of a TRAIN COMPONENT. A TRAIN ELEMENT with a specific order in a TRAIN. +SIRI v2.1 + Type for identifier of a TRAIN COMPONENT. A TRAIN ELEMENT with a specific order within a TRAIN. +SIRI v2.1 @@ -379,7 +379,7 @@ Rail transport, Roads and road transport - Type for identifier of a COMPOUND TRAIN. An ordered sequence of TRAINs. A journey does always have one or more JOURNEY PARTs in which the TRAIN composition remains unchanged. +SIRI v2.1 + Type for identifier of a COMPOUND TRAIN. An ordered sequence of TRAINs or TRAIN IN COMPOUND TRAINs respectively. +SIRI v2.1 @@ -398,7 +398,7 @@ Rail transport, Roads and road transport - Type for identifier of a TRAIN IN COMPOUND TRAIN. A TRAIN with a specific order in a COMPOUND TRAIN (the train formation as a whole). +SIRI v2.1 + Type for identifier of a TRAIN IN COMPOUND TRAIN. A TRAIN with a specific order within a COMPOUND TRAIN. +SIRI v2.1 @@ -415,17 +415,40 @@ Rail transport, Roads and road transport Reference to a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 + + + Type for identifier of an ENTRANCE TO VEHICLE, e.g. a door of a TRAIN ELEMENT. +SIRI v2.1 + + + + + + Type for reference to an ENTRANCE TO VEHICLE. +SIRI v2.1 + + + + + + + + Reference to an ENTRANCE TO VEHICLE. +SIRI v2.1 + + - Groups together the relevant references needed in a formation. -Either the smallest part of a formation, a TRAIN COMPONENT, is referenced or the TRAIN itself. -If the formation consists of multiple coupled TRAINs, a reference to the COMPOUND TRAIN is possible too. + Groups together the relevant references needed in a formation. +SIRI v2.1 +Has the following uses: +- Either the smallest part of a formation, a TRAIN COMPONENT, is referenced or the TRAIN itself. The former is ideally used in a FORMATION ASSIGNMENT, i.e. QUAY (sector) assignment, to provide the highest level of detail for passenger orientation. +- If the formation consists of multiple coupled TRAINs, a reference to the COMPOUND TRAIN is also possible. This might be used in a FORMATION CONDITION to signal a change of the train composition. +- In case alighting/boarding data from an automatic passenger counting system is available, the respective vehicle entrances may be referenced. + - + + From 6864b9f7b4eb4821a4b93571005d5a2f54e3f219 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Sat, 4 Jul 2020 01:15:02 +0200 Subject: [PATCH 152/290] CR005: update JourneyPart annotations --- xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd index 908f5ed8..7f237f0f 100644 --- a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd @@ -324,8 +324,8 @@ For SIRI-VM this is the most recent stop visited by the VEHICLE. - Reference to a COMPOUND TRAIN which represents the train formation/composition as a whole. -A journey (with VEHICLE TYPE 'rail') does always have one or more JOURNEY PARTs in which the train composition remains unchanged. +SIRI v2.1 + Reference to COMPOUND TRAIN that represents the train formation/composition as a whole (for this JOURNEY PART). +SIRI v2.1 +A journey does always have one or more JOURNEY PARTs for which the train formation/composition remains unchanged. @@ -353,8 +353,9 @@ A journey (with VEHICLE TYPE 'rail') does always have one or more JOURNEY PARTs - Reference to a COMPOUND TRAIN which represents the train formation/composition as a whole. -A journey (with VEHICLE TYPE 'rail') does always have one or more JOURNEY PARTs in which the train composition remains unchanged. + Reference to COMPOUND TRAIN that represents the train formation/composition as a whole (for this JOURNEY PART). +SIRI v2.1 +A journey does always have one or more JOURNEY PARTs for which the train formation/composition remains unchanged. + @@ -362,7 +363,7 @@ A journey (with VEHICLE TYPE 'rail') does always have one or more JOURNEY PARTs - JourneyPart information instead of or in addition to the JourneyPartRef. +SIRI v2.0 + If no JOURNEY PART reference is available (or in addition to the reference), identify it indirectly by From-/ToStopPointRef and Start-/EndTime (i.e. the scheduled times at these stops). +SIRI v2.1 From c32136315b36245a63d512108900649d08f0f2f6 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Sat, 4 Jul 2020 01:19:28 +0200 Subject: [PATCH 153/290] CR002: clean-up for comments 630089574 / 428639912 --- xsd/siri_model/siri_journey-v2.0.xsd | 84 ++++++++++++---------------- 1 file changed, 37 insertions(+), 47 deletions(-) diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index 262adfc7..b956df2e 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -1008,8 +1008,11 @@ Groups of carriages may be managed as sections by composing TRAINs into a COMPOU - Indication of the direction of travel of the vehicle or formation (e.g. TRAIN composition ) with respect to the platform, or more precisely the QUAY. -For example "towards A", which means that the vehicle departs towards sector "A" of the QUAY. It is advised to specify a reference point that is meaningful for passengers on location. +SIRI v2.1 + Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. +SIRI v2.1 +Examples: +- "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle arriving or departing in the direction of sector A on a QUAY with sectors A-B-C-D. If the arriving vehicle is represented as an arrow, "towards A" would be abstracted as "=> A-B-C-D". If the departing vehicle is represented as an arrow, "towards A" would be abstracted as "<= A-B-C-D". +- "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle arriving or departing in the direction of this reference point. If the arriving vehicle is represented as an arrow, "towards 0" would be abstracted as "=> 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). If the departing vehicle is represented as an arrow, "towards 0" would be abstracted as "<= 0...100". +It is advised to specify a reference point that is meaningful for passengers on location. @@ -1020,26 +1023,21 @@ For example "towards A", which means that the vehicle departs towards sector "A" Assignment of the arrival/departure of a VEHICLE within a formation, e.g. carriage in a TRAIN composition, to a physical QUAY or nested QUAY (i.e. platform or sector of a platform). +SIRI v2.1 - - - - - - + Relative position of TRAIN ELEMENT. - + - Reference to the QUAY on which the particular VEHICLE of the formation arrives or departs from. -If a QUAY is divided into sectors (with the help of STOP ASSIGNMENTs), and a VEHICLE stops in two sectors of the QUAY, the FORMATION ASSIGNMENT must reference both. +SIRI v2.1 + Reference to the QUAY on which the particular VEHICLE, i.e., component of the formation, arrives or departs from. +If a QUAY is divided into sectors (with the help of STOP ASSIGNMENTs), and a wagon/coach, or TRAIN COMPONENT respectively, stops in two sectors of the QUAY, the FORMATION ASSIGNMENT must reference both. - Information about a change of a VEHICLE within the formation, e.g., whether a VEHICLE is open, booked or has defective doors. +SIRI v2.1 + Information about a change of a VEHICLE within the formation, e.g., whether a VEHICLE is open, booked or has defective doors. @@ -1059,12 +1057,12 @@ If a QUAY is divided into sectors (with the help of STOP ASSIGNMENTs), and a VEH - Status of formation. + Status of formation, e.g., whether it has changed compared to the plan, certain VEHICLEs or features are missing or extra VEHICLEs are added. - Status of a vehicle within formation. + Status of a VEHICLE within formation, e.g., whether a VEHICLE is open, booked or has defective doors. @@ -1338,8 +1336,8 @@ More accurate data can be provided by the individual occupancies or capacities b Identifier for TRAIN ELEMENT. - + @@ -1352,14 +1350,10 @@ More accurate data can be provided by the individual occupancies or capacities b Type of TRAIN ELEMENT. - - - Denotes the official "registration number" of the vehicle. Mainly for production purposes. - - - + + - Advertised serial number of the vehicle for seat reservations and passenger orientation. + Denotes the official "registration number" of the vehicle or wagon/coach. In rail transport VEHICLE NUMBER would be equal to the 12 digit UIC wagon/coach number, possibly followed by other combinations of letters, e.g. by the UIC classification of railway coaches. @@ -1368,7 +1362,7 @@ More accurate data can be provided by the individual occupancies or capacities b - An assembled TRAIN ELEMENT as part of a TRAIN, i.e., a TRAIN ELEMENT with a certain position or order within a TRAIN. +SIRI v2.1 + Specifies the order of a certain TRAIN ELEMENT within a TRAIN and how the TRAIN ELEMENT is labeled in that context. +SIRI v2.1 @@ -1383,7 +1377,7 @@ More accurate data can be provided by the individual occupancies or capacities b - Order of the TRAIN COMPONENT (or more precisely the referenced TRAIN ELEMENT) within the TRAIN. + Specifies the order of the TRAIN ELEMENT within the TRAIN. The locomotive would ideally have ORDER '1', the first wagon/coach attached to the locomotive ORDER '2' and so on. @@ -1396,12 +1390,12 @@ More accurate data can be provided by the individual occupancies or capacities b - Label for TRAIN COMPONENT. + Specifies how the TRAIN ELEMENT is labeled within the context of the TRAIN. This advertised label or number, e.g. "Carriage B" or "23", can be used for seat reservations and passenger orientation. - Description of TRAIN COMPONENT. + Description of TRAIN COMPONENT, e.g. "Front Carriage 1st Class". @@ -1418,7 +1412,7 @@ More accurate data can be provided by the individual occupancies or capacities b - A vehicle composed of TRAIN ELEMENTs assembled in a certain order (so called TRAIN COMPONENTs), i.e. of wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 + A vehicle composed of TRAIN ELEMENTs assembled in a certain order (so called TRAIN COMPONENTs), i.e. wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 @@ -1447,12 +1441,12 @@ More accurate data can be provided by the individual occupancies or capacities b - Nature of Train Size., Short, long, normal. Default is normal. + Nature of TRAIN size, e.g "short", "long", "normal". Default is "normal". - + - Ordered collection of TRAIN COMPONENTs making up TRAIN. + Ordered collection of TRAIN COMPONENTs making up the TRAIN. @@ -1466,7 +1460,8 @@ More accurate data can be provided by the individual occupancies or capacities b - Groups of carriages may be managed as sections by composing TRAINs into a COMPOUND TRAIN, for example if a train joins (or splits from) another train. +SIRI v2.1 + Groups of carriages may be managed as sections by composing TRAINs into a COMPOUND TRAIN, for example if a TRAIN joins (or splits from) another TRAIN. +SIRI v2.1 +TRAINs within a COMPOUND TRAIN may have different origins and destinations due to joining/splitting. A COMPOUND TRAIN may be stable for one or multiple JOURNEY PARTs and change at a certain STOP POINT due to planned joining/splitting, despatching alterations or a situation. @@ -1480,9 +1475,9 @@ More accurate data can be provided by the individual occupancies or capacities b - + - Ordered collection of TRAINs making up a COMPOUND TRAIN. Each of those components is or references a TRAIN. + Ordered collection of TRAINs making up the COMPOUND TRAIN. @@ -1495,7 +1490,7 @@ More accurate data can be provided by the individual occupancies or capacities b - An instance of a TRAIN (that has a certain position within the formation) making up a COMPOUND TRAIN. +SIRI v2.1 + Specifies the order of a certain TRAIN within a COMPOUND TRAIN and how the TRAIN is labeled in that context. +SIRI v2.1 @@ -1510,7 +1505,7 @@ More accurate data can be provided by the individual occupancies or capacities b - Order of TRAIN within COMPOUND TRAIN. + Specifies the order of the TRAIN within the COMPOUND TRAIN. @@ -1523,7 +1518,7 @@ More accurate data can be provided by the individual occupancies or capacities b - Label for TRAIN IN COMPOUND TRAIN. + Specifies how the TRAIN is labeled within the context of the COMPOUND TRAIN. This advertised label or number, e.g. the individual TRAIN NUMBER, can be used for seat reservations and passenger orientation. @@ -1543,28 +1538,23 @@ More accurate data can be provided by the individual occupancies or capacities b - Specifies whether a passage from/to an adjacent VEHICLE is possible for passengers. + Specifies whether a passage from/to an adjacent TRAIN is possible for passengers. - + - + - Indicates whether passengers have access to adjacent VEHICLEs or carriages, i.e., whether passage between those VEHICLES is possible. +SIRI v2.1 + Indicates whether passengers have access to adjacent TRAINs or TRAIN COMPONENTs within a COMPOUND TRAIN, i.e., whether passage between those wagons/coaches is possible. +SIRI v2.1 - - - - - - - + + From 5d2e2f548363fbfc3b0d91cdb9e8ddd5912a364d Mon Sep 17 00:00:00 2001 From: Adrian A Date: Mon, 6 Jul 2020 00:07:10 +0200 Subject: [PATCH 154/290] CR002: rename VehicleStatus in FormationCondition --- xsd/siri_model/siri_journey-v2.0.xsd | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index b956df2e..10cb410e 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -1060,7 +1060,7 @@ If a QUAY is divided into sectors (with the help of STOP ASSIGNMENTs), and a wag Status of formation, e.g., whether it has changed compared to the plan, certain VEHICLEs or features are missing or extra VEHICLEs are added. - + Status of a VEHICLE within formation, e.g., whether a VEHICLE is open, booked or has defective doors. @@ -1088,7 +1088,7 @@ If a QUAY is divided into sectors (with the help of STOP ASSIGNMENTs), and a wag - + Description of the status of a monitored vehicle. @@ -1353,7 +1353,7 @@ More accurate data can be provided by the individual occupancies or capacities b - Denotes the official "registration number" of the vehicle or wagon/coach. In rail transport VEHICLE NUMBER would be equal to the 12 digit UIC wagon/coach number, possibly followed by other combinations of letters, e.g. by the UIC classification of railway coaches. + Denotes the official "registration number" of the vehicle or wagon/coach. In rail transport VEHICLE NUMBER would be equal to the 12-digit UIC wagon/coach number, possibly followed by other combinations of letters, e.g. by the UIC classification of railway coaches. From d76eb85267d2eb1d2d7da8a7cae3cd6666dfaa91 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Mon, 6 Jul 2020 00:16:18 +0200 Subject: [PATCH 155/290] CR002: rename VehicleStatus in FormationAssignment --- xsd/siri_model/siri_journey-v2.0.xsd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index 10cb410e..67c688e8 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -1035,7 +1035,7 @@ It is advised to specify a reference point that is meaningful for passengers on If a QUAY is divided into sectors (with the help of STOP ASSIGNMENTs), and a wagon/coach, or TRAIN COMPONENT respectively, stops in two sectors of the QUAY, the FORMATION ASSIGNMENT must reference both. - + Information about a change of a VEHICLE within the formation, e.g., whether a VEHICLE is open, booked or has defective doors. From f9416e49013b390d6413dd6ac1dc30f6ff733c09 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Mon, 6 Jul 2020 00:25:30 +0200 Subject: [PATCH 156/290] TypeOfActionRef in FormationCondition mandatory --- xsd/siri_model/siri_journey-v2.0.xsd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index 67c688e8..feab58f9 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -1124,7 +1124,7 @@ If a QUAY is divided into sectors (with the help of STOP ASSIGNMENTs), and a wag Description of the recommended action for passengers on how to deal with changes, for example of the TRAIN formation. - + Type of the recommendation, e.g. 'unknown', 'replacement' or 'otherRoute'. From 919cc4c62bab1a3498763c8a8d90dbc89773c075 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Mon, 6 Jul 2020 12:57:18 +0200 Subject: [PATCH 157/290] CR002: extend QuayRef in FormationAssignment --- xsd/siri_model/siri_journey-v2.0.xsd | 24 +++++++++++++++++------- 1 file changed, 17 insertions(+), 7 deletions(-) diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index feab58f9..6b5290ca 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -756,7 +756,7 @@ It is advised to specify a reference point that is meaningful for passengers on - Type for assignment of a SCHEDULED STOP POINT to a specific QUAY or platform +SIRI v2.0. + Type for assignment of a SCHEDULED STOP POINT to a specific QUAY or platform. +SIRI v2.0. @@ -771,7 +771,12 @@ It is advised to specify a reference point that is meaningful for passengers on - Physical QUAY to use accoring to the real-time prediction. +SIRI v2.0 + Physical QUAY to use according to the real-time prediction. +SIRI v2.0 + + + + + Expected Platform name. Can be used to indicate real-time prediction. +SIRI v2.1 @@ -779,6 +784,11 @@ It is advised to specify a reference point that is meaningful for passengers on Physical QUAY actually used. +SIRI v2.0 + + + Actual Platform name. Can be used to indicate recorded platform. +SIRI v2.1 + + @@ -1029,15 +1039,15 @@ It is advised to specify a reference point that is meaningful for passengers on Relative position of TRAIN ELEMENT. - + - Reference to the QUAY on which the particular VEHICLE, i.e., component of the formation, arrives or departs from. -If a QUAY is divided into sectors (with the help of STOP ASSIGNMENTs), and a wagon/coach, or TRAIN COMPONENT respectively, stops in two sectors of the QUAY, the FORMATION ASSIGNMENT must reference both. + Information about a change of a VEHICLE within the formation, e.g., whether a VEHICLE is open, booked or has defective doors. - + - Information about a change of a VEHICLE within the formation, e.g., whether a VEHICLE is open, booked or has defective doors. + References to the QUAY on which the particular VEHICLE, i.e., component of the formation, arrives or departs from. +If a QUAY is divided into sub-QUAYs or sectors (with the help of STOP ASSIGNMENTs), and a TRAIN COMPONENT spans over multiple sectors of the QUAY, the FORMATION ASSIGNMENT must reference all of them (in multiple STOP ASSIGNMENTs). From aac99d7081af8ae423e57551dcca07fb48f20697 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 7 Jul 2020 16:25:22 +0200 Subject: [PATCH 158/290] CR002: change of Occupancy/Capacities and clean-up --- .../siri_estimatedVehicleJourney-v2.0.xsd | 18 +++--- xsd/siri_model/siri_journey-v2.0.xsd | 55 +++++++------------ .../siri_monitoredVehicleJourney-v2.0.xsd | 3 +- 3 files changed, 33 insertions(+), 43 deletions(-) diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index 771cbd94..f76e3f68 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -167,7 +167,8 @@ DEPRECATED from SRI 2.0 - How full the bus is. If omitted: Passenger load is unknown. + An approximate figure of how occupied the journey is after departing from a given stop, e.g. 'manySeatsAvailable' or 'standingRoomOnly'. If omitted: Passenger load is unknown. +Occupancies and capacities for individual VEHICLEs, e.g. parts of a COMPOUND TRAIN, can also be specified in more detail for the departure on CALL level. @@ -366,7 +367,8 @@ the original journey and the nature of the difference. - How full the bus is at the stop. If omitted: Passenger load is unknown. + An approximate figure of how occupied the journey is after departing from a given stop, e.g. 'manySeatsAvailable' or 'standingRoomOnly'. If omitted: Passenger load is unknown. +Occupancies and capacities for individual VEHICLEs, e.g. parts of a COMPOUND TRAIN, can also be specified in more detail for the departure on CALL level. @@ -408,11 +410,6 @@ the original journey and the nature of the difference. Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). If not given, assume same as for departure. +SIRI v2.1 - - - Recorded occupancies and capacities of a vehicle (by fare classes) when arriving at a given STOP POINT. +SIRI v2.1 - - Target departure time of VEHICLE according to latest working timetable. @@ -455,7 +452,12 @@ the original journey and the nature of the difference. - Recorded occupancies and capacities of a vehicle (by fare classes) when departing at a given STOP POINT. +SIRI v2.1 + Recorded occupancies of a VEHICLE and reserved seats after departing from a given stop. +SIRI v2.1 + + + + + Recorded capacities of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. +SIRI v2.1 diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index 6b5290ca..57b0a0b3 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -514,11 +514,6 @@ It is advised to specify a reference point that is meaningful for passengers on - - - Real-time occupancies and capacities of a vehicle (by fare classes) when arriving at a given STOP POINT. +SIRI v2.1 - - OPERATORs of of servcie up until arrival.. May change for departure. +SIRI v2.0. @@ -561,7 +556,12 @@ It is advised to specify a reference point that is meaningful for passengers on - Real-time occupancies and capacities of a vehicle (by fare classes) when departing at a given STOP POINT. +SIRI v2.1 + Real-time occupancies of a VEHICLE and reservations after departing from a given stop. +SIRI v2.1 + + + + + Real-time capacities (number of available seats) of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. +SIRI v2.1 @@ -1150,7 +1150,7 @@ If a QUAY is divided into sub-QUAYs or sectors (with the help of STOP ASSIGNMENT - Elements for a PASSENGER CAPACITY. Used to indicate the maximum capacities of a TRAIN ELEMENT or the estimated/recorded capacities of a TRAIN ELEMENT at a specific stop (in number of passengers). +SIRI v2.1 + Elements for a PASSENGER CAPACITY. Used to indicate the maximum capacities of a TRAIN ELEMENT or the estimated/recorded capacities of a VEHICLE at a given stop, i.e., the number of seats available. +SIRI v2.1 @@ -1170,7 +1170,7 @@ If a QUAY is divided into sub-QUAYs or sectors (with the help of STOP ASSIGNMENT - The number of special places on the vehicle, e.g. seats for the disabled. + The number of special places on the vehicle, e.g. seats for the disabled or lounge seats. @@ -1203,7 +1203,7 @@ If a QUAY is divided into sub-QUAYs or sectors (with the help of STOP ASSIGNMENT - Fare class in VEHICLE for which occupancy and capacities are specified. + Fare class in VEHICLE for which occupancy or capacities are specified. @@ -1220,7 +1220,7 @@ If a QUAY is divided into sub-QUAYs or sectors (with the help of STOP ASSIGNMENT - An approximate figure of how occupied or full the VEHICLE is, e.g. manySeatsAvailable or standingRoomOnly. + An approximate figure of how occupied or full a VEHICLE and its parts are, e.g. 'manySeatsAvailable' or 'standingRoomOnly'. More accurate data can be provided by the individual occupancies or capacities below. @@ -1246,7 +1246,7 @@ More accurate data can be provided by the individual occupancies or capacities b - Total number of special places, e.g. seats for the disabled, that are occupied after departing the STOP POINT. + Total number of special places, e.g. seats for the disabled or lounge seats, that are occupied after departing the STOP POINT. @@ -1281,7 +1281,7 @@ More accurate data can be provided by the individual occupancies or capacities b Name for which the travel group has made the reservation. - + Number of seats that the group has booked. @@ -1291,23 +1291,16 @@ More accurate data can be provided by the individual occupancies or capacities b - Occupancies and real-time capacities of a vehicle (by fare classes). +SIRI v2.1 + Real-time occupancies of a VEHICLE (by fare class). Could be feedback from an automatic passenger counting system (APC) or estimated values from statistics. +SIRI v2.1 - + - Provides capacity information relevant for the used occupancy scope filter. + Total number of booked seats from individual and group reservations. - - - - - - Reservations of travel groups, i.e., name of group and number of seats booked. @@ -1315,21 +1308,15 @@ More accurate data can be provided by the individual occupancies or capacities b - - Maximum capacities of a vehicle, e.g. TRAIN ELEMENT, by its fare classes. +SIRI v2.1 + Real-time capacities of a VEHICLE (by fare class), i.e., number of available seats. Alternative way to communicate occupancy measurements. +SIRI v2.1 - - - Maximum number of passengers that can be carried by a vehicle of given type. - - @@ -1485,7 +1472,7 @@ TRAINs within a COMPOUND TRAIN may have different origins and destinations due t - + Ordered collection of TRAINs making up the COMPOUND TRAIN. @@ -1629,16 +1616,16 @@ TRAINs within a COMPOUND TRAIN may have different origins and destinations due t - Euroclass of the vehicle type. + Euroclass of the vehicle type. Corresponds to the 12-digit European Identification Number (EIN). - + - Break down of capacities by FARE CLASS (number of passengers that TRAIN ELEMENT can carry). + Break down of capacities by FARE CLASS, i.e., maximum number of passengers that TRAIN ELEMENT can carry. - + diff --git a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd index 7f237f0f..c174d8fa 100644 --- a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd @@ -207,7 +207,8 @@ Rail transport, Roads and road transport - How full the VEHICLE is. If omitted, not known. + An approximate figure of how occupied the journey is across all of its stops, e.g. 'manySeatsAvailable' or 'standingRoomOnly'. If omitted: Passenger load is unknown. +Occupancies and capacities for individual VEHICLEs, e.g. parts of a COMPOUND TRAIN, can also be specified in more detail for the departure on CALL level. From 920ba161db3e44ef6fd2deed73c6abd65dafe4b4 Mon Sep 17 00:00:00 2001 From: u215619 Date: Thu, 9 Jul 2020 17:27:41 +0200 Subject: [PATCH 159/290] StopPlaceRef / StopPlaceName added to AffectedStopPointStructure Lines added to AffectedStopPointStructure StopPoints and StopPlaces added to AffectedLineStructure --- xsd/siri_model/siri_situationAffects-v2.0.xsd | 41 +++++++++++++++++++ 1 file changed, 41 insertions(+) diff --git a/xsd/siri_model/siri_situationAffects-v2.0.xsd b/xsd/siri_model/siri_situationAffects-v2.0.xsd index 747ac04e..ccc1acdd 100644 --- a/xsd/siri_model/siri_situationAffects-v2.0.xsd +++ b/xsd/siri_model/siri_situationAffects-v2.0.xsd @@ -134,6 +134,17 @@ Rail transport, Roads and road transport Spatial coordinates of STOP POINT. Derivable from StopRef. + + + Reference of Stop Place related to this affected StopPoint. + + + + + vdv20200626-02 + Name of Stop Place related to this affected StopPoint. (Unbounded to allow a text for every language) + + Modes within station/stop affected by the SITUATION. If not specified, assume all modes of that station. @@ -173,6 +184,16 @@ Rail transport, Roads and road transport + + + Used to restrict stop points to some lines + + + + + + + @@ -593,6 +614,26 @@ Rail transport, Roads and road transport + + + Used to restrict lines to some stop points + + + + + + + + + + Used to restrict lines to some stop places + + + + + + + From 4ebe8e1cfb06723f6087cf5b62df83840cd44a0d Mon Sep 17 00:00:00 2001 From: u215619 Date: Fri, 10 Jul 2020 05:54:33 +0200 Subject: [PATCH 160/290] swiss changelog deleted --- xsd/siri_model/siri_situationAffects-v2.0.xsd | 1 - 1 file changed, 1 deletion(-) diff --git a/xsd/siri_model/siri_situationAffects-v2.0.xsd b/xsd/siri_model/siri_situationAffects-v2.0.xsd index ccc1acdd..a5ba355c 100644 --- a/xsd/siri_model/siri_situationAffects-v2.0.xsd +++ b/xsd/siri_model/siri_situationAffects-v2.0.xsd @@ -141,7 +141,6 @@ Rail transport, Roads and road transport - vdv20200626-02 Name of Stop Place related to this affected StopPoint. (Unbounded to allow a text for every language) From c01e2445aee30df5ac84bc6b5311c98f0644a124 Mon Sep 17 00:00:00 2001 From: u215619 Date: Tue, 14 Jul 2020 09:43:39 +0200 Subject: [PATCH 161/290] New proposal for PublishingAction integration in Siri --- xsd/siri_model/siri_situationActions-v2.0.xsd | 328 +++++++++++++++++- 1 file changed, 326 insertions(+), 2 deletions(-) diff --git a/xsd/siri_model/siri_situationActions-v2.0.xsd b/xsd/siri_model/siri_situationActions-v2.0.xsd index f1919f1c..85da3ffa 100644 --- a/xsd/siri_model/siri_situationActions-v2.0.xsd +++ b/xsd/siri_model/siri_situationActions-v2.0.xsd @@ -1,6 +1,10 @@ + + + + @@ -90,6 +94,42 @@ Rail transport, Roads and road transport Type for list of SITUATIONs. + + + Reference to the action number within the incident concept. + + + + + The time of the last update + + + + + The monotonically inscresing version of the passenger information instance. If absent, is the same version as the enclosing Situation + + + + + The system which created this passenger information. If absent, is the same version as the enclosing Situation + + + + + The organisation which owns this passenger information. + + + + + Perspective of the passenger, e.g. general, vehicleJourney, stopPoint. + + + + + Prioritises a passenger information action from the information owner's point of view, e.g. suitable for sorting or hiding individual passenger information actions. + 1 = highest priority. + + Processing Status of action at time of SITUATION publication. @@ -110,10 +150,33 @@ Rail transport, Roads and road transport Description of action. - + + + + Data associated with action. + + + + + All texts of the passenger information. + + + + + + Defines a number of validity periods. When not sent, then the validity periods of higher level are valid. Can be overwritten by deeper level. + + + - Data associated with action. + Defines the information area where the action has to be published. + + + + + + @@ -467,4 +530,265 @@ Rail transport, Roads and road transport + + + + + + Description of SITUATION. Should not repeat any strap line included in Summary. (Unbounded since SIRI 2.0) + + + + + TBD + + + + + + + Extension point. + + + + + + + + Prioritises a description from the information owner's point of view, e.g. usable for sorting or hiding individual descriptions. + 1 = highest priority. + + + + + + + + + Further consequence to passengers. (Unbounded since SIRI 2.0) + + + + + TBD + + + + + + + Extension point. + + + + + + + + Prioritises a consequence from the information owner's point of view, e.g. usable for sorting or hiding individual consequences. + 1 = highest priority. + + + + + + + + + Further information about the duration to passengers. + + + + + + + Values for reason in cloze. + + + + + + + + + + ReasonName of passenger information action. + + + + + TBD + + + + + + + + Extension point. + + + + + + + + + + + + Further recommendation to passengers. (Unbounded since SIRI 2.0) + + + + + TBD + + + + + + + Extension point. + + + + + + + + Prioritises a recommendation from the information owner's point of view, e.g. usable for sorting or hiding individual recommendations. + 1 = highest priority. + + + + + + + + + + + + + Values for reason in cloze. + + + + + + + + + + + + + Further remark to passengers, e,g, "For more information call xy". + + + + + Prioritises a remark from the information owner's point of view, e.g. usable for sorting or hiding individual remarks. + 1 = highest priority. + + + + + + + + + Summary of passenger information action. + + + + + TBD + + + + + + Enum for summary description. Enums are TBD + + + + + + Extension point. + + + + + + + + + + + + Class of size, e.g. L (large), M (medium), S (small) + + + + + + Content for summary of a passenger information action + + + + + + Content for n descriptions of a passenger information action + + + + + Content for n consequences of a passenger information action + + + + + Content for n recommendations of a passenger information action + + + + + Content to inform about a passenger information action. + + + + + Content for n remarks of a passenger information action, e,g, "For more information call xy". + + + + + Hyperlinks to other resources associated with SITUATION. + + + + + Any images associated with SITUATION. + + + + + for internal information only, not passenger relevant + + + + + + + Values for perspectives. + + + + + + + + From 12d87170cc1f224ecb17946ba7656ebee9a3bf43 Mon Sep 17 00:00:00 2001 From: u215619 Date: Tue, 14 Jul 2020 09:48:54 +0200 Subject: [PATCH 162/290] annotations improved --- xsd/siri_model/siri_situationActions-v2.0.xsd | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/xsd/siri_model/siri_situationActions-v2.0.xsd b/xsd/siri_model/siri_situationActions-v2.0.xsd index 85da3ffa..27a3529d 100644 --- a/xsd/siri_model/siri_situationActions-v2.0.xsd +++ b/xsd/siri_model/siri_situationActions-v2.0.xsd @@ -106,17 +106,17 @@ Rail transport, Roads and road transport - The monotonically inscresing version of the passenger information instance. If absent, is the same version as the enclosing Situation + The monotonically increasing version of the action instance. If absent, is the same version as the enclosing Situation - The system which created this passenger information. If absent, is the same version as the enclosing Situation + The system which created this action information. If absent, is the same version as the enclosing Situation - The organisation which owns this passenger information. + The organisation which owns this action information. From d4f43d60e0cdd55e9f6a5906d7e4d36299f573bc Mon Sep 17 00:00:00 2001 From: u215619 Date: Thu, 16 Jul 2020 21:57:32 +0200 Subject: [PATCH 163/290] Integrate publishingAction in ParameterisedAction Leave out priority in textual content / cardinality changes in the passenger information action bundle infoLink / image / internal text in wrapper structures --- xsd/siri_model/siri_situation-v2.0.xsd | 58 +++-- xsd/siri_model/siri_situationActions-v2.0.xsd | 224 ++++++------------ 2 files changed, 101 insertions(+), 181 deletions(-) diff --git a/xsd/siri_model/siri_situation-v2.0.xsd b/xsd/siri_model/siri_situation-v2.0.xsd index 12e8f076..c317213d 100644 --- a/xsd/siri_model/siri_situation-v2.0.xsd +++ b/xsd/siri_model/siri_situation-v2.0.xsd @@ -1052,6 +1052,23 @@ Note: this means that ReasonName is NOT a complete message, but only a (few) wor + + + Any images associated with SITUATION. + + + + + Image description. + + + + + + + + + Type for image. @@ -1106,43 +1123,20 @@ Note: this means that ReasonName is NOT a complete message, but only a (few) wor Further advice to passengers. (Unbounded since SIRI 2.0) - + Further advice to passengers. - + Any images associated with SITUATION. - - - - - Image description. - - - - - - - - - - + Hyperlinks to other resources associated with SITUATION. - - - - - Hyperlink description. - - - - @@ -1182,6 +1176,18 @@ Note: this means that ReasonName is NOT a complete message, but only a (few) wor + + + Hyperlinks to other resources associated with SITUATION. + + + + + Hyperlink description. + + + + Type for a general hyperlink. diff --git a/xsd/siri_model/siri_situationActions-v2.0.xsd b/xsd/siri_model/siri_situationActions-v2.0.xsd index 27a3529d..263715b3 100644 --- a/xsd/siri_model/siri_situationActions-v2.0.xsd +++ b/xsd/siri_model/siri_situationActions-v2.0.xsd @@ -32,6 +32,9 @@ [vdv] PublishToDisplayAction added to ActionsGroup [vdv] ActionsStructure.ActionsGroup.PublishToTvAction.Ceefax and Teletext: annotation switched + 2020-07-14 + [vdv] New elements added to the ParameterisedActionStructure +

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

@@ -94,32 +97,43 @@ Rail transport, Roads and road transport Type for list of SITUATIONs. - + + + Processing Status of action at time of SITUATION publication. + + + + + + + + + Reference to the action number within the incident concept. - + The time of the last update - The monotonically increasing version of the action instance. If absent, is the same version as the enclosing Situation + The monotonically inscresing version of the passenger information instance. If absent, is the same version as the enclosing Situation - The system which created this action information. If absent, is the same version as the enclosing Situation + The system which created this passenger information. If absent, is the same version as the enclosing Situation - The organisation which owns this action information. + The organisation which owns this passenger information. - + Perspective of the passenger, e.g. general, vehicleJourney, stopPoint. @@ -130,14 +144,37 @@ Rail transport, Roads and road transport 1 = highest priority. - + - Processing Status of action at time of SITUATION publication. + All texts of the passenger information. + + + + + + + + + Defines the information area where the action has to be published. + + + + + + + + + Type for description of the whole action to be published. + + + + + + Description of the whole passenger information of one action. - Type for parameterised, i.e. user definable, actions. @@ -156,9 +193,9 @@ Rail transport, Roads and road transport Data associated with action. - + - All texts of the passenger information. + Type for description of the whole action to be published. @@ -167,17 +204,6 @@ Rail transport, Roads and road transport Defines a number of validity periods. When not sent, then the validity periods of higher level are valid. Can be overwritten by deeper level. - - - Defines the information area where the action has to be published. - - - - - - - - @@ -538,27 +564,6 @@ Rail transport, Roads and road transport Description of SITUATION. Should not repeat any strap line included in Summary. (Unbounded since SIRI 2.0) - - - TBD - - - - - - - Extension point. - - - - - - - - Prioritises a description from the information owner's point of view, e.g. usable for sorting or hiding individual descriptions. - 1 = highest priority. - - @@ -568,27 +573,6 @@ Rail transport, Roads and road transport Further consequence to passengers. (Unbounded since SIRI 2.0) - - - TBD - - - - - - - Extension point. - - - - - - - - Prioritises a consequence from the information owner's point of view, e.g. usable for sorting or hiding individual consequences. - 1 = highest priority. - - @@ -600,14 +584,6 @@ Rail transport, Roads and road transport - - - Values for reason in cloze. - - - - - @@ -615,71 +591,17 @@ Rail transport, Roads and road transport ReasonName of passenger information action. - - - TBD - - - - - - - - Extension point. - - - - - - + - + Further recommendation to passengers. (Unbounded since SIRI 2.0) - - - TBD - - - - - - - Extension point. - - - - - - - - Prioritises a recommendation from the information owner's point of view, e.g. usable for sorting or hiding individual recommendations. - 1 = highest priority. - - - - - - - - - - - Values for reason in cloze. - - - - - - - - @@ -702,25 +624,14 @@ Rail transport, Roads and road transport Summary of passenger information action. - + + + + + - TBD + Summary of passenger information action. - - - - - Enum for summary description. Enums are TBD - - - - - - Extension point. - - - - @@ -731,26 +642,29 @@ Rail transport, Roads and road transport Class of size, e.g. L (large), M (medium), S (small) - Content for summary of a passenger information action - - + + + Content for n reasons of a passenger information action + + + Content for n descriptions of a passenger information action - + Content for n consequences of a passenger information action - + - Content for n recommendations of a passenger information action + Content for n advices of a passenger information action @@ -758,22 +672,22 @@ Rail transport, Roads and road transport Content to inform about a passenger information action. - + Content for n remarks of a passenger information action, e,g, "For more information call xy". - + Hyperlinks to other resources associated with SITUATION. - + Any images associated with SITUATION. - + for internal information only, not passenger relevant From 86f60d46dca4280a9c4515d5897b59cb46f4cdcb Mon Sep 17 00:00:00 2001 From: u215619 Date: Mon, 20 Jul 2020 07:15:47 +0200 Subject: [PATCH 164/290] delete RemarkPriority Harmonize Internal/Image/InfoLink in situation and -action --- xsd/siri_model/siri_situationActions-v2.0.xsd | 14 ++++---------- 1 file changed, 4 insertions(+), 10 deletions(-) diff --git a/xsd/siri_model/siri_situationActions-v2.0.xsd b/xsd/siri_model/siri_situationActions-v2.0.xsd index 263715b3..85d281f2 100644 --- a/xsd/siri_model/siri_situationActions-v2.0.xsd +++ b/xsd/siri_model/siri_situationActions-v2.0.xsd @@ -609,12 +609,6 @@ Rail transport, Roads and road transport Further remark to passengers, e,g, "For more information call xy". - - - Prioritises a remark from the information owner's point of view, e.g. usable for sorting or hiding individual remarks. - 1 = highest priority. - - @@ -677,9 +671,9 @@ Rail transport, Roads and road transport Content for n remarks of a passenger information action, e,g, "For more information call xy". - + - Hyperlinks to other resources associated with SITUATION. + for internal information only, not passenger relevant @@ -687,9 +681,9 @@ Rail transport, Roads and road transport Any images associated with SITUATION. - + - for internal information only, not passenger relevant + Hyperlinks to other resources associated with SITUATION. From 59eb50efe8e0a791e47835385d5c2fcf7549db38 Mon Sep 17 00:00:00 2001 From: u215619 Date: Mon, 20 Jul 2020 07:33:08 +0200 Subject: [PATCH 165/290] Annotation harmonized for "Internal" --- xsd/siri_model/siri_situation-v2.0.xsd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xsd/siri_model/siri_situation-v2.0.xsd b/xsd/siri_model/siri_situation-v2.0.xsd index c317213d..350c7cc2 100644 --- a/xsd/siri_model/siri_situation-v2.0.xsd +++ b/xsd/siri_model/siri_situation-v2.0.xsd @@ -1125,7 +1125,7 @@ Note: this means that ReasonName is NOT a complete message, but only a (few) wor - Further advice to passengers. + For internal information only, not passenger relevant From 5497271bca1ee36e95ed718c44c402094f1fd2d9 Mon Sep 17 00:00:00 2001 From: u215619 Date: Mon, 27 Jul 2020 16:25:22 +0200 Subject: [PATCH 166/290] Additions to CR15-RoutePointTypeEnum --- .../siri_situationServiceTypes-v1.0.xsd | 69 +++++++++++++++++-- 1 file changed, 62 insertions(+), 7 deletions(-) diff --git a/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd b/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd index 6ac66a03..89883cd9 100644 --- a/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd +++ b/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd @@ -440,22 +440,28 @@ There are several possible reasons for the loss of a feeder, e.g. loss/cancellat - Values for TPEG Pti015 - RoutePointType + Values for TPEG PTS044: StopPlaceUsage - RoutePointType (Pti015: deprecated since SIRI v2.1) - TPEG Pti15_0, unknown + TPEG Pti15_0, PTS044_0 unknown - TPEG Pti15_1, start point + TPEG Pti15_1, start point + Deprecated since SIRI v2.1. Use the PTS value 'origin' (PTS044_1) instead. + + + + + TPEG PTS044_1, origin - TPEG Pti15_2, destination + TPEG Pti15_2, PTS044_2 destination @@ -465,7 +471,13 @@ There are several possible reasons for the loss of a feeder, e.g. loss/cancellat - TPEG Pti15_4, via + TPEG Pti15_4, via + Deprecated since SIRI v2.1. Use the PTS value 'intermediate' (PTS044_3) instead. + + + + + TPEG PTS044_3, intermediate. @@ -520,19 +532,62 @@ There are several possible reasons for the loss of a feeder, e.g. loss/cancellat - TPEG Pti15_15, altered start point + TPEG Pti15_15, altered start point + Deprecated since SIRI v2.1. Use the PTS value 'firstRoutePoint' (PTS044_7) instead. + + + TPEG PTS044_7, first route point + + - TPEG Pti15_16, altered destination + TPEG Pti15_16, altered destination + Deprecated since SIRI v2.1. Use the PTS value 'lastRoutePoint' (PTS044_8) instead. + + + + TPEG PTS044_8, last route point + + TPEG Pti15_255, undefined route point + + + PTS044_4, leg board + + + + + PTS044_5, leg intermediate + + + + + PTS044_6, leg alight + + + + + PTS044_9, affected stop place + + + + + PTS044_10, presented stop place + + + + + PTS044_255, undefined stop place usage + + From 7e557f6f22b8ebed8b5258a53e14abcc23400d97 Mon Sep 17 00:00:00 2001 From: u215619 Date: Tue, 28 Jul 2020 04:24:27 +0200 Subject: [PATCH 167/290] validation error fixed --- .../siri_situationServiceTypes-v1.0.xsd | 74 ++++++++----------- 1 file changed, 30 insertions(+), 44 deletions(-) diff --git a/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd b/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd index 89883cd9..9e73b09f 100644 --- a/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd +++ b/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd @@ -5,7 +5,7 @@ main schema e-service developers - Add names + Add names Europe Drafted for version 1.0 Kizoom Incident Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk @@ -20,15 +20,15 @@ 2007-05-14 + [vdv] ReportTypeEnumeration TPEC-code "2_27_1_Alias_3" changed to "27_1_Alias_3" according to recommendation document + --> 2020-01-10 + Align with TPEG2 PTS + Remove numerical values ("Pti25_0") from enumerations + -->

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

@@ -41,27 +41,20 @@ {http://www.siri.org.uk/standards/siri/schema/2.0/xsd/siri_model/}siri_situationServiceTypes-v1.0.xsd [ISO 639-2/B] ENG CEN - - + Unclassified - Kizoom 2000-2007, CEN 2009-2020 - + Kizoom 2000-2007, CEN 2009-2020 +
    -
  • Schema derived Derived from the Kizoom XTIS schema
    • -
  • Derived from the TPEG2 PTS schemas
    • +
  • Schema derived Derived from the Kizoom XTIS schema
    • +
  • Derived from the TPEG2 PTS schemas
Version 2.0 - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - + Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, Ports and maritime transport, Ferries (marine), Public transport, Bus services, Coach services, Bus stops and stations, Rail transport, Railway stations and track, Train services, Underground trains, Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, Rail transport, Roads and road transport + CEN TC278 WG3 SG7 Xml Schema for PT Incidents. Service subschema @@ -146,7 +139,7 @@ Rail transport, Roads and road transport - Status of a SERVICE JOURNEY INTERCHANGE - TPEG Pti31 InterchangeStatus + Status of a SERVICE JOURNEY INTERCHANGE - TPEG Pti31 InterchangeStatus @@ -201,8 +194,7 @@ Rail transport, Roads and road transport - An important function of connection protection is the ability to hold back a distributor VEHICLE (i.e. prolonged waiting) to allow passengers to transfer from delayed feeders. -To achieve this a distributorWaitProlonged status shall be communicated back to the feeder VEHICLEs to inform the passengers about the new departure time of the distributor or even a willWait guarantee. +SIRI v2.1 + An important function of connection protection is the ability to hold back a distributor VEHICLE (i.e. prolonged waiting) to allow passengers to transfer from delayed feeders. To achieve this a distributorWaitProlonged status shall be communicated back to the feeder VEHICLEs to inform the passengers about the new departure time of the distributor or even a willWait guarantee. +SIRI v2.1 @@ -222,8 +214,7 @@ To achieve this a distributorWaitProlonged status shall be communicated back to - Loss of the inbound connection indicates the cancellation of the visit (of the FeederJourney) to the FeederArrivalStop, or a severely delayed arrival. This can lead to the distributor VEHICLE abandoning the connection. -There are several possible reasons for the loss of a feeder, e.g. loss/cancellation of the feeder VEHICLE, diversion of the feeder LINE/DIRECTION, disruption of a LINE section etc. +SIRI v2.1 + Loss of the inbound connection indicates the cancellation of the visit (of the FeederJourney) to the FeederArrivalStop, or a severely delayed arrival. This can lead to the distributor VEHICLE abandoning the connection. There are several possible reasons for the loss of a feeder, e.g. loss/cancellation of the feeder VEHICLE, diversion of the feeder LINE/DIRECTION, disruption of a LINE section etc. +SIRI v2.1 @@ -450,8 +441,7 @@ There are several possible reasons for the loss of a feeder, e.g. loss/cancellat - TPEG Pti15_1, start point - Deprecated since SIRI v2.1. Use the PTS value 'origin' (PTS044_1) instead. + TPEG Pti15_1, start point Deprecated since SIRI v2.1. Use the PTS value 'origin' (PTS044_1) instead. @@ -471,8 +461,7 @@ There are several possible reasons for the loss of a feeder, e.g. loss/cancellat - TPEG Pti15_4, via - Deprecated since SIRI v2.1. Use the PTS value 'intermediate' (PTS044_3) instead. + TPEG Pti15_4, via Deprecated since SIRI v2.1. Use the PTS value 'intermediate' (PTS044_3) instead. @@ -532,26 +521,23 @@ There are several possible reasons for the loss of a feeder, e.g. loss/cancellat - TPEG Pti15_15, altered start point - Deprecated since SIRI v2.1. Use the PTS value 'firstRoutePoint' (PTS044_7) instead. + TPEG Pti15_15, altered start point Deprecated since SIRI v2.1. Use the PTS value 'firstRoutePoint' (PTS044_7) instead. + + + + + TPEG PTS044_7, first route point - - - TPEG PTS044_7, first route point - - - TPEG Pti15_16, altered destination - Deprecated since SIRI v2.1. Use the PTS value 'lastRoutePoint' (PTS044_8) instead. + TPEG Pti15_16, altered destination Deprecated since SIRI v2.1. Use the PTS value 'lastRoutePoint' (PTS044_8) instead. + + + + + TPEG PTS044_8, last route point - - - - TPEG PTS044_8, last route point - - From 36ad24cdb6a42f9fc0eaaa7782585d1c08c6cb3a Mon Sep 17 00:00:00 2001 From: u215619 Date: Tue, 28 Jul 2020 04:54:59 +0200 Subject: [PATCH 168/290] new lines added in annotations --- xsd/siri_model/siri_situationServiceTypes-v1.0.xsd | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd b/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd index 9e73b09f..a0413182 100644 --- a/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd +++ b/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd @@ -441,7 +441,7 @@ - TPEG Pti15_1, start point Deprecated since SIRI v2.1. Use the PTS value 'origin' (PTS044_1) instead. + TPEG Pti15_1, start point
Deprecated since SIRI v2.1. Use the PTS value 'origin' (PTS044_1) instead. @@ -461,7 +461,7 @@ - TPEG Pti15_4, via Deprecated since SIRI v2.1. Use the PTS value 'intermediate' (PTS044_3) instead. + TPEG Pti15_4, via
Deprecated since SIRI v2.1. Use the PTS value 'intermediate' (PTS044_3) instead. @@ -521,7 +521,7 @@ - TPEG Pti15_15, altered start point Deprecated since SIRI v2.1. Use the PTS value 'firstRoutePoint' (PTS044_7) instead. + TPEG Pti15_15, altered start point
Deprecated since SIRI v2.1. Use the PTS value 'firstRoutePoint' (PTS044_7) instead. @@ -531,7 +531,7 @@ - TPEG Pti15_16, altered destination Deprecated since SIRI v2.1. Use the PTS value 'lastRoutePoint' (PTS044_8) instead. + TPEG Pti15_16, altered destination
Deprecated since SIRI v2.1. Use the PTS value 'lastRoutePoint' (PTS044_8) instead. From e6a9d5ae832d89c4c76cd87be5bd81e1f6a89992 Mon Sep 17 00:00:00 2001 From: u215619 Date: Tue, 28 Jul 2020 09:26:08 +0200 Subject: [PATCH 169/290] integrate PublicationWindow in ActionData Typos in annotations fixed --- xsd/siri_model/siri_situationActions-v2.0.xsd | 1394 ++++++++--------- 1 file changed, 696 insertions(+), 698 deletions(-) diff --git a/xsd/siri_model/siri_situationActions-v2.0.xsd b/xsd/siri_model/siri_situationActions-v2.0.xsd index 85d281f2..4cef5a67 100644 --- a/xsd/siri_model/siri_situationActions-v2.0.xsd +++ b/xsd/siri_model/siri_situationActions-v2.0.xsd @@ -1,702 +1,700 @@ - - - - - - - - - main schema - e-service developers - Add names - Europe - >Drafted for version 1.0 Kizoom SITUATION Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk - - 2006-09-29 - - - 2007-04-17 - - 2013-10-01 - (a) Added PublishToDisplayAction element definition - (b) Corrected default values for string fields - - 2013-05-01 - [de] Add SocialNetworks to PublishToWeb action - - 2018-11-13 - [vdv] ActionsStructure.ActionsGroup.PublishToTvAction changed to unbounded - [vdv] ActionsStructure.ActionsGroup.NotifyBySmsAction changed to unbounded - [vdv] PublishToDisplayAction added to ActionsGroup - [vdv] ActionsStructure.ActionsGroup.PublishToTvAction.Ceefax and Teletext: annotation switched - - 2020-07-14 - [vdv] New elements added to the ParameterisedActionStructure - - -

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

- - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/schema/2.0/xsd/siri_model}/siri_situationActions-v1.0.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types-v2.0.xsd - - Unclassified - - Kizoom 2000-2007, CEN 2009-2014 - - -
    -
  • Schema derived Derived from the Kizoom XTIS schema
    • -
- - Version 2.0 Draft - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI-SX XML Schema for PT SITUATIONs. Actions subschema - Standard - - - SIRI-SX Situation Actions. - - - - - - Type for list of actions. - - - - - - Extension point. - - - - - - - - Type for list of SITUATIONs. - - - - - Processing Status of action at time of SITUATION publication. - - - - - - - - - - - Reference to the action number within the incident concept. - - - - - The time of the last update - - - - - The monotonically inscresing version of the passenger information instance. If absent, is the same version as the enclosing Situation - - - - - The system which created this passenger information. If absent, is the same version as the enclosing Situation - - - - - The organisation which owns this passenger information. - - - - - Perspective of the passenger, e.g. general, vehicleJourney, stopPoint. - - - - - Prioritises a passenger information action from the information owner's point of view, e.g. suitable for sorting or hiding individual passenger information actions. - 1 = highest priority. - - - - - All texts of the passenger information. - - - - - - - - - Defines the information area where the action has to be published. - - - - - - - - - Type for description of the whole action to be published. - - - - - - Description of the whole passenger information of one action. - - - - - - - Type for parameterised, i.e. user definable, actions. - - - - - - - Description of action. - - - - - - Data associated with action. - - - - - Type for description of the whole action to be published. - - - - - - Defines a number of validity periods. When not sent, then the validity periods of higher level are valid. Can be overwritten by deeper level. - - - - - - - - - Type for publication action. - - - - - - - Whether reminders should be sent. - - - - - - Intervals before validity start date to send reminders. - - - - - - - - Whether a clearing notice should be displayed. - - - - - - - - - Values for Progress Status. - - - - - - - - - - Type for list of SITUATIONs. - - - - - Name of action data Element. - - - - - Data type of action data. - - - - - Value for action. - - - - - Display prompt for presenting action to user. (Unbounded since SIRI 2.0) - - - - - - - - Allowed actions to perform to distribute SITUATION. - - - - - - - - - - - - - - - - - Action: Publish SITUATION To Web. - - - - - Type for Action Publish SITUATION To Web. - - - - - - - Include in SITUATION lists on web site. Default is 'true'. - - - - - Include on home page on web site. Default is 'false'. - - - - - Include in moving ticker band. Default is 'false'. - - - - - Include in social NETWORK indicated by this name. Possible value could be "twitter.com", "facebook.com", "vk.com" and so on. Parameters may be specifed as Action data. (SIRIv 2.10) - - - - - - - - - Action: Publish SITUATION To WAP and PDA. - - - - - Type for Action Publish SITUATION To Displays. - - - - - - - Include in SITUATION lists on mobile site. Default is 'true'. - - - - - Include in home page on mobile site. Default is 'false'. - - - - - - - - - Action: Publish SITUATION To Displays. - - - - - Type for Action Publish SITUATION To Web. - - - - - - - Include in SITUATION lists on station displays. - - - - - Include onboard displays. - - - - - - - - - Action: Publish SITUATION To Alert Service. - - - - - Type for Action Publish SITUATION To Alert Service. - - - - - - - Send as email alert. - - - - - Send as mobile alert by SMS or WAP push. - - - - - - - - - Action: Publish SITUATION To TvService. - - - - - Type for Notify SITUATION to Tv. - - - - - - - Publish to Ceefax. Default is 'true'. - - - - - Publish to Teletext. Default is 'true'. - - - - - - - - - - Action: Publish SITUATION Manually. i.e. a procedure must be carried out. - - - - - - - - - - Type for Action Publish SITUATION Manual process. - - - - - - - - Action: Publish SITUATION to an individual by SMS. - - - - - Type for Notify user by SMS. - - - - - - - MSISDN of user to which to send messages. - - - - - Whether content is flagged as subject to premium charge. - - - - - - - - - Action: Publish SITUATION to a named workgroup or individual by email. - - - - - Type for Notify user by Email. - - - - - - - Email address to which notice should be sent. - - - - - - - - - Action: Publish SITUATION To pager. - - - - - Type for Notify user by Pager. - - - - - - - Reference to a pager group to be notfied. - - - - - Pager number of pager to be notfied. - - - - - - - - - Action: Publish SITUATION To User. - - - - - Type for Notify user by other means. - - - - - - - Workgroup of user to be notified. - - - - - Name of user to be notified. - - - - - Reference to a user to be notified. - - - - - - - - - - - - Description of SITUATION. Should not repeat any strap line included in Summary. (Unbounded since SIRI 2.0) - - - - - - - - - Further consequence to passengers. (Unbounded since SIRI 2.0) - - - - - - - - - Further information about the duration to passengers. - - - - - - - - - ReasonName of passenger information action. - - - - - - - - - Further recommendation to passengers. (Unbounded since SIRI 2.0) - - - - - - - - - Further remark to passengers, e,g, "For more information call xy". - - - - - - - - - Summary of passenger information action. - - - - - - - - - Summary of passenger information action. - - - - - - - - - Class of size, e.g. L (large), M (medium), S (small) - - - - - Content for summary of a passenger information action - - - - - Content for n reasons of a passenger information action - - - - - Content for n descriptions of a passenger information action - - - - - Content for n consequences of a passenger information action - - - - - Content for n advices of a passenger information action - - - - - Content to inform about a passenger information action. - - - - - Content for n remarks of a passenger information action, e,g, "For more information call xy". - - - - - for internal information only, not passenger relevant - - - - - Any images associated with SITUATION. - - - - - Hyperlinks to other resources associated with SITUATION. - - - - - - - Values for perspectives. - - - - - - - + + + + + + + + + main schema + e-service developers + Add names + Europe + >Drafted for version 1.0 Kizoom SITUATION Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk + + 2006-09-29 + + + 2007-04-17 + + + 2013-10-01 + (a) Added PublishToDisplayAction element definition (b) Corrected default values for string fields + + + 2013-05-01 + [de] Add SocialNetworks to PublishToWeb action + + + 2018-11-13 + [vdv] ActionsStructure.ActionsGroup.PublishToTvAction changed to unbounded [vdv] ActionsStructure.ActionsGroup.NotifyBySmsAction changed to unbounded [vdv] PublishToDisplayAction added to ActionsGroup [vdv] ActionsStructure.ActionsGroup.PublishToTvAction.Ceefax and Teletext: annotation switched + + + 2020-07-14 + [vdv] New elements added to the ParameterisedActionStructure + + +

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

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/schema/2.0/xsd/siri_model}/siri_situationActions-v1.0.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types-v2.0.xsd + + Unclassified + + Kizoom 2000-2007, CEN 2009-2014 + + +
    +
  • Schema derived Derived from the Kizoom XTIS schema
    • +
+ + Version 2.0 Draft + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, Ports and maritime transport, Ferries (marine), Public transport, Bus services, Coach services, Bus stops and stations, Rail transport, Railway stations and track, Train services, Underground trains, Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI-SX XML Schema for PT SITUATIONs. Actions subschema + Standard + + + SIRI-SX Situation Actions. + + + + + + Type for list of actions. + + + + + + Extension point. + + + + + + + + Type for list of SITUATIONs. + + + + + Processing Status of action at time of SITUATION publication. + + + + + + + + + + + Reference to the action number within the incident concept. + + + + + The time of the last update + + + + + The monotonically increasing version of the passenger information instance. If absent, is the same version as the enclosing Situation + + + + + The system which created this passenger information. If absent, is the same version as the enclosing Situation + + + + + The organisation which owns this passenger information. + + + + + Perspective of the passenger, e.g. general, vehicleJourney, stopPoint. + + + + + Prioritises a passenger information action from the information owner's point of view, e.g. suitable for sorting or hiding individual passenger information actions. 1 = highest priority. + + + + + All texts of the passenger information. + + + + + + + + + Defines the information area where the action has to be published. + + + + + + + + + Type for description of the whole action to be published. + + + + + + Description of the whole passenger information of one action. + + + + + + + Type for parameterised, i.e. user definable, actions. + + + + + + + Description of action. + + + + + + Data associated with action. + + + + + Type for description of the whole action to be published. + + + + + + Defines a number of validity periods. When not sent, then the validity periods of higher level are valid. Can be overwritten by deeper level. + + + + + + + + + Type for publication action. + + + + + + + Whether reminders should be sent. + + + + + + Intervals before validity start date to send reminders. + + + + + + + + Whether a clearing notice should be displayed. + + + + + + + + + Values for Progress Status. + + + + + + + + + + Type for list of SITUATIONs. + + + + + Name of action data Element. + + + + + Data type of action data. + + + + + Value for action. + + + + + Display prompt for presenting action to user. (Unbounded since SIRI 2.0) + + + + + Defines the information area where the action has to be published. + + + + + + + + Allowed actions to perform to distribute SITUATION. + + + + + + + + + + + + + + + + + Action: Publish SITUATION To Web. + + + + + Type for Action Publish SITUATION To Web. + + + + + + + Include in SITUATION lists on web site. Default is 'true'. + + + + + Include on home page on web site. Default is 'false'. + + + + + Include in moving ticker band. Default is 'false'. + + + + + Include in social NETWORK indicated by this name. Possible value could be "twitter.com", "facebook.com", "vk.com" and so on. Parameters may be specifed as Action data. (SIRIv 2.10) + + + + + + + + + Action: Publish SITUATION To WAP and PDA. + + + + + Type for Action Publish SITUATION To Displays. + + + + + + + Include in SITUATION lists on mobile site. Default is 'true'. + + + + + Include in home page on mobile site. Default is 'false'. + + + + + + + + + Action: Publish SITUATION To Displays. + + + + + Type for Action Publish SITUATION To Web. + + + + + + + Include in SITUATION lists on station displays. + + + + + Include onboard displays. + + + + + + + + + Action: Publish SITUATION To Alert Service. + + + + + Type for Action Publish SITUATION To Alert Service. + + + + + + + Send as email alert. + + + + + Send as mobile alert by SMS or WAP push. + + + + + + + + + Action: Publish SITUATION To TvService. + + + + + Type for Notify SITUATION to Tv. + + + + + + + Publish to Ceefax. Default is 'true'. + + + + + Publish to Teletext. Default is 'true'. + + + + + + + + + + Action: Publish SITUATION Manually. i.e. a procedure must be carried out. + + + + + + + + + + Type for Action Publish SITUATION Manual process. + + + + + + + + Action: Publish SITUATION to an individual by SMS. + + + + + Type for Notify user by SMS. + + + + + + + MSISDN of user to which to send messages. + + + + + Whether content is flagged as subject to premium charge. + + + + + + + + + Action: Publish SITUATION to a named workgroup or individual by email. + + + + + Type for Notify user by Email. + + + + + + + Email address to which notice should be sent. + + + + + + + + + Action: Publish SITUATION To pager. + + + + + Type for Notify user by Pager. + + + + + + + Reference to a pager group to be notfied. + + + + + Pager number of pager to be notfied. + + + + + + + + + Action: Publish SITUATION To User. + + + + + Type for Notify user by other means. + + + + + + + Workgroup of user to be notified. + + + + + Name of user to be notified. + + + + + Reference to a user to be notified. + + + + + + + + + + + + Description of SITUATION. Should not repeat any strap line included in Summary. (Unbounded since SIRI 2.0) + + + + + + + + + Further consequence to passengers. (Unbounded since SIRI 2.0) + + + + + + + + + Further information about the duration to passengers. + + + + + + + + + ReasonName of passenger information action. + + + + + + + + + Further recommendation to passengers. (Unbounded since SIRI 2.0) + + + + + + + + + Further remark to passengers, e,g, "For more information call xy". + + + + + + + + + Summary of passenger information action. + + + + + + + + + Summary of passenger information action. + + + + + + + + + Class of size, e.g. L (large), M (medium), S (small) + + + + + Content for summary of a passenger information action + + + + + Content for the reason of a passenger information action + + + + + Content for the description of a passenger information action + + + + + Content for the consequence of a passenger information action + + + + + Content for the advice of a passenger information action + + + + + Content for the duration of a passenger information action. + + + + + Content for the remark of a passenger information action, e,g, "For more information call xy". + + + + + for internal information only, not passenger relevant + + + + + Any images associated with SITUATION. + + + + + Hyperlinks to other resources associated with SITUATION. + + + + + + + Values for perspectives. + + + + + + + From 4e989d0c13a1b0f2ad3d1b3026fb107dbd000b3b Mon Sep 17 00:00:00 2001 From: Korbinian Grimme Date: Fri, 31 Jul 2020 17:05:01 +0200 Subject: [PATCH 170/290] undo last commit and make documentation instead match the XSD --- xsd/siri_model/siri_situationAffects-v2.0.xsd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xsd/siri_model/siri_situationAffects-v2.0.xsd b/xsd/siri_model/siri_situationAffects-v2.0.xsd index 5d445c09..8eca886d 100644 --- a/xsd/siri_model/siri_situationAffects-v2.0.xsd +++ b/xsd/siri_model/siri_situationAffects-v2.0.xsd @@ -962,7 +962,7 @@ Rail transport, Roads and road transport - + From 9de63621b6e156d1c15f934f4dac781ed317c0e2 Mon Sep 17 00:00:00 2001 From: Travis CI User Date: Mon, 3 Aug 2020 13:07:54 +0000 Subject: [PATCH 171/290] Travis CI update [skip ci] --- xsd/siri_model/siri_journey-v2.0.xsd | 18 +- xsd/siri_model/siri_journey_support-v2.0.xsd | 992 ------------------ .../siri_monitoredVehicleJourney-v2.0.xsd | 44 +- xsd/siri_model/siri_situation-v2.0.xsd | 6 +- 4 files changed, 34 insertions(+), 1026 deletions(-) diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index e8400aa8..b55c7cc3 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -554,8 +554,8 @@ Examples: - "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle departing in the direction of this reference point. If the departing vehicle is represented as an arrow, "towards 0" would be abstracted as "<= 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). It is advised to specify a reference point that is meaningful for passengers on location. - - + + Real-time occupancies of a VEHICLE and reservations after departing from a given stop. +SIRI v2.1 @@ -1198,7 +1198,7 @@ If a QUAY is divided into sub-QUAYs or sectors (with the help of STOP ASSIGNMENT Status of formation, e.g., whether it has changed compared to the plan, certain VEHICLEs or features are missing or extra VEHICLEs are added. - + Status of a VEHICLE within formation, e.g., whether a VEHICLE is open, booked or has defective doors. @@ -1532,7 +1532,7 @@ More accurate data can be provided by the individual occupancies or capacities b - + A vehicle composed of TRAIN ELEMENTs assembled in a certain order (so called TRAIN COMPONENTs), i.e. wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 @@ -1664,9 +1664,9 @@ TRAINs within a COMPOUND TRAIN may have different origins and destinations due t Specifies whether a passage from/to an adjacent TRAIN is possible for passengers. - + - + @@ -1708,10 +1708,10 @@ TRAINs within a COMPOUND TRAIN may have different origins and destinations due t Facilities of VEHICLE TYPE. - + - + @@ -1751,7 +1751,7 @@ TRAINs within a COMPOUND TRAIN may have different origins and destinations due t - + diff --git a/xsd/siri_model/siri_journey_support-v2.0.xsd b/xsd/siri_model/siri_journey_support-v2.0.xsd index 789a4115..e69de29b 100644 --- a/xsd/siri_model/siri_journey_support-v2.0.xsd +++ b/xsd/siri_model/siri_journey_support-v2.0.xsd @@ -1,992 +0,0 @@ - - - - - - main schema - e-service developers - Cen TC278 WG3 SG7 Team - Europe - Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2004-03-05 - - - 2004-10-06 - - - 2005-05-11 - - - 2005-11-15 - - - 2007-03-29 - - 2008-11-13 - Correct Cardinalities on SIRI DESTINATION REF Structure - - 2011-04-18 - siri_journey-v2.0.xsd (l.1015). FramedVehicleJourneyRef isn't mandatory in MonitoredCall SIRI-SM answer accourding to CEN TS (prCEN/TS 15531-3:2006 (E) p.56). Make optional. RV ixxx.com - - - 2012-03-22 - SIRI 2.0 - Create from siri_journey - Add TrainNumber - Add departed, missed states to ProgressStatusEnum (arrivalStatus and DepartureStatus) - Add VehicleStatusEnum - - 2013-02-11 - SIRI 2.0 - Add notExpected state to ProgressStatusEnum - Corrected enumeration value cancellled in VehicleStatusEnum - - -

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

-

This subschema defines identifer definitions for common journey elements.

- - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_journey_support.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_types-v2.0.xsd - - Unclassified - - CEN, VDV, RTIG 2004-2012 - - -
    -
  • Derived from the VDV, RTIG CML and Trident standards.
    • -
- - Version 2.0 Draft - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of identifers common journey elements - Standard - - - SIRI Journey Model Identifiers. - - - - - - - Elements identifying VEHICLE JOURNEY. - - - - - Reference to a LINE. - - - - - Reference to a DIRECTION, typically outward or return. - - - - - A reference to the dated VEHICLE JOURNEY that the VEHICLE is making. - - - - - - - Elements identifying a VEHICLE JOURNEY. LINE and DIRECTION will be same as for journey unless overridden. - - - - - Reference to LINE of journey. - - - - - Reference to DIRECTION of journey. - - - - - A reference to the DATED VEHICLE JOURNEY that the VEHICLE is making, unique with the data horizon of the service. - - - - - - - - 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. - - - - - - - Type for a reference to a connecting journey. - - - - - A reference to the DATE VEHICLE JOURNEY that the VEHICLE is making, unique with the data horizon of the service. - - - - - Optionally identify the VEHICLE JOURNEY indirectly by origin and destination and the scheduled times at these stops. - - - - - Reference to LINE. - - - - - TRAIN NUMBER Reference. - - - - - OPERATOR Reference. - - - - - - - - - Type for identifer of a SERVCIE JOURNEY INTERCHANGE. - - - - - - Type for reference to a SERVCIE JOURNEY INTERCHANGE. - - - - - - - - Reference to a SERVCIE JOURNEY INTERCHANGE. - - - - - - Type for identifer of a VEHICLE JOURNEY within data Horizon of a service. - - - - - identifier of data frame within particpant service. Used to ensure that the Reference to a DATED VEGICLE JOURNEY 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 identifier of a data VERSION FRAME. - - - - - - Type for identifier of a data VERSION FRAME. - - - - - - - - - Type for identifier of Train Part. - - - - - - Type for reference to a Train Part. - - - - - - - - - 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). - - - - - - - - - Type for identifier of an JOURNEY PART - - - - - - Type for reference to a JOURNEY PART - - - - - - - - Type for identifier of an TRAIN NUMBER - - - - - - Type for reference to a TRAIN NUMBER - - - - - - - - Type for identifier of a TRAIN ELEMENT. An elementary component of a TRAIN (e.g. wagon, locomotive etc.). +SIRI v2.1 - - - - - - Type for reference to a TRAIN ELEMENT. +SIRI v2.1 - - - - - - - - Reference to a TRAIN ELEMENT. +SIRI v2.1 - - - - - Type for identifier of a TRAIN COMPONENT. A TRAIN ELEMENT with a specific order within a TRAIN. +SIRI v2.1 - - - - - - Type for reference to a TRAIN COMPONENT. +SIRI v2.1 - - - - - - - - Reference to a TRAIN COMPONENT. +SIRI v2.1 - - - - - Type for identifier of a TRAIN. An ordered sequence of TRAIN ELEMENTs or TRAIN COMPONENTs respectively. +SIRI v2.1 - - - - - - Type for reference to a TRAIN. +SIRI v2.1 - - - - - - - - Reference to a TRAIN. +SIRI v2.1 - - - - - Type for identifier of a COMPOUND TRAIN. An ordered sequence of TRAINs or TRAIN IN COMPOUND TRAINs respectively. +SIRI v2.1 - - - - - - Type for reference to a COMPOUND TRAIN. +SIRI v2.1 - - - - - - - - Reference to a COMPOUND TRAIN. +SIRI v2.1 - - - - - Type for identifier of a TRAIN IN COMPOUND TRAIN. A TRAIN with a specific order within a COMPOUND TRAIN. +SIRI v2.1 - - - - - - Type for reference to a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 - - - - - - - - Reference to a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 - - - - - Type for identifier of an ENTRANCE TO VEHICLE, e.g. a door of a TRAIN ELEMENT. +SIRI v2.1 - - - - - - Type for reference to an ENTRANCE TO VEHICLE. +SIRI v2.1 - - - - - - - - Reference to an ENTRANCE TO VEHICLE. +SIRI v2.1 - - - - - - Groups together the relevant references needed in a formation. +SIRI v2.1 -Has the following uses: -- Either the smallest part of a formation, a TRAIN COMPONENT, is referenced or the TRAIN itself. The former is ideally used in a FORMATION ASSIGNMENT, i.e. QUAY (sector) assignment, to provide the highest level of detail for passenger orientation. -- If the formation consists of multiple coupled TRAINs, a reference to the COMPOUND TRAIN is also possible. This might be used in a FORMATION CONDITION to signal a change of the train composition. -- In case alighting/boarding data from an automatic passenger counting system is available, the respective vehicle entrances may be referenced. - - - - - - - - - - - - - Allowed types activity for Boarding and Alighting. - - - - - - - - - - - Allowed types activity for Alighting. - - - - - - - - - - Allowed types activity for Boarding. - - - - - - - - - - - - Reference to the origin SCHEDULED STOP POINT of the journey. - - - - - Reference to a SCHEDULED STOP POINT that is a VIA point on the journey. - - - - - Reference to the destination SCHEDULED STOP POINT of the journey. - - - - - Type for reference to a DESTINATION. - - - - - - - - - Information that classifies journey. - - - - - OPERATOR of a VEHICLE JOURNEY. Note that the operator may change over the course of a journey. This shoudl show teh operator for the curent point in the journey. Use Journey Parts tp record all the operators in the whole journeyh. - - - - - Product Classification of VEHICLE 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. -Corresponds to NeTEX TYPE OF SERVICe. - - - - - - - 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. - - - - - - - - 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 still 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 cancelled. - - - - - Service has arrived. - - - - - - - There is no information about the service. - - - - - Service is not expected to call this stop. For instance a flexible service that has not yet been preordered. - - - - - - - Classification of the State of the VEHICLE JORUNEY according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are still classified as on-time. Applications may use this to guide their own presentation of times. - - - - - Service is expected to be performed. - - - - - Service is not expected to be run. For instance a flexible service that has not yet been preordered. - - - - - - - - - Service has departed from first stop. - - - - - - - It has been detected that the Service was completed. - - - - - It is assumed that the Service has completed. - - - - - - - - Classification of the quality of the prediction 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). - - - - - - - Allowed types activity for FirstOrLastJourney. - - - - - - - - - - - - Allowed values for PredictionInaccurateReason, i.e., possible reasons for a change in prediction (in)accuracy. - - - - - Prediction is inaccurate because of a traffic jam. - - - - - Prediction is inaccurate because of technical problems. - - - - - Prediction is inaccurate because of a despatching alteration. - - - - - Prediction is inaccurate because communication errors have prevented any updates. - - - - - Prediction is inaccurate but the reason for an inaccurate prediction is unknown. - - - - - - - - Allowed values for QuayType which is used to characterise the STOP ASSIGNMENTs. +SIRI v2.1 - - - - - A type of QUAY that consists of multiple QUAYs of type 'platform'. Examples of such groups would be the lower and upper level of a station. - - - - - A type of QUAY that consists of at least two child QUAYs of type 'platformEdge'. - - - - - A type of QUAY which allows direct access to a VEHICLE, e.g. an on-street bus stop, or consists of multiple child QUAYs of type 'platformSector'. - - - - - A QUAY of type 'platformEdge' may be divided into multiple sectors, e.g. "A", "B", "C" etc., to help passengers find a specific part of a vehicle. -The first class carriage of a TRAIN might, for example, be assigned to sector "A" of a QUAY. - - - - - A location within a QUAY from which passengers may directly board, or onto which passengers may directly alight from a VEHICLE. - - - - - - - - Allowed types of relation between JOURNEYs. - - - - - The journey is a continuation of the specified RelatedJourney at the stop point given in CallInfo. -Passengers don't need to change vehicles. The new journey is not communicated as an interchange. - - - - - The journey is continued by the specified RelatedJourney at the stop point given in CallInfo. -Passengers don't need to change vehicles. The new journey is not communicated as an interchange. - - - - - The journey splits into multiple RelatedJourneys at the stop point given in CallInfo. - - - - - The journey is a continuation of a single RelatedJourney splitting into multiple journeys at the stop point given in CallInfo. - - - - - The journey is the continuation of multiple RelatedJourneys joining together at the stop point given in CallInfo. - - - - - The journey is continued by a single RelatedJourney after joining other journeys at the stop point given in CallInfo. - - - - - The journey replaces one or more partially or fully cancelled RelatedJourneys during the JourneyPart defined or referenced in JourneyPartInfo. - - - - - The partially or fully cancelled journey is replaced by one or more RelatedJourneys during the JourneyPart defined or referenced in JourneyPartInfo. - - - - - The journey partially or fully supports one or more RelatedJourneys during the JourneyPart defined or referenced in JourneyPartInfo. - - - - - The journey is partially or fully supported by one or more RelatedJourneys during the JourneyPart defined or referenced in JourneyPartInfo. - - - - - - - - Allowed values for TYPE OF TRAIN ELEMENT. +SIRI v2.1 - - - - - - - - - - - - - - - Allowed values for TRAIN SIZE. +SIRI v2.1 - - - - - - - - - - Allowed values for TYPE OF FUEL. +SIRI v2.1 - - - - - - - - - - - - - - Classification of FARE CLASSes. +SIRI v2.1 - - - - - List of FARE CLASSes. +SIRI v2.1 - - - - - List of values for FARE CLASSes. +SIRI v2.1 - - - - - - Values for Fare Class Facility. +SIRI v2.1 - - - - - pti23_0 - - - - - pti23_6 - - - - - pti23_7 - - - - - pti23_8 - - - - - - pti23_6_1 - - - - - Business Class - pti23_10 - - - - - Standard class Add pti23_7 - - - - - - pti23_9 - - - - - - - - Allowed values for VEHICLE IN FORMATION STATUS CODE. +SIRI v2.1 - - - - - - - - - - - - - - - - - - Allowed values for FORMATION CHANGE CODE. +SIRI v2.1 - - - - - - - - - - - - - - - - - diff --git a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd index 6a0a8d6c..cba57977 100644 --- a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd @@ -337,7 +337,7 @@ A journey does always have one or more JOURNEY PARTs for which the train formati - + Type for a reference to JOURNEY PART. +SIRI v2.1 @@ -369,29 +369,29 @@ A journey does always have one or more JOURNEY PARTs for which the train formati - If no JOURNEY PART reference is available (or in addition to the reference), identify it indirectly by From-/ToStopPointRef and Start-/EndTime (i.e. the scheduled times at these stops). +SIRI v2.1 + If no JOURNEY PART reference is available (or in addition to the reference), identify it indirectly by From-/ToStopPointRef and Start-/EndTime (i.e. the scheduled times at these stops). +SIRI v2.1 - - - Reference to the SCHEDULED STOP POINT at which the related JOURNEY PART begins. - - - - - Reference to the SCHEDULED STOP POINT at which the related JOURNEY PART ends. - - - - - Time at which the related JOURNEY PART begins. - - - - - Time at which the related JOURNEY PART ends. - - + + + Reference to the SCHEDULED STOP POINT at which the related JOURNEY PART begins. + + + + + Reference to the SCHEDULED STOP POINT at which the related JOURNEY PART ends. + + + + + Time at which the related JOURNEY PART begins. + + + + + Time at which the related JOURNEY PART ends. + + diff --git a/xsd/siri_model/siri_situation-v2.0.xsd b/xsd/siri_model/siri_situation-v2.0.xsd index 6ffabebd..68c2698c 100644 --- a/xsd/siri_model/siri_situation-v2.0.xsd +++ b/xsd/siri_model/siri_situation-v2.0.xsd @@ -33,7 +33,7 @@ 2008-07-05 - @@ -41,7 +41,7 @@ 2011-04-18 - + 2012-03-23 - +

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

From 5a983350eadd1325fd77690790af47881a3d2f91 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Mon, 3 Aug 2020 15:40:28 +0200 Subject: [PATCH 172/290] restore xsd after travis rm and fix incorrect tag --- xsd/siri_model/siri_journey_support-v2.0.xsd | 977 +++++++++++++++++++ 1 file changed, 977 insertions(+) diff --git a/xsd/siri_model/siri_journey_support-v2.0.xsd b/xsd/siri_model/siri_journey_support-v2.0.xsd index e69de29b..fa024bfc 100644 --- a/xsd/siri_model/siri_journey_support-v2.0.xsd +++ b/xsd/siri_model/siri_journey_support-v2.0.xsd @@ -0,0 +1,977 @@ + + + + + + main schema + e-service developers + Cen TC278 WG3 SG7 Team + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2004-03-05 + + + 2004-10-06 + + + 2005-05-11 + + + 2005-11-15 + + + 2007-03-29 + + 2008-11-13 + Correct Cardinalities on SIRI DESTINATION REF Structure + + 2011-04-18 + siri_journey-v2.0.xsd (l.1015). FramedVehicleJourneyRef isn't mandatory in MonitoredCall SIRI-SM answer accourding to CEN TS (prCEN/TS 15531-3:2006 (E) p.56). Make optional. RV ixxx.com + + + 2012-03-22 + SIRI 2.0 + Create from siri_journey + Add TrainNumber + Add departed, missed states to ProgressStatusEnum (arrivalStatus and DepartureStatus) + Add VehicleStatusEnum + + 2013-02-11 + SIRI 2.0 + Add notExpected state to ProgressStatusEnum + Corrected enumeration value cancellled in VehicleStatusEnum + + +

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

+

This subschema defines identifer definitions for common journey elements.

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_journey_support.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_types-v2.0.xsd + + Unclassified + + CEN, VDV, RTIG 2004-2012 + + +
    +
  • Derived from the VDV, RTIG CML and Trident standards.
    • +
+ + Version 2.0 Draft + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of identifers common journey elements + Standard + + + SIRI Journey Model Identifiers. + + + + + + + Elements identifying VEHICLE JOURNEY. + + + + + Reference to a LINE. + + + + + Reference to a DIRECTION, typically outward or return. + + + + + A reference to the dated VEHICLE JOURNEY that the VEHICLE is making. + + + + + + + Elements identifying a VEHICLE JOURNEY. LINE and DIRECTION will be same as for journey unless overridden. + + + + + Reference to LINE of journey. + + + + + Reference to DIRECTION of journey. + + + + + A reference to the DATED VEHICLE JOURNEY that the VEHICLE is making, unique with the data horizon of the service. + + + + + + + + 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. + + + + + + + Type for a reference to a connecting journey. + + + + + A reference to the DATE VEHICLE JOURNEY that the VEHICLE is making, unique with the data horizon of the service. + + + + + LINE Reference. + + + + + + + + + Type for identifer of a SERVCIE JOURNEY INTERCHANGE. + + + + + + Type for reference to a SERVCIE JOURNEY INTERCHANGE. + + + + + + + + Reference to a SERVCIE JOURNEY INTERCHANGE. + + + + + + Type for identifer of a VEHICLE JOURNEY within data Horizon of a service. + + + + + identifier of data frame within particpant service. Used to ensure that the Reference to a DATED VEGICLE JOURNEY 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 identifier of a data VERSION FRAME. + + + + + + Type for identifier of a data VERSION FRAME. + + + + + + + + + Type for identifier of Train Part. + + + + + + Type for reference to a Train Part. + + + + + + + + + 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). + + + + + + + + + Type for identifier of an JOURNEY PART + + + + + + Type for reference to a JOURNEY PART + + + + + + + + Type for identifier of an TRAIN NUMBER + + + + + + Type for reference to a TRAIN NUMBER + + + + + + + + Type for identifier of a TRAIN ELEMENT. An elementary component of a TRAIN (e.g. wagon, locomotive etc.). +SIRI v2.1 + + + + + + Type for reference to a TRAIN ELEMENT. +SIRI v2.1 + + + + + + + + Reference to a TRAIN ELEMENT. +SIRI v2.1 + + + + + Type for identifier of a TRAIN COMPONENT. A TRAIN ELEMENT with a specific order within a TRAIN. +SIRI v2.1 + + + + + + Type for reference to a TRAIN COMPONENT. +SIRI v2.1 + + + + + + + + Reference to a TRAIN COMPONENT. +SIRI v2.1 + + + + + Type for identifier of a TRAIN. An ordered sequence of TRAIN ELEMENTs or TRAIN COMPONENTs respectively. +SIRI v2.1 + + + + + + Type for reference to a TRAIN. +SIRI v2.1 + + + + + + + + Reference to a TRAIN. +SIRI v2.1 + + + + + Type for identifier of a COMPOUND TRAIN. An ordered sequence of TRAINs or TRAIN IN COMPOUND TRAINs respectively. +SIRI v2.1 + + + + + + Type for reference to a COMPOUND TRAIN. +SIRI v2.1 + + + + + + + + Reference to a COMPOUND TRAIN. +SIRI v2.1 + + + + + Type for identifier of a TRAIN IN COMPOUND TRAIN. A TRAIN with a specific order within a COMPOUND TRAIN. +SIRI v2.1 + + + + + + Type for reference to a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 + + + + + + + + Reference to a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 + + + + + Type for identifier of an ENTRANCE TO VEHICLE, e.g. a door of a TRAIN ELEMENT. +SIRI v2.1 + + + + + + Type for reference to an ENTRANCE TO VEHICLE. +SIRI v2.1 + + + + + + + + Reference to an ENTRANCE TO VEHICLE. +SIRI v2.1 + + + + + + Groups together the relevant references needed in a formation. +SIRI v2.1 +Has the following uses: +- Either the smallest part of a formation, a TRAIN COMPONENT, is referenced or the TRAIN itself. The former is ideally used in a FORMATION ASSIGNMENT, i.e. QUAY (sector) assignment, to provide the highest level of detail for passenger orientation. +- If the formation consists of multiple coupled TRAINs, a reference to the COMPOUND TRAIN is also possible. This might be used in a FORMATION CONDITION to signal a change of the train composition. +- In case alighting/boarding data from an automatic passenger counting system is available, the respective vehicle entrances may be referenced. + + + + + + + + + + + + + Allowed types activity for Boarding and Alighting. + + + + + + + + + + + Allowed types activity for Alighting. + + + + + + + + + + Allowed types activity for Boarding. + + + + + + + + + + + + Reference to the origin SCHEDULED STOP POINT of the journey. + + + + + Reference to a SCHEDULED STOP POINT that is a VIA point on the journey. + + + + + Reference to the destination SCHEDULED STOP POINT of the journey. + + + + + Type for reference to a DESTINATION. + + + + + + + + + Information that classifies journey. + + + + + OPERATOR of a VEHICLE JOURNEY. Note that the operator may change over the course of a journey. This shoudl show teh operator for the curent point in the journey. Use Journey Parts tp record all the operators in the whole journeyh. + + + + + Product Classification of VEHICLE 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. +Corresponds to NeTEX TYPE OF SERVICe. + + + + + + + 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. + + + + + + + + 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 still 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 cancelled. + + + + + Service has arrived. + + + + + + + There is no information about the service. + + + + + Service is not expected to call this stop. For instance a flexible service that has not yet been preordered. + + + + + + + Classification of the State of the VEHICLE JORUNEY according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are still classified as on-time. Applications may use this to guide their own presentation of times. + + + + + Service is expected to be performed. + + + + + Service is not expected to be run. For instance a flexible service that has not yet been preordered. + + + + + + + + + Service has departed from first stop. + + + + + + + It has been detected that the Service was completed. + + + + + It is assumed that the Service has completed. + + + + + + + + Classification of the quality of the prediction 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). + + + + + + + Allowed types activity for FirstOrLastJourney. + + + + + + + + + + + + Allowed values for PredictionInaccurateReason, i.e., possible reasons for a change in prediction (in)accuracy. + + + + + Prediction is inaccurate because of a traffic jam. + + + + + Prediction is inaccurate because of technical problems. + + + + + Prediction is inaccurate because of a despatching alteration. + + + + + Prediction is inaccurate because communication errors have prevented any updates. + + + + + Prediction is inaccurate but the reason for an inaccurate prediction is unknown. + + + + + + + + Allowed types of relation between JOURNEYs. + + + + + The journey is a continuation of the specified RelatedJourney at the stop point given in CallInfo. +Passengers don't need to change vehicles. The new journey is not communicated as an interchange. + + + + + The journey is continued by the specified RelatedJourney at the stop point given in CallInfo. +Passengers don't need to change vehicles. The new journey is not communicated as an interchange. + + + + + The journey splits into multiple RelatedJourneys at the stop point given in CallInfo. + + + + + The journey is a continuation of a single RelatedJourney splitting into multiple journeys at the stop point given in CallInfo. + + + + + The journey is the continuation of multiple RelatedJourneys joining together at the stop point given in CallInfo. + + + + + The journey is continued by a single RelatedJourney after joining other journeys at the stop point given in CallInfo. + + + + + The journey replaces one or more partially or fully cancelled RelatedJourneys during the JourneyPart defined or referenced in JourneyPartInfo. + + + + + The partially or fully cancelled journey is replaced by one or more RelatedJourneys during the JourneyPart defined or referenced in JourneyPartInfo. + + + + + The journey partially or fully supports one or more RelatedJourneys during the JourneyPart defined or referenced in JourneyPartInfo. + + + + + The journey is partially or fully supported by one or more RelatedJourneys during the JourneyPart defined or referenced in JourneyPartInfo. + + + + + + + + Allowed values for QuayType which is used to characterise the STOP ASSIGNMENTs. +SIRI v2.1 + + + + + A type of QUAY that consists of multiple QUAYs of type 'platform'. Examples of such groups would be the lower and upper level of a station. + + + + + A type of QUAY that consists of at least two child QUAYs of type 'platformEdge'. + + + + + A type of QUAY which allows direct access to a VEHICLE, e.g. an on-street bus stop, or consists of multiple child QUAYs of type 'platformSector'. + + + + + A QUAY of type 'platformEdge' may be divided into multiple sectors, e.g. "A", "B", "C" etc., to help passengers find a specific part of a vehicle. +The first class carriage of a TRAIN might, for example, be assigned to sector "A" of a QUAY. + + + + + A location within a QUAY from which passengers may directly board, or onto which passengers may directly alight from a VEHICLE. + + + + + + + + Allowed values for TYPE OF TRAIN ELEMENT. +SIRI v2.1 + + + + + + + + + + + + + + + Allowed values for TRAIN SIZE. +SIRI v2.1 + + + + + + + + + + Allowed values for TYPE OF FUEL. +SIRI v2.1 + + + + + + + + + + + + + + Classification of FARE CLASSes. +SIRI v2.1 + + + + + List of FARE CLASSes. +SIRI v2.1 + + + + + List of values for FARE CLASSes. +SIRI v2.1 + + + + + + Values for Fare Class Facility. +SIRI v2.1 + + + + + pti23_0 + + + + + pti23_6 + + + + + pti23_7 + + + + + pti23_8 + + + + + + pti23_6_1 + + + + + Business Class - pti23_10 + + + + + Standard class Add pti23_7 + + + + + + pti23_9 + + + + + + + + Allowed values for VEHICLE IN FORMATION STATUS CODE. +SIRI v2.1 + + + + + + + + + + + + + + + + + + Allowed values for FORMATION CHANGE CODE. +SIRI v2.1 + + + + + + + + + + + + + + + + + From 0b0da174e90e4207923d8a59ce40d142f9ee4da2 Mon Sep 17 00:00:00 2001 From: Travis CI User Date: Mon, 3 Aug 2020 13:44:44 +0000 Subject: [PATCH 173/290] Travis CI update [skip ci] --- xsd/siri_model/siri_journey_support-v2.0.xsd | 188 +++++++++---------- 1 file changed, 94 insertions(+), 94 deletions(-) diff --git a/xsd/siri_model/siri_journey_support-v2.0.xsd b/xsd/siri_model/siri_journey_support-v2.0.xsd index fa024bfc..c1a530e8 100644 --- a/xsd/siri_model/siri_journey_support-v2.0.xsd +++ b/xsd/siri_model/siri_journey_support-v2.0.xsd @@ -336,7 +336,7 @@ Rail transport, Roads and road transport - Reference to a TRAIN ELEMENT. +SIRI v2.1 + Reference to a TRAIN ELEMENT. +SIRI v2.1 @@ -355,7 +355,7 @@ Rail transport, Roads and road transport - Reference to a TRAIN COMPONENT. +SIRI v2.1 + Reference to a TRAIN COMPONENT. +SIRI v2.1 @@ -374,7 +374,7 @@ Rail transport, Roads and road transport - Reference to a TRAIN. +SIRI v2.1 + Reference to a TRAIN. +SIRI v2.1 @@ -393,7 +393,7 @@ Rail transport, Roads and road transport - Reference to a COMPOUND TRAIN. +SIRI v2.1 + Reference to a COMPOUND TRAIN. +SIRI v2.1 @@ -412,7 +412,7 @@ Rail transport, Roads and road transport - Reference to a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 + Reference to a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 @@ -431,7 +431,7 @@ Rail transport, Roads and road transport - Reference to an ENTRANCE TO VEHICLE. +SIRI v2.1 + Reference to an ENTRANCE TO VEHICLE. +SIRI v2.1 @@ -848,95 +848,95 @@ The first class carriage of a TRAIN might, for example, be assigned to sector "A - - Allowed values for TRAIN SIZE. +SIRI v2.1 - - - - - - - - - - Allowed values for TYPE OF FUEL. +SIRI v2.1 - - - - - - - - - - - + + Allowed values for TRAIN SIZE. +SIRI v2.1 + + + + + + + + + + Allowed values for TYPE OF FUEL. +SIRI v2.1 + + + + + + + + + + + - - Classification of FARE CLASSes. +SIRI v2.1 - - - - - List of FARE CLASSes. +SIRI v2.1 - - - - - List of values for FARE CLASSes. +SIRI v2.1 - - - - - - Values for Fare Class Facility. +SIRI v2.1 - - - - - pti23_0 - - - - - pti23_6 - - - - - pti23_7 - - - - - pti23_8 - - - - - - pti23_6_1 - - - - - Business Class - pti23_10 - - - - - Standard class Add pti23_7 - - - - - - pti23_9 - - - - - + + Classification of FARE CLASSes. +SIRI v2.1 + + + + + List of FARE CLASSes. +SIRI v2.1 + + + + + List of values for FARE CLASSes. +SIRI v2.1 + + + + + + Values for Fare Class Facility. +SIRI v2.1 + + + + + pti23_0 + + + + + pti23_6 + + + + + pti23_7 + + + + + pti23_8 + + + + + + pti23_6_1 + + + + + Business Class - pti23_10 + + + + + Standard class Add pti23_7 + + + + + + pti23_9 + + + + + Allowed values for VEHICLE IN FORMATION STATUS CODE. +SIRI v2.1 From b315d4a24a2f3c659e7042d71a80cce746dc167f Mon Sep 17 00:00:00 2001 From: Adrian A Date: Mon, 3 Aug 2020 16:01:59 +0200 Subject: [PATCH 174/290] restore ConnectingJourneyRefStr. after travis rm --- xsd/siri_model/siri_journey_support-v2.0.xsd | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/xsd/siri_model/siri_journey_support-v2.0.xsd b/xsd/siri_model/siri_journey_support-v2.0.xsd index c1a530e8..0cc84c96 100644 --- a/xsd/siri_model/siri_journey_support-v2.0.xsd +++ b/xsd/siri_model/siri_journey_support-v2.0.xsd @@ -187,9 +187,24 @@ Rail transport, Roads and road transport A reference to the DATE VEHICLE JOURNEY that the VEHICLE is making, unique with the data horizon of the service. + + + Optionally identify the VEHICLE JOURNEY indirectly by origin and destination and the scheduled times at these stops. + + - LINE Reference. + Reference to LINE. + + + + + TRAIN NUMBER Reference. + + + + + OPERATOR Reference. From 092711417c96f78b93714efaa28af9e05265c917 Mon Sep 17 00:00:00 2001 From: hennoit Date: Thu, 6 Aug 2020 15:01:49 +0200 Subject: [PATCH 175/290] CR55 changes to CR69 --- xsd/siri_model/siri_situationActions-v2.0.xsd | 1388 +++++++++-------- 1 file changed, 702 insertions(+), 686 deletions(-) diff --git a/xsd/siri_model/siri_situationActions-v2.0.xsd b/xsd/siri_model/siri_situationActions-v2.0.xsd index 4cef5a67..1276606c 100644 --- a/xsd/siri_model/siri_situationActions-v2.0.xsd +++ b/xsd/siri_model/siri_situationActions-v2.0.xsd @@ -1,700 +1,716 @@ - - - - - - - - - main schema - e-service developers - Add names - Europe - >Drafted for version 1.0 Kizoom SITUATION Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk - - 2006-09-29 - - - 2007-04-17 - - - 2013-10-01 + + + + + + + + + main schema + e-service developers + Add names + Europe + >Drafted for version 1.0 Kizoom SITUATION Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk + + 2006-09-29 + + + 2007-04-17 + + + 2013-10-01 (a) Added PublishToDisplayAction element definition (b) Corrected default values for string fields - - 2013-05-01 + + 2013-05-01 [de] Add SocialNetworks to PublishToWeb action - - 2018-11-13 + + 2018-11-13 [vdv] ActionsStructure.ActionsGroup.PublishToTvAction changed to unbounded [vdv] ActionsStructure.ActionsGroup.NotifyBySmsAction changed to unbounded [vdv] PublishToDisplayAction added to ActionsGroup [vdv] ActionsStructure.ActionsGroup.PublishToTvAction.Ceefax and Teletext: annotation switched - - 2020-07-14 + + 2020-07-14 [vdv] New elements added to the ParameterisedActionStructure - -

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

- - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/schema/2.0/xsd/siri_model}/siri_situationActions-v1.0.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types-v2.0.xsd - - Unclassified + +

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

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/schema/2.0/xsd/siri_model}/siri_situationActions-v1.0.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types-v2.0.xsd + + Unclassified Kizoom 2000-2007, CEN 2009-2014 - - -
    -
  • Schema derived Derived from the Kizoom XTIS schema
    • -
- - Version 2.0 Draft - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, Ports and maritime transport, Ferries (marine), Public transport, Bus services, Coach services, Bus stops and stations, Rail transport, Railway stations and track, Train services, Underground trains, Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, Rail transport, Roads and road transport + + +
    +
  • Schema derived Derived from the Kizoom XTIS schema
    • +
+ + Version 2.0 Draft + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, Ports and maritime transport, Ferries (marine), Public transport, Bus services, Coach services, Bus stops and stations, Rail transport, Railway stations and track, Train services, Underground trains, Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, Rail transport, Roads and road transport - CEN TC278 WG3 SG7 - - SIRI-SX XML Schema for PT SITUATIONs. Actions subschema - Standard - - - SIRI-SX Situation Actions. - - - - - - Type for list of actions. - - - - - - Extension point. - - - - - - - - Type for list of SITUATIONs. - - - - - Processing Status of action at time of SITUATION publication. - - - - - - - - - - - Reference to the action number within the incident concept. - - - - - The time of the last update - - - - - The monotonically increasing version of the passenger information instance. If absent, is the same version as the enclosing Situation - - - - - The system which created this passenger information. If absent, is the same version as the enclosing Situation - - - - - The organisation which owns this passenger information. - - - - - Perspective of the passenger, e.g. general, vehicleJourney, stopPoint. - - - - - Prioritises a passenger information action from the information owner's point of view, e.g. suitable for sorting or hiding individual passenger information actions. 1 = highest priority. - - - - - All texts of the passenger information. - - - - - - - - - Defines the information area where the action has to be published. - - - - - - - - - Type for description of the whole action to be published. - - - - - - Description of the whole passenger information of one action. - - - - - - - Type for parameterised, i.e. user definable, actions. - - - - - - - Description of action. - - - - - - Data associated with action. - - - - - Type for description of the whole action to be published. - - - - - - Defines a number of validity periods. When not sent, then the validity periods of higher level are valid. Can be overwritten by deeper level. - - - - - - - - - Type for publication action. - - - - - - - Whether reminders should be sent. - - - - - - Intervals before validity start date to send reminders. - - - - - - - - Whether a clearing notice should be displayed. - - - - - - - - - Values for Progress Status. - - - - - - - - - - Type for list of SITUATIONs. - - - - - Name of action data Element. - - - - - Data type of action data. - - - - - Value for action. - - - - - Display prompt for presenting action to user. (Unbounded since SIRI 2.0) - - - - - Defines the information area where the action has to be published. - - - - - - - - Allowed actions to perform to distribute SITUATION. - - - - - - - - - - - - - - - - - Action: Publish SITUATION To Web. - - - - - Type for Action Publish SITUATION To Web. - - - - - - - Include in SITUATION lists on web site. Default is 'true'. - - - - - Include on home page on web site. Default is 'false'. - - - - - Include in moving ticker band. Default is 'false'. - - - - - Include in social NETWORK indicated by this name. Possible value could be "twitter.com", "facebook.com", "vk.com" and so on. Parameters may be specifed as Action data. (SIRIv 2.10) - - - - - - - - - Action: Publish SITUATION To WAP and PDA. - - - - - Type for Action Publish SITUATION To Displays. - - - - - - - Include in SITUATION lists on mobile site. Default is 'true'. - - - - - Include in home page on mobile site. Default is 'false'. - - - - - - - - - Action: Publish SITUATION To Displays. - - - - - Type for Action Publish SITUATION To Web. - - - - - - - Include in SITUATION lists on station displays. - - - - - Include onboard displays. - - - - - - - - - Action: Publish SITUATION To Alert Service. - - - - - Type for Action Publish SITUATION To Alert Service. - - - - - - - Send as email alert. - - - - - Send as mobile alert by SMS or WAP push. - - - - - - - - - Action: Publish SITUATION To TvService. - - - - - Type for Notify SITUATION to Tv. - - - - - - - Publish to Ceefax. Default is 'true'. - - - - - Publish to Teletext. Default is 'true'. - - - - - - - - - - Action: Publish SITUATION Manually. i.e. a procedure must be carried out. - - - - - - - - - - Type for Action Publish SITUATION Manual process. - - - - - - - - Action: Publish SITUATION to an individual by SMS. - - - - - Type for Notify user by SMS. - - - - - - - MSISDN of user to which to send messages. - - - - - Whether content is flagged as subject to premium charge. - - - - - - - - - Action: Publish SITUATION to a named workgroup or individual by email. - - - - - Type for Notify user by Email. - - - - - - - Email address to which notice should be sent. - - - - - - - - - Action: Publish SITUATION To pager. - - - - - Type for Notify user by Pager. - - - - - - - Reference to a pager group to be notfied. - - - - - Pager number of pager to be notfied. - - - - - - - - - Action: Publish SITUATION To User. - - - - - Type for Notify user by other means. - - - - - - - Workgroup of user to be notified. - - - - - Name of user to be notified. - - - - - Reference to a user to be notified. - - - - - - - - - - - - Description of SITUATION. Should not repeat any strap line included in Summary. (Unbounded since SIRI 2.0) - - - - - - - - - Further consequence to passengers. (Unbounded since SIRI 2.0) - - - - - - - - - Further information about the duration to passengers. - - - - - - - - - ReasonName of passenger information action. - - - - - - - - - Further recommendation to passengers. (Unbounded since SIRI 2.0) - - - - - - - - - Further remark to passengers, e,g, "For more information call xy". - - - - - - - - - Summary of passenger information action. - - - - - - - - - Summary of passenger information action. - - - - - - - - - Class of size, e.g. L (large), M (medium), S (small) - - - - - Content for summary of a passenger information action - - - - - Content for the reason of a passenger information action - - - - - Content for the description of a passenger information action - - - - - Content for the consequence of a passenger information action - - - - - Content for the advice of a passenger information action - - - - - Content for the duration of a passenger information action. - - - - - Content for the remark of a passenger information action, e,g, "For more information call xy". - - - - - for internal information only, not passenger relevant - - - - - Any images associated with SITUATION. - - - - - Hyperlinks to other resources associated with SITUATION. - - - - - - - Values for perspectives. - - - - - - - + CEN TC278 WG3 SG7 + + SIRI-SX XML Schema for PT SITUATIONs. Actions subschema + Standard + + + SIRI-SX Situation Actions. + + + + + + Type for list of actions. + + + + + + Extension point. + + + + + + + + Type for list of SITUATIONs. + + + + + Processing Status of action at time of SITUATION publication. + + + + + + + + + + + Reference to the action number within the incident concept. + + + + + The time of the last update + + + + + The monotonically increasing version of the passenger information instance. If absent, is the same version as the enclosing Situation + + + + + The system which created this passenger information. If absent, is the same version as the enclosing Situation + + + + + The organisation which owns this passenger information. + + + + + Perspective of the passenger, e.g. general, vehicleJourney, stopPoint. + + + + + Prioritises a passenger information action from the information owner's point of view, e.g. suitable for sorting or hiding individual passenger information actions. 1 = highest priority. + + + + + All texts of the passenger information. + + + + + + + + Structured Reason elements. The TpegReason and/or PublicEventReason enumerated values can be used to generate standardized messages for the current Perspective. If no enumerated values are given, ReasonName is used instead. +Note: this means that ReasonName is NOT a complete message, but only a (few) word(s) to be included in the message! + + + + + Structured elements describing the effect of disruption and the advice to passengers. The enumerated values can be used to generate standardized messages for the current Perspective. If no enumerated values are given, the xxxxName is used instead. +Note: this means that a xxxxName is NOT a complete message, but only a (few) word(s) to be included in the message! + + + + + + + + + + + Defines the information area where the action has to be published. + + + + + + + + + Type for description of the whole action to be published. + + + + + + Description of the whole passenger information of one action. + + + + + + + Type for parameterised, i.e. user definable, actions. + + + + + + + Description of action. + + + + + + Data associated with action. + + + + + Type for description of the whole action to be published. + + + + + + Defines a number of validity periods. When not sent, then the validity periods of higher level are valid. Can be overwritten by deeper level. + + + + + + + + + Type for publication action. + + + + + + + Whether reminders should be sent. + + + + + + Intervals before validity start date to send reminders. + + + + + + + + Whether a clearing notice should be displayed. + + + + + + + + + Values for Progress Status. + + + + + + + + + + Type for list of SITUATIONs. + + + + + Name of action data Element. + + + + + Data type of action data. + + + + + Value for action. + + + + + Display prompt for presenting action to user. (Unbounded since SIRI 2.0) + + + + + Defines the information area where the action has to be published. + + + + + + + + Allowed actions to perform to distribute SITUATION. + + + + + + + + + + + + + + + + + Action: Publish SITUATION To Web. + + + + + Type for Action Publish SITUATION To Web. + + + + + + + Include in SITUATION lists on web site. Default is 'true'. + + + + + Include on home page on web site. Default is 'false'. + + + + + Include in moving ticker band. Default is 'false'. + + + + + Include in social NETWORK indicated by this name. Possible value could be "twitter.com", "facebook.com", "vk.com" and so on. Parameters may be specifed as Action data. (SIRIv 2.10) + + + + + + + + + Action: Publish SITUATION To WAP and PDA. + + + + + Type for Action Publish SITUATION To Displays. + + + + + + + Include in SITUATION lists on mobile site. Default is 'true'. + + + + + Include in home page on mobile site. Default is 'false'. + + + + + + + + + Action: Publish SITUATION To Displays. + + + + + Type for Action Publish SITUATION To Web. + + + + + + + Include in SITUATION lists on station displays. + + + + + Include onboard displays. + + + + + + + + + Action: Publish SITUATION To Alert Service. + + + + + Type for Action Publish SITUATION To Alert Service. + + + + + + + Send as email alert. + + + + + Send as mobile alert by SMS or WAP push. + + + + + + + + + Action: Publish SITUATION To TvService. + + + + + Type for Notify SITUATION to Tv. + + + + + + + Publish to Ceefax. Default is 'true'. + + + + + Publish to Teletext. Default is 'true'. + + + + + + + + + + Action: Publish SITUATION Manually. i.e. a procedure must be carried out. + + + + + + + + + + Type for Action Publish SITUATION Manual process. + + + + + + + + Action: Publish SITUATION to an individual by SMS. + + + + + Type for Notify user by SMS. + + + + + + + MSISDN of user to which to send messages. + + + + + Whether content is flagged as subject to premium charge. + + + + + + + + + Action: Publish SITUATION to a named workgroup or individual by email. + + + + + Type for Notify user by Email. + + + + + + + Email address to which notice should be sent. + + + + + + + + + Action: Publish SITUATION To pager. + + + + + Type for Notify user by Pager. + + + + + + + Reference to a pager group to be notfied. + + + + + Pager number of pager to be notfied. + + + + + + + + + Action: Publish SITUATION To User. + + + + + Type for Notify user by other means. + + + + + + + Workgroup of user to be notified. + + + + + Name of user to be notified. + + + + + Reference to a user to be notified. + + + + + + + + + + + + Description of SITUATION. Should not repeat any strap line included in Summary. (Unbounded since SIRI 2.0) + + + + + + + + + Further consequence to passengers. (Unbounded since SIRI 2.0) + + + + + + + + + Further information about the duration to passengers. + + + + + + + + + ReasonName of passenger information action. + + + + + + + + + Further recommendation to passengers. (Unbounded since SIRI 2.0) + + + + + + + + + Further remark to passengers, e,g, "For more information call xy". + + + + + + + + + Summary of passenger information action. + + + + + + + + + Summary of passenger information action. + + + + + + + + + Class of size, e.g. L (large), M (medium), S (small) + + + + + Content for summary of a passenger information action + + + + + Content for the reason of a passenger information action + + + + + Content for the description of a passenger information action + + + + + Content for the consequence of a passenger information action + + + + + Content for the advice of a passenger information action + + + + + Content for the duration of a passenger information action. + + + + + Content for the remark of a passenger information action, e,g, "For more information call xy". + + + + + for internal information only, not passenger relevant + + + + + Any images associated with SITUATION. + + + + + Hyperlinks to other resources associated with SITUATION. + + + + + + + Values for perspectives. + + + + + + + - From c280161c8b28332ca8a084b655ece87f34f8a08c Mon Sep 17 00:00:00 2001 From: hennoit Date: Thu, 6 Aug 2020 15:34:12 +0200 Subject: [PATCH 176/290] moved structure to stop XmlSpy complaining... --- .../siri_estimatedVehicleJourney-v2.0.xsd | 44 +++++------------ xsd/siri_model/siri_journey_support-v2.0.xsd | 49 +++++++++++++++---- 2 files changed, 51 insertions(+), 42 deletions(-) diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index 599746a7..196e22e8 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -25,19 +25,24 @@ 2005-05-11 - 2007-04-17 + + 2007-04-17 Name Space changes - 2008-03-26 + + 2008-03-26 Add wrapper tag for Line DIRECTION to help binding to Axis - 2008-11-17 + + 2008-11-17 Revise to support substitution groups - 2011-01-19 + + 2011-01-19 Drop use of As Flat Groups for EstimatedCalls - 2012-03-23 + + 2012-03-23 +SIRI v2.0 Factored out of estimatedTimetableService Add EstimatedServiceJourneyInterchange (i.e. Estimated Connection of VEHICLE) to EstimatedTimetableDelivery @@ -60,7 +65,7 @@ Unclassified CEN, VDV, RTIG 2004-2012 - +
  • Derived from the VDV, RTIG XML and Trident standards.
    • @@ -182,33 +187,6 @@ Occupancies and capacities for individual VEHICLEs, e.g. parts of a COMPOUND TRA - - - Type for Origin and Destination stop of a VEHICLE JOURNEY. - - - - - The origin is used to help identify the VEHICLE JOURNEY. - - - - - Departure time from origin SCHEDULED STOP POINT. - - - - - The destination is used to help identify the VEHICLE JOURNEY. - - - - - Arrival time at destination SCHEDULED STOP POINT. - - - - diff --git a/xsd/siri_model/siri_journey_support-v2.0.xsd b/xsd/siri_model/siri_journey_support-v2.0.xsd index 0cc84c96..33825b13 100644 --- a/xsd/siri_model/siri_journey_support-v2.0.xsd +++ b/xsd/siri_model/siri_journey_support-v2.0.xsd @@ -23,21 +23,25 @@ 2007-03-29 - 2008-11-13 + + 2008-11-13 Correct Cardinalities on SIRI DESTINATION REF Structure - 2011-04-18 + + 2011-04-18 siri_journey-v2.0.xsd (l.1015). FramedVehicleJourneyRef isn't mandatory in MonitoredCall SIRI-SM answer accourding to CEN TS (prCEN/TS 15531-3:2006 (E) p.56). Make optional. RV ixxx.com - 2012-03-22 + + 2012-03-22 SIRI 2.0 Create from siri_journey Add TrainNumber Add departed, missed states to ProgressStatusEnum (arrivalStatus and DepartureStatus) Add VehicleStatusEnum - 2013-02-11 + + 2013-02-11 SIRI 2.0 Add notExpected state to ProgressStatusEnum Corrected enumeration value cancellled in VehicleStatusEnum @@ -60,7 +64,7 @@ Unclassified CEN, VDV, RTIG 2004-2012 - +
    • Derived from the VDV, RTIG CML and Trident standards.
      • @@ -176,6 +180,33 @@ Rail transport, Roads and road transport + + + Type for Origin and Destination stop of a VEHICLE JOURNEY. + + + + + The origin is used to help identify the VEHICLE JOURNEY. + + + + + Departure time from origin SCHEDULED STOP POINT. + + + + + The destination is used to help identify the VEHICLE JOURNEY. + + + + + Arrival time at destination SCHEDULED STOP POINT. + + + + @@ -213,13 +244,13 @@ Rail transport, Roads and road transport - Type for identifer of a SERVCIE JOURNEY INTERCHANGE. + Type for identifer of a SERVICE JOURNEY INTERCHANGE. - Type for reference to a SERVCIE JOURNEY INTERCHANGE. + Type for reference to a SERVICE JOURNEY INTERCHANGE. @@ -227,7 +258,7 @@ Rail transport, Roads and road transport - Reference to a SERVCIE JOURNEY INTERCHANGE. + Reference to a SERVICE JOURNEY INTERCHANGE. @@ -639,7 +670,7 @@ Corresponds to NeTEX TYPE OF SERVICe. - Classification of the State of the VEHICLE JORUNEY according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are still classified as on-time. Applications may use this to guide their own presentation of times. + Classification of the State of the VEHICLE JOURNEY according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are still classified as on-time. Applications may use this to guide their own presentation of times. From 344c73889d3ce4126cc3da9d419caed98cbd3ab9 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 12 Aug 2020 17:08:44 +0200 Subject: [PATCH 177/290] merge clean-up: fix DatedVehicleJourneyIndirectRef --- .../siri_estimatedVehicleJourney-v2.0.xsd | 27 ------------ xsd/siri_model/siri_journey_support-v2.0.xsd | 41 ++++++++++++++++--- 2 files changed, 36 insertions(+), 32 deletions(-) diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index 599746a7..30358cd1 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -182,33 +182,6 @@ Occupancies and capacities for individual VEHICLEs, e.g. parts of a COMPOUND TRA - - - Type for Origin and Destination stop of a VEHICLE JOURNEY. - - - - - The origin is used to help identify the VEHICLE JOURNEY. - - - - - Departure time from origin SCHEDULED STOP POINT. - - - - - The destination is used to help identify the VEHICLE JOURNEY. - - - - - Arrival time at destination SCHEDULED STOP POINT. - - - - diff --git a/xsd/siri_model/siri_journey_support-v2.0.xsd b/xsd/siri_model/siri_journey_support-v2.0.xsd index 0cc84c96..c79875bf 100644 --- a/xsd/siri_model/siri_journey_support-v2.0.xsd +++ b/xsd/siri_model/siri_journey_support-v2.0.xsd @@ -176,6 +176,33 @@ Rail transport, Roads and road transport + + + Type for Origin and Destination stop of a VEHICLE JOURNEY. + + + + + The origin is used to help identify the VEHICLE JOURNEY. + + + + + Departure time from origin SCHEDULED STOP POINT. + + + + + The destination is used to help identify the VEHICLE JOURNEY. + + + + + Arrival time at destination SCHEDULED STOP POINT. + + + + @@ -189,25 +216,29 @@ Rail transport, Roads and road transport - Optionally identify the VEHICLE JOURNEY indirectly by origin and destination and the scheduled times at these stops. + Identify a VEHICLE JOURNEY indirectly by origin and destination as well as the scheduled times at these stops. - Reference to LINE. + Reference to LINE of journey. - TRAIN NUMBER Reference. + Reference to TRAIN NUMBER of journey. - OPERATOR Reference. + Reference to OPERATOR of journey. + + + + + PARTICIPANT reference that identifies data producer of journey. - From 3d8e19c086532178de18aab314d521c24208dbc0 Mon Sep 17 00:00:00 2001 From: u215619 Date: Sun, 16 Aug 2020 18:50:18 +0200 Subject: [PATCH 178/290] renaming Remark to RemarkText improving annotations --- xsd/siri_model/siri_situation-v2.0.xsd | 8 ++++---- xsd/siri_model/siri_situationActions-v2.0.xsd | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/xsd/siri_model/siri_situation-v2.0.xsd b/xsd/siri_model/siri_situation-v2.0.xsd index 350c7cc2..770f5c44 100644 --- a/xsd/siri_model/siri_situation-v2.0.xsd +++ b/xsd/siri_model/siri_situation-v2.0.xsd @@ -945,7 +945,7 @@ Note: this means that ReasonName is NOT a complete message, but only a (few) wor - Nrtworks and Route(s) affected by SITUATION. + Networks and Route(s) affected by SITUATION. @@ -964,7 +964,7 @@ Note: this means that ReasonName is NOT a complete message, but only a (few) wor - Stop affected by SITUATION. + STOP POINT affected by SITUATION. @@ -978,7 +978,7 @@ Note: this means that ReasonName is NOT a complete message, but only a (few) wor - Stop affected by SITUATION. + Place other than STOP POINTs affected by SITUATION. @@ -992,7 +992,7 @@ Note: this means that ReasonName is NOT a complete message, but only a (few) wor - Stop affected by SITUATION. + Place affected by SITUATION. diff --git a/xsd/siri_model/siri_situationActions-v2.0.xsd b/xsd/siri_model/siri_situationActions-v2.0.xsd index 4cef5a67..d7c6be2d 100644 --- a/xsd/siri_model/siri_situationActions-v2.0.xsd +++ b/xsd/siri_model/siri_situationActions-v2.0.xsd @@ -602,7 +602,7 @@ - + Further remark to passengers, e,g, "For more information call xy". From fa23cb209469402843812a0b04a6c2073844bea5 Mon Sep 17 00:00:00 2001 From: u215619 Date: Sun, 16 Aug 2020 23:05:59 +0200 Subject: [PATCH 179/290] Changelog formatted to comments --- xsd/acsb/acsb_accessibility-v0.3.xsd | 4 +- xsd/acsb/acsb_limitations-v0.2.xsd | 4 +- xsd/acsb/acsb_passengerMobility-v0.3.xsd | 4 +- xsd/ifopt/ifopt_administration-v0.3.xsd | 4 +- xsd/ifopt/ifopt_checkpoint-v0.3.xsd | 11 +- xsd/ifopt/ifopt_countries-v0.2.xsd | 4 +- xsd/ifopt/ifopt_equipment-v0.3.xsd | 4 +- xsd/ifopt/ifopt_location-v0.3.xsd | 4 +- xsd/ifopt/ifopt_modes-v0.2.xsd | 4 +- xsd/ifopt/ifopt_modification-v0.3.xsd | 4 +- xsd/ifopt/ifopt_path-v0.2.xsd | 4 +- xsd/ifopt/ifopt_stop-v0.3.xsd | 4 +- xsd/ifopt/ifopt_time-v0.2.xsd | 4 +- xsd/ifopt/ifopt_types-v0.2.xsd | 4 +- xsd/siri.xsd | 2 +- xsd/siri/siri_base-v2.0.xsd | 4 +- xsd/siri/siri_common_services-v2.0.xsd | 4 +- .../siri_request_errorConditions-v2.0.xsd | 4 +- xsd/siri/siri_request_support-v2.0.xsd | 4 +- xsd/siri/siri_requests-v2.0.xsd | 157 +++++++++--------- xsd/siriSg.xsd | 41 +++-- xsd/siri_all_functionalServices.xsd | 4 +- xsd/siri_connectionMonitoring_service.xsd | 4 +- xsd/siri_connectionTimetable_service.xsd | 41 +++-- xsd/siri_discovery.xsd | 56 ++++--- xsd/siri_estimatedTimetable_service.xsd | 4 +- xsd/siri_facilityMonitoring_service.xsd | 4 +- xsd/siri_generalMessage_service.xsd | 35 ++-- .../siri_datedVehicleJourney-v2.0.xsd | 4 +- .../siri_estimatedVehicleJourney-v2.0.xsd | 41 +++-- xsd/siri_model/siri_facilities-v1.2.xsd | 4 +- xsd/siri_model/siri_feature_support-v2.0.xsd | 4 +- .../siri_interchangeJourney-v2.0.xsd | 4 +- xsd/siri_model/siri_journey-v2.0.xsd | 4 +- xsd/siri_model/siri_journey_support-v2.0.xsd | 2 +- xsd/siri_model/siri_modelPermissions-v2.0.xsd | 4 +- xsd/siri_model/siri_modes-v1.1.xsd | 4 +- .../siri_monitoredVehicleJourney-v2.0.xsd | 4 +- xsd/siri_model/siri_operator_support-v2.0.xsd | 4 +- xsd/siri_model/siri_situation-v2.0.xsd | 2 +- xsd/siri_model/siri_situationActions-v2.0.xsd | 21 +-- .../siri_situationIdentity-v1.1.xsd | 4 +- .../siri_targetedVehicleJourney-v2.0.xsd | 33 ++-- .../siri_connectionLink-v2.0.xsd | 4 +- .../siri_feature-v2.0.xsd | 22 +-- .../siri_infoChannel-v2.0.xsd | 22 +-- xsd/siri_model_discovery/siri_line-v2.0.xsd | 40 +++-- .../siri_stopPoint-v2.0.xsd | 31 ++-- xsd/siri_productionTimetable_service.xsd | 16 +- xsd/siri_situationExchange_service.xsd | 80 +++++---- xsd/siri_stopMonitoring_service.xsd | 4 +- xsd/siri_stopTimetable_service.xsd | 4 +- xsd/siri_utility/siri_location-v2.0.xsd | 22 +-- xsd/siri_utility/siri_participant-v2.0.xsd | 21 +-- xsd/siri_utility/siri_permissions-v2.0.xsd | 13 +- xsd/siri_utility/siri_types-v2.0.xsd | 6 +- xsd/siri_utility/siri_utility-v1.1.xsd | 11 +- xsd/siri_vehicleMonitoring_service.xsd | 50 +++--- xsd/wsdl_model/siri_wsConsumer-Framework.xsd | 4 +- xsd/wsdl_model/siri_wsConsumer-Services.xsd | 4 +- .../siri_wsProducer-DiscoveryCapability.xsd | 4 +- xsd/wsdl_model/siri_wsProducer-Framework.xsd | 4 +- xsd/wsdl_model/siri_wsProducer-Services.xsd | 4 +- .../siri_estimatedVehicleJourney-v2.0.xsd | 4 +- xsd/zrescue/siri_situation-v2.0.xsd | 4 +- xsd/zrescue/siri_situationAffects-v2.0.xsd | 4 +- 66 files changed, 502 insertions(+), 442 deletions(-) diff --git a/xsd/acsb/acsb_accessibility-v0.3.xsd b/xsd/acsb/acsb_accessibility-v0.3.xsd index c8f41e2f..50b68eba 100644 --- a/xsd/acsb/acsb_accessibility-v0.3.xsd +++ b/xsd/acsb/acsb_accessibility-v0.3.xsd @@ -28,14 +28,14 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified - CEN, Crown Copyright 2006-2012 + CEN, Crown Copyright 2006-2020
      • Derived from the SIRI standards.
      - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/acsb/acsb_limitations-v0.2.xsd b/xsd/acsb/acsb_limitations-v0.2.xsd index 1e34c4c8..55e536f8 100644 --- a/xsd/acsb/acsb_limitations-v0.2.xsd +++ b/xsd/acsb/acsb_limitations-v0.2.xsd @@ -28,14 +28,14 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified - CEN, Crown Copyright 2006-2012 + CEN, Crown Copyright 2006-2020
      • Derived from the SIRI standards.
      - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/acsb/acsb_passengerMobility-v0.3.xsd b/xsd/acsb/acsb_passengerMobility-v0.3.xsd index d5bbab82..d144e727 100644 --- a/xsd/acsb/acsb_passengerMobility-v0.3.xsd +++ b/xsd/acsb/acsb_passengerMobility-v0.3.xsd @@ -28,14 +28,14 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified - CEN, Crown Copyright 2006-2012 + CEN, Crown Copyright 2006-2020
      • Derived from the SIRI standards.
      - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/ifopt/ifopt_administration-v0.3.xsd b/xsd/ifopt/ifopt_administration-v0.3.xsd index 973fc2d5..d1e85306 100644 --- a/xsd/ifopt/ifopt_administration-v0.3.xsd +++ b/xsd/ifopt/ifopt_administration-v0.3.xsd @@ -28,14 +28,14 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified - CEN, Crown Copyright 2006-2012 + CEN, Crown Copyright 2006-2020
      • Derived from the SIRI standards.
      - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/ifopt/ifopt_checkpoint-v0.3.xsd b/xsd/ifopt/ifopt_checkpoint-v0.3.xsd index 670017ed..10a87494 100644 --- a/xsd/ifopt/ifopt_checkpoint-v0.3.xsd +++ b/xsd/ifopt/ifopt_checkpoint-v0.3.xsd @@ -16,9 +16,10 @@ 2007-03-29 - 2011-04-19 - Add explicit incldue of ifopt time so that will validate - + + 2011-04-19 + +

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

       @@ -31,14 +32,14 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified - CEN, Crown Copyright 2006-2012 + CEN, Crown Copyright 2006-2020
      • Derived from the IFOPT standards.
      - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/ifopt/ifopt_countries-v0.2.xsd b/xsd/ifopt/ifopt_countries-v0.2.xsd index 0ab276d2..7d25038a 100644 --- a/xsd/ifopt/ifopt_countries-v0.2.xsd +++ b/xsd/ifopt/ifopt_countries-v0.2.xsd @@ -28,14 +28,14 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified - CEN, Crown Copyright 2006-2012 + CEN, Crown Copyright 2006-2020
      • Derived from the SIRI standards.
      - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/ifopt/ifopt_equipment-v0.3.xsd b/xsd/ifopt/ifopt_equipment-v0.3.xsd index af560cbb..0fad790c 100644 --- a/xsd/ifopt/ifopt_equipment-v0.3.xsd +++ b/xsd/ifopt/ifopt_equipment-v0.3.xsd @@ -28,14 +28,14 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified - CEN, Crown Copyright 2006-2012 + CEN, Crown Copyright 2006-2020
      • Derived from the TransModel standards.
      - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/ifopt/ifopt_location-v0.3.xsd b/xsd/ifopt/ifopt_location-v0.3.xsd index a93b502e..f212b528 100644 --- a/xsd/ifopt/ifopt_location-v0.3.xsd +++ b/xsd/ifopt/ifopt_location-v0.3.xsd @@ -34,14 +34,14 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified - CEN, Crown Copyright 2006-2012 + CEN, Crown Copyright 2006-2020
      • Derived from the SIRI standards.
      - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/ifopt/ifopt_modes-v0.2.xsd b/xsd/ifopt/ifopt_modes-v0.2.xsd index 0a120646..2cf9e64d 100644 --- a/xsd/ifopt/ifopt_modes-v0.2.xsd +++ b/xsd/ifopt/ifopt_modes-v0.2.xsd @@ -25,14 +25,14 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified - CEN, Crown Copyright 2006-2012 + CEN, Crown Copyright 2006-2020
      • Derived from the SIRI standards.
      - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/ifopt/ifopt_modification-v0.3.xsd b/xsd/ifopt/ifopt_modification-v0.3.xsd index af92f5c7..5c4205f9 100644 --- a/xsd/ifopt/ifopt_modification-v0.3.xsd +++ b/xsd/ifopt/ifopt_modification-v0.3.xsd @@ -29,14 +29,14 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified - CEN, Crown Copyright 2006-2012 + CEN, Crown Copyright 2006-2020
      • Derived from the SIRI standards.
      - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/ifopt/ifopt_path-v0.2.xsd b/xsd/ifopt/ifopt_path-v0.2.xsd index a1a2847f..ee748a70 100644 --- a/xsd/ifopt/ifopt_path-v0.2.xsd +++ b/xsd/ifopt/ifopt_path-v0.2.xsd @@ -25,14 +25,14 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified - CEN, Crown Copyright 2006-2012 + CEN, Crown Copyright 2006-2020
      • Derived from the SIRI standards.
      - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/ifopt/ifopt_stop-v0.3.xsd b/xsd/ifopt/ifopt_stop-v0.3.xsd index fd826f04..c5ae666a 100644 --- a/xsd/ifopt/ifopt_stop-v0.3.xsd +++ b/xsd/ifopt/ifopt_stop-v0.3.xsd @@ -34,14 +34,14 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified - CEN, Crown Copyright 2006-2012 + CEN, Crown Copyright 2006-2020
      • Derived from the SIRI standards.
      - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/ifopt/ifopt_time-v0.2.xsd b/xsd/ifopt/ifopt_time-v0.2.xsd index e413ae7a..9c4725cd 100644 --- a/xsd/ifopt/ifopt_time-v0.2.xsd +++ b/xsd/ifopt/ifopt_time-v0.2.xsd @@ -25,14 +25,14 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified - CEN, Crown Copyright 2006-2012 + CEN, Crown Copyright 2006-2020
      • Derived from the SIRI standards.
      - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/ifopt/ifopt_types-v0.2.xsd b/xsd/ifopt/ifopt_types-v0.2.xsd index 21826202..7052b418 100644 --- a/xsd/ifopt/ifopt_types-v0.2.xsd +++ b/xsd/ifopt/ifopt_types-v0.2.xsd @@ -28,14 +28,14 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified - CEN, Crown Copyright 2006-2012 + CEN, Crown Copyright 2006-2020
      • Derived from the SIRI standards.
      - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri.xsd b/xsd/siri.xsd index 610a705f..aabc549a 100644 --- a/xsd/siri.xsd +++ b/xsd/siri.xsd @@ -130,7 +130,7 @@ mailto:schemer@siri.org.uk http://www.siri.org.uk/schema/2.0/xsd/siri__situationExchange_service.xsd Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
        diff --git a/xsd/siri/siri_base-v2.0.xsd b/xsd/siri/siri_base-v2.0.xsd index 8d33e84b..cd5618dc 100644 --- a/xsd/siri/siri_base-v2.0.xsd +++ b/xsd/siri/siri_base-v2.0.xsd @@ -60,14 +60,14 @@ http://www.siri.org.uk/schema/2.0/xsd/siri__common_services-v1.3xsd Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
        • Derived from the VDV, RTIG XML and Trident standards.
        - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri/siri_common_services-v2.0.xsd b/xsd/siri/siri_common_services-v2.0.xsd index 167b350f..e65accce 100644 --- a/xsd/siri/siri_common_services-v2.0.xsd +++ b/xsd/siri/siri_common_services-v2.0.xsd @@ -74,14 +74,14 @@ http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests-v2.0.xsd Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
        • Derived from the VDV, RTIG XML and Trident standards.
        - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri/siri_request_errorConditions-v2.0.xsd b/xsd/siri/siri_request_errorConditions-v2.0.xsd index 06ae5a5d..1d86d135 100644 --- a/xsd/siri/siri_request_errorConditions-v2.0.xsd +++ b/xsd/siri/siri_request_errorConditions-v2.0.xsd @@ -57,14 +57,14 @@ Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
        • Derived from the VDV, RTIGXML and Trident standards.
        - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri/siri_request_support-v2.0.xsd b/xsd/siri/siri_request_support-v2.0.xsd index d3c9ae76..8c7cfdbe 100644 --- a/xsd/siri/siri_request_support-v2.0.xsd +++ b/xsd/siri/siri_request_support-v2.0.xsd @@ -35,14 +35,14 @@ Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
        • Derived from the SIRI 1.0 standards.
        - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri/siri_requests-v2.0.xsd b/xsd/siri/siri_requests-v2.0.xsd index e1ed5605..d78a5a6c 100644 --- a/xsd/siri/siri_requests-v2.0.xsd +++ b/xsd/siri/siri_requests-v2.0.xsd @@ -29,48 +29,60 @@ 2007-03-29 - 2008-11-11 - -- add substitution groups for - AbstractRequest - AbstractResponse - AbstractFunctionalServiceRequest - AbstractFunctionalServiceSubscriptionRequest - AbstractFunctionalServiceDelivery - AbstractFunctionalServiceCapabilityRequest - AbstractFunctionalServiceCapabilityDelivery - AbstractDiscoveryDelivery - ErrorCode - - - 2008-11-13 - Move abstract discovery deliveries to here from siri_discoveries - - 2008-11-17 - -- Add abstract discovery request - Make request and response descendent of Request and Response Types - - 2009-03-31 - - Add ErrorConditionelement to enable WSDL axis binding - - 2011-04-18 - - ErrorConditionStructure Line 841 should not be abstract. Fix from RV ixxi.biz - Also Add ServiceConditionErrorConditionElement - - 2012-03-23 - +SIRI v2.0 - Add error number to Error structure - factor out base identifier defintiiosn so can be share dwith error codes - Factor out error codes - Factor our Permission model to separate package siri_permissions - - 2012-06-17 - +SIRI v2.0 x - Add delegator endpoint group to ServiceRequest and FunctionalServcieResponse - - 2013-02-11 - Added AbstractRequiredIdentifiedItemStructure - Added AbstractRequiredReferencingItemStructure - + + 2008-11-11 + + + + 2008-11-13 + + + + 2008-11-17 + + + + 2009-03-31 + + + + 2011-04-18 + + + + 2012-03-23 + + + + 2012-06-17 + + + + 2013-02-11 + +

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

         @@ -81,32 +93,26 @@ {http://www.siri.org.uk/schema/2.0/xsd/siri/}siri_requests-v2.0.xsd [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD + Kizoom, 109-123 Clifton Street, London EC4A 4LD http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types-v2.0.xsd Unclassified - - CEN, VDV, RTIG 2004-2012 - + + CEN, VDV, RTIG 2004-2020 +
        • Derived from the VDV, RTIGXML and Trident standards.
        - Version 2.0 Draft + Version 2.0 - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - + Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, Ports and maritime transport, Ferries (marine), Public transport, Bus services, Coach services, Bus stops and stations, Rail transport, Railway stations and track, Train services, Underground trains, Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, Rail transport, Roads and road transport + CEN TC278 WG3 SG7 - SIRI XML schema. Common Request elements. + SIRI XML schema. Common Request elements. Standard @@ -154,7 +160,7 @@ Rail transport, Roads and road transport - Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . +SIRI v2.0 + Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . +SIRI v2.0 @@ -175,7 +181,7 @@ Rail transport, Roads and road transport - If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 + If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 @@ -202,12 +208,12 @@ Rail transport, Roads and road transport - If request has been proxied by an intermediate aggregating system , tracking informattion relating to the original requestor. This allows the aggregation to be stateless. + If request has been proxied by an intermediate aggregating system , tracking informattion relating to the original requestor. This allows the aggregation to be stateless. - Address of original Consumer, i.e. requesting system to which delegating response is to be returned. +SIRI 2.0 + Address of original Consumer, i.e. requesting system to which delegating response is to be returned. +SIRI 2.0 @@ -289,9 +295,7 @@ Rail transport, Roads and road transport - By using this element, the subscriber asks the data provider for an extension of the InitialTerminationTime of the subscription. -If SubscriptionRenewal is omitted, this request is to be treated as a re-subscription and therefore all data corresponding to the SubscriptionRequest must -be sent in the initial response (or a portion of the data if MoreData is set to 'true'). +SIRI v2.1 + By using this element, the subscriber asks the data provider for an extension of the InitialTerminationTime of the subscription. If SubscriptionRenewal is omitted, this request is to be treated as a re-subscription and therefore all data corresponding to the SubscriptionRequest must be sent in the initial response (or a portion of the data if MoreData is set to 'true'). +SIRI v2.1 @@ -396,7 +400,7 @@ be sent in the initial response (or a portion of the data if MoreData is set to - If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 + If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 @@ -444,7 +448,7 @@ be sent in the initial response (or a portion of the data if MoreData is set to - If request has been proxied by an intermediate aggregting system, trackng informattion relating to the original requestor. This allows the aggregation to be stateless. + If request has been proxied by an intermediate aggregting system, trackng informattion relating to the original requestor. This allows the aggregation to be stateless. @@ -571,7 +575,7 @@ be sent in the initial response (or a portion of the data if MoreData is set to - If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 + If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 @@ -605,7 +609,7 @@ be sent in the initial response (or a portion of the data if MoreData is set to - If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 + If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 @@ -624,7 +628,7 @@ be sent in the initial response (or a portion of the data if MoreData is set to - If request has been proxied by an intermediate aggregting system, trackng informattion relating to the original requestor. This allows the aggregation to be stateless. + If request has been proxied by an intermediate aggregting system, trackng informattion relating to the original requestor. This allows the aggregation to be stateless. @@ -677,9 +681,10 @@ be sent in the initial response (or a portion of the data if MoreData is set to - Type for Unique reference to reponse. May be used to reference request in subsequent interactions. Used for WSDL - - . + Type for Unique reference to reponse. May be used to reference request in subsequent interactions. Used for WSDL + + . + @@ -687,7 +692,7 @@ be sent in the initial response (or a portion of the data if MoreData is set to - If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 + If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 @@ -787,7 +792,7 @@ be sent in the initial response (or a portion of the data if MoreData is set to - Reference to an Activity Element of a delivery. + Reference to an Activity Element of a delivery. @@ -803,7 +808,7 @@ be sent in the initial response (or a portion of the data if MoreData is set to - Reference to an Activity Element of a delivery. + Reference to an Activity Element of a delivery. @@ -868,7 +873,7 @@ be sent in the initial response (or a portion of the data if MoreData is set to - If request has been proxied by an intermediate aggregting system, trackng informattion relating to the original requestor. This allows the aggregation to be stateless. + If request has been proxied by an intermediate aggregting system, trackng informattion relating to the original requestor. This allows the aggregation to be stateless. @@ -977,7 +982,7 @@ be sent in the initial response (or a portion of the data if MoreData is set to - Whether producer can provide multiple translations of NL text elements +SIRI 2.0 + Whether producer can provide multiple translations of NL text elements +SIRI 2.0 diff --git a/xsd/siriSg.xsd b/xsd/siriSg.xsd index 5063795e..6506889d 100644 --- a/xsd/siriSg.xsd +++ b/xsd/siriSg.xsd @@ -51,24 +51,29 @@ Jeff Maki, openplans, us, v2.0 Europe >Drafted for version 1.0 & Version 2.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - 2008-11-17 - Created from Siri.xsd - - 2008-04-18 - Revised - - 2009-03-30 - Remove uneccessary groups - - 2011-04-18 - Updated journey, request and other subpackages - see readme - - 2012-03-23 - SIRI Version 2.0 + + 2008-11-17 + + + + 2008-04-18 + + + + 2009-03-30 + + + + 2011-04-18 + + + + 2012-03-23 + +

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

        SIRI is defined by XMLschemas and comprises a general protocol for communication, and a modular set of functional services. @@ -94,7 +99,7 @@ http://www.siri.org.uk/schema/2.0/xsd/siri__allFunctionalServices.xsd Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020

          @@ -102,7 +107,7 @@
        • Derived from the SIRI Version 1.0
        - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_all_functionalServices.xsd b/xsd/siri_all_functionalServices.xsd index 97283f46..03ec58ec 100644 --- a/xsd/siri_all_functionalServices.xsd +++ b/xsd/siri_all_functionalServices.xsd @@ -51,7 +51,7 @@ http://www.siri.org.uk/schema/2.0/xsd/siri__facilityMonitoring_service.xsd Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
          @@ -59,7 +59,7 @@
        • Derived from the SIRI Version 1.0.
        - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_connectionMonitoring_service.xsd b/xsd/siri_connectionMonitoring_service.xsd index 3af80faf..a9adeb70 100644 --- a/xsd/siri_connectionMonitoring_service.xsd +++ b/xsd/siri_connectionMonitoring_service.xsd @@ -64,14 +64,14 @@ http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions-v2.0.xsd Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
        • Derived from the VDV, RTIG XML and Trident standards.
        - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_connectionTimetable_service.xsd b/xsd/siri_connectionTimetable_service.xsd index c2f247fb..91db75d5 100644 --- a/xsd/siri_connectionTimetable_service.xsd +++ b/xsd/siri_connectionTimetable_service.xsd @@ -25,25 +25,30 @@ 2005-05-11 - 2007-04-17 - Name Space changes - - 2008-11-17 - Revise to support substitution groups - - 2011-01-19 - Drop use of As Flat Groups for InterChangeJourney - - 2012-03-23 - +SIRI v2.0 - - 2012-04-18 - Add valid until to response + + 2007-04-17 + + + + 2008-11-17 + + + + 2011-01-19 + + + + 2012-03-23 + + + + 2012-04-18 + +

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

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

        @@ -61,14 +66,14 @@ http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey-v2.0.xsd Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
        • Derived from the VDV, RTIG XML and Trident standards.
        - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_discovery.xsd b/xsd/siri_discovery.xsd index 913823d8..2ca4f717 100644 --- a/xsd/siri_discovery.xsd +++ b/xsd/siri_discovery.xsd @@ -24,37 +24,43 @@ 2005-11-25 - 2007-04-17 - Name Space changes - - 2008-11-13 - Fix cardinalities on delivery items eg LINEs, refs, facilities - MoveAbstractDiscoveryDelivery to siri_requests - - 2008-11-17 - Revise to support substitution groups - Correct Type on VEHICLE features delivery structure - - 2012-03-23 - +SIRI v2.0 + + 2007-04-17 + + + + 2008-11-13 + + + + 2008-11-17 + + + + 2012-03-23 + + + + 2012-05-17 + + + + 2013-03-28 + +

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

        This subschema describes discovery services used by different SIRI functional services @@ -74,14 +80,14 @@ http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference-v2.0.xsd Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020

        • Discovery services Derived from the NaPTAN standard .
        - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_estimatedTimetable_service.xsd b/xsd/siri_estimatedTimetable_service.xsd index b5c3f893..57730fdf 100644 --- a/xsd/siri_estimatedTimetable_service.xsd +++ b/xsd/siri_estimatedTimetable_service.xsd @@ -62,14 +62,14 @@ http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions-v2.0.xsd Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
        • Derived from the VDV, RTIG XML and Trident standards.
        - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_facilityMonitoring_service.xsd b/xsd/siri_facilityMonitoring_service.xsd index 8e70d606..a2fad698 100644 --- a/xsd/siri_facilityMonitoring_service.xsd +++ b/xsd/siri_facilityMonitoring_service.xsd @@ -47,14 +47,14 @@ http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions-v2.0.xsd Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
        • Derived from the VDV, RTIG XML and Trident standards.
        - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_generalMessage_service.xsd b/xsd/siri_generalMessage_service.xsd index a109673d..d2383ef3 100644 --- a/xsd/siri_generalMessage_service.xsd +++ b/xsd/siri_generalMessage_service.xsd @@ -24,20 +24,25 @@ 2005-05-11 - 2007-04-17 - Name Space changes - - 2008-11-17 - Revise to support substitution groups - - 2011-04-18 + + 2007-04-17 + + + + 2008-11-17 + + + + 2011-04-18 + + + + 2012-03-23 + +

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

        This sub-schema describes the General Message Service.

        @@ -55,14 +60,14 @@ http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_reference-v2.0.xsd Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
        • Derived from the VDV, RTIG XML and Trident standards.
        - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd index 8488d5a2..0c65d553 100644 --- a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd @@ -69,14 +69,14 @@ http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey-v2.0.xsd Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
        • Derived from the VDV, RTIG XML and Trident standards.
        - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index 6268dc4b..02d58710 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -25,24 +25,29 @@ 2005-05-11 - 2007-04-17 - Name Space changes - - 2008-03-26 - Add wrapper tag for Line DIRECTION to help binding to Axis - - 2008-11-17 - Revise to support substitution groups - - 2011-01-19 - Drop use of As Flat Groups for EstimatedCalls - - 2012-03-23 - +SIRI v2.0 + + 2007-04-17 + + + + 2008-03-26 + + + + 2008-11-17 + + + + 2011-01-19 + + + + 2012-03-23 + +

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

        This sub-schema describes the Estimated Timetable Service.

        @@ -59,14 +64,14 @@ http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey-v2.0.xsd Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
        • Derived from the VDV, RTIG XML and Trident standards.
        - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_facilities-v1.2.xsd b/xsd/siri_model/siri_facilities-v1.2.xsd index 04ef8135..4012538c 100644 --- a/xsd/siri_model/siri_facilities-v1.2.xsd +++ b/xsd/siri_model/siri_facilities-v1.2.xsd @@ -38,14 +38,14 @@ Unclassified - Kizoom 2000-2005, CEN 2009-2012 + Kizoom 2000-2005, CEN 2009-2020
        • Derived from the TPEG Categories schema as encoded in the Kizoom XTIS schema.
        - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_feature_support-v2.0.xsd b/xsd/siri_model/siri_feature_support-v2.0.xsd index a8ad0c0c..2701f3f8 100644 --- a/xsd/siri_model/siri_feature_support-v2.0.xsd +++ b/xsd/siri_model/siri_feature_support-v2.0.xsd @@ -47,14 +47,14 @@ Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
        • Derived from the VDV, RTIG CML and Trident standards.
        - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_interchangeJourney-v2.0.xsd b/xsd/siri_model/siri_interchangeJourney-v2.0.xsd index 992b4efa..51a75eeb 100644 --- a/xsd/siri_model/siri_interchangeJourney-v2.0.xsd +++ b/xsd/siri_model/siri_interchangeJourney-v2.0.xsd @@ -33,14 +33,14 @@ http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey-v2.0.xsd Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
        • Derived from the VDV, RTIG XML and Trident standards.
        - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index 82b0fff0..f94d3bf4 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -96,14 +96,14 @@ Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
        • Derived from the VDV, RTIG CML and Trident standards.
        - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_journey_support-v2.0.xsd b/xsd/siri_model/siri_journey_support-v2.0.xsd index ed795fa2..e20f297c 100644 --- a/xsd/siri_model/siri_journey_support-v2.0.xsd +++ b/xsd/siri_model/siri_journey_support-v2.0.xsd @@ -69,7 +69,7 @@
      • Derived from the VDV, RTIG CML and Trident standards.
      - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_modelPermissions-v2.0.xsd b/xsd/siri_model/siri_modelPermissions-v2.0.xsd index 7162963d..88dda23c 100644 --- a/xsd/siri_model/siri_modelPermissions-v2.0.xsd +++ b/xsd/siri_model/siri_modelPermissions-v2.0.xsd @@ -38,14 +38,14 @@ Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
      • Derived from the VDV, RTIGXML and Trident standards.
      - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_modes-v1.1.xsd b/xsd/siri_model/siri_modes-v1.1.xsd index e3f876c2..d85f79e4 100644 --- a/xsd/siri_model/siri_modes-v1.1.xsd +++ b/xsd/siri_model/siri_modes-v1.1.xsd @@ -34,7 +34,7 @@ Unclassified - Kizoom 2000-2005, CEN 2009-2012 + Kizoom 2000-2005, CEN 2009-2020
        @@ -42,7 +42,7 @@
      • Derived from the TPEG Categories schema
      - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd index cba57977..278e8dc4 100644 --- a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd @@ -77,14 +77,14 @@       Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
      • Derived from the VDV, RTIG CML and Trident standards.
      - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_operator_support-v2.0.xsd b/xsd/siri_model/siri_operator_support-v2.0.xsd index 342ec61a..01ad5a84 100644 --- a/xsd/siri_model/siri_operator_support-v2.0.xsd +++ b/xsd/siri_model/siri_operator_support-v2.0.xsd @@ -28,14 +28,14 @@ [ISO 639-2/B] ENG CEN - Add POSTAL ADDRESS Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
      • Derived from the SIRI standards.
      - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_situation-v2.0.xsd b/xsd/siri_model/siri_situation-v2.0.xsd index dc6dda8f..cdf4e90e 100644 --- a/xsd/siri_model/siri_situation-v2.0.xsd +++ b/xsd/siri_model/siri_situation-v2.0.xsd @@ -83,7 +83,7 @@ 2020-07-15 diff --git a/xsd/siri_model/siri_situationActions-v2.0.xsd b/xsd/siri_model/siri_situationActions-v2.0.xsd index 4ce54a15..c94c1bd6 100644 --- a/xsd/siri_model/siri_situationActions-v2.0.xsd +++ b/xsd/siri_model/siri_situationActions-v2.0.xsd @@ -21,28 +21,19 @@ 2013-10-01 - + 2013-05-01 - + 2018-11-13 - + 2020-07-14 - +

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

      @@ -60,14 +51,14 @@ Unclassified - Kizoom 2000-2007, CEN 2009-2014 + Kizoom 2000-2007, CEN 2009-2020
      • Schema derived Derived from the Kizoom XTIS schema
      - Version 2.0 Draft + Version 2.0 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 diff --git a/xsd/siri_model/siri_situationIdentity-v1.1.xsd b/xsd/siri_model/siri_situationIdentity-v1.1.xsd index db32d9cf..d672fedb 100644 --- a/xsd/siri_model/siri_situationIdentity-v1.1.xsd +++ b/xsd/siri_model/siri_situationIdentity-v1.1.xsd @@ -34,14 +34,14 @@ Unclassified - Kizoom CEN, VDV, RTIG 2004,2007 + Kizoom CEN, VDV, RTIG 2004-2020
      • Derived from the VDV, RTIG CML and Trident standards.
      - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_targetedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_targetedVehicleJourney-v2.0.xsd index a7befe72..1ea55267 100644 --- a/xsd/siri_model/siri_targetedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_targetedVehicleJourney-v2.0.xsd @@ -26,19 +26,22 @@ 2005-12-12 - 2007-04-17 - Name Space changes - - 2007-03-26 - Drop separate flatten structure on response for stopVisit - - 2008-11-17 - Revise to support substitution groups - - 2012-03-23 - +SIRI v2.0 - - + + 2007-04-17 + + + + 2007-03-26 + + + + 2008-11-17 + + + + 2012-03-23 + +

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

      This sub-schema describes the TargetedVehicleJourney used in the Stop Timetable Service.

      @@ -55,14 +58,14 @@ http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey-v2.0.xsd Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
      • Derived from the VDV, RTIG XML and Trident standards.
      - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model_discovery/siri_connectionLink-v2.0.xsd b/xsd/siri_model_discovery/siri_connectionLink-v2.0.xsd index f704dd9a..03896aed 100644 --- a/xsd/siri_model_discovery/siri_connectionLink-v2.0.xsd +++ b/xsd/siri_model_discovery/siri_connectionLink-v2.0.xsd @@ -30,14 +30,14 @@ http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference-v2.0.xsd Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
      • Discovery services Derived from the NaPTAN standard .
      - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model_discovery/siri_feature-v2.0.xsd b/xsd/siri_model_discovery/siri_feature-v2.0.xsd index c0757125..30fb1e89 100644 --- a/xsd/siri_model_discovery/siri_feature-v2.0.xsd +++ b/xsd/siri_model_discovery/siri_feature-v2.0.xsd @@ -11,15 +11,17 @@ 2012-03-23 - 2008-11-17 - Revise to support substitution groups - Correct Type on VEHICLE features delivery structure - - 2012-03-23 - +SIRI v2.0 + + 2008-11-17 + + + + 2012-03-23 + +

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

      This subschema describes soem code value models used by different SIRI functional services @@ -39,14 +41,14 @@ http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference-v2.0.xsd Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020

      • Discovery services Derived from the NaPTAN standard .
      - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model_discovery/siri_infoChannel-v2.0.xsd b/xsd/siri_model_discovery/siri_infoChannel-v2.0.xsd index c16cfc98..63d1f0ec 100644 --- a/xsd/siri_model_discovery/siri_infoChannel-v2.0.xsd +++ b/xsd/siri_model_discovery/siri_infoChannel-v2.0.xsd @@ -11,14 +11,16 @@ 2012-03-23 - 2008-11-17 - Revise to support substitution groups - Correct Type on VEHICLE features delivery structure - - 2012-03-23 - +SIRI v2.0 - Factored out from siri_discovery - + + 2008-11-17 + + + + 2012-03-23 + +

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

      This subschema describes soem code value models used by different SIRI functional services @@ -38,14 +40,14 @@ http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference-v2.0.xsd Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020

      • Discovery services Derived from the NaPTAN standard .
      - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model_discovery/siri_line-v2.0.xsd b/xsd/siri_model_discovery/siri_line-v2.0.xsd index 23ecf389..581c822b 100644 --- a/xsd/siri_model_discovery/siri_line-v2.0.xsd +++ b/xsd/siri_model_discovery/siri_line-v2.0.xsd @@ -11,23 +11,27 @@ 2012-03-23 - 2008-11-17 - Revise to support substitution groups - Correct Type on VEHICLE features delivery structure - - 2012-03-23 - +SIRI v2.0 - Factored out from siri_discovery - - 2012-05-10 - +SIRI v2.0 + + 2008-11-17 + + + + 2012-03-23 + + + + 2012-05-10 + + + + 2012-06-12 + +

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

      This subschema describes soem code value models used by different SIRI functional services @@ -47,14 +51,14 @@ http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference-v2.0.xsd Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020

      • Discovery services Derived from the NaPTAN standard .
      - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model_discovery/siri_stopPoint-v2.0.xsd b/xsd/siri_model_discovery/siri_stopPoint-v2.0.xsd index 9308ea8a..25ea7814 100644 --- a/xsd/siri_model_discovery/siri_stopPoint-v2.0.xsd +++ b/xsd/siri_model_discovery/siri_stopPoint-v2.0.xsd @@ -11,20 +11,23 @@ 2012-03-23 - 2008-11-17 - Revise to support substitution groups - Correct Type on VEHICLE features delivery structure - - 2012-03-23 - +SIRI v2.0 + + 2008-11-17 + + + + 2012-03-23 + + + + 2012-06-12 + +

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

      This subschema describes soem code value models used by different SIRI functional services @@ -44,14 +47,14 @@ http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference-v2.0.xsd Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020

      • Discovery services Derived from the NaPTAN standard .
      - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_productionTimetable_service.xsd b/xsd/siri_productionTimetable_service.xsd index 485024e6..b9873a50 100644 --- a/xsd/siri_productionTimetable_service.xsd +++ b/xsd/siri_productionTimetable_service.xsd @@ -27,25 +27,25 @@ 2007-04-17 2008-03-26 - 2008-11-17 - 2011-04-18 @@ -53,7 +53,7 @@ 2011-01-19 @@ -85,7 +85,7 @@ http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions-v2.0.xsd Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
        diff --git a/xsd/siri_situationExchange_service.xsd b/xsd/siri_situationExchange_service.xsd index d36fd25a..a72374c0 100644 --- a/xsd/siri_situationExchange_service.xsd +++ b/xsd/siri_situationExchange_service.xsd @@ -17,42 +17,56 @@ 2008-01-22 - 2009-04-17 - Name Space changes - - 2008-01-17 - IFOPT and Datex2 compatibility changes - - 2008-07-05 - Allow zero sized SITUATIONs - - 2008-10-01 - -- Add StatusFilterGroup to SIRI-SX request with Verification, Progerss and Reality - -- Change caridinality on LineRef and CONNECTION link filters to allow many rather than just one. - -- Corret predictability filter values to be an enum. - -- Add a place and Road filter. - - 2008-11-17 - -- Revise to support substitution groups - - 2012-03-23 - +SIRI v2.0 + + 2009-04-17 + + + + 2008-01-17 + + + + 2008-07-05 + + + + 2008-10-01 + + + + 2008-11-17 + + + + 2012-03-23 + + + + 2013-10-09 + + + + 2014-06-20 + + + + 2018-11-13 + +

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

        This sub-schema describes the Situation Exchange Service.

        @@ -71,7 +85,7 @@ http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions-v2.0.xsd Unclassified - CEN, VDV, RTIG 2004, 2007 + CEN, VDV, RTIG 2004-2020
          @@ -79,7 +93,7 @@
        • categories from TPEG
        - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_stopMonitoring_service.xsd b/xsd/siri_stopMonitoring_service.xsd index 5225ed65..dbfbe4b1 100644 --- a/xsd/siri_stopMonitoring_service.xsd +++ b/xsd/siri_stopMonitoring_service.xsd @@ -87,14 +87,14 @@ http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey-v2.0.xsd Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
        • Derived from the VDV, RTIG XML and Trident standards.
        - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_stopTimetable_service.xsd b/xsd/siri_stopTimetable_service.xsd index 677297c7..79662e9d 100644 --- a/xsd/siri_stopTimetable_service.xsd +++ b/xsd/siri_stopTimetable_service.xsd @@ -61,14 +61,14 @@ http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions-v2.0.xsd Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
        • Derived from the VDV, RTIG XML and Trident standards.
        - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_utility/siri_location-v2.0.xsd b/xsd/siri_utility/siri_location-v2.0.xsd index 89065cbd..912cc6c6 100644 --- a/xsd/siri_utility/siri_location-v2.0.xsd +++ b/xsd/siri_utility/siri_location-v2.0.xsd @@ -26,15 +26,17 @@ 2007-03-29 - 2012-03-23 - +SIRI v2.0 + + 2012-03-23 + + + + 2012-05-10 + +

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

         @@ -47,14 +49,14 @@ [ISO 639-2/B] ENG CEN Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
        • Derived from the VDV, RTIG XML and Trident standards.
        - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_utility/siri_participant-v2.0.xsd b/xsd/siri_utility/siri_participant-v2.0.xsd index 4af406d9..511ca1d3 100644 --- a/xsd/siri_utility/siri_participant-v2.0.xsd +++ b/xsd/siri_utility/siri_participant-v2.0.xsd @@ -15,14 +15,15 @@ 2007-05-15 - 2008-07-015 - drop use of partipant pair - - - 2012-03-22 - SIRI 2.0 - Move Capability - + + 2008-07-015 + + + + 2012-03-22 + +

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

         @@ -36,14 +37,14 @@ Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
        • Derived from the VDV, RTIGXML and Trident standards.
        - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_utility/siri_permissions-v2.0.xsd b/xsd/siri_utility/siri_permissions-v2.0.xsd index 8620cf55..c41d6931 100644 --- a/xsd/siri_utility/siri_permissions-v2.0.xsd +++ b/xsd/siri_utility/siri_permissions-v2.0.xsd @@ -11,10 +11,11 @@ 2012-03-24 - 2012-03-23 - +SIRI v2.0 - Add error number to Error structure - + + 2012-03-23 + +

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

         @@ -33,14 +34,14 @@ Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
        • Derived from the VDV, RTIGXML and Trident standards.
        - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_utility/siri_types-v2.0.xsd b/xsd/siri_utility/siri_types-v2.0.xsd index 76afede1..1779d7b5 100644 --- a/xsd/siri_utility/siri_types-v2.0.xsd +++ b/xsd/siri_utility/siri_types-v2.0.xsd @@ -22,10 +22,8 @@         2012-03-23 - +

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

        diff --git a/xsd/siri_utility/siri_utility-v1.1.xsd b/xsd/siri_utility/siri_utility-v1.1.xsd index ec11acbd..2a064526 100644 --- a/xsd/siri_utility/siri_utility-v1.1.xsd +++ b/xsd/siri_utility/siri_utility-v1.1.xsd @@ -10,9 +10,10 @@ CEN TC278 WG3 SG9 Team. Europe First drafted for version 1.0 CEN TC278 WG3 SG9 Editor Nicholas Knowles. mailto:schemer@siri.org.uk - 2008-09-307 - change any to lax / emopty - + + 2008-09-307 + + 2007-04-17 @@ -28,14 +29,14 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
        • Derived from the VDV, RTIGXML and Trident standards.
        - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_vehicleMonitoring_service.xsd b/xsd/siri_vehicleMonitoring_service.xsd index 2d0a2c00..c9e42cf6 100644 --- a/xsd/siri_vehicleMonitoring_service.xsd +++ b/xsd/siri_vehicleMonitoring_service.xsd @@ -23,33 +23,39 @@ 2005-05-11 - 2007-04-17 - Name Space changes - - 2007-03-26 - Drop separate flatten structure on response for VehicleActivity - - 2008-11-17 - Revise to support substitution groups - - 2012-03-23 - +SIRI v2.0 + + 2007-04-17 + + + + 2007-03-26 + + + + 2008-11-17 + + + + 2012-03-23 + + + + 2012-04-29 + + + + 2013-02-11 + +

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

        This sub-schema describes the Vehicle Monitoring Service.

        @@ -68,14 +74,14 @@ http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions-v2.0.xsd Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
        • Derived from the VDV, RTIG XML and Trident standards.
        - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/wsdl_model/siri_wsConsumer-Framework.xsd b/xsd/wsdl_model/siri_wsConsumer-Framework.xsd index aa970cb0..f8f91027 100644 --- a/xsd/wsdl_model/siri_wsConsumer-Framework.xsd +++ b/xsd/wsdl_model/siri_wsConsumer-Framework.xsd @@ -39,14 +39,14 @@ http://www.siri.org.uk/schema/2.0/siri_wsCOnsumer-Document.wsdl Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
        • Derived from the VDV, RTIG XML and Trident standards.
        - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/wsdl_model/siri_wsConsumer-Services.xsd b/xsd/wsdl_model/siri_wsConsumer-Services.xsd index 5ddc7c1f..cdd77175 100644 --- a/xsd/wsdl_model/siri_wsConsumer-Services.xsd +++ b/xsd/wsdl_model/siri_wsConsumer-Services.xsd @@ -39,14 +39,14 @@ http://www.siri.org.uk/schema/2.0/siri_wsCOnsumer-Document.wsdl Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
        • Derived from the VDV, RTIG XML and Trident standards.
        - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/wsdl_model/siri_wsProducer-DiscoveryCapability.xsd b/xsd/wsdl_model/siri_wsProducer-DiscoveryCapability.xsd index 0554aa03..1e901c82 100644 --- a/xsd/wsdl_model/siri_wsProducer-DiscoveryCapability.xsd +++ b/xsd/wsdl_model/siri_wsProducer-DiscoveryCapability.xsd @@ -38,14 +38,14 @@ http://www.siri.org.uk/schema/2.0/siri_wsCOnsumer-Document.wsdl Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
        • Derived from the VDV, RTIG XML and Trident standards.
        - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/wsdl_model/siri_wsProducer-Framework.xsd b/xsd/wsdl_model/siri_wsProducer-Framework.xsd index 1aa41d7b..9df4a581 100644 --- a/xsd/wsdl_model/siri_wsProducer-Framework.xsd +++ b/xsd/wsdl_model/siri_wsProducer-Framework.xsd @@ -38,14 +38,14 @@ http://www.siri.org.uk/schema/2.0/siri_wsCOnsumer-Document.wsdl Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
        • Derived from the VDV, RTIG XML and Trident standards.
        - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/wsdl_model/siri_wsProducer-Services.xsd b/xsd/wsdl_model/siri_wsProducer-Services.xsd index f3b2fd9d..0fbc780d 100644 --- a/xsd/wsdl_model/siri_wsProducer-Services.xsd +++ b/xsd/wsdl_model/siri_wsProducer-Services.xsd @@ -38,14 +38,14 @@ http://www.siri.org.uk/schema/2.0/siri_wsCOnsumer-Document.wsdl Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
        • Derived from the VDV, RTIG XML and Trident standards.
        - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/zrescue/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/zrescue/siri_estimatedVehicleJourney-v2.0.xsd index c0c677fe..ed39ce1e 100644 --- a/xsd/zrescue/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/zrescue/siri_estimatedVehicleJourney-v2.0.xsd @@ -59,14 +59,14 @@ http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey-v2.0.xsd Unclassified - CEN, VDV, RTIG 2004-2012 + CEN, VDV, RTIG 2004-2020
        • Derived from the VDV, RTIG XML and Trident standards.
        - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/zrescue/siri_situation-v2.0.xsd b/xsd/zrescue/siri_situation-v2.0.xsd index 0ba0c1ae..8913928f 100644 --- a/xsd/zrescue/siri_situation-v2.0.xsd +++ b/xsd/zrescue/siri_situation-v2.0.xsd @@ -79,14 +79,14 @@ Unclassified - Kizoom 2000-2005, CEN 2009-2012 + Kizoom 2000-2005, CEN 2009-2020
        • Schema Derived from the Kizoom XTIS schema
        - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/zrescue/siri_situationAffects-v2.0.xsd b/xsd/zrescue/siri_situationAffects-v2.0.xsd index 315bca5e..c4ee9eff 100644 --- a/xsd/zrescue/siri_situationAffects-v2.0.xsd +++ b/xsd/zrescue/siri_situationAffects-v2.0.xsd @@ -60,14 +60,14 @@ Unclassified - Kizoom 2000-2007, CEN 2009-2012 + Kizoom 2000-2007, CEN 2009-2020
        • Schema derived Derived from the Kizoom XTIS schema
        - Version 2.0 Draft + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, From 25352b35b26d0808f5e2e6f60f2cffbb359d03ff Mon Sep 17 00:00:00 2001 From: u215619 Date: Mon, 17 Aug 2020 10:54:26 +0200 Subject: [PATCH 180/290] Mark some elements with default value as optional Set default value according to existing annotations --- xsd/siri/siri_common_services-v2.0.xsd | 4 ++-- xsd/siri/siri_request_support-v2.0.xsd | 2 +- xsd/siri_stopMonitoring_service.xsd | 6 +++--- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/xsd/siri/siri_common_services-v2.0.xsd b/xsd/siri/siri_common_services-v2.0.xsd index e65accce..03bf39d1 100644 --- a/xsd/siri/siri_common_services-v2.0.xsd +++ b/xsd/siri/siri_common_services-v2.0.xsd @@ -467,7 +467,7 @@ Rail transport, Roads and road transport - + Description of any error or warning condition. @@ -704,7 +704,7 @@ Rail transport, Roads and road transport Data received Acknowledgement content. - + Description of any error or warning condition. diff --git a/xsd/siri/siri_request_support-v2.0.xsd b/xsd/siri/siri_request_support-v2.0.xsd index 8c7cfdbe..86954fbb 100644 --- a/xsd/siri/siri_request_support-v2.0.xsd +++ b/xsd/siri/siri_request_support-v2.0.xsd @@ -140,7 +140,7 @@ Rail transport, Roads and road transport - + Whether additional translations of text names are to be included in elements. If 'false', then only one element should be returned. Default is 'false'. Where multiple values are returned The first element returned will be used as the default value. diff --git a/xsd/siri_stopMonitoring_service.xsd b/xsd/siri_stopMonitoring_service.xsd index dbfbe4b1..a2d309c2 100644 --- a/xsd/siri_stopMonitoring_service.xsd +++ b/xsd/siri_stopMonitoring_service.xsd @@ -228,7 +228,7 @@ Rail transport, Roads and road transport Level of detail to include in response. Default is 'normal'. - + Whether any related SITUATIONs should be included in the ServiceDelivery. Default is 'false'. +SIRI v2.0 @@ -357,7 +357,7 @@ Rail transport, Roads and road transport 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. @@ -874,7 +874,7 @@ If false each subscription response will contain the full information as specifi - Whether a start time other than now can be specified for preview interval. Default is 'truet. + Whether a start time other than now can be specified for preview interval. Default is 'true'. From 9a65f9fb4d42b5f4d5644dc09467d2f722a70843 Mon Sep 17 00:00:00 2001 From: u215619 Date: Mon, 17 Aug 2020 11:01:50 +0200 Subject: [PATCH 181/290] Duration type fixed in default --- xsd/siri_stopMonitoring_service.xsd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xsd/siri_stopMonitoring_service.xsd b/xsd/siri_stopMonitoring_service.xsd index a2d309c2..f227d6a0 100644 --- a/xsd/siri_stopMonitoring_service.xsd +++ b/xsd/siri_stopMonitoring_service.xsd @@ -357,7 +357,7 @@ Rail transport, Roads and road transport 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. From 7c1d53b1e05641f4f26dd8acfc3b8786ddea54ad Mon Sep 17 00:00:00 2001 From: Adrian A Date: Fri, 21 Aug 2020 11:25:04 +0200 Subject: [PATCH 182/290] CR069 cleanup: remove wrong default value/annot. --- xsd/siri_model/siri_situation-v2.0.xsd | 2 +- xsd/siri_stopMonitoring_service.xsd | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/xsd/siri_model/siri_situation-v2.0.xsd b/xsd/siri_model/siri_situation-v2.0.xsd index cdf4e90e..6e1325bc 100644 --- a/xsd/siri_model/siri_situation-v2.0.xsd +++ b/xsd/siri_model/siri_situation-v2.0.xsd @@ -984,7 +984,7 @@ Note: this means that ReasonName is NOT a complete message, but only a (few) wor - Place other than STOP POINTs affected by SITUATION. + STOP PLACE affected by SITUATION. diff --git a/xsd/siri_stopMonitoring_service.xsd b/xsd/siri_stopMonitoring_service.xsd index f227d6a0..4a0a88b9 100644 --- a/xsd/siri_stopMonitoring_service.xsd +++ b/xsd/siri_stopMonitoring_service.xsd @@ -357,7 +357,7 @@ Rail transport, Roads and road transport 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. From 96fb995496f33ca7a14a9a20b319fba3bc7b8995 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Sat, 22 Aug 2020 22:34:29 +0200 Subject: [PATCH 183/290] CR047: update annot. of ValidityPeriod in req/resp --- xsd/siri_productionTimetable_service.xsd | 27 ++++++++++++++++++------ 1 file changed, 21 insertions(+), 6 deletions(-) diff --git a/xsd/siri_productionTimetable_service.xsd b/xsd/siri_productionTimetable_service.xsd index c7bcceb3..ec9ddb64 100644 --- a/xsd/siri_productionTimetable_service.xsd +++ b/xsd/siri_productionTimetable_service.xsd @@ -145,7 +145,15 @@ Rail transport, Roads and road transport - 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. + Start and end of timetable validity (time window) of journeys for which schedules are to be returned by the data producer. If omitted, then the configured data horizon applies. +Since the end of an OPERATING DAY of one ITCS does not usually coincide with the end of another ITCS, it may happen that data cannot be provided for the complete time frame requested by a subscriber. +In order for the data consumer to be aware of this situation, the data producer should confirm - in each returned timetable - for which part of the requested ValidityPeriod he can actually deliver journey schedules. +If the requested period is so far in the past that the data producer does no longer have any data, he should reject the subscription with “Status=false" and a BeyondDataHorizon ErrorCondition. +If the requested period is so far in the future that the data producer does not yet have any data, he will deliver data as soon as it is available. + +A timetable falls inside the ValidityPeriod if all of its journeys fall inside it. +A journey falls inside the ValidityPeriod if the AimedDepartureTime at its first CALL (i.e. at the origin stop) lies between the Start- and EndTime of the ValidityPeriod (regardless of whether the AimedArrivalTime at a subsequent CALL falls ouside of the ValidityPeriod). +Careful: Journeys which themselves fall outside the ValidityPeriod, but which are linked to a journey within the ValidityPeriod by a JOURNEY RELATION, are also regarded as falling inside the ValidityPeriod. Examples are journeys where the vehicle is split or joins with or is replaced by another vehicle. @@ -287,11 +295,18 @@ If false each subscription response will contain the full information as specifi - Start and end of timetable validity (time window) of journeys for which schedules are returned. -Refers to the departure time at the first stop of each VEHICLE JOURNEY If blank the configured data horizon will be used. -The data producer will cover the VALIDITY PERIOD requested by the subscriber as completely as possible, and is encouraged -to include the actually covered time frame in the delivery message in each of the DATED TIMETABLE VERSION FRAMEs. However, -the VALIDITY PERIOD delivered in the response must not exceed the VALIDITY PERIOD requested by the subscriber. +SIRI v2.1 + Start and end of timetable validity (time window) of journeys for which schedules are to be returned by the data producer. +SIRI v2.1 +The ValidityPeriod of the timetable must not exceed the ValidityPeriod requested by the subscriber. +If omitted, then the full - by the subscriber requested - ValidityPeriod or configured data horizon applies. + +Since the end of an OPERATING DAY of one ITCS does not usually coincide with the end of another ITCS, it may happen that data cannot be provided for the complete time frame requested by a subscriber. +In order for the data consumer to be aware of this situation, the data producer should confirm - in each returned timetable - for which part of the requested ValidityPeriod he can actually deliver journey schedules. +If the requested period is so far in the past that the data producer does no longer have any data, he should reject the subscription with “Status=false" and a BeyondDataHorizon ErrorCondition. +If the requested period is so far in the future that the data producer does not yet have any data, he will deliver data as soon as it is available. + +A timetable falls inside the ValidityPeriod if all of its journeys fall inside it. +A journey falls inside the ValidityPeriod if the AimedDepartureTime at its first CALL (i.e. at the origin stop) lies between the Start- and EndTime of the ValidityPeriod (regardless of whether the AimedArrivalTime at a subsequent CALL falls ouside of the ValidityPeriod). +Careful: Journeys which themselves fall outside the ValidityPeriod, but which are linked to a journey within the ValidityPeriod by a JOURNEY RELATION, are also regarded as falling inside the ValidityPeriod. Examples are journeys where the vehicle is split or joins with or is replaced by another vehicle. From 8a20cc9301dca765d7e874f93e60a22db74ae51c Mon Sep 17 00:00:00 2001 From: Travis CI User Date: Mon, 24 Aug 2020 13:09:42 +0000 Subject: [PATCH 184/290] Travis CI update [skip ci] --- .../siri_estimatedVehicleJourney-v2.0.xsd | 15 +++++---------- xsd/siri_model/siri_facility-v2.0.xsd | 1 - xsd/siri_model/siri_journey_support-v2.0.xsd | 12 ++++-------- 3 files changed, 9 insertions(+), 19 deletions(-) diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index 196e22e8..6268dc4b 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -25,24 +25,19 @@ 2005-05-11 - - 2007-04-17 + 2007-04-17 Name Space changes - - 2008-03-26 + 2008-03-26 Add wrapper tag for Line DIRECTION to help binding to Axis - - 2008-11-17 + 2008-11-17 Revise to support substitution groups - - 2011-01-19 + 2011-01-19 Drop use of As Flat Groups for EstimatedCalls - - 2012-03-23 + 2012-03-23 +SIRI v2.0 Factored out of estimatedTimetableService Add EstimatedServiceJourneyInterchange (i.e. Estimated Connection of VEHICLE) to EstimatedTimetableDelivery diff --git a/xsd/siri_model/siri_facility-v2.0.xsd b/xsd/siri_model/siri_facility-v2.0.xsd index 4d59874d..73698598 100644 --- a/xsd/siri_model/siri_facility-v2.0.xsd +++ b/xsd/siri_model/siri_facility-v2.0.xsd @@ -31,7 +31,6 @@ 2012-03-23 -

        SIRI is a European CEN standard for the exchange of real-time information. diff --git a/xsd/siri_model/siri_journey_support-v2.0.xsd b/xsd/siri_model/siri_journey_support-v2.0.xsd index 430ac845..7e485698 100644 --- a/xsd/siri_model/siri_journey_support-v2.0.xsd +++ b/xsd/siri_model/siri_journey_support-v2.0.xsd @@ -23,25 +23,21 @@ 2007-03-29 - - 2008-11-13 + 2008-11-13 Correct Cardinalities on SIRI DESTINATION REF Structure - - 2011-04-18 + 2011-04-18 siri_journey-v2.0.xsd (l.1015). FramedVehicleJourneyRef isn't mandatory in MonitoredCall SIRI-SM answer accourding to CEN TS (prCEN/TS 15531-3:2006 (E) p.56). Make optional. RV ixxx.com - - 2012-03-22 + 2012-03-22 SIRI 2.0 Create from siri_journey Add TrainNumber Add departed, missed states to ProgressStatusEnum (arrivalStatus and DepartureStatus) Add VehicleStatusEnum - - 2013-02-11 + 2013-02-11 SIRI 2.0 Add notExpected state to ProgressStatusEnum Corrected enumeration value cancellled in VehicleStatusEnum From d7004c87a7a48ecd7e06a2c629c149f8f1ccbbb9 Mon Sep 17 00:00:00 2001 From: u215619 Date: Tue, 25 Aug 2020 16:33:33 +0200 Subject: [PATCH 185/290] Default in Language change in SituationElement changed to xsd:language for harmonization Classification/PtConsequenceFilterStructure added for use in PublishingAction --- xsd/siri_model/siri_situation-v2.0.xsd | 36 +++++++++++++- xsd/siri_model/siri_situationActions-v2.0.xsd | 47 ++++++++++++------- .../siri_situationIdentity-v1.1.xsd | 2 +- 3 files changed, 67 insertions(+), 18 deletions(-) diff --git a/xsd/siri_model/siri_situation-v2.0.xsd b/xsd/siri_model/siri_situation-v2.0.xsd index cdf4e90e..fbe3f3bc 100644 --- a/xsd/siri_model/siri_situation-v2.0.xsd +++ b/xsd/siri_model/siri_situation-v2.0.xsd @@ -13,6 +13,7 @@ + @@ -1104,7 +1105,7 @@ Note: this means that ReasonName is NOT a complete message, but only a (few) wor 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. @@ -1234,6 +1235,39 @@ Note: this means that ReasonName is NOT a complete message, but only a (few) wor + + + Filter matching consequences + + + + + Period of effect of disruption, if different from that of SITUATION. + + + + + Classification of effect on service - TPEG Pts43 + + + + + Parts of transport network affected by disruption if different from that of SITUATION. + + + + + Reference to a standard advisory NOTICE to be given to passengers if a particular condition arises. + + + + + Structured classification of advice for passengers in the given SITUATION, from which a standardized message can be generated. + + + + + Type for disruption. diff --git a/xsd/siri_model/siri_situationActions-v2.0.xsd b/xsd/siri_model/siri_situationActions-v2.0.xsd index c94c1bd6..d71631ce 100644 --- a/xsd/siri_model/siri_situationActions-v2.0.xsd +++ b/xsd/siri_model/siri_situationActions-v2.0.xsd @@ -142,22 +142,6 @@ All texts of the passenger information. - - - - - - Structured Reason elements. The TpegReason and/or PublicEventReason enumerated values can be used to generate standardized messages for the current Perspective. If no enumerated values are given, ReasonName is used instead. Note: this means that ReasonName is NOT a complete message, but only a (few) word(s) to be included in the message! - - - - - Structured elements describing the effect of disruption and the advice to passengers. The enumerated values can be used to generate standardized messages for the current Perspective. If no enumerated values are given, the xxxxName is used instead. Note: this means that a xxxxName is NOT a complete message, but only a (few) word(s) to be included in the message! - - - - - @@ -181,6 +165,22 @@ Description of the whole passenger information of one action. + + + + + + + Structured elements describing the effect of disruption and the advice to passengers. The enumerated values can be used to generate standardized messages for the current Perspective. If no enumerated values are given, the xxxxName is used instead. Note: this means that a xxxxName is NOT a complete message, but only a (few) word(s) to be included in the message! + + + + + @@ -299,6 +299,7 @@ + @@ -306,6 +307,20 @@ + + + Action: Publish SITUATION To one or more passenger perspectives. + + + + + Type for Action Publish SITUATION To one or more passenger perspectives. + + + + + + Action: Publish SITUATION To Web. diff --git a/xsd/siri_model/siri_situationIdentity-v1.1.xsd b/xsd/siri_model/siri_situationIdentity-v1.1.xsd index d672fedb..c910282b 100644 --- a/xsd/siri_model/siri_situationIdentity-v1.1.xsd +++ b/xsd/siri_model/siri_situationIdentity-v1.1.xsd @@ -116,7 +116,7 @@ Rail transport, Roads and road transport - Identifier of SITUATION within a Participant. Excldue versionr. + Identifier of SITUATION within a Participant. Exclude versionr. From 16eba1ac83920fcce7f7b7ab6aa3c71eb13b7c5c Mon Sep 17 00:00:00 2001 From: u215619 Date: Tue, 25 Aug 2020 16:50:55 +0200 Subject: [PATCH 186/290] VersionAtt 2.0 upgraded to 2.1 --- xsd/siri.xsd | 8 ++--- xsd/siri/siri_all_framework-v2.0.xsd | 2 +- xsd/siri/siri_base-v2.0.xsd | 6 ++-- xsd/siri/siri_common_services-v2.0.xsd | 4 +-- .../siri_request_errorConditions-v2.0.xsd | 2 +- xsd/siri/siri_request_support-v2.0.xsd | 2 +- xsd/siri/siri_requests-v2.0.xsd | 4 +-- xsd/siriSg.xsd | 4 +-- xsd/siri_all_functionalServices.xsd | 2 +- xsd/siri_connectionMonitoring_service.xsd | 10 +++--- xsd/siri_connectionTimetable_service.xsd | 8 ++--- xsd/siri_discovery.xsd | 34 +++++++++---------- xsd/siri_estimatedTimetable_service.xsd | 8 ++--- xsd/siri_facilityMonitoring_service.xsd | 8 ++--- xsd/siri_generalMessage_service.xsd | 8 ++--- xsd/siri_model/siri_all-v2.0.xsd | 2 +- xsd/siri_model/siri_all_journeyModel-v2.0.xsd | 2 +- xsd/siri_model/siri_all_model-v2.0.xsd | 2 +- xsd/siri_model/siri_all_situation-v2.0.xsd | 2 +- .../siri_datedVehicleJourney-v2.0.xsd | 2 +- .../siri_estimatedVehicleJourney-v2.0.xsd | 2 +- xsd/siri_model/siri_facility-v2.0.xsd | 2 +- xsd/siri_model/siri_feature_support-v2.0.xsd | 2 +- .../siri_interchangeJourney-v2.0.xsd | 2 +- xsd/siri_model/siri_journey-v2.0.xsd | 2 +- xsd/siri_model/siri_journey_support-v2.0.xsd | 2 +- xsd/siri_model/siri_modelPermissions-v2.0.xsd | 2 +- .../siri_monitoredVehicleJourney-v2.0.xsd | 2 +- xsd/siri_model/siri_operator_support-v2.0.xsd | 2 +- xsd/siri_model/siri_reference-v2.0.xsd | 2 +- xsd/siri_model/siri_situationActions-v2.0.xsd | 2 +- xsd/siri_model/siri_situationAffects-v2.0.xsd | 2 +- xsd/siri_model/siri_situationReasons-v2.0.xsd | 2 +- .../siri_targetedVehicleJourney-v2.0.xsd | 2 +- xsd/siri_model/siri_time-v2.0.xsd | 2 +- .../siri_connectionLink-v2.0.xsd | 2 +- .../siri_feature-v2.0.xsd | 2 +- .../siri_infoChannel-v2.0.xsd | 2 +- xsd/siri_model_discovery/siri_line-v2.0.xsd | 2 +- .../siri_stopPoint-v2.0.xsd | 2 +- xsd/siri_productionTimetable_service.xsd | 8 ++--- xsd/siri_situationExchange_service.xsd | 8 ++--- xsd/siri_stopTimetable_service.xsd | 8 ++--- xsd/siri_utility/siri_all_utility-v2.0.xsd | 2 +- xsd/siri_utility/siri_location-v2.0.xsd | 2 +- xsd/siri_utility/siri_permissions-v2.0.xsd | 2 +- xsd/siri_vehicleMonitoring_service.xsd | 8 ++--- .../siri_estimatedVehicleJourney-v2.0.xsd | 2 +- xsd/zrescue/siri_situation-v2.0.xsd | 2 +- xsd/zrescue/siri_situationAffects-v2.0.xsd | 2 +- 50 files changed, 102 insertions(+), 102 deletions(-) diff --git a/xsd/siri.xsd b/xsd/siri.xsd index aabc549a..7eb08e0a 100644 --- a/xsd/siri.xsd +++ b/xsd/siri.xsd @@ -1,6 +1,6 @@ - + @@ -169,7 +169,7 @@ Rail transport, Roads and road transport. - + @@ -471,7 +471,7 @@ Rail transport, Roads and road transport. - + @@ -507,7 +507,7 @@ Rail transport, Roads and road transport. - + diff --git a/xsd/siri/siri_all_framework-v2.0.xsd b/xsd/siri/siri_all_framework-v2.0.xsd index dbc9c58a..b6fdc86a 100644 --- a/xsd/siri/siri_all_framework-v2.0.xsd +++ b/xsd/siri/siri_all_framework-v2.0.xsd @@ -3,7 +3,7 @@ (C) Copyright CEN 2004-2012 --> - + diff --git a/xsd/siri/siri_base-v2.0.xsd b/xsd/siri/siri_base-v2.0.xsd index cd5618dc..dab8e566 100644 --- a/xsd/siri/siri_base-v2.0.xsd +++ b/xsd/siri/siri_base-v2.0.xsd @@ -1,5 +1,5 @@ - + @@ -94,7 +94,7 @@ Rail transport, Roads and road transport. - + @@ -290,7 +290,7 @@ Rail transport, Roads and road transport. - + diff --git a/xsd/siri/siri_common_services-v2.0.xsd b/xsd/siri/siri_common_services-v2.0.xsd index 03bf39d1..f2e94174 100644 --- a/xsd/siri/siri_common_services-v2.0.xsd +++ b/xsd/siri/siri_common_services-v2.0.xsd @@ -1,6 +1,6 @@ - + @@ -767,7 +767,7 @@ Rail transport, Roads and road transport - + Version number of request. diff --git a/xsd/siri/siri_request_errorConditions-v2.0.xsd b/xsd/siri/siri_request_errorConditions-v2.0.xsd index 1d86d135..ea6690a3 100644 --- a/xsd/siri/siri_request_errorConditions-v2.0.xsd +++ b/xsd/siri/siri_request_errorConditions-v2.0.xsd @@ -1,6 +1,6 @@ - + diff --git a/xsd/siri/siri_request_support-v2.0.xsd b/xsd/siri/siri_request_support-v2.0.xsd index 86954fbb..0ab402b9 100644 --- a/xsd/siri/siri_request_support-v2.0.xsd +++ b/xsd/siri/siri_request_support-v2.0.xsd @@ -1,5 +1,5 @@ - + diff --git a/xsd/siri/siri_requests-v2.0.xsd b/xsd/siri/siri_requests-v2.0.xsd index d78a5a6c..c105fa12 100644 --- a/xsd/siri/siri_requests-v2.0.xsd +++ b/xsd/siri/siri_requests-v2.0.xsd @@ -1,5 +1,5 @@ - + @@ -836,7 +836,7 @@ - + Version number of request. Fixed. diff --git a/xsd/siriSg.xsd b/xsd/siriSg.xsd index 6506889d..6f5f57f0 100644 --- a/xsd/siriSg.xsd +++ b/xsd/siriSg.xsd @@ -1,6 +1,6 @@ - + @@ -143,7 +143,7 @@ Rail transport, Roads and road transport. - + diff --git a/xsd/siri_all_functionalServices.xsd b/xsd/siri_all_functionalServices.xsd index 03ec58ec..7d87f2b6 100644 --- a/xsd/siri_all_functionalServices.xsd +++ b/xsd/siri_all_functionalServices.xsd @@ -1,5 +1,5 @@ - + diff --git a/xsd/siri_connectionMonitoring_service.xsd b/xsd/siri_connectionMonitoring_service.xsd index a9adeb70..6fcbc248 100644 --- a/xsd/siri_connectionMonitoring_service.xsd +++ b/xsd/siri_connectionMonitoring_service.xsd @@ -1,6 +1,6 @@ - + @@ -134,7 +134,7 @@ Rail transport, Roads and road transport - + Version number of request. Fixed @@ -311,7 +311,7 @@ Rail transport, Roads and road transport - + Version number of response. Fixed @@ -430,7 +430,7 @@ Rail transport, Roads and road transport - + Version number of response. Fixed @@ -621,7 +621,7 @@ Rail transport, Roads and road transport - + Version number of response. Fixed diff --git a/xsd/siri_connectionTimetable_service.xsd b/xsd/siri_connectionTimetable_service.xsd index 91db75d5..be458b25 100644 --- a/xsd/siri_connectionTimetable_service.xsd +++ b/xsd/siri_connectionTimetable_service.xsd @@ -1,5 +1,5 @@ - + @@ -154,7 +154,7 @@ Rail transport, Roads and road transport - + Version number of request. Fixed @@ -218,7 +218,7 @@ Rail transport, Roads and road transport - + Version number of response. Fixed @@ -395,7 +395,7 @@ Rail transport, Roads and road transport - + Version number of response. Fixed diff --git a/xsd/siri_discovery.xsd b/xsd/siri_discovery.xsd index 2ca4f717..d904b971 100644 --- a/xsd/siri_discovery.xsd +++ b/xsd/siri_discovery.xsd @@ -1,6 +1,6 @@ - + @@ -187,7 +187,7 @@ Rail transport, Roads and road transport - + Version number of request. Fixed @@ -285,7 +285,7 @@ Rail transport, Roads and road transport - + Version number of response. Fixed @@ -312,7 +312,7 @@ Rail transport, Roads and road transport - + Version number of request. Fixed @@ -413,7 +413,7 @@ Rail transport, Roads and road transport - + Version number of response. Fixed. @@ -438,7 +438,7 @@ Rail transport, Roads and road transport - + Version number of request. Fixed @@ -475,7 +475,7 @@ Rail transport, Roads and road transport - + Version number of response. Fixed. @@ -500,7 +500,7 @@ Rail transport, Roads and road transport - + Version number of request. Fixed @@ -537,7 +537,7 @@ Rail transport, Roads and road transport - + Version number of response. Fixed. @@ -561,7 +561,7 @@ Rail transport, Roads and road transport - + Version number of request. Fixed @@ -586,7 +586,7 @@ Rail transport, Roads and road transport - + Version number of response. Fixed. @@ -612,7 +612,7 @@ Rail transport, Roads and road transport - + Version number of request. Fixed @@ -709,7 +709,7 @@ Rail transport, Roads and road transport - + Version number of response. Fixed. @@ -739,7 +739,7 @@ Rail transport, Roads and road transport - + Version number of request. Fixed @@ -763,7 +763,7 @@ Rail transport, Roads and road transport - + Version number of response. Fixed. @@ -789,7 +789,7 @@ Rail transport, Roads and road transport - + Version number of request. Fixed @@ -888,7 +888,7 @@ Rail transport, Roads and road transport - + Version number of response. Fixed. diff --git a/xsd/siri_estimatedTimetable_service.xsd b/xsd/siri_estimatedTimetable_service.xsd index 57730fdf..91781e39 100644 --- a/xsd/siri_estimatedTimetable_service.xsd +++ b/xsd/siri_estimatedTimetable_service.xsd @@ -1,6 +1,6 @@ - + @@ -125,7 +125,7 @@ Rail transport, Roads and road transport - + Version number of request. Fixed @@ -314,7 +314,7 @@ The server will automatically proceed with 'false' if capability is not supporte - + Version number of response. Fixed @@ -388,7 +388,7 @@ The server will automatically proceed with 'false' if capability is not supporte - + diff --git a/xsd/siri_facilityMonitoring_service.xsd b/xsd/siri_facilityMonitoring_service.xsd index a2fad698..3899f417 100644 --- a/xsd/siri_facilityMonitoring_service.xsd +++ b/xsd/siri_facilityMonitoring_service.xsd @@ -1,5 +1,5 @@ - + @@ -118,7 +118,7 @@ Rail transport, Roads and road transport - + Version number of request. Fixed @@ -281,7 +281,7 @@ If false or omitted, each subscription response will contain the full informatio - + Version number of response. Fixed @@ -334,7 +334,7 @@ If false or omitted, each subscription response will contain the full informatio - + Version number of response. Fixed diff --git a/xsd/siri_generalMessage_service.xsd b/xsd/siri_generalMessage_service.xsd index d2383ef3..ce4a917b 100644 --- a/xsd/siri_generalMessage_service.xsd +++ b/xsd/siri_generalMessage_service.xsd @@ -1,5 +1,5 @@ - + @@ -122,7 +122,7 @@ Rail transport, Roads and road transport - + Version number of request. Fixed @@ -199,7 +199,7 @@ Rail transport, Roads and road transport - + Version number of response. Fixed @@ -347,7 +347,7 @@ Rail transport, Roads and road transport - + Version number of response. Fixed diff --git a/xsd/siri_model/siri_all-v2.0.xsd b/xsd/siri_model/siri_all-v2.0.xsd index 23d4b928..a3368be3 100644 --- a/xsd/siri_model/siri_all-v2.0.xsd +++ b/xsd/siri_model/siri_all-v2.0.xsd @@ -3,7 +3,7 @@ (C) Copyright CEN 2004-2012 --> - + diff --git a/xsd/siri_model/siri_all_journeyModel-v2.0.xsd b/xsd/siri_model/siri_all_journeyModel-v2.0.xsd index 665b5b9a..ce10bcde 100644 --- a/xsd/siri_model/siri_all_journeyModel-v2.0.xsd +++ b/xsd/siri_model/siri_all_journeyModel-v2.0.xsd @@ -3,7 +3,7 @@ (C) Copyright CEN 2004-2012 --> - + diff --git a/xsd/siri_model/siri_all_model-v2.0.xsd b/xsd/siri_model/siri_all_model-v2.0.xsd index b1fbec30..fc98f55d 100644 --- a/xsd/siri_model/siri_all_model-v2.0.xsd +++ b/xsd/siri_model/siri_all_model-v2.0.xsd @@ -3,7 +3,7 @@ (C) Copyright CEN 2004-2012 --> - + diff --git a/xsd/siri_model/siri_all_situation-v2.0.xsd b/xsd/siri_model/siri_all_situation-v2.0.xsd index 9af6522b..d2c37627 100644 --- a/xsd/siri_model/siri_all_situation-v2.0.xsd +++ b/xsd/siri_model/siri_all_situation-v2.0.xsd @@ -3,7 +3,7 @@ Copyright CEN 2004-2012 --> - + diff --git a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd index 0c65d553..e72fb70a 100644 --- a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd @@ -1,6 +1,6 @@ - + diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index 02d58710..8f4db506 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -1,6 +1,6 @@ - + diff --git a/xsd/siri_model/siri_facility-v2.0.xsd b/xsd/siri_model/siri_facility-v2.0.xsd index 73698598..3b78401f 100644 --- a/xsd/siri_model/siri_facility-v2.0.xsd +++ b/xsd/siri_model/siri_facility-v2.0.xsd @@ -1,5 +1,5 @@ - + diff --git a/xsd/siri_model/siri_feature_support-v2.0.xsd b/xsd/siri_model/siri_feature_support-v2.0.xsd index 2701f3f8..3ae65c92 100644 --- a/xsd/siri_model/siri_feature_support-v2.0.xsd +++ b/xsd/siri_model/siri_feature_support-v2.0.xsd @@ -1,5 +1,5 @@ - + diff --git a/xsd/siri_model/siri_interchangeJourney-v2.0.xsd b/xsd/siri_model/siri_interchangeJourney-v2.0.xsd index 51a75eeb..895d1405 100644 --- a/xsd/siri_model/siri_interchangeJourney-v2.0.xsd +++ b/xsd/siri_model/siri_interchangeJourney-v2.0.xsd @@ -1,5 +1,5 @@ - + diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index f94d3bf4..6751cda1 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -1,6 +1,6 @@ - + diff --git a/xsd/siri_model/siri_journey_support-v2.0.xsd b/xsd/siri_model/siri_journey_support-v2.0.xsd index e20f297c..b40fcb52 100644 --- a/xsd/siri_model/siri_journey_support-v2.0.xsd +++ b/xsd/siri_model/siri_journey_support-v2.0.xsd @@ -1,5 +1,5 @@ - + diff --git a/xsd/siri_model/siri_modelPermissions-v2.0.xsd b/xsd/siri_model/siri_modelPermissions-v2.0.xsd index 88dda23c..e83c27c5 100644 --- a/xsd/siri_model/siri_modelPermissions-v2.0.xsd +++ b/xsd/siri_model/siri_modelPermissions-v2.0.xsd @@ -1,5 +1,5 @@ - + diff --git a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd index 278e8dc4..9d4fd026 100644 --- a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd @@ -1,5 +1,5 @@ - + diff --git a/xsd/siri_model/siri_operator_support-v2.0.xsd b/xsd/siri_model/siri_operator_support-v2.0.xsd index 01ad5a84..196746f2 100644 --- a/xsd/siri_model/siri_operator_support-v2.0.xsd +++ b/xsd/siri_model/siri_operator_support-v2.0.xsd @@ -1,5 +1,5 @@ - + diff --git a/xsd/siri_model/siri_reference-v2.0.xsd b/xsd/siri_model/siri_reference-v2.0.xsd index da20ab6c..3c49588f 100644 --- a/xsd/siri_model/siri_reference-v2.0.xsd +++ b/xsd/siri_model/siri_reference-v2.0.xsd @@ -1,5 +1,5 @@ - + diff --git a/xsd/siri_model/siri_situationActions-v2.0.xsd b/xsd/siri_model/siri_situationActions-v2.0.xsd index d71631ce..05db374a 100644 --- a/xsd/siri_model/siri_situationActions-v2.0.xsd +++ b/xsd/siri_model/siri_situationActions-v2.0.xsd @@ -1,5 +1,5 @@ - + diff --git a/xsd/siri_model/siri_situationAffects-v2.0.xsd b/xsd/siri_model/siri_situationAffects-v2.0.xsd index 747ac04e..98147b1a 100644 --- a/xsd/siri_model/siri_situationAffects-v2.0.xsd +++ b/xsd/siri_model/siri_situationAffects-v2.0.xsd @@ -1,5 +1,5 @@ - + diff --git a/xsd/siri_model/siri_situationReasons-v2.0.xsd b/xsd/siri_model/siri_situationReasons-v2.0.xsd index 70e9f006..c28f6037 100644 --- a/xsd/siri_model/siri_situationReasons-v2.0.xsd +++ b/xsd/siri_model/siri_situationReasons-v2.0.xsd @@ -1,5 +1,5 @@ - + diff --git a/xsd/siri_model/siri_targetedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_targetedVehicleJourney-v2.0.xsd index 1ea55267..fe50c4ce 100644 --- a/xsd/siri_model/siri_targetedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_targetedVehicleJourney-v2.0.xsd @@ -1,5 +1,5 @@ - + diff --git a/xsd/siri_model/siri_time-v2.0.xsd b/xsd/siri_model/siri_time-v2.0.xsd index 10652a4b..1dd1ba1c 100644 --- a/xsd/siri_model/siri_time-v2.0.xsd +++ b/xsd/siri_model/siri_time-v2.0.xsd @@ -1,5 +1,5 @@ - + diff --git a/xsd/siri_model_discovery/siri_connectionLink-v2.0.xsd b/xsd/siri_model_discovery/siri_connectionLink-v2.0.xsd index 03896aed..b71d2855 100644 --- a/xsd/siri_model_discovery/siri_connectionLink-v2.0.xsd +++ b/xsd/siri_model_discovery/siri_connectionLink-v2.0.xsd @@ -1,5 +1,5 @@ - + diff --git a/xsd/siri_model_discovery/siri_feature-v2.0.xsd b/xsd/siri_model_discovery/siri_feature-v2.0.xsd index 30fb1e89..d5c00b55 100644 --- a/xsd/siri_model_discovery/siri_feature-v2.0.xsd +++ b/xsd/siri_model_discovery/siri_feature-v2.0.xsd @@ -1,5 +1,5 @@ - + diff --git a/xsd/siri_model_discovery/siri_infoChannel-v2.0.xsd b/xsd/siri_model_discovery/siri_infoChannel-v2.0.xsd index 63d1f0ec..1d34250b 100644 --- a/xsd/siri_model_discovery/siri_infoChannel-v2.0.xsd +++ b/xsd/siri_model_discovery/siri_infoChannel-v2.0.xsd @@ -1,5 +1,5 @@ - + diff --git a/xsd/siri_model_discovery/siri_line-v2.0.xsd b/xsd/siri_model_discovery/siri_line-v2.0.xsd index 581c822b..4d005d7c 100644 --- a/xsd/siri_model_discovery/siri_line-v2.0.xsd +++ b/xsd/siri_model_discovery/siri_line-v2.0.xsd @@ -1,5 +1,5 @@ - + diff --git a/xsd/siri_model_discovery/siri_stopPoint-v2.0.xsd b/xsd/siri_model_discovery/siri_stopPoint-v2.0.xsd index 25ea7814..e9d6bc24 100644 --- a/xsd/siri_model_discovery/siri_stopPoint-v2.0.xsd +++ b/xsd/siri_model_discovery/siri_stopPoint-v2.0.xsd @@ -1,5 +1,5 @@ - + diff --git a/xsd/siri_productionTimetable_service.xsd b/xsd/siri_productionTimetable_service.xsd index b9873a50..07a90247 100644 --- a/xsd/siri_productionTimetable_service.xsd +++ b/xsd/siri_productionTimetable_service.xsd @@ -1,5 +1,5 @@ - + @@ -147,7 +147,7 @@ Rail transport, Roads and road transport - + Version number of request. Fixed. @@ -294,7 +294,7 @@ If false each subscription response will contain the full information as specifi - + Version number of response. fixed. @@ -395,7 +395,7 @@ It is strongly advised to only use this feature in cases where an interchange wa - + Version number of response. fixed. diff --git a/xsd/siri_situationExchange_service.xsd b/xsd/siri_situationExchange_service.xsd index a72374c0..0998104b 100644 --- a/xsd/siri_situationExchange_service.xsd +++ b/xsd/siri_situationExchange_service.xsd @@ -1,6 +1,6 @@ - + @@ -157,7 +157,7 @@ Rail transport, Roads and road transport - + Version number of request. Fixed @@ -519,7 +519,7 @@ If false or omitted, each subscription response will contain the full informatio - + Version number of response. Fixed @@ -627,7 +627,7 @@ If false or omitted, each subscription response will contain the full informatio - + Version number of response. Fixed diff --git a/xsd/siri_stopTimetable_service.xsd b/xsd/siri_stopTimetable_service.xsd index 79662e9d..a34833d4 100644 --- a/xsd/siri_stopTimetable_service.xsd +++ b/xsd/siri_stopTimetable_service.xsd @@ -1,5 +1,5 @@ - + @@ -122,7 +122,7 @@ Rail transport, Roads and road transport - + Version number of request. Fixed @@ -226,7 +226,7 @@ If false each subscription response will contain the full information as specifi - + Version number of response. Fixed @@ -331,7 +331,7 @@ If false each subscription response will contain the full information as specifi - + Version number of response. Fixed diff --git a/xsd/siri_utility/siri_all_utility-v2.0.xsd b/xsd/siri_utility/siri_all_utility-v2.0.xsd index 9e7721dc..9d8131a0 100644 --- a/xsd/siri_utility/siri_all_utility-v2.0.xsd +++ b/xsd/siri_utility/siri_all_utility-v2.0.xsd @@ -3,7 +3,7 @@ Copyright CEN 2004-2012 --> - + diff --git a/xsd/siri_utility/siri_location-v2.0.xsd b/xsd/siri_utility/siri_location-v2.0.xsd index 912cc6c6..af8b3075 100644 --- a/xsd/siri_utility/siri_location-v2.0.xsd +++ b/xsd/siri_utility/siri_location-v2.0.xsd @@ -1,5 +1,5 @@ - + diff --git a/xsd/siri_utility/siri_permissions-v2.0.xsd b/xsd/siri_utility/siri_permissions-v2.0.xsd index c41d6931..bb997e8e 100644 --- a/xsd/siri_utility/siri_permissions-v2.0.xsd +++ b/xsd/siri_utility/siri_permissions-v2.0.xsd @@ -1,5 +1,5 @@ - + diff --git a/xsd/siri_vehicleMonitoring_service.xsd b/xsd/siri_vehicleMonitoring_service.xsd index c9e42cf6..2b4f31e9 100644 --- a/xsd/siri_vehicleMonitoring_service.xsd +++ b/xsd/siri_vehicleMonitoring_service.xsd @@ -1,5 +1,5 @@ - + @@ -136,7 +136,7 @@ Rail transport, Roads and road transport - + Version number of request. Fixed @@ -332,7 +332,7 @@ If false or omitted, each subscription response will contain the full informatio - + Version number of response. Fixed @@ -499,7 +499,7 @@ If false or omitted, each subscription response will contain the full informatio - + Version number of response. Fixed diff --git a/xsd/zrescue/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/zrescue/siri_estimatedVehicleJourney-v2.0.xsd index ed39ce1e..5065f697 100644 --- a/xsd/zrescue/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/zrescue/siri_estimatedVehicleJourney-v2.0.xsd @@ -1,6 +1,6 @@ - + diff --git a/xsd/zrescue/siri_situation-v2.0.xsd b/xsd/zrescue/siri_situation-v2.0.xsd index 8913928f..38e2ef2f 100644 --- a/xsd/zrescue/siri_situation-v2.0.xsd +++ b/xsd/zrescue/siri_situation-v2.0.xsd @@ -1,5 +1,5 @@ - + diff --git a/xsd/zrescue/siri_situationAffects-v2.0.xsd b/xsd/zrescue/siri_situationAffects-v2.0.xsd index c4ee9eff..032a7463 100644 --- a/xsd/zrescue/siri_situationAffects-v2.0.xsd +++ b/xsd/zrescue/siri_situationAffects-v2.0.xsd @@ -1,5 +1,5 @@ - + From ec0edb13acee8e345367120102968484d15e0d93 Mon Sep 17 00:00:00 2001 From: u215619 Date: Tue, 25 Aug 2020 16:52:08 +0200 Subject: [PATCH 187/290] VersionAtt 2.0 upgraded to 2.1 --- xsd/siri_model/siri_situation-v2.0.xsd | 2 +- xsd/siri_stopMonitoring_service.xsd | 10 +++++----- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/xsd/siri_model/siri_situation-v2.0.xsd b/xsd/siri_model/siri_situation-v2.0.xsd index 825e153d..6c882101 100644 --- a/xsd/siri_model/siri_situation-v2.0.xsd +++ b/xsd/siri_model/siri_situation-v2.0.xsd @@ -1,6 +1,6 @@ - + diff --git a/xsd/siri_stopMonitoring_service.xsd b/xsd/siri_stopMonitoring_service.xsd index 4a0a88b9..b093e269 100644 --- a/xsd/siri_stopMonitoring_service.xsd +++ b/xsd/siri_stopMonitoring_service.xsd @@ -1,6 +1,6 @@ - + @@ -299,7 +299,7 @@ Rail transport, Roads and road transport - + Version number of request. @@ -326,7 +326,7 @@ Rail transport, Roads and road transport - + @@ -408,7 +408,7 @@ If false each subscription response will contain the full information as specifi - + Version number of response. Fixed @@ -840,7 +840,7 @@ If false each subscription response will contain the full information as specifi - + Version number of response. Fixed From d98b9c92f5376aea02b01c5b6ab4d7e7af10c3bd Mon Sep 17 00:00:00 2001 From: u215619 Date: Wed, 26 Aug 2020 14:03:24 +0200 Subject: [PATCH 188/290] PublicationScope optional for legacy issues --- xsd/siri_model/siri_situationActions-v2.0.xsd | 32 +++++++++---------- 1 file changed, 16 insertions(+), 16 deletions(-) diff --git a/xsd/siri_model/siri_situationActions-v2.0.xsd b/xsd/siri_model/siri_situationActions-v2.0.xsd index 05db374a..7d73d7cb 100644 --- a/xsd/siri_model/siri_situationActions-v2.0.xsd +++ b/xsd/siri_model/siri_situationActions-v2.0.xsd @@ -281,7 +281,7 @@ Display prompt for presenting action to user. (Unbounded since SIRI 2.0) - + Defines the information area where the action has to be published. @@ -299,7 +299,7 @@ - + @@ -307,20 +307,20 @@ - - - Action: Publish SITUATION To one or more passenger perspectives. - - - - - Type for Action Publish SITUATION To one or more passenger perspectives. - - - - - - + + + Action: Publish SITUATION To one or more passenger perspectives. + + + + + Type for Action Publish SITUATION To one or more passenger perspectives. + + + + + + Action: Publish SITUATION To Web. From ce2a9a0fa3f7fdbf4a4ffefba7b3eca14632781c Mon Sep 17 00:00:00 2001 From: Christophe Duquesne Date: Wed, 26 Aug 2020 17:29:16 +0200 Subject: [PATCH 189/290] SIRI FM - Site filter addition Complement to CR71 to be able to filter by Site in SIRI FM (SITE generalisation was introduced by Transmodel after the definition of SIRI FM, and only STOP PLACE and STOP PLACE COMPONENT were the only SITE related available filters at that time). --- xsd/siri_facilityMonitoring_service.xsd | 5 +++++ xsd/siri_model/siri_reference-v2.0.xsd | 19 +++++++++++++++++++ 2 files changed, 24 insertions(+) diff --git a/xsd/siri_facilityMonitoring_service.xsd b/xsd/siri_facilityMonitoring_service.xsd index 8e70d606..ee0ff5b6 100644 --- a/xsd/siri_facilityMonitoring_service.xsd +++ b/xsd/siri_facilityMonitoring_service.xsd @@ -199,6 +199,11 @@ Rail transport, Roads and road transport Reference to a stop place component. + + + Reference to a Site. + + diff --git a/xsd/siri_model/siri_reference-v2.0.xsd b/xsd/siri_model/siri_reference-v2.0.xsd index da20ab6c..92405115 100644 --- a/xsd/siri_model/siri_reference-v2.0.xsd +++ b/xsd/siri_model/siri_reference-v2.0.xsd @@ -792,4 +792,23 @@ Values for these elements can be specified on an annual schedule and will be inh + + + Identifier of a SITE + + + + + + Reference to a SITE + + + + + + + + Reference to a SITE + + From cd383b84b78258f640f45ceca574f94ea181a56d Mon Sep 17 00:00:00 2001 From: Christophe Duquesne Date: Wed, 26 Aug 2020 18:23:36 +0200 Subject: [PATCH 190/290] Alignment with the SIRI FM documentation FeatureRef is now unbounded to be compliant with the SIRI FM documentation --- xsd/siri_facilityMonitoring_service.xsd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xsd/siri_facilityMonitoring_service.xsd b/xsd/siri_facilityMonitoring_service.xsd index ee0ff5b6..9871a05f 100644 --- a/xsd/siri_facilityMonitoring_service.xsd +++ b/xsd/siri_facilityMonitoring_service.xsd @@ -172,7 +172,7 @@ Rail transport, Roads and road transport - + From ed11afe9cd5ddbfe2c6b856b06741d89cbf5215e Mon Sep 17 00:00:00 2001 From: u215619 Date: Fri, 28 Aug 2020 11:16:44 +0200 Subject: [PATCH 191/290] Cleanup routepointtype --- .../siri_situationServiceTypes-v1.0.xsd | 107 +++++++++--------- 1 file changed, 56 insertions(+), 51 deletions(-) diff --git a/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd b/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd index a0413182..4c17220a 100644 --- a/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd +++ b/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd @@ -439,11 +439,6 @@ TPEG Pti15_0, PTS044_0 unknown - - - TPEG Pti15_1, start point
        Deprecated since SIRI v2.1. Use the PTS value 'origin' (PTS044_1) instead.         -         -         TPEG PTS044_1, origin @@ -454,19 +449,64 @@ TPEG Pti15_2, PTS044_2 destination - + - TPEG Pti15_3, stop + TPEG PTS044_3, intermediate. - + + + PTS044_4, leg board + + + - TPEG Pti15_4, via
        Deprecated since SIRI v2.1. Use the PTS value 'intermediate' (PTS044_3) instead.         + PTS044_5, leg intermediate         - + - TPEG PTS044_3, intermediate. + PTS044_6, leg alight + + + + + TPEG PTS044_7, first route point + + + + + TPEG PTS044_8, last route point + + + + + PTS044_9, affected stop place + + + + + PTS044_10, presented stop place + + + + + PTS044_255, undefined stop place usage
        Deprecated since SIRI v2.1. Use the PTS value 'undefined' instead.         +         +         + + + TPEG Pti15_1, start point
        Deprecated since SIRI v2.1. Use the PTS value 'origin' (PTS044_1) instead.         +         +         + + + TPEG Pti15_3, stop + + + + + TPEG Pti15_4, via @@ -521,57 +561,22 @@ - TPEG Pti15_15, altered start point
        Deprecated since SIRI v2.1. Use the PTS value 'firstRoutePoint' (PTS044_7) instead.         -         -         - - - TPEG PTS044_7, first route point + TPEG Pti15_15, altered start point - TPEG Pti15_16, altered destination
        Deprecated since SIRI v2.1. Use the PTS value 'lastRoutePoint' (PTS044_8) instead.         -         -         - - - TPEG PTS044_8, last route point + TPEG Pti15_16, altered destination - TPEG Pti15_255, undefined route point - - - - - PTS044_4, leg board - - - - - PTS044_5, leg intermediate - - - - - PTS044_6, leg alight - - - - - PTS044_9, affected stop place - - - - - PTS044_10, presented stop place + TPEG Pti15_255, undefined route point
        Deprecated since SIRI v2.1. Use the PTS value 'undefined' instead.                 - + - PTS044_255, undefined stop place usage + TPEG Pti15_255, PTS044_255 undefined From d49041b2f0f01fc15b69776d1658cdd272732437 Mon Sep 17 00:00:00 2001 From: Christophe Duquesne Date: Fri, 28 Aug 2020 18:34:18 +0200 Subject: [PATCH 192/290] Update lost in previous commit from CR71 Facility Class Update lost in previous commit from CR71 (addition of some enum values) --- xsd/siri_model/siri_facility-v2.0.xsd | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/xsd/siri_model/siri_facility-v2.0.xsd b/xsd/siri_model/siri_facility-v2.0.xsd index 4d59874d..9ba23c67 100644 --- a/xsd/siri_model/siri_facility-v2.0.xsd +++ b/xsd/siri_model/siri_facility-v2.0.xsd @@ -245,9 +245,14 @@ Rail transport, Roads and road transport + + + + + From 0cd6f82fb2b65ad1f0630b4088a469a858105047 Mon Sep 17 00:00:00 2001 From: u215619 Date: Fri, 28 Aug 2020 21:19:50 +0200 Subject: [PATCH 193/290] Extended Classification structure as discussed in basecamp https://3.basecamp.com/3256016/buckets/9672657/messages/2949095046#__recording_2970472161 --- xsd/siri_model/siri_situation-v2.0.xsd | 18 ++++------ xsd/siri_model/siri_situationActions-v2.0.xsd | 34 +++++++++---------- 2 files changed, 24 insertions(+), 28 deletions(-) diff --git a/xsd/siri_model/siri_situation-v2.0.xsd b/xsd/siri_model/siri_situation-v2.0.xsd index 6c882101..20af1d3e 100644 --- a/xsd/siri_model/siri_situation-v2.0.xsd +++ b/xsd/siri_model/siri_situation-v2.0.xsd @@ -1237,7 +1237,7 @@ Note: this means that ReasonName is NOT a complete message, but only a (few) wor - Filter matching consequences + Filter for matching consequences. Can be used to construct generated messages. @@ -1245,26 +1245,22 @@ Note: this means that ReasonName is NOT a complete message, but only a (few) wor Period of effect of disruption, if different from that of SITUATION.         - + - Classification of effect on service - TPEG Pts43 + Condition(s) of effect of disruptione. - +         Parts of transport network affected by disruption if different from that of SITUATION. - - - Reference to a standard advisory NOTICE to be given to passengers if a particular condition arises. - - - + - Structured classification of advice for passengers in the given SITUATION, from which a standardized message can be generated. + Advice to passengers. + diff --git a/xsd/siri_model/siri_situationActions-v2.0.xsd b/xsd/siri_model/siri_situationActions-v2.0.xsd index 7d73d7cb..eca3d02a 100644 --- a/xsd/siri_model/siri_situationActions-v2.0.xsd +++ b/xsd/siri_model/siri_situationActions-v2.0.xsd @@ -142,6 +142,22 @@ All texts of the passenger information.         + + + + + + Structured Reason elements. The TpegReason and/or PublicEventReason enumerated values can be used to generate standardized messages for the current Perspective. If no enumerated values are given, ReasonName is used instead. Note: this means that ReasonName is NOT a complete message, but only a (few) word(s) to be included in the message! + + + + + Filter for matching consequences. Can be used to construct generated messages. + + + + + @@ -165,22 +181,6 @@ Description of the whole passenger information of one action.         - - - - - - - Structured elements describing the effect of disruption and the advice to passengers. The enumerated values can be used to generate standardized messages for the current Perspective. If no enumerated values are given, the xxxxName is used instead. Note: this means that a xxxxName is NOT a complete message, but only a (few) word(s) to be included in the message! - - - - - @@ -661,7 +661,7 @@ - Class of size, e.g. L (large), M (medium), S (small) + Class of size, e.g. L (large), M (medium), S (small).
        If text length for a class size varies on perspective and a PassengerInformationAction applies to several perspectives, take the smallest class                 From 0693e5049346bdb14a5bee3a3bd57446f45dcbcc Mon Sep 17 00:00:00 2001 From: u215619 Date: Fri, 28 Aug 2020 21:34:46 +0200 Subject: [PATCH 194/290] Changed the type "SelectedRoutes" as a list of AffectedRoutes in AffectedNetwork. See discussion https://3.basecamp.com/3256016/buckets/9672657/messages/2804978374 --- xsd/siri_model/siri_situationAffects-v2.0.xsd | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/xsd/siri_model/siri_situationAffects-v2.0.xsd b/xsd/siri_model/siri_situationAffects-v2.0.xsd index a5ba355c..7f8637f9 100644 --- a/xsd/siri_model/siri_situationAffects-v2.0.xsd +++ b/xsd/siri_model/siri_situationAffects-v2.0.xsd @@ -552,10 +552,19 @@ Rail transport, Roads and road transport All LINEs in the network are affected.         - + - Only some ROUTEs are affected, LINE level information not available. See the AffectedRoutes element for textual description. + Only some ROUTEs are affected, LINE level information not available. See the RoutesAffected element for textual description. + + + + + An ordered list of MAPPING POINTs defining one single path through the road (or rail) Network. A ROUTE may pass through the same MAPPING POINT more than once. + + + + From b6cf4349a733ea554fd6c4fcdfe56bbc50a1199d Mon Sep 17 00:00:00 2001 From: u215619 Date: Fri, 28 Aug 2020 21:50:19 +0200 Subject: [PATCH 195/290] Upgrade to current view-source:https://www.w3.org/2001/xml.xsd version See https://3.basecamp.com/3256016/buckets/9672657/messages/2938532101 --- xsd/xml/xml.xsd | 333 +++++++++++++++++------------------------------- 1 file changed, 117 insertions(+), 216 deletions(-) diff --git a/xsd/xml/xml.xsd b/xsd/xml/xml.xsd index a169b9e4..a5006a13 100644 --- a/xsd/xml/xml.xsd +++ b/xsd/xml/xml.xsd @@ -1,217 +1,118 @@ - - - - - - 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. - - - - - - - - + + + + + + + See http://www.w3.org/XML/1998/namespace.html and + http://www.w3.org/TR/REC-xml for information about this namespace. + + This schema document describes the XML namespace, in a form + suitable for import by other schema documents. + + Note that local names in this namespace are intended to be defined + only by the World Wide Web Consortium or its subgroups. The + following names are currently defined in this namespace and should + not be used with conflicting semantics by any Working Group, + specification, or document instance: + + base (as an attribute name): denotes an attribute whose value + provides a URI to be used as the base for interpreting any + relative URIs in the scope of the element on which it + appears; its value is inherited. This name is reserved + by virtue of its definition in the XML Base specification. + + lang (as an attribute name): denotes an attribute whose value + is a language code for the natural language of the content of + any element; its value is inherited. This name is reserved + by virtue of its definition in the XML specification. + + space (as an attribute name): denotes an attribute whose + value is a keyword indicating what whitespace processing + discipline is intended for the content of the element; its + value is inherited. This name is reserved by virtue of its + definition in the XML specification. + + Father (in any context at all): denotes Jon Bosak, the chair of + the original XML Working Group. This name is reserved by + the following decision of the W3C XML Plenary and + XML Coordination groups: + + In appreciation for his vision, leadership and dedication + the W3C XML Plenary on this 10th day of February, 2000 + reserves for Jon Bosak in perpetuity the XML name + xml:Father + + + + + This schema defines attributes and an attribute group + suitable for use by + schemas wishing to allow xml:base, xml:lang 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 2- and 3-letter + codes as the enumerated possible values . . . + + + + + + + + + + + + + + + See http://www.w3.org/TR/xmlbase/ for + information about this attribute. + + + + + + + + + + From 544aad4a3736a4e5c3675e65c19965170d5827a9 Mon Sep 17 00:00:00 2001 From: u215619 Date: Fri, 28 Aug 2020 21:57:09 +0200 Subject: [PATCH 196/290] first line was a typo --- xsd/xml/xml.xsd | 87 ++++++++++++++++++++++--------------------------- 1 file changed, 39 insertions(+), 48 deletions(-) diff --git a/xsd/xml/xml.xsd b/xsd/xml/xml.xsd index a5006a13..e75b14bc 100644 --- a/xsd/xml/xml.xsd +++ b/xsd/xml/xml.xsd @@ -1,10 +1,8 @@ - - - - - - - + + + + + See http://www.w3.org/XML/1998/namespace.html and http://www.w3.org/TR/REC-xml for information about this namespace. @@ -44,34 +42,32 @@ reserves for Jon Bosak in perpetuity the XML name xml:Father - - - - This schema defines attributes and an attribute group + + + 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 . . .> + <schema . . .> . . . <import namespace="http://www.w3.org/XML/1998/namespace" - schemaLocation="http://www.w3.org/2001/03/xml.xsd"/> + 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 . . .> + <type . . .> . . . - <attributeGroup ref="xml:specialAttrs"/> + <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 + + + 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 @@ -84,35 +80,30 @@ accordingly; the version at http://www.w3.org/2001/03/xml.xsd will not change. - - - - - In due course, we should install the relevant ISO 2- and 3-letter + + + + In due course, we should install the relevant ISO 2- and 3-letter codes as the enumerated possible values . . . - - - - - - - - - - - - - - - See http://www.w3.org/TR/xmlbase/ for + + + + + + + + + + + + + See http://www.w3.org/TR/xmlbase/ for information about this attribute. - - - - - - - - - + + + + + + + From 13beb99bb45e8c89e5a55312b7f5d71f04be1296 Mon Sep 17 00:00:00 2001 From: u215619 Date: Mon, 31 Aug 2020 07:17:42 +0200 Subject: [PATCH 197/290] Elements added that should not have been deleted from UmS proposal - DescriptionPriority - ConsequencePriority - RemarkPriority - AdvicePriority Changed cardinality of correspondent wrapper elements --- xsd/siri_model/siri_situationActions-v2.0.xsd | 32 ++++++++++++++++--- 1 file changed, 28 insertions(+), 4 deletions(-) diff --git a/xsd/siri_model/siri_situationActions-v2.0.xsd b/xsd/siri_model/siri_situationActions-v2.0.xsd index eca3d02a..4de931ab 100644 --- a/xsd/siri_model/siri_situationActions-v2.0.xsd +++ b/xsd/siri_model/siri_situationActions-v2.0.xsd @@ -592,6 +592,12 @@ Description of SITUATION. Should not repeat any strap line included in Summary. (Unbounded since SIRI 2.0)         + + + Prioritises a description from the information owner's point of view, e.g. usable for sorting or hiding individual descriptions. + 1 = highest priority. + + @@ -601,6 +607,12 @@ Further consequence to passengers. (Unbounded since SIRI 2.0)         + + + Prioritises a consequence from the information owner's point of view, e.g. usable for sorting or hiding individual consequences. + 1 = highest priority. + + @@ -628,6 +640,12 @@ Further recommendation to passengers. (Unbounded since SIRI 2.0)         + + + Prioritises a recommendation from the information owner's point of view, e.g. usable for sorting or hiding individual recommendations. + 1 = highest priority. + + @@ -637,6 +655,12 @@ Further remark to passengers, e,g, "For more information call xy".         + + + Prioritises a remark from the information owner's point of view, e.g. usable for sorting or hiding individual remarks. + 1 = highest priority. + + @@ -674,17 +698,17 @@ Content for the reason of a passenger information action         - + Content for the description of a passenger information action - + Content for the consequence of a passenger information action - + Content for the advice of a passenger information action @@ -694,7 +718,7 @@ Content for the duration of a passenger information action.         - + Content for the remark of a passenger information action, e,g, "For more information call xy". From dc0bc90ceebe04ceac4739d1d9e2501e9e1b7b13 Mon Sep 17 00:00:00 2001 From: Christophe Duquesne Date: Mon, 31 Aug 2020 11:41:37 +0200 Subject: [PATCH 198/290] Addition of RemedyPeriod to conform the documentation Addition of RemedyPeriod to conform the documentation --- xsd/siri_model/siri_facility-v2.0.xsd | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/xsd/siri_model/siri_facility-v2.0.xsd b/xsd/siri_model/siri_facility-v2.0.xsd index 4d59874d..f53a17cd 100644 --- a/xsd/siri_model/siri_facility-v2.0.xsd +++ b/xsd/siri_model/siri_facility-v2.0.xsd @@ -533,6 +533,11 @@ Rail transport, Roads and road transport Description of the set up remedy in natural language. (Unbounded since SIRI 2.0)         + + + Validity period for the remedy + + From d42aa90f0a534960f46086ef66a90c31b0d05f16 Mon Sep 17 00:00:00 2001 From: u215619 Date: Mon, 31 Aug 2020 15:15:53 +0200 Subject: [PATCH 199/290] Let ReasonGroup be optional --- xsd/siri_model/siri_situationActions-v2.0.xsd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xsd/siri_model/siri_situationActions-v2.0.xsd b/xsd/siri_model/siri_situationActions-v2.0.xsd index 4de931ab..24a2481b 100644 --- a/xsd/siri_model/siri_situationActions-v2.0.xsd +++ b/xsd/siri_model/siri_situationActions-v2.0.xsd @@ -145,7 +145,7 @@ - + Structured Reason elements. The TpegReason and/or PublicEventReason enumerated values can be used to generate standardized messages for the current Perspective. If no enumerated values are given, ReasonName is used instead. Note: this means that ReasonName is NOT a complete message, but only a (few) word(s) to be included in the message! From 7ef5e189cc1e143bb56b0621522e98805bf8a488 Mon Sep 17 00:00:00 2001 From: u215619 Date: Mon, 31 Aug 2020 17:00:19 +0200 Subject: [PATCH 200/290] Default aligned to Docu --- xsd/siri_situationExchange_service.xsd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xsd/siri_situationExchange_service.xsd b/xsd/siri_situationExchange_service.xsd index d36fd25a..353ee5f4 100644 --- a/xsd/siri_situationExchange_service.xsd +++ b/xsd/siri_situationExchange_service.xsd @@ -430,7 +430,7 @@ Rail transport, Roads and road transport Parameters that affect the subscription publishing and notification processing.         - + Whether the producer will return the complete set of current data, or only provide updates to this data, i.e. additions, modifications and deletions. If false or omitted, each subscription response will contain the full information as specified in this request. From 3cf23b4adc8e6a477b23350acd7060c8ce3146a0 Mon Sep 17 00:00:00 2001 From: Tim Rivett Date: Fri, 4 Sep 2020 16:56:52 +0100 Subject: [PATCH 201/290] CR073 Add Fuel Type Add fuel type to match NeTEX into siri_facilities.xsd --- xsd/siri_model/siri_facility-v2.0.xsd | 35 +++++++++++++++++++++++++++ 1 file changed, 35 insertions(+) diff --git a/xsd/siri_model/siri_facility-v2.0.xsd b/xsd/siri_model/siri_facility-v2.0.xsd index 4d59874d..cb1b96bb 100644 --- a/xsd/siri_model/siri_facility-v2.0.xsd +++ b/xsd/siri_model/siri_facility-v2.0.xsd @@ -712,4 +712,39 @@ Rail transport, Roads and road transport         + + + + Classification of Vehicle Energy type. See Transmodel TypeOfFuel + + + + + + Values for Vehicle fuel type. +SIRI v2.1 + + + + + An arbitrary vehicle fuel classification. +SIRI v2.1 + + + + + + + + Values for Vehicle fuel type. Use of "other" requires the additional open ended FuelTypeOther to be filled + + + + + + + + + + + +         From 9d245ec88782f8b9c2ba2e1e3b43cf86c3b7d0dd Mon Sep 17 00:00:00 2001 From: u215619 Date: Mon, 7 Sep 2020 16:06:30 +0200 Subject: [PATCH 202/290] Version upgrade auf 2.1 --- xsd/acsb/acsb_accessibility-v0.3.xsd | 2 +- xsd/acsb/acsb_limitations-v0.2.xsd | 2 +- xsd/acsb/acsb_passengerMobility-v0.3.xsd | 2 +- xsd/ifopt/ifopt_administration-v0.3.xsd | 2 +- xsd/ifopt/ifopt_checkpoint-v0.3.xsd | 2 +- xsd/ifopt/ifopt_countries-v0.2.xsd | 2 +- xsd/ifopt/ifopt_equipment-v0.3.xsd | 2 +- xsd/ifopt/ifopt_location-v0.3.xsd | 2 +- xsd/ifopt/ifopt_modes-v0.2.xsd | 2 +- xsd/ifopt/ifopt_modification-v0.3.xsd | 2 +- xsd/ifopt/ifopt_path-v0.2.xsd | 2 +- xsd/ifopt/ifopt_stop-v0.3.xsd | 2 +- xsd/ifopt/ifopt_time-v0.2.xsd | 2 +- xsd/ifopt/ifopt_types-v0.2.xsd | 2 +- xsd/siri/siri_base-v2.0.xsd | 2 +- xsd/siri/siri_common_services-v2.0.xsd | 2 +- xsd/siri/siri_request_errorConditions-v2.0.xsd | 2 +- xsd/siri/siri_request_support-v2.0.xsd | 2 +- xsd/siri/siri_requests-v2.0.xsd | 2 +- xsd/siriSg.xsd | 2 +- xsd/siri_all_functionalServices.xsd | 2 +- xsd/siri_connectionMonitoring_service.xsd | 2 +- xsd/siri_connectionTimetable_service.xsd | 2 +- xsd/siri_discovery.xsd | 2 +- xsd/siri_estimatedTimetable_service.xsd | 2 +- xsd/siri_facilityMonitoring_service.xsd | 2 +- xsd/siri_generalMessage_service.xsd | 2 +- xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd | 2 +- xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd | 2 +- xsd/siri_model/siri_facilities-v1.2.xsd | 2 +- xsd/siri_model/siri_facility-v2.0.xsd | 2 +- xsd/siri_model/siri_feature_support-v2.0.xsd | 2 +- xsd/siri_model/siri_interchangeJourney-v2.0.xsd | 2 +- xsd/siri_model/siri_journey-v2.0.xsd | 2 +- xsd/siri_model/siri_journey_support-v2.0.xsd | 2 +- xsd/siri_model/siri_modelPermissions-v2.0.xsd | 2 +- xsd/siri_model/siri_modes-v1.1.xsd | 2 +- xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd | 2 +- xsd/siri_model/siri_operator_support-v2.0.xsd | 2 +- xsd/siri_model/siri_reference-v2.0.xsd | 2 +- xsd/siri_model/siri_situation-v2.0.xsd | 2 +- xsd/siri_model/siri_situationActions-v2.0.xsd | 2 +- xsd/siri_model/siri_situationAffects-v2.0.xsd | 2 +- xsd/siri_model/siri_situationClassifiers-v1.1.xsd | 2 +- xsd/siri_model/siri_situationIdentity-v1.1.xsd | 2 +- xsd/siri_model/siri_situationReasons-v2.0.xsd | 2 +- xsd/siri_model/siri_situationServiceTypes-v1.0.xsd | 2 +- xsd/siri_model/siri_targetedVehicleJourney-v2.0.xsd | 2 +- xsd/siri_model/siri_time-v2.0.xsd | 2 +- xsd/siri_model_discovery/siri_connectionLink-v2.0.xsd | 2 +- xsd/siri_model_discovery/siri_feature-v2.0.xsd | 2 +- xsd/siri_model_discovery/siri_infoChannel-v2.0.xsd | 2 +- xsd/siri_model_discovery/siri_line-v2.0.xsd | 2 +- xsd/siri_model_discovery/siri_stopPoint-v2.0.xsd | 2 +- xsd/siri_productionTimetable_service.xsd | 2 +- xsd/siri_situationExchange_service.xsd | 2 +- xsd/siri_stopMonitoring_service.xsd | 2 +- xsd/siri_stopTimetable_service.xsd | 2 +- xsd/siri_utility/siri_location-v2.0.xsd | 2 +- xsd/siri_utility/siri_participant-v2.0.xsd | 2 +- xsd/siri_utility/siri_permissions-v2.0.xsd | 2 +- xsd/siri_utility/siri_types-v2.0.xsd | 2 +- xsd/siri_utility/siri_utility-v1.1.xsd | 2 +- xsd/wsdl_model/siri_wsConsumer-Framework.xsd | 2 +- xsd/wsdl_model/siri_wsConsumer-Services.xsd | 2 +- xsd/wsdl_model/siri_wsProducer-DiscoveryCapability.xsd | 2 +- xsd/wsdl_model/siri_wsProducer-Framework.xsd | 2 +- xsd/wsdl_model/siri_wsProducer-Services.xsd | 2 +- xsd/zrescue/siri_estimatedVehicleJourney-v2.0.xsd | 2 +- xsd/zrescue/siri_situation-v2.0.xsd | 2 +- xsd/zrescue/siri_situationAffects-v2.0.xsd | 2 +- 71 files changed, 71 insertions(+), 71 deletions(-) diff --git a/xsd/acsb/acsb_accessibility-v0.3.xsd b/xsd/acsb/acsb_accessibility-v0.3.xsd index 50b68eba..68485fd7 100644 --- a/xsd/acsb/acsb_accessibility-v0.3.xsd +++ b/xsd/acsb/acsb_accessibility-v0.3.xsd @@ -35,7 +35,7 @@

      • Derived from the SIRI standards.
      - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/acsb/acsb_limitations-v0.2.xsd b/xsd/acsb/acsb_limitations-v0.2.xsd index 55e536f8..9e00be80 100644 --- a/xsd/acsb/acsb_limitations-v0.2.xsd +++ b/xsd/acsb/acsb_limitations-v0.2.xsd @@ -35,7 +35,7 @@
    • Derived from the SIRI standards.
    - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/acsb/acsb_passengerMobility-v0.3.xsd b/xsd/acsb/acsb_passengerMobility-v0.3.xsd index d144e727..ae0d4e6e 100644 --- a/xsd/acsb/acsb_passengerMobility-v0.3.xsd +++ b/xsd/acsb/acsb_passengerMobility-v0.3.xsd @@ -35,7 +35,7 @@
  • Derived from the SIRI standards.
- Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/ifopt/ifopt_administration-v0.3.xsd b/xsd/ifopt/ifopt_administration-v0.3.xsd index d1e85306..12a7070d 100644 --- a/xsd/ifopt/ifopt_administration-v0.3.xsd +++ b/xsd/ifopt/ifopt_administration-v0.3.xsd @@ -35,7 +35,7 @@
  • Derived from the SIRI standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/ifopt/ifopt_checkpoint-v0.3.xsd b/xsd/ifopt/ifopt_checkpoint-v0.3.xsd index 10a87494..7208c03f 100644 --- a/xsd/ifopt/ifopt_checkpoint-v0.3.xsd +++ b/xsd/ifopt/ifopt_checkpoint-v0.3.xsd @@ -39,7 +39,7 @@
  • Derived from the IFOPT standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/ifopt/ifopt_countries-v0.2.xsd b/xsd/ifopt/ifopt_countries-v0.2.xsd index 7d25038a..ba5d7e71 100644 --- a/xsd/ifopt/ifopt_countries-v0.2.xsd +++ b/xsd/ifopt/ifopt_countries-v0.2.xsd @@ -35,7 +35,7 @@
  • Derived from the SIRI standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/ifopt/ifopt_equipment-v0.3.xsd b/xsd/ifopt/ifopt_equipment-v0.3.xsd index 0fad790c..7a418aad 100644 --- a/xsd/ifopt/ifopt_equipment-v0.3.xsd +++ b/xsd/ifopt/ifopt_equipment-v0.3.xsd @@ -35,7 +35,7 @@
  • Derived from the TransModel standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/ifopt/ifopt_location-v0.3.xsd b/xsd/ifopt/ifopt_location-v0.3.xsd index f212b528..2526610d 100644 --- a/xsd/ifopt/ifopt_location-v0.3.xsd +++ b/xsd/ifopt/ifopt_location-v0.3.xsd @@ -41,7 +41,7 @@
  • Derived from the SIRI standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/ifopt/ifopt_modes-v0.2.xsd b/xsd/ifopt/ifopt_modes-v0.2.xsd index 2cf9e64d..a41ace18 100644 --- a/xsd/ifopt/ifopt_modes-v0.2.xsd +++ b/xsd/ifopt/ifopt_modes-v0.2.xsd @@ -32,7 +32,7 @@
  • Derived from the SIRI standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/ifopt/ifopt_modification-v0.3.xsd b/xsd/ifopt/ifopt_modification-v0.3.xsd index 5c4205f9..3e6b8101 100644 --- a/xsd/ifopt/ifopt_modification-v0.3.xsd +++ b/xsd/ifopt/ifopt_modification-v0.3.xsd @@ -36,7 +36,7 @@
  • Derived from the SIRI standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/ifopt/ifopt_path-v0.2.xsd b/xsd/ifopt/ifopt_path-v0.2.xsd index ee748a70..286c3a25 100644 --- a/xsd/ifopt/ifopt_path-v0.2.xsd +++ b/xsd/ifopt/ifopt_path-v0.2.xsd @@ -32,7 +32,7 @@
  • Derived from the SIRI standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/ifopt/ifopt_stop-v0.3.xsd b/xsd/ifopt/ifopt_stop-v0.3.xsd index c5ae666a..db92837c 100644 --- a/xsd/ifopt/ifopt_stop-v0.3.xsd +++ b/xsd/ifopt/ifopt_stop-v0.3.xsd @@ -41,7 +41,7 @@
  • Derived from the SIRI standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/ifopt/ifopt_time-v0.2.xsd b/xsd/ifopt/ifopt_time-v0.2.xsd index 9c4725cd..3427adb0 100644 --- a/xsd/ifopt/ifopt_time-v0.2.xsd +++ b/xsd/ifopt/ifopt_time-v0.2.xsd @@ -32,7 +32,7 @@
  • Derived from the SIRI standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/ifopt/ifopt_types-v0.2.xsd b/xsd/ifopt/ifopt_types-v0.2.xsd index 7052b418..1152bf97 100644 --- a/xsd/ifopt/ifopt_types-v0.2.xsd +++ b/xsd/ifopt/ifopt_types-v0.2.xsd @@ -35,7 +35,7 @@
  • Derived from the SIRI standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri/siri_base-v2.0.xsd b/xsd/siri/siri_base-v2.0.xsd index dab8e566..0037bfc3 100644 --- a/xsd/siri/siri_base-v2.0.xsd +++ b/xsd/siri/siri_base-v2.0.xsd @@ -67,7 +67,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri/siri_common_services-v2.0.xsd b/xsd/siri/siri_common_services-v2.0.xsd index f2e94174..47ee42cf 100644 --- a/xsd/siri/siri_common_services-v2.0.xsd +++ b/xsd/siri/siri_common_services-v2.0.xsd @@ -81,7 +81,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri/siri_request_errorConditions-v2.0.xsd b/xsd/siri/siri_request_errorConditions-v2.0.xsd index ea6690a3..5e7f87c8 100644 --- a/xsd/siri/siri_request_errorConditions-v2.0.xsd +++ b/xsd/siri/siri_request_errorConditions-v2.0.xsd @@ -64,7 +64,7 @@
  • Derived from the VDV, RTIGXML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri/siri_request_support-v2.0.xsd b/xsd/siri/siri_request_support-v2.0.xsd index 0ab402b9..b64b7e85 100644 --- a/xsd/siri/siri_request_support-v2.0.xsd +++ b/xsd/siri/siri_request_support-v2.0.xsd @@ -42,7 +42,7 @@
  • Derived from the SIRI 1.0 standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri/siri_requests-v2.0.xsd b/xsd/siri/siri_requests-v2.0.xsd index c105fa12..1e8f10f4 100644 --- a/xsd/siri/siri_requests-v2.0.xsd +++ b/xsd/siri/siri_requests-v2.0.xsd @@ -106,7 +106,7 @@
  • Derived from the VDV, RTIGXML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, Ports and maritime transport, Ferries (marine), Public transport, Bus services, Coach services, Bus stops and stations, Rail transport, Railway stations and track, Train services, Underground trains, Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, Rail transport, Roads and road transport diff --git a/xsd/siriSg.xsd b/xsd/siriSg.xsd index 6f5f57f0..6f7b9ea4 100644 --- a/xsd/siriSg.xsd +++ b/xsd/siriSg.xsd @@ -107,7 +107,7 @@
  • Derived from the SIRI Version 1.0
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_all_functionalServices.xsd b/xsd/siri_all_functionalServices.xsd index 7d87f2b6..17227a5f 100644 --- a/xsd/siri_all_functionalServices.xsd +++ b/xsd/siri_all_functionalServices.xsd @@ -59,7 +59,7 @@
  • Derived from the SIRI Version 1.0.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_connectionMonitoring_service.xsd b/xsd/siri_connectionMonitoring_service.xsd index 6fcbc248..22cbc5b4 100644 --- a/xsd/siri_connectionMonitoring_service.xsd +++ b/xsd/siri_connectionMonitoring_service.xsd @@ -71,7 +71,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_connectionTimetable_service.xsd b/xsd/siri_connectionTimetable_service.xsd index be458b25..dd814ba6 100644 --- a/xsd/siri_connectionTimetable_service.xsd +++ b/xsd/siri_connectionTimetable_service.xsd @@ -73,7 +73,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_discovery.xsd b/xsd/siri_discovery.xsd index d904b971..2bb7d9a8 100644 --- a/xsd/siri_discovery.xsd +++ b/xsd/siri_discovery.xsd @@ -87,7 +87,7 @@
  • Discovery services Derived from the NaPTAN standard .
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_estimatedTimetable_service.xsd b/xsd/siri_estimatedTimetable_service.xsd index 91781e39..b11fa597 100644 --- a/xsd/siri_estimatedTimetable_service.xsd +++ b/xsd/siri_estimatedTimetable_service.xsd @@ -69,7 +69,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_facilityMonitoring_service.xsd b/xsd/siri_facilityMonitoring_service.xsd index 3899f417..04227bce 100644 --- a/xsd/siri_facilityMonitoring_service.xsd +++ b/xsd/siri_facilityMonitoring_service.xsd @@ -54,7 +54,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_generalMessage_service.xsd b/xsd/siri_generalMessage_service.xsd index ce4a917b..fefa69d8 100644 --- a/xsd/siri_generalMessage_service.xsd +++ b/xsd/siri_generalMessage_service.xsd @@ -67,7 +67,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd index e72fb70a..bd3db7db 100644 --- a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd @@ -76,7 +76,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index 8f4db506..6afea759 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -71,7 +71,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_facilities-v1.2.xsd b/xsd/siri_model/siri_facilities-v1.2.xsd index 4012538c..66b26fec 100644 --- a/xsd/siri_model/siri_facilities-v1.2.xsd +++ b/xsd/siri_model/siri_facilities-v1.2.xsd @@ -45,7 +45,7 @@
  • Derived from the TPEG Categories schema as encoded in the Kizoom XTIS schema.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_facility-v2.0.xsd b/xsd/siri_model/siri_facility-v2.0.xsd index 3b78401f..78f770e4 100644 --- a/xsd/siri_model/siri_facility-v2.0.xsd +++ b/xsd/siri_model/siri_facility-v2.0.xsd @@ -57,7 +57,7 @@
  • Derived from TransModel and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_feature_support-v2.0.xsd b/xsd/siri_model/siri_feature_support-v2.0.xsd index 3ae65c92..79d73d1d 100644 --- a/xsd/siri_model/siri_feature_support-v2.0.xsd +++ b/xsd/siri_model/siri_feature_support-v2.0.xsd @@ -54,7 +54,7 @@
  • Derived from the VDV, RTIG CML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_interchangeJourney-v2.0.xsd b/xsd/siri_model/siri_interchangeJourney-v2.0.xsd index 895d1405..76f50547 100644 --- a/xsd/siri_model/siri_interchangeJourney-v2.0.xsd +++ b/xsd/siri_model/siri_interchangeJourney-v2.0.xsd @@ -40,7 +40,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index 6751cda1..fe55d2d9 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -103,7 +103,7 @@
  • Derived from the VDV, RTIG CML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_journey_support-v2.0.xsd b/xsd/siri_model/siri_journey_support-v2.0.xsd index b40fcb52..c7e36e34 100644 --- a/xsd/siri_model/siri_journey_support-v2.0.xsd +++ b/xsd/siri_model/siri_journey_support-v2.0.xsd @@ -69,7 +69,7 @@
  • Derived from the VDV, RTIG CML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_modelPermissions-v2.0.xsd b/xsd/siri_model/siri_modelPermissions-v2.0.xsd index e83c27c5..1f3c729b 100644 --- a/xsd/siri_model/siri_modelPermissions-v2.0.xsd +++ b/xsd/siri_model/siri_modelPermissions-v2.0.xsd @@ -45,7 +45,7 @@
  • Derived from the VDV, RTIGXML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_modes-v1.1.xsd b/xsd/siri_model/siri_modes-v1.1.xsd index d85f79e4..cc56086f 100644 --- a/xsd/siri_model/siri_modes-v1.1.xsd +++ b/xsd/siri_model/siri_modes-v1.1.xsd @@ -42,7 +42,7 @@
  • Derived from the TPEG Categories schema
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd index 9d4fd026..40c37708 100644 --- a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd @@ -84,7 +84,7 @@
  • Derived from the VDV, RTIG CML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_operator_support-v2.0.xsd b/xsd/siri_model/siri_operator_support-v2.0.xsd index 196746f2..b006847b 100644 --- a/xsd/siri_model/siri_operator_support-v2.0.xsd +++ b/xsd/siri_model/siri_operator_support-v2.0.xsd @@ -35,7 +35,7 @@
  • Derived from the SIRI standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_reference-v2.0.xsd b/xsd/siri_model/siri_reference-v2.0.xsd index 3c49588f..1de7bf96 100644 --- a/xsd/siri_model/siri_reference-v2.0.xsd +++ b/xsd/siri_model/siri_reference-v2.0.xsd @@ -83,7 +83,7 @@
  • Derived from the VDV, RTIG CML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_situation-v2.0.xsd b/xsd/siri_model/siri_situation-v2.0.xsd index 20af1d3e..6abe66fe 100644 --- a/xsd/siri_model/siri_situation-v2.0.xsd +++ b/xsd/siri_model/siri_situation-v2.0.xsd @@ -111,7 +111,7 @@
  • Schema Derived from the Kizoom XTIS schema
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_situationActions-v2.0.xsd b/xsd/siri_model/siri_situationActions-v2.0.xsd index 24a2481b..ae5aa9d1 100644 --- a/xsd/siri_model/siri_situationActions-v2.0.xsd +++ b/xsd/siri_model/siri_situationActions-v2.0.xsd @@ -58,7 +58,7 @@
  • Schema derived Derived from the Kizoom XTIS schema
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, Ports and maritime transport, Ferries (marine), Public transport, Bus services, Coach services, Bus stops and stations, Rail transport, Railway stations and track, Train services, Underground trains, Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, Rail transport, Roads and road transport diff --git a/xsd/siri_model/siri_situationAffects-v2.0.xsd b/xsd/siri_model/siri_situationAffects-v2.0.xsd index 98147b1a..d785dcf0 100644 --- a/xsd/siri_model/siri_situationAffects-v2.0.xsd +++ b/xsd/siri_model/siri_situationAffects-v2.0.xsd @@ -89,7 +89,7 @@
  • Schema derived Derived from the Kizoom XTIS schema
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_situationClassifiers-v1.1.xsd b/xsd/siri_model/siri_situationClassifiers-v1.1.xsd index 8b5ee21c..8b157e69 100644 --- a/xsd/siri_model/siri_situationClassifiers-v1.1.xsd +++ b/xsd/siri_model/siri_situationClassifiers-v1.1.xsd @@ -47,7 +47,7 @@
  • Derived from the TPEG Categories schema
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_situationIdentity-v1.1.xsd b/xsd/siri_model/siri_situationIdentity-v1.1.xsd index c910282b..8aa72a0c 100644 --- a/xsd/siri_model/siri_situationIdentity-v1.1.xsd +++ b/xsd/siri_model/siri_situationIdentity-v1.1.xsd @@ -41,7 +41,7 @@
  • Derived from the VDV, RTIG CML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_situationReasons-v2.0.xsd b/xsd/siri_model/siri_situationReasons-v2.0.xsd index c28f6037..8c553c82 100644 --- a/xsd/siri_model/siri_situationReasons-v2.0.xsd +++ b/xsd/siri_model/siri_situationReasons-v2.0.xsd @@ -89,7 +89,7 @@
  • Derived from the TPEG2 AlertCause schema
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd b/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd index 6ac66a03..073a5f26 100644 --- a/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd +++ b/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd @@ -52,7 +52,7 @@
  • Derived from the TPEG2 PTS schemas
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_targetedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_targetedVehicleJourney-v2.0.xsd index fe50c4ce..c5ae66b2 100644 --- a/xsd/siri_model/siri_targetedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_targetedVehicleJourney-v2.0.xsd @@ -65,7 +65,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_time-v2.0.xsd b/xsd/siri_model/siri_time-v2.0.xsd index 1dd1ba1c..6eb34a77 100644 --- a/xsd/siri_model/siri_time-v2.0.xsd +++ b/xsd/siri_model/siri_time-v2.0.xsd @@ -54,7 +54,7 @@
  • Derived from the VDV, RTIG CML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model_discovery/siri_connectionLink-v2.0.xsd b/xsd/siri_model_discovery/siri_connectionLink-v2.0.xsd index b71d2855..190f3fd1 100644 --- a/xsd/siri_model_discovery/siri_connectionLink-v2.0.xsd +++ b/xsd/siri_model_discovery/siri_connectionLink-v2.0.xsd @@ -37,7 +37,7 @@
  • Discovery services Derived from the NaPTAN standard .
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model_discovery/siri_feature-v2.0.xsd b/xsd/siri_model_discovery/siri_feature-v2.0.xsd index d5c00b55..e28f108b 100644 --- a/xsd/siri_model_discovery/siri_feature-v2.0.xsd +++ b/xsd/siri_model_discovery/siri_feature-v2.0.xsd @@ -48,7 +48,7 @@
  • Discovery services Derived from the NaPTAN standard .
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model_discovery/siri_infoChannel-v2.0.xsd b/xsd/siri_model_discovery/siri_infoChannel-v2.0.xsd index 1d34250b..b663e0d1 100644 --- a/xsd/siri_model_discovery/siri_infoChannel-v2.0.xsd +++ b/xsd/siri_model_discovery/siri_infoChannel-v2.0.xsd @@ -47,7 +47,7 @@
  • Discovery services Derived from the NaPTAN standard .
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model_discovery/siri_line-v2.0.xsd b/xsd/siri_model_discovery/siri_line-v2.0.xsd index 4d005d7c..8ffd1c74 100644 --- a/xsd/siri_model_discovery/siri_line-v2.0.xsd +++ b/xsd/siri_model_discovery/siri_line-v2.0.xsd @@ -58,7 +58,7 @@
  • Discovery services Derived from the NaPTAN standard .
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model_discovery/siri_stopPoint-v2.0.xsd b/xsd/siri_model_discovery/siri_stopPoint-v2.0.xsd index e9d6bc24..7324bef7 100644 --- a/xsd/siri_model_discovery/siri_stopPoint-v2.0.xsd +++ b/xsd/siri_model_discovery/siri_stopPoint-v2.0.xsd @@ -54,7 +54,7 @@
  • Discovery services Derived from the NaPTAN standard .
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_productionTimetable_service.xsd b/xsd/siri_productionTimetable_service.xsd index 07a90247..84cf94cc 100644 --- a/xsd/siri_productionTimetable_service.xsd +++ b/xsd/siri_productionTimetable_service.xsd @@ -92,7 +92,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_situationExchange_service.xsd b/xsd/siri_situationExchange_service.xsd index 0998104b..5cea01bf 100644 --- a/xsd/siri_situationExchange_service.xsd +++ b/xsd/siri_situationExchange_service.xsd @@ -93,7 +93,7 @@
  • categories from TPEG
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_stopMonitoring_service.xsd b/xsd/siri_stopMonitoring_service.xsd index b093e269..cf30cc4f 100644 --- a/xsd/siri_stopMonitoring_service.xsd +++ b/xsd/siri_stopMonitoring_service.xsd @@ -94,7 +94,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_stopTimetable_service.xsd b/xsd/siri_stopTimetable_service.xsd index a34833d4..27b8dce0 100644 --- a/xsd/siri_stopTimetable_service.xsd +++ b/xsd/siri_stopTimetable_service.xsd @@ -68,7 +68,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_utility/siri_location-v2.0.xsd b/xsd/siri_utility/siri_location-v2.0.xsd index af8b3075..ab8cbf7c 100644 --- a/xsd/siri_utility/siri_location-v2.0.xsd +++ b/xsd/siri_utility/siri_location-v2.0.xsd @@ -56,7 +56,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_utility/siri_participant-v2.0.xsd b/xsd/siri_utility/siri_participant-v2.0.xsd index 511ca1d3..de75b15d 100644 --- a/xsd/siri_utility/siri_participant-v2.0.xsd +++ b/xsd/siri_utility/siri_participant-v2.0.xsd @@ -44,7 +44,7 @@
  • Derived from the VDV, RTIGXML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_utility/siri_permissions-v2.0.xsd b/xsd/siri_utility/siri_permissions-v2.0.xsd index bb997e8e..41361da2 100644 --- a/xsd/siri_utility/siri_permissions-v2.0.xsd +++ b/xsd/siri_utility/siri_permissions-v2.0.xsd @@ -41,7 +41,7 @@
  • Derived from the VDV, RTIGXML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_utility/siri_types-v2.0.xsd b/xsd/siri_utility/siri_types-v2.0.xsd index 1779d7b5..9de24d20 100644 --- a/xsd/siri_utility/siri_types-v2.0.xsd +++ b/xsd/siri_utility/siri_types-v2.0.xsd @@ -44,7 +44,7 @@
  • Derived from the VDV, RTIG CML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_utility/siri_utility-v1.1.xsd b/xsd/siri_utility/siri_utility-v1.1.xsd index 2a064526..c2e38ad9 100644 --- a/xsd/siri_utility/siri_utility-v1.1.xsd +++ b/xsd/siri_utility/siri_utility-v1.1.xsd @@ -36,7 +36,7 @@
  • Derived from the VDV, RTIGXML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/wsdl_model/siri_wsConsumer-Framework.xsd b/xsd/wsdl_model/siri_wsConsumer-Framework.xsd index f8f91027..55ad0979 100644 --- a/xsd/wsdl_model/siri_wsConsumer-Framework.xsd +++ b/xsd/wsdl_model/siri_wsConsumer-Framework.xsd @@ -46,7 +46,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/wsdl_model/siri_wsConsumer-Services.xsd b/xsd/wsdl_model/siri_wsConsumer-Services.xsd index cdd77175..fad24c53 100644 --- a/xsd/wsdl_model/siri_wsConsumer-Services.xsd +++ b/xsd/wsdl_model/siri_wsConsumer-Services.xsd @@ -46,7 +46,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/wsdl_model/siri_wsProducer-DiscoveryCapability.xsd b/xsd/wsdl_model/siri_wsProducer-DiscoveryCapability.xsd index 1e901c82..ba22d2b3 100644 --- a/xsd/wsdl_model/siri_wsProducer-DiscoveryCapability.xsd +++ b/xsd/wsdl_model/siri_wsProducer-DiscoveryCapability.xsd @@ -45,7 +45,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/wsdl_model/siri_wsProducer-Framework.xsd b/xsd/wsdl_model/siri_wsProducer-Framework.xsd index 9df4a581..01de86a2 100644 --- a/xsd/wsdl_model/siri_wsProducer-Framework.xsd +++ b/xsd/wsdl_model/siri_wsProducer-Framework.xsd @@ -45,7 +45,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/wsdl_model/siri_wsProducer-Services.xsd b/xsd/wsdl_model/siri_wsProducer-Services.xsd index 0fbc780d..cb172b67 100644 --- a/xsd/wsdl_model/siri_wsProducer-Services.xsd +++ b/xsd/wsdl_model/siri_wsProducer-Services.xsd @@ -45,7 +45,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/zrescue/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/zrescue/siri_estimatedVehicleJourney-v2.0.xsd index 5065f697..60216895 100644 --- a/xsd/zrescue/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/zrescue/siri_estimatedVehicleJourney-v2.0.xsd @@ -66,7 +66,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/zrescue/siri_situation-v2.0.xsd b/xsd/zrescue/siri_situation-v2.0.xsd index 38e2ef2f..2d3ec5ca 100644 --- a/xsd/zrescue/siri_situation-v2.0.xsd +++ b/xsd/zrescue/siri_situation-v2.0.xsd @@ -86,7 +86,7 @@
  • Schema Derived from the Kizoom XTIS schema
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/zrescue/siri_situationAffects-v2.0.xsd b/xsd/zrescue/siri_situationAffects-v2.0.xsd index 032a7463..76150d27 100644 --- a/xsd/zrescue/siri_situationAffects-v2.0.xsd +++ b/xsd/zrescue/siri_situationAffects-v2.0.xsd @@ -67,7 +67,7 @@
  • Schema derived Derived from the Kizoom XTIS schema
    • - Version 2.0 + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, From 66ddfcb2305b1677cf30844c926a80ce225d705f Mon Sep 17 00:00:00 2001 From: Christophe Duquesne Date: Tue, 15 Sep 2020 11:43:10 +0200 Subject: [PATCH 203/290] Update siri_reference-v2.0.xsd --- xsd/siri_model/siri_reference-v2.0.xsd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xsd/siri_model/siri_reference-v2.0.xsd b/xsd/siri_model/siri_reference-v2.0.xsd index 92405115..45ec0299 100644 --- a/xsd/siri_model/siri_reference-v2.0.xsd +++ b/xsd/siri_model/siri_reference-v2.0.xsd @@ -798,7 +798,7 @@ Values for these elements can be specified on an annual schedule and will be inh     - + Reference to a SITE From f22ed0f211c35ac3c1cb86ff25cf8000fd03e236 Mon Sep 17 00:00:00 2001 From: Tim Rivett Date: Wed, 16 Sep 2020 08:00:24 +0100 Subject: [PATCH 204/290] Update siri_facility-v2.0.xsd removed choice structure as per SIRI working group 15 Sept 2020 --- xsd/siri_model/siri_facility-v2.0.xsd | 22 ++++++++++------------ 1 file changed, 10 insertions(+), 12 deletions(-) diff --git a/xsd/siri_model/siri_facility-v2.0.xsd b/xsd/siri_model/siri_facility-v2.0.xsd index cb1b96bb..360d5334 100644 --- a/xsd/siri_model/siri_facility-v2.0.xsd +++ b/xsd/siri_model/siri_facility-v2.0.xsd @@ -718,18 +718,16 @@ Rail transport, Roads and road transport Classification of Vehicle Energy type. See Transmodel TypeOfFuel - - - - Values for Vehicle fuel type. +SIRI v2.1 - - - - - An arbitrary vehicle fuel classification. +SIRI v2.1 - - - + + + Values for Vehicle fuel type. +SIRI v2.1 + + + + + An arbitrary vehicle fuel classification. +SIRI v2.1 + + From b34feadfa38f54ec5230717918656295edb202e9 Mon Sep 17 00:00:00 2001 From: Tim Rivett Date: Wed, 16 Sep 2020 08:38:22 +0100 Subject: [PATCH 205/290] Update siri_facility-v2.0.xsd --- xsd/siri_model/siri_facility-v2.0.xsd | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/xsd/siri_model/siri_facility-v2.0.xsd b/xsd/siri_model/siri_facility-v2.0.xsd index a3c56b38..3743356d 100644 --- a/xsd/siri_model/siri_facility-v2.0.xsd +++ b/xsd/siri_model/siri_facility-v2.0.xsd @@ -723,24 +723,24 @@ Rail transport, Roads and road transport     - + Classification of Vehicle Energy type. See Transmodel TypeOfFuel - + Values for Vehicle fuel type. +SIRI v2.1 - + An arbitrary vehicle fuel classification. +SIRI v2.1 - + Values for Vehicle fuel type. Use of "other" requires the additional open ended FuelTypeOther to be filled From ba4ae59b0d9e6540605297ad6a40456a47ddb5d5 Mon Sep 17 00:00:00 2001 From: Tim Rivett Date: Wed, 16 Sep 2020 11:11:51 +0100 Subject: [PATCH 206/290] Update siri_facility-v2.0.xsd correction to annotation of TypeOfVehicleFuelEnumeration --- xsd/siri_model/siri_facility-v2.0.xsd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xsd/siri_model/siri_facility-v2.0.xsd b/xsd/siri_model/siri_facility-v2.0.xsd index 3743356d..9d8190bb 100644 --- a/xsd/siri_model/siri_facility-v2.0.xsd +++ b/xsd/siri_model/siri_facility-v2.0.xsd @@ -742,7 +742,7 @@ Rail transport, Roads and road transport - Values for Vehicle fuel type. Use of "other" requires the additional open ended FuelTypeOther to be filled + Values for Vehicle fuel type. Use of "other" requires the additional open ended VehicleFuelTypeOther to be filled From be39d91ee0c5cc1de8b814877ddf3ae4e7362df7 Mon Sep 17 00:00:00 2001 From: u215619 Date: Wed, 16 Sep 2020 14:03:01 +0200 Subject: [PATCH 207/290] AffectedSection added to AffectedNetwork choice --- xsd/siri_model/siri_situationAffects-v2.0.xsd | 36 +++++++++++++++++++ 1 file changed, 36 insertions(+) diff --git a/xsd/siri_model/siri_situationAffects-v2.0.xsd b/xsd/siri_model/siri_situationAffects-v2.0.xsd index 7f8637f9..cd1694a5 100644 --- a/xsd/siri_model/siri_situationAffects-v2.0.xsd +++ b/xsd/siri_model/siri_situationAffects-v2.0.xsd @@ -566,6 +566,16 @@ Rail transport, Roads and road transport + + + Only some Sections are affected, LINE level information not available. + + + + + + + @@ -655,6 +665,32 @@ Rail transport, Roads and road transport Reference to a section of ROUTE affected by a SITUATION. + + + Stop Poins of the SECTION. Can be either all or only affected by SITUATION. + + + + + + Indicates whether the list of STOP POINTS contains all STOP POINTS of SECTION or only affected by SITUATION. + + + + + + Stop Point of the SECTION + + + + + GIs projection of Link to the next provided StopPoint. NB Line here means Geometry Polyline, not Transmodel Transport Line. + + + + + + Spatial projection of element that can be used to show affected area on a map. From 86ee87c34ebf546e514bb78def22fc48153e0ae9 Mon Sep 17 00:00:00 2001 From: u215619 Date: Fri, 18 Sep 2020 16:09:21 +0200 Subject: [PATCH 208/290] AffectedSection added to AffectedNetwork choice --- xsd/siri_model/siri_situationAffects-v2.0.xsd | 60 +++++++------------ 1 file changed, 23 insertions(+), 37 deletions(-) diff --git a/xsd/siri_model/siri_situationAffects-v2.0.xsd b/xsd/siri_model/siri_situationAffects-v2.0.xsd index cd1694a5..da70ce50 100644 --- a/xsd/siri_model/siri_situationAffects-v2.0.xsd +++ b/xsd/siri_model/siri_situationAffects-v2.0.xsd @@ -552,29 +552,15 @@ Rail transport, Roads and road transport All LINEs in the network are affected. - + Only some ROUTEs are affected, LINE level information not available. See the RoutesAffected element for textual description. - - - - - An ordered list of MAPPING POINTs defining one single path through the road (or rail) Network. A ROUTE may pass through the same MAPPING POINT more than once. - - - - - + - Only some Sections are affected, LINE level information not available. + Only some COMMON SECTIONs are affected, LINE level information not available. - - - - - @@ -589,18 +575,18 @@ Rail transport, Roads and road transport - Type for information about the LINEs affected by a SITUATION. + Information about the individual LINEs in the network that are affected by a SITUATION. If not explicitly overrided, modes and submodes will be defaulted to any values present (i) in the AffectedNetwork (ii) in the General Context. - Operators of LINEs affected by incident. Overrides any value specified for (i) Affected Network (ii) General Context. + Restricts the affected scope to the specified operators of LINEs that are affected by the situation. Overrides any value specified for (i) Affected Network (ii) General Context. - DESTINATIONs to which the LINE runs. + Restricts the affected scope to the specified DIRECTIONs @@ -610,7 +596,7 @@ Rail transport, Roads and road transport - ROUTEs affected if LINE has multiple ROUTEs. + Restricts the affected scope to the specified ROUTEs @@ -624,7 +610,7 @@ Rail transport, Roads and road transport - Sections of LINE affected. + Restricts the affected scope to the specified LINE SECTIONs @@ -657,40 +643,40 @@ Rail transport, Roads and road transport - Type for information about the sectons affected by a SITUATION. + Type for information about the SECTIONs affected by a SITUATION. + Reference to a section of ROUTE affected by a SITUATION. - + - Stop Poins of the SECTION. Can be either all or only affected by SITUATION. + An indirect reference to a COMMON SECTION by stating the stop point ref of the first and last POINT IN JOURNEY PATTERN of the section in question. Intermediate POINTs should be added if necessary to distinguish different sections having the same start and end PONT. - - - Indicates whether the list of STOP POINTS contains all STOP POINTS of SECTION or only affected by SITUATION. - - - - + + + First Stop POINT of the SECTION + + + - Stop Point of the SECTION + Any intermediate Stop POINT of the SECTION required for identifying a SECTION - + - GIs projection of Link to the next provided StopPoint. NB Line here means Geometry Polyline, not Transmodel Transport Line. + Last Stop POINT of the SECTION - + Spatial projection of element that can be used to show affected area on a map. @@ -702,7 +688,7 @@ Rail transport, Roads and road transport - Type for information about the routes affected by a SITUATION. + An ordered list of MAPPING POINTs defining one single path through the road (or rail) Network. A ROUTE may pass through the same MAPPING POINT more than once. From e741a072df3040b6f7934fafd68e6410d374e532 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Fri, 2 Oct 2020 17:17:41 +0200 Subject: [PATCH 209/290] CR089: remove PositionOfTrainElement (NeTEx) until clarified --- xsd/siri_model/siri_journey-v2.0.xsd | 5 ----- 1 file changed, 5 deletions(-) diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index b55c7cc3..1e3f0059 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -1163,11 +1163,6 @@ It is advised to specify a reference point that is meaningful for passengers on - - - Relative position of TRAIN ELEMENT. - - Information about a change of a VEHICLE within the formation, e.g., whether a VEHICLE is open, booked or has defective doors. From 3d61e27a113644fbe524a50f3f71b1c65afdb27c Mon Sep 17 00:00:00 2001 From: Pri Date: Tue, 20 Oct 2020 13:17:31 +0200 Subject: [PATCH 210/290] rename recommendation priority --- xsd/siri_model/siri_situationActions-v2.0.xsd | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/xsd/siri_model/siri_situationActions-v2.0.xsd b/xsd/siri_model/siri_situationActions-v2.0.xsd index ae5aa9d1..c79c8f0d 100644 --- a/xsd/siri_model/siri_situationActions-v2.0.xsd +++ b/xsd/siri_model/siri_situationActions-v2.0.xsd @@ -637,12 +637,12 @@ - Further recommendation to passengers. (Unbounded since SIRI 2.0) + Further advice to passengers. (Unbounded since SIRI 2.0) - + - Prioritises a recommendation from the information owner's point of view, e.g. usable for sorting or hiding individual recommendations. + Prioritises an advice from the information owner's point of view, e.g. usable for sorting or hiding individual recommendations. 1 = highest priority. From 5aa73d51a442e0c687d28fa446d4c81fbdbf0fb0 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 20 Oct 2020 16:48:35 +0200 Subject: [PATCH 211/290] CR080: extend StopAssignmentStructure by BoardingPosition --- xsd/siri_model/siri_journey-v2.0.xsd | 111 +++++++++++++++---- xsd/siri_model/siri_journey_support-v2.0.xsd | 9 +- xsd/siri_model/siri_reference-v2.0.xsd | 25 ++++- 3 files changed, 112 insertions(+), 33 deletions(-) diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index b55c7cc3..2476b74e 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -114,6 +114,8 @@ Rail transport, Roads and road transport SIRI Common Journey Model. + + @@ -779,21 +781,21 @@ To avoid this, the producer should transmit xxxPredictionUnknown instead of any - Lower bound on time of for prediction for confidence level if different from defaults +SIRI v2.0 + Lower bound on time of for prediction for confidence level if different from defaults +SIRI v2.0 - Upper bound on time of for predictios for confidence level if different from defaults +SIRI v2.0 + Upper bound on time of for predictios for confidence level if different from defaults +SIRI v2.0 - - + + - Type for assignment of a SCHEDULED STOP POINT to a specific QUAY or platform. +SIRI v2.0. + Elements for assignment of a SCHEDULED STOP POINT to a specific QUAY or platform. +SIRI v2.1 @@ -828,26 +830,99 @@ To avoid this, the producer should transmit xxxPredictionUnknown instead of any - + - + - Type for assignment of a SCHEDULED STOP POINT to a specific QUAY or platform +SIRI v2.0. + Elements for assignment of a SCHEDULED STOP POINT to a specific BOARDING POSITION or location on a QUAY. +SIRI v2.1 - + - Physical QUAY to use according to the planned timetable. +SIRI v2.0 + Physical BOARDING POSITION to use according to the planned timetable. - + - Scheduled Platform name. +SIRI v2.0 + Scheduled BOARDING POSITION name. Can be used to indicate boarding position change. - + + + Physical BOARDING POSITION to use according to the real-time prediction. + + + + + Expected BOARDING POSITION name. Can be used to indicate real-time prediction. + + + + + Actually recorded BOARDING POSITION. Can be used to indicate the actually used boarding position. + + + + + Recorded BOARDING POSITION name. Can be used to indicate the actually used boarding position. + + + + + + + + Type for assignment of a SCHEDULED STOP POINT to a physical location, in particular to a QUAY or BOARDING POSITION. +SIRI v2.0. + + + + + + + + + + Type for assignment of a SCHEDULED STOP POINT to a physical location, in particular to a QUAY or BOARDING POSITION, according to the planned timetable. +SIRI v2.0. + + + + + + + Physical QUAY to use according to the planned timetable. +SIRI v2.0 + + + + + Scheduled Platform name. +SIRI v2.0 + + + + + + + + Physical BOARDING POSITION to use according to the planned timetable. +SIRI v2.1 + + + + + Scheduled BOARDING POSITION name. +SIRI v2.1 + + + + + + + + + + Indicates the type of a nested QUAY in case of detailed STOP PLACE models. +A QUAY may be part of a group of QUAYs, or may be divided into sectors, i.e., smaller sub-QUAYs. +SIRI v2.1 + + @@ -1005,13 +1080,6 @@ To avoid this, the producer should transmit xxxPredictionUnknown instead of any - - - - Indicates the type of the referenced QUAY. In case of detailed STOP PLACE models, a QUAY may be a nested structure. -A QUAY may be part of a group of QUAYs, or may be divided into sectors, i.e., smaller sub-QUAYs. +SIRI v2.1 - - @@ -1325,7 +1393,8 @@ If a QUAY is divided into sub-QUAYs or sectors (with the help of STOP ASSIGNMENT - The intersection of supplied elements describes the extent that the Occupancy values applies to. +SIRI v2.1 + The intersection of supplied elements describes the extent that the Occupancy values applies to. +SIRI v2.1 +Only vehicle-centric filter (measurement in a part or at an entrance of a TRAIN) are available here, but a stop-centric filtering (measurement in a sector or at a position on a QUAY) can be achieved indirectly via Arrival-/DepartureFormationAssignment. diff --git a/xsd/siri_model/siri_journey_support-v2.0.xsd b/xsd/siri_model/siri_journey_support-v2.0.xsd index 430ac845..0bb1f76c 100644 --- a/xsd/siri_model/siri_journey_support-v2.0.xsd +++ b/xsd/siri_model/siri_journey_support-v2.0.xsd @@ -848,9 +848,9 @@ Passengers don't need to change vehicles. The new journey is not communicated as - + - Allowed values for QuayType which is used to characterise the STOP ASSIGNMENTs. +SIRI v2.1 + Allowed values for characterisation of nested QUAYs as part of a STOP ASSIGNMENT. +SIRI v2.1 @@ -874,11 +874,6 @@ Passengers don't need to change vehicles. The new journey is not communicated as The first class carriage of a TRAIN might, for example, be assigned to sector "A" of a QUAY. - - - A location within a QUAY from which passengers may directly board, or onto which passengers may directly alight from a VEHICLE. - - diff --git a/xsd/siri_model/siri_reference-v2.0.xsd b/xsd/siri_model/siri_reference-v2.0.xsd index da20ab6c..a20eabcb 100644 --- a/xsd/siri_model/siri_reference-v2.0.xsd +++ b/xsd/siri_model/siri_reference-v2.0.xsd @@ -61,7 +61,7 @@ --> -

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

    +

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

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

     @@ -230,7 +230,7 @@ Rail transport, Roads and road transport - + Type for identifier of a STOP AREA. @@ -245,7 +245,7 @@ Rail transport, Roads and road transport - + Type for identifier of a QUAY (Platform, Bay, etc). @@ -260,6 +260,21 @@ Rail transport, Roads and road transport + + + + Type for identifier of a BOARDING POSITION (location on a QUAY where passengers can actually board/alight). + + + + + + Type for reference to a BOARDING POSITION. + + + + + @@ -286,7 +301,7 @@ Rail transport, Roads and road transport Whether VEHICLE is currently at stop. Default is false (xml default added from SIRI 2.0) - + Type for identifier of a CONNECTION link @@ -306,7 +321,7 @@ Rail transport, Roads and road transport - + MODEs of transport applicable to timetabled public transport. From c7418cf16af7207451d1bc35e0299e9b5ed9007c Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 20 Oct 2020 16:48:35 +0200 Subject: [PATCH 212/290] CR080: extend StopAssignmentStructure by BoardingPosition --- xsd/siri_model/siri_journey-v2.0.xsd | 111 +++++++++++++++---- xsd/siri_model/siri_journey_support-v2.0.xsd | 9 +- xsd/siri_model/siri_reference-v2.0.xsd | 25 ++++- 3 files changed, 112 insertions(+), 33 deletions(-) diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index b55c7cc3..2476b74e 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -114,6 +114,8 @@ Rail transport, Roads and road transport SIRI Common Journey Model. + + @@ -779,21 +781,21 @@ To avoid this, the producer should transmit xxxPredictionUnknown instead of any - Lower bound on time of for prediction for confidence level if different from defaults +SIRI v2.0 + Lower bound on time of for prediction for confidence level if different from defaults +SIRI v2.0 - Upper bound on time of for predictios for confidence level if different from defaults +SIRI v2.0 + Upper bound on time of for predictios for confidence level if different from defaults +SIRI v2.0 - - + + - Type for assignment of a SCHEDULED STOP POINT to a specific QUAY or platform. +SIRI v2.0. + Elements for assignment of a SCHEDULED STOP POINT to a specific QUAY or platform. +SIRI v2.1 @@ -828,26 +830,99 @@ To avoid this, the producer should transmit xxxPredictionUnknown instead of any - + - + - Type for assignment of a SCHEDULED STOP POINT to a specific QUAY or platform +SIRI v2.0. + Elements for assignment of a SCHEDULED STOP POINT to a specific BOARDING POSITION or location on a QUAY. +SIRI v2.1 - + - Physical QUAY to use according to the planned timetable. +SIRI v2.0 + Physical BOARDING POSITION to use according to the planned timetable. - + - Scheduled Platform name. +SIRI v2.0 + Scheduled BOARDING POSITION name. Can be used to indicate boarding position change. - + + + Physical BOARDING POSITION to use according to the real-time prediction. + + + + + Expected BOARDING POSITION name. Can be used to indicate real-time prediction. + + + + + Actually recorded BOARDING POSITION. Can be used to indicate the actually used boarding position. + + + + + Recorded BOARDING POSITION name. Can be used to indicate the actually used boarding position. + + + + + + + + Type for assignment of a SCHEDULED STOP POINT to a physical location, in particular to a QUAY or BOARDING POSITION. +SIRI v2.0. + + + + + + + + + + Type for assignment of a SCHEDULED STOP POINT to a physical location, in particular to a QUAY or BOARDING POSITION, according to the planned timetable. +SIRI v2.0. + + + + + + + Physical QUAY to use according to the planned timetable. +SIRI v2.0 + + + + + Scheduled Platform name. +SIRI v2.0 + + + + + + + + Physical BOARDING POSITION to use according to the planned timetable. +SIRI v2.1 + + + + + Scheduled BOARDING POSITION name. +SIRI v2.1 + + + + + + + + + + Indicates the type of a nested QUAY in case of detailed STOP PLACE models. +A QUAY may be part of a group of QUAYs, or may be divided into sectors, i.e., smaller sub-QUAYs. +SIRI v2.1 + + @@ -1005,13 +1080,6 @@ To avoid this, the producer should transmit xxxPredictionUnknown instead of any - - - - Indicates the type of the referenced QUAY. In case of detailed STOP PLACE models, a QUAY may be a nested structure. -A QUAY may be part of a group of QUAYs, or may be divided into sectors, i.e., smaller sub-QUAYs. +SIRI v2.1 - - @@ -1325,7 +1393,8 @@ If a QUAY is divided into sub-QUAYs or sectors (with the help of STOP ASSIGNMENT - The intersection of supplied elements describes the extent that the Occupancy values applies to. +SIRI v2.1 + The intersection of supplied elements describes the extent that the Occupancy values applies to. +SIRI v2.1 +Only vehicle-centric filter (measurement in a part or at an entrance of a TRAIN) are available here, but a stop-centric filtering (measurement in a sector or at a position on a QUAY) can be achieved indirectly via Arrival-/DepartureFormationAssignment. diff --git a/xsd/siri_model/siri_journey_support-v2.0.xsd b/xsd/siri_model/siri_journey_support-v2.0.xsd index 430ac845..0bb1f76c 100644 --- a/xsd/siri_model/siri_journey_support-v2.0.xsd +++ b/xsd/siri_model/siri_journey_support-v2.0.xsd @@ -848,9 +848,9 @@ Passengers don't need to change vehicles. The new journey is not communicated as - + - Allowed values for QuayType which is used to characterise the STOP ASSIGNMENTs. +SIRI v2.1 + Allowed values for characterisation of nested QUAYs as part of a STOP ASSIGNMENT. +SIRI v2.1 @@ -874,11 +874,6 @@ Passengers don't need to change vehicles. The new journey is not communicated as The first class carriage of a TRAIN might, for example, be assigned to sector "A" of a QUAY.     - - - A location within a QUAY from which passengers may directly board, or onto which passengers may directly alight from a VEHICLE. - - diff --git a/xsd/siri_model/siri_reference-v2.0.xsd b/xsd/siri_model/siri_reference-v2.0.xsd index da20ab6c..a20eabcb 100644 --- a/xsd/siri_model/siri_reference-v2.0.xsd +++ b/xsd/siri_model/siri_reference-v2.0.xsd @@ -61,7 +61,7 @@ --> -

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

    +

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

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

     @@ -230,7 +230,7 @@ Rail transport, Roads and road transport - + Type for identifier of a STOP AREA. @@ -245,7 +245,7 @@ Rail transport, Roads and road transport - + Type for identifier of a QUAY (Platform, Bay, etc). @@ -260,6 +260,21 @@ Rail transport, Roads and road transport + + + + Type for identifier of a BOARDING POSITION (location on a QUAY where passengers can actually board/alight). + + + + + + Type for reference to a BOARDING POSITION. + + + + + @@ -286,7 +301,7 @@ Rail transport, Roads and road transport Whether VEHICLE is currently at stop. Default is false (xml default added from SIRI 2.0) - + Type for identifier of a CONNECTION link @@ -306,7 +321,7 @@ Rail transport, Roads and road transport - + MODEs of transport applicable to timetabled public transport. From 05df38dc7053a0fcef0be1b34d681d0bc8a9d968 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 20 Oct 2020 17:02:06 +0200 Subject: [PATCH 213/290] CR081: extend StopAssignmentStructure by FlexibleArea --- xsd/gml/basicTypes.xsd | 267 ++++++++++++++++++ xsd/gml/geometryBasic0d1d-extract-v3_2_1.xsd | 271 +++++++++++++++++++ xsd/gml/gmlBase-extract-v3_2_1.xsd | 168 ++++++++++++ xsd/gml/gmlBasic2d-extract-v3_2_1-.xsd | 120 ++++++++ xsd/gml/gml_extract_all_objects_v_3_2_1.xsd | 12 + xsd/siri_model/siri_journey-v2.0.xsd | 56 +++- xsd/siri_model/siri_reference-v2.0.xsd | 15 + xsd/siri_utility/siri_location-v2.0.xsd | 57 ++-- 8 files changed, 947 insertions(+), 19 deletions(-) create mode 100644 xsd/gml/basicTypes.xsd create mode 100644 xsd/gml/geometryBasic0d1d-extract-v3_2_1.xsd create mode 100644 xsd/gml/gmlBase-extract-v3_2_1.xsd create mode 100644 xsd/gml/gmlBasic2d-extract-v3_2_1-.xsd create mode 100644 xsd/gml/gml_extract_all_objects_v_3_2_1.xsd diff --git a/xsd/gml/basicTypes.xsd b/xsd/gml/basicTypes.xsd new file mode 100644 index 00000000..463203ca --- /dev/null +++ b/xsd/gml/basicTypes.xsd @@ -0,0 +1,267 @@ + + + + basicTypes.xsd + See ISO/DIS 19136 8.2. +W3C XML Schema provides a set of built-in "simple" types which define methods for representing values as literals without internal markup. These are described in W3C XML Schema Part 2:2001. Because GML is an XML encoding in which instances are described using XML Schema, these simple types shall be used as far as possible and practical for the representation of data types. W3C XML Schema also provides methods for defining +- new simple types by restriction and combination of the built-in types, and +- complex types, with simple content, but which also have XML attributes. +In many places where a suitable built-in simple type is not available, simple content types derived using the XML Schema mechanisms are used for the representation of data types in GML. +A set of these simple content types that are required by several GML components are defined in the basicTypes schema, as well as some elements based on them. These are primarily based around components needed to record amounts, counts, flags and terms, together with support for exceptions or null values. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium, Inc. All Rights Reserved. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + gml:NilReasonType defines a content model that allows recording of an explanation for a void value or other exception. +gml:NilReasonType is a union of the following enumerated values: +- inapplicable there is no value +- missing the correct value is not readily available to the sender of this data. Furthermore, a correct value may not exist +- template the value will be available later +- unknown the correct value is not known to, and not computable by, the sender of this data. However, a correct value probably exists +- withheld the value is not divulged +- other:text other brief explanation, where text is a string of two or more characters with no included spaces +and +- anyURI which should refer to a resource which describes the reason for the exception +A particular community may choose to assign more detailed semantics to the standard values provided. Alternatively, the URI method enables a specific or more complete explanation for the absence of a value to be provided elsewhere and indicated by-reference in an instance document. +gml:NilReasonType is used as a member of a union in a number of simple content types where it is necessary to permit a value from the NilReasonType union as an alternative to the primary type. + + + + + + + + + + + + + + + + + + + + + + + + gml:SignType is a convenience type with values "+" (plus) and "-" (minus). + + + + + + + + + Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. + + + + + + Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. + + + + + + Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. + + + + + + Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. + + + + + + Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. + + + + + + gml:CodeType is a generalized type to be used for a term, keyword or name. +It adds a XML attribute codeSpace to a term, where the value of the codeSpace attribute (if present) shall indicate a dictionary, thesaurus, classification scheme, authority, or pattern for the term. + + + + + + + + + + gml:CodeWithAuthorityType requires that the codeSpace attribute is provided in an instance. + + + + + + + + + + gml:MeasureType supports recording an amount encoded as a value of XML Schema double, together with a units of measure indicated by an attribute uom, short for "units of measure". The value of the uom attribute identifies a reference system for the amount, usually a ratio or interval scale. + + + + + + + + + + The simple type gml:Uomidentifier defines the syntax and value space of the unit of measure identifier. + + + + + + This type specifies a character string of length at least one, and restricted such that it must not contain any of the following characters: ":" (colon), " " (space), (newline), (carriage return), (tab). This allows values corresponding to familiar abbreviations, such as "kg", "m/s", etc. +It is recommended that the symbol be an identifier for a unit of measure as specified in the "Unified Code of Units of Measure" (UCUM) (http://aurora.regenstrief.org/UCUM). This provides a set of symbols and a grammar for constructing identifiers for units of measure that are unique, and may be easily entered with a keyboard supporting the limited character set known as 7-bit ASCII. ISO 2955 formerly provided a specification with this scope, but was withdrawn in 2001. UCUM largely follows ISO 2955 with modifications to remove ambiguities and other problems. + + + + + + + + This type specifies a URI, restricted such that it must start with one of the following sequences: "#", "./", "../", or a string of characters followed by a ":". These patterns ensure that the most common URI forms are supported, including absolute and relative URIs and URIs that are simple fragment identifiers, but prohibits certain forms of relative URI that could be mistaken for unit of measure symbol . +NOTE It is possible to re-write such a relative URI to conform to the restriction (e.g. "./m/s"). +In an instance document, on elements of type gml:MeasureType the mandatory uom attribute shall carry a value corresponding to either +- a conventional unit of measure symbol, +- a link to a definition of a unit of measure that does not have a conventional symbol, or when it is desired to indicate a precise or variant definition. + + + + + + + + This type is deprecated for tuples with ordinate values that are numbers. +CoordinatesType is a text string, intended to be used to record an array of tuples or coordinates. +While it is not possible to enforce the internal structure of the string through schema validation, some optional attributes have been provided in previous versions of GML to support a description of the internal structure. These attributes are deprecated. The attributes were intended to be used as follows: +Decimal symbol used for a decimal point (default="." a stop or period) +cs symbol used to separate components within a tuple or coordinate string (default="," a comma) +ts symbol used to separate tuples or coordinate strings (default=" " a space) +Since it is based on the XML Schema string type, CoordinatesType may be used in the construction of tables of tuples or arrays of tuples, including ones that contain mixed text and numeric values. + + + + + + + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + gml:CodeListType provides for lists of terms. The values in an instance element shall all be valid according to the rules of the dictionary, classification scheme, or authority identified by the value of its codeSpace attribute. + + + + + + + + + + gml:CodeOrNilReasonListType provides for lists of terms. The values in an instance element shall all be valid according to the rules of the dictionary, classification scheme, or authority identified by the value of its codeSpace attribute. An instance element may also include embedded values from NilReasonType. It is intended to be used in situations where a term or classification is expected, but the value may be absent for some reason. + + + + + + + + + + gml:MeasureListType provides for a list of quantities. + + + + + + + + + + gml:MeasureOrNilReasonListType provides for a list of quantities. An instance element may also include embedded values from NilReasonType. It is intended to be used in situations where a value is expected, but the value may be absent for some reason. + + + + + + + + diff --git a/xsd/gml/geometryBasic0d1d-extract-v3_2_1.xsd b/xsd/gml/geometryBasic0d1d-extract-v3_2_1.xsd new file mode 100644 index 00000000..a30fa6af --- /dev/null +++ b/xsd/gml/geometryBasic0d1d-extract-v3_2_1.xsd @@ -0,0 +1,271 @@ + + + + + geometryBasic0d1d.xsd + See ISO/DIS 19136 Clause 10. +Any geometry element that inherits the semantics of AbstractGeometryType may be viewed as a set of direct positions. +All of the classes derived from AbstractGeometryType inherit an optional association to a coordinate reference system. All direct positions shall directly or indirectly be associated with a coordinate reference system. When geometry elements are aggregated in another geometry element (such as a MultiGeometry or GeometricComplex), which already has a coordinate reference system specified, then these elements are assumed to be in that same coordinate reference system unless otherwise specified. +The geometry model distinguishes geometric primitives, aggregates and complexes. +Geometric primitives, i.e. instances of a subtype of AbstractGeometricPrimitiveType, will be open, that is, they will not contain their boundary points; curves will not contain their end points, surfaces will not contain their boundary curves, and solids will not contain their bounding surfaces. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium, Inc. All Rights Reserved. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + All geometry elements are derived directly or indirectly from this abstract supertype. A geometry element may have an identifying attribute (gml:id), one or more names (elements identifier and name) and a description (elements description and descriptionReference) . It may be associated with a spatial reference system (attribute group gml:SRSReferenceGroup). +The following rules shall be adhered to: +- Every geometry type shall derive from this abstract type. +- Every geometry element (i.e. an element of a geometry type) shall be directly or indirectly in the substitution group of AbstractGeometry. + + + + + + + + + + The attribute group SRSReferenceGroup is an optional reference to the CRS used by this geometry, with optional additional information to simplify the processing of the coordinates when a more complete definition of the CRS is not needed. +In general the attribute srsName points to a CRS instance of gml:AbstractCoordinateReferenceSystem. For well-known references it is not required that the CRS description exists at the location the URI points to. +If no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of. + + + + + + + + The attributes uomLabels and axisLabels, defined in the SRSInformationGroup attribute group, are optional additional and redundant information for a CRS to simplify the processing of the coordinate values when a more complete definition of the CRS is not needed. This information shall be the same as included in the complete definition of the CRS, referenced by the srsName attribute. When the srsName attribute is included, either both or neither of the axisLabels and uomLabels attributes shall be included. When the srsName attribute is omitted, both of these attributes shall be omitted. +The attribute axisLabels is an ordered list of labels for all the axes of this CRS. The gml:axisAbbrev value should be used for these axis labels, after spaces and forbidden characters are removed. When the srsName attribute is included, this attribute is optional. When the srsName attribute is omitted, this attribute shall also be omitted. +The attribute uomLabels is an ordered list of unit of measure (uom) labels for all the axes of this CRS. The value of the string in the gml:catalogSymbol should be used for this uom labels, after spaces and forbidden characters are removed. When the axisLabels attribute is included, this attribute shall also be included. When the axisLabels attribute is omitted, this attribute shall also be omitted. + + + + + The AbstractGeometry element is the abstract head of the substitution group for all geometry elements of GML. This includes pre-defined and user-defined geometry elements. Any geometry element shall be a direct or indirect extension/restriction of AbstractGeometryType and shall be directly or indirectly in the substitution group of AbstractGeometry. + + + + + A geometric property may either be any geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same or another document). Note that either the reference or the contained element shall be given, but not both or none. +If a feature has a property that takes a geometry element as its value, this is called a geometry property. A generic type for such a geometry property is GeometryPropertyType. + + + + + + + + + + If a feature has a property which takes an array of geometry elements as its value, this is called a geometry array property. A generic type for such a geometry property is GeometryArrayPropertyType. +The elements are always contained inline in the array property, referencing geometry elements or arrays of geometry elements via XLinks is not supported. + + + + + + + + + Direct position instances hold the coordinates for a position within some coordinate reference system (CRS). Since direct positions, as data types, will often be included in larger objects (such as geometry elements) that have references to CRS, the srsName attribute will in general be missing, if this particular direct position is included in a larger element with such a reference to a CRS. In this case, the CRS is implicitly assumed to take on the value of the containing object's CRS. +if no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of, typically a geometric object like a point, curve, etc. + + + + + + + + + + + posList instances (and other instances with the content model specified by DirectPositionListType) hold the coordinates for a sequence of direct positions within the same coordinate reference system (CRS). +if no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of, typically a geometric object like a point, curve, etc. +The optional attribute count specifies the number of direct positions in the list. If the attribute count is present then the attribute srsDimension shall be present, too. +The number of entries in the list is equal to the product of the dimensionality of the coordinate reference system (i.e. it is a derived value of the coordinate reference system definition) and the number of direct positions. + + + + + + + + + + + + GML supports two different ways to specify a geometric position: either by a direct position (a data type) or a point (a geometric object). +pos elements are positions that are "owned" by the geometric primitive encapsulating this geometric position. +pointProperty elements contain a point that may be referenced from other geometry elements or reference another point defined elsewhere (reuse of existing points). + + + + + + + + + GML supports two different ways to specify a list of geometric positions: either by a sequence of geometric positions (by reusing the group definition) or a sequence of direct positions (element posList). +The posList element allows for a compact way to specify the coordinates of the positions, if all positions are represented in the same coordinate reference system. + + + + + + + + + For some applications the components of the position may be adjusted to yield a unit vector. + + + + + + + + + + + + + + + deprecated + + + + + + + + Envelope defines an extent using a pair of positions defining opposite corners in arbitrary dimensions. The first direct position is the "lower corner" (a coordinate position consisting of all the minimal ordinates for each dimension for all points within the envelope), the second one the "upper corner" (a coordinate position consisting of all the maximal ordinates for each dimension for all points within the envelope). +The use of the properties "coordinates" and "pos" has been deprecated. The explicitly named properties "lowerCorner" and "upperCorner" shall be used instead. + + + + + gml:AbstractGeometricPrimitiveType is the abstract root type of the geometric primitives. A geometric primitive is a geometric object that is not decomposed further into other primitives in the system. All primitives are oriented in the direction implied by the sequence of their coordinate tuples. + + + + + + + + The AbstractGeometricPrimitive element is the abstract head of the substitution group for all (pre- and user-defined) geometric primitives. + + + + + A property that has a geometric primitive as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + + + + + + + + + + + + A Point is defined by a single coordinate tuple. The direct position of a point is specified by the pos element which is of type DirectPositionType. + + + + + A property that has a point as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + This property element either references a point via the XLink-attributes or contains the point element. pointProperty is the predefined property which may be used by GML Application Schemas whenever a GML feature has a property with a value that is substitutable for Point. + + + + + gml:PointArrayPropertyType is a container for an array of points. The elements are always contained inline in the array property, referencing geometry elements or arrays of geometry elements via XLinks is not supported. + + + + + + + + + gml:AbstractCurveType is an abstraction of a curve to support the different levels of complexity. The curve may always be viewed as a geometric primitive, i.e. is continuous. + + + + + + + + The AbstractCurve element is the abstract head of the substitution group for all (continuous) curve elements. + + + + + A property that has a curve as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + This property element either references a curve via the XLink-attributes or contains the curve element. curveProperty is the predefined property which may be used by GML Application Schemas whenever a GML feature has a property with a value that is substitutable for AbstractCurve. + + + + + A container for an array of curves. The elements are always contained in the array property, referencing geometry elements or arrays of geometry elements via XLinks is not supported. + + + + + + + + + + + + + + + + + + + + + + + + A LineString is a special curve that consists of a single segment with linear interpolation. It is defined by two or more coordinate tuples, with linear interpolation between them. The number of direct positions in the list shall be at least two. + + + diff --git a/xsd/gml/gmlBase-extract-v3_2_1.xsd b/xsd/gml/gmlBase-extract-v3_2_1.xsd new file mode 100644 index 00000000..a870b6d7 --- /dev/null +++ b/xsd/gml/gmlBase-extract-v3_2_1.xsd @@ -0,0 +1,168 @@ + + + + gmlBase.xsd + See ISO/DIS 19136 7.2. +The gmlBase schema components establish the GML model and syntax, in particular +- a root XML type from which XML types for all GML objects should be derived, +- a pattern and components for GML properties, +- patterns for collections and arrays, and components for generic collections and arrays, +- components for associating metadata with GML objects, +- components for constructing definitions and dictionaries. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium, Inc. All Rights Reserved. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + + This element has no type defined, and is therefore implicitly (according to the rules of W3C XML Schema) an XML Schema anyType. It is used as the head of an XML Schema substitution group which unifies complex content and certain simple content elements used for datatypes in GML, including the gml:AbstractGML substitution group. + + + + + The abstract element gml:AbstractGML is "any GML object having identity". It acts as the head of an XML Schema substitution group, which may include any element which is a GML feature, or other object, with identity. This is used as a variable in content models in GML core and application schemas. It is effectively an abstract superclass for all GML objects. + + + + + + + + + + + + + + + + + + XLink components are the standard method to support hypertext referencing in XML. An XML Schema attribute group, gml:AssociationAttributeGroup, is provided to support the use of Xlinks as the method for indicating the value of a property by reference in a uniform manner in GML. + + + + + + Applying this pattern shall restrict the multiplicity of objects in a property element using this content model to exactly one. An instance of this type shall contain an element representing an object, or serve as a pointer to a remote object. +Applying the pattern to define an application schema specific property type allows to restrict +- the inline object to specified object types, +- the encoding to "by-reference only" (see 7.2.3.7), +- the encoding to "inline only" (see 7.2.3.8). + + + + + + + + + + + + Encoding a GML property inline vs. by-reference shall not imply anything about the "ownership" of the contained or referenced GML Object, i.e. the encoding style shall not imply any "deep-copy" or "deep-delete" semantics. To express ownership over the contained or referenced GML Object, the gml:OwnershipAttributeGroup attribute group may be added to object-valued property elements. If the attribute group is not part of the content model of such a property element, then the value may not be "owned". +When the value of the owns attribute is "true", the existence of inline or referenced object(s) depends upon the existence of the parent object. + + + + + + This element shows how an element + declaration may include a Schematron constraint to limit the property to act + in either inline or by-reference mode, but not both. + + + + + gml:abstractReference may be used as the head of a subtitution group of more specific elements providing a value by-reference. + + + + + gml:ReferenceType is intended to be used in application schemas directly, if a property element shall use a "by-reference only" encoding. + + + + + + + gml:abstractInlineProperty may be used as the head of a subtitution group of more specific elements providing a value inline. + + + + + + + + + + + If the value of an object property is another object and that object contains also a property for the association between the two objects, then this name of the reverse property may be encoded in a gml:reversePropertyName element in an appinfo annotation of the property element to document the constraint between the two properties. The value of the element shall contain the qualified name of the property element. + + + + + The value of this property is a remote text description of the object. The xlink:href attribute of the gml:descriptionReference property references the external description. + + + + + The gml:name property provides a label or identifier for the object, commonly a descriptive name. An object may have several names, typically assigned by different authorities. gml:name uses the gml:CodeType content model. The authority for a name is indicated by the value of its (optional) codeSpace attribute. The name may or may not be unique, as determined by the rules of the organization responsible for the codeSpace. In common usage there will be one name per authority, so a processing application may select the name from its preferred codeSpace. + + + + + Often, a special identifier is assigned to an object by the maintaining authority with the intention that it is used in references to the object For such cases, the codeSpace shall be provided. That identifier is usually unique either globally or within an application domain. gml:identifier is a pre-defined property for such identifiers. + + + + + The attribute gml:id supports provision of a handle for the XML element representing a GML Object. Its use is mandatory for all GML objects. It is of XML type ID, so is constrained to be unique in the XML document within which it occurs. + + + + + To create a collection of GML Objects that are not all features, a property type shall be derived by extension from gml:AbstractMemberType. +This abstract property type is intended to be used only in object types where software shall be able to identify that an instance of such an object type is to be interpreted as a collection of objects. +By default, this abstract property type does not imply any ownership of the objects in the collection. The owns attribute of gml:OwnershipAttributeGroup may be used on a property element instance to assert ownership of an object in the collection. A collection shall not own an object already owned by another object. + + + + + + + A GML Object Collection is any GML Object with a property element in its content model whose content model is derived by extension from gml:AbstractMemberType. +In addition, the complex type describing the content model of the GML Object Collection may also include a reference to the attribute group gml:AggregationAttributeGroup to provide additional information about the semantics of the object collection. This information may be used by applications to group GML objects, and optionally to order and index them. +The allowed values for the aggregationType attribute are defined by gml:AggregationType. See 8.4 of ISO/IEC 11404:1996 for the meaning of the values in the enumeration. + + + + + + + + + + + + + + + + To associate metadata described by any XML Schema with a GML object, a property element shall be defined whose content model is derived by extension from gml:AbstractMetadataPropertyType. +The value of such a property shall be metadata. The content model of such a property type, i.e. the metadata application schema shall be specified by the GML Application Schema. +By default, this abstract property type does not imply any ownership of the metadata. The owns attribute of gml:OwnershipAttributeGroup may be used on a metadata property element instance to assert ownership of the metadata. +If metadata following the conceptual model of ISO 19115 is to be encoded in a GML document, the corresponding Implementation Specification specified in ISO/TS 19139 shall be used to encode the metadata information. + + + + + + + + + diff --git a/xsd/gml/gmlBasic2d-extract-v3_2_1-.xsd b/xsd/gml/gmlBasic2d-extract-v3_2_1-.xsd new file mode 100644 index 00000000..fabab137 --- /dev/null +++ b/xsd/gml/gmlBasic2d-extract-v3_2_1-.xsd @@ -0,0 +1,120 @@ + + + + geometryBasic2d.xsd + See ISO/DIS 19136 Clause 10. + + GML is an OGC Standard. + Copyright (c) 2007,2010 Open Geospatial Consortium, Inc. All Rights Reserved. + To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + gml:AbstractSurfaceType is an abstraction of a surface to support the different levels of complexity. A surface is always a continuous region of a plane. + + + + + + + + The AbstractSurface element is the abstract head of the substitution group for all (continuous) surface elements. + + + + + A property that has a surface as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + This property element either references a surface via the XLink-attributes or contains the surface element. surfaceProperty is the predefined property which may be used by GML Application Schemas whenever a GML feature has a property with a value that is substitutable for AbstractSurface. + + + + + gml:SurfaceArrayPropertyType is a container for an array of surfaces. The elements are always contained in the array property, referencing geometry elements or arrays of geometry elements via XLinks is not supported. + + + + + + + + + + + + + + + + + + + A Polygon is a special surface that is defined by a single surface patch (see D.3.6). The boundary of this patch is coplanar and the polygon uses planar interpolation in its interior. +The elements exterior and interior describe the surface boundary of the polygon. + + + + + A boundary of a surface consists of a number of rings. In the normal 2D case, one of these rings is distinguished as being the exterior boundary. In a general manifold this is not always possible, in which case all boundaries shall be listed as interior boundaries, and the exterior will be empty. + + + + + A boundary of a surface consists of a number of rings. The "interior" rings separate the surface / surface patch from the area enclosed by the rings. + + + + + + + An abstraction of a ring to support surface boundaries of different complexity. +The AbstractRing element is the abstract head of the substituition group for all closed boundaries of a surface patch. + + + + + A property with the content model of gml:AbstractRingPropertyType encapsulates a ring to represent the surface boundary property of a surface. + + + + + + + + + + + + + + + + + + + + + + + A LinearRing is defined by four or more coordinate tuples, with linear interpolation between them; the first and last coordinates shall be coincident. The number of direct positions in the list shall be at least four. + + + + + A property with the content model of gml:LinearRingPropertyType encapsulates a linear ring to represent a component of a surface boundary. + + + + + + diff --git a/xsd/gml/gml_extract_all_objects_v_3_2_1.xsd b/xsd/gml/gml_extract_all_objects_v_3_2_1.xsd new file mode 100644 index 00000000..4f8fa068 --- /dev/null +++ b/xsd/gml/gml_extract_all_objects_v_3_2_1.xsd @@ -0,0 +1,12 @@ + + + + + + + + + + + + diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index 2476b74e..4685ade2 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -1,6 +1,6 @@ - + @@ -119,6 +119,7 @@ Rail transport, Roads and road transport + @@ -793,6 +794,55 @@ To avoid this, the producer should transmit xxxPredictionUnknown instead of any + + + Area that encompasses the scheduled flexible stop locations according to the planned timetable. +SIRI v2.1 + + + + + Reference to the scheduled location or flexible area. +SIRI v2.1 + + + + + Name or description (e.g. address) of the scheduled location or flexible area. +SIRI v2.1 + + + + + + Elements for location of flexible stops or service that allows pickup anywhere in a designated area. +SIRI v2.1 + + + + + + + + Area that encompasses the expected flexible stop locations according to the real-time prediction. + + + + + + Name or description (e.g. address) of the expected location or flexible area. + + + + + Area that encompasses the actually recorded flexible stop locations. + + + + + + Name or description (e.g. address) of the actually recorded location or flexible area. + + + + + Elements for assignment of a SCHEDULED STOP POINT to a specific QUAY or platform. +SIRI v2.1 @@ -879,6 +929,7 @@ To avoid this, the producer should transmit xxxPredictionUnknown instead of any + @@ -914,6 +965,9 @@ To avoid this, the producer should transmit xxxPredictionUnknown instead of any + + + diff --git a/xsd/siri_model/siri_reference-v2.0.xsd b/xsd/siri_model/siri_reference-v2.0.xsd index a20eabcb..ffdaccaa 100644 --- a/xsd/siri_model/siri_reference-v2.0.xsd +++ b/xsd/siri_model/siri_reference-v2.0.xsd @@ -275,6 +275,21 @@ Rail transport, Roads and road transport + + + + Type for identifier of a FLEXIBLE AREA (area that encompasses the stop location of a flexible service). + + + + + + Type for reference to a FLEXIBLE AREA. + + + + + diff --git a/xsd/siri_utility/siri_location-v2.0.xsd b/xsd/siri_utility/siri_location-v2.0.xsd index 89065cbd..53cc40b9 100644 --- a/xsd/siri_utility/siri_location-v2.0.xsd +++ b/xsd/siri_utility/siri_location-v2.0.xsd @@ -1,5 +1,5 @@ - + @@ -72,6 +72,10 @@ Rail transport, Roads and road transport SIRI Framewrok Location Types. + + + + @@ -107,17 +111,17 @@ Rail transport, Roads and road transport - Longitude from Greenwich Meridian. -180 (East) to +180 (West). + Longitude from Greenwich Meridian. -180 (West) to +180 (East). Decimal degrees, e.g. 2.356 - Latitude from equator. -90 (South) to +90 (North). + Latitude from equator. -90 (South) to +90 (North). Decimal degrees, e.g. 56.356 - Altitude. + Altitude metres from sea level. @@ -141,7 +145,7 @@ Rail transport, Roads and road transport GML Spatial coordinate reference system. - + Type for gepspatial Position of a point. May be expressed in concrete WGS 84 Coordinates or any gml compatible point coordinates format. @@ -149,16 +153,7 @@ Rail transport, Roads and road transport - - - Longitude from Greenwich Meridian. -180 (West) to +180 (East). Decimal degrees. eg 2.356 - - - - - Latitude from equator. -90 (South) to +90 (North). Decimal degrees. eg 56.356 - - + @@ -166,6 +161,11 @@ Rail transport, Roads and road transport + + + Radius in case the location is specified as a circular area. In meters. +SIRI v2.1 + + Precision for point measurement. In meters. @@ -211,13 +211,34 @@ Lower right corner. - A geospatial point. +SIRI v2.0 - -. + A geospatial point. +SIRI v2.0 + + + Bounding box, circular area or gml:polyon of the area where stops of a flexible service are called. +SIRI v2.1 +A flexible area is used in cases where a pre-booked service allows pick-up/drop-off anywhere in a designated area and provides a possible interchange to a higher-frequency service. + + + + + Flexible area specified as a rectangular bounding box. + + + + + Flexible area specified as a circular area (center coordinates and radius). + + + + + Flexible area specified as a gml:Polygon that consists of an interior and exterior linear ring. + + + + From 3624ba1d1f4c7ee92615dc704e4c7f292d97c501 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Mon, 26 Oct 2020 16:29:09 +0100 Subject: [PATCH 214/290] CR082: harmonize RecordedCallStr. and clean-up references --- .../siri_datedVehicleJourney-v2.0.xsd | 12 +- .../siri_estimatedVehicleJourney-v2.0.xsd | 211 ++++-------- xsd/siri_model/siri_journey-v2.0.xsd | 303 ++++++++---------- .../siri_monitoredVehicleJourney-v2.0.xsd | 37 +-- 4 files changed, 212 insertions(+), 351 deletions(-) diff --git a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd index 8488d5a2..ea503082 100644 --- a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd @@ -257,7 +257,7 @@ Rail transport, Roads and road transport - + @@ -341,7 +341,7 @@ Rail transport, Roads and road transport - + @@ -635,11 +635,13 @@ Rail transport, Roads and road transport Whether this interchange is an addition to the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the interchange is not an addition. +SIRI v2.1 - + - Whether this interchange is a cancellation of a previously announced interchange (or planned according to the long-term timetable. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the interchange is not cancelled. +SIRI v2.1 + Whether this interchange is a cancellation of a previously announced interchange (or planned according to the long-term timetable. +Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the interchange is not cancelled. +SIRI v2.1 - + + The data producer must provide a reason, e.g. type of error and description, in case he wants to silently remove (instead of cancel) a journey or an interchange from the plan. +SIRI v2.1 diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index 196e22e8..831d0e96 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -169,22 +169,9 @@ DEPRECATED from SIRI 2.0 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'. - - - - - Can be used to inform the passenger about the reason for a change of the prediction (in)accuracy in case PredictionInaccurate is set to 'true'. +SIRI v2.1 - - - - - An approximate figure of how occupied the journey is after departing from a given stop, e.g. 'manySeatsAvailable' or 'standingRoomOnly'. If omitted: Passenger load is unknown. -Occupancies and capacities for individual VEHICLEs, e.g. parts of a COMPOUND TRAIN, can also be specified in more detail for the departure on CALL level. - - + + + @@ -408,11 +395,24 @@ the original journey and the nature of the difference. + Ordered sequence of SCHEDULED STOP POINTs called at by the VEHICLE JOURNEY. If IsCompleteStopSequence is false, may be just those stops that are altered. + + + This ESTIMATED CALL is an addition to the respective journey in the production timetable or to the previously sent prediction. If omitted: CALL is planned. + + + + + This ESTIMATED CALL is a cancellation of a previously announced call. + + + + Type for real-time info about a VEHICLE JOURNEY Stop. @@ -420,16 +420,8 @@ the original journey and the nature of the difference. - - - This call is additional and unplanned. If omitted: CALL is planned. - - - - - This call is a cancellation of a previously announced call. - - + + @@ -444,22 +436,9 @@ the original journey and the nature of the difference. 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] - - - - - Can be used to inform the passenger about the reason for a change of the prediction (in)accuracy in case PredictionInaccurate is set to 'true'. +SIRI v2.1 - - - - - An approximate figure of how occupied the journey is after departing from a given stop, e.g. 'manySeatsAvailable' or 'standingRoomOnly'. If omitted: Passenger load is unknown. -Occupancies and capacities for individual VEHICLEs, e.g. parts of a COMPOUND TRAIN, can also be specified in more detail for the departure on CALL level. - - + + + @@ -468,107 +447,6 @@ Occupancies and capacities for individual VEHICLEs, e.g. parts of a COMPOUND TRA Ordered sequence of SCHEDULED STOP POINTs called at by the VEHICLE JOURNEY. Only used if observed stop data is being recorded. (SIRI 2.0) - - - Information relating to recorded real-time properties of call. - - - - - - - - Classification of the timeliness of the visit according to a fixed list of values. If not specified, same as DepartureStatus. +SIRI v2.1 - - - - - Text annotation to be used in cases where ArrivalStatus is set to 'cancelled'. +SIRI v2.1 - - - - - Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicle to arrive at. Inheritable property. Can be omitted if the same as the DeparturePlatformName. If there is no arrival platform name separate from the departure platform name, the precedence is -(i) any arrival platform on any related dated timetable element, -(ii) any departure platform name on this estimated element; -(iii) any departure platform name on any related dated timetable CALL. - - - - - Type of alighting at stop, e.g. alighting, noAlighting or passThru. +SIRI v2.1 - - - - - Assignment of arrival of Scheduled STOP POINT to a physical QUAY (platform). If not given, assume same as for departure. +SIRI v2.1 - - - - - Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). If not given, assume same as for departure. +SIRI v2.1 - - - - - Target departure time of VEHICLE according to latest working timetable. - - - - - Estimated time of departure of VEHICLE. - - - - - Bay or platform (QUAY) name from which VEHICLE will depart. Inherited property. - - - - - Estimated time of departure of VEHICLE. - - - - - 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. +SIRI v2.1 - - - - - Text annotation to be used in cases where DepartureStatus is set to 'cancelled'. +SIRI v2.1 - - - - - Nature of boarding at stop, e.g. boarding, noBoarding or passThru. +SIRI v2.1 - - - - - Assignment of departure platform for Scheduled STOP POINT to a physical QUAY. +SIRI v2.1 - - - - - Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). +SIRI v2.1 - - - - - Recorded occupancies of a VEHICLE and reserved seats after departing from a given stop. +SIRI v2.1 - - - - - Recorded capacities of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. +SIRI v2.1 - - - - - - - Type for recroded Real-time info about a VEHICLE JOURNEY Stop. @@ -576,21 +454,48 @@ Occupancies and capacities for individual VEHICLEs, e.g. parts of a COMPOUND TRA - - - This call is additional and unplanned. If omitted: CALL is planned. - - - - - This call is a cancellation of a previously announced call. - - + + + + + Information relating to recorded real-time properties of call. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index b55c7cc3..ec239101 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -25,14 +25,14 @@ 2007-03-29 2008-11-13 - Correct Cardinalities on SIRI DESTINATION REF Structure + 2011-04-18 - siri_journey-v2.0.xsd (l.1015). FramedVehicleJourneyRef isn't mandatory in MonitoredCall SIRI-SM answer accourding to CEN TS (prCEN/TS 15531-3:2006 (E) p.56). Make optional. RV ixxx.com + 2012-03-22 - SIRI 2.0 + 2012-04-27 - SIRI 2.0 + 2013-01-25 - WB: elements LowerTimeLimit and UpperTimeLimit optional in prediction quality + 2013-02-11 - ArrivalStopAssignment and DepartureStopAssignment added to DatedCall: SIRI:PT - Correction: DestinationDisplay unbounded to allow multiple languages + 2014-06-20 - [ch] Add origin display wherever destination display as per Cologne meeting (siri-Journey-v2.0.xsd - * [xh[ Add OriginAtDestination wherever destination display as per Cologne meeting (siri-Journey-v2.0.xsd) +

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

    @@ -86,7 +86,7 @@ http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types-v2.0.xsd - Unclassified + CEN, VDV, RTIG 2004-2012 @@ -410,7 +410,7 @@ Rail transport, Roads and road transport - Elements describing the the targeted CALL of a VEHICLE at a stop. + Elements describing the targeted CALL of a VEHICLE at a stop. @@ -421,7 +421,7 @@ Rail transport, Roads and road transport - Elements describing the the arrival of a VEHICLE at a stop. + Elements describing the arrival of a VEHICLE at a stop. @@ -429,40 +429,24 @@ Rail transport, Roads and road transport - Assignment of arrival of Scheduled STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. +SIRI v2.0. - - - - - Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). If not given, assume same as for departure. +SIRI v2.1 - - - - - OPERATORs of of servcie up until arrival.. May change for departure. +SIRI v2.0. + Assignment of planned arrival at scheduled STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. +SIRI v2.0. + + - Elements describing the the departure of a VEHICLE from a stop. + Elements describing the departure of a VEHICLE from a stop. - - - Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). +SIRI v2.1 - - - - - OPERATORs of of service for departure and onwards.. May change from that for arrival. +SIRI v2.0. - - + + @@ -476,101 +460,40 @@ Rail transport, Roads and road transport - Elements describing the the arrival status of a VEHICLE at a stop. + Elements describing the arrival status of a VEHICLE at a stop. - - - Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicel to arrive at.Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is -(i) any arrival platform on any related dated timetable element, -(ii) any departure platform name on this estimated element; -(iii) any departure platform name on any related dated timetable CALL. - - - - - Nature of boarding and alighting allowed at stop. Default is 'Alighting'. - - + + - Assignment of arrival of Scheduled STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. +SIRI v2.0. - - - - - Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). If not given, assume same as for departure. +SIRI v2.1 - - - - - Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. +SIRI v2.1 -Examples: -- "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle arriving at sector A first when approaching the QUAY with sectors A-B-C-D. If the arriving vehicle is represented as an arrow, "towards A" would be abstracted as "=> A-B-C-D". -- "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle arriving at this reference point first when approaching the QUAY. If the arriving vehicle is represented as an arrow, "towards 0" would be abstracted as "=> 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). -It is advised to specify a reference point that is meaningful for passengers on location. - - - - - - OPERATORs of of servcie up until arrival.. May change for departure. +SIRI v2.0. + Assignment of planned, expected and/or recorded arrival at STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. +SIRI v2.0. + + + - Elements describing the the departure status of a VEHICLE from a stop. + Elements describing the departure status of a VEHICLE from a stop. - - - Departure QUAY (Bay or platform) name. Default taken from planned timetable.. - - + - - - Assignment of departure platfiorm for Scheduled STOP POINT to a physical QUAY. +SIRI v2.0. - - - - - Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). +SIRI v2.1 - - - - - Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. +SIRI v2.1 -Examples: -- "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle departing in the direction of sector A on a QUAY with sectors A-B-C-D. If the departing vehicle is represented as an arrow, "towards A" would be abstracted as "<= A-B-C-D". -- "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle departing in the direction of this reference point. If the departing vehicle is represented as an arrow, "towards 0" would be abstracted as "<= 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). -It is advised to specify a reference point that is meaningful for passengers on location. - - - - - - Real-time occupancies of a VEHICLE and reservations after departing from a given stop. +SIRI v2.1 - - - - - Real-time capacities (number of available seats) of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. +SIRI v2.1 - - - - - OPERATORs of of service for departure and onwards.. May change from that for arrival. +SIRI v2.0. - - + + + + + + @@ -693,18 +616,10 @@ To avoid this, the producer should transmit xxxPredictionUnknown instead of any Elements for departure in ONWARD CALL.     - - - Target departure time of VEHICLE according to latest working timetable. - - + - - - Estimated time of departure of VEHICLE, most likely taking into account all control actions such as waiting. - - + Expected departure time of VEHICLE without waiting time due to operational actions. For people at stop this would normally be shown if different from Expected departure time. So if servcie decides not to wait may leave earler than expected departure time +SIRI v2.0. @@ -848,6 +763,25 @@ To avoid this, the producer should transmit xxxPredictionUnknown instead of any + + + + Whether the prediction for a stop or the whole journey is considered to be of useful accuracy or not. Default is 'false'. + Whether the prediction for the specific stop is considered to be of a useful accuracy or not. Default is 'false', i.e. prediction is considered to be accurate. +If prediction is degraded, e.g. because of a situation, PredictionInaccurate is used to indicate a lowered quality of data. Inherited property. PredictionInaccurate can be used in combination with InCongestion, but is more general. + + + + + Can be used to inform the passenger about the reason for a change of the prediction (in)accuracy in case PredictionInaccurate is set to 'true'. +SIRI v2.1 + + + + + An approximate figure of how occupied the journey is after departing from a given stop, e.g. 'manySeatsAvailable' or 'standingRoomOnly'. If omitted: Passenger load is unknown. +Occupancies and capacities for individual VEHICLEs, e.g. parts of a COMPOUND TRAIN, can also be specified in more detail for the departure on CALL level. + + @@ -881,7 +815,11 @@ To avoid this, the producer should transmit xxxPredictionUnknown instead of any - 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. + Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicle to arrive at. +Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is: +(i) any arrival platform on any related dated timetable element, +(ii) any departure platform name on this estimated element; +(iii) any departure platform name on any related dated timetable CALL. @@ -889,27 +827,36 @@ To avoid this, the producer should transmit xxxPredictionUnknown instead of any Type of boarding and alighting allowed at stop. Default is 'Alighting'.     + + + Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). If not given, assume same as for departure. +SIRI v2.1 + + + + + Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. +SIRI v2.1 +Examples: +- "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle arriving at sector A first when approaching the QUAY with sectors A-B-C-D. If the arriving vehicle is represented as an arrow, "towards A" would be abstracted as "=> A-B-C-D". +- "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle arriving at this reference point first when approaching the QUAY. If the arriving vehicle is represented as an arrow, "towards 0" would be abstracted as "=> 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). +It is advised to specify a reference point that is meaningful for passengers on location. + + + + + + OPERATORs of of service up until arrival. May change for departure. +SIRI v2.0. + + + Arrival times for CALL. - - - Target arrival time of VEHICLE according to latest working timetable. - - + - - - Observed time of arrival of VEHICLE. - - - - - Estimated time of arriival of VEHICLE. - - + + @@ -926,17 +873,17 @@ To avoid this, the producer should transmit xxxPredictionUnknown instead of any - Estimated time of departure of VEHICLE from stop. + Estimated time of departure of VEHICLE from stop, most likely taking into account all control actions such as waiting. - Latest target time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data) If absent assume to be the same as Earliest expected departure time, +SIRI 2.0 + Latest target time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. +SIRI 2.0 - Latest expected time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data) If absent assume to be the same as Earliest expected departure time, +SIRI 2.0 + Latest expected time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. +SIRI 2.0 @@ -956,7 +903,7 @@ To avoid this, the producer should transmit xxxPredictionUnknown instead of any - Departure QUAY ( Bay or platform) name. Inheritable property. + Departure QUAY (bay or platform) name. Default taken from planned timetable. @@ -964,45 +911,65 @@ To avoid this, the producer should transmit xxxPredictionUnknown instead of any Nature of boarding allowed at stop. Default is 'Boarding'. + + + Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). +SIRI v2.1 + + + + + Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. +SIRI v2.1 +Examples: +- "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle departing in the direction of sector A on a QUAY with sectors A-B-C-D. If the departing vehicle is represented as an arrow, "towards A" would be abstracted as "<= A-B-C-D". +- "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle departing in the direction of this reference point. If the departing vehicle is represented as an arrow, "towards 0" would be abstracted as "<= 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). +It is advised to specify a reference point that is meaningful for passengers on location. + + + + + Real-time occupancies of a VEHICLE and reservations after departing from a given stop. +SIRI v2.1 + + + + + Real-time capacities (number of available seats) of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. +SIRI v2.1 + + + + + OPERATORs of service for departure and onwards. May change from that for arrival. +SIRI v2.0. + + + + + Recorded occupancies of a VEHICLE and reserved seats after departing from a given stop. +SIRI v2.1 + + + + + Recorded capacities of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. +SIRI v2.1 + + + Departure times for CALL. - - - Target departure time of VEHICLE according to latest working timetable. - - + - - - Observed time of departure of VEHICLE from stop. - - - - - Estimated time of departure of VEHICLE from stop. May include waiting time. For people on a VEHICLE this is the time that would normally be shown. - - + + - Passenget arrivel times at STOP PLACE in order to meet VEHICLEdeparture times for CALL. + Passenger arrival times at STOP PLACE in order to meet VEHICLE departure times for CALL. - - - Target Latest time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times as itmay include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data) If absent assume to be the same as Earliest expected departure time, +SIRI v2.0 - - - - - Expected Latest time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times as it may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data) If absent assume to be the same as Earliest expected departure time, +SIRI v2.0 - - + + diff --git a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd index cba57977..d0a1aca4 100644 --- a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd @@ -24,14 +24,14 @@ 2007-03-29 2008-11-13 - Correct Cardinalities on SIRI DESTINATION REF Structure + 2011-04-18 - siri_journey-v2.0.xsd (l.1015). FramedVehicleJourneyRef isn't mandatory in MonitoredCall SIRI-SM answer accourding to CEN TS (prCEN/TS 15531-3:2006 (E) p.56). Make optional. RV ixxx.com + 2012-03-22 - SIRI 2.0 + 2012-04-27 - SIRI 2.0 - [MTA] Add DIstanceFromSTop and NumberOfStops away to MonitoredCall and OnwardsCall : SIRI-SM and SIRI-ET + 2012-04-27 - SIRI 2.0 - [SE] Add Vehicle Status +

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

    @@ -75,7 +75,7 @@ http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types-v2.0.xsd - Unclassified + CEN, VDV, RTIG 2004-2012 @@ -153,16 +153,8 @@ Rail transport, Roads and road transport Whether the panic alarm on the VEHICLE is activated. This may lead to indeterminate predictions. If absent, default is 'false'. - - - Whether the prediction should be judged as inaccurate. - - - - - Can be used to inform the passenger about the reason for a change of the prediction (in)accuracy in case PredictionInaccurate is set to 'true'. +SIRI v2.1 - - + + System originating real-time data. Can be used to make judgements of relative quality and accuracy compared to other feeds. @@ -210,12 +202,7 @@ Rail transport, Roads and road transport Whether the engine of the vehicle is on. Default is 'true' (+SIRI 2.0) - - - An approximate figure of how occupied the journey is across all of its stops, e.g. 'manySeatsAvailable' or 'standingRoomOnly'. If omitted: Passenger load is unknown. -Occupancies and capacities for individual VEHICLEs, e.g. parts of a COMPOUND TRAIN, can also be specified in more detail for the departure on CALL level. - - + Delay of VEHICLE against schedule, to a precision in seconds. Early times are shown as negative values. From 09fcd0f265c95456544be2bd54bc71b44a5765c2 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 28 Oct 2020 16:53:29 +0100 Subject: [PATCH 215/290] CR047: clean-up and update annotation --- xsd/siri_productionTimetable_service.xsd | 51 ++++++++++-------------- 1 file changed, 22 insertions(+), 29 deletions(-) diff --git a/xsd/siri_productionTimetable_service.xsd b/xsd/siri_productionTimetable_service.xsd index ec9ddb64..704524ac 100644 --- a/xsd/siri_productionTimetable_service.xsd +++ b/xsd/siri_productionTimetable_service.xsd @@ -143,19 +143,7 @@ Rail transport, Roads and road transport 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 by the data producer. If omitted, then the configured data horizon applies. -Since the end of an OPERATING DAY of one ITCS does not usually coincide with the end of another ITCS, it may happen that data cannot be provided for the complete time frame requested by a subscriber. -In order for the data consumer to be aware of this situation, the data producer should confirm - in each returned timetable - for which part of the requested ValidityPeriod he can actually deliver journey schedules. -If the requested period is so far in the past that the data producer does no longer have any data, he should reject the subscription with “Status=false" and a BeyondDataHorizon ErrorCondition. -If the requested period is so far in the future that the data producer does not yet have any data, he will deliver data as soon as it is available. - -A timetable falls inside the ValidityPeriod if all of its journeys fall inside it. -A journey falls inside the ValidityPeriod if the AimedDepartureTime at its first CALL (i.e. at the origin stop) lies between the Start- and EndTime of the ValidityPeriod (regardless of whether the AimedArrivalTime at a subsequent CALL falls ouside of the ValidityPeriod). -Careful: Journeys which themselves fall outside the ValidityPeriod, but which are linked to a journey within the ValidityPeriod by a JOURNEY RELATION, are also regarded as falling inside the ValidityPeriod. Examples are journeys where the vehicle is split or joins with or is replaced by another vehicle. - - + Communicate only differences to the timetable specified by this VERSION of the TIMETABLe. @@ -293,22 +281,7 @@ If false each subscription response will contain the full information as specifi Timetable Version. - - - Start and end of timetable validity (time window) of journeys for which schedules are to be returned by the data producer. +SIRI v2.1 -The ValidityPeriod of the timetable must not exceed the ValidityPeriod requested by the subscriber. -If omitted, then the full - by the subscriber requested - ValidityPeriod or configured data horizon applies. - -Since the end of an OPERATING DAY of one ITCS does not usually coincide with the end of another ITCS, it may happen that data cannot be provided for the complete time frame requested by a subscriber. -In order for the data consumer to be aware of this situation, the data producer should confirm - in each returned timetable - for which part of the requested ValidityPeriod he can actually deliver journey schedules. -If the requested period is so far in the past that the data producer does no longer have any data, he should reject the subscription with “Status=false" and a BeyondDataHorizon ErrorCondition. -If the requested period is so far in the future that the data producer does not yet have any data, he will deliver data as soon as it is available. - -A timetable falls inside the ValidityPeriod if all of its journeys fall inside it. -A journey falls inside the ValidityPeriod if the AimedDepartureTime at its first CALL (i.e. at the origin stop) lies between the Start- and EndTime of the ValidityPeriod (regardless of whether the AimedArrivalTime at a subsequent CALL falls ouside of the ValidityPeriod). -Careful: Journeys which themselves fall outside the ValidityPeriod, but which are linked to a journey within the ValidityPeriod by a JOURNEY RELATION, are also regarded as falling inside the ValidityPeriod. Examples are journeys where the vehicle is split or joins with or is replaced by another vehicle. - - + Minimum interval at which updates for this DATED TIMETABLE VERSION FRAME can be sent. +SIRI v2.1 @@ -335,6 +308,26 @@ Careful: Journeys which themselves fall outside the ValidityPeriod, but which ar + + + Start and end of timetable validity (time window) of journeys for which schedules are to be returned by the data producer. +The ValidityPeriod of the timetable must not exceed the ValidityPeriod requested by the subscriber. +If omitted, then the full - by the subscriber requested - ValidityPeriod or configured data horizon applies. + +Since the end of an OPERATING DAY of one ITCS does not usually coincide with the end of another ITCS, it may happen that data cannot be provided for the complete time frame requested by a subscriber. +In order for the data consumer to be aware of this situation, the data producer should confirm - in each returned timetable - for which part of the requested ValidityPeriod he can actually deliver journey schedules. +If the requested period is so far in the past that the data producer does no longer have any data, he should reject the subscription with "Status=false" and a BeyondDataHorizon ErrorCondition. +If the requested period is so far in the future that the data producer does not yet have any data, he will deliver data as soon as it is available. + +A timetable falls inside the ValidityPeriod if all of its journeys fall inside it. +A journey falls inside the ValidityPeriod if the AimedDepartureTime or AimedArrivalTime at any CALL lies between the Start- and EndTime of the ValidityPeriod (regardless of whether the aimed times at a previous or subsequent CALL fall ouside of the ValidityPeriod). +Careful: Journeys which themselves fall outside the ValidityPeriod, but which are linked to a journey within the ValidityPeriod by a JOURNEY RELATION, are also regarded as falling inside the ValidityPeriod. Examples are journeys where the vehicle is split or joins with or is replaced by another vehicle. + + + + + + From 0fe50f3f3ed82148675cb44247298e05fc202c07 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Thu, 29 Oct 2020 21:11:24 +0100 Subject: [PATCH 216/290] rename schema files, update status/version and clean-up --- xsd/ReadMe.txt | 66 +- xsd/{Siri-2.0.spp => Siri.spp} | 124 +- xsd/{Siri-2.0.xpr => Siri.xpr} | 94 +- ...bility-v0.3.xsd => acsb_accessibility.xsd} | 10 +- xsd/acsb/{acsb_all-v0.3.xsd => acsb_all.xsd} | 6 +- ...itations-v0.2.xsd => acsb_limitations.xsd} | 4 +- ...ty-v0.3.xsd => acsb_passengerMobility.xsd} | 4 +- ...tion-v0.3.xsd => ifopt_administration.xsd} | 10 +- ...pPlace-v0.3.xsd => ifopt_allStopPlace.xsd} | 28 +- ...eckpoint-v0.3.xsd => ifopt_checkpoint.xsd} | 10 +- ...countries-v0.2.xsd => ifopt_countries.xsd} | 4 +- ...equipment-v0.3.xsd => ifopt_equipment.xsd} | 12 +- ...t_location-v0.3.xsd => ifopt_location.xsd} | 6 +- .../{ifopt_modes-v0.2.xsd => ifopt_modes.xsd} | 6 +- ...cation-v0.3.xsd => ifopt_modification.xsd} | 6 +- .../{ifopt_path-v0.2.xsd => ifopt_path.xsd} | 4 +- .../{ifopt_stop-v0.3.xsd => ifopt_stop.xsd} | 4 +- .../{ifopt_time-v0.2.xsd => ifopt_time.xsd} | 6 +- .../{ifopt_types-v0.2.xsd => ifopt_types.xsd} | 4 +- xsd/siri.xsd | 4 +- ...mework-v2.0.xsd => siri_all_framework.xsd} | 10 +- .../{siri_base-v2.0.xsd => siri_base.xsd} | 8 +- ...ices-v2.0.xsd => siri_common_services.xsd} | 8 +- ...0.xsd => siri_request_errorConditions.xsd} | 14 +- ...port-v2.0.xsd => siri_request_support.xsd} | 10 +- ...ri_requests-v2.0.xsd => siri_requests.xsd} | 14 +- xsd/siriSg.xsd | 6 +- xsd/siri_all_functionalServices.xsd | 2 +- xsd/siri_connectionMonitoring_service.xsd | 10 +- xsd/siri_connectionTimetable_service.xsd | 14 +- xsd/siri_discovery.xsd | 22 +- xsd/siri_estimatedTimetable_service.xsd | 16 +- xsd/siri_facilityMonitoring_service.xsd | 26 +- xsd/siri_generalMessage_service.xsd | 14 +- .../{siri_all-v2.0.xsd => siri_all.xsd} | 8 +- ...del-v2.0.xsd => siri_all_journeyModel.xsd} | 24 +- ..._all_model-v2.0.xsd => siri_all_model.xsd} | 8 +- ...uation-v2.0.xsd => siri_all_situation.xsd} | 16 +- ...-v2.0.xsd => siri_datedVehicleJourney.xsd} | 8 +- ...0.xsd => siri_estimatedVehicleJourney.xsd} | 12 +- ...acilities-v1.2.xsd => siri_facilities.xsd} | 6 +- ...ri_facility-v2.0.xsd => siri_facility.xsd} | 18 +- ...port-v2.0.xsd => siri_feature_support.xsd} | 6 +- ...y-v2.0.xsd => siri_interchangeJourney.xsd} | 10 +- ...siri_journey-v2.0.xsd => siri_journey.xsd} | 22 +- ...port-v2.0.xsd => siri_journey_support.xsd} | 10 +- ...ons-v2.0.xsd => siri_modelPermissions.xsd} | 12 +- .../{siri_modes-v1.1.xsd => siri_modes.xsd} | 6 +- ...0.xsd => siri_monitoredVehicleJourney.xsd} | 10 +- ...ort-v2.0.xsd => siri_operator_support.xsd} | 6 +- ..._reference-v2.0.xsd => siri_reference.xsd} | 16 +- ..._situation-v2.0.xsd => siri_situation.xsd} | 26 +- ...ons-v2.0.xsd => siri_situationActions.xsd} | 10 +- ...cts-v2.0.xsd => siri_situationAffects.xsd} | 38 +- ...v1.1.xsd => siri_situationClassifiers.xsd} | 4 +- ...ty-v1.1.xsd => siri_situationIdentity.xsd} | 16 +- ...ons-v2.0.xsd => siri_situationReasons.xsd} | 4 +- ...1.0.xsd => siri_situationServiceTypes.xsd} | 4 +- ....0.xsd => siri_targetedVehicleJourney.xsd} | 8 +- .../{siri_time-v2.0.xsd => siri_time.xsd} | 8 +- ...nLink-v2.0.xsd => siri_connectionLink.xsd} | 12 +- ...siri_feature-v2.0.xsd => siri_feature.xsd} | 12 +- ...oChannel-v2.0.xsd => siri_infoChannel.xsd} | 10 +- .../{siri_line-v2.0.xsd => siri_line.xsd} | 14 +- ..._stopPoint-v2.0.xsd => siri_stopPoint.xsd} | 12 +- xsd/siri_productionTimetable_service.xsd | 16 +- xsd/siri_situationExchange_service.xsd | 22 +- xsd/siri_stopMonitoring_service.xsd | 14 +- xsd/siri_stopTimetable_service.xsd | 16 +- ..._utility-v2.0.xsd => siri_all_utility.xsd} | 12 +- ...ri_location-v2.0.xsd => siri_location.xsd} | 6 +- ...ticipant-v2.0.xsd => siri_participant.xsd} | 6 +- ...missions-v2.0.xsd => siri_permissions.xsd} | 18 +- .../{siri_types-v2.0.xsd => siri_types.xsd} | 6 +- ...siri_utility-v1.1.xsd => siri_utility.xsd} | 8 +- xsd/siri_vehicleMonitoring_service.xsd | 16 +- xsd/siri_wsConsumer-Document.wsdl | 4 +- xsd/siri_wsConsumer-WSDL2.wsdl | 4 +- xsd/siri_wsConsumer.wsdl | 4 +- xsd/siri_wsProducer.wsdl | 2 +- xsd/wsdl_model/siri_wsConsumer-Framework.xsd | 2 +- xsd/wsdl_model/siri_wsConsumer-Services.xsd | 2 +- .../siri_wsProducer-DiscoveryCapability.xsd | 2 +- xsd/wsdl_model/siri_wsProducer-Framework.xsd | 2 +- xsd/wsdl_model/siri_wsProducer-Services.xsd | 2 +- .../siri_estimatedVehicleJourney-v2.0.xsd | 416 ------ xsd/zrescue/siri_situation-v2.0.xsd | 1270 ----------------- xsd/zrescue/siri_situationAffects-v2.0.xsd | 1058 -------------- 88 files changed, 563 insertions(+), 3307 deletions(-) rename xsd/{Siri-2.0.spp => Siri.spp} (74%) rename xsd/{Siri-2.0.xpr => Siri.xpr} (82%) rename xsd/acsb/{acsb_accessibility-v0.3.xsd => acsb_accessibility.xsd} (96%) rename xsd/acsb/{acsb_all-v0.3.xsd => acsb_all.xsd} (71%) rename xsd/acsb/{acsb_limitations-v0.2.xsd => acsb_limitations.xsd} (98%) rename xsd/acsb/{acsb_passengerMobility-v0.3.xsd => acsb_passengerMobility.xsd} (99%) rename xsd/ifopt/{ifopt_administration-v0.3.xsd => ifopt_administration.xsd} (97%) rename xsd/ifopt/{ifopt_allStopPlace-v0.3.xsd => ifopt_allStopPlace.xsd} (71%) rename xsd/ifopt/{ifopt_checkpoint-v0.3.xsd => ifopt_checkpoint.xsd} (97%) rename xsd/ifopt/{ifopt_countries-v0.2.xsd => ifopt_countries.xsd} (99%) rename xsd/ifopt/{ifopt_equipment-v0.3.xsd => ifopt_equipment.xsd} (96%) rename xsd/ifopt/{ifopt_location-v0.3.xsd => ifopt_location.xsd} (98%) rename xsd/ifopt/{ifopt_modes-v0.2.xsd => ifopt_modes.xsd} (97%) rename xsd/ifopt/{ifopt_modification-v0.3.xsd => ifopt_modification.xsd} (98%) rename xsd/ifopt/{ifopt_path-v0.2.xsd => ifopt_path.xsd} (98%) rename xsd/ifopt/{ifopt_stop-v0.3.xsd => ifopt_stop.xsd} (99%) rename xsd/ifopt/{ifopt_time-v0.2.xsd => ifopt_time.xsd} (97%) rename xsd/ifopt/{ifopt_types-v0.2.xsd => ifopt_types.xsd} (98%) rename xsd/siri/{siri_all_framework-v2.0.xsd => siri_all_framework.xsd} (58%) rename xsd/siri/{siri_base-v2.0.xsd => siri_base.xsd} (98%) rename xsd/siri/{siri_common_services-v2.0.xsd => siri_common_services.xsd} (99%) rename xsd/siri/{siri_request_errorConditions-v2.0.xsd => siri_request_errorConditions.xsd} (98%) rename xsd/siri/{siri_request_support-v2.0.xsd => siri_request_support.xsd} (97%) rename xsd/siri/{siri_requests-v2.0.xsd => siri_requests.xsd} (99%) rename xsd/siri_model/{siri_all-v2.0.xsd => siri_all.xsd} (76%) rename xsd/siri_model/{siri_all_journeyModel-v2.0.xsd => siri_all_journeyModel.xsd} (51%) rename xsd/siri_model/{siri_all_model-v2.0.xsd => siri_all_model.xsd} (77%) rename xsd/siri_model/{siri_all_situation-v2.0.xsd => siri_all_situation.xsd} (60%) rename xsd/siri_model/{siri_datedVehicleJourney-v2.0.xsd => siri_datedVehicleJourney.xsd} (99%) rename xsd/siri_model/{siri_estimatedVehicleJourney-v2.0.xsd => siri_estimatedVehicleJourney.xsd} (98%) rename xsd/siri_model/{siri_facilities-v1.2.xsd => siri_facilities.xsd} (99%) rename xsd/siri_model/{siri_facility-v2.0.xsd => siri_facility.xsd} (98%) rename xsd/siri_model/{siri_feature_support-v2.0.xsd => siri_feature_support.xsd} (98%) rename xsd/siri_model/{siri_interchangeJourney-v2.0.xsd => siri_interchangeJourney.xsd} (95%) rename xsd/siri_model/{siri_journey-v2.0.xsd => siri_journey.xsd} (99%) rename xsd/siri_model/{siri_journey_support-v2.0.xsd => siri_journey_support.xsd} (99%) rename xsd/siri_model/{siri_modelPermissions-v2.0.xsd => siri_modelPermissions.xsd} (97%) rename xsd/siri_model/{siri_modes-v1.1.xsd => siri_modes.xsd} (99%) rename xsd/siri_model/{siri_monitoredVehicleJourney-v2.0.xsd => siri_monitoredVehicleJourney.xsd} (98%) rename xsd/siri_model/{siri_operator_support-v2.0.xsd => siri_operator_support.xsd} (96%) rename xsd/siri_model/{siri_reference-v2.0.xsd => siri_reference.xsd} (98%) rename xsd/siri_model/{siri_situation-v2.0.xsd => siri_situation.xsd} (99%) rename xsd/siri_model/{siri_situationActions-v2.0.xsd => siri_situationActions.xsd} (98%) rename xsd/siri_model/{siri_situationAffects-v2.0.xsd => siri_situationAffects.xsd} (98%) rename xsd/siri_model/{siri_situationClassifiers-v1.1.xsd => siri_situationClassifiers.xsd} (99%) rename xsd/siri_model/{siri_situationIdentity-v1.1.xsd => siri_situationIdentity.xsd} (96%) rename xsd/siri_model/{siri_situationReasons-v2.0.xsd => siri_situationReasons.xsd} (99%) rename xsd/siri_model/{siri_situationServiceTypes-v1.0.xsd => siri_situationServiceTypes.xsd} (99%) rename xsd/siri_model/{siri_targetedVehicleJourney-v2.0.xsd => siri_targetedVehicleJourney.xsd} (96%) rename xsd/siri_model/{siri_time-v2.0.xsd => siri_time.xsd} (99%) rename xsd/siri_model_discovery/{siri_connectionLink-v2.0.xsd => siri_connectionLink.xsd} (95%) rename xsd/siri_model_discovery/{siri_feature-v2.0.xsd => siri_feature.xsd} (96%) rename xsd/siri_model_discovery/{siri_infoChannel-v2.0.xsd => siri_infoChannel.xsd} (94%) rename xsd/siri_model_discovery/{siri_line-v2.0.xsd => siri_line.xsd} (97%) rename xsd/siri_model_discovery/{siri_stopPoint-v2.0.xsd => siri_stopPoint.xsd} (96%) rename xsd/siri_utility/{siri_all_utility-v2.0.xsd => siri_all_utility.xsd} (54%) rename xsd/siri_utility/{siri_location-v2.0.xsd => siri_location.xsd} (98%) rename xsd/siri_utility/{siri_participant-v2.0.xsd => siri_participant.xsd} (95%) rename xsd/siri_utility/{siri_permissions-v2.0.xsd => siri_permissions.xsd} (93%) rename xsd/siri_utility/{siri_types-v2.0.xsd => siri_types.xsd} (98%) rename xsd/siri_utility/{siri_utility-v1.1.xsd => siri_utility.xsd} (98%) delete mode 100644 xsd/zrescue/siri_estimatedVehicleJourney-v2.0.xsd delete mode 100644 xsd/zrescue/siri_situation-v2.0.xsd delete mode 100644 xsd/zrescue/siri_situationAffects-v2.0.xsd diff --git a/xsd/ReadMe.txt b/xsd/ReadMe.txt index 6636724d..0c64160f 100644 --- a/xsd/ReadMe.txt +++ b/xsd/ReadMe.txt @@ -29,13 +29,13 @@ Changes to SIRI schema v2.0 since v1.4 * siri_situationExchange_service.xsd: addition of IncludedSituationExchangeDelivery element 2015.05.11 Bug fix (from SG7 skype meeting on May 11th 2015) SIRI 2.0o - * Allow multiple tags within an extension (reapply lost chnage from 2012.06.18 SIRI 2.0d) - siri_utility-v1.1.xsd - * siri_estimatedVehicleJourney-v2.0.xsd : in EstimatedTimetableAlterationGroup, addition of FramedVehicleJourneyRef as an alternative to DatedVehicleJourneyRef (choice) and deprecation of DatedVehicleJourneyRef and EstimatedVehicleJourneyCode - * siri_datedVehicleJourney-v2.0.xsd : DatedVehicleJourneyCode is now optional + * Allow multiple tags within an extension (reapply lost chnage from 2012.06.18 SIRI 2.0d) - siri_utility.xsd + * siri_estimatedVehicleJourney.xsd : in EstimatedTimetableAlterationGroup, addition of FramedVehicleJourneyRef as an alternative to DatedVehicleJourneyRef (choice) and deprecation of DatedVehicleJourneyRef and EstimatedVehicleJourneyCode + * siri_datedVehicleJourney.xsd : DatedVehicleJourneyCode is now optional * siri.xsd: SituationExchangeDelivery now can be provided as a complement to any other Service delivery (and can still be provided standalone)... note that the SituationExchangeDelivery must be after the other Delivery to get a validating, non-ambiguous XSD. - * siri_estimatedVehicleJourney-v2.0.xsd : EstimatedVehicleJourneyStructure brought back to SIRI 2.0k situation + * siri_estimatedVehicleJourney.xsd : EstimatedVehicleJourneyStructure brought back to SIRI 2.0k situation * Replacement of EstimatedJourneyInfoGroup by JourneyEndTimesGroup - * Replacement of inclusion of siri_journey-v2.0.xsd by siri_monitoredVehicleJourney-v2.0.xsd + * Replacement of inclusion of siri_journey.xsd by siri_monitoredVehicleJourney.xsd * Replacement of EstimatedRealtimeInfoGroup by journeyProgressGroup * Replacement of OperationalInfoGroup by TrainOperationalInfoGroup @@ -52,25 +52,25 @@ Changes to SIRI schema v2.0 since v1.4 2014.06.20 Correction and revisions from Stenungsund [Part2] - * [fx] Document SubscriptionTerminatedNotification and add error code. (siri-requests-v2.0.xsd) - * [fx] StopDiscovery response. Add RouteDirection. Rename JourneyPattern/Stops to JourneyPattern/StopsInPattern SubscriptionTerminatedNotification and add error code. (siri-requests-v2.0.xsd) - * [de] Add Extensions to discovery requests. (siri_discovery-v2.0.xsd) + * [fx] Document SubscriptionTerminatedNotification and add error code. (siri-requests.xsd) + * [fx] StopDiscovery response. Add RouteDirection. Rename JourneyPattern/Stops to JourneyPattern/StopsInPattern SubscriptionTerminatedNotification and add error code. (siri-requests.xsd) + * [de] Add Extensions to discovery requests. (siri_discovery.xsd) [Part3] - * [ch] Add origin display whereever destination display as per Cologne meeting (siri-Journey-v2.0.xsd, siri-DatedVehicleJourney-v2.0.xsd, - * [xh[ Add OriginAtDestination wherever destination display as per Cologne meeting (siri-Journey-v2.0.xsd) - * [fx] Set default on new DetailLevels on ConnectionMonitoring and EstimatedJourney for backwards compatability. (siri_connectionMonitoring_ervice-v2.0.xsd siri_EstimatedTimetable_service-v2.0.xsd - * [ch] Add recordedCall to Estimated jouernesy to allow times for passed stops to be included. iri_EstimatedVehicleJourney-v2.0.xsd + * [ch] Add origin display whereever destination display as per Cologne meeting (siri-Journey.xsd, siri-DatedVehicleJourney.xsd, + * [xh[ Add OriginAtDestination wherever destination display as per Cologne meeting (siri-Journey.xsd) + * [fx] Set default on new DetailLevels on ConnectionMonitoring and EstimatedJourney for backwards compatability. (siri_connectionMonitoring_ervice.xsd siri_EstimatedTimetable_service.xsd + * [ch] Add recordedCall to Estimated jouernesy to allow times for passed stops to be included. iri_EstimatedVehicleJourney.xsd [Part5 SituationExchange] - * [de] Add missing AffectedFacility that was in document but missing from schema. VehicleJourney, STop & StopComponent siri_situationAffects-v2.0.xsd. + * [de] Add missing AffectedFacility that was in document but missing from schema. VehicleJourney, STop & StopComponent siri_situationAffects.xsd. emporal filter siri_situationExchaneg_service.xsd. * [de] Add temporal filter to request with ValidityPeriod in siri_situationExchange_service.xsd. - * [se] Add end time precision to halfopen time rangefor input a siri_time-v2.0.xsd. - * [se] Add end time status to halfopen time range output siri_time-v2.0.xsd. - * [fr] Add additional small delay bands siri_situation-v2.0.xsd + * [se] Add end time precision to halfopen time rangefor input a siri_time.xsd. + * [se] Add end time status to halfopen time range output siri_time.xsd. + * [fr] Add additional small delay bands siri_situation.xsd * [de] Add IncludeOnly-IfInPublicationWindow to situation request temporal filter siri_situationExchange_service.xsd. * [fx] StopPlaceFilterGroup: add missing component ref and facility that was in doc but missing from schema siri_situationExchange_service.xsd. - * [fx] Add missing AccessFeature type to AFfectedStopPlaceComponent siri_situationAffects-v2.0.xsd. + * [fx] Add missing AccessFeature type to AFfectedStopPlaceComponent siri_situationAffects.xsd. * [fx] Correct cardinality on FacilitRef on request to match doc siri_situationExchaneg_service.xsd. * [fx] Correct spec to include projection attributes for AFfectedStopPlaceComponent doc. * [doc] Document FacilityRef as part of request doc @@ -79,19 +79,19 @@ emporal filter siri_situationExchaneg_service.xsd. * [doc] Document RoadFilter and Accessibility need filter as part of request doc * [doc] Correct Documentation of AfFfectedRoads as part of Delivery doc * [doc/fx] Correct Documentation of capability Matrix and update in schemas well siri_situationExchange_service.xsd. - * [doc/fx] Correct Documentation of Reason codes and correct in schemas siri_reasons-v2.0.xml + * [doc/fx] Correct Documentation of Reason codes and correct in schema siri_reasons.xsd * [doc] Add Annex D to Doc on GTFS real-time mapping 2014.05.26 Changes to answer comment from the EU ballot * [fr] Addition of SubscriptionTerminatedNotification (XSD and WSDL SOAP Web Services(RPC/Document & WSDL2)) - - File siri_common_services-v2.0.xsd: Addition of SubscriptionTerminatedNotification (SubscriptionTerminatedNotification element + SubscriptionTerminatedNotificationStructure ) + - File siri_common_services.xsd: Addition of SubscriptionTerminatedNotification (SubscriptionTerminatedNotification element + SubscriptionTerminatedNotificationStructure ) - File siri.xsd: addition of SubscriptionTerminatedNotification in servicesResponseGroup - Update of siri_wsConsumer-Document.wsdl, siri_wsConsumer.wsdl, siri_wsConsumer-WSDL2.wsdl to add a NotifyTerminateSubscription - File siri_wsConsumer-Framework.xsd: Addition of WsSubscriptionTerminatedNotificationStructure and NotifySubscriptionTerminated - * [fr] Added ParameterName [0..*] to ParametersIgnoredErrorStructure (siri_request_errorConditions-v2.0.xsd) - * [fr] Added ExtensionName [0..*] to UnknownExtensionsErrorStructure (siri_request_errorConditions-v2.0.xsd) - * [fr] Added InvalidRef [0..*] to InvalidDataReferencesErrorStructure (siri_request_errorConditions-v2.0.xsd) - * [fr] Added Vesion attribute (non mandatory) to CheckStatus request (siri_common_services-v2.0.xsd) + * [fr] Added ParameterName [0..*] to ParametersIgnoredErrorStructure (siri_request_errorConditions.xsd) + * [fr] Added ExtensionName [0..*] to UnknownExtensionsErrorStructure (siri_request_errorConditions.xsd) + * [fr] Added InvalidRef [0..*] to InvalidDataReferencesErrorStructure (siri_request_errorConditions.xsd) + * [fr] Added Vesion attribute (non mandatory) to CheckStatus request (siri_common_services.xsd) * [fr] ChangeBeforeUpdates not anymore mandatory in EstimatedTimetableSubscriptionPolicyGroup * [fr] added optional RecordedAtTime to EstimatedVehicleJourney * [fr] added ConnectionLinksDiscovery service to WSDL (RPC/Document & WSDL2) (and siri_wsProducerDicoveryCapability.xsd) @@ -300,19 +300,19 @@ Changes to SIRI schema v1.4a since v1.3 (ii) and siri_generalMessage_service.xsd subscription structure x (iii) Missing type: Assign a type of normalizedString to formatRef x dx - (b) siri_requests-v1.2.xsd (line 814) ErrorConditionStructure should not be abstract . Fix from RV ixxi.biz- + (b) siri_requests.xsd (line 814) ErrorConditionStructure should not be abstract . Fix from RV ixxi.biz- made abstract x - (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 + (c) siri_journey.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 x ?? (d) siri_productionTimetable_service.xsd Type on request ValidityPeriod start and end should be datetime not time - Change to ClosedTimestampRange instead of ClosedDateeRange x tx. - Fix Subscription request to be an element and to have IncrementalUpdate parameter Extensions x - (e) siri_situation-v1.0.xsd AffectedVehicleJourney should allow multiple journeys. Brian Ferris onebusaway.org>, x + (e) siri_situation.xsd AffectedVehicleJourney should allow multiple journeys. Brian Ferris onebusaway.org>, x - (f) ifopt_location-v0.3.xsd Correct siri: namespace x + (f) ifopt_location.xsd Correct siri: namespace x (g) Fix up examples (i) correct estimated timetable request, production timetable request, stop monitoring request, stop monitoring eprmissions. drop flat examples tx. @@ -324,10 +324,10 @@ Changes to SIRI schema v1.4a since v1.3 siri_productionTimetable_service.xsd DatedCalls --> x tx (i) Add missing type - siri_requests-v1.3.xsd formatRef x + siri_requests.xsd formatRef x DATEXIISchema_1_0_1_0.xsd modelBaseversion - (j)siri_facility-v1.3.xsd TidyUp empty ValidityConditionGroup x + (j)siri_facility.xsd TidyUp empty ValidityConditionGroup x (g) Add xmlSPy project spp. x @@ -362,15 +362,15 @@ ___________________________________________________________________________ (a) Relax mandatory on in siri_common x 2008-11-18 Revise FM servics - (a) Revise daytypes in siri_time-v1.2 x + (a) Revise daytypes in siri_time.xsd x 2008-11-17 Revise to support substitution groups (a) Make all requests subtypes of abstract request. Add Subst elements x (b) Introduce AbstractFunctionalServiceRequest, AbstractCapabilityServiceRequest, AbstractDiscoveryRequest - 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 + as common supertypes. revised versiosn of siri_requests.xsd, siri_journey.xsd and siri_permissions.xsd, siri-All and siribase - (c) add SiriSg and Siri_base-v1.3.xsd packages + (c) add SiriSg and Siri_base.xsd packages 2008-11-12 Corrections to the Caridnailities on the siri_discovery services x (a) Change min maxes on >LineRef, StopPoints, Features etc etc x @@ -437,7 +437,7 @@ ___________________________________________________________________________ ===================================== 2007 10 17 Add Situation Exchange & Facility Exchange services. x tx - 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. + Added a siri_all.xsd, ifopt_allStopPlace.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 diff --git a/xsd/Siri-2.0.spp b/xsd/Siri.spp similarity index 74% rename from xsd/Siri-2.0.spp rename to xsd/Siri.spp index 4c8b4387..14947cdb 100644 --- a/xsd/Siri-2.0.spp +++ b/xsd/Siri.spp @@ -20,82 +20,82 @@ - - - - - - + + + + + + - - - - - - + + + + + + - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + - - - - - + + + + + - - - + + + - - - - - - + + + + + + - - - - + + + + - - - - - - - - - - - - + + + + + + + + + + + + diff --git a/xsd/Siri-2.0.xpr b/xsd/Siri.xpr similarity index 82% rename from xsd/Siri-2.0.xpr rename to xsd/Siri.xpr index 305eef5f..934c8eee 100644 --- a/xsd/Siri-2.0.xpr +++ b/xsd/Siri.xpr @@ -104,27 +104,27 @@ - - - - + + + + - - - - - - - - - - - - + + + + + + + + + + + + @@ -140,45 +140,45 @@ - - - - - + + + + + - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + - - - - + + + + - + - - - - + + + + diff --git a/xsd/acsb/acsb_accessibility-v0.3.xsd b/xsd/acsb/acsb_accessibility.xsd similarity index 96% rename from xsd/acsb/acsb_accessibility-v0.3.xsd rename to xsd/acsb/acsb_accessibility.xsd index c8f41e2f..526b5362 100644 --- a/xsd/acsb/acsb_accessibility-v0.3.xsd +++ b/xsd/acsb/acsb_accessibility.xsd @@ -24,7 +24,7 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001     - {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_accessibility-v0.3.xsd + {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_accessibility.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified @@ -35,7 +35,7 @@
  • Derived from the SIRI standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -53,9 +53,9 @@ Rail transport, Roads and road transport Fixed Objects accessibility types for IFOPT Fixed Objects in Public Transport. - - - + + + diff --git a/xsd/acsb/acsb_all-v0.3.xsd b/xsd/acsb/acsb_all.xsd similarity index 71% rename from xsd/acsb/acsb_all-v0.3.xsd rename to xsd/acsb/acsb_all.xsd index 3a3bf05d..358a9a71 100644 --- a/xsd/acsb/acsb_all-v0.3.xsd +++ b/xsd/acsb/acsb_all.xsd @@ -5,7 +5,7 @@ --> - - - + + + diff --git a/xsd/acsb/acsb_limitations-v0.2.xsd b/xsd/acsb/acsb_limitations.xsd similarity index 98% rename from xsd/acsb/acsb_limitations-v0.2.xsd rename to xsd/acsb/acsb_limitations.xsd index 1e34c4c8..98a34a36 100644 --- a/xsd/acsb/acsb_limitations-v0.2.xsd +++ b/xsd/acsb/acsb_limitations.xsd @@ -24,7 +24,7 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_accessibility-v0.2.xsd + {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_accessibility.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified @@ -35,7 +35,7 @@
  • Derived from the SIRI standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/acsb/acsb_passengerMobility-v0.3.xsd b/xsd/acsb/acsb_passengerMobility.xsd similarity index 99% rename from xsd/acsb/acsb_passengerMobility-v0.3.xsd rename to xsd/acsb/acsb_passengerMobility.xsd index d5bbab82..12a9b740 100644 --- a/xsd/acsb/acsb_passengerMobility-v0.3.xsd +++ b/xsd/acsb/acsb_passengerMobility.xsd @@ -24,7 +24,7 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_accessibility-v0.3.xsd + {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_accessibility.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified @@ -35,7 +35,7 @@
  • Derived from the SIRI standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/ifopt/ifopt_administration-v0.3.xsd b/xsd/ifopt/ifopt_administration.xsd similarity index 97% rename from xsd/ifopt/ifopt_administration-v0.3.xsd rename to xsd/ifopt/ifopt_administration.xsd index 973fc2d5..8eb8afe5 100644 --- a/xsd/ifopt/ifopt_administration-v0.3.xsd +++ b/xsd/ifopt/ifopt_administration.xsd @@ -24,7 +24,7 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_administration-v0.3.xsd + {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_administration.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified @@ -35,7 +35,7 @@
  • Derived from the SIRI standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -53,9 +53,9 @@ Rail transport, Roads and road transport Data administration types for IFOPT Fixed Objects in Public Transport.     - - - + + + diff --git a/xsd/ifopt/ifopt_allStopPlace-v0.3.xsd b/xsd/ifopt/ifopt_allStopPlace.xsd similarity index 71% rename from xsd/ifopt/ifopt_allStopPlace-v0.3.xsd rename to xsd/ifopt/ifopt_allStopPlace.xsd index 749d384e..bd231b33 100644 --- a/xsd/ifopt/ifopt_allStopPlace-v0.3.xsd +++ b/xsd/ifopt/ifopt_allStopPlace.xsd @@ -15,19 +15,19 @@ The Purpose of this file is to overcome a technical limitation in Xerces (and po --> - + - - - - - - - - - - - - - + + + + + + + + + + + + + diff --git a/xsd/ifopt/ifopt_checkpoint-v0.3.xsd b/xsd/ifopt/ifopt_checkpoint.xsd similarity index 97% rename from xsd/ifopt/ifopt_checkpoint-v0.3.xsd rename to xsd/ifopt/ifopt_checkpoint.xsd index 670017ed..eb6002f8 100644 --- a/xsd/ifopt/ifopt_checkpoint-v0.3.xsd +++ b/xsd/ifopt/ifopt_checkpoint.xsd @@ -27,7 +27,7 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_accessibility-v0.3.xsd + {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_accessibility.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified @@ -38,7 +38,7 @@
  • Derived from the IFOPT standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -56,9 +56,9 @@ Rail transport, Roads and road transport Fixed Objects CHECK CONSTRAINT types for IFOPT Fixed Objects in Public Transport.     - - - + + + Type for identifier of a CHECK CONSTRAINT.within a STOP PLACE. diff --git a/xsd/ifopt/ifopt_countries-v0.2.xsd b/xsd/ifopt/ifopt_countries.xsd similarity index 99% rename from xsd/ifopt/ifopt_countries-v0.2.xsd rename to xsd/ifopt/ifopt_countries.xsd index 0ab276d2..221c1a60 100644 --- a/xsd/ifopt/ifopt_countries-v0.2.xsd +++ b/xsd/ifopt/ifopt_countries.xsd @@ -24,7 +24,7 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_countries-v0.2.xsd + {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_countries.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified @@ -35,7 +35,7 @@
  • Derived from the SIRI standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/ifopt/ifopt_equipment-v0.3.xsd b/xsd/ifopt/ifopt_equipment.xsd similarity index 96% rename from xsd/ifopt/ifopt_equipment-v0.3.xsd rename to xsd/ifopt/ifopt_equipment.xsd index af560cbb..d6a974ee 100644 --- a/xsd/ifopt/ifopt_equipment-v0.3.xsd +++ b/xsd/ifopt/ifopt_equipment.xsd @@ -24,7 +24,7 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_equipment-v0.3.xsd + {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_equipment.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified @@ -35,7 +35,7 @@
  • Derived from the TransModel standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -53,10 +53,10 @@ Rail transport, Roads and road transport Equipment types for IFOPT Fixed Objects in Public Transport.     - - - - + + + + diff --git a/xsd/ifopt/ifopt_location-v0.3.xsd b/xsd/ifopt/ifopt_location.xsd similarity index 98% rename from xsd/ifopt/ifopt_location-v0.3.xsd rename to xsd/ifopt/ifopt_location.xsd index a93b502e..355354db 100644 --- a/xsd/ifopt/ifopt_location-v0.3.xsd +++ b/xsd/ifopt/ifopt_location.xsd @@ -30,7 +30,7 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_location-v0.3.xsd + {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_location.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified @@ -41,7 +41,7 @@
  • Derived from the SIRI standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -59,7 +59,7 @@ Rail transport, Roads and road transport location types for IFOPT Fixed Objects in Public Transport.     - + diff --git a/xsd/ifopt/ifopt_modes-v0.2.xsd b/xsd/ifopt/ifopt_modes.xsd similarity index 97% rename from xsd/ifopt/ifopt_modes-v0.2.xsd rename to xsd/ifopt/ifopt_modes.xsd index 0a120646..f6aa2f54 100644 --- a/xsd/ifopt/ifopt_modes-v0.2.xsd +++ b/xsd/ifopt/ifopt_modes.xsd @@ -21,7 +21,7 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_modes-v0.2.xsd + {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_modes.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified @@ -32,7 +32,7 @@
  • Derived from the SIRI standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -50,7 +50,7 @@ Rail transport, Roads and road transport Mode types for IFOPT Fixed Objects in Public Transport. - + diff --git a/xsd/ifopt/ifopt_modification-v0.3.xsd b/xsd/ifopt/ifopt_modification.xsd similarity index 98% rename from xsd/ifopt/ifopt_modification-v0.3.xsd rename to xsd/ifopt/ifopt_modification.xsd index af92f5c7..0731dbf7 100644 --- a/xsd/ifopt/ifopt_modification-v0.3.xsd +++ b/xsd/ifopt/ifopt_modification.xsd @@ -25,7 +25,7 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_modification-v0.3.xsd + {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_modification.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified @@ -36,7 +36,7 @@
  • Derived from the SIRI standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -54,7 +54,7 @@ Rail transport, Roads and road transport Data Modification types for IFOPT Fixed Objects in Public Transport.     - + diff --git a/xsd/ifopt/ifopt_path-v0.2.xsd b/xsd/ifopt/ifopt_path.xsd similarity index 98% rename from xsd/ifopt/ifopt_path-v0.2.xsd rename to xsd/ifopt/ifopt_path.xsd index a1a2847f..3cab0dc0 100644 --- a/xsd/ifopt/ifopt_path-v0.2.xsd +++ b/xsd/ifopt/ifopt_path.xsd @@ -21,7 +21,7 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_types-v0.2.xsd + {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_types.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified @@ -32,7 +32,7 @@
  • Derived from the SIRI standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/ifopt/ifopt_stop-v0.3.xsd b/xsd/ifopt/ifopt_stop.xsd similarity index 99% rename from xsd/ifopt/ifopt_stop-v0.3.xsd rename to xsd/ifopt/ifopt_stop.xsd index fd826f04..c8511364 100644 --- a/xsd/ifopt/ifopt_stop-v0.3.xsd +++ b/xsd/ifopt/ifopt_stop.xsd @@ -30,7 +30,7 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_types-v0.2.xsd + {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_types.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified @@ -41,7 +41,7 @@
  • Derived from the SIRI standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/ifopt/ifopt_time-v0.2.xsd b/xsd/ifopt/ifopt_time.xsd similarity index 97% rename from xsd/ifopt/ifopt_time-v0.2.xsd rename to xsd/ifopt/ifopt_time.xsd index e413ae7a..4be236d8 100644 --- a/xsd/ifopt/ifopt_time-v0.2.xsd +++ b/xsd/ifopt/ifopt_time.xsd @@ -21,7 +21,7 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_types-v0.2.xsd + {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_types.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified @@ -32,7 +32,7 @@
  • Derived from the SIRI standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -50,7 +50,7 @@ Rail transport, Roads and road transport Basic Time types for IFOPT Fixed Objects in Public Transport. - + diff --git a/xsd/ifopt/ifopt_types-v0.2.xsd b/xsd/ifopt/ifopt_types.xsd similarity index 98% rename from xsd/ifopt/ifopt_types-v0.2.xsd rename to xsd/ifopt/ifopt_types.xsd index 21826202..b81e3159 100644 --- a/xsd/ifopt/ifopt_types-v0.2.xsd +++ b/xsd/ifopt/ifopt_types.xsd @@ -24,7 +24,7 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_types-v0.2.xsd + {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_types.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified @@ -35,7 +35,7 @@
  • Derived from the SIRI standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri.xsd b/xsd/siri.xsd index 610a705f..53f715e1 100644 --- a/xsd/siri.xsd +++ b/xsd/siri.xsd @@ -1,6 +1,6 @@ - + @@ -156,7 +156,7 @@ Rail transport, Roads and road transport. SIRI Service Interface for Real-time Information relating to Public Transport Operations. - XML Schema with explicit functional services - + diff --git a/xsd/siri/siri_all_framework-v2.0.xsd b/xsd/siri/siri_all_framework.xsd similarity index 58% rename from xsd/siri/siri_all_framework-v2.0.xsd rename to xsd/siri/siri_all_framework.xsd index dbc9c58a..f1b3f959 100644 --- a/xsd/siri/siri_all_framework-v2.0.xsd +++ b/xsd/siri/siri_all_framework.xsd @@ -3,10 +3,10 @@ (C) Copyright CEN 2004-2012 --> - + - - - - + + + + diff --git a/xsd/siri/siri_base-v2.0.xsd b/xsd/siri/siri_base.xsd similarity index 98% rename from xsd/siri/siri_base-v2.0.xsd rename to xsd/siri/siri_base.xsd index 8d33e84b..53886d19 100644 --- a/xsd/siri/siri_base-v2.0.xsd +++ b/xsd/siri/siri_base.xsd @@ -1,5 +1,5 @@ - + @@ -57,7 +57,7 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri__common_services-v1.3xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__common_services.xsd Unclassified CEN, VDV, RTIG 2004-2012 @@ -67,7 +67,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -86,7 +86,7 @@ Rail transport, Roads and road transport. SIRI Common Request Fra,mework     - + diff --git a/xsd/siri/siri_common_services-v2.0.xsd b/xsd/siri/siri_common_services.xsd similarity index 99% rename from xsd/siri/siri_common_services-v2.0.xsd rename to xsd/siri/siri_common_services.xsd index 167b350f..a4613228 100644 --- a/xsd/siri/siri_common_services-v2.0.xsd +++ b/xsd/siri/siri_common_services.xsd @@ -1,6 +1,6 @@ - + @@ -71,7 +71,7 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd Unclassified CEN, VDV, RTIG 2004-2012 @@ -81,7 +81,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -101,7 +101,7 @@ Rail transport, Roads and road transport     - + diff --git a/xsd/siri/siri_request_errorConditions-v2.0.xsd b/xsd/siri/siri_request_errorConditions.xsd similarity index 98% rename from xsd/siri/siri_request_errorConditions-v2.0.xsd rename to xsd/siri/siri_request_errorConditions.xsd index 06ae5a5d..8d2869ff 100644 --- a/xsd/siri/siri_request_errorConditions-v2.0.xsd +++ b/xsd/siri/siri_request_errorConditions.xsd @@ -1,8 +1,8 @@ - - - + + + @@ -48,12 +48,12 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri/}siri_requests_errorConditions-v2.0.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri/}siri_requests_errorConditions.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri_uility/siri_types-v2.0.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_uility/siri_participant-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_uility/siri_types.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_uility/siri_participant.xsd Unclassified @@ -64,7 +64,7 @@
  • Derived from the VDV, RTIGXML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri/siri_request_support-v2.0.xsd b/xsd/siri/siri_request_support.xsd similarity index 97% rename from xsd/siri/siri_request_support-v2.0.xsd rename to xsd/siri/siri_request_support.xsd index d3c9ae76..8b66e404 100644 --- a/xsd/siri/siri_request_support-v2.0.xsd +++ b/xsd/siri/siri_request_support.xsd @@ -1,6 +1,6 @@ - - + + @@ -27,11 +27,11 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri/}siri_request_support-v2.0.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri/}siri_request_support.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd Unclassified @@ -42,7 +42,7 @@
  • Derived from the SIRI 1.0 standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri/siri_requests-v2.0.xsd b/xsd/siri/siri_requests.xsd similarity index 99% rename from xsd/siri/siri_requests-v2.0.xsd rename to xsd/siri/siri_requests.xsd index e1ed5605..e9111f55 100644 --- a/xsd/siri/siri_requests-v2.0.xsd +++ b/xsd/siri/siri_requests.xsd @@ -1,5 +1,5 @@ - + @@ -79,11 +79,11 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri/}siri_requests-v2.0.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri/}siri_requests.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd Unclassified @@ -94,7 +94,7 @@
  • Derived from the VDV, RTIGXML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -113,9 +113,9 @@ Rail transport, Roads and road transport SIRI Common Request Framework.     - - - + + + diff --git a/xsd/siriSg.xsd b/xsd/siriSg.xsd index 5063795e..708f9b0f 100644 --- a/xsd/siriSg.xsd +++ b/xsd/siriSg.xsd @@ -1,6 +1,6 @@ - + @@ -102,7 +102,7 @@
  • Derived from the SIRI Version 1.0
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -121,7 +121,7 @@ Rail transport, Roads and road transport. SIRI Service Interface for Real-time Information relating to Public Transport Operations. XML Schema with loosely coupled functional services,     - + diff --git a/xsd/siri_all_functionalServices.xsd b/xsd/siri_all_functionalServices.xsd index 97283f46..95db40b1 100644 --- a/xsd/siri_all_functionalServices.xsd +++ b/xsd/siri_all_functionalServices.xsd @@ -59,7 +59,7 @@
  • Derived from the SIRI Version 1.0.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_connectionMonitoring_service.xsd b/xsd/siri_connectionMonitoring_service.xsd index 3af80faf..40491ea6 100644 --- a/xsd/siri_connectionMonitoring_service.xsd +++ b/xsd/siri_connectionMonitoring_service.xsd @@ -1,6 +1,6 @@ - + @@ -59,9 +59,9 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests-v.2.0.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey-v2.0.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions.xsd Unclassified CEN, VDV, RTIG 2004-2012 @@ -71,7 +71,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_connectionTimetable_service.xsd b/xsd/siri_connectionTimetable_service.xsd index c2f247fb..48934133 100644 --- a/xsd/siri_connectionTimetable_service.xsd +++ b/xsd/siri_connectionTimetable_service.xsd @@ -1,5 +1,5 @@ - + @@ -57,8 +57,8 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests-v2.0.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd Unclassified CEN, VDV, RTIG 2004-2012 @@ -68,7 +68,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -87,9 +87,9 @@ Rail transport, Roads and road transport SIRI-CT Connection Timetable Service.     - - - + + + Convenience artifact to pick out main elements of the Connection Timetable Service. diff --git a/xsd/siri_discovery.xsd b/xsd/siri_discovery.xsd index 913823d8..a3b89a85 100644 --- a/xsd/siri_discovery.xsd +++ b/xsd/siri_discovery.xsd @@ -1,6 +1,6 @@ - + @@ -70,8 +70,8 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests-v2.0.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference.xsd Unclassified CEN, VDV, RTIG 2004-2012 @@ -81,7 +81,7 @@
  • Discovery services Derived from the NaPTAN standard .
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -100,13 +100,13 @@ Rail transport, Roads and road transport SIRI DIscovery Services for SCHEDULED STOP POINTs, LINEs,OPERATORs, FACILITies and feature TYPE OF VALUE codes.     - - - - - - - + + + + + + + diff --git a/xsd/siri_estimatedTimetable_service.xsd b/xsd/siri_estimatedTimetable_service.xsd index b5c3f893..6ea4d7fe 100644 --- a/xsd/siri_estimatedTimetable_service.xsd +++ b/xsd/siri_estimatedTimetable_service.xsd @@ -1,6 +1,6 @@ - + @@ -57,9 +57,9 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests-v2.0.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_estimatedVehicleJourney.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions.xsd Unclassified CEN, VDV, RTIG 2004-2012 @@ -69,7 +69,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -88,9 +88,9 @@ Rail transport, Roads and road transport SIRI-ET Estimated Timetable Service.     - - - + + + diff --git a/xsd/siri_facilityMonitoring_service.xsd b/xsd/siri_facilityMonitoring_service.xsd index 8e70d606..a5df0126 100644 --- a/xsd/siri_facilityMonitoring_service.xsd +++ b/xsd/siri_facilityMonitoring_service.xsd @@ -1,5 +1,5 @@ - + @@ -42,9 +42,9 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests-v2.0.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_reference-v2.0.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_reference.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions.xsd Unclassified CEN, VDV, RTIG 2004-2012 @@ -54,7 +54,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -73,18 +73,18 @@ Rail transport, Roads and road transport SIRI-FM Facility Monitoring Service.     - - + + - + - - + + - - - + + + diff --git a/xsd/siri_generalMessage_service.xsd b/xsd/siri_generalMessage_service.xsd index a109673d..cbadb8bb 100644 --- a/xsd/siri_generalMessage_service.xsd +++ b/xsd/siri_generalMessage_service.xsd @@ -1,5 +1,5 @@ - + @@ -51,8 +51,8 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests-v2.0.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_reference-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_reference.xsd Unclassified CEN, VDV, RTIG 2004-2012 @@ -62,7 +62,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -80,10 +80,10 @@ Rail transport, Roads and road transport     SIRI-GM General Message Service.     - + - - + + Convenience artefact to pick out main elements of the General Message Service. diff --git a/xsd/siri_model/siri_all-v2.0.xsd b/xsd/siri_model/siri_all.xsd similarity index 76% rename from xsd/siri_model/siri_all-v2.0.xsd rename to xsd/siri_model/siri_all.xsd index 23d4b928..0ab0d00f 100644 --- a/xsd/siri_model/siri_all-v2.0.xsd +++ b/xsd/siri_model/siri_all.xsd @@ -3,11 +3,11 @@ (C) Copyright CEN 2004-2012 --> - + - + - - + + diff --git a/xsd/siri_model/siri_all_journeyModel-v2.0.xsd b/xsd/siri_model/siri_all_journeyModel.xsd similarity index 51% rename from xsd/siri_model/siri_all_journeyModel-v2.0.xsd rename to xsd/siri_model/siri_all_journeyModel.xsd index 665b5b9a..48079667 100644 --- a/xsd/siri_model/siri_all_journeyModel-v2.0.xsd +++ b/xsd/siri_model/siri_all_journeyModel.xsd @@ -3,19 +3,19 @@ (C) Copyright CEN 2004-2012 --> - + - + - - - - - - - - - - + + + + + + + + + + diff --git a/xsd/siri_model/siri_all_model-v2.0.xsd b/xsd/siri_model/siri_all_model.xsd similarity index 77% rename from xsd/siri_model/siri_all_model-v2.0.xsd rename to xsd/siri_model/siri_all_model.xsd index b1fbec30..984702ec 100644 --- a/xsd/siri_model/siri_all_model-v2.0.xsd +++ b/xsd/siri_model/siri_all_model.xsd @@ -3,11 +3,11 @@ (C) Copyright CEN 2004-2012 --> - + - + - - + + diff --git a/xsd/siri_model/siri_all_situation-v2.0.xsd b/xsd/siri_model/siri_all_situation.xsd similarity index 60% rename from xsd/siri_model/siri_all_situation-v2.0.xsd rename to xsd/siri_model/siri_all_situation.xsd index 9af6522b..2c0f6a2c 100644 --- a/xsd/siri_model/siri_all_situation-v2.0.xsd +++ b/xsd/siri_model/siri_all_situation.xsd @@ -3,15 +3,15 @@ Copyright CEN 2004-2012 --> - + - + - - - - - - + + + + + + diff --git a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_datedVehicleJourney.xsd similarity index 99% rename from xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd rename to xsd/siri_model/siri_datedVehicleJourney.xsd index 8488d5a2..c72eed15 100644 --- a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_datedVehicleJourney.xsd @@ -1,6 +1,6 @@ - + @@ -66,7 +66,7 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd Unclassified CEN, VDV, RTIG 2004-2012 @@ -76,7 +76,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -95,7 +95,7 @@ Rail transport, Roads and road transport SIRI-Model Dated Vehicle Joruney.     - + diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney.xsd similarity index 98% rename from xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd rename to xsd/siri_model/siri_estimatedVehicleJourney.xsd index 196e22e8..410f642a 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney.xsd @@ -1,6 +1,6 @@ - + @@ -61,7 +61,7 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd Unclassified CEN, VDV, RTIG 2004-2012 @@ -71,7 +71,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -90,9 +90,9 @@ Rail transport, Roads and road transport SIRI-ET Estimated Timetable Service.     - - - + + + diff --git a/xsd/siri_model/siri_facilities-v1.2.xsd b/xsd/siri_model/siri_facilities.xsd similarity index 99% rename from xsd/siri_model/siri_facilities-v1.2.xsd rename to xsd/siri_model/siri_facilities.xsd index 04ef8135..34e69a03 100644 --- a/xsd/siri_model/siri_facilities-v1.2.xsd +++ b/xsd/siri_model/siri_facilities.xsd @@ -1,5 +1,5 @@ - + @@ -30,7 +30,7 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}facilities-v1.2.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}facilities.xsd [ISO 639-2/B] ENG CEN @@ -45,7 +45,7 @@
  • Derived from the TPEG Categories schema as encoded in the Kizoom XTIS schema.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_facility-v2.0.xsd b/xsd/siri_model/siri_facility.xsd similarity index 98% rename from xsd/siri_model/siri_facility-v2.0.xsd rename to xsd/siri_model/siri_facility.xsd index 4d59874d..66d542ef 100644 --- a/xsd/siri_model/siri_facility-v2.0.xsd +++ b/xsd/siri_model/siri_facility.xsd @@ -1,5 +1,5 @@ - + @@ -43,11 +43,11 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_facility-v2.0.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_facility.xsd [ISO 639-2/B] ENG CEN - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd Unclassified @@ -77,16 +77,16 @@ Rail transport, Roads and road transport SIRi Facility model elemenys - - - + + + - + - + - + diff --git a/xsd/siri_model/siri_feature_support-v2.0.xsd b/xsd/siri_model/siri_feature_support.xsd similarity index 98% rename from xsd/siri_model/siri_feature_support-v2.0.xsd rename to xsd/siri_model/siri_feature_support.xsd index a8ad0c0c..17457a5a 100644 --- a/xsd/siri_model/siri_feature_support-v2.0.xsd +++ b/xsd/siri_model/siri_feature_support.xsd @@ -1,5 +1,5 @@ - + @@ -42,7 +42,7 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_feature-v1.1.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_feature.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified @@ -54,7 +54,7 @@
  • Derived from the VDV, RTIG CML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_interchangeJourney-v2.0.xsd b/xsd/siri_model/siri_interchangeJourney.xsd similarity index 95% rename from xsd/siri_model/siri_interchangeJourney-v2.0.xsd rename to xsd/siri_model/siri_interchangeJourney.xsd index 992b4efa..59ae6b5f 100644 --- a/xsd/siri_model/siri_interchangeJourney-v2.0.xsd +++ b/xsd/siri_model/siri_interchangeJourney.xsd @@ -1,5 +1,5 @@ - + @@ -29,8 +29,8 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests-v2.0.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd Unclassified CEN, VDV, RTIG 2004-2012 @@ -40,7 +40,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -59,7 +59,7 @@ Rail transport, Roads and road transport SIRI-CT Interchange journey Connection Timetable Service.     - + diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey.xsd similarity index 99% rename from xsd/siri_model/siri_journey-v2.0.xsd rename to xsd/siri_model/siri_journey.xsd index b55c7cc3..603f6cf6 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey.xsd @@ -1,6 +1,6 @@ - + @@ -28,7 +28,7 @@ Correct Cardinalities on SIRI DESTINATION REF Structure 2011-04-18 - siri_journey-v2.0.xsd (l.1015). FramedVehicleJourneyRef isn't mandatory in MonitoredCall SIRI-SM answer accourding to CEN TS (prCEN/TS 15531-3:2006 (E) p.56). Make optional. RV ixxx.com + siri_journey.xsd (l.1015). FramedVehicleJourneyRef isn't mandatory in MonitoredCall SIRI-SM answer accourding to CEN TS (prCEN/TS 15531-3:2006 (E) p.56). Make optional. RV ixxx.com 2012-03-22 @@ -68,8 +68,8 @@ Correction: DestinationDisplay unbounded to allow multiple languages 2014-06-20 - [ch] Add origin display wherever destination display as per Cologne meeting (siri-Journey-v2.0.xsd - * [xh[ Add OriginAtDestination wherever destination display as per Cologne meeting (siri-Journey-v2.0.xsd) + [ch] Add origin display wherever destination display as per Cologne meeting (siri-Journey.xsd + * [xh[ Add OriginAtDestination wherever destination display as per Cologne meeting (siri-Journey.xsd)

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

    @@ -84,7 +84,7 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd Unclassified @@ -95,7 +95,7 @@
  • Derived from the VDV, RTIG CML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -114,14 +114,14 @@ Rail transport, Roads and road transport SIRI Common Journey Model.     - - - + + + - + - + diff --git a/xsd/siri_model/siri_journey_support-v2.0.xsd b/xsd/siri_model/siri_journey_support.xsd similarity index 99% rename from xsd/siri_model/siri_journey_support-v2.0.xsd rename to xsd/siri_model/siri_journey_support.xsd index 430ac845..2e7e700a 100644 --- a/xsd/siri_model/siri_journey_support-v2.0.xsd +++ b/xsd/siri_model/siri_journey_support.xsd @@ -1,5 +1,5 @@ - + @@ -29,7 +29,7 @@ 2011-04-18 - siri_journey-v2.0.xsd (l.1015). FramedVehicleJourneyRef isn't mandatory in MonitoredCall SIRI-SM answer accourding to CEN TS (prCEN/TS 15531-3:2006 (E) p.56). Make optional. RV ixxx.com + siri_journey.xsd (l.1015). FramedVehicleJourneyRef isn't mandatory in MonitoredCall SIRI-SM answer accourding to CEN TS (prCEN/TS 15531-3:2006 (E) p.56). Make optional. RV ixxx.com @@ -59,7 +59,7 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_types-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_types.xsd Unclassified @@ -70,7 +70,7 @@
  • Derived from the VDV, RTIG CML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -89,7 +89,7 @@ Rail transport, Roads and road transport SIRI Journey Model Identifiers.     - + diff --git a/xsd/siri_model/siri_modelPermissions-v2.0.xsd b/xsd/siri_model/siri_modelPermissions.xsd similarity index 97% rename from xsd/siri_model/siri_modelPermissions-v2.0.xsd rename to xsd/siri_model/siri_modelPermissions.xsd index 7162963d..670ff9cb 100644 --- a/xsd/siri_model/siri_modelPermissions-v2.0.xsd +++ b/xsd/siri_model/siri_modelPermissions.xsd @@ -1,7 +1,7 @@ - - - + + + @@ -30,11 +30,11 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri_model}siri_modelPermissions-v2.0.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri_model}siri_modelPermissions.xsd [ISO 639-2/B] ENG CEN - http://www.siri.org.uk/schema/2.0/xsd/siri_types-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_types.xsd Unclassified @@ -45,7 +45,7 @@
  • Derived from the VDV, RTIGXML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_modes-v1.1.xsd b/xsd/siri_model/siri_modes.xsd similarity index 99% rename from xsd/siri_model/siri_modes-v1.1.xsd rename to xsd/siri_model/siri_modes.xsd index e3f876c2..6a08e766 100644 --- a/xsd/siri_model/siri_modes-v1.1.xsd +++ b/xsd/siri_model/siri_modes.xsd @@ -1,5 +1,5 @@ - + @@ -28,7 +28,7 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_modes-v1.1.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_modes.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD @@ -42,7 +42,7 @@
  • Derived from the TPEG Categories schema
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_monitoredVehicleJourney.xsd similarity index 98% rename from xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd rename to xsd/siri_model/siri_monitoredVehicleJourney.xsd index cba57977..a1e7b4e1 100644 --- a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_monitoredVehicleJourney.xsd @@ -1,5 +1,5 @@ - + @@ -27,7 +27,7 @@ Correct Cardinalities on SIRI DESTINATION REF Structure 2011-04-18 - siri_journey-v2.0.xsd (l.1015). FramedVehicleJourneyRef isn't mandatory in MonitoredCall SIRI-SM answer accourding to CEN TS (prCEN/TS 15531-3:2006 (E) p.56). Make optional. RV ixxx.com + siri_journey.xsd (l.1015). FramedVehicleJourneyRef isn't mandatory in MonitoredCall SIRI-SM answer accourding to CEN TS (prCEN/TS 15531-3:2006 (E) p.56). Make optional. RV ixxx.com 2012-03-22 @@ -73,7 +73,7 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd Unclassified @@ -84,7 +84,7 @@
  • Derived from the VDV, RTIG CML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -103,7 +103,7 @@ Rail transport, Roads and road transport SIRI MONITORED VEHICLE JOURNEY Model.     - + diff --git a/xsd/siri_model/siri_operator_support-v2.0.xsd b/xsd/siri_model/siri_operator_support.xsd similarity index 96% rename from xsd/siri_model/siri_operator_support-v2.0.xsd rename to xsd/siri_model/siri_operator_support.xsd index 342ec61a..bbd123af 100644 --- a/xsd/siri_model/siri_operator_support-v2.0.xsd +++ b/xsd/siri_model/siri_operator_support.xsd @@ -1,5 +1,5 @@ - + @@ -24,7 +24,7 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_operator_support-v2.0.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_operator_support.xsd [ISO 639-2/B] ENG CEN - Add POSTAL ADDRESS Unclassified @@ -35,7 +35,7 @@
  • Derived from the SIRI standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_reference-v2.0.xsd b/xsd/siri_model/siri_reference.xsd similarity index 98% rename from xsd/siri_model/siri_reference-v2.0.xsd rename to xsd/siri_model/siri_reference.xsd index da20ab6c..3491dca3 100644 --- a/xsd/siri_model/siri_reference-v2.0.xsd +++ b/xsd/siri_model/siri_reference.xsd @@ -1,5 +1,5 @@ - + @@ -69,11 +69,11 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri/utility/}siri_reference-v2.0.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri/utility/}siri_reference.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd Unclassified CEN, VDV, RTIG 2004-2020 @@ -101,11 +101,11 @@ Rail transport, Roads and road transport - - - - - + + + + + diff --git a/xsd/siri_model/siri_situation-v2.0.xsd b/xsd/siri_model/siri_situation.xsd similarity index 99% rename from xsd/siri_model/siri_situation-v2.0.xsd rename to xsd/siri_model/siri_situation.xsd index 68c2698c..bb84fcad 100644 --- a/xsd/siri_model/siri_situation-v2.0.xsd +++ b/xsd/siri_model/siri_situation.xsd @@ -1,18 +1,18 @@ - + - - - + + + - - - - - + + + + + @@ -88,13 +88,13 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/}siri_model/siri_situation-v2.0.xsd + {http://www.siri.org.uk/schema/2.0/xsd/}siri_model/siri_situation.xsd [ISO 639-2/B] ENG CEN - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_stop-v0.2.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modes-v1.1.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_stop.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modes.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_monitoredVehicleJourney.xsd Unclassified Kizoom 2000-2005, CEN 2009-2020 diff --git a/xsd/siri_model/siri_situationActions-v2.0.xsd b/xsd/siri_model/siri_situationActions.xsd similarity index 98% rename from xsd/siri_model/siri_situationActions-v2.0.xsd rename to xsd/siri_model/siri_situationActions.xsd index f1919f1c..cdefddc6 100644 --- a/xsd/siri_model/siri_situationActions-v2.0.xsd +++ b/xsd/siri_model/siri_situationActions.xsd @@ -1,6 +1,6 @@ - - + + @@ -36,11 +36,11 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/schema/2.0/xsd/siri_model}/siri_situationActions-v1.0.xsd + {http://www.siri.org.uk/schema/schema/2.0/xsd/siri_model}/siri_situationActions.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd Unclassified @@ -51,7 +51,7 @@
  • Schema derived Derived from the Kizoom XTIS schema
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_model/siri_situationAffects-v2.0.xsd b/xsd/siri_model/siri_situationAffects.xsd similarity index 98% rename from xsd/siri_model/siri_situationAffects-v2.0.xsd rename to xsd/siri_model/siri_situationAffects.xsd index 747ac04e..2b13a873 100644 --- a/xsd/siri_model/siri_situationAffects-v2.0.xsd +++ b/xsd/siri_model/siri_situationAffects.xsd @@ -1,19 +1,19 @@ - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + @@ -73,13 +73,13 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/}siri_model/siri_situationAffects-v2.0.xsd + {http://www.siri.org.uk/schema/2.0/xsd/}siri_model/siri_situationAffects.xsd [ISO 639-2/B] ENG CEN - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modes-v1.1.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_situationServiceTypes.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modes.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd Unclassified Kizoom 2000-2007, CEN 2009-2020 diff --git a/xsd/siri_model/siri_situationClassifiers-v1.1.xsd b/xsd/siri_model/siri_situationClassifiers.xsd similarity index 99% rename from xsd/siri_model/siri_situationClassifiers-v1.1.xsd rename to xsd/siri_model/siri_situationClassifiers.xsd index 8b5ee21c..f845f653 100644 --- a/xsd/siri_model/siri_situationClassifiers-v1.1.xsd +++ b/xsd/siri_model/siri_situationClassifiers.xsd @@ -1,5 +1,5 @@ - + @@ -34,7 +34,7 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}/siri_situationClassifiers-v1.1.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}/siri_situationClassifiers.xsd [ISO 639-2/B] ENG CEN diff --git a/xsd/siri_model/siri_situationIdentity-v1.1.xsd b/xsd/siri_model/siri_situationIdentity.xsd similarity index 96% rename from xsd/siri_model/siri_situationIdentity-v1.1.xsd rename to xsd/siri_model/siri_situationIdentity.xsd index db32d9cf..7c19009a 100644 --- a/xsd/siri_model/siri_situationIdentity-v1.1.xsd +++ b/xsd/siri_model/siri_situationIdentity.xsd @@ -1,5 +1,5 @@ - + @@ -26,11 +26,11 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri_utility/}siri_situationIdentity-v1.1.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri_utility/}siri_situationIdentity.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri_uility/siri_participant-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_uility/siri_participant.xsd Unclassified @@ -41,7 +41,7 @@
  • Derived from the VDV, RTIG CML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -60,10 +60,10 @@ Rail transport, Roads and road transport SIRI-SX Situation IDentifiers.     - - - - + + + + diff --git a/xsd/siri_model/siri_situationReasons-v2.0.xsd b/xsd/siri_model/siri_situationReasons.xsd similarity index 99% rename from xsd/siri_model/siri_situationReasons-v2.0.xsd rename to xsd/siri_model/siri_situationReasons.xsd index 70e9f006..b6e0a045 100644 --- a/xsd/siri_model/siri_situationReasons-v2.0.xsd +++ b/xsd/siri_model/siri_situationReasons.xsd @@ -1,5 +1,5 @@ - + @@ -75,7 +75,7 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri_model}/siri_situationReasons-v2.0.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri_model}/siri_situationReasons.xsd [ISO 639-2/B] ENG CEN diff --git a/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd b/xsd/siri_model/siri_situationServiceTypes.xsd similarity index 99% rename from xsd/siri_model/siri_situationServiceTypes-v1.0.xsd rename to xsd/siri_model/siri_situationServiceTypes.xsd index 6ac66a03..1b1e8124 100644 --- a/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd +++ b/xsd/siri_model/siri_situationServiceTypes.xsd @@ -1,5 +1,5 @@ - + @@ -38,7 +38,7 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/standards/siri/schema/2.0/xsd/siri_model/}siri_situationServiceTypes-v1.0.xsd + {http://www.siri.org.uk/standards/siri/schema/2.0/xsd/siri_model/}siri_situationServiceTypes.xsd [ISO 639-2/B] ENG CEN diff --git a/xsd/siri_model/siri_targetedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_targetedVehicleJourney.xsd similarity index 96% rename from xsd/siri_model/siri_targetedVehicleJourney-v2.0.xsd rename to xsd/siri_model/siri_targetedVehicleJourney.xsd index a7befe72..a5ad0734 100644 --- a/xsd/siri_model/siri_targetedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_targetedVehicleJourney.xsd @@ -1,5 +1,5 @@ - + @@ -52,7 +52,7 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd Unclassified CEN, VDV, RTIG 2004-2012 @@ -62,7 +62,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -81,7 +81,7 @@ Rail transport, Roads and road transport SIRI-ST TargetedVehicleJourney for Stop Timetable Service.     - + diff --git a/xsd/siri_model/siri_time-v2.0.xsd b/xsd/siri_model/siri_time.xsd similarity index 99% rename from xsd/siri_model/siri_time-v2.0.xsd rename to xsd/siri_model/siri_time.xsd index 10652a4b..009b46b4 100644 --- a/xsd/siri_model/siri_time-v2.0.xsd +++ b/xsd/siri_model/siri_time.xsd @@ -1,5 +1,5 @@ - + @@ -25,8 +25,8 @@ 2014-06-20 - @@ -43,7 +43,7 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_time-v2.0.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_time.xsd [ISO 639-2/B] ENG CEN Unclassified diff --git a/xsd/siri_model_discovery/siri_connectionLink-v2.0.xsd b/xsd/siri_model_discovery/siri_connectionLink.xsd similarity index 95% rename from xsd/siri_model_discovery/siri_connectionLink-v2.0.xsd rename to xsd/siri_model_discovery/siri_connectionLink.xsd index f704dd9a..b2be49d9 100644 --- a/xsd/siri_model_discovery/siri_connectionLink-v2.0.xsd +++ b/xsd/siri_model_discovery/siri_connectionLink.xsd @@ -1,5 +1,5 @@ - + @@ -26,8 +26,8 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests-v2.0.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference.xsd Unclassified CEN, VDV, RTIG 2004-2012 @@ -37,7 +37,7 @@
  • Discovery services Derived from the NaPTAN standard .
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -56,8 +56,8 @@ Rail transport, Roads and road transport SIRI subschema with view of SCHEDULED CONNECTION LINKS for use in Connection Link Discovery service     - - + + diff --git a/xsd/siri_model_discovery/siri_feature-v2.0.xsd b/xsd/siri_model_discovery/siri_feature.xsd similarity index 96% rename from xsd/siri_model_discovery/siri_feature-v2.0.xsd rename to xsd/siri_model_discovery/siri_feature.xsd index c0757125..b6c7a6f9 100644 --- a/xsd/siri_model_discovery/siri_feature-v2.0.xsd +++ b/xsd/siri_model_discovery/siri_feature.xsd @@ -1,5 +1,5 @@ - + @@ -35,8 +35,8 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests-v2.0.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference.xsd Unclassified CEN, VDV, RTIG 2004-2012 @@ -46,7 +46,7 @@
  • Discovery services Derived from the NaPTAN standard .
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -65,8 +65,8 @@ Rail transport, Roads and road transport SIRI subschema with view of classifiers for use in Discovery service     - - + + diff --git a/xsd/siri_model_discovery/siri_infoChannel-v2.0.xsd b/xsd/siri_model_discovery/siri_infoChannel.xsd similarity index 94% rename from xsd/siri_model_discovery/siri_infoChannel-v2.0.xsd rename to xsd/siri_model_discovery/siri_infoChannel.xsd index c16cfc98..85d1c28f 100644 --- a/xsd/siri_model_discovery/siri_infoChannel-v2.0.xsd +++ b/xsd/siri_model_discovery/siri_infoChannel.xsd @@ -1,5 +1,5 @@ - + @@ -34,8 +34,8 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests-v2.0.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference.xsd Unclassified CEN, VDV, RTIG 2004-2012 @@ -45,7 +45,7 @@
  • Discovery services Derived from the NaPTAN standard .
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -64,7 +64,7 @@ Rail transport, Roads and road transport SIRI subschema with view of Info channel for use in Discovery service     - + diff --git a/xsd/siri_model_discovery/siri_line-v2.0.xsd b/xsd/siri_model_discovery/siri_line.xsd similarity index 97% rename from xsd/siri_model_discovery/siri_line-v2.0.xsd rename to xsd/siri_model_discovery/siri_line.xsd index 23ecf389..b32eedec 100644 --- a/xsd/siri_model_discovery/siri_line-v2.0.xsd +++ b/xsd/siri_model_discovery/siri_line.xsd @@ -1,5 +1,5 @@ - + @@ -43,8 +43,8 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests-v2.0.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference.xsd Unclassified CEN, VDV, RTIG 2004-2012 @@ -54,7 +54,7 @@
  • Discovery services Derived from the NaPTAN standard .
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -73,9 +73,9 @@ Rail transport, Roads and road transport SIRI subschema with view of LINE for use in Discovery service     - - - + + + diff --git a/xsd/siri_model_discovery/siri_stopPoint-v2.0.xsd b/xsd/siri_model_discovery/siri_stopPoint.xsd similarity index 96% rename from xsd/siri_model_discovery/siri_stopPoint-v2.0.xsd rename to xsd/siri_model_discovery/siri_stopPoint.xsd index 9308ea8a..702104b7 100644 --- a/xsd/siri_model_discovery/siri_stopPoint-v2.0.xsd +++ b/xsd/siri_model_discovery/siri_stopPoint.xsd @@ -1,5 +1,5 @@ - + @@ -40,8 +40,8 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests-v2.0.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference.xsd Unclassified CEN, VDV, RTIG 2004-2012 @@ -51,7 +51,7 @@
  • Discovery services Derived from the NaPTAN standard .
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -70,8 +70,8 @@ Rail transport, Roads and road transport SIRI subschema with view of SCHEDUELD STOP POINT for use in Stop Discovery service     - - + + diff --git a/xsd/siri_productionTimetable_service.xsd b/xsd/siri_productionTimetable_service.xsd index aeb05e4e..7c0a3028 100644 --- a/xsd/siri_productionTimetable_service.xsd +++ b/xsd/siri_productionTimetable_service.xsd @@ -1,5 +1,5 @@ - + @@ -63,9 +63,9 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests-v2.0.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_targetedVehicleJourney-v2.0.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_targetedVehicleJourney.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions.xsd Unclassified CEN, VDV, RTIG 2004-2012 @@ -75,7 +75,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -94,9 +94,9 @@ Rail transport, Roads and road transport SIRI-PT DATED JOURNEY Model view.     - - - + + + diff --git a/xsd/siri_situationExchange_service.xsd b/xsd/siri_situationExchange_service.xsd index d36fd25a..9344fcb6 100644 --- a/xsd/siri_situationExchange_service.xsd +++ b/xsd/siri_situationExchange_service.xsd @@ -1,6 +1,6 @@ - + @@ -66,9 +66,9 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests-v2.0.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_situation-v2.0.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_situation.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions.xsd Unclassified CEN, VDV, RTIG 2004, 2007 @@ -79,7 +79,7 @@
  • categories from TPEG
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -99,16 +99,16 @@ Rail transport, Roads and road transport     - + - + - - - - + + + + diff --git a/xsd/siri_stopMonitoring_service.xsd b/xsd/siri_stopMonitoring_service.xsd index 5225ed65..239fc5fa 100644 --- a/xsd/siri_stopMonitoring_service.xsd +++ b/xsd/siri_stopMonitoring_service.xsd @@ -1,6 +1,6 @@ - + @@ -83,8 +83,8 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests-v2.0.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd Unclassified CEN, VDV, RTIG 2004-2012 @@ -94,7 +94,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -113,9 +113,9 @@ Rail transport, Roads and road transport SIRI-SM Stop Monitoring Service.     - - - + + + diff --git a/xsd/siri_stopTimetable_service.xsd b/xsd/siri_stopTimetable_service.xsd index 677297c7..8e7c773c 100644 --- a/xsd/siri_stopTimetable_service.xsd +++ b/xsd/siri_stopTimetable_service.xsd @@ -1,5 +1,5 @@ - + @@ -56,9 +56,9 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests-v2.0.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey-v2.0.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions.xsd Unclassified CEN, VDV, RTIG 2004-2012 @@ -68,7 +68,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -87,9 +87,9 @@ Rail transport, Roads and road transport SIRI-ST Stop Timetable Service.     - - - + + + Convenience artifact to pick out main elements of the Stop Timetable Service. diff --git a/xsd/siri_utility/siri_all_utility-v2.0.xsd b/xsd/siri_utility/siri_all_utility.xsd similarity index 54% rename from xsd/siri_utility/siri_all_utility-v2.0.xsd rename to xsd/siri_utility/siri_all_utility.xsd index 9e7721dc..6160a385 100644 --- a/xsd/siri_utility/siri_all_utility-v2.0.xsd +++ b/xsd/siri_utility/siri_all_utility.xsd @@ -3,12 +3,12 @@ Copyright CEN 2004-2012 --> - + - - - - - + + + + + diff --git a/xsd/siri_utility/siri_location-v2.0.xsd b/xsd/siri_utility/siri_location.xsd similarity index 98% rename from xsd/siri_utility/siri_location-v2.0.xsd rename to xsd/siri_utility/siri_location.xsd index 89065cbd..f64f023d 100644 --- a/xsd/siri_utility/siri_location-v2.0.xsd +++ b/xsd/siri_utility/siri_location.xsd @@ -1,5 +1,5 @@ - + @@ -43,7 +43,7 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri_utility/}siri_location-v2.0.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri_utility/}siri_location.xsd [ISO 639-2/B] ENG CEN Unclassified @@ -54,7 +54,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_utility/siri_participant-v2.0.xsd b/xsd/siri_utility/siri_participant.xsd similarity index 95% rename from xsd/siri_utility/siri_participant-v2.0.xsd rename to xsd/siri_utility/siri_participant.xsd index 4af406d9..f7cade84 100644 --- a/xsd/siri_utility/siri_participant-v2.0.xsd +++ b/xsd/siri_utility/siri_participant.xsd @@ -1,5 +1,5 @@ - + @@ -31,7 +31,7 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri_utility/}siri_participant-v2.0.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri_utility/}siri_participant.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified @@ -43,7 +43,7 @@
  • Derived from the VDV, RTIGXML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_utility/siri_permissions-v2.0.xsd b/xsd/siri_utility/siri_permissions.xsd similarity index 93% rename from xsd/siri_utility/siri_permissions-v2.0.xsd rename to xsd/siri_utility/siri_permissions.xsd index 8620cf55..16beabf8 100644 --- a/xsd/siri_utility/siri_permissions-v2.0.xsd +++ b/xsd/siri_utility/siri_permissions.xsd @@ -1,5 +1,5 @@ - + @@ -23,13 +23,13 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri_utility/}siri_permissions-v2.0.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri_utility/}siri_permissions.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types-v2.0.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_utility-v2.0.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_uility/siri_participant-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_utility.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_uility/siri_participant.xsd Unclassified @@ -40,7 +40,7 @@
  • Derived from the VDV, RTIGXML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -58,9 +58,9 @@ Rail transport, Roads and road transport     SIRI Framework Permission Types.     - - - + + + diff --git a/xsd/siri_utility/siri_types-v2.0.xsd b/xsd/siri_utility/siri_types.xsd similarity index 98% rename from xsd/siri_utility/siri_types-v2.0.xsd rename to xsd/siri_utility/siri_types.xsd index 93df23d2..36bd00ac 100644 --- a/xsd/siri_utility/siri_types-v2.0.xsd +++ b/xsd/siri_utility/siri_types.xsd @@ -1,5 +1,5 @@ - + @@ -32,7 +32,7 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri_utility/}siri_types-v2.0.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri_utility/}siri_types.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified @@ -43,7 +43,7 @@
  • Derived from the VDV, RTIG CML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_utility/siri_utility-v1.1.xsd b/xsd/siri_utility/siri_utility.xsd similarity index 98% rename from xsd/siri_utility/siri_utility-v1.1.xsd rename to xsd/siri_utility/siri_utility.xsd index ec11acbd..f1fbe811 100644 --- a/xsd/siri_utility/siri_utility-v1.1.xsd +++ b/xsd/siri_utility/siri_utility.xsd @@ -1,6 +1,6 @@ - + @@ -24,7 +24,7 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri_utiliyty/}siri_utility-v1.1.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri_utiliyty/}siri_utility.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified @@ -35,7 +35,7 @@
  • Derived from the VDV, RTIGXML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -54,7 +54,7 @@ Rail transport, Roads and road transport SIRI Framework Utility Types.     - + diff --git a/xsd/siri_vehicleMonitoring_service.xsd b/xsd/siri_vehicleMonitoring_service.xsd index 2d0a2c00..9c2d297d 100644 --- a/xsd/siri_vehicleMonitoring_service.xsd +++ b/xsd/siri_vehicleMonitoring_service.xsd @@ -1,5 +1,5 @@ - + @@ -63,9 +63,9 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests-v2.0.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_reference-v2.0.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_reference.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions.xsd Unclassified CEN, VDV, RTIG 2004-2012 @@ -75,7 +75,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -94,9 +94,9 @@ Rail transport, Roads and road transport SIRI-VM Vehicle Monitoring Service.     - - - + + + diff --git a/xsd/siri_wsConsumer-Document.wsdl b/xsd/siri_wsConsumer-Document.wsdl index f99b320d..b60312ba 100644 --- a/xsd/siri_wsConsumer-Document.wsdl +++ b/xsd/siri_wsConsumer-Document.wsdl @@ -228,7 +228,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -296,7 +296,7 @@ Rail transport, Roads and road transport.
  • SIRI is derived from the VDV, RTIGXML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_wsConsumer-WSDL2.wsdl b/xsd/siri_wsConsumer-WSDL2.wsdl index 1cc114d0..19f13182 100644 --- a/xsd/siri_wsConsumer-WSDL2.wsdl +++ b/xsd/siri_wsConsumer-WSDL2.wsdl @@ -55,7 +55,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -123,7 +123,7 @@ Rail transport, Roads and road transport.
  • SIRI is derived from the VDV, RTIGXML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_wsConsumer.wsdl b/xsd/siri_wsConsumer.wsdl index 029cc40f..acbb091b 100644 --- a/xsd/siri_wsConsumer.wsdl +++ b/xsd/siri_wsConsumer.wsdl @@ -267,7 +267,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -333,7 +333,7 @@ Rail transport, Roads and road transport.
  • SIRI is derived from the VDV, RTIGXML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/siri_wsProducer.wsdl b/xsd/siri_wsProducer.wsdl index 22d62a0e..73c9e36f 100644 --- a/xsd/siri_wsProducer.wsdl +++ b/xsd/siri_wsProducer.wsdl @@ -690,7 +690,7 @@
  • SIRI is derived from the VDV, RTIGXML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/wsdl_model/siri_wsConsumer-Framework.xsd b/xsd/wsdl_model/siri_wsConsumer-Framework.xsd index aa970cb0..684eb197 100644 --- a/xsd/wsdl_model/siri_wsConsumer-Framework.xsd +++ b/xsd/wsdl_model/siri_wsConsumer-Framework.xsd @@ -46,7 +46,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/wsdl_model/siri_wsConsumer-Services.xsd b/xsd/wsdl_model/siri_wsConsumer-Services.xsd index 5ddc7c1f..4fc5076d 100644 --- a/xsd/wsdl_model/siri_wsConsumer-Services.xsd +++ b/xsd/wsdl_model/siri_wsConsumer-Services.xsd @@ -46,7 +46,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/wsdl_model/siri_wsProducer-DiscoveryCapability.xsd b/xsd/wsdl_model/siri_wsProducer-DiscoveryCapability.xsd index 0554aa03..d529d365 100644 --- a/xsd/wsdl_model/siri_wsProducer-DiscoveryCapability.xsd +++ b/xsd/wsdl_model/siri_wsProducer-DiscoveryCapability.xsd @@ -45,7 +45,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/wsdl_model/siri_wsProducer-Framework.xsd b/xsd/wsdl_model/siri_wsProducer-Framework.xsd index 1aa41d7b..96d6ae33 100644 --- a/xsd/wsdl_model/siri_wsProducer-Framework.xsd +++ b/xsd/wsdl_model/siri_wsProducer-Framework.xsd @@ -45,7 +45,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/wsdl_model/siri_wsProducer-Services.xsd b/xsd/wsdl_model/siri_wsProducer-Services.xsd index f3b2fd9d..66a0f4ce 100644 --- a/xsd/wsdl_model/siri_wsProducer-Services.xsd +++ b/xsd/wsdl_model/siri_wsProducer-Services.xsd @@ -45,7 +45,7 @@
  • Derived from the VDV, RTIG XML and Trident standards.
    • - Version 2.0 Draft + Version 2.1 Draft Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/xsd/zrescue/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/zrescue/siri_estimatedVehicleJourney-v2.0.xsd deleted file mode 100644 index c0c677fe..00000000 --- a/xsd/zrescue/siri_estimatedVehicleJourney-v2.0.xsd +++ /dev/null @@ -1,416 +0,0 @@ - - - - - - - main schema - e-service developers - CEN TC278 WG3 SG7 Team - Werner Kohl MDV - Europe - Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2003-02-10 - - - 2004-10-31 - - - 2005-02-14 - - - 2005-02-20 - - - 2005-05-11 - - 2007-04-17 - Name Space changes - - 2008-03-26 - Add wrapper tag for Line DIRECTION to help binding to Axis - - 2008-11-17 - Revise to support substitution groups - - 2011-01-19 - Drop use of As Flat Groups for EstimatedCalls - - 2012-03-23 - +SIRI v2.0 - Factored out of estimatedTimetableService - Add EstimatedServiceJourneyInterchange (i.e. Estimated Connection of VEHICLE) to EstimatedTimetableDelivery - Corrected feed and distributor Journety refs and add InterchangeRef - - -

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

    -

    This sub-schema describes the Estimated Timetable Service.

    -     - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri_model}siri_estimatedVehicleJourney.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey-v2.0.xsd - - Unclassified - CEN, VDV, RTIG 2004-2012 - - -
      -
    • Derived from the VDV, RTIG XML and Trident standards.
      • -
    - - Version 2.0 Draft - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI-ET XML schema. Service Interface for Real-time Information. Estimated Timetable Service. - Standard -     -     - SIRI-ET Estimated Timetable Service. -     - - - - - - A VEHICLE JOURNEY taking place on a particular date that will be managed by an AVMs. - - - - - If the journey is an alteration to a timetable, indicates the original journey and the nature of the difference. - - - - - - 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. If omitted: Passenger load is unknown. - - - - - - - Type for Origin and Destination stop of a VEHICLE JOURNEY. - - - - - The origin is used to help identify the VEHICLE JOURNEY. - - - - - Departure time from origin SCHEDULED STOP POINT. - - - - - The destination is used to help identify the VEHICLE JOURNEY. - - - - - Arrival time at destination SCHEDULED STOP POINT. - - - - - - - - A VEHICLE JOURNEY taking place on a particular date that will be managed by an AVMs. - - - - - Type for Estimated SERVICE JOURNEY INTERCHANGE. - - - - - - - - Reference to a connecting distributor VEHICLE JOURNEY. +SIRI v2.0 - - - - - Reference to a connecting distributor VEHICLE JOURNEY. +SIRI v2.0 - - - - - - - - Distributor will not wait (i.e. connection broken) SIRI w.0 - - - - - Nature of wait that distributer will make. +SIRI v2.0 - - - - - - Time at which distributor VEHICLE is expected to depart. +SIRI v2.0 - - - - - Whether connection monitoring is active or not for this connection +SIRI v2.0 - - - - - - - Type for Will Wait details - - - - - Time up until which the distributor will wait. +SIRI v2.0 - - - - - Whether an acknowledgement has been received that the driver will wait. +SIRI v2.0 - - - - - - - - Type for Real-time info about a VEHICLE JOURNEY. - - - - - Time at which data was recorded for that individual Journey - - - - - - - - - - - - - - - - - - - - - - - Whether the above call sequence is complete, i.e. represents every CALL of the SERVICE PATTERN and so can be used to replace a previous call sequence. Default is 'false'. - - - - - - - - - Ordered sequence of SCHEDULED STOP POINTs called at by the VEHICLE JOURNEY If IsCompleteStopSequence is false, may be just those stops that are altered. - - - - - Type for Rea-ltime info about a VEHICLE JOURNEY Stop. - - - - - - - This call is additional and unplanned. If omitted: CALL is planned. - - - - - This call is a cancellation of a previously announced call. - - - - - - - - - - - - - - - - Information relating to real-time properties of call. - - - - - Whether the prediction for the specific stop is considered to be of a useful accuracy or not. Default is 'false', i.e. prediction is not known to be inaccurate. {DOUBLE NEGATIVE IS BAD _ BETTER AS PredictionAccurate. Default is 'true'?]. If prediction is degraded, e.g. because in congestion, used to 9indicate a lowered quality of data. Inherited property. {SHOULD THIS JUST BE THE SPECIFIC InCongestion INDICATOR INSTEAD, OR IS IT MORE GENERAL] - - - - - How full the bus is at the stop. If omitted: Passenger load is unknown. - - - - - - - - Ordered sequence of SCHEDULED STOP POINTs called at by the VEHICLE JOURNEY If IsCompleteStopSequence is false, may be just those stops that are altered. - - - - - Information relating to recorded real-time properties of call. - - - - - - - - Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicel to arrive at.Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is -(i) any arrival platform on any related dated timetable element, -(ii) any departure platform name on this estimated element; -(iii) any departure platform name on any related dated timetable CALL. - - - - - Target departure time of VEHICLE according to latest working timetable. - - - - - Estimated time of departure of VEHICLE. - - - - - Departure QUAY ( Bay or platform) name. Defaulted taken from from planned timetable.. - - - - - Estimated time of departure of VEHICLE. - - - - - - - Type for recroded Real-time info about a VEHICLE JOURNEY Stop. - - - - - - - This call is additional and unplanned. If omitted: CALL is planned. - - - - - This call is a cancellation of a previously announced call. - - - - - - - - - -     diff --git a/xsd/zrescue/siri_situation-v2.0.xsd b/xsd/zrescue/siri_situation-v2.0.xsd deleted file mode 100644 index 0ba0c1ae..00000000 --- a/xsd/zrescue/siri_situation-v2.0.xsd +++ /dev/null @@ -1,1270 +0,0 @@ - - - - - - - - - - - - - - - - - - main schema - e-service developers - Waldemar Isajkin (INIT GmbH) - 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 - - correct data tupe to be particpant ref not participant pair - - add missing scopeType to classifier - - 2011-04-18 - - AffectedVehicleJourney should allow multiple journeys. Brian Ferris onebusaway.org - - 2012-03-23 - +SIRI v2.0 - Use revised 2.0 definitions - Update to use DATEXII V 2.0 schema - Namespace changed from http://datex2.eu/schema/1_0/1_0 to http://datex2.eu/schema/2_0RC1/2_0 - - - D2LogicalModel:ReferencePointLinear has been renamed to D2LogicalModel:ReferencePointLinear - - DelayCodeENum renamed to DelayBandEnum - - - InformationUsageOverride / D2LogicalModel:InformationUsage dropped for D2 - - D2LogicalModel:SourceInformation renamed to D2LogicalModel:Source - - - D2LogicalModel:SourceInformation values wrapped in valuse tag - - D2LogicalModel:Advcie dropped. - - D2LogicalModel:Imppact ImpactDetails wrapper tag dropped. - - D2 trafficResstrictionType renamed to trafficConstrictionType - Correct type on easementref to normalized string. - Allow transalatiobs of NLString elements - - 2013-02-11 - Correction: Certain elements of DescriptionGroup unbounded. - - 2013-10-01 - - [VDV] Added TpegSubReasonGroup to the ReasonGroup as described in the SX Documentation - - -

    SIRI-SX 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.siri.org.uk/schema/2.0/xsd/}siri_model/siri_situation-v2.0.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_stop-v0.2.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modes-v1.1.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd - - Unclassified - - Kizoom 2000-2005, CEN 2009-2012 - - -
      -
    • Schema Derived from the Kizoom XTIS schema
      • -
    - - Version 2.0 Draft - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI-SX Xml Schema for PT SITUATIONs. Common element subschema - Standard -     -     - SIRI-SX Situation Model. -     - - - - 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. - - - - - Elements identifying a SITUATION element or an update to a SITUATION. Participant reference 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 describing 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 describing 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. - - - - - 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. - - - - - Datex 2 comments for public use. - - - - - Ccomments not for public use. - - - - - Datex 2 model of where event ois taking place on the 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 Reference, 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, i.e. 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. - - - - - Reference to an 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. (Unbounded since SIRI 2.0) - - - - - - - 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. - - - - - 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 - - - - - - - - Specific vehicles affected by SITUATION. - - - - - - Vehicles 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. (Unbounded since SIRI 2.0) - - - - - Description of SITUATION. Should not repeat any strap line included in Summary. (Unbounded since SIRI 2.0) - - - - - Additional descriptive details about the SITUATION (Unbounded since SIRI 2.0). - - - - - Further advice to passengers. (Unbounded since SIRI 2.0) - - - - - 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. Default is 'true'. - - - - - - - - Values for image content. - - - - - - - - - - - - Type for a general hyperlink. - - - - - URI for link. - - - - - Label for Link. (Unbounded since SIRI 2.0) - - - - - 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 boarding restrictions. - - - - - Type of boarding and alighting allowed at stop. Default is 'Alighting'. - - - - - Type of alighting allowed at stop. Default is 'Boarding'. - - - - - - - Type for advice. - - - - - Reference to a standardis advisory NOTICE to be given to passengers if a particular condition arises . - - - - - Further Textual advice to passengers. (Unbounded since SIRI 2.0) - - - - - - - Type for blocking. - - - - - Whether information about parts of the network identified by Affects should be blocked from computation made by a Journey Planner that has a real-tiem feed of the SITUATIONs. Default is 'false'; do not suppress. - - - - - Whether information about parts of the network identified by 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. (Unbounded since SIRI 2.0) - - - - - Refernce to a fare exceptions code that is allowed because of the disruption. An easement may relax a fare condition, for exampel "You may use your metro ticket on the bus', or 'You may use your bus ticket in teh metro between these two stops'. - - - - - - - - Type for easement info. - - - - - Time band into which delay will fall. - - - - - Category of delay. - - - - - Additional journey time needed to overcome disruption. - - - - - - -     diff --git a/xsd/zrescue/siri_situationAffects-v2.0.xsd b/xsd/zrescue/siri_situationAffects-v2.0.xsd deleted file mode 100644 index 315bca5e..00000000 --- a/xsd/zrescue/siri_situationAffects-v2.0.xsd +++ /dev/null @@ -1,1058 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - main schema - e-service developers - Waldemar Isajkin (INIT GmbH) - 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 - - - 2013-10-10 - [vdv] Added Service Condition to the AffectedVehicleJourney - [vdv] Corrected LineGroup - added PublishedLineName and changed cardinality of LineRef to 1:1 - [vdv] CallCondition - changed cardinality to allow to include multiple conditions - [vdv] AffectedCallStructure - added CallPropertyGroup - [vdv] AffectedVehicleJourneyStructure - added DestinationDisplayAtOrigin - [vdv] AffectedRouteStructure - added possibility to expose the ROUTE as a sequence of STOP POINTS with links between them - [vdv] AffectedVehicles added - - -

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

    -     - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/}siri_model/siri_situationAffects-v2.0.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_situationServiceTypes-v1.2.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modes-v1.1.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey-v2.0.xsd - - Unclassified - - Kizoom 2000-2007, CEN 2009-2012 - - -
      -
    • Schema derived Derived from the Kizoom XTIS schema
      • -
    - - Version 2.0 Draft - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI-SX Xml Schema for PT Incidents. Common affects element subschema - Standard -     -     - SIRI-SX Situation Scope. -     - - - - Type for an SCHEDUELD STOP POINT affected by a SITUATION. - - - - - - Alternative private code of stop. - - - - - Name of SCHEDULED STOP POIHT. (Unbounded since SIRI 2.0) - - - - - Type of stop type. Normally implicit in VEHICLE mode. TPEG table pti 17_4 - - - - - Spatial coordinates of STOP POINT. Derivable from StopRef. - - - - - Modes within station/stop affected by the SITUATION. If not specified, assume all modes of that station. - - - - - Refernce to a SITE or TOPOGRAPHIC PLACE affected by the Locality of stop (In UK NPtg Locality Code). Derivable from StopRef. - - - - - Name of locality in which stop is found. Derivable from LocalityRef. (Unbounded since SIRI 2.0) - - - - - Assesment of current ACCESSIBILITY of the STOP POINT as affected by the SITUATION. - - - - - Status of STOP - - - - - CONNECTION links from stop. - - - - - - CONNECTION LINKs from stop that are affected by the SITUATION. - - - - - - - - - - - Type for TRANSPORT MODEs affecetd by a SITUATION. - - - - - All known modes for stop. - - - - - Mode affected by SITUATION. - - - - - - - - - - - Values for Area Of Interest. - - - - - - - - - - - - - Type for identifier of a ZONe. - - - - - - Type for a reference to a ZONE or locality. - - - - - - - - - - Type for a reference Information about a CONNECTION link from a given stop that is affected by a SITUATION. - - - - - Reference to a CONNECTION link affected by a SITUATION. - - - - - Name of CONNECTION link affected by a SITUATION. - - - - - - - - - Reference to other connecting STOP POINT of a CONNECTION link. 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 link. Derivable from StopRef. (Unbounded since SIRI 2.0) - - - - - Zone in which connecting stop lies. - - - - - - - Direction of SERVICE JOURNEY INTERCHANGE. Default is 'both'. - - - - - PATH LINKs affected by a SITUATION. - - - - - - - - Values for DIRECTION of CONNECTION link or SERVCIE JOURNEY INTERCHANGE. - - - - - - - - - - - Information about a CONNECTION link from a given stop affected by a SITUATION. - - - - - Identifier of CONNECTION link. - - - - - Description of Link. (Unbounded since SIRI 2.0) - - - - - Nature of CONNECTION link. - - - - - Description of a DIRECTION of CONNECTION link. - - - - - 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 SERVICE JOURNEY INTERCHANGE at CONNECTION link from a given SCHEDULED STOP POINT. - - - - - Reference to a SERVICE JOURNEY INTERCHANGE affected by a SITUATION. - - - - - 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. (Unbounded since SIRI 2.0) - - - - - Reference to connecting VEHICLE JOURNEY affected by a SITUATION. - - - - - - Reference to a CONNECTION Link affected by a SITUATION. - - - - - - - - - Type for identifier of an OPERATOR Code. - - - - - - Type for reference to an OPERATOR. - - - - - - - - Type for identifier of an OPERATOR Code. - - - - - - Type for reference to an Operatorational Unit Code. - - - - - - - - Type for Annotated reference to an OPERATOR affected by a SITUATION. - - - - - Reference to an OPERATOR. - - - - - Public Name of OPERATOR. Can be derived from OperatorRef. (Unbounded since SIRI 2.0) - - - - - Short Name for OPERATOR. Can be derived from OperatorRef. (Unbounded since SIRI 2.0) - - - - - OPERATIONAL UNIT responsible for managing services. - - - - - - - - Type for Annotated reference to a NETWORK affected by a SITUATION. - - - - - Reference to a NETWORK. - - - - - Name of NETWORK. Can be derived from NetworkRef. (Unbounded since SIRI 2.0) - - - - - - - - - Type for ideifier of a Route section. - - - - - - Type for reference to a Section. - - - - - - - - Line to which link connects. - - - - - - - - - - Type for identifier of an advisory NOTICE - - - - - - Type for reference to predefined advisory NOTICE. - - - - - - - - - - - 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. (Unbounded since SIRI 2.0) - - - - - Textual description of overall routes affected. Should correspond to any structured description in the AffectedLines element. (Unbounded since SIRI 2.0) - - - - - - - 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 specified for (i) Affected Network (ii) General Context. - - - - - - DESTINATIONs to which the LINE runs. - - - - - DIRECTIONs affected. - - - - - ROUTEs affected if LINE has multiple ROUTEs. - - - - - - Route. - - - - - - - - Sections of LINE affected. - - - - - - - - - - - - - Type for information about the sectons affected by an SITUATION. - - - - - Reference to a section of ROUTE affected by a SITUATION. - - - - - 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. - - - - - Reference to a ROUTE affected by SITUATION. - - - - - DIRECTIONS affected by SITUATION. - - - - - Sections of ROUTE affected by SITUATION. - - - - - - Sections of ROUTE that is affected by SITUATION. - - - - - - - - Stop Poins of the ROUTE. Can be either all or only affected by SITUATION. - - - - - - Indicates whether the list of STOP POINTS contains all STOP POINTS of ROUTE or only affected by SITUATION. - - - - - - Stop Point of the ROUTE - - - - - GIs projection of Link to the next provided StopPoint. NB Line here means Geometry Polyline, not Transmodel Transport Line. - - - - - - - - - ROUTE LINKs affected by SITUATION. - - - - - - - - - - - - - - Type for information about a VEHICLE JOURNEY affected by an SITUATION. - - - - - Use of simple reference is deprecated - - - - Refercence to a VEHICLE JOURENY framed by the day. SIRI 2.0 - - - - - Reference to a service VEHICLE JOURNEY affected by an SITUATION. - - - - - - Reference to a specific DATED VEHICLE JOURNEY affected by an SITUATION. - - - - - Name of journey affected by an SITUATION. (Unbounded since SIRI 2.0) - - - - - OPERATOR of LINE affected by SITUATION. - - - - - Reference to the LINE of the journey affected by an SITUATION. - - - - - - DIRECTION of LINE in which journey runs. - - - - - BLOCK which journey runs. - - - - - Origin SCHEDULED STOP POINTs from which the LINE runs. [equivalent to pti15 1 start_point route_description_type] - - - - - Destination SCHEDULED STOP POINTs to which the LINE runs. [equivalent to pti15 2 destination route_description_type] - - - - - ROUTE affected by the SITUATION. - - - - - Timetabled departure tme of journey from Origin. - - - - - Timetabled arrival time of journey at Destination. - - - - - DESTINATION name shown for journey at the origin. Can be overwritten section by section by the entry in an individual CALl. - - - - - - - CALLs making up VEHICLE JOURNEY [equivalent to TPEG pti15 3 stop, 15_5 not-stopping, 15-6 temporary stop route_description_type] - - - - - - - - - - - - - Type for information about a VEHICLE JOURNEY affected by an SITUATION. - - - - - Reference to a specific VEHICLE affected by an SITUATION. - - - - - Registration plate of VEHICLE - - - - - (Mobile) phone number on which the vehicle can be called - - - - - Internet protocol address of the VEHICLE in form 000.000.000.000 - - - - - Radio address of the VEHICLE - - - - - A reference to the DRIVER or Crew currently logged in to operate a monitored VEHICLE. May be omitted if real-time data is not available - i.e. it is timetabled data. +SIRI v2.0 - - - - - The name oo the Driver or Crew +SIRI v2.0 - - - - - Reference to VEHICLE JOURNEY that VEHICLE is making. - - - - - Location where the VEHICLE was when the situation arised - - - - - Current Location where the VEHICLE - - - - - - - - Whether the VEHICLE is in traffic congestion. If not, present, not known. - - - - - Whether the panic alarm on the VEHICLE is activated. Default is 'false'. - - - - - Whether this is a Headway Service, that is shown as operating at a prescribed interval rather than to a fixed timetable. Default is 'false'. - - - - - - - - Type for information about a CALL affected by an SITUATION. - - - - - - - Order of visit to stop within JORUNYE PATTERN of journey. - - - - - Status of CALL TPEG 13_6 - - - - - - - - - - - - - - - Elements describing the the arrival of a VEHICLE at a SCHEDULED STOP POINT. - - - - - - - - - - - Elements describing the the departure of a VEHICLE from a SCHEDULED STOP POINT. - - - - - - - - - - - - Type for annotated references to a TOPOGRAPHIC PLACE. - - - - - Reference to a SITE or TOPOGRAPHIC PLACE (Locality). - - - - - Alternative identifier of SITE or TOPOGRAPHIC PLACE - - - - - Name of SITE or TOPOGRAPHIC PLACE (locality) in which stop is found. (Unbounded since SIRI 2.0) - - - - - Spatial coordinates of STOP POINT. Derivable from StopRef. - - - - - Category of TOPGRAPHIC PLACE or SITE. - - - - - Reference to an EQUIPMENT found at location. - - - - - Changes to accessibility for SITE. - - - - - - - - - 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. (Unbounded since SIRI 2.0) - - - - - 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. (Unbounded since SIRI 2.0) - - - - - Type of Component. - - - - - - Further qualifcation of affected part of Link projection, - - - - - - - - - - Type for Information on casualties. - - - - - Number of fatalities. - - - - - Number of injured presons. - - - - - -     From 619196f228842aec7f76d8b874c16e206993a2a8 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Thu, 29 Oct 2020 21:54:31 +0100 Subject: [PATCH 217/290] non-functional clean-up and alignment with documentation --- xsd/siri/siri_common_services-v2.0.xsd | 6 +++--- xsd/siri/siri_request_support-v2.0.xsd | 16 ++++++++++++---- xsd/siri/siri_requests-v2.0.xsd | 8 ++++---- xsd/siri_situationExchange_service.xsd | 2 +- 4 files changed, 20 insertions(+), 12 deletions(-) diff --git a/xsd/siri/siri_common_services-v2.0.xsd b/xsd/siri/siri_common_services-v2.0.xsd index 167b350f..986ad957 100644 --- a/xsd/siri/siri_common_services-v2.0.xsd +++ b/xsd/siri/siri_common_services-v2.0.xsd @@ -467,7 +467,7 @@ Rail transport, Roads and road transport - + Description of any error or warning condition. @@ -704,7 +704,7 @@ Rail transport, Roads and road transport Data received Acknowledgement content. - + Description of any error or warning condition. @@ -745,7 +745,7 @@ Rail transport, Roads and road transport - + Reference to an arbitrary unique reference associated with the request which gave rise to this response. diff --git a/xsd/siri/siri_request_support-v2.0.xsd b/xsd/siri/siri_request_support-v2.0.xsd index d3c9ae76..c61558c4 100644 --- a/xsd/siri/siri_request_support-v2.0.xsd +++ b/xsd/siri/siri_request_support-v2.0.xsd @@ -72,7 +72,7 @@ Rail transport, Roads and road transport     - Type for message ref. + Type for reference to a message. @@ -80,15 +80,23 @@ Rail transport, Roads and road transport - Type Unique identifier of Subscription within Participant. + Type for unique identifier of Subscription within Participant. + + + Type for reference to a subscription. + + + + + - Type Unique identifier of Subscription Filter within Participant. + Type for unique identifier of Subscription filter within Participant. @@ -96,7 +104,7 @@ Rail transport, Roads and road transport - Type Unique identifier of Subscription Filter within Participant. + Type for unique identifier of Subscription filter within Participant. diff --git a/xsd/siri/siri_requests-v2.0.xsd b/xsd/siri/siri_requests-v2.0.xsd index e1ed5605..4814e811 100644 --- a/xsd/siri/siri_requests-v2.0.xsd +++ b/xsd/siri/siri_requests-v2.0.xsd @@ -497,7 +497,7 @@ be sent in the initial response (or a portion of the data if MoreData is set to Unique identifier of Subscription filter to which this subscription is assigned. If there is onlya single filter, then can be omitted.     - + Reference to a service subscription: unique within Service and Subscriber. @@ -514,7 +514,7 @@ be sent in the initial response (or a portion of the data if MoreData is set to 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. @@ -526,7 +526,7 @@ be sent in the initial response (or a portion of the data if MoreData is set to 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. @@ -668,7 +668,7 @@ be sent in the initial response (or a portion of the data if MoreData is set to Participant reference that identifies responder.     - + Reference to an arbitrary unique reference associated with the request which gave rise to this response. diff --git a/xsd/siri_situationExchange_service.xsd b/xsd/siri_situationExchange_service.xsd index d36fd25a..523565fb 100644 --- a/xsd/siri_situationExchange_service.xsd +++ b/xsd/siri_situationExchange_service.xsd @@ -411,7 +411,7 @@ Rail transport, Roads and road transport Preferred languages in which to return text values.     - + The maximum number of SITUATION elements to return in a given delivery. The most recent n Events within the look ahead window are included. From a1a7b3423d8f8b9ed2030ebf9333a913b59635d9 Mon Sep 17 00:00:00 2001 From: Christophe Duquesne Date: Mon, 2 Nov 2020 10:46:50 +0100 Subject: [PATCH 218/290] Item List for item counting List of the IDs of the counted items: usefull mainly for reservation and detailed information purposes (Required for compatibility and mapping with existing interfaces) --- xsd/siri_model/siri_facility-v2.0.xsd | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/xsd/siri_model/siri_facility-v2.0.xsd b/xsd/siri_model/siri_facility-v2.0.xsd index de73a2ed..a8862845 100644 --- a/xsd/siri_model/siri_facility-v2.0.xsd +++ b/xsd/siri_model/siri_facility-v2.0.xsd @@ -451,6 +451,20 @@ Rail transport, Roads and road transport Description of what is counted + + + List of the IDs of the counted items: usefull mainly for reservation and detailed information purposes + + + + + + IDs of a counted item + + + + +     From 691dabef6d3913652c0668f87ffd19b521c711e1 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 4 Nov 2020 18:50:47 +0100 Subject: [PATCH 219/290] correct default value of IncludeTranslations --- xsd/siri/siri_request_support-v2.0.xsd | 2 +- xsd/siri_situationExchange_service.xsd | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/xsd/siri/siri_request_support-v2.0.xsd b/xsd/siri/siri_request_support-v2.0.xsd index c61558c4..6cfcffee 100644 --- a/xsd/siri/siri_request_support-v2.0.xsd +++ b/xsd/siri/siri_request_support-v2.0.xsd @@ -148,7 +148,7 @@ Rail transport, Roads and road transport - + Whether additional translations of text names are to be included in elements. If 'false', then only one element should be returned. Default is 'false'. Where multiple values are returned The first element returned will be used as the default value. diff --git a/xsd/siri_situationExchange_service.xsd b/xsd/siri_situationExchange_service.xsd index 523565fb..d36fd25a 100644 --- a/xsd/siri_situationExchange_service.xsd +++ b/xsd/siri_situationExchange_service.xsd @@ -411,7 +411,7 @@ Rail transport, Roads and road transport Preferred languages in which to return text values. - + The maximum number of SITUATION elements to return in a given delivery. The most recent n Events within the look ahead window are included. From 9bd7adea8aa2ea3883a5c9ade42f649589a952c9 Mon Sep 17 00:00:00 2001 From: Pri Date: Wed, 18 Nov 2020 09:24:08 +0100 Subject: [PATCH 220/290] ConsequenceFilter replaced by List of Consequences --- xsd/siri_model/siri_situationActions-v2.0.xsd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xsd/siri_model/siri_situationActions-v2.0.xsd b/xsd/siri_model/siri_situationActions-v2.0.xsd index ae5aa9d1..3536f029 100644 --- a/xsd/siri_model/siri_situationActions-v2.0.xsd +++ b/xsd/siri_model/siri_situationActions-v2.0.xsd @@ -150,9 +150,9 @@ Structured Reason elements. The TpegReason and/or PublicEventReason enumerated values can be used to generate standardized messages for the current Perspective. If no enumerated values are given, ReasonName is used instead. Note: this means that ReasonName is NOT a complete message, but only a (few) word(s) to be included in the message! - + - Filter for matching consequences. Can be used to construct generated messages. + Reference to effects caused by situation From 3f18e9d2dbb6f11d47d820a3605f4ea71c208375 Mon Sep 17 00:00:00 2001 From: Pri Date: Wed, 18 Nov 2020 09:26:36 +0100 Subject: [PATCH 221/290] Remove unused type --- xsd/siri_model/siri_situation-v2.0.xsd | 29 -------------------------- 1 file changed, 29 deletions(-) diff --git a/xsd/siri_model/siri_situation-v2.0.xsd b/xsd/siri_model/siri_situation-v2.0.xsd index 6abe66fe..1dcaec65 100644 --- a/xsd/siri_model/siri_situation-v2.0.xsd +++ b/xsd/siri_model/siri_situation-v2.0.xsd @@ -1235,35 +1235,6 @@ Note: this means that ReasonName is NOT a complete message, but only a (few) wor - - - Filter for matching consequences. Can be used to construct generated messages. - - - - - Period of effect of disruption, if different from that of SITUATION. - - - - - Condition(s) of effect of disruptione. - - - - - Parts of transport network affected by disruption if different from that of SITUATION. - - - - - Advice to passengers. - - - - - - Type for disruption. From 838e4453bb78701c1305f3657dfc53c5ee3d905b Mon Sep 17 00:00:00 2001 From: Pri Date: Tue, 24 Nov 2020 11:21:04 +0100 Subject: [PATCH 222/290] Lines added to StopPlaceStructure according to UmS 1.0 --- xsd/siri_model/siri_situationAffects-v2.0.xsd | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/xsd/siri_model/siri_situationAffects-v2.0.xsd b/xsd/siri_model/siri_situationAffects-v2.0.xsd index 433590de..c47b2d62 100644 --- a/xsd/siri_model/siri_situationAffects-v2.0.xsd +++ b/xsd/siri_model/siri_situationAffects-v2.0.xsd @@ -89,7 +89,7 @@
  • Schema derived Derived from the Kizoom XTIS schema
    • - Version 2.1 + Version 2.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -1182,6 +1182,16 @@ Rail transport, Roads and road transport     + + + Used to restrict stop places to some lines + + + + + + + From 21ba8c2805887595dc0981b1e3d866349d987f26 Mon Sep 17 00:00:00 2001 From: Pri Date: Tue, 1 Dec 2020 08:18:10 +0100 Subject: [PATCH 223/290] AffectedSection definition in new pullrequest for separating CRs --- xsd/siri_model/siri_situationAffects-v2.0.xsd | 85 +++++++++++++++++-- 1 file changed, 76 insertions(+), 9 deletions(-) diff --git a/xsd/siri_model/siri_situationAffects-v2.0.xsd b/xsd/siri_model/siri_situationAffects-v2.0.xsd index 747ac04e..f611b766 100644 --- a/xsd/siri_model/siri_situationAffects-v2.0.xsd +++ b/xsd/siri_model/siri_situationAffects-v2.0.xsd @@ -532,9 +532,14 @@ Rail transport, Roads and road transport All LINEs in the network are affected. - + - Only some ROUTEs are affected, LINE level information not available. See the AffectedRoutes element for textual description. + Only some ROUTEs are affected, LINE level information not available. See the RoutesAffected element for textual description. + + + + + Only some COMMON SECTIONs are affected, LINE level information not available. @@ -550,18 +555,18 @@ Rail transport, Roads and road transport - Type for information about the LINEs affected by a SITUATION. + Information about the individual LINEs in the network that are affected by a SITUATION. If not explicitly overrided, modes and submodes will be defaulted to any values present (i) in the AffectedNetwork (ii) in the General Context. - Operators of LINEs affected by incident. Overrides any value specified for (i) Affected Network (ii) General Context. + Restricts the affected scope to the specified operators of LINEs that are affected by the situation. Overrides any value specified for (i) Affected Network (ii) General Context. - DESTINATIONs to which the LINE runs. + Restricts the affected scope to the specified DIRECTIONs @@ -571,7 +576,7 @@ Rail transport, Roads and road transport - ROUTEs affected if LINE has multiple ROUTEs. + Restricts the affected scope to the specified ROUTEs @@ -585,7 +590,7 @@ Rail transport, Roads and road transport - Sections of LINE affected. + Restricts the affected scope to the specified LINE SECTIONs @@ -598,14 +603,76 @@ Rail transport, Roads and road transport - Type for information about the sectons affected by a SITUATION. + Type for information about the SECTIONs affected by a SITUATION. + Reference to a section of ROUTE affected by a SITUATION. + + + An indirect reference to a COMMON SECTION by stating the stop point ref of the first and last POINT IN JOURNEY PATTERN of the section in question. Intermediate POINTs should be added if necessary to distinguish different sections having the same start and end point and is a means to exclude sections not containing those stop points. + + + + + + + Used to indicate the SCHEDULED stop point with a stop assignment to be considered as start of the SECTION + + + + + Used to indicate that any SCHEDULED stop point with a stop assignment of the indicated StopPlace is to be considered as start of the SECTION + + + + + Used to indicate that any SCHEDULED stop point with a stop assignment to the indicated QUAY is to be considered as start of the SECTION + + + + + + + An intermediate Stop POINT of the SECTION that must be part of SECTION + + + + + Used to indicate that at least one SCHEDULED stop point with a stop assignment of the indicated StopPlace is to be considered as start of the SECTION + + + + + Used to indicate that at least one SCHEDULED stop point with a stop assignment to the indicated QUAY must be part of the SECTION + + + + + + + Used to indicate the SCHEDULED stop point with a stop assignment to be considered as end of the SECTION + + + + + Used to indicate that any SCHEDULED stop point with a stop assignment of the indicated StopPlace is to be considered as end of the SECTION + + + + + Used to indicate that any SCHEDULED stop point with a stop assignment to the indicated QUAY is to be considered as end of the SECTION + + + + + + + Spatial projection of element that can be used to show affected area on a map. @@ -617,7 +684,7 @@ Rail transport, Roads and road transport - Type for information about the routes affected by a SITUATION. + An ordered list of MAPPING POINTs defining one single path through the road (or rail) Network. A ROUTE may pass through the same MAPPING POINT more than once. From e2708dfc4cb4f740784a45ac227032510e9abfc7 Mon Sep 17 00:00:00 2001 From: Pri Date: Tue, 1 Dec 2020 08:45:53 +0100 Subject: [PATCH 224/290] AffectedSection definition in new pullrequest CR83 for separating CRs --- xsd/siri_model/siri_situationAffects-v2.0.xsd | 37 ++----------------- 1 file changed, 3 insertions(+), 34 deletions(-) diff --git a/xsd/siri_model/siri_situationAffects-v2.0.xsd b/xsd/siri_model/siri_situationAffects-v2.0.xsd index c47b2d62..fd092ec1 100644 --- a/xsd/siri_model/siri_situationAffects-v2.0.xsd +++ b/xsd/siri_model/siri_situationAffects-v2.0.xsd @@ -552,14 +552,9 @@ Rail transport, Roads and road transport All LINEs in the network are affected. - + - Only some ROUTEs are affected, LINE level information not available. See the RoutesAffected element for textual description. - - - - - Only some COMMON SECTIONs are affected, LINE level information not available. + Only some ROUTEs are affected, LINE level information not available. See the AffectedRoutes element for textual description. @@ -646,37 +641,11 @@ Rail transport, Roads and road transport Type for information about the SECTIONs affected by a SITUATION. - Reference to a section of ROUTE affected by a SITUATION. - - - An indirect reference to a COMMON SECTION by stating the stop point ref of the first and last POINT IN JOURNEY PATTERN of the section in question. Intermediate POINTs should be added if necessary to distinguish different sections having the same start and end PONT. - - - - - - First Stop POINT of the SECTION - - - - - Any intermediate Stop POINT of the SECTION required for identifying a SECTION - - - - - Last Stop POINT of the SECTION - - - - - - Spatial projection of element that can be used to show affected area on a map. @@ -688,7 +657,7 @@ Rail transport, Roads and road transport - An ordered list of MAPPING POINTs defining one single path through the road (or rail) Network. A ROUTE may pass through the same MAPPING POINT more than once. + Type for information about the routes affected by a SITUATION. From 0f1011376462270e94e294f8801ed85df68e27a6 Mon Sep 17 00:00:00 2001 From: Pri Date: Tue, 1 Dec 2020 08:58:35 +0100 Subject: [PATCH 225/290] Annotation corrected --- xsd/siri_model/siri_situationAffects-v2.0.xsd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xsd/siri_model/siri_situationAffects-v2.0.xsd b/xsd/siri_model/siri_situationAffects-v2.0.xsd index fd092ec1..1faac2c9 100644 --- a/xsd/siri_model/siri_situationAffects-v2.0.xsd +++ b/xsd/siri_model/siri_situationAffects-v2.0.xsd @@ -581,7 +581,7 @@ Rail transport, Roads and road transport - Restricts the affected scope to the specified DIRECTIONs + Restricts the affected scope to the specified DESTINATIONs From b0a83cc75e5127b976b1c925a78181ad476e6ade Mon Sep 17 00:00:00 2001 From: Pri Date: Tue, 1 Dec 2020 10:21:07 +0100 Subject: [PATCH 226/290] Upgrading content according to view-source:https://www.w3.org/2001/xml.xsd into current xml.xsd definition --- xsd/xml/xml.xsd | 387 +++++++++++++++++++++++++++++++++++------------- 1 file changed, 282 insertions(+), 105 deletions(-) diff --git a/xsd/xml/xml.xsd b/xsd/xml/xml.xsd index e75b14bc..e94f87f7 100644 --- a/xsd/xml/xml.xsd +++ b/xsd/xml/xml.xsd @@ -1,109 +1,286 @@ - - - - - See http://www.w3.org/XML/1998/namespace.html and - http://www.w3.org/TR/REC-xml for information about this namespace. - - This schema document describes the XML namespace, in a form - suitable for import by other schema documents. - - Note that local names in this namespace are intended to be defined - only by the World Wide Web Consortium or its subgroups. The - following names are currently defined in this namespace and should - not be used with conflicting semantics by any Working Group, - specification, or document instance: - - base (as an attribute name): denotes an attribute whose value - provides a URI to be used as the base for interpreting any - relative URIs in the scope of the element on which it - appears; its value is inherited. This name is reserved - by virtue of its definition in the XML Base specification. - - lang (as an attribute name): denotes an attribute whose value - is a language code for the natural language of the content of - any element; its value is inherited. This name is reserved - by virtue of its definition in the XML specification. - - space (as an attribute name): denotes an attribute whose - value is a keyword indicating what whitespace processing - discipline is intended for the content of the element; its - value is inherited. This name is reserved by virtue of its - definition in the XML specification. - - Father (in any context at all): denotes Jon Bosak, the chair of - the original XML Working Group. This name is reserved by - the following decision of the W3C XML Plenary and - XML Coordination groups: - - In appreciation for his vision, leadership and dedication - the W3C XML Plenary on this 10th day of February, 2000 - reserves for Jon Bosak in perpetuity the XML name - xml:Father + + + + +
    +

    About the XML namespace

    + +
    +

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

    +

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

    +

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

    +

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

    +
    +
    -     - - 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. + + + + + +
    + +

    lang (as an attribute name)

    +

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

    + +
    +
    +

    Notes

    +

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

    +

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

    +

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

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

    space (as an attribute name)

    +

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

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

    base (as an attribute name)

    +

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

    + +

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

    +
    -     - - - In due course, we should install the relevant ISO 2- and 3-letter - codes as the enumerated possible values . . . - - - - - - - - - - - - - See http://www.w3.org/TR/xmlbase/ for - information about this attribute. - - - - - - - +     + + + + + +
    + +

    id (as an attribute name)

    +

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

    + +

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

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

    Father (in any context at all)

    + +
    +

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

    +
    +

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

    +
    +
    +
    +     +     + + + +
    +

    About this schema document

    + +
    +

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

    +

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

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

    + or +

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

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

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

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

    +
    +
    +     +     + + + +
    +

    Versioning policy for this schema document

    +
    +

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

    +

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

    +

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

    +

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

    + +
    +
    +     +     +     + From abd9a81d05b94287158fe8d4e28029db2475e4de Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 1 Dec 2020 10:34:44 +0100 Subject: [PATCH 227/290] CR081: separate CircularAreaStrc from LocationStrc --- xsd/siri_model/siri_journey-v2.0.xsd | 8 +++---- xsd/siri_utility/siri_location-v2.0.xsd | 31 ++++++++++++++----------- 2 files changed, 22 insertions(+), 17 deletions(-) diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index 4685ade2..a87a52ac 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -771,23 +771,23 @@ To avoid this, the producer should transmit xxxPredictionUnknown instead of any - An approxiimate characterisation of prediction quality as one of five values . +SIRI v2.0 + An approxiimate characterisation of prediction quality as one of five values. +SIRI v2.0 - Percentile associated with range as specified by lower and upper bound +SIRI v2.0 + Percentile associated with range as specified by lower and upper bound. +SIRI v2.0 - Lower bound on time of for prediction for confidence level if different from defaults +SIRI v2.0 + Lower bound on time of for prediction for confidence level if different from defaults. +SIRI v2.0 - Upper bound on time of for predictios for confidence level if different from defaults +SIRI v2.0 + Upper bound on time of for prediction for confidence level if different from defaults. +SIRI v2.0 diff --git a/xsd/siri_utility/siri_location-v2.0.xsd b/xsd/siri_utility/siri_location-v2.0.xsd index 53cc40b9..d15843fc 100644 --- a/xsd/siri_utility/siri_location-v2.0.xsd +++ b/xsd/siri_utility/siri_location-v2.0.xsd @@ -148,7 +148,7 @@ Rail transport, Roads and road transport - Type for gepspatial Position of a point. May be expressed in concrete WGS 84 Coordinates or any gml compatible point coordinates format. + Type for geospatial Position of a point. May be expressed in concrete WGS 84 Coordinates or any gml compatible point coordinates format. @@ -161,11 +161,6 @@ Rail transport, Roads and road transport     - - - Radius in case the location is specified as a circular area. In meters. +SIRI v2.1 - - Precision for point measurement. In meters. @@ -190,16 +185,12 @@ Rail transport, Roads and road transport - A geospatial point. -Upper Left corner. -. + Upper Left corner as a geospatial point. - A geospatial point. -Lower right corner. -. + Lower right corner as a geospatial point. @@ -216,6 +207,20 @@ Lower right corner.     + + + Type for a circular area centered around a point that may be expressed in concrete WGS 84 Coordinates or any gml compatible point coordinates format. +SIRI v2.1 + + + + + + Radius around the center point in meters. + + + + + Bounding box, circular area or gml:polyon of the area where stops of a flexible service are called. +SIRI v2.1 @@ -227,7 +232,7 @@ A flexible area is used in cases where a pre-booked service allows pick-up/drop- Flexible area specified as a rectangular bounding box.     - + Flexible area specified as a circular area (center coordinates and radius). From c9c902d4e8a34b7a34e712d2ec7ebc4ee5523591 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 2 Dec 2020 11:47:45 +0100 Subject: [PATCH 228/290] CR081: fix mistake in CircularAreaStructure --- xsd/siri_utility/siri_location-v2.0.xsd | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/xsd/siri_utility/siri_location-v2.0.xsd b/xsd/siri_utility/siri_location-v2.0.xsd index d15843fc..1b1782fc 100644 --- a/xsd/siri_utility/siri_location-v2.0.xsd +++ b/xsd/siri_utility/siri_location-v2.0.xsd @@ -213,11 +213,13 @@ Rail transport, Roads and road transport - - - Radius around the center point in meters. - - + + + + Radius around the center point in meters. + + + From 556774f103897e58b34dc0dd955798e0165b7c90 Mon Sep 17 00:00:00 2001 From: Pri Date: Mon, 7 Dec 2020 16:38:30 +0100 Subject: [PATCH 229/290] Typos corrected --- examples/siri_exm_SX/exx_situationExchangeResponse.xml | 2 +- examples/siri_exm_SX/exx_situationExchange_ATOC.xml | 2 +- examples/siri_exm_SX/exx_situationExchange_Pt.xml | 2 +- examples/siri_exm_SX/exx_situationExchange_response.xml | 2 +- xsd/siri.xsd | 2 +- xsd/siri/siri_requests-v2.0.xsd | 8 ++++---- xsd/siri_model/siri_situationActions-v2.0.xsd | 4 ++-- xsd/siri_model/siri_situationAffects-v2.0.xsd | 2 +- 8 files changed, 12 insertions(+), 12 deletions(-) diff --git a/examples/siri_exm_SX/exx_situationExchangeResponse.xml b/examples/siri_exm_SX/exx_situationExchangeResponse.xml index 87d98ac4..cdeaace9 100644 --- a/examples/siri_exm_SX/exx_situationExchangeResponse.xml +++ b/examples/siri_exm_SX/exx_situationExchangeResponse.xml @@ -46,7 +46,7 @@ public point Bomb at Barchester station - Building evacuated. AVoid station untile furtehr notice + Building evacuated. Avoid station until further notice diff --git a/examples/siri_exm_SX/exx_situationExchange_ATOC.xml b/examples/siri_exm_SX/exx_situationExchange_ATOC.xml index 991cccd5..c0661d54 100644 --- a/examples/siri_exm_SX/exx_situationExchange_ATOC.xml +++ b/examples/siri_exm_SX/exx_situationExchange_ATOC.xml @@ -35,7 +35,7 @@ public point Bomb at Barchester station - Building evacuated. AVoid station untile furtehr notice + Building evacuated. Avoid station until further notice diff --git a/examples/siri_exm_SX/exx_situationExchange_Pt.xml b/examples/siri_exm_SX/exx_situationExchange_Pt.xml index 6abf1c75..9e075e11 100644 --- a/examples/siri_exm_SX/exx_situationExchange_Pt.xml +++ b/examples/siri_exm_SX/exx_situationExchange_Pt.xml @@ -35,7 +35,7 @@ public point Bomb at Barchester station - Building evacuated. AVoid station untile furtehr notice + Building evacuated. Avoid station until further notice diff --git a/examples/siri_exm_SX/exx_situationExchange_response.xml b/examples/siri_exm_SX/exx_situationExchange_response.xml index 5d4e78ba..ade2e6b8 100644 --- a/examples/siri_exm_SX/exx_situationExchange_response.xml +++ b/examples/siri_exm_SX/exx_situationExchange_response.xml @@ -46,7 +46,7 @@ public point Bomb at Barchester station - Building evacuated. AVoid station untile further notice + Building evacuated. Avoid station until further notice diff --git a/xsd/siri.xsd b/xsd/siri.xsd index 7eb08e0a..21b5db08 100644 --- a/xsd/siri.xsd +++ b/xsd/siri.xsd @@ -466,7 +466,7 @@ Rail transport, Roads and road transport. - If request has been proxied by an intermediate aggregting system, trackng informattion relating to the original requestor. This allows the aggregation to be stateless + If request has been proxied by an intermediate aggregating system, tracking information relating to the original requestor. This allows the aggregation to be stateless diff --git a/xsd/siri/siri_requests-v2.0.xsd b/xsd/siri/siri_requests-v2.0.xsd index 18974cfd..b0a5e82d 100644 --- a/xsd/siri/siri_requests-v2.0.xsd +++ b/xsd/siri/siri_requests-v2.0.xsd @@ -208,7 +208,7 @@ - If request has been proxied by an intermediate aggregating system , tracking informattion relating to the original requestor. This allows the aggregation to be stateless. + If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. @@ -448,7 +448,7 @@ - If request has been proxied by an intermediate aggregting system, trackng informattion relating to the original requestor. This allows the aggregation to be stateless. + If request has been proxied by an intermediate aggregating system, tracking information relating to the original requestor. This allows the aggregation to be stateless. @@ -628,7 +628,7 @@ - If request has been proxied by an intermediate aggregting system, trackng informattion relating to the original requestor. This allows the aggregation to be stateless. + If request has been proxied by an intermediate aggregating system, tracking information relating to the original requestor. This allows the aggregation to be stateless. @@ -873,7 +873,7 @@ - If request has been proxied by an intermediate aggregting system, trackng informattion relating to the original requestor. This allows the aggregation to be stateless. + If request has been proxied by an intermediate aggregating system, tracking information relating to the original requestor. This allows the aggregation to be stateless. diff --git a/xsd/siri_model/siri_situationActions-v2.0.xsd b/xsd/siri_model/siri_situationActions-v2.0.xsd index 548f2304..f348c498 100644 --- a/xsd/siri_model/siri_situationActions-v2.0.xsd +++ b/xsd/siri_model/siri_situationActions-v2.0.xsd @@ -676,7 +676,7 @@ - Summary of passenger information action. + For internal information only, not passenger relevant. @@ -725,7 +725,7 @@ - for internal information only, not passenger relevant + For internal information only, not passenger relevant diff --git a/xsd/siri_model/siri_situationAffects-v2.0.xsd b/xsd/siri_model/siri_situationAffects-v2.0.xsd index 1faac2c9..640788bc 100644 --- a/xsd/siri_model/siri_situationAffects-v2.0.xsd +++ b/xsd/siri_model/siri_situationAffects-v2.0.xsd @@ -810,7 +810,7 @@ Rail transport, Roads and road transport - Destination SCHEDULED STOP POINTs to which the LINE runs. [equivalent to pti15 2 destination route_description_type] + Restricts the affected scope to the specified DESTINATIONs From dc213d41167792fc7a1c224ccf75e89b22bd7f30 Mon Sep 17 00:00:00 2001 From: Pri Date: Mon, 7 Dec 2020 16:45:46 +0100 Subject: [PATCH 230/290] Added stylesheet for displaying schema --- xsd/xml/2008/09/xsd.xsl | 997 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 997 insertions(+) create mode 100644 xsd/xml/2008/09/xsd.xsl diff --git a/xsd/xml/2008/09/xsd.xsl b/xsd/xml/2008/09/xsd.xsl new file mode 100644 index 00000000..32277ae1 --- /dev/null +++ b/xsd/xml/2008/09/xsd.xsl @@ -0,0 +1,997 @@ + + + + + + + + + + + + + + +]> + + + + + + + + + + + + + + + + + + + + + Schema document for + + + namespace + + + + unspecified namespace + + + + + + + + + + + + + + text/css + .bodytext .bodytext { + margin-left: 0; + margin-right: 0; + } + .bodytext { + margin-left: 15%; + margin-right: 2%; + } + .annotation { + + + } + .same-ns { + color: Green; + } + .diff-ns { + color: maroon; + } + .warning { + color: red; + } + p.note { + font-style: italic; + } + p.dt { + font-weight: bold; + } + span.rfc { + font-variant: small-caps; + } + + + + + + + + * * + + + + + + + + + + + bodytext + + + + + + + + + + + + + + + + + + + + + + annotation + + + + + + Annotation + + + + + + + + bodytext + + + + + + + + + + + + + + ! Unrecognized children in xs:documentation element + + + + + + + + + + + + + + + + + + + + + + +   + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + bodytext + + + + + Notes + + + + + External documentation at + + + + + + + + + + + + + + + Formal declaration in XSD source form + + + + + + + + + + + + + + + + + + + + + + + + + + + + + < + + + + + break + nobreak + + + + + + + + + + + > + + </ + + > + + /> + + + + + + + + + nobreak + + + + + + + + + + + + + + + + + + + + + + + =" + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + " + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Warning: not matched. + + warning + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + external-link same-ns + + + + + + external-link diff-ns + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + attnames + + + + + + attvals + + + + + + + + + + + + + + + + + + unknown + + + + + + + + 0 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + From a2e44183c304b56a84bc16f563542ca21d25751c Mon Sep 17 00:00:00 2001 From: Pri Date: Mon, 7 Dec 2020 16:50:09 +0100 Subject: [PATCH 231/290] Added view-source:https://www.w3.org/2005/08/xml.xsd in xml.xsd --- xsd/xml/2008/09/xsd.xsl | 997 ---------------------------------------- xsd/xml/xml.xsd | 346 +++++--------- 2 files changed, 103 insertions(+), 1240 deletions(-) delete mode 100644 xsd/xml/2008/09/xsd.xsl diff --git a/xsd/xml/2008/09/xsd.xsl b/xsd/xml/2008/09/xsd.xsl deleted file mode 100644 index 32277ae1..00000000 --- a/xsd/xml/2008/09/xsd.xsl +++ /dev/null @@ -1,997 +0,0 @@ - - - - - - - - - - - - - - -]> - - - - - - - - - - - - - - - - - - - - - Schema document for - - - namespace - - - - unspecified namespace - - - - - - - - - - - - - - text/css - .bodytext .bodytext { - margin-left: 0; - margin-right: 0; - } - .bodytext { - margin-left: 15%; - margin-right: 2%; - } - .annotation { - - - } - .same-ns { - color: Green; - } - .diff-ns { - color: maroon; - } - .warning { - color: red; - } - p.note { - font-style: italic; - } - p.dt { - font-weight: bold; - } - span.rfc { - font-variant: small-caps; - } - - - - - - - - * * - - - - - - - - - - - bodytext - - - - - - - - - - - - - - - - - - - - - - annotation - - - - - - Annotation - - - - - - - - bodytext - - - - - - - - - - - - - - ! Unrecognized children in xs:documentation element - - - - - - - - - - - - - - - - - - - - - - -   - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - bodytext - - - - - Notes - - - - - External documentation at - - - - - - - - - - - - - - - Formal declaration in XSD source form - - - - - - - - - - - - - - - - - - - - - - - - - - - - - < - - - - - break - nobreak - - - - - - - - - - - > - - </ - - > - - /> - - - - - - - - - nobreak - - - - - - - - - - - - - - - - - - - - - - - =" - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - " - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Warning: not matched. - - warning - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - external-link same-ns - - - - - - external-link diff-ns - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - attnames - - - - - - attvals - - - - - - - - - - - - - - - - - - unknown - - - - - - - - 0 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/xsd/xml/xml.xsd b/xsd/xml/xml.xsd index e94f87f7..e5cbefe0 100644 --- a/xsd/xml/xml.xsd +++ b/xsd/xml/xml.xsd @@ -1,78 +1,107 @@ - - - + + + -
    -

    About the XML namespace

    - -
    -

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

    -

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

    -

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

    -

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

    -
    -
    + See http://www.w3.org/XML/1998/namespace.html and + http://www.w3.org/TR/REC-xml for information about this namespace. + + This schema document describes the XML namespace, in a form + suitable for import by other schema documents. + + Note that local names in this namespace are intended to be defined + only by the World Wide Web Consortium or its subgroups. The + following names are currently defined in this namespace and should + not be used with conflicting semantics by any Working Group, + specification, or document instance: + + base (as an attribute name): denotes an attribute whose value + provides a URI to be used as the base for interpreting any + relative URIs in the scope of the element on which it + appears; its value is inherited. This name is reserved + by virtue of its definition in the XML Base specification. + + id (as an attribute name): denotes an attribute whose value + should be interpreted as if declared to be of type ID. + The xml:id specification is not yet a W3C Recommendation, + but this attribute is included here to facilitate experimentation + with the mechanisms it proposes. Note that it is _not_ included + in the specialAttrs attribute group. + + lang (as an attribute name): denotes an attribute whose value + is a language code for the natural language of the content of + any element; its value is inherited. This name is reserved + by virtue of its definition in the XML specification. + + space (as an attribute name): denotes an attribute whose + value is a keyword indicating what whitespace processing + discipline is intended for the content of the element; its + value is inherited. This name is reserved by virtue of its + definition in the XML specification. + + Father (in any context at all): denotes Jon Bosak, the chair of + the original XML Working Group. This name is reserved by + the following decision of the W3C XML Plenary and + XML Coordination groups: + + In appreciation for his vision, leadership and dedication + the W3C XML Plenary on this 10th day of February, 2000 + reserves for Jon Bosak in perpetuity the XML name + xml:Father +     +     + + + This schema defines attributes and an attribute group + suitable for use by + schemas wishing to allow xml:base, xml:lang, xml:space or xml:id + attributes on elements they define. + + To enable this, such a schema must import this schema + for the XML namespace, e.g. as follows: + <schema . . .> + . . . + <import namespace="http://www.w3.org/XML/1998/namespace" + schemaLocation="http://www.w3.org/2005/08/xml.xsd"/> + + Subsequently, qualified reference to any of the attributes + or the group defined below will have the desired effect, e.g. + + <type . . .> + . . . + <attributeGroup ref="xml:specialAttrs"/> + + will define a type which will schema-validate an instance + element with any of those attributes + + + + In keeping with the XML Schema WG's standard versioning + policy, this schema document will persist at + http://www.w3.org/2005/08/xml.xsd. + At the date of issue it can also be found at + http://www.w3.org/2001/xml.xsd. + The schema document at that URI may however change in the future, + in order to remain compatible with the latest version of XML Schema + itself, or with the XML namespace itself. In other words, if the XML + Schema or XML namespaces change, the version of this document at + http://www.w3.org/2001/xml.xsd will change + accordingly; the version at + http://www.w3.org/2005/08/xml.xsd will not change. - -
    - -

    lang (as an attribute name)

    -

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

    + Attempting to install the relevant ISO 2- and 3-letter + codes as the enumerated possible values is probably never + going to be a realistic possibility. See + RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry + at http://www.iana.org/assignments/lang-tag-apps.htm for + further information. -
    -
    -

    Notes

    -

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

    -

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

    -

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

    -
    -     + The union allows for the 'un-declaration' of xml:lang with + the empty string.     @@ -86,21 +115,6 @@     - - -
    - -

    space (as an attribute name)

    -

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

    - -
    -     -     @@ -109,47 +123,17 @@     - - -
    - -

    base (as an attribute name)

    -

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

    - -

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

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

    id (as an attribute name)

    -

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

    - -

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

    -
    -     + See http://www.w3.org/TR/xml-id/ for + information about this attribute.     @@ -157,130 +141,6 @@ - - - - -
    - -

    Father (in any context at all)

    - -
    -

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

    -
    -

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

    -
    -
    -
    -     -     - - - -
    -

    About this schema document

    - -
    -

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

    -

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

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

    - or -

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

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

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

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

    -
    -
    -     -     - - - -
    -

    Versioning policy for this schema document

    -
    -

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

    -

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

    -

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

    -

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

    - -
    -
    -     -     - From 1162aee94567dcf60ddcfc9924ecbfb97b367912 Mon Sep 17 00:00:00 2001 From: Pri Date: Mon, 7 Dec 2020 17:07:02 +0100 Subject: [PATCH 232/290] Added reference where xml schema is imported from view-source:https://www.w3.org/2009/01/xml.xsd --- xsd/siri_utility/siri_types-v2.0.xsd | 2 +- xsd/xml/2008/09/xsd.xsl | 997 +++++++++++++++++++++++++++ xsd/xml/2009/01/XMLSchema.xsd | 286 ++++++++ xsd/xml/xml.xsd | 146 ---- 4 files changed, 1284 insertions(+), 147 deletions(-) create mode 100644 xsd/xml/2008/09/xsd.xsl create mode 100644 xsd/xml/2009/01/XMLSchema.xsd delete mode 100644 xsd/xml/xml.xsd diff --git a/xsd/siri_utility/siri_types-v2.0.xsd b/xsd/siri_utility/siri_types-v2.0.xsd index 9de24d20..236b39a2 100644 --- a/xsd/siri_utility/siri_types-v2.0.xsd +++ b/xsd/siri_utility/siri_types-v2.0.xsd @@ -1,6 +1,6 @@ - + diff --git a/xsd/xml/2008/09/xsd.xsl b/xsd/xml/2008/09/xsd.xsl new file mode 100644 index 00000000..32277ae1 --- /dev/null +++ b/xsd/xml/2008/09/xsd.xsl @@ -0,0 +1,997 @@ + + + + + + + + + + + + + + +]> + + + + + + + + + + + + + + + + + + + + + Schema document for + + + namespace + + + + unspecified namespace + + + + + + + + + + + + + + text/css + .bodytext .bodytext { + margin-left: 0; + margin-right: 0; + } + .bodytext { + margin-left: 15%; + margin-right: 2%; + } + .annotation { + + + } + .same-ns { + color: Green; + } + .diff-ns { + color: maroon; + } + .warning { + color: red; + } + p.note { + font-style: italic; + } + p.dt { + font-weight: bold; + } + span.rfc { + font-variant: small-caps; + } + + + + + + + + * * + + + + + + + + + + + bodytext + + + + + + + + + + + + + + + + + + + + + + annotation + + + + + + Annotation + + + + + + + + bodytext + + + + + + + + + + + + + + ! Unrecognized children in xs:documentation element + + + + + + + + + + + + + + + + + + + + + + +   + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + bodytext + + + + + Notes + + + + + External documentation at + + + + + + + + + + + + + + + Formal declaration in XSD source form + + + + + + + + + + + + + + + + + + + + + + + + + + + + + < + + + + + break + nobreak + + + + + + + + + + + > + + </ + + > + + /> + + + + + + + + + nobreak + + + + + + + + + + + + + + + + + + + + + + + =" + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + " + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Warning: not matched. + + warning + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + external-link same-ns + + + + + + external-link diff-ns + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + attnames + + + + + + attvals + + + + + + + + + + + + + + + + + + unknown + + + + + + + + 0 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/xsd/xml/2009/01/XMLSchema.xsd b/xsd/xml/2009/01/XMLSchema.xsd new file mode 100644 index 00000000..60bb6c56 --- /dev/null +++ b/xsd/xml/2009/01/XMLSchema.xsd @@ -0,0 +1,286 @@ + + + + + + +
    +

    About the XML namespace

    + +
    +

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

    +

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

    +

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

    +

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

    +
    +
    +     +     + + + + +
    + +

    lang (as an attribute name)

    +

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

    + +
    +
    +

    Notes

    +

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

    +

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

    +

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

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

    space (as an attribute name)

    +

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

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

    base (as an attribute name)

    +

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

    + +

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

    +
    +     +     +     + + + + +
    + +

    id (as an attribute name)

    +

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

    + +

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

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

    Father (in any context at all)

    + +
    +

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

    +
    +

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

    +
    +
    +
    +     +     + + + +
    +

    About this schema document

    + +
    +

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

    +

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

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

    + or +

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

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

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

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

    +
    +
    +     +     + + + +
    +

    Versioning policy for this schema document

    +
    +

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

    +

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

    +

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

    +

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

    + +
    +
    +     +     + +     diff --git a/xsd/xml/xml.xsd b/xsd/xml/xml.xsd deleted file mode 100644 index e5cbefe0..00000000 --- a/xsd/xml/xml.xsd +++ /dev/null @@ -1,146 +0,0 @@ - - - - - - See http://www.w3.org/XML/1998/namespace.html and - http://www.w3.org/TR/REC-xml for information about this namespace. - - This schema document describes the XML namespace, in a form - suitable for import by other schema documents. - - Note that local names in this namespace are intended to be defined - only by the World Wide Web Consortium or its subgroups. The - following names are currently defined in this namespace and should - not be used with conflicting semantics by any Working Group, - specification, or document instance: - - base (as an attribute name): denotes an attribute whose value - provides a URI to be used as the base for interpreting any - relative URIs in the scope of the element on which it - appears; its value is inherited. This name is reserved - by virtue of its definition in the XML Base specification. - - id (as an attribute name): denotes an attribute whose value - should be interpreted as if declared to be of type ID. - The xml:id specification is not yet a W3C Recommendation, - but this attribute is included here to facilitate experimentation - with the mechanisms it proposes. Note that it is _not_ included - in the specialAttrs attribute group. - - lang (as an attribute name): denotes an attribute whose value - is a language code for the natural language of the content of - any element; its value is inherited. This name is reserved - by virtue of its definition in the XML specification. - - space (as an attribute name): denotes an attribute whose - value is a keyword indicating what whitespace processing - discipline is intended for the content of the element; its - value is inherited. This name is reserved by virtue of its - definition in the XML specification. - - Father (in any context at all): denotes Jon Bosak, the chair of - the original XML Working Group. This name is reserved by - the following decision of the W3C XML Plenary and - XML Coordination groups: - - In appreciation for his vision, leadership and dedication - the W3C XML Plenary on this 10th day of February, 2000 - reserves for Jon Bosak in perpetuity the XML name - xml:Father - - - - - This schema defines attributes and an attribute group - suitable for use by - schemas wishing to allow xml:base, xml:lang, xml:space or xml:id - attributes on elements they define. - - To enable this, such a schema must import this schema - for the XML namespace, e.g. as follows: - <schema . . .> - . . . - <import namespace="http://www.w3.org/XML/1998/namespace" - schemaLocation="http://www.w3.org/2005/08/xml.xsd"/> - - Subsequently, qualified reference to any of the attributes - or the group defined below will have the desired effect, e.g. - - <type . . .> - . . . - <attributeGroup ref="xml:specialAttrs"/> - - will define a type which will schema-validate an instance - element with any of those attributes - - - - In keeping with the XML Schema WG's standard versioning - policy, this schema document will persist at - http://www.w3.org/2005/08/xml.xsd. - At the date of issue it can also be found at - http://www.w3.org/2001/xml.xsd. - The schema document at that URI may however change in the future, - in order to remain compatible with the latest version of XML Schema - itself, or with the XML namespace itself. In other words, if the XML - Schema or XML namespaces change, the version of this document at - http://www.w3.org/2001/xml.xsd will change - accordingly; the version at - http://www.w3.org/2005/08/xml.xsd will not change. - - - - - - Attempting to install the relevant ISO 2- and 3-letter - codes as the enumerated possible values is probably never - going to be a realistic possibility. See - RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry - at http://www.iana.org/assignments/lang-tag-apps.htm for - further information. - - The union allows for the 'un-declaration' of xml:lang with - the empty string. - - - - - - - - - - - - - - - - - - - - - - - - See http://www.w3.org/TR/xmlbase/ for - information about this attribute. - - - - - - See http://www.w3.org/TR/xml-id/ for - information about this attribute. - - - - - - - - - - From 3e0a479f79da826ac0e076dc895f6469111c8711 Mon Sep 17 00:00:00 2001 From: Pri Date: Mon, 14 Dec 2020 07:22:29 +0100 Subject: [PATCH 233/290] Stop assignment requirement in section --- xsd/siri_model/siri_situationAffects-v2.0.xsd | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/xsd/siri_model/siri_situationAffects-v2.0.xsd b/xsd/siri_model/siri_situationAffects-v2.0.xsd index f611b766..7f6a87a4 100644 --- a/xsd/siri_model/siri_situationAffects-v2.0.xsd +++ b/xsd/siri_model/siri_situationAffects-v2.0.xsd @@ -621,12 +621,12 @@ Rail transport, Roads and road transport - Used to indicate the SCHEDULED stop point with a stop assignment to be considered as start of the SECTION + Used to indicate the SCHEDULED stop point at the start of the SECTION - Used to indicate that any SCHEDULED stop point with a stop assignment of the indicated StopPlace is to be considered as start of the SECTION + Used to indicate that any SCHEDULED stop point with a stop assignment to the indicated StopPlace is to be considered as start of the SECTION @@ -635,15 +635,15 @@ Rail transport, Roads and road transport     - - + + An intermediate Stop POINT of the SECTION that must be part of SECTION - Used to indicate that at least one SCHEDULED stop point with a stop assignment of the indicated StopPlace is to be considered as start of the SECTION + Used to indicate that at least one SCHEDULED stop point with a stop assignment to the indicated StopPlace must be part of the SECTION @@ -655,12 +655,12 @@ Rail transport, Roads and road transport - Used to indicate the SCHEDULED stop point with a stop assignment to be considered as end of the SECTION + Used to indicate the SCHEDULED stop point at the end of the SECTION - Used to indicate that any SCHEDULED stop point with a stop assignment of the indicated StopPlace is to be considered as end of the SECTION + Used to indicate that any SCHEDULED stop point with a stop assignment to the indicated StopPlace is to be considered as end of the SECTION From 91a1d99c9d38ee74cc85f919886393f6b5840111 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Mon, 14 Dec 2020 19:13:33 +0100 Subject: [PATCH 234/290] CR069: structural changes from UmS VDV736 v1.0 without the changes to siri_modes and siri_situationServiceTypes --- xsd/siri_model/siri_situation-v2.0.xsd | 21 +- xsd/siri_model/siri_situationActions-v2.0.xsd | 311 +++++++++++++++++- xsd/siri_model/siri_situationAffects-v2.0.xsd | 60 +++- .../siri_situationClassifiers-v1.1.xsd | 160 ++------- xsd/siri_model/siri_situationReasons-v2.0.xsd | 166 +++++++++- 5 files changed, 572 insertions(+), 146 deletions(-) diff --git a/xsd/siri_model/siri_situation-v2.0.xsd b/xsd/siri_model/siri_situation-v2.0.xsd index 905ed0e0..d9cea90f 100644 --- a/xsd/siri_model/siri_situation-v2.0.xsd +++ b/xsd/siri_model/siri_situation-v2.0.xsd @@ -1,11 +1,26 @@ + + + @@ -472,7 +487,7 @@ Rail transport, Roads and road transport Type for a source, i.e. provider of information. - + Country of origin of source element. @@ -651,7 +666,7 @@ Rail transport, Roads and road transport - + Publication Window for SITUATION if different from validity period. @@ -1119,7 +1134,7 @@ Rail transport, Roads and road transport Type for disruption. - + Period of effect of disruption, if different from that of SITUATION. diff --git a/xsd/siri_model/siri_situationActions-v2.0.xsd b/xsd/siri_model/siri_situationActions-v2.0.xsd index f1919f1c..75dfc5c7 100644 --- a/xsd/siri_model/siri_situationActions-v2.0.xsd +++ b/xsd/siri_model/siri_situationActions-v2.0.xsd @@ -1,5 +1,39 @@ + + + + + + @@ -18,16 +52,10 @@ 2013-10-01 (a) Added PublishToDisplayAction element definition (b) Corrected default values for string fields - + 2013-05-01 [de] Add SocialNetworks to PublishToWeb action - - 2018-11-13 - [vdv] ActionsStructure.ActionsGroup.PublishToTvAction changed to unbounded - [vdv] ActionsStructure.ActionsGroup.NotifyBySmsAction changed to unbounded - [vdv] PublishToDisplayAction added to ActionsGroup - [vdv] ActionsStructure.ActionsGroup.PublishToTvAction.Ceefax and Teletext: annotation switched - +

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

    @@ -44,8 +72,8 @@ Unclassified - Kizoom 2000-2007, CEN 2009-2014 - + Kizoom 2000-2007, CEN 2009-2014 +
    • Schema derived Derived from the Kizoom XTIS schema
      • @@ -77,6 +105,11 @@ Rail transport, Roads and road transport + + + Description of the whole action to be published. >SIRI 2.0 + + Extension point. @@ -115,6 +148,11 @@ Rail transport, Roads and road transport Data associated with action. + + + Defines a number of validity periods. When not sent, then the validity periods of higher level are valid. Can be overwritten by deeper level. + + @@ -467,4 +505,257 @@ Rail transport, Roads and road transport + + + + + + + + + + + + + + + + + + Description of SITUATION. Should not repeat any strap line included in Summary. (Unbounded since SIRI 2.0) + + + + + Prioritises a description from the information owner's point of view, e.g. usable for sorting or hiding individual descriptions. +1 = highest priority. + + + + + + + + + Further consequence to passengers. (Unbounded since SIRI 2.0) + + + + + Prioritises a consequence from the information owner's point of view, e.g. usable for sorting or hiding individual consequences. +1 = highest priority. + + + + + + + Duration of specific time range (smaller than 24h). StartTime plus Duration can result in a time on the next day, smaller than the StartTime. + + + + + + + + + + + Further information about the duration to passengers. + + + + + + + + + + + + Reference to the action number within the incident concept. + + + + + The time of the last update + + + + + The monotonically inscresing version of the passenger information instance. If absent, is the same version as the enclosing Situation + + + + + The system which created this passenger information. If absent, is the same version as the enclosing Situation + + + + + The organisation which owns this passenger information. + + + + + Perspective of the passenger, e.g. general, vehicleJourney, stopPoint. + + + + + Prioritises a passenger information action from the information owner's point of view, e.g. suitable for sorting or hiding individual passenger information actions. +1 = highest priority. + + + + + All texts of the passenger information. + + + + + + + + + Type for description of the whole action to be published (extends SIRI-SX v2.0p). + + + + + Defines the information area where the action has to be published. + + + + + + + + + + + Description of the whole passenger information of one action. + + + + + + + + + ReasonName of passenger information action. + + + + + + + + + Further recommendation to passengers. (Unbounded since SIRI 2.0) + + + + + Prioritises a recommendation from the information owner's point of view, e.g. usable for sorting or hiding individual recommendations. +1 = highest priority. + + + + + + + + + + + + + + Further remark to passengers, e,g, "For more information call xy". + + + + + Prioritises a remark from the information owner's point of view, e.g. usable for sorting or hiding individual remarks. +1 = highest priority. + + + + + + + + + Summary of passenger information action. + + + + + + + + + Class of size, e.g. L (large), M (medium), S (small) + + + + + + Content for summary of a passenger information action + + + + + + Content for n descriptions of a passenger information action + + + + + Content for n consequences of a passenger information action + + + + + Content for n recommendations of a passenger information action + + + + + Content to inform about a passenger information action. + + + + + Content for n remarks of a passenger information action, e,g, "For more information call xy". + + + + + Hyperlinks to other resources associated with SITUATION. + + + + + Any images associated with SITUATION. + + + + + for internal information only, not passenger relevant + + + + + + + Values for perspectives. + + + + + + + diff --git a/xsd/siri_model/siri_situationAffects-v2.0.xsd b/xsd/siri_model/siri_situationAffects-v2.0.xsd index 8eca886d..707435b8 100644 --- a/xsd/siri_model/siri_situationAffects-v2.0.xsd +++ b/xsd/siri_model/siri_situationAffects-v2.0.xsd @@ -47,11 +47,19 @@ * [de] Add IncludeOnly-IfInPublicationWindow to situation request temporal filter siri_situationExchange_service.xsd. * [doc/fx] Correct capability Matrix siri_situationExchange_service.xsd. + 2018-06-13 + [vdv-UmS] StopPoints and StopPlaces added to AffectedLineStructure to be able to restrict line-oriented information for specific stopping points or stops + [vdv-UmS] Lines added to AffectedStopPointStructure and AffectedStopPlaceStructure to be able to restrict stopping point- or stop-oriented information for specific lines + 2018-11-08 [vdv] Wrapped "AffectedInterchanges" node around AffectedInterchange in AffectedCallStructure [vdv] "PublishedLineName" inside "LineGroup" and "AffectedVehicleJourneyStructure" changed to "unbounded" to allow multiple definitions for different languages due to the xml:lang-Attribute + [VDV-UmS] optional "StopPlaceName" (unbounded because of lang-attr.) and optional "StopPlaceRef" inserted to "AffectedStopPointStructure" to be able to send stop information for the affected StopPoint [vdv] "Route" inside "AffectedVehicleJourneyStructure" is now optional since all of its content are optional + 2019-05-07 + [VDV-UmS] "AffectedLines" inside "LineGroup" changed to "AffectedLine" +

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

      @@ -122,6 +130,16 @@ Rail transport, Roads and road transport Spatial coordinates of STOP POINT. Derivable from StopRef.       + + + Reference of Stop Place related to this affected StopPoint. + + + + + Name of Stop Place related to this affected StopPoint. (Unbounded to allow a text for every language) + + Modes within station/stop affected by the SITUATION. If not specified, assume all modes of that station. @@ -161,6 +179,16 @@ Rail transport, Roads and road transport + + + Used to restrict stop points to some lines + + + + + + + @@ -594,6 +622,26 @@ Rail transport, Roads and road transport + + + Used to restrict lines to some stop points + + + + + + + + + + Used to restrict lines to some stop places + + + + + + + @@ -962,7 +1010,7 @@ Rail transport, Roads and road transport - + @@ -1112,6 +1160,16 @@ Rail transport, Roads and road transport + + + Used to restrict stop places to some lines + + + + + + + diff --git a/xsd/siri_model/siri_situationClassifiers-v1.1.xsd b/xsd/siri_model/siri_situationClassifiers-v1.1.xsd index fbd0cbf1..369c3443 100644 --- a/xsd/siri_model/siri_situationClassifiers-v1.1.xsd +++ b/xsd/siri_model/siri_situationClassifiers-v1.1.xsd @@ -1,4 +1,5 @@ + @@ -124,140 +125,43 @@ Rail transport, Roads and road transport - Classification of effect on service. TPEG Pti13 Service Condition values. + Classification of effect on service. TPEG PTS043 ServiceStatus - Values for Service Condition. Corresponds to TPEG Pti13 Service Condition values. + Values for Service Condition. Corresponds to TPEG PTS043 ServiceStatus - - - - 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. - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/xsd/siri_model/siri_situationReasons-v2.0.xsd b/xsd/siri_model/siri_situationReasons-v2.0.xsd index adfddca6..d6d2cbb9 100644 --- a/xsd/siri_model/siri_situationReasons-v2.0.xsd +++ b/xsd/siri_model/siri_situationReasons-v2.0.xsd @@ -1,4 +1,5 @@ + @@ -101,6 +102,7 @@ Rail transport, Roads and road transport Structured Classification Elements. Corresponds to TPEG 18 Event Reason. + @@ -136,6 +138,161 @@ Rail transport, Roads and road transport + + + TPEG PTS038: AlertCause. + + + + + Values for AlertCause. TPEG PTS038: AlertCause + + + + + TPEG Pti_19_0 unknown. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -1975,10 +2132,11 @@ Rail transport, Roads and road transport TPEG Pti22_2 rough sea. - - - TPEG Pti22_3 heavy snow fall. - + + + TPEG Pti22_3 heavy snow fall. + + drifting snow - Alias to TPEG Pti22_3 heavySnowFall. From 4c141f6ac8847b6f3fb7267ddcbbe379ff1158cb Mon Sep 17 00:00:00 2001 From: Adrian A Date: Mon, 14 Dec 2020 19:15:47 +0100 Subject: [PATCH 235/290] CR069: cosmetic changes and new examples from UmS VDV736 v1.0 --- .../luzern_example/SX_1010_first_message.xml | 254 ++ .../luzern_example/SX_1022_main_message.xml | 2311 +++++++++++++++++ .../SX_1135_main_message_update.xml | 2206 ++++++++++++++++ .../luzern_example/SX_1247_end_message.xml | 397 +++ .../exs_stopMonitoring_response_complex.xml | 18 +- .../exx_situationExchangeResponse.xml | 18 +- .../exx_situationExchange_ATOC.xml | 4 +- .../siri_exm_SX/exx_situationExchange_Pt.xml | 4 +- .../exx_situationExchange_response.xml | 8 +- .../exx_situationExchange_road.xml | 4 +- .../exd_allServices_capabilitiesResponse.xml | 7 +- 11 files changed, 5198 insertions(+), 33 deletions(-) create mode 100644 examples/luzern_example/SX_1010_first_message.xml create mode 100644 examples/luzern_example/SX_1022_main_message.xml create mode 100644 examples/luzern_example/SX_1135_main_message_update.xml create mode 100644 examples/luzern_example/SX_1247_end_message.xml diff --git a/examples/luzern_example/SX_1010_first_message.xml b/examples/luzern_example/SX_1010_first_message.xml new file mode 100644 index 00000000..d5780f43 --- /dev/null +++ b/examples/luzern_example/SX_1010_first_message.xml @@ -0,0 +1,254 @@ + + + + 2018-10-04T10:11:00+00:00 + ch:VBL +
      http:/server/siri/20_ums
      + t3xWB5cY3 + true + false + + 2018-10-04T10:11:00+00:00 + ch:VBL + 40599x2dsjmu8yjzy + + + 2017-05-28T10:10:00+02:00 + VBL + 5a7cf4f0-c7a5-11e8-813f-f38697968b53 + 1 + + feed + VBL + + published + + 2017-05-04T10:10:00+02:00 + 2017-05-28T17:10:00+02:00 + + fire + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + 3 + line + false + DE + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + + + ch:vbl:622 + Haldensteig + + + + + + disruption + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 24 + + + + + + + false + + + + + + + line + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 24 + + + ch:pb:PB073 + 73 + + + + + + + open + 0010 + 2017-05-28T10:10:00+02:00 + VBL + VBL + general + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Betroffen sind die Linien 6, 8, 24 und 73 + Affected lines are 6, 8, 24 and 73 + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + Es muss mit Verspätungen, Ausfällen und Umleitungen gerechnet werden. Wir werden sie rasch möglichst detaillierter informieren. + Expect delays, cancellations and diversions. More details to come soon. + + + + + + + line + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 24 + + + ch:pb:PB073 + 73 + + + + + + + open + 0010 + 2017-05-28T10:10:00+02:00 + VBL + VBL + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Betroffen sind die Linien 6, 8, 24 und 73 + Affected lines are 6, 8, 24 and 73 + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + Es muss mit Verspätungen, Ausfällen und Umleitungen gerechnet werden. Wir werden sie rasch möglichst detaillierter informieren. + Expect delays, cancellations and diversions. More details to come soon. + + + + + + + line + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 24 + + + ch:pb:PB073 + 73 + + + + + + + open + 0010 + 2017-05-28T10:10:00+02:00 + VBL + VBL + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Betroffen sind die Linien 6, 8, 24 und 73 + Affected lines are 6, 8, 24 and 73 + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + Es muss mit Verspätungen, Ausfällen und Umleitungen gerechnet werden. Wir werden sie rasch möglichst detaillierter informieren. + Expect delays, cancellations and diversions. More details to come soon. + + + + + + + + +       +       diff --git a/examples/luzern_example/SX_1022_main_message.xml b/examples/luzern_example/SX_1022_main_message.xml new file mode 100644 index 00000000..1afe09a5 --- /dev/null +++ b/examples/luzern_example/SX_1022_main_message.xml @@ -0,0 +1,2311 @@ + + + + 2018-10-16T10:22:30+00:00 + ch:VBL +
      http:/server/siri/20_ums
      + Pgfkw0GAsg + true + false + + 2018-10-16T10:22:30+00:00 + ch:VBL + 40599x2dsjmu8yjzy + + + 2017-05-28T10:22:00+02:00 + VBL + 5a7cf4f0-c7a5-11e8-813f-f38697968b53 + 2 + + feed + VBL + + published + + 2017-05-28T10:10:00+02:00 + 2017-05-28T17:10:00+02:00 + + fire + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + 3 + route + DE + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + http://www.vbl.ch/aktuelles/verkehrsmeldungen/stoerungen/20160603_13? + + + + + + + + ch:vbl:622 + Haldensteig + + + + + + disruption + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:2507::01 + Büttenhalde + + + ch:vbl:VBL006:A + Büttenhalde + + + + ch:vbl:621::01 + Casino-Palace + affectedStopplace + + + ch:vbl:615::01 + Europe + affectedStopplace + + + ch:vbl:616::01 + Dietschiberg + affectedStopplace + + + ch:vbl:617::01 + Verkehrshaus + affectedStopplace + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:601:01 + Matthof + + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:617::02 + Verkehrshaus + affectedStopplace + + + ch:vbl:616::02 + Dietschiberg + affectedStopplace + + + ch:vbl:615::02 + Europe + affectedStopplace + + + ch:vbl:621::02 + Casino-Palace + affectedStopplace + + + ch:vbl:622::02 + Haldensteig + affectedStopplace + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:620:01 + Würzenbach + + + ch:vbl:VBL008:A + Würzenbach + + + + ch:vbl:621::01 + Casino-Palace + affectedStopplace + + + ch:vbl:615::01 + Europe + affectedStopplace + + + ch:vbl:616::01 + Dietschiberg + affectedStopplace + + + ch:vbl:617::01 + Verkehrshaus + affectedStopplace + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:801:01 + Hirtenhof + + + ch:vbl:VBL008:B + Hirtenhof + + + + ch:vbl:617::02 + Verkehrshaus + affectedStopplace + + + ch:vbl:616::02 + Dietschiberg + affectedStopplace + + + ch:vbl:615::02 + Europe + affectedStopplace + + + ch:vbl:621::02 + Casino-Palace + affectedStopplace + + + ch:vbl:622::02 + Haldensteig + affectedStopplace + + + + + + + + true + true + + + + diverted + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:2433:01 + Tschädigen + + + ch:vbl:VBL024:A + Tschädigen + + + + ch:vbl:121::02 + affectedStopplace + + + ch:vbl:621::01 + Casino-Palace + affectedStopplace + + + ch:vbl:617::01 + Verkehrshaus + affectedStopplace + + + ch:vbl:715::01 + intermediate + + + ch:vbl:716::01 + intermediate + + + ch:vbl:1405::01 + intermediate + + + ch:vbl:1406::01 + intermediate + + + ch:vbl:1407::01 + intermediate + + + ch:vbl:1408::01 + intermediate + + + ch:vbl:1409::01 + intermediate + + + ch:vbl:1410::01 + intermediate + + + ch:vbl:1411::01 + intermediate + + + ch:vbl:1412::01 + intermediate + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:119:13 + Bahnhof + + + ch:vbl:VBL024:B + Bahnhof + + + + ch:vbl:617::02 + Verkehrshaus + affectedStopplace + + + ch:vbl:621::02 + affectedStopplace + + + ch:vbl:622::02 + affectedStopplace + + + ch:vbl:1412::02 + intermediate + + + ch:vbl:1411::02 + intermediate + + + ch:vbl:1410::02 + intermediate + + + ch:vbl:1409::02 + intermediate + + + ch:vbl:1408::02 + intermediate + + + ch:vbl:1407::02 + intermediate + + + ch:vbl:1406::02 + intermediate + + + ch:vbl:1405::02 + intermediate + + + ch:vbl:716::02 + intermediate + + + ch:vbl:715::01 + intermediate + + + + + + + + true + true + + + PT7M + + + + + + + line + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 24 + + + ch:pb:PB073 + 73 + + + + + + + open + 0020 + 2017-05-28T10:22:00+02:00 + 1 + vbl + general + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Betroffen sind die Linien 6,8, 24 und 73 + Affected lines are 6, 8, 24 and 73 + + + Linie 6 und 8 fallen zwischen Luzernerhof und Brüelstrasse aus. + Linie 24 wird zwischen Luzernerhof und Brüelstrasse via St. Anna umgeleitet. Ca. 7 Min. längere Fahrzeit. + Linie 73 wird zwischen Luzernerhof und Brüelstrasse via St. Anna umgeleitet. Ca. 6 Min. längere Fahrzeit. + Line 6 and 8 disrupted Luzernerhof and Brüelstrasse. + Line 24 diverted between Luzernerhof and Brüelstrasse via St. Anna. Approx. 7 min delay. + Line 73 diverted between Luzernerhof and Brüelstrasse via St. Anna. Approx. 6 min delay. + + + Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Zwischen Luzern, Bahnhof und Verkehrshaus benutzen sie die S3 oder das Schiff. + Umstiegsempfehlung für die Linien 6 und 8: Bei den Haltestellen Luzernerhof bzw. Brüelstrasse auf die umgeleiteten Linien 24 und 73, die normal verkehrende Linie 14 oder den Entlastungsbus umsteigen. + Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + Between Luzern, Bahnhof and Verkehrshaus use the S3 or ferry. + Transfer advice for line 6 and 8: At Luzernerhof or Brüelstrasse use diverted line 24, 73, additional buses or the regular line 14 services. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:A + Büttenenhalde + + + + ch:vbl:601::01 + Matthof + + + ch:vbl:602::01 + Schönbühl + + + ch:vbl:603::03 + Wartegg + + + ch:vbl:604::01 + Eisfeldstrasse + + + ch:vbl:605::01 + Weinbergli + + + ch:vbl:606::01 + Werkhofstrasse + + + ch:vbl:407::02 + Bundesplatz + + + ch:vbl:118::01 + Kantonalbank (C) + + + ch:vbl:119::02 + Bahnhof (B) + + + ch:vbl:120:01 + Schwanenplatz + + + + + + + + + open + 0030 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Linie 6 fällt zwischen Luzernerhof und Brüelstrasse aus. + Line 6 cancelled between Luzernerhof and Brüelstrasse. + + + Reisende nach Brüelstrasse und weiter benützen die umgeleitete Linie 24 und 73 (ohne Halte zwischen Wey und Brühlstrasse) oder die normal verkehrende Linie 14 (mit Halten) und steigen an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Travellers to Brüelstrasse or further use the diverted line 24, 73 (direct between Wey and Brühlstrasse) or the regular line 14 services (all stop) and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + + + open + 0040 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Linie 6 fällt zwischen Luzernerhof und Brüelstrasse aus. + Line 6 cancelled between Luzernerhof and Brüelstrasse. + + + Reisende nach Brüelstrasse und weiter benützen die umgeleitete Linie 24 und 73 (ohne Halte zwischen Wey und Brühlstrasse) oder die normal verkehrende Linie 14 (mit Halten) und steigen an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Travellers to Brüelstrasse or further use the diverted line 24, 73 (direct between Wey and Brühlstrasse) or the regular line 14 services (all stop) and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + Weitere Informationen erhalten Sie unter www.vbl.ch/stoerung/haldenstrasse + For further information, please visit www.vbl.ch/stoerung/haldenstrasse + + + www.vbl.ch/stoerung/haldenstrasse + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:A + Büttenenhalde + + + + ch:vbl:121::02 + Luzernerhof (D) + + + + + + + + + open + 0050 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Linie 6 wendet hier + Line 6 turns here + + + Reisende zur Brühlstrasse und weiter benützen die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte zwischen Wey und Brühlstrasse) oder die normale verkehrende Linie 14 (mit Halten) ab Kante F (Wey) und steigen an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Travellers to Brüelstrasse or further use the diverted line 24, 73, additonal buses (direct between Wey and Brühlstrasse) or the regular line 14 services (all stop) from platform F (Wey) and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:A + Büttenenhalde + + + + ch:vbl:121::01 + Luzernerhof (C) + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:A + Würzenbach + + + + ch:vbl:121::01 + Luzernerhof (C) + + + + + + + + + open + 0060 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8 + Line 6 and 8 disrupted + + + Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die umgeleiteten Linien 24 und 73, die normal verkehrende Linie 14 oder den Entlastungsbus ab Kante F (Wey) und steigen Sie an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Transfer advice line 6 and 8: Use diverted line 24, 73, the regular line 14 services or the additional buses to Brüelstrasse and transfer back to line 6 and 8. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + Weitere Informationen erhalten Sie beim Auskunftspersonal. + For further information, please contact staff. + + + + + + + route + + + + + + ch:vbl:VBL014 + 14 + + ch:vbl:VBL014:A + Brüelstrasse + + + + ch:vbl:715::02 + Wey + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:VBL024:A + Tschädingen + + + + ch:vbl:715::02 + Wey + + + + + ch:vbl:VBL073 + 73 + + + ch:vbl:715::02 + Wey + + + + + + + + + + open + 0070 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8; Umleitung der Linien 24 und 73 + Line 6 and 8 disrupted; Line 24 and 73 diverted + + + Benutzen Sie die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte bis Brühlstrasse) oder die normal verkehrende Linie 14 (mit Halten) bis Brüelstrasse. + Use the diverted line 24, 73, additional buses (direct to Brühlstrasse) or the regular line 14 services (all stops) to Brüelstrasse. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:A + Büttenenhalde + + + + ch:vbl:121::02 + Luzernerhof (D) + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:A + Würzenbach + + + + ch:vbl:121::02 + Luzernerhof (D) + + + + + + + + + open + 0130 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Linie 6 und 8 fallen bis Brüelstrasse aus. Linie 24 wird zwischen Luzernerhof und Brüelstrasse via St. Anna umgeleitet. Ca. 7 Min. längere Fahrzeit. Linie 73 wird zwischen Luzernerhof und Brüelstrasse via St. Anna umgeleitet. Ca. 6 Min. längere Fahrzeit. + Line 6 and 8 services cancelled to Brüelstrasse. Line 24 services diverted between Luzernerhof and Brüelstrasse via St. Anna. Approx. 7 min. delay. Line 73 services diverted between Luzernerhof and Brüelstrasse. Approx. 6 min delay. + + + Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte zwischen Wey und Brühlstrasse) oder die normale verkehrende Linie 14 (mit Halten) ab Kante F (Wey) und steigen Sie an der Brüelstrasse um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Transfer advice for line 6 and 8: To Brüelstrasse use diverted line 24, 73, additional buses (direct between Wey and Brühlstrasse) or the regular line 14 services (all stops) from platform F (Way) and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:A + Büttenenhalde + + + + ch:vbl:621::01 + Casino-Palace + + + ch:vbl:615::01 + Europe + + + ch:vbl:616::01 + Dietschiberg + + + ch:vbl:617::01 + Verkehrshaus + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:617::02 + Verkehrshaus + + + ch:vbl:616::02 + Dietschiberg + + + ch:vbl:615::02 + Europe + + + ch:vbl:621::02 + Casino-Palace + + + ch:vbl:622::01 + Haldensteig + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:A + Würzenbach + + + + ch:vbl:621::01 + Casino-Palace + + + ch:vbl:615::01 + Europe + + + ch:vbl:616::01 + Dietschiberg + + + ch:vbl:617::01 + Verkehrshaus + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:B + Hirtenhof + + + + ch:vbl:617::02 + Verkehrshaus + + + ch:vbl:616::02 + Dietschiberg + + + ch:vbl:615::02 + Europe + + + ch:vbl:621::02 + Casino-Palace + + + ch:vbl:622::01 + Haldensteig + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:VBL024:A + Tschädingen + + + + ch:vbl:621::01 + Casino-Palace + + + ch:vbl:615::01 + Europe + + + ch:vbl:616::01 + Dietschiberg + + + ch:vbl:617::01 + Verkehrshaus + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:VBL024:B + Bahnhof + + + + ch:vbl:617::02 + Verkehrshaus + + + ch:vbl:616::02 + Dietschiberg + + + ch:vbl:615::02 + Europe + + + ch:vbl:621::02 + Casino-Palace + + + ch:vbl:622::01 + Haldensteig + + + + + ch:pb:PB073 + 73 + + + ch:vbl:621::01 + Casino-Palace + + + ch:vbl:615::01 + Europe + + + ch:vbl:616::01 + Dietschiberg + + + ch:vbl:617::01 + Verkehrshaus + + + ch:vbl:617::02 + Verkehrshaus + + + ch:vbl:616::02 + Dietschiberg + + + ch:vbl:615::02 + Europe + + + ch:vbl:621::02 + Casino-Palace + + + ch:vbl:622::01 + Haldensteig + + + + + + + + + open + 0140 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Keine Bedienung der Linien 6, 8, 24 und 73 zwischen Luzernerhof und Brüelstrasse + No service for line 6, 8, 24 and 73 between Luzernerhof and Brüelstrasse + + + Reisende zwischen Luzernerhof und Brüelstrasse erreichen ihr Ziel nur zu Fuß. Ab Luzernerhof und Brüelstrasse verkehren die Linie auf den normalen Fahrwegen. + Travellers between Luzernerhof and Brüelstrasse can only reach their destination on foot. From Luzernerhof and Brüelstrasse lines will run on regular routes. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + Fällt aus + Cancelled + + + + + + + route + + + + + ch:vbl:014 + 14 + + ch:vbl:VBL014:A + Brüelstrasse + + + + ch:vbl:618::01 + Brüelstrasse + destination + + + + + + + + + open + 0080 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Einstieg der Linien 6 und 8 bei Kante C. Reisende nach Verkehrshaus und Dietschiberg erreichen ihr Ziel nur zu Fuß. + Board line 6 and 8 from platform C. Travellers to Verkehrshaus and Dietschiberg can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:024 + 24 + + ch:vbl:VBL024:A + Tschädingen + + + + ch:vbl:618::01 + Brüelstrasse + intermediate + + + + + ch:pb:073 + 73 + + ch:pb:PB073:A + Rotkreuz + + + + ch:vbl:618::04 + Brüelstrasse + destination + + + + + + + + + open + 0090 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Umleitung endet hier + Diversion ends here + + + Umstieg auf Linie 6 und 8: Einstieg bei Kante C. Reisende nach Verkehrshaus und Dietschiberg erreichen ihr Ziel nur zu Fuß. + Transfer to line 6 and 8: Board from platform C. Travellers to Verkehrshaus and Dietschiberg can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:A + Büttenhalde + + + + ch:vbl:618::03 + Brüelstrasse + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:A + Würzenbach + + + + ch:vbl:618::03 + Brüelstrasse + + + + + + + + + open + 0100 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Normale Bedienung der Linien 6 bis Büttenenhalde und 8 bis Würzenbach. + Regular line 6 services to Büttenenhalde and 8 to Würzenbach. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + Es muss mit Verspätungen gerechnet werden. + Expect delays. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:A + Büttenhalde + + + + + ch:vbl:618::03 + Brüelstrasse(B) + + + ch:vbl:2502::01 + Giseli + intermediate + + + ch:vbl:2503::01 + Oberseeburg + intermediate + + + ch:vbl:2504::01 + Oberseeburghöhe + intermediate + + + ch:vbl:2505::01 + Eggen + intermediate + + + ch:vbl:2506::01 + Büttenen + intermediate + + + ch:vbl:2507::01 + Büttenenhalde + destination + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:A + Würzenbach + + + + + ch:vbl:618::03 + Brüelstrasse(B) + + + ch:vbl:619::01 + Würzenbachmatte + intermediate + + + ch:vbl:620::01 + Würzenbach + destination + + + + + + + + + open + 0110 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + Es muss mit Verspätungen gerechnet werden. + Expect delays. + + + + + + + route + + + + + ch:vbl:Entlastungsbus + Entlastungsbus + + ch:vbl:VBL006:A + Büttenhalde + + + + ch:vbl:618::04 + Brüelstrasse + + + + + + + + + open + 0120 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Diese Fahrt endet hier + This service terminates here + + + Einstieg der Linien 6 und 8 bei Kante C. Reisende nach Verkehrshaus und Dietschiberg erreichen ihr Ziel nur zu Fuß. + Board line 6 and 8 from platform C. Travellers to Verkehrshaus and Dietschiberg can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:2507::01 + Büttenenhalde + origin + + + ch:vbl:2506::02 + Büttenen + intermediate + + + ch:vbl:2505::02 + Eggen + intermediate + + + ch:vbl:2504::02 + Oberseeburghöhe + intermediate + + + ch:vbl:2503::02 + Oberseeburg + intermediate + + + ch:vbl:2502::02 + Giseli + intermediate + + + + + + + + + open + 0150 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Linie 6 fällt zwischen Brüelstrasse und Luzernerhof aus. + Line 6 cancelled between Brüelstrasse and Luzernerhof. + + + Reisende nach Luzernerhof oder weiter benützen die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte zwischen Brühlstrasse und Luzernerhof) oder die normal verkehrende Linie 14 (mit Halten) bis Luzernerhof und steigen dort wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. + Travellers to Luzernerhof or further use the diverted lines 24, 73 and the additional bus (direct between Brühlstrasse and Luzernerhof) or the regular line 14 services (all stop) to Luzernhof and transfer there. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:2507::01 + Büttenenhalde + origin + + + ch:vbl:2506::02 + Büttenen + intermediate + + + ch:vbl:2505::02 + Eggen + intermediate + + + ch:vbl:2504::02 + Oberseeburghöhe + intermediate + + + ch:vbl:2503::02 + Oberseeburg + intermediate + + + ch:vbl:2502::02 + Giseli + intermediate + + + + + + + + + open + 0160 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Linie 6 fällt zwischen Brüelstrasse und Luzernerhof aus. + Line 6 cancelled between Brüelstrasse and Luzernerhof. + + + Reisende nach Luzernerhof oder weiter benützen die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte zwischen Brühlstrasse und Luzernerhof) oder die normal verkehrende Linie 14 (mit Halten) bis Luzernerhof und steigen dort wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. + Travellers to Luzernerhof or further use the diverted lines 24, 73 and the additional bus (direct between Brühlstrasse and Luzernerhof) or the regular line 14 services (all stop) to Luzernhof and transfer there. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:618::02 + Brüelstrasse + destination + + + + + + + + + open + 0170 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Linie 6 wendet hier + Line 6 turns here + + + Reisende zum Luzernerhof oder weiter benützen die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte bis Luzernerhof) oder die normal verkehrende Linie 14 (mit Halten) ab Kante D und steigen beim Luzernerhof wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. + Travellers to Luzernerhof or further use the diverted lines 24, 73, addintionl buses (direct to Luzernerhof) or the regular line 14 services (all stops) from platform D and transfer back to line 6 and 8 at Luzernerhof. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:618::02 + Brüelstrasse + destination + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:B + Hirtenhof + + + + ch:vbl:618::02 + Brüelstrasse + destination + + + + + + + + + open + 0180 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8 + Line 6 and 8 disrupted + + + Reisende zum Luzernerhof oder weiter benützen die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte bis Luzernerhof) oder die normal verkehrende Linie 14 (mit Halten) ab Kante D und steigen beim Luzernerhof wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. + Travellers to Luzernerhof or further use the diverted lines 24, 73, addintionl buses (direct to Luzernerhof) or the regular line 14 services (all stops) from platform D and transfer back to line 6 and 8 at Luzernerhof. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL014 + 14 + + ch:vbl:VBL014:A + Brühlstrasse + + + + ch:vbl:618::04 + Brühlstrasse + destination + + + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:VBL024:B + Bahnhof + + + + ch:vbl:618::04 + Brühlstrasse + destination + + + + + + + + + open + 0190 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8; Umleitung der Linien 24 und 73. + Line 6 and 8 disrupted; Line 24 and 73 diverted. + + + Benutzen Sie die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte bis Luzernerhof) oder die normal verkehrende Linie 14 (mit Halten) bis Luzernerhof. + Use diverted line 24, 73, additional buses (direct ot Luzernhof) or the regular line 14 services (all stops) to Luzernhof. + + + + + + + route + + + + + + ch:vbl:VBLEBUS + EBUS + + ch:vbl:VBLEBUS:B + Luzernerhof + + + + ch:vbl:121::xx + Luzernerhof + destination + + + + + + + + + open + 0200 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Umleitung endet hier + Diversion ends here + + + Einstieg der Linien 6 und 8 bei Kante A. Reisende nach Haldensteig, Casino-Palace und Europe erreichen ihr Ziel nur zu Fuß. + Board line 6 and 8 from platform A. Travellers to Haldensteig, Casino-Palace and Europe can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL014 + 14 + + ch:vbl:VBL014:B + Horw Zentrum + + + + ch:vbl:121::03 + Luzernerhof + intermediate + + + + + + + + + open + 0210 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Einstieg der Linien 6 und 8 bei Kante A. Reisende nach Haldensteig, Casino-Palace und Europe erreichen ihr Ziel nur zu Fuß. + Board line 6 and 8 from platform A. Travellers to Haldensteig, Casino-Palace and Europe can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:VBL024:B + Bahnhof + + + + ch:vbl:121::3 + Luzernerhof + origin + + + + + ch:vbl:VBL073 + 73 + + ch:vbl:VBL073:B + Bahnhof + + + + ch:vbl:121::3 + Luzernerhof + origin + + + + + + + + + open + 0215 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Umleitung endet hier + Diversion ends here + + + Einstieg der Linien 6 und 8 bei Kante A. Reisende nach Haldensteig, Casino-Palace und Europe erreichen ihr Ziel nur zu Fuß. + Board line 6 and 8 from platform A. Travellers to Haldensteig, Casino-Palace and Europe can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:VBL024:B + Bahnhof + + + + ch:vbl:121::3 + Luzernerhof + origin + + + + + + + + + open + 0220 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Umleitung endet hier + Diversion ends here + + + Umstieg auf die Linien 6 und 8: Einstieg bei Kante A. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Transfer to line 6 and 8: Board from platform A. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:121::04 + Luzernerhof + origin + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:B + Hirtenhof + + + + ch:vbl:121::04 + Luzernerhof + origin + + + + + + + + + open + 0230 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Normale Bedienung der Linien 6 bis Matthof und 8 bis Hirtenhof. + Regular service on line 6 to Matthof and line 8 to Hirtenhof. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + Es muss mit Verspätungen gerechnet werden. + Expect delays. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:120::02 + Schwanenplatz + intermediate + + + ch:vbl:119::01 + Bahnhof + intermediate + + + ch:vbl:118::02 + Kantonalbank + intermediate + + + ch:vbl:407::03 + Bundesplatz + intermediate + + + ch:vbl:606::02 + Werkhofstrasse + intermediate + + + ch:vbl:605::02 + Weinbergli + intermediate + + + ch:vbl:604::02 + Eisfeldstrasse + intermediate + + + ch:vbl:603::02 + Wartegg + intermediate + + + ch:vbl:602::02 + Schönbühl + intermediate + + + ch:vbl:601::01 + Matthof + destination + + + + + + + + + open + 0240 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Es muss mit Verspätungen gerechnet werden. + Expect delays. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + + + + + route + + + + + ch:vbl:VBL02A + 2 + + + ch:vbl:119::06 + Luzern Bahnhof + + + + + + + + + open + 0245 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8 + Line 6 and 8 disrupted + + + Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die umgeleitete Linie 73 oder die normal verkehrende Linie 14 und steigen Sie an der Brüelstrasse wieder um. Reisende nach dem Verkehrshaus benutzen die S3 oder das Schiff. + Transfer advice for line 6 and 8: Use diverted line 73 or the regular line 14 services to Brüelstrasse and transfer back to line 6 and 8. Travellers to Verkehrshaus use the S3 or ferry. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + + + + + route + + + + + ch:vbl:VBL014A + 14 + + ch:vbl:VBL014:A + Brüelstrasse + + + + ch:vbl:119::08 + Luzern Bahnhof + + + + + + + + + open + 0246 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8 + Line 6 and 8 disrupted + + + Empfehlung für Linien 6 und 8: Für Fahrten zur Brüelstrasse und weiter bleiben Sie in der Linie 14 und steigen Sie an der Brüelstrasse um. Reisende nach dem Verkehrshaus benutzen ab dem Bahnhof die S3 oder das Schiff. + Advice for line 6 and 8: For services to Brüelstrasse and further, stay on line 14 and transfer at Brüelstrasse. Travellers after Verkehrshaus use the S3 or ferry from main station. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + + + + + + +       +       diff --git a/examples/luzern_example/SX_1135_main_message_update.xml b/examples/luzern_example/SX_1135_main_message_update.xml new file mode 100644 index 00000000..1d8d64f6 --- /dev/null +++ b/examples/luzern_example/SX_1135_main_message_update.xml @@ -0,0 +1,2206 @@ + + + + 2018-10-16T10:22:30+00:00 + ch:VBL +
      http:/server/siri/20_ums
      + Pgfkw0GAsg + true + false + + 2018-10-16T10:22:30+00:00 + ch:VBL + 40599x2dsjmu8yjzy + + + 2017-05-28T09:42:00+02:00 + VBL + 5a7cf4f0-c7a5-11e8-813f-f38697968b53 + 2 + + feed + VBL + + published + + 2017-05-28T09:42:00+02:00 + 2017-05-28T17:10:00+02:00 + + fire + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + 3 + route + DE + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + http://www.vbl.ch/aktuelles/verkehrsmeldungen/stoerungen/20160603_13? + + + + + + + + ch:vbl:622 + Haldensteig + + + + + + disruption + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:2507::01 + Büttenhalde + + + ch:vbl:VBL006:A + Büttenhalde + + + + ch:vbl:621::01 + Casino-Palace + affectedStopplace + + + ch:vbl:615::01 + Europe + affectedStopplace + + + ch:vbl:616::01 + Dietschiberg + affectedStopplace + + + ch:vbl:617::01 + Verkehrshaus + affectedStopplace + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:601:01 + Matthof + + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:617::02 + Verkehrshaus + affectedStopplace + + + ch:vbl:616::02 + Dietschiberg + affectedStopplace + + + ch:vbl:615::02 + Europe + affectedStopplace + + + ch:vbl:621::02 + Casino-Palace + affectedStopplace + + + ch:vbl:622::02 + Haldensteig + affectedStopplace + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:620:01 + Würzenbach + + + ch:vbl:VBL008:A + Würzenbach + + + + ch:vbl:621::01 + Casino-Palace + affectedStopplace + + + ch:vbl:615::01 + Europe + affectedStopplace + + + ch:vbl:616::01 + Dietschiberg + affectedStopplace + + + ch:vbl:617::01 + Verkehrshaus + affectedStopplace + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:801:01 + Hirtenhof + + + ch:vbl:VBL008:B + Hirtenhof + + + + ch:vbl:617::02 + Verkehrshaus + affectedStopplace + + + ch:vbl:616::02 + Dietschiberg + affectedStopplace + + + ch:vbl:615::02 + Europe + affectedStopplace + + + ch:vbl:621::02 + Casino-Palace + affectedStopplace + + + ch:vbl:622::02 + Haldensteig + affectedStopplace + + + + + + + + true + true + + + + diverted + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:2433:01 + Tschädigen + + + ch:vbl:VBL024:A + Tschädigen + + + + ch:vbl:121::02 + affectedStopplace + + + ch:vbl:621::01 + Casino-Palace + affectedStopplace + + + ch:vbl:617::01 + Verkehrshaus + affectedStopplace + + + ch:vbl:715::01 + intermediate + + + ch:vbl:716::01 + intermediate + + + ch:vbl:1405::01 + intermediate + + + ch:vbl:1406::01 + intermediate + + + ch:vbl:1407::01 + intermediate + + + ch:vbl:1408::01 + intermediate + + + ch:vbl:1409::01 + intermediate + + + ch:vbl:1410::01 + intermediate + + + ch:vbl:1411::01 + intermediate + + + ch:vbl:1412::01 + intermediate + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:119:13 + Bahnhof + + + ch:vbl:VBL024:B + Bahnhof + + + + ch:vbl:617::02 + Verkehrshaus + affectedStopplace + + + ch:vbl:621::02 + affectedStopplace + + + ch:vbl:622::02 + affectedStopplace + + + ch:vbl:1412::02 + intermediate + + + ch:vbl:1411::02 + intermediate + + + ch:vbl:1410::02 + intermediate + + + ch:vbl:1409::02 + intermediate + + + ch:vbl:1408::02 + intermediate + + + ch:vbl:1407::02 + intermediate + + + ch:vbl:1406::02 + intermediate + + + ch:vbl:1405::02 + intermediate + + + ch:vbl:716::02 + intermediate + + + ch:vbl:715::01 + Wey Auch? + intermediate + + + + + + + + true + true + + + PT7M + + + + + + + line + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 24 + + + + + + + open + 0250 + 2017-05-28T09:42:00+02:00 + 1 + vbl + general + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Betroffen sind die Linien 6, 8 und 24 + Affected lines are 6, 8 and 24 + + + Linie 6 und 8 fallen zwischen Luzernerhof und Brüelstrasse aus. + Linie 24 wird zwischen Luzernerhof und Brüelstrasse via St. Anna umgeleitet. Ca. 7 Min. längere Fahrzeit. + Line 6 and 8 services cancelled between Luzernerhof and Brüelstrasse. + Line 24 divirted between Luzernerhof and Brüelstrasse via St. Anna. Approx. 7 min delay. + + + Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Zwischen Luzern, Bahnhof und Verkehrshaus benutzen sie die S3 oder das Schiff. + Umstiegsempfehlung für die Linien 6 und 8: Bei den Haltestellen Luzernerhof bzw. Brüelstrasse auf die umgeleitete Linie 24, die normal verkehrenden Linien 14 und 73 oder den Entlastungsbus umsteigen. + Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + Between Luzern, Bahnhof and Verkehrshaus use the S3 or ferry. + Transfer advice for line 6 and 8: At Luzernerhof or Brüelstrasse use diverted line 24, 73, additional buses or the regular line 14 services. + + + Die Störung dauert bis ca.12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:A + Büttenenhalde + + + + ch:vbl:601::01 + Matthof + + + ch:vbl:602::01 + Schönbühl + + + ch:vbl:603::03 + Wartegg + + + ch:vbl:604::01 + Eisfeldstrasse + + + ch:vbl:605::01 + Weinbergli + + + ch:vbl:606::01 + Werkhofstrasse + + + ch:vbl:407::02 + Bundesplatz + + + ch:vbl:118::01 + Kantonalbank (C) + + + ch:vbl:119::02 + Bahnhof (B) + + + ch:vbl:120::01 + Schwanenplatz + + + + + + + + + open + 0260 + 2017-05-28T09:42:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Linie 6 fällt zwischen Luzernerhof und Brüelstrasse aus. + Line 6 cancelled between Luzernerhof and Brüelstrasse. + + + Reisende nach Brüelstrasse und weiter benützen die umgeleitete Linie 24 (ohne Halte zwischen Wey und Brüelstrasse) oder die normal verkehrenden Linien 14 und 73 und steigen an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Travellers to Brüelstrasse or further use the diverted line 24 (direct between Wey and Brühlstrasse) or the regular line 14 or 73 services and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + Die Störung dauert bis ca.12:30 Uhr. + Disruption duration until 12:30pm. + + + + + open + 0270 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Linie 6 fällt zwischen Luzernerhof und Brüelstrasse aus. + Line 6 cancelled between Luzernerhof and Brüelstrasse. + + + Reisende nach Brüelstrasse und weiter benützen die umgeleitete Linie 24 (ohne Halte zwischen Wey und Brüelstrasse) oder die normal verkehrenden Linien 14 und 73 und steigen an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Travellers to Brüelstrasse or further use the diverted line 24 (direct between Wey and Brühlstrasse) or the regular services of line 14 or 73 and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + Die Störung dauert bis ca.12:30 Uhr. + Disruption duration until 12:30pm. + + + Weitere Informationen erhalten Sie unter www.vbl.ch/stoerung/haldenstrasse + For further information, please visit www.vbl.ch/stoerung/haldenstrasse + + + www.vbl.ch/stoerung/haldenstrasse + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:121::02 + Luzernerhof (B) + + + + + + + + + open + 0280 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Linie 6 wendet hier + Line 6 turns here + + + Reisende zur Brüelstrasse und weiter benützen die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte zwischen Wey und Brüelstrasse) oder die normale verkehrende Linie 14 (mit Halten) ab Kante F (Wey) oder die Linie 73 ab Kante D und steigen an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Travellers to Brüelstrasse or further use the diverted line 24, additonal buses (direct between Wey and Brüelstrasse), the regular services of line 14 (all stops) from platform F (Way) or line 73 from platform D and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:121::01 + Luzernerhof (C) + + + ch:vbl:121::02 + Luzernerhof (D) + + + + + ch:vbl:VBL008 + 8 + + + ch:vbl:121::01 + Luzernerhof (C) + + + ch:vbl:121::02 + Luzernerhof (D) + + + + + + + + + open + 0290 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8 + Line 6 and 8 disrupted + + + Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die umgeleitete Linie 24, die normal verkehrende Linie 14 und den Entlastungsbus ab Kante F (Wey) oder die Linie 73 ab Kante D und steigen Sie an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Transfer advice line 6 and 8: To Brüelstrasse use diverted line 24, the regular line 14 services or the additional buses from platform F (Wey) or line 73 from platform D and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + Die Störung dauert bis ca.12:30 Uhr. + Disruption duration until 12:30pm. + + + Weitere Informationen erhalten Sie beim Auskunftspersonal. + For further information, please contact staff. + + + + + + + route + + + + + ch:vbl:Entlastungsbusse + + + ch:vbl:715::01 + Wey + + + + + ch:vbl:VBL014 + 14 + + + ch:vbl:715::01 + Wey + + + + + ch:vbl:VBL24 + 24 + + + ch:vbl:715::01 + Wey + + + + + + + + + open + 0300 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8; Umleitung der Linien 24. + Line 6 and 8 disrupted; Line 24 diverted. + + + Benutzen Sie die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte bis Brüelstrasse) oder die normal verkehrenden Linie 14 (mit Halten) und 73 bis Brüelstrasse. + Use diverted line 24, additional buses (direct to Brüelstrasse), regular services of line 14 (all stops) or 73 to Brüelstrasse. + + + Die Störung dauert bis ca.12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:VBL006 + 06 + + ch:vbl:VBL006:A + Büttenenhalde + + + + ch:vbl:121::02 + Luzernerhof (D) + + + + + ch:vbl:VBL008 + 08 + + ch:vbl:VBL008:A + Würzenbach + + + + ch:vbl:121::02 + Luzernerhof (D) + + + + + + + + + open + 0370 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Linie 6 und 8 fallen bis Brüelstrasse aus. Linie 24 wird zwischen Luzernerhof und Brüel via St. Anna umgeleitet. Ca. 7 Min. längere Fahrzeit. Linie 73 verkehrt wieder normal. + Line 6 and 8 cancelled services to Brüelstrasse. Line 24 services diverted between Luzernerhof and Brüel via St. Anna. Approx. 7 min delay. Line 73 back to regular service. + + + Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte zwischen Wey und Brüelstrasse) oder die normale verkehrende Linie 14 (mit Halten) ab Kante F (Wey) oder die Linie 73 ab Kante D und steigen Sie an der Brüelstrasse um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Transfer advice for line 6 and 8: Use diverted line 73, additonal buses (direct between Wey and Brüelstrasse), the regular line 14 services (all stops) from platform F (Wey) or line 73 from platform D and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + Die Störung dauert bis ca.12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:A + Büttenenhalde + + + + ch:vbl:621::01 + Casino-Palace + + + ch:vbl:615::01 + Europe + + + ch:vbl:616::01 + Dietschiberg + + + ch:vbl:617::01 + Verkehrshaus + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:A + Würzenbach + + + + ch:vbl:621::01 + Casino-Palace + + + ch:vbl:615::01 + Europe + + + ch:vbl:616::01 + Dietschiberg + + + ch:vbl:617::01 + Verkehrshaus + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:VBL024:A + Tschädingen + + + + ch:vbl:621::01 + Casino-Palace + + + ch:vbl:615::01 + Europe + + + ch:vbl:616::01 + Dietschiberg + + + ch:vbl:617::01 + Verkehrshaus + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:617::02 + Verkehrshaus + + + ch:vbl:616::02 + Dietschiberg + + + ch:vbl:615::02 + Europe + + + ch:vbl:621::02 + Casino-Palace + + + ch:vbl:622::01 + Haldensteig + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:B + Hirtenhof + + + + ch:vbl:617::02 + Verkehrshaus + + + ch:vbl:616::02 + Dietschiberg + + + ch:vbl:615::02 + Europe + + + ch:vbl:621::02 + Casino-Palace + + + ch:vbl:622::01 + Haldensteig + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:VBL024:B + Bahnhof + + + + ch:vbl:617::02 + Verkehrshaus + + + ch:vbl:616::02 + Dietschiberg + + + ch:vbl:615::02 + Europe + + + ch:vbl:621::02 + Casino-Palace + + + ch:vbl:622::01 + Haldensteig + + + + + + + + + open + 0380 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Keine Bedienung der Linien 6, 8 und 24 zwischen Luzernerhof und Brüelstrasse + Line 6, 8 and 24 no service between Luzernerhof and Brüelstrasse + + + Reisende zwischen Luzernerhof und Brüelstrasse erreichen ihr Ziel nur zu Fuß. Ab Luzernerhof und Brüelstrasse verkehren die Linie auf den normalen Fahrwegen. + Travellers between Luzernerhof and Brüelstrasse can only reach their destination on foot. From Luzernerhof and Brüelstrasse lines will run on regular routes. + + + Die Störung dauert bis ca.12:30 Uhr. + Disruption duration until 12:30pm. + + + Fällt aus + Cancelled + + + + + + + route + + + + + ch:vbl:014 + 14 + + ch:vbl:VBL014:A + Brüelstrasse + + + + ch:vbl:618::01 + Brüelstrasse + destination + + + + + + + + + open + 0310 + 2017-05-28T09:42:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Fahrt endet hier + Service terminates here + + + Einstieg der Linien 6 und 8 bei Kante C. Reisende nach Verkehrshaus und Dietschiberg erreichen ihr Ziel nur zu Fuß. + Board line 6 and 8 from platform C. Travellers to Verkehrshaus and Dietschiberg can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:024 + 24 + + ch:vbl:VBL014:A + Brüelstrasse + + + + ch:vbl:618::04 + Brüelstrasse + destination + + + + + + + + + open + 0320 + 2017-05-28T09:42:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Umleitung endet hier + Diversion ends here + + + Umstieg auf Linie 6 und 8: Einstieg bei Kante C. Reisende nach Verkehrshaus und Dietschiberg erreichen ihr Ziel nur zu Fuß. + Transfer to line 6 and 8: Board from platform C. Travellers to Verkehrshaus and Dietschiberg can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL006 + 06 + + ch:vbl:VBL006:A + Büttenenhalde + + + + ch:vbl:618::03 + Brüelstrasse + + + + + ch:vbl:VBL008 + 08 + + ch:vbl:VBL008:A + Würzenbach + + + + ch:vbl:618::03 + Brüelstrasse + + + + + + + + + open + 0330 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Normale Bedienung der Linien 6 bis Büttenenhalde und 8 bis Würzenbach. Es muss mit Verspätungen gerechnet werden. + Regular service on line 6 to Büttenenhalde and 8 to Würzenbach. Expect delays. + + + Die Störung dauert bis ca.12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:A + Büttenhalde + + + + ch:vbl:2502::01 + Giseli + + + ch:vbl:2503::01 + Oberseeburg + intermediate + + + ch:vbl:2504::01 + Oberseeburghöhe + intermediate + + + ch:vbl:2505::01 + Eggen + intermediate + + + ch:vbl:2506::01 + Büttenen + intermediate + + + ch:vbl:2507::01 + Büttenenhalde + destination + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:A + Würzenbach + + + + ch:vbl:619::01 + Würzenbachmatte + intermediate + + + ch:vbl:620::01 + Würzenbach + destination + + + + + + + + + open + 0340 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Es muss mit Verspätungen gerechnet werden. + Expect delays. + + + Die Störung dauert bis ca. 12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:Entlastungsbus + Entlastungsbus + + ch:vbl:VBL006:A + Büttenhalde + + + + ch:vbl:618::04 + Brüelstrasse + + + + + + + + + open + 0350 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Diese Fahrt endet hier + This service terminates here + + + Einstieg der Linien 6 und 8 bei Kante C. Reisende nach Verkehrshaus und Dietschiberg erreichen ihr Ziel nur zu Fuß. + Board line 6 and 8 from platform C. Travellers to Verkehrshaus and Dietschiberg can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:2507::01 + Büttenenhalde + origin + + + ch:vbl:2506::02 + Büttenen + intermediate + + + ch:vbl:2505::02 + Eggen + intermediate + + + ch:vbl:2504::02 + Oberseeburghöhe + intermediate + + + ch:vbl:2503::02 + Oberseeburg + intermediate + + + ch:vbl:2502::02 + Giseli + intermediate + + + + + + + + + open + 0390 + 2017-05-28T09:42:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Linie 6 fällt zwischen Brüelstrasse und Luzernerhof aus. + Line 6 cancelled between Brüelstrasse and Luzernerhof. + + + Reisende nach Luzernerhof oder weiter benützen die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte zwischen Brüelstrasse und Luzernerhof) oder die normal verkehrenden Linien 14 (mit Halten) und 73 bis Luzernerhof und steigen dort wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. + Travellers to Luzernerhof or further use the diverted line 24, additional buses (direct between Brühlstrasse and Luzernerhof), the regular line 14 services (all stop) or line 73 to Luzernhof and transfer there. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. + + + Die Störung dauert bis ca. 12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:2507::01 + Büttenenhalde + origin + + + ch:vbl:2506::02 + Büttenen + intermediate + + + ch:vbl:2505::02 + Eggen + intermediate + + + ch:vbl:2504::02 + Oberseeburghöhe + intermediate + + + ch:vbl:2503::02 + Oberseeburg + intermediate + + + ch:vbl:2502::02 + Giseli + intermediate + + + + + + + + + open + 0400 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Linie 6 fällt zwischen Brüelstrasse und Luzernerhof aus. + Line 6 cancelled between Brüelstrasse and Luzernerhof. + + + Reisende nach Luzernerhof oder weiter benützen die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte zwischen Brüelstrasse und Luzernerhof) oder die normal verkehrenden Linien 14 (mit Halten) und 73 bis Luzernerhof und steigen dort wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. + Travellers to Luzernerhof or further use the diverted line 24, the additional buses (direct between Brühlstrasse and Luzernerhof), the regular line 14 services (all stop) or line 73 to Luzernhof and transfer there. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. + + + Die Störung dauert bis ca. 12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:618::02 + Brüelstrasse + + + + + + + + + open + 0410 + 2017-05-28T09:42:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Linie 6 wendet hier + Line 6 turns here + + + Reisende zum Luzernerhof oder weiter benützen die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte bis Luzernerhof) oder die normal verkehrende Linie 14 (mit Halten) oder 73 ab Kante D und steigen beim Luzernerhof wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. + Travellers to Luzernerhof or further use the diverted line 24, addintional buses (direct to Luzernerhof), the regular line 14 services (all stops) or line 73 from platform D and transfer back to Luzernerhof. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:618::02 + Brüelstrasse + + + + + + + + + open + 0420 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8 + Line 6 and 8 disrupted + + + Reisende zum Luzernerhof oder weiter benützen die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte bis Luzernerhof) ab Kante D oder die normal verkehrenden Linien 14 (mit Halten) ab Kante D und 73 ab Kante C und steigen beim Luzernerhof wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. + Travellers to Luzernerhof or further use the diverted line 24, addintional buses (direct to Luzernerhof) from platform D, the regular line 14 services (all stops) from platform D or line 73 from platform C and transfer back to Luzernerhof. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. + + + Die Störung dauert bis ca. 12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:Entlastungsbus + Entlastungsbus + + ch:vbl:VBL006:A + Büttenhalde + + + + ch:vbl:VBL014 + 14 + + ch:vbl:VBL014:A + Brühlstrasse + + + + ch:vbl:618::01 + Brühlstrasse + destination + + + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:VBL024:B + Bahnhof + + + + ch:vbl:618::01 + Brühlstrasse + destination + + + + + + + + + open + 0430 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8; Umleitung der Linien 24. + Line 6 and 8 disrupted; Line 24 diverted. + + + Benutzen Sie die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte bis Luzernerhof) oder die normal verkehrenden Linien 14 (mit Halten) und 73 bis Luzernerhof. + Use diverted line 24 and additional buses (direct to Luzernerhof) or the regular line 14 (all stops) and line 73 to Luzernerhof. + + + Die Störung dauert bis ca. 12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:Entlastungsbus + Entlastungsbus + + ch:vbl:VBL006:A + Büttenhalde + + + + ch:vbl:121::03 + Luzernerhof + + + + + + + + + open + 0440 + 2017-05-28T09:42:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Diese Fahrt endet hier + This service terminates here + + + Einstieg der Linien 6 und 8 bei Kante A. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Board line 6 and 8 from platform A. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + Die Störung dauert bis ca. 12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:VBL024:B + Bahnhof + + + + ch:vbl:121::04 + Luzernerhof + origin + + + + + + + + + open + 0450 + 2017-05-28T09:42:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Umleitung endet hier + Diversion ends here + + + Umstieg auf Linie 6 und 8: Einstieg bei Kante A. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Transfer to line 6 and 8: Board from platform A. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL014 + 14 + + ch:vbl:VBL014:B + Horw Zentrum + + + + ch:vbl:121::03 + Luzernerhof + intermediate + + + + + + + + + open + 0455 + 2017-05-28T09:42:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + + + Umstieg auf Linie 6 und 8: Einstieg bei Kante A. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + + + + + + + route + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:VBL024:B + Bahnhof + + + + ch:vbl:121::03 + Luzernerhof + origin + + + + + + + + + open + 0460 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Umleitung endet hier + Diversion ends here + + + Umstieg auf die Linien 6 und 8: Einstieg bei Kante A. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Transfer to line 6 and 8: Board from platform A. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:121::04 + Luzernerhof + origin + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:B + Hiertenhof + + + + ch:vbl:121::04 + Luzernerhof + origin + + + + + + + + + open + 0470 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Normale Bedienung der Linien 6 bis Matthof und 8 bis Hirtenhof. Es muss mit Verspätungen gerechnet werden. + Regular service on line 6 to Matthof and line 8 to Hirtenhof. Expect delays. + + + Die Störung dauert bis ca. 12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:120::02 + Schwanenplatz + intermediate + + + ch:vbl:119::01 + Bahnhof + intermediate + + + ch:vbl:118::02 + Kantonalbank + intermediate + + + ch:vbl:407::03 + Bundesplatz + intermediate + + + ch:vbl:606::02 + Werkhofstrasse + intermediate + + + ch:vbl:605::02 + Weinbergli + intermediate + + + ch:vbl:604::02 + Eisfeldstrasse + intermediate + + + ch:vbl:603::02 + Wartegg + intermediate + + + ch:vbl:602::02 + Schönbühl + intermediate + + + ch:vbl:601::01 + Matthof + destination + + + + + + + + + open + 0480 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Es muss mit Verspätungen gerechnet werden. + Expect delays. + + + Die Störung dauert bis ca. 12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + line + + + + + ch:vbl:VBL002 + 2 + + + ch:vbl:VBL002:A + Bahnhof + + + + ch:vbl:119::06 + Bahnhof + destination + + + + + + + + + open + 0481 + 2017-05-28T09:42:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8 + Line 6 and 8 disrupted + + + Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die Linien 14 oder 73 und steigen Sie an der Brüelstrasse wieder um. Reisende nach dem Verkehrshaus benutzen die S3 oder das Schiff. + Transfer advice line 6 and 8: Use line 14 or 73 to Brüelstrasse and transfer back to line 6 and 8. Travellers to Verkehrshaus use the S3 or ferry. + + + Die Störung dauert bis ca. 12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:VBL014 + 14 + + ch:vbl:VBL014:A + Brüelstrasse + + + + ch:vbl:119::08 + Bahnhof + intermediate + + + + + + + + + open + 0482 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8 + Line 6 and 8 disrupted + + + Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die Linien 14 oder 73 und steigen Sie an der Brüelstrasse wieder um. Reisende nach dem Verkehrshaus benutzen die S3 oder das Schiff. + Transfer advice line 6 and 8: Use line 14 or 73 to Brüelstrasse and transfer back to line 6 and 8. Travellers to Verkehrshaus use the S3 or ferry. + + + Die Störung dauert bis ca. 12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + + +       +       diff --git a/examples/luzern_example/SX_1247_end_message.xml b/examples/luzern_example/SX_1247_end_message.xml new file mode 100644 index 00000000..fea32f98 --- /dev/null +++ b/examples/luzern_example/SX_1247_end_message.xml @@ -0,0 +1,397 @@ + + + + 2018-10-04T12:22:00+00:00 + ch:VBL +
      http:/server/siri/20_ums
      + JFI2d2mWP + true + false + + 2018-10-04T12:22:00+00:00 + ch:VBL + 40599x2dsjmu8yjzy + + + 2017-05-28T12:22:00+02:00 + VBL + 1 + 5 + + feed + VBL + + closing + + + 2017-05-28T12:22:00+02:00 + 2017-05-28T17:10:00+02:00 + + fire + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + 3 + line + false + DE + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line interruption between Luzernerhof and Verkehrshaus + + + + ch:vbl:622 + Haldensteig + + + + + + disturbanceRectified + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 24 + + + + + + false + + + + + + + line + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 14 + + + ch:vbl:VBL024 + 24 + + + ch:vbl:VBL024 + 73 + + + + + + + open + 0510 + 2017-05-28T12:22:00+02:00 + 1 + vbl + VBL + general + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line interruption between Luzernerhof and Verkehrshaus + + + Der Streckenunterbruch zwischen Luzernerhof und Brüelstrasse ist behoben. + The route disruption between Luzernerhof and Brüelstrasse is resolved. + + + Die Linien 6, 8, 24 und 73 verkehren wieder gemäß Fahrplan. + Line 6, 8, 24 and 73 are back to regular service. + + + + + + + line + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 14 + + + ch:vbl:VBL024 + 24 + + + ch:vbl:VBL024 + 73 + + + + + + + open + 0510 + 2017-05-28T12:22:00+02:00 + 1 + vbl + VBL + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line interruption between Luzernerhof and Verkehrshaus + + + Der Streckenunterbruch zwischen Luzernerhof und Brüelstrasse ist behoben. + The route disruption between Luzernerhof and Brüelstrasse is resolved. + + + Die Linien 6, 8, 24 und 73 verkehren wieder gemäß Fahrplan. + Line 6, 8, 24 and 73 are back to regular service. + + + + + + + line + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 14 + + + ch:vbl:VBL024 + 24 + + + ch:vbl:VBL024 + 73 + + + + + + + open + 0510 + 2017-05-28T12:22:00+02:00 + 1 + vbl + VBL + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line interruption between Luzernerhof and Verkehrshaus + + + Der Streckenunterbruch zwischen Luzernerhof und Brüelstrasse ist behoben. + The route disruption between Luzernerhof and Brüelstrasse is resolved. + + + Die Linien 6, 8, 24 und 73 verkehren wieder gemäß Fahrplan. + Line 6, 8, 24 and 73 are back to regular service. + + + + + + + line + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 24 + + + + + + + open + + 2017-05-28T12:47:00+02:00 + 2017-05-28T13:15:00+02:00 + + 0510 + 2017-05-28T12:47:00+02:00 + 1 + vbl + VBL + general + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line interruption between Luzernerhof and Verkehrshaus + + + Der Streckenunterbruch zwischen Luzernerhof und Brüelstrasse ist behoben. + The route disruption between Luzernerhof and Brüelstrasse is resolved. + + + Die Linien 6, 8, 24 und 73 verkehren wieder gemäß Fahrplan. + Line 6, 8, 24 and 73 are back to regular service. + + + + + + + line + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 24 + + + + + + + open + + 2017-05-28T12:47:00+02:00 + 2017-05-28T13:15:00+02:00 + + 0510 + 2017-05-28T12:47:00+02:00 + 1 + vbl + VBL + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line interruption between Luzernerhof and Verkehrshaus + + + Der Streckenunterbruch zwischen Luzernerhof und Brüelstrasse ist behoben. + The route disruption between Luzernerhof and Brüelstrasse is resolved. + + + Die Linien 6, 8, 24 und 73 verkehren wieder gemäß Fahrplan. + Line 6, 8, 24 and 73 are back to regular service. + + + + + + + line + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 24 + + + + + + + open + + 2017-05-28T12:47:00+02:00 + 2017-05-28T13:15:00+02:00 + + 0510 + 2017-05-28T12:47:00+02:00 + 1 + vbl + VBL + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line interruption between Luzernerhof and Verkehrshaus + + + Der Streckenunterbruch zwischen Luzernerhof und Brüelstrasse ist behoben. + The route disruption between Luzernerhof and Brüelstrasse is resolved. + + + Die Linien 6, 8, 24 und 73 verkehren wieder gemäß Fahrplan. + Line 6, 8, 24 and 73 are back to regular service. + + + + + + + + +       +       diff --git a/examples/siri_exm_SM/exs_stopMonitoring_response_complex.xml b/examples/siri_exm_SM/exs_stopMonitoring_response_complex.xml index d3a54f8f..4b48f27c 100644 --- a/examples/siri_exm_SM/exs_stopMonitoring_response_complex.xml +++ b/examples/siri_exm_SM/exs_stopMonitoring_response_complex.xml @@ -24,8 +24,8 @@ 2004-12-17T09:30:47-05:00 PT3M HLTST011 - British Museum Stop A - Musee Britannique Halte A + British Museum Stop A + Musee Britannique Halte A 2004-12-17T09:25:46-05:00 @@ -58,8 +58,8 @@ Roman Road PLACE45 - Paradise Park - Parc du Paradis + Paradise Park + Parc du Paradis Boris Special Kensall Green @@ -95,8 +95,8 @@ HLT0010 2 - Town Hall - Hotel de Ville + Town Hall + Hotel de Ville false 2004-12-17T09:32:43-05:00 2004-12-17T09:32:43-05:00 @@ -125,8 +125,8 @@ HLTST012 4 - Church - Eglise + Church + Eglise false 2004-12-17T09:30:56-05:00 2004-12-17T09:30:56-05:00 @@ -267,7 +267,7 @@ 2004-12-17T09:55:47-05:00 onTime - Approaching stop + Approaching stop 2 PT10M PT11M diff --git a/examples/siri_exm_SX/exx_situationExchangeResponse.xml b/examples/siri_exm_SX/exx_situationExchangeResponse.xml index f7dafe95..158e6d80 100644 --- a/examples/siri_exm_SX/exx_situationExchangeResponse.xml +++ b/examples/siri_exm_SX/exx_situationExchangeResponse.xml @@ -40,7 +40,7 @@ severe public point - Bomb at Barchester station + Bomb at Barchester station Building evacuated. AVoid station untile furtehr notice @@ -75,8 +75,8 @@ 2001-12-17T09:30:47.0Z - pti13_0 - pti26_0 + unknown + unknown true true @@ -134,7 +134,7 @@ severe public point - Jam on the access road to Barchester Station + Jam on the access road to Barchester Station Grislock and panic @@ -169,7 +169,7 @@ 2001-12-17T09:30:47.0Z - delayed + delay severe @@ -202,8 +202,8 @@ SRA - Vägverket - Swedish Road Administration + Vägverket + Swedish Road Administration roadAuthorities @@ -224,8 +224,8 @@ - Detta är en svensk olycka - This is a swedish accident + Detta är en svensk olycka + This is a swedish accident diff --git a/examples/siri_exm_SX/exx_situationExchange_ATOC.xml b/examples/siri_exm_SX/exx_situationExchange_ATOC.xml index dbd63c82..0f1a7208 100644 --- a/examples/siri_exm_SX/exx_situationExchange_ATOC.xml +++ b/examples/siri_exm_SX/exx_situationExchange_ATOC.xml @@ -29,7 +29,7 @@ severe public point - Bomb at Barchester station + Bomb at Barchester station Building evacuated. AVoid station untile furtehr notice @@ -64,7 +64,7 @@ 2001-12-17T09:30:47.0Z - delayed + delay severe true diff --git a/examples/siri_exm_SX/exx_situationExchange_Pt.xml b/examples/siri_exm_SX/exx_situationExchange_Pt.xml index dbd63c82..0f1a7208 100644 --- a/examples/siri_exm_SX/exx_situationExchange_Pt.xml +++ b/examples/siri_exm_SX/exx_situationExchange_Pt.xml @@ -29,7 +29,7 @@ severe public point - Bomb at Barchester station + Bomb at Barchester station Building evacuated. AVoid station untile furtehr notice @@ -64,7 +64,7 @@ 2001-12-17T09:30:47.0Z - delayed + delay severe true diff --git a/examples/siri_exm_SX/exx_situationExchange_response.xml b/examples/siri_exm_SX/exx_situationExchange_response.xml index add226ce..f97a8ccc 100644 --- a/examples/siri_exm_SX/exx_situationExchange_response.xml +++ b/examples/siri_exm_SX/exx_situationExchange_response.xml @@ -40,7 +40,7 @@ severe public point - Bomb at Barchester station + Bomb at Barchester station Building evacuated. AVoid station untile further notice @@ -75,7 +75,7 @@ 2001-12-17T09:30:47.0Z - pti13_0 + unknown pti26_0 true @@ -134,7 +134,7 @@ severe public point - Jam on the access road to Barchester Station + Jam on the access road to Barchester Station Grislock and panic @@ -169,7 +169,7 @@ 2001-12-17T09:30:47.0Z - delayed + delay severe diff --git a/examples/siri_exm_SX/exx_situationExchange_road.xml b/examples/siri_exm_SX/exx_situationExchange_road.xml index f48c5b6f..81ce32e8 100644 --- a/examples/siri_exm_SX/exx_situationExchange_road.xml +++ b/examples/siri_exm_SX/exx_situationExchange_road.xml @@ -29,7 +29,7 @@ severe public point - Jam on the access road to Barchester Station + Jam on the access road to Barchester Station Grislock and panic @@ -64,7 +64,7 @@ 2001-12-17T09:30:47.0Z - delayed + delay severe diff --git a/examples/siri_exu_capability/exd_allServices_capabilitiesResponse.xml b/examples/siri_exu_capability/exd_allServices_capabilitiesResponse.xml index 6cf1027c..74143dac 100644 --- a/examples/siri_exu_capability/exd_allServices_capabilitiesResponse.xml +++ b/examples/siri_exu_capability/exd_allServices_capabilitiesResponse.xml @@ -476,7 +476,7 @@ en WGS84 - true + true true @@ -487,10 +487,7 @@ false false - - true - true - + From 14ce43f72759034c6609409cedc4f35929ac9491 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 15 Dec 2020 10:42:34 +0100 Subject: [PATCH 236/290] correction according to ../pull/62#discussion_r526009390 --- xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd index d0a1aca4..14dbc10a 100644 --- a/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd @@ -202,7 +202,7 @@ Rail transport, Roads and road transport Whether the engine of the vehicle is on. Default is 'true' (+SIRI 2.0)       - + Delay of VEHICLE against schedule, to a precision in seconds. Early times are shown as negative values. From 71d874684426327180546a9668157be814155a10 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 15 Dec 2020 10:44:20 +0100 Subject: [PATCH 237/290] correction according to ../pull/62#discussion_r526022692 --- xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index 831d0e96..3909f846 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -403,12 +403,12 @@ the original journey and the nature of the difference. - This ESTIMATED CALL is an addition to the respective journey in the production timetable or to the previously sent prediction. If omitted: CALL is planned. + This CALL is an addition to the respective journey in the production timetable or to the previously sent prediction. If omitted: CALL is planned. - This ESTIMATED CALL is a cancellation of a previously announced call. + This CALL is a cancellation of a previously announced call. From 91e1055974b821c59f6535d9bc4efbee465188fd Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 15 Dec 2020 11:05:42 +0100 Subject: [PATCH 238/290] fix annotation of PredictionInaccurate --- xsd/siri_model/siri_journey-v2.0.xsd | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index ec239101..4873e343 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -766,8 +766,7 @@ To avoid this, the producer should transmit xxxPredictionUnknown instead of any - Whether the prediction for a stop or the whole journey is considered to be of useful accuracy or not. Default is 'false'. - Whether the prediction for the specific stop is considered to be of a useful accuracy or not. Default is 'false', i.e. prediction is considered to be accurate. + Whether the prediction for a specific stop or the whole journey is considered to be of a useful accuracy or not. Default is 'false', i.e. prediction is considered to be accurate. If prediction is degraded, e.g. because of a situation, PredictionInaccurate is used to indicate a lowered quality of data. Inherited property. PredictionInaccurate can be used in combination with InCongestion, but is more general. From 70f86f3f2876e430e30f67cc9122538308babafe Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 15 Dec 2020 11:09:24 +0100 Subject: [PATCH 239/290] merge clean-up: fix corrupted tags in Occupancy --- xsd/siri_model/siri_journey-v2.0.xsd | 2 ++ 1 file changed, 2 insertions(+) diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index f6ebc773..5c09deb8 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -908,6 +908,8 @@ If prediction is degraded, e.g. because of a situation, PredictionInaccurate is An approximate figure of how occupied the journey is after departing from a given stop, e.g. 'manySeatsAvailable' or 'standingRoomOnly'. If omitted: Passenger load is unknown. Occupancies and capacities for individual VEHICLEs, e.g. parts of a COMPOUND TRAIN, can also be specified in more detail for the departure on CALL level. + + From fe357b67271a9010cf602b9c40e7586f267da282 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 15 Dec 2020 12:02:27 +0100 Subject: [PATCH 240/290] CR073: alignment with CR002 / new vehicle formation model --- xsd/siri_model/siri_facility-v2.0.xsd | 51 +++++++------------- xsd/siri_model/siri_journey_support-v2.0.xsd | 1 + 2 files changed, 19 insertions(+), 33 deletions(-) diff --git a/xsd/siri_model/siri_facility-v2.0.xsd b/xsd/siri_model/siri_facility-v2.0.xsd index 69884d08..60ba6f75 100644 --- a/xsd/siri_model/siri_facility-v2.0.xsd +++ b/xsd/siri_model/siri_facility-v2.0.xsd @@ -721,37 +721,22 @@ Rail transport, Roads and road transport - - - - Classification of Vehicle Energy type. See Transmodel TypeOfFuel - - - - - Values for Vehicle fuel type. +SIRI v2.1 - - - - - An arbitrary vehicle fuel classification. +SIRI v2.1 - - - - - - - Values for Vehicle fuel type. Use of "other" requires the additional open ended VehicleFuelTypeOther to be filled - - - - - - - - - - - - + + + + Classification of vehicle energy type. See Transmodel TypeOfFuel. +SIRI v2.1 + + + + + Values for vehicle fuel type. Use of 'other' requires the additional open ended VehicleFuelTypeOther to be filled. + + + + + An arbitrary vehicle fuel classification. + + + +       diff --git a/xsd/siri_model/siri_journey_support-v2.0.xsd b/xsd/siri_model/siri_journey_support-v2.0.xsd index 4b9c7eff..c0b02d4e 100644 --- a/xsd/siri_model/siri_journey_support-v2.0.xsd +++ b/xsd/siri_model/siri_journey_support-v2.0.xsd @@ -910,6 +910,7 @@ The first class carriage of a TRAIN might, for example, be assigned to sector "A + From 7e9e8b1e19189f453d6a91b25053ea7926e0eba2 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 13 Jan 2021 19:14:52 +0100 Subject: [PATCH 241/290] clean-up: remove auto-generated comments --- xsd/siri.xsd | 1 - xsd/siri/siri_common_services-v2.0.xsd | 1 - xsd/siri/siri_request_errorConditions-v2.0.xsd | 1 - xsd/siriSg.xsd | 1 - xsd/siri_connectionMonitoring_service.xsd | 1 - xsd/siri_discovery.xsd | 1 - xsd/siri_estimatedTimetable_service.xsd | 1 - xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd | 1 - xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd | 5 ++--- xsd/siri_model/siri_journey-v2.0.xsd | 1 - xsd/siri_model/siri_situation-v2.0.xsd | 2 -- xsd/siri_situationExchange_service.xsd | 1 - xsd/siri_stopMonitoring_service.xsd | 1 - xsd/siri_utility/siri_utility-v1.1.xsd | 1 - xsd/siri_wsConsumer-Document.wsdl | 2 -- xsd/siri_wsConsumer-WSDL2.wsdl | 2 -- xsd/siri_wsConsumer.wsdl | 2 -- xsd/siri_wsProducer-Document.wsdl | 2 -- xsd/siri_wsProducer-WSDL2.wsdl | 2 -- xsd/siri_wsProducer.wsdl | 2 -- xsd/wsdl_model/siri_wsConsumer-Framework.xsd | 2 -- xsd/wsdl_model/siri_wsConsumer-Services.xsd | 2 -- xsd/wsdl_model/siri_wsProducer-DiscoveryCapability.xsd | 1 - xsd/wsdl_model/siri_wsProducer-Framework.xsd | 1 - xsd/wsdl_model/siri_wsProducer-Services.xsd | 1 - xsd/zrescue/siri_estimatedVehicleJourney-v2.0.xsd | 1 - 26 files changed, 2 insertions(+), 37 deletions(-) diff --git a/xsd/siri.xsd b/xsd/siri.xsd index 610a705f..3127359b 100644 --- a/xsd/siri.xsd +++ b/xsd/siri.xsd @@ -1,5 +1,4 @@ - diff --git a/xsd/siri/siri_common_services-v2.0.xsd b/xsd/siri/siri_common_services-v2.0.xsd index bf0bd548..70ca77c5 100644 --- a/xsd/siri/siri_common_services-v2.0.xsd +++ b/xsd/siri/siri_common_services-v2.0.xsd @@ -1,5 +1,4 @@ - diff --git a/xsd/siri/siri_request_errorConditions-v2.0.xsd b/xsd/siri/siri_request_errorConditions-v2.0.xsd index 06ae5a5d..49b36d73 100644 --- a/xsd/siri/siri_request_errorConditions-v2.0.xsd +++ b/xsd/siri/siri_request_errorConditions-v2.0.xsd @@ -1,5 +1,4 @@ - diff --git a/xsd/siriSg.xsd b/xsd/siriSg.xsd index 5063795e..43bbd915 100644 --- a/xsd/siriSg.xsd +++ b/xsd/siriSg.xsd @@ -1,5 +1,4 @@ - diff --git a/xsd/siri_connectionMonitoring_service.xsd b/xsd/siri_connectionMonitoring_service.xsd index 572bc51e..0778db11 100644 --- a/xsd/siri_connectionMonitoring_service.xsd +++ b/xsd/siri_connectionMonitoring_service.xsd @@ -1,5 +1,4 @@ - diff --git a/xsd/siri_discovery.xsd b/xsd/siri_discovery.xsd index 4e53f271..68617ae3 100644 --- a/xsd/siri_discovery.xsd +++ b/xsd/siri_discovery.xsd @@ -1,5 +1,4 @@ - diff --git a/xsd/siri_estimatedTimetable_service.xsd b/xsd/siri_estimatedTimetable_service.xsd index 22d7ca87..d7e07ec2 100644 --- a/xsd/siri_estimatedTimetable_service.xsd +++ b/xsd/siri_estimatedTimetable_service.xsd @@ -1,5 +1,4 @@ - diff --git a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd index f0b4f821..031efc96 100644 --- a/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_datedVehicleJourney-v2.0.xsd @@ -1,5 +1,4 @@ - diff --git a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd index ce2d84ee..69a3c6c7 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney-v2.0.xsd @@ -1,5 +1,4 @@ - @@ -107,7 +106,7 @@ Rail transport, Roads and road transport Reference to a dated VEHICLE JOURNEY. This will be 'framed' ie be with the data context of the ESTIMATED Timetable. -DEPRECATED from SRI 2.0 +DEPRECATED since SIRI v2.0 @@ -119,7 +118,7 @@ DEPRECATED from SRI 2.0 If this is the first message about an extra unplanned VEHICLE JOURNEY, a new and unique code must be given for it. ExtraJourney should be set to 'true'. -DEPRECATED from SRI 2.0 +DEPRECATED since SIRI v2.0 diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index b95675a7..c5846fbc 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -1,5 +1,4 @@ - diff --git a/xsd/siri_model/siri_situation-v2.0.xsd b/xsd/siri_model/siri_situation-v2.0.xsd index d9cea90f..1948fc69 100644 --- a/xsd/siri_model/siri_situation-v2.0.xsd +++ b/xsd/siri_model/siri_situation-v2.0.xsd @@ -1,6 +1,4 @@ - - diff --git a/xsd/siri_stopMonitoring_service.xsd b/xsd/siri_stopMonitoring_service.xsd index 1bdd2709..df455389 100644 --- a/xsd/siri_stopMonitoring_service.xsd +++ b/xsd/siri_stopMonitoring_service.xsd @@ -1,5 +1,4 @@ - diff --git a/xsd/siri_utility/siri_utility-v1.1.xsd b/xsd/siri_utility/siri_utility-v1.1.xsd index aa4bf7a6..9037677c 100644 --- a/xsd/siri_utility/siri_utility-v1.1.xsd +++ b/xsd/siri_utility/siri_utility-v1.1.xsd @@ -1,5 +1,4 @@ - diff --git a/xsd/siri_wsConsumer-Document.wsdl b/xsd/siri_wsConsumer-Document.wsdl index f99b320d..18cb2341 100644 --- a/xsd/siri_wsConsumer-Document.wsdl +++ b/xsd/siri_wsConsumer-Document.wsdl @@ -1,6 +1,4 @@ - - diff --git a/xsd/siri_wsConsumer-WSDL2.wsdl b/xsd/siri_wsConsumer-WSDL2.wsdl index 1cc114d0..fa40fdb1 100644 --- a/xsd/siri_wsConsumer-WSDL2.wsdl +++ b/xsd/siri_wsConsumer-WSDL2.wsdl @@ -1,6 +1,4 @@ - - - diff --git a/xsd/siri_wsProducer-Document.wsdl b/xsd/siri_wsProducer-Document.wsdl index 208e1e79..d8a7f145 100644 --- a/xsd/siri_wsProducer-Document.wsdl +++ b/xsd/siri_wsProducer-Document.wsdl @@ -1,6 +1,4 @@ - - diff --git a/xsd/siri_wsProducer-WSDL2.wsdl b/xsd/siri_wsProducer-WSDL2.wsdl index fa628092..b98e75fb 100644 --- a/xsd/siri_wsProducer-WSDL2.wsdl +++ b/xsd/siri_wsProducer-WSDL2.wsdl @@ -1,6 +1,4 @@ - - - diff --git a/xsd/wsdl_model/siri_wsConsumer-Framework.xsd b/xsd/wsdl_model/siri_wsConsumer-Framework.xsd index aa970cb0..3091e637 100644 --- a/xsd/wsdl_model/siri_wsConsumer-Framework.xsd +++ b/xsd/wsdl_model/siri_wsConsumer-Framework.xsd @@ -1,6 +1,4 @@ - - diff --git a/xsd/wsdl_model/siri_wsConsumer-Services.xsd b/xsd/wsdl_model/siri_wsConsumer-Services.xsd index 5ddc7c1f..3f41cfca 100644 --- a/xsd/wsdl_model/siri_wsConsumer-Services.xsd +++ b/xsd/wsdl_model/siri_wsConsumer-Services.xsd @@ -1,6 +1,4 @@ - - diff --git a/xsd/wsdl_model/siri_wsProducer-DiscoveryCapability.xsd b/xsd/wsdl_model/siri_wsProducer-DiscoveryCapability.xsd index 0554aa03..49064c03 100644 --- a/xsd/wsdl_model/siri_wsProducer-DiscoveryCapability.xsd +++ b/xsd/wsdl_model/siri_wsProducer-DiscoveryCapability.xsd @@ -1,5 +1,4 @@ - diff --git a/xsd/wsdl_model/siri_wsProducer-Framework.xsd b/xsd/wsdl_model/siri_wsProducer-Framework.xsd index 1aa41d7b..fc1af5bf 100644 --- a/xsd/wsdl_model/siri_wsProducer-Framework.xsd +++ b/xsd/wsdl_model/siri_wsProducer-Framework.xsd @@ -1,5 +1,4 @@ - diff --git a/xsd/wsdl_model/siri_wsProducer-Services.xsd b/xsd/wsdl_model/siri_wsProducer-Services.xsd index f3b2fd9d..3ac703c4 100644 --- a/xsd/wsdl_model/siri_wsProducer-Services.xsd +++ b/xsd/wsdl_model/siri_wsProducer-Services.xsd @@ -1,5 +1,4 @@ - diff --git a/xsd/zrescue/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/zrescue/siri_estimatedVehicleJourney-v2.0.xsd index c0c677fe..dea8bb87 100644 --- a/xsd/zrescue/siri_estimatedVehicleJourney-v2.0.xsd +++ b/xsd/zrescue/siri_estimatedVehicleJourney-v2.0.xsd @@ -1,5 +1,4 @@ - From 1fa6465ae71a89e1f54e30a1f199f14516f444dc Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 13 Jan 2021 19:17:26 +0100 Subject: [PATCH 242/290] clean-up: merge with enum updates from CR015 --- .../siri_situationClassifiers-v1.1.xsd | 267 +++- xsd/siri_model/siri_situationReasons-v2.0.xsd | 1279 +++++++++++++++-- .../siri_situationServiceTypes-v1.0.xsd | 180 ++- 3 files changed, 1516 insertions(+), 210 deletions(-) diff --git a/xsd/siri_model/siri_situationClassifiers-v1.1.xsd b/xsd/siri_model/siri_situationClassifiers-v1.1.xsd index 369c3443..0eec71ec 100644 --- a/xsd/siri_model/siri_situationClassifiers-v1.1.xsd +++ b/xsd/siri_model/siri_situationClassifiers-v1.1.xsd @@ -1,5 +1,4 @@ - @@ -130,38 +129,244 @@ Rail transport, Roads and road transport - Values for Service Condition. Corresponds to TPEG PTS043 ServiceStatus + Values for TPEG Pts43 ServiceStatus, with additional values from Pti013 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + TPEG Pts43_0, unknown + + + + + TPEG Pts43_1, delay + + + + + TPEG Pts43_2, minor delays + + + + + TPEG Pts43_3, major delays + + + + + TPEG Pts43_4, operation time extension + + + + + TPEG Pts43_5, on time + + + + + TPEG Pts43_6, disturbance rectified + + + + + TPEG Pts43_7, change of platform + + + + + TPEG Pts43_8, line cancellation + + + + + TPEG Pts43_9, trip cancellation + + + + + TPEG Pts43_10, boarding + + + + + TPEG Pts43_11, go to gate + + + + + TPEG Pts43_12, stop cancelled + + + + + TPEG Pts43_13, stop moved + + + + + TPEG Pts43_14, stop on demand + + + + + TPEG Pts43_15, additional stop + + + + + TPEG Pts43_16, substituted stop + + + + + TPEG Pts43_17, diverted + + + + + TPEG Pts43_18, disruption + + + + + TPEG Pts43_19, limited operation + + + + + TPEG Pts43_20, discontinued operation + + + + + TPEG Pts43_21, irregular traffic + + + + + TPEG Pts43_22, wagon order changed + + + + + TPEG Pts43_23, train shortened + + + + + TPEG Pts43_24, additional ride + + + + + TPEG Pts43_25, replacement ride + + + + + TPEG Pts43_26, temporarily non-stopping + + + + + TPEG Pts43_27, temporary stopplace + + + + + TPEG Pts43_255, undefined status + + + + + TPEG Pti13_1, deprecated (SIRI 2.1) + + + + + TPEG Pti13_2, deprecated (SIRI 2.1) + + + + + TPEG Pti13_3, deprecated (SIRI 2.1) + + + + + TPEG Pti13_5, deprecated (SIRI 2.1) + + + + + TPEG Pti13_6, deprecated (SIRI 2.1) + + + + + TPEG Pti13_7, deprecated (SIRI 2.1) + + + + + TPEG Pti13_8, deprecated (SIRI 2.1) + + + + + TPEG Pti13_10, deprecated (SIRI 2.1) + + + + + TPEG Pti13_11, deprecated (SIRI 2.1) + + + + + TPEG Pti13_12, deprecated (SIRI 2.1) + + + + + TPEG Pti13_13, deprecated (SIRI 2.1) + + + + + TPEG Pti13_14, deprecated (SIRI 2.1) + + + + + TPEG Pti13_15, deprecated (SIRI 2.1) + + + + + TPEG Pti13_16, deprecated (SIRI 2.1) + + + + + TPEG Pti13_17, deprecated (SIRI 2.1) + + + + + TPEG Pti13_18, deprecated (SIRI 2.1) + + + + + TPEG Pti13_19, deprecated (SIRI 2.1) + + + + + TPEG Pti13_255, deprecated (SIRI 2.1) + + diff --git a/xsd/siri_model/siri_situationReasons-v2.0.xsd b/xsd/siri_model/siri_situationReasons-v2.0.xsd index d6d2cbb9..2e30ca9b 100644 --- a/xsd/siri_model/siri_situationReasons-v2.0.xsd +++ b/xsd/siri_model/siri_situationReasons-v2.0.xsd @@ -1,5 +1,4 @@ - @@ -145,152 +144,1150 @@ Rail transport, Roads and road transport       - Values for AlertCause. TPEG PTS038: AlertCause + Values for TPEG Pts38 - AlertCause, plus additional values from TPEG Pti19/20/21/22 - TPEG Pti_19_0 unknown. + TPEG Pts38_0, unknown + + + + + TPEG Pts38_1, security alert + + + + + TPEG Pts38_2, emergency services call + + + + + TPEG Pts38_3, police activity + + + + + TPEG Pts38_4, police order + + + + + TPEG Pts38_5, fire + + + + + TPEG Pts38_6, cable fire + + + + + TPEG Pts38_7, smoke detected on vehicle + + + + + TPEG Pts38_8, fire at the station + + + + + TPEG Pts38_9, fire run + + + + + TPEG Pts38_10, fire brigade order + + + + + TPEG Pts38_11, explosion + + + + + TPEG Pts38_12, explosion hazard + + + + + TPEG Pts38_13, bomb disposal + + + + + TPEG Pts38_14, emergency medical services + + + + + TPEG Pts38_15, emergency brake + + + + + TPEG Pts38_16, vandalism + + + + + TPEG Pts38_17, cable theft + + + + + TPEG Pts38_18, signal passed at danger + + + + + TPEG Pts38_19, station overrun + + + + + TPEG Pts38_20, passengers blocking doors + + + + + TPEG Pts38_21, defective security system + + + + + TPEG Pts38_22, overcrowded + + + + + TPEG Pts38_23, border control + + + + + TPEG Pts38_24, unattended bag + + + + + TPEG Pts38_25, telephoned threat + + + + + TPEG Pts38_26, suspect vehicle + + + + + TPEG Pts38_27, evacuation + + + + + TPEG Pts38_28, terrorist incident + + + + + TPEG Pts38_29, public disturbance + + + + + TPEG Pts38_30, technical problem + + + + + TPEG Pts38_31, vehicle failure + + + + + TPEG Pts38_32, service disruption + + + + + TPEG Pts38_33, door failure + + + + + TPEG Pts38_34, lighting failure + + + + + TPEG Pts38_35, points problem + + + + + TPEG Pts38_36, points failure + + + + + TPEG Pts38_37, signal problem + + + + + TPEG Pts38_38, signal failure + + + + + TPEG Pts38_39, overhead wire failure + + + + + TPEG Pts38_40, level crossing failure + + + + + TPEG Pts38_41, traffic management system failure + + + + + TPEG Pts38_42, engine failure + + + + + TPEG Pts38_43, break down + + + + + TPEG Pts38_44, repair work + + + + + TPEG Pts38_45, construction work + + + + + TPEG Pts38_46, maintenance work + + + + + TPEG Pts38_47, power problem + + + + + TPEG Pts38_48, track circuit + + + + + TPEG Pts38_49, swing bridge failure + + + + + TPEG Pts38_50, escalator failure + + + + + TPEG Pts38_51, lift failure + + + + + TPEG Pts38_52, gangway problem + + + + + TPEG Pts38_53, defective vehicle + + + + + TPEG Pts38_54, broken rail + + + + + TPEG Pts38_55, poor rail conditions + + + + + TPEG Pts38_56, de-icing work + + + + + TPEG Pts38_57, wheel problem + + + + + TPEG Pts38_58, route blockage + + + + + TPEG Pts38_59, congestion + + + + + TPEG Pts38_60, heavy traffic + + + + + TPEG Pts38_61, route diversion + + + + + TPEG Pts38_62, roadworks + + + + + TPEG Pts38_63, unscheduled construction work + + + + + TPEG Pts38_64, level crossing incident + + + + + TPEG Pts38_65, sewerageMaintenance + + + + + TPEG Pts38_66, road closed + + + + + TPEG Pts38_67, roadway damage + + + + + TPEG Pts38_68, bridge damage + + + + + TPEG Pts38_69, person on the line + + + + + TPEG Pts38_70, object on the line + + + + + TPEG Pts38_71, vehicle on the line + + + + + TPEG Pts38_72, animal on the line + + + + + TPEG Pts38_73, fallen tree on the line + + + + + TPEG Pts38_74, vegetation + + + + + TPEG Pts38_75, speed restrictions + + + + + TPEG Pts38_76, preceding vehicle + + + + + TPEG Pts38_77, accident + + + + + TPEG Pts38_78, near miss + + + + + TPEG Pts38_79, person hit by vehicle + + + + + TPEG Pts38_80, vehicle struck object + + + + + TPEG Pts38_81, vehicle struck animal + + + + + TPEG Pts38_82, derailment + + + + + TPEG Pts38_83, collision + + + + + TPEG Pts38_84, level crossing accident + + + + + TPEG Pts38_85, poor weather + + + + + TPEG Pts38_86, fog + + + + + TPEG Pts38_87, heavy snowfall + + + + + TPEG Pts38_88, heavy rain + + + + + TPEG Pts38_89, strong winds + + + + + TPEG Pts38_90, ice + + + + + TPEG Pts38_91, hail + + + + + TPEG Pts38_92, high temperatures + + + + + TPEG Pts38_93, flooding + + + + + TPEG Pts38_94, low water level + + + + + TPEG Pts38_95, risk of flooding + + + + + TPEG Pts38_96, high water level + + + + + TPEG Pts38_97, fallen leaves + + + + + TPEG Pts38_98, fallen tree + + + + + TPEG Pts38_99, landslide + + + + + TPEG Pts38_100, risk of landslide + + + + + TPEG Pts38_101, drifting snow + + + + + TPEG Pts38_102, blizzard conditions + + + + + TPEG Pts38_103, storm damage + + + + + TPEG Pts38_104, lightning strike + + + + + TPEG Pts38_105, rough sea + + + + + TPEG Pts38_106, high tide + + + + + TPEG Pts38_107, low tide + + + + + TPEG Pts38_108, ice drift + + + + + TPEG Pts38_109, avalanches + + + + + TPEG Pts38_110, risk of avalanches + + + + + TPEG Pts38_111, flash floods + + + + + TPEG Pts38_112, mudslide + + + + + TPEG Pts38_113, rockfalls + + + + + TPEG Pts38_114, subsidence + + + + + TPEG Pts38_115, earthquake damage + + + + + TPEG Pts38_116, grass fire + + + + + TPEG Pts38_117, wildland fire + + + + + TPEG Pts38_118, ice on railway + + + + + TPEG Pts38_119, ice on carriages + + + + + TPEG Pts38_120, special event + + + + + TPEG Pts38_121, procession + + + + + TPEG Pts38_122, demonstration + + + + + TPEG Pts38_123, industrial action + + + + + TPEG Pts38_124, staff sickness + + + + + TPEG Pts38_125, staff absence + + + + + TPEG Pts38_126, operator ceased trading + + + + + TPEG Pts38_127, previous disturbances + + + + + TPEG Pts38_128, vehicle blocking track + + + + + TPEG Pts38_129, foreign disturbances + + + + + TPEG Pts38_130, awaiting shuttle + + + + + TPEG Pts38_131, change in carriages + + + + + TPEG Pts38_132, train coupling + + + + + TPEG Pts38_133, boarding delay + + + + + TPEG Pts38_134, awaiting approach + + + + + TPEG Pts38_135, overtaking + + + + + TPEG Pts38_136, provision delay + + + + + TPEG Pts38_137, miscellaneous + + + + + TPEG Pts38_255, undefined alert cause + + + + + TPEG Pti19_1, deprecated (SIRI 2.1) + + + + + TPEG Pti19_1_2, deprecated (SIRI 2.1) + + + + + TPEG Pti19_1_5, deprecated (SIRI 2.1) - replaced by Pts38_33, door failure + + + + + TPEG Pti19_1_7, deprecated (SIRI 2.1) + + + + + TPEG Pti19_1_8, deprecated (SIRI 2.1) + + + + + TPEG Pti19_1_12, deprecated (SIRI 2.1) - replaced by Pts38_32, service disruption + + + + + TPEG Pti19_2, deprecated (SIRI 2.1) + + + + + TPEG Pti19_3_2, deprecated (SIRI 2.1) + + + + + TPEG Pti19_3_6, deprecated (SIRI 2.1) + + + + + TPEG Pti19_3_7, deprecated (SIRI 2.1) + + + + + TPEG Pti19_3_8, deprecated (SIRI 2.1) + + + + + TPEG Pti19_3_9, deprecated (SIRI 2.1) + + + + + TPEG Pti19_3_10, deprecated (SIRI 2.1) + + + + + TPEG Pti19_3_13, deprecated (SIRI 2.1) + + + + + TPEG Pti19_3_16, deprecated (SIRI 2.1) + + + + + TPEG Pti19_4_1, deprecated (SIRI 2.1) + + + + + TPEG Pti19_5_1, deprecated (SIRI 2.1) + + + + + TPEG Pti19_5_2, deprecated (SIRI 2.1) + + + + + TPEG Pti19_5_3, deprecated (SIRI 2.1) + + + + + TPEG Pti19_5_4, deprecated (SIRI 2.1) + + + + + TPEG Pti19_5_5, deprecated (SIRI 2.1) + + + + + TPEG Pti19_6_1, deprecated (SIRI 2.1) + + + + + TPEG Pti19_6_2, deprecated (SIRI 2.1) + + + + + TPEG Pti19_6_3, deprecated (SIRI 2.1) - replaced by Pts38_79, person hit by vehicle + + + + + TPEG Pti19_6_4, deprecated (SIRI 2.1) + + + + + TPEG Pti19_6_5, deprecated (SIRI 2.1) - replaced by Pts38_14, emergency medical services + + + + + TPEG Pti19_8, deprecated (SIRI 2.1) + + + + + TPEG Pti19_10, deprecated (SIRI 2.1) + + + + + TPEG Pti19_11, deprecated (SIRI 2.1) + + + + + TPEG Pti19_14, deprecated (SIRI 2.1) + + + + + TPEG Pti19_15_1, deprecated (SIRI 2.1) - replaced by Pts38_23, border control + + + + + TPEG Pti19_15_2, deprecated (SIRI 2.1) + + + + + TPEG Pti19_18_1, deprecated (SIRI 2.1) - replaced by Pts38_64, level crossing blocked + + + + + TPEG Pti19_19_3, deprecated (SIRI 2.1) - replaced by Pts38_81, vehicle struck animal + + + + + TPEG Pti19_19_4, deprecated (SIRI 2.1) - replaced by Pts38_80, vehicle struck object + + + + + TPEG Pti19_23_2, deprecated (SIRI 2.1) + + + + + TPEG Pti19_23_3, deprecated (SIRI 2.1) + + + + + TPEG Pti19_23_4, deprecated (SIRI 2.1) + + + + + TPEG Pti19_24_1, deprecated (SIRI 2.1) + + + + + TPEG Pti19_24_5, deprecated (SIRI 2.1) + + + + + TPEG Pti19_24_6, deprecated (SIRI 2.1) + + + + + TPEG Pti19_24_7, deprecated (SIRI 2.1) + + + + + TPEG Pti19_25, deprecated (SIRI 2.1) - replaced by Pts38_68, bridge damage + + + + + TPEG Pti19_25_1, deprecated (SIRI 2.1) + + + + + TPEG Pti19_26, deprecated (SIRI 2.1) + + + + + TPEG Pti19_255, deprecated (SIRI 2.1) + + + + + TPEG Pti19_255_1, deprecated (SIRI 2.1) + + + + + TPEG Pti19_255_2, deprecated (SIRI 2.1) + + + + + TPEG Pti19_255, deprecated (SIRI 2.1) - replaced by Pts38_255, undefined alert cause + + + + + TPEG Pti20_1_1, deprecated (SIRI 2.1) + + + + + TPEG Pti20_1_2, deprecated (SIRI 2.1) + + + + + TPEG Pti20_3, deprecated (SIRI 2.1) + + + + + TPEG Pti20_4, deprecated (SIRI 2.1) + + + + + TPEG Pti20_5_1, deprecated (SIRI 2.1) + + + + + TPEG Pti20_6, deprecated (SIRI 2.1) + + + + + TPEG Pti20_255, deprecated (SIRI 2.1) - replaced by Pts38_255, undefined alert cause + + + + + TPEG Pti21_3_1, deprecated (SIRI 2.1) + + + + + TPEG Pti21_4_1, deprecated (SIRI 2.1) + + + + + TPEG Pti21_6_1, deprecated (SIRI 2.1) + + + + + TPEG Pti21_6_2, deprecated (SIRI 2.1) - replaced by Pts38_53, defective vehicle + + + + + TPEG Pti21_8_3, deprecated (SIRI 2.1) + + + + + TPEG Pti21_8_4, deprecated (SIRI 2.1) + + + + + TPEG Pti21_8_5, deprecated (SIRI 2.1) + + + + + TPEG Pti21_8_6, deprecated (SIRI 2.1) + + + + + TPEG Pti21_8_7, deprecated (SIRI 2.1) + + + + + TPEG Pti21_8_8, deprecated (SIRI 2.1) + + + + + TPEG Pti21_8_9, deprecated (SIRI 2.1) + + + + + TPEG Pti21_11_1, deprecated (SIRI 2.1) + + + + + TPEG Pti21_11_2, deprecated (SIRI 2.1) + + + + + TPEG Pti21_13, deprecated (SIRI 2.1) + + + + + TPEG Pti21_18, deprecated (SIRI 2.1) + + + + + TPEG Pti21_19, deprecated (SIRI 2.1) + + + + + TPEG Pti21_21_1, deprecated (SIRI 2.1) + + + + + TPEG Pti21_22, deprecated (SIRI 2.1) + + + + + TPEG Pti21_255, deprecated (SIRI 2.1) - replaced by Pts38_255, undefined alert cause + + + + + TPEG Pti22_5_1, deprecated (SIRI 2.1) + + + + + TPEG Pti22_6, deprecated (SIRI 2.1) + + + + + TPEG Pti22_9_1, deprecated (SIRI 2.1) + + + + + TPEG Pti22_9_3, deprecated (SIRI 2.1) + + + + + TPEG Pti22_10, deprecated (SIRI 2.1) + + + + + TPEG Pti22_11_1, deprecated (SIRI 2.1) + + + + + TPEG Pti22_14, deprecated (SIRI 2.1) + + + + + TPEG Pti22_255_2, deprecated (SIRI 2.1) + + + + + TPEG Pti22_255, deprecated (SIRI 2.1) - replaced by Pts38_255, undefined alert cause + + + + + + Value was added in SIRI v2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. See also TPEG Pts38_8 value 'fireAtStation'. + + + + + Value was added in SIRI v2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. See also TPEG Pts38_43 value 'breakDown'. + + + + + Value was added in SIRI v2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. See also TPEG Pts38_64 value 'levelCrossingIncident'. + + + + + Value was added in SIRI v2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. See also TPEG Pts38_130 value 'awaitingShuttle'. + + + + + Value was added in SIRI v2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. See also TPEG Pts38_134 value 'awaitingApproach'. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd b/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd index f3c5c463..dd1d5fb8 100644 --- a/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd +++ b/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd @@ -238,50 +238,154 @@ Rail transport, Roads and road transport - Route point type Tpeg Report Type pti15. + Route point type Tpeg Report Type PTi15. - route_point_type TPEG pti_table15. + Values for TPEG PTs44: StopPlaceUsage - RoutePointType (Pti15: deprecated since SIRI v2.1) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + TPEG Pti15_0, PTs44_0, unknown + + + + + TPEG PTs44_1, origin + + + + + TPEG Pti15_2, PTs44_2, destination + + + + + TPEG PTs44_3, intermediate. + + + + + TPEG PTs44_4, leg board + + + + + TPEG PTs44_5, leg intermediate + + + + + TPEG PTs44_6, leg alight + + + + + TPEG PTs44_7, first route point + + + + + TPEG PTs44_8, last route point + + + + + TPEG PTs44_9, affected stop place + + + + + TPEG PTs44_10, presented stop place + + + + + TPEG PTs44_255, undefined stop place usage + + + + + TPEG Pti15_1, start point, deprecated (SIRI v2.1) and replaced by PTs44_1 value 'origin'. + + + + + TPEG Pti15_3, stop, deprecated (SIRI v2.1) + + + + + TPEG Pti15_4, via, deprecated (SIRI v2.1) + + + + + TPEG Pti15_5, not-stopping, deprecated (SIRI v2.1) + + + + + TPEG Pti15_6, temporary stop, deprecated (SIRI v2.1) + + + + + TPEG Pti15_7, temporarily not-stopping, deprecated (SIRI v2.1) + + + + + TPEG Pti15_8, exceptional stop, deprecated (SIRI v2.1) + + + + + TPEG Pti15_9, additional stop, deprecated (SIRI v2.1) + + + + + TPEG Pti15_10, request stop, deprecated (SIRI v2.1) + + + + + TPEG Pti15_11, front train destination, deprecated (SIRI v2.1) + + + + + TPEG Pti15_12, rear train destination, deprecated (SIRI v2.1) + + + + + TPEG Pti15_13, through service destination, deprecated (SIRI v2.1) + + + + + TPEG Pti15_14, not via, deprecated (SIRI v2.1) + + + + + TPEG Pti15_15, altered start point, deprecated (SIRI v2.1) + + + + + TPEG Pti15_16, altered destination, deprecated (SIRI v2.1) + + + + + TPEG Pti15_255, undefined route point, deprecated (SIRI v2.1) + + From f9eb338081070237c4e59c6223bca2f59f0a487c Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 13 Jan 2021 19:29:03 +0100 Subject: [PATCH 243/290] add new PublishAtScope to ActionData for upgrade of all older actions --- xsd/siri_model/siri_situationActions-v2.0.xsd | 14 ++++++++++++-- xsd/siri_model/siri_situationAffects-v2.0.xsd | 5 +++-- 2 files changed, 15 insertions(+), 4 deletions(-) diff --git a/xsd/siri_model/siri_situationActions-v2.0.xsd b/xsd/siri_model/siri_situationActions-v2.0.xsd index 75dfc5c7..d1193060 100644 --- a/xsd/siri_model/siri_situationActions-v2.0.xsd +++ b/xsd/siri_model/siri_situationActions-v2.0.xsd @@ -1,5 +1,4 @@ - diff --git a/xsd/siri_model/siri_situationAffects-v2.0.xsd b/xsd/siri_model/siri_situationAffects-v2.0.xsd index 707435b8..ebbc24fa 100644 --- a/xsd/siri_model/siri_situationAffects-v2.0.xsd +++ b/xsd/siri_model/siri_situationAffects-v2.0.xsd @@ -994,7 +994,7 @@ Rail transport, Roads and road transport - Elements describing the the arrival of a VEHICLE at a SCHEDULED STOP POINT. + Elements describing the arrival of a VEHICLE at a SCHEDULED STOP POINT. @@ -1005,11 +1005,12 @@ Rail transport, Roads and road transport - Elements describing the the departure of a VEHICLE from a SCHEDULED STOP POINT. + Elements describing the departure of a VEHICLE from a SCHEDULED STOP POINT. + From 5aa7a94211adbe52ba137b85478a0f47df6cc9c0 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 13 Jan 2021 23:57:22 +0100 Subject: [PATCH 244/290] clean-up and renaming because of homonymous structure in CR069 --- xsd/siri_model/siri_journey-v2.0.xsd | 4 ++-- xsd/siri_model/siri_situationActions-v2.0.xsd | 6 ------ 2 files changed, 2 insertions(+), 8 deletions(-) diff --git a/xsd/siri_model/siri_journey-v2.0.xsd b/xsd/siri_model/siri_journey-v2.0.xsd index f23cecf0..928654e1 100644 --- a/xsd/siri_model/siri_journey-v2.0.xsd +++ b/xsd/siri_model/siri_journey-v2.0.xsd @@ -1287,7 +1287,7 @@ If a QUAY is divided into sub-QUAYs or sectors (with the help of STOP ASSIGNMENT - + Information on recommendations for passengers on how to deal with the formation change. @@ -1339,7 +1339,7 @@ If a QUAY is divided into sub-QUAYs or sectors (with the help of STOP ASSIGNMENT - + Description of the recommended action for passengers on how to deal with changes, for example of the TRAIN formation. diff --git a/xsd/siri_model/siri_situationActions-v2.0.xsd b/xsd/siri_model/siri_situationActions-v2.0.xsd index d1193060..e95ff49e 100644 --- a/xsd/siri_model/siri_situationActions-v2.0.xsd +++ b/xsd/siri_model/siri_situationActions-v2.0.xsd @@ -28,7 +28,6 @@ - because ParameterisedActionStructure is base of PassengerInformationAction, PublicationWindow replaces there the ActionValidityPeriod of version Siri_XML-2.0p_a0.4, which had wrongly not the name PublicationWindow - because ParameterisedActionStructure is base of all PublishTo...-structures, PublicationWindow is now automatically also available there - ScopeType renamed to Perspective with new enumeration "general" / "stopPoint" / "vehicleJourney" -08.05.2019 D. Rubli, Siri_XML-2.0p_a0.15: --> @@ -673,11 +672,6 @@ Rail transport, Roads and road transport - - - - - From 57a9e66b98e77a06a9a15405a27f81466c350dff Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 19 Jan 2021 09:05:20 +0100 Subject: [PATCH 245/290] annotation update according to comment ..r544995185 --- xsd/siri_model/siri_facility-v2.0.xsd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xsd/siri_model/siri_facility-v2.0.xsd b/xsd/siri_model/siri_facility-v2.0.xsd index 60ba6f75..4f42c867 100644 --- a/xsd/siri_model/siri_facility-v2.0.xsd +++ b/xsd/siri_model/siri_facility-v2.0.xsd @@ -729,7 +729,7 @@ Rail transport, Roads and road transport - Values for vehicle fuel type. Use of 'other' requires the additional open ended VehicleFuelTypeOther to be filled. + Values for vehicle fuel type. Use of 'other' requires the additional open ended OtherTypeOfFuel to be filled. From 55604179a4b76f1e7bdcd37106673c02b33afc95 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 19 Jan 2021 17:36:06 +0100 Subject: [PATCH 246/290] clean-up: better xmllint check and relocation of new sx examples --- .travis/xmllint-check.sh | 2 +- .../VDV736_exm}/SX_1010_first_message.xml | 0 .../VDV736_exm}/SX_1022_main_message.xml | 0 .../VDV736_exm}/SX_1135_main_message_update.xml | 0 .../VDV736_exm}/SX_1247_end_message.xml | 0 xsd/siri_model/siri_situation-v2.0.xsd | 2 +- 6 files changed, 2 insertions(+), 2 deletions(-) rename examples/{luzern_example => siri_exm_SX/VDV736_exm}/SX_1010_first_message.xml (100%) rename examples/{luzern_example => siri_exm_SX/VDV736_exm}/SX_1022_main_message.xml (100%) rename examples/{luzern_example => siri_exm_SX/VDV736_exm}/SX_1135_main_message_update.xml (100%) rename examples/{luzern_example => siri_exm_SX/VDV736_exm}/SX_1247_end_message.xml (100%) diff --git a/.travis/xmllint-check.sh b/.travis/xmllint-check.sh index c87b7cd8..ac2f81b1 100644 --- a/.travis/xmllint-check.sh +++ b/.travis/xmllint-check.sh @@ -1,4 +1,4 @@ #!/bin/bash /usr/bin/find . -name "*.xsd" -type f | while read i; do XMLLINT_INDENT=" " xmllint --pretty 1 "$i" > "$i.pretty"; mv "$i.pretty" "$i"; done; /usr/bin/find . -name "*.xml" -type f | while read i; do XMLLINT_INDENT=" " xmllint --pretty 1 "$i" > "$i.pretty"; mv "$i.pretty" "$i"; done; /usr/bin/find . -name "*.wsdl" -type f | while read i; do XMLLINT_INDENT=" " xmllint --pretty 1 "$i" > "$i.pretty"; mv "$i.pretty" "$i"; done; echo "finished formatting" -xmllint --noout --schema xsd/siri.xsd examples/siri_exa_framework/*xml examples/siri_exm_CM/*xml examples/siri_exm_CT/*xml examples/siri_exm_ET/*xml examples/siri_exm_FM/*xml examples/siri_exm_GM/*xml examples/siri_exm_PT/*xml examples/siri_exm_SM/*xml examples/siri_exm_ST/*xml examples/siri_exm_SX/*xml examples/siri_exm_VM/*xml examples/siri_exu_capability/*xml examples/siri_exu_discovery/*xml +find examples/ -iname "*.xml" | xargs xmllint --noout --schema xsd/siri.xsd \ No newline at end of file diff --git a/examples/luzern_example/SX_1010_first_message.xml b/examples/siri_exm_SX/VDV736_exm/SX_1010_first_message.xml similarity index 100% rename from examples/luzern_example/SX_1010_first_message.xml rename to examples/siri_exm_SX/VDV736_exm/SX_1010_first_message.xml diff --git a/examples/luzern_example/SX_1022_main_message.xml b/examples/siri_exm_SX/VDV736_exm/SX_1022_main_message.xml similarity index 100% rename from examples/luzern_example/SX_1022_main_message.xml rename to examples/siri_exm_SX/VDV736_exm/SX_1022_main_message.xml diff --git a/examples/luzern_example/SX_1135_main_message_update.xml b/examples/siri_exm_SX/VDV736_exm/SX_1135_main_message_update.xml similarity index 100% rename from examples/luzern_example/SX_1135_main_message_update.xml rename to examples/siri_exm_SX/VDV736_exm/SX_1135_main_message_update.xml diff --git a/examples/luzern_example/SX_1247_end_message.xml b/examples/siri_exm_SX/VDV736_exm/SX_1247_end_message.xml similarity index 100% rename from examples/luzern_example/SX_1247_end_message.xml rename to examples/siri_exm_SX/VDV736_exm/SX_1247_end_message.xml diff --git a/xsd/siri_model/siri_situation-v2.0.xsd b/xsd/siri_model/siri_situation-v2.0.xsd index a1e17990..ea75c0df 100644 --- a/xsd/siri_model/siri_situation-v2.0.xsd +++ b/xsd/siri_model/siri_situation-v2.0.xsd @@ -761,7 +761,7 @@ Note: this means that ReasonName is NOT a complete message, but only a (few) wor - Deprecated (SIRI 2.1) - use only TpegReasonGroup and PublicEventReason. + DEPRECATED (SIRI 2.1) - use only TpegReasonGroup and PublicEventReason. From e811984067550dd1667320abd300d90e12fca553 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 19 Jan 2021 17:56:47 +0100 Subject: [PATCH 247/290] add VDV736 value in AlertCauseEnum for compatibility --- xsd/siri_model/siri_situationReasons-v2.0.xsd | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/xsd/siri_model/siri_situationReasons-v2.0.xsd b/xsd/siri_model/siri_situationReasons-v2.0.xsd index e8799fd6..ba2d5b2e 100644 --- a/xsd/siri_model/siri_situationReasons-v2.0.xsd +++ b/xsd/siri_model/siri_situationReasons-v2.0.xsd @@ -1289,6 +1289,11 @@ Rail transport, Roads and road transport Value was added in SIRI v2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. See also TPEG Pts38_64 value 'levelCrossingIncident'. + + + Value was added in SIRI v2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. See also TPEG Pts38_87 value 'heavySnowFall'. + + Value was added in SIRI v2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. See also TPEG Pts38_130 value 'awaitingShuttle'. From 9f6b595e2c20d50969c4a4dfdf81883ebe374a8e Mon Sep 17 00:00:00 2001 From: u215619 Date: Tue, 9 Mar 2021 08:44:30 +0100 Subject: [PATCH 248/290] typo --- xsd/siri.xsd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xsd/siri.xsd b/xsd/siri.xsd index 3127359b..f4239f8e 100644 --- a/xsd/siri.xsd +++ b/xsd/siri.xsd @@ -363,7 +363,7 @@ Rail transport, Roads and road transport. - Whether there is a further delvery message with more current updates that follows this one. Default is 'false'. + Whether there is a further delivery message with more current updates that follows this one. Default is 'false'. From 9160379880d180b9c0862eef58c4dd102030dce2 Mon Sep 17 00:00:00 2001 From: u215619 Date: Tue, 9 Mar 2021 09:14:14 +0100 Subject: [PATCH 249/290] AffectedLine.Origins Alignment in QualityIndexEnumeration --- xsd/siri.xsd | 4 ++-- xsd/siri/siri_base-v2.0.xsd | 2 +- xsd/siri_estimatedTimetable_service.xsd | 2 +- xsd/siri_model/siri_situation-v2.0.xsd | 14 +------------- xsd/siri_model/siri_situationAffects-v2.0.xsd | 5 +++++ xsd/siri_stopMonitoring_service.xsd | 2 +- 6 files changed, 11 insertions(+), 18 deletions(-) diff --git a/xsd/siri.xsd b/xsd/siri.xsd index f4239f8e..de0a41b9 100644 --- a/xsd/siri.xsd +++ b/xsd/siri.xsd @@ -390,12 +390,12 @@ Rail transport, Roads and road transport. - Delviery for Stop Event service. + Delivery for Stop Event service. - Delviery for Vehicle Activity Service. + Delivery for Vehicle Activity Service. diff --git a/xsd/siri/siri_base-v2.0.xsd b/xsd/siri/siri_base-v2.0.xsd index 8d33e84b..873e6092 100644 --- a/xsd/siri/siri_base-v2.0.xsd +++ b/xsd/siri/siri_base-v2.0.xsd @@ -197,7 +197,7 @@ Rail transport, Roads and road transport. - + Response from Producer to Consumer to deliver payload data. Either answers a direct ServiceRequest, or asynchronously satisfies a subscription. May be sent directly in one step, or fetched in response to a DataSupply Request. diff --git a/xsd/siri_estimatedTimetable_service.xsd b/xsd/siri_estimatedTimetable_service.xsd index 7e49bdbd..22030faa 100644 --- a/xsd/siri_estimatedTimetable_service.xsd +++ b/xsd/siri_estimatedTimetable_service.xsd @@ -38,7 +38,7 @@ 2012-03-23 +SIRI v2.0 - - Add EstimatedServiceJourneyInterchange (i.e. Estimated Connection of VEHICLE) to EstimatedTimetableDelviery + - Add EstimatedServiceJourneyInterchange (i.e. Estimated Connection of VEHICLE) to EstimatedTimetableDelivery - [FR] Add Extensions tag to EstimatedTimetableSubscriptionRequest - [DE] Add ExpectedDeparturePredictionQuality to OnwardVehicleDepartureTimes [DE] Correct capabilites matrix to matx doc. Add defauklt preview intervakl and versionref diff --git a/xsd/siri_model/siri_situation-v2.0.xsd b/xsd/siri_model/siri_situation-v2.0.xsd index ea75c0df..4ec31780 100644 --- a/xsd/siri_model/siri_situation-v2.0.xsd +++ b/xsd/siri_model/siri_situation-v2.0.xsd @@ -603,7 +603,7 @@ Rail transport, Roads and road transport ProgressStatus. One of a specified set of overall processing states assigned to SITUATION. For example, 'Draft' for not yet published; 'Published' for live SITUATIONs; 'Closed' indicates a completed SITUATION. - + Assessement of likely correctness of data. @@ -645,18 +645,6 @@ Rail transport, Roads and road transport - - - Type for Quality of data indication. - - - - - - - - - diff --git a/xsd/siri_model/siri_situationAffects-v2.0.xsd b/xsd/siri_model/siri_situationAffects-v2.0.xsd index 4767dcb5..1ae42874 100644 --- a/xsd/siri_model/siri_situationAffects-v2.0.xsd +++ b/xsd/siri_model/siri_situationAffects-v2.0.xsd @@ -585,6 +585,11 @@ Rail transport, Roads and road transport + + + ORIGINs to which the LINE runs. + + DESTINATIONs to which the LINE runs. diff --git a/xsd/siri_stopMonitoring_service.xsd b/xsd/siri_stopMonitoring_service.xsd index e4a186f3..6ec22c68 100644 --- a/xsd/siri_stopMonitoring_service.xsd +++ b/xsd/siri_stopMonitoring_service.xsd @@ -621,7 +621,7 @@ If false each subscription response will contain the full information as specifi - Type for Delviery Variant +SIRI v2.0 + Type for Delivery Variant +SIRI v2.0 From 534de316967adf57ad3b6d6da5700a6527ce7721 Mon Sep 17 00:00:00 2001 From: u215619 Date: Thu, 11 Mar 2021 10:03:09 +0100 Subject: [PATCH 250/290] Documenting elements deprecated in TpegGroup element to be more consistent --- xsd/siri_model/siri_situationReasons-v2.0.xsd | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/xsd/siri_model/siri_situationReasons-v2.0.xsd b/xsd/siri_model/siri_situationReasons-v2.0.xsd index ba2d5b2e..ab88cd13 100644 --- a/xsd/siri_model/siri_situationReasons-v2.0.xsd +++ b/xsd/siri_model/siri_situationReasons-v2.0.xsd @@ -113,7 +113,11 @@ Rail transport, Roads and road transport - + + + DEPRECATED (SIRI 2.1) - use only AlertCause. + + DEPRECATED (SIRI 2.1) - use only AlertCause. @@ -134,7 +138,11 @@ Rail transport, Roads and road transport DEPRECATED (SIRI 2.1) - use only AlertCause. - + + + DEPRECATED (SIRI 2.1) - use only AlertCause. + + From 1c177c4db31251e43d75eb793536d97b72668d4c Mon Sep 17 00:00:00 2001 From: u215619 Date: Thu, 11 Mar 2021 14:09:32 +0100 Subject: [PATCH 251/290] SourceMethod typos, DescriptionGroup.Language type set, Annotations optimize, ReasonNameContentStructure renamed to ReasonContentStructure --- xsd/datex2/DATEXIISchema_1_0_1_0.xsd | 15 ++++++++++++ xsd/siri_model/siri_situation-v2.0.xsd | 2 +- xsd/siri_model/siri_situationActions-v2.0.xsd | 24 +++++++++++-------- 3 files changed, 30 insertions(+), 11 deletions(-) diff --git a/xsd/datex2/DATEXIISchema_1_0_1_0.xsd b/xsd/datex2/DATEXIISchema_1_0_1_0.xsd index 5ed4aa6e..b87e8071 100644 --- a/xsd/datex2/DATEXIISchema_1_0_1_0.xsd +++ b/xsd/datex2/DATEXIISchema_1_0_1_0.xsd @@ -8134,6 +8134,11 @@ A station dedicated to the monitoring of the road network by processing microwave information. + + + Value was added in SIRI 2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. See also 'microwaveMonitoringStation' + + A caller using a mobile telephone (who may or may not be on the road network). @@ -8144,6 +8149,11 @@ Emergency service patrols other than police. + + + Value was added in SIRI 2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. See also 'nonPoliceEmergencyServicePatrol' + + Other sources of information. @@ -8174,6 +8184,11 @@ A motorist who is an officially registered observer. + + + Value was added in SIRI 2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. See also 'registeredMotoristObserver' + + A road authority. diff --git a/xsd/siri_model/siri_situation-v2.0.xsd b/xsd/siri_model/siri_situation-v2.0.xsd index ea75c0df..9a8ff498 100644 --- a/xsd/siri_model/siri_situation-v2.0.xsd +++ b/xsd/siri_model/siri_situation-v2.0.xsd @@ -1094,7 +1094,7 @@ Note: this means that ReasonName is NOT a complete message, but only a (few) wor 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. diff --git a/xsd/siri_model/siri_situationActions-v2.0.xsd b/xsd/siri_model/siri_situationActions-v2.0.xsd index e95ff49e..61a6c60e 100644 --- a/xsd/siri_model/siri_situationActions-v2.0.xsd +++ b/xsd/siri_model/siri_situationActions-v2.0.xsd @@ -531,7 +531,7 @@ Rail transport, Roads and road transport - Description of SITUATION. Should not repeat any strap line included in Summary. (Unbounded since SIRI 2.0) + Description of SITUATION. Should not repeat any strap line included in Summary. @@ -546,7 +546,7 @@ Rail transport, Roads and road transport - Further consequence to passengers. (Unbounded since SIRI 2.0) + Further consequence to passengers. @@ -648,11 +648,11 @@ Rail transport, Roads and road transport - + - ReasonName of passenger information action. + Reason of passenger information action. @@ -661,7 +661,7 @@ Rail transport, Roads and road transport - Further recommendation to passengers. (Unbounded since SIRI 2.0) + Further recommendation to passengers. @@ -709,20 +709,24 @@ Rail transport, Roads and road transport Content for summary of a passenger information action - + + + Content for reason of a passenger information action + + - Content for n descriptions of a passenger information action + Content for n descriptions of a passenger information action. For hiding / sorting descriptions in end devices, a description priority can be set. - Content for n consequences of a passenger information action + Content for n consequences of a passenger information action. For hiding / sorting descriptions in end devices, a consequence priority can be set. - Content for n recommendations of a passenger information action + Content for n recommendations of a passenger information action. For hiding / sorting descriptions in end devices, a recommendation priority can be set. @@ -732,7 +736,7 @@ Rail transport, Roads and road transport - Content for n remarks of a passenger information action, e,g, "For more information call xy". + Content for n remarks of a passenger information action, e,g, "For more information call xy". For hiding / sorting descriptions in end devices, a remark priority can be set. From 9c4ef445b842cf141a03579b137495a98e6bb8bc Mon Sep 17 00:00:00 2001 From: u215619 Date: Thu, 11 Mar 2021 21:36:30 +0100 Subject: [PATCH 252/290] Integrating missing improvements from https://github.com/SIRI-CEN/SIRI/tree/cr79-newElementsInAffectsForUmS --- .../exx_situationExchangeResponse.xml | 22 +- .../exx_situationExchange_ATOC.xml | 10 +- .../siri_exm_SX/exx_situationExchange_Pt.xml | 10 +- .../exx_situationExchange_response.xml | 22 +- .../exx_situationExchange_road.xml | 8 +- xsd/siri/siri_requests-v2.0.xsd | 8 +- xsd/siri_model/siri_situation-v2.0.xsd | 12 +- xsd/siri_model/siri_situationActions-v2.0.xsd | 23 +- xsd/siri_model/siri_situationAffects-v2.0.xsd | 12 +- .../siri_situationIdentity-v1.1.xsd | 2 +- xsd/siri_stopMonitoring_service.xsd | 2 +- xsd/siri_utility/siri_types-v2.0.xsd | 2 +- xsd/xml/2008/09/xsd.xsl | 997 +++++++++++++ xsd/xml/2009/01/XMLSchema.xsd | 286 ++++ xsd/xml/xml.xsd | 217 --- .../siri_estimatedVehicleJourney-v2.0.xsd | 415 ------ xsd/zrescue/siri_situation-v2.0.xsd | 1270 ----------------- xsd/zrescue/siri_situationAffects-v2.0.xsd | 1058 -------------- 18 files changed, 1360 insertions(+), 3016 deletions(-) create mode 100644 xsd/xml/2008/09/xsd.xsl create mode 100644 xsd/xml/2009/01/XMLSchema.xsd delete mode 100644 xsd/xml/xml.xsd delete mode 100644 xsd/zrescue/siri_estimatedVehicleJourney-v2.0.xsd delete mode 100644 xsd/zrescue/siri_situation-v2.0.xsd delete mode 100644 xsd/zrescue/siri_situationAffects-v2.0.xsd diff --git a/examples/siri_exm_SX/exx_situationExchangeResponse.xml b/examples/siri_exm_SX/exx_situationExchangeResponse.xml index d13537eb..c07a9368 100644 --- a/examples/siri_exm_SX/exx_situationExchangeResponse.xml +++ b/examples/siri_exm_SX/exx_situationExchangeResponse.xml @@ -13,18 +13,21 @@ 2001-12-17T09:30:47.0Z + de RAILCO01 000354 0 2001-12-17T09:30:47.0Z + de RAILCO01 000354 0 + de phone 01223333337654 03274 @@ -35,13 +38,15 @@ certain 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z - bombExplosion + bombExplosion severe + 3 public point Bomb at Barchester station - Building evacuated. AVoid station untile furtehr notice + Building evacuated. Avoid station until further notice @@ -49,7 +54,7 @@ BAAR0003 - Barchester Station + Barchester Station unknown -180 @@ -74,6 +79,7 @@ 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z unknown unknown @@ -107,18 +113,21 @@ 2001-12-17T09:30:47.0Z + de RAILCO01 000354 0 2001-12-17T09:30:47.0Z + de RAILCO01 000354 0 + de phone 01223333337654 03274 @@ -129,9 +138,11 @@ certain 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z - bombExplosion + bombExplosion severe + 3 public point Jam on the access road to Barchester Station @@ -143,7 +154,7 @@ BAAR0003 - Barchester Station + Barchester Station unknown -180 @@ -168,6 +179,7 @@ 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z delay severe diff --git a/examples/siri_exm_SX/exx_situationExchange_ATOC.xml b/examples/siri_exm_SX/exx_situationExchange_ATOC.xml index 59a90032..24dcd168 100644 --- a/examples/siri_exm_SX/exx_situationExchange_ATOC.xml +++ b/examples/siri_exm_SX/exx_situationExchange_ATOC.xml @@ -2,18 +2,21 @@ 2001-12-17T09:30:47.0Z + de RAILCO01 000354 0 2001-12-17T09:30:47.0Z + de RAILCO01 000354 0 + de phone 01223333337654 03274 @@ -24,13 +27,15 @@ certain 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z - bombExplosion + bombExplosion severe + 3 public point Bomb at Barchester station - Building evacuated. AVoid station untile furtehr notice + Building evacuated. Avoid station until further notice @@ -63,6 +68,7 @@ 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z delay severe diff --git a/examples/siri_exm_SX/exx_situationExchange_Pt.xml b/examples/siri_exm_SX/exx_situationExchange_Pt.xml index f91995b3..cb32c9a3 100644 --- a/examples/siri_exm_SX/exx_situationExchange_Pt.xml +++ b/examples/siri_exm_SX/exx_situationExchange_Pt.xml @@ -2,18 +2,21 @@ 2001-12-17T09:30:47.0Z + de RAILCO01 000354 0 2001-12-17T09:30:47.0Z + de RAILCO01 000354 0 + de phone 01223333337654 03274 @@ -24,13 +27,15 @@ certain 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z - bombExplosion + bombExplosion severe + 3 public point Bomb at Barchester station - Building evacuated. AVoid station untile furtehr notice + Building evacuated. Avoid station until further notice @@ -63,6 +68,7 @@ 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z delay severe diff --git a/examples/siri_exm_SX/exx_situationExchange_response.xml b/examples/siri_exm_SX/exx_situationExchange_response.xml index edeeb448..431a5e05 100644 --- a/examples/siri_exm_SX/exx_situationExchange_response.xml +++ b/examples/siri_exm_SX/exx_situationExchange_response.xml @@ -13,18 +13,21 @@ 2001-12-17T09:30:47.0Z + de RAILCO01 000354 0 2001-12-17T09:30:47.0Z + de RAILCO01 000354 0 + de phone 01223333337654 03274 @@ -35,13 +38,15 @@ certain 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z - bombExplosion + bombExplosion severe + 3 public point Bomb at Barchester station - Building evacuated. AVoid station untile further notice + Building evacuated. Avoid station until further notice @@ -49,7 +54,7 @@ BAAR0003 - Barchester Station + Barchester Station unknown -180 @@ -74,6 +79,7 @@ 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z unknown unknown @@ -107,18 +113,21 @@ 2001-12-17T09:30:47.0Z + de RAILCO01 000354 0 2001-12-17T09:30:47.0Z + de RAILCO01 000354 0 + de phone 01223333337654 03274 @@ -129,9 +138,11 @@ certain 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z - bombExplosion + bombExplosion severe + 3 public point Jam on the access road to Barchester Station @@ -143,7 +154,7 @@ BAAR0003 - Barchester Station + Barchester Station unknown -180 @@ -168,6 +179,7 @@ 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z delay severe diff --git a/examples/siri_exm_SX/exx_situationExchange_road.xml b/examples/siri_exm_SX/exx_situationExchange_road.xml index 24d0e071..e8bfb7d0 100644 --- a/examples/siri_exm_SX/exx_situationExchange_road.xml +++ b/examples/siri_exm_SX/exx_situationExchange_road.xml @@ -2,18 +2,21 @@ 2001-12-17T09:30:47.0Z + de RAILCO01 000354 0 2001-12-17T09:30:47.0Z + de RAILCO01 000354 0 + de phone 01223333337654 03274 @@ -24,9 +27,11 @@ certain 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z - bombExplosion + bombExplosion severe + 3 public point Jam on the access road to Barchester Station @@ -63,6 +68,7 @@ 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z delay severe diff --git a/xsd/siri/siri_requests-v2.0.xsd b/xsd/siri/siri_requests-v2.0.xsd index 4814e811..d8866cf4 100644 --- a/xsd/siri/siri_requests-v2.0.xsd +++ b/xsd/siri/siri_requests-v2.0.xsd @@ -202,7 +202,7 @@ Rail transport, Roads and road transport - If request has been proxied by an intermediate aggregating system , tracking informattion relating to the original requestor. This allows the aggregation to be stateless. + If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. @@ -444,7 +444,7 @@ be sent in the initial response (or a portion of the data if MoreData is set to - If request has been proxied by an intermediate aggregting system, trackng informattion relating to the original requestor. This allows the aggregation to be stateless. + If request has been proxied by an intermediate aggregating system, tracking information relating to the original requestor. This allows the aggregation to be stateless. @@ -624,7 +624,7 @@ be sent in the initial response (or a portion of the data if MoreData is set to - If request has been proxied by an intermediate aggregting system, trackng informattion relating to the original requestor. This allows the aggregation to be stateless. + If request has been proxied by an intermediate aggregating system, tracking information relating to the original requestor. This allows the aggregation to be stateless. @@ -868,7 +868,7 @@ be sent in the initial response (or a portion of the data if MoreData is set to - If request has been proxied by an intermediate aggregting system, trackng informattion relating to the original requestor. This allows the aggregation to be stateless. + If request has been proxied by an intermediate aggregating system, tracking information relating to the original requestor. This allows the aggregation to be stateless. diff --git a/xsd/siri_model/siri_situation-v2.0.xsd b/xsd/siri_model/siri_situation-v2.0.xsd index 9a8ff498..046e32cc 100644 --- a/xsd/siri_model/siri_situation-v2.0.xsd +++ b/xsd/siri_model/siri_situation-v2.0.xsd @@ -19,13 +19,13 @@ siri_model\siri_situation-v2.0.xsd: - + @@ -958,7 +958,7 @@ Note: this means that ReasonName is NOT a complete message, but only a (few) wor - Nrtworks and Route(s) affected by SITUATION. + Networks and Route(s) affected by SITUATION. @@ -977,7 +977,7 @@ Note: this means that ReasonName is NOT a complete message, but only a (few) wor - Stop affected by SITUATION. + STOP POINT affected by SITUATION. @@ -991,7 +991,7 @@ Note: this means that ReasonName is NOT a complete message, but only a (few) wor - Stop affected by SITUATION. + STOP PLACE affected by SITUATION. @@ -1005,7 +1005,7 @@ Note: this means that ReasonName is NOT a complete message, but only a (few) wor - Stop affected by SITUATION. + Place affected by SITUATION. @@ -1121,7 +1121,7 @@ Note: this means that ReasonName is NOT a complete message, but only a (few) wor - Further advice to passengers. + For internal information only, not passenger relevant diff --git a/xsd/siri_model/siri_situationActions-v2.0.xsd b/xsd/siri_model/siri_situationActions-v2.0.xsd index 61a6c60e..bac4fdd2 100644 --- a/xsd/siri_model/siri_situationActions-v2.0.xsd +++ b/xsd/siri_model/siri_situationActions-v2.0.xsd @@ -515,18 +515,6 @@ Rail transport, Roads and road transport - - - - - - - - - - - - @@ -557,15 +545,6 @@ Rail transport, Roads and road transport - - - Duration of specific time range (smaller than 24h). StartTime plus Duration can result in a time on the next day, smaller than the StartTime. - - - - - - @@ -731,7 +710,7 @@ Rail transport, Roads and road transport - Content to inform about a passenger information action. + Content for the duration of a passenger information action. diff --git a/xsd/siri_model/siri_situationAffects-v2.0.xsd b/xsd/siri_model/siri_situationAffects-v2.0.xsd index 4767dcb5..cbabbd36 100644 --- a/xsd/siri_model/siri_situationAffects-v2.0.xsd +++ b/xsd/siri_model/siri_situationAffects-v2.0.xsd @@ -576,18 +576,18 @@ Rail transport, Roads and road transport - Type for information about the LINEs affected by a SITUATION. + Information about the individual LINEs in the network that are affected by a SITUATION. If not explicitly overrided, modes and submodes will be defaulted to any values present (i) in the AffectedNetwork (ii) in the General Context. - Operators of LINEs affected by incident. Overrides any value specified for (i) Affected Network (ii) General Context. + Restricts the affected scope to the specified operators of LINEs that are affected by the situation. Overrides any value specified for (i) Affected Network (ii) General Context. - DESTINATIONs to which the LINE runs. + Restricts the affected scope to the specified DESTINATIONs @@ -597,7 +597,7 @@ Rail transport, Roads and road transport - ROUTEs affected if LINE has multiple ROUTEs. + Restricts the affected scope to the specified ROUTEs @@ -611,7 +611,7 @@ Rail transport, Roads and road transport - Sections of LINE affected. + Restricts the affected scope to the specified LINE SECTIONs @@ -644,7 +644,7 @@ Rail transport, Roads and road transport - Type for information about the sectons affected by a SITUATION. + Type for information about the SECTIONs affected by a SITUATION. diff --git a/xsd/siri_model/siri_situationIdentity-v1.1.xsd b/xsd/siri_model/siri_situationIdentity-v1.1.xsd index db32d9cf..46308ef6 100644 --- a/xsd/siri_model/siri_situationIdentity-v1.1.xsd +++ b/xsd/siri_model/siri_situationIdentity-v1.1.xsd @@ -116,7 +116,7 @@ Rail transport, Roads and road transport - Identifier of SITUATION within a Participant. Excldue versionr. + Identifier of SITUATION within a Participant. Exclude versionr. diff --git a/xsd/siri_stopMonitoring_service.xsd b/xsd/siri_stopMonitoring_service.xsd index e4a186f3..6d0df399 100644 --- a/xsd/siri_stopMonitoring_service.xsd +++ b/xsd/siri_stopMonitoring_service.xsd @@ -873,7 +873,7 @@ If false each subscription response will contain the full information as specifi - Whether a start time other than now can be specified for preview interval. Default is 'truet. + Whether a start time other than now can be specified for preview interval. Default is 'true'. diff --git a/xsd/siri_utility/siri_types-v2.0.xsd b/xsd/siri_utility/siri_types-v2.0.xsd index 93df23d2..0a7b26cd 100644 --- a/xsd/siri_utility/siri_types-v2.0.xsd +++ b/xsd/siri_utility/siri_types-v2.0.xsd @@ -1,6 +1,6 @@ - + diff --git a/xsd/xml/2008/09/xsd.xsl b/xsd/xml/2008/09/xsd.xsl new file mode 100644 index 00000000..cacffdb9 --- /dev/null +++ b/xsd/xml/2008/09/xsd.xsl @@ -0,0 +1,997 @@ + + + + + + + + + + + + + + + ]> + + + + + + + + + + + + + + + + + + + + + Schema document for + + + namespace + + + + unspecified namespace + + + + + + + + + + + + + + text/css + .bodytext .bodytext { + margin-left: 0; + margin-right: 0; + } + .bodytext { + margin-left: 15%; + margin-right: 2%; + } + .annotation { + + + } + .same-ns { + color: Green; + } + .diff-ns { + color: maroon; + } + .warning { + color: red; + } + p.note { + font-style: italic; + } + p.dt { + font-weight: bold; + } + span.rfc { + font-variant: small-caps; + } + + + + + + + + * * + + + + + + + + + + + bodytext + + + + + + + + + + + + + + + + + + + + + + annotation + + + + + + Annotation + + + + + + + + bodytext + + + + + + + + + + + + + + ! Unrecognized children in xs:documentation element + + + + + + + + + + + + + + + + + + + + + + +   + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + bodytext + + + + + Notes + + + + + External documentation at + + + + + + + + + + + + + + + Formal declaration in XSD source form + + + + + + + + + + + + + + + + + + + + + + + + + + + + + < + + + + + break + nobreak + + + + + + + + + + + > + + </ + + > + + /> + + + + + + + + + nobreak + + + + + + + + + + + + + + + + + + + + + + + =" + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + " + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Warning: not matched. + + warning + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + external-link same-ns + + + + + + external-link diff-ns + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + attnames + + + + + + attvals + + + + + + + + + + + + + + + + + + unknown + + + + + + + + 0 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/xsd/xml/2009/01/XMLSchema.xsd b/xsd/xml/2009/01/XMLSchema.xsd new file mode 100644 index 00000000..b5baeb33 --- /dev/null +++ b/xsd/xml/2009/01/XMLSchema.xsd @@ -0,0 +1,286 @@ + + + + + + +
      +

      About the XML namespace

      + +
      +

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

      +

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

      +

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

      +

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

      +
      +
      +       +       + + + + +
      + +

      lang (as an attribute name)

      +

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

      + +
      +
      +

      Notes

      +

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

      +

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

      +

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

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

      space (as an attribute name)

      +

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

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

      base (as an attribute name)

      +

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

      + +

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

      +
      +       +       +       + + + + +
      + +

      id (as an attribute name)

      +

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

      + +

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

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

      Father (in any context at all)

      + +
      +

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

      +
      +

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

      +
      +
      +
      +       +       + + + +
      +

      About this schema document

      + +
      +

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

      +

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

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

      + or +

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

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

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

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

      +
      +
      +       +       + + + +
      +

      Versioning policy for this schema document

      +
      +

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

      +

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

      +

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

      +

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

      + +
      +
      +       +       + +       diff --git a/xsd/xml/xml.xsd b/xsd/xml/xml.xsd deleted file mode 100644 index a169b9e4..00000000 --- a/xsd/xml/xml.xsd +++ /dev/null @@ -1,217 +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. - - - - - - - - diff --git a/xsd/zrescue/siri_estimatedVehicleJourney-v2.0.xsd b/xsd/zrescue/siri_estimatedVehicleJourney-v2.0.xsd deleted file mode 100644 index dea8bb87..00000000 --- a/xsd/zrescue/siri_estimatedVehicleJourney-v2.0.xsd +++ /dev/null @@ -1,415 +0,0 @@ - - - - - - main schema - e-service developers - CEN TC278 WG3 SG7 Team - Werner Kohl MDV - Europe - Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2003-02-10 - - - 2004-10-31 - - - 2005-02-14 - - - 2005-02-20 - - - 2005-05-11 - - 2007-04-17 - Name Space changes - - 2008-03-26 - Add wrapper tag for Line DIRECTION to help binding to Axis - - 2008-11-17 - Revise to support substitution groups - - 2011-01-19 - Drop use of As Flat Groups for EstimatedCalls - - 2012-03-23 - +SIRI v2.0 - Factored out of estimatedTimetableService - Add EstimatedServiceJourneyInterchange (i.e. Estimated Connection of VEHICLE) to EstimatedTimetableDelivery - Corrected feed and distributor Journety refs and add InterchangeRef - - -

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

      -

      This sub-schema describes the Estimated Timetable Service.

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri_model}siri_estimatedVehicleJourney.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey-v2.0.xsd - - Unclassified - CEN, VDV, RTIG 2004-2012 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.0 Draft - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI-ET XML schema. Service Interface for Real-time Information. Estimated Timetable Service. - Standard -       -       - SIRI-ET Estimated Timetable Service. -       - - - - - - A VEHICLE JOURNEY taking place on a particular date that will be managed by an AVMs. - - - - - If the journey is an alteration to a timetable, indicates the original journey and the nature of the difference. - - - - - - 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. If omitted: Passenger load is unknown. - - - - - - - Type for Origin and Destination stop of a VEHICLE JOURNEY. - - - - - The origin is used to help identify the VEHICLE JOURNEY. - - - - - Departure time from origin SCHEDULED STOP POINT. - - - - - The destination is used to help identify the VEHICLE JOURNEY. - - - - - Arrival time at destination SCHEDULED STOP POINT. - - - - - - - - A VEHICLE JOURNEY taking place on a particular date that will be managed by an AVMs. - - - - - Type for Estimated SERVICE JOURNEY INTERCHANGE. - - - - - - - - Reference to a connecting distributor VEHICLE JOURNEY. +SIRI v2.0 - - - - - Reference to a connecting distributor VEHICLE JOURNEY. +SIRI v2.0 - - - - - - - - Distributor will not wait (i.e. connection broken) SIRI w.0 - - - - - Nature of wait that distributer will make. +SIRI v2.0 - - - - - - Time at which distributor VEHICLE is expected to depart. +SIRI v2.0 - - - - - Whether connection monitoring is active or not for this connection +SIRI v2.0 - - - - - - - Type for Will Wait details - - - - - Time up until which the distributor will wait. +SIRI v2.0 - - - - - Whether an acknowledgement has been received that the driver will wait. +SIRI v2.0 - - - - - - - - Type for Real-time info about a VEHICLE JOURNEY. - - - - - Time at which data was recorded for that individual Journey - - - - - - - - - - - - - - - - - - - - - - - Whether the above call sequence is complete, i.e. represents every CALL of the SERVICE PATTERN and so can be used to replace a previous call sequence. Default is 'false'. - - - - - - - - - Ordered sequence of SCHEDULED STOP POINTs called at by the VEHICLE JOURNEY If IsCompleteStopSequence is false, may be just those stops that are altered. - - - - - Type for Rea-ltime info about a VEHICLE JOURNEY Stop. - - - - - - - This call is additional and unplanned. If omitted: CALL is planned. - - - - - This call is a cancellation of a previously announced call. - - - - - - - - - - - - - - - - Information relating to real-time properties of call. - - - - - Whether the prediction for the specific stop is considered to be of a useful accuracy or not. Default is 'false', i.e. prediction is not known to be inaccurate. {DOUBLE NEGATIVE IS BAD _ BETTER AS PredictionAccurate. Default is 'true'?]. If prediction is degraded, e.g. because in congestion, used to 9indicate a lowered quality of data. Inherited property. {SHOULD THIS JUST BE THE SPECIFIC InCongestion INDICATOR INSTEAD, OR IS IT MORE GENERAL] - - - - - How full the bus is at the stop. If omitted: Passenger load is unknown. - - - - - - - - Ordered sequence of SCHEDULED STOP POINTs called at by the VEHICLE JOURNEY If IsCompleteStopSequence is false, may be just those stops that are altered. - - - - - Information relating to recorded real-time properties of call. - - - - - - - - Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicel to arrive at.Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is -(i) any arrival platform on any related dated timetable element, -(ii) any departure platform name on this estimated element; -(iii) any departure platform name on any related dated timetable CALL. - - - - - Target departure time of VEHICLE according to latest working timetable. - - - - - Estimated time of departure of VEHICLE. - - - - - Departure QUAY ( Bay or platform) name. Defaulted taken from from planned timetable.. - - - - - Estimated time of departure of VEHICLE. - - - - - - - Type for recroded Real-time info about a VEHICLE JOURNEY Stop. - - - - - - - This call is additional and unplanned. If omitted: CALL is planned. - - - - - This call is a cancellation of a previously announced call. - - - - - - - - - -       diff --git a/xsd/zrescue/siri_situation-v2.0.xsd b/xsd/zrescue/siri_situation-v2.0.xsd deleted file mode 100644 index 0ba0c1ae..00000000 --- a/xsd/zrescue/siri_situation-v2.0.xsd +++ /dev/null @@ -1,1270 +0,0 @@ - - - - - - - - - - - - - - - - - - main schema - e-service developers - Waldemar Isajkin (INIT GmbH) - 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 - - correct data tupe to be particpant ref not participant pair - - add missing scopeType to classifier - - 2011-04-18 - - AffectedVehicleJourney should allow multiple journeys. Brian Ferris onebusaway.org - - 2012-03-23 - +SIRI v2.0 - Use revised 2.0 definitions - Update to use DATEXII V 2.0 schema - Namespace changed from http://datex2.eu/schema/1_0/1_0 to http://datex2.eu/schema/2_0RC1/2_0 - - - D2LogicalModel:ReferencePointLinear has been renamed to D2LogicalModel:ReferencePointLinear - - DelayCodeENum renamed to DelayBandEnum - - - InformationUsageOverride / D2LogicalModel:InformationUsage dropped for D2 - - D2LogicalModel:SourceInformation renamed to D2LogicalModel:Source - - - D2LogicalModel:SourceInformation values wrapped in valuse tag - - D2LogicalModel:Advcie dropped. - - D2LogicalModel:Imppact ImpactDetails wrapper tag dropped. - - D2 trafficResstrictionType renamed to trafficConstrictionType - Correct type on easementref to normalized string. - Allow transalatiobs of NLString elements - - 2013-02-11 - Correction: Certain elements of DescriptionGroup unbounded. - - 2013-10-01 - - [VDV] Added TpegSubReasonGroup to the ReasonGroup as described in the SX Documentation - - -

      SIRI-SX 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.siri.org.uk/schema/2.0/xsd/}siri_model/siri_situation-v2.0.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_stop-v0.2.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modes-v1.1.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd - - Unclassified - - Kizoom 2000-2005, CEN 2009-2012 - - -
        -
      • Schema Derived from the Kizoom XTIS schema
        • -
      - - Version 2.0 Draft - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI-SX Xml Schema for PT SITUATIONs. Common element subschema - Standard -       -       - SIRI-SX Situation Model. -       - - - - 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. - - - - - Elements identifying a SITUATION element or an update to a SITUATION. Participant reference 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 describing 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 describing 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. - - - - - 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. - - - - - Datex 2 comments for public use. - - - - - Ccomments not for public use. - - - - - Datex 2 model of where event ois taking place on the 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 Reference, 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, i.e. 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. - - - - - Reference to an 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. (Unbounded since SIRI 2.0) - - - - - - - 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. - - - - - 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 - - - - - - - - Specific vehicles affected by SITUATION. - - - - - - Vehicles 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. (Unbounded since SIRI 2.0) - - - - - Description of SITUATION. Should not repeat any strap line included in Summary. (Unbounded since SIRI 2.0) - - - - - Additional descriptive details about the SITUATION (Unbounded since SIRI 2.0). - - - - - Further advice to passengers. (Unbounded since SIRI 2.0) - - - - - 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. Default is 'true'. - - - - - - - - Values for image content. - - - - - - - - - - - - Type for a general hyperlink. - - - - - URI for link. - - - - - Label for Link. (Unbounded since SIRI 2.0) - - - - - 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 boarding restrictions. - - - - - Type of boarding and alighting allowed at stop. Default is 'Alighting'. - - - - - Type of alighting allowed at stop. Default is 'Boarding'. - - - - - - - Type for advice. - - - - - Reference to a standardis advisory NOTICE to be given to passengers if a particular condition arises . - - - - - Further Textual advice to passengers. (Unbounded since SIRI 2.0) - - - - - - - Type for blocking. - - - - - Whether information about parts of the network identified by Affects should be blocked from computation made by a Journey Planner that has a real-tiem feed of the SITUATIONs. Default is 'false'; do not suppress. - - - - - Whether information about parts of the network identified by 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. (Unbounded since SIRI 2.0) - - - - - Refernce to a fare exceptions code that is allowed because of the disruption. An easement may relax a fare condition, for exampel "You may use your metro ticket on the bus', or 'You may use your bus ticket in teh metro between these two stops'. - - - - - - - - Type for easement info. - - - - - Time band into which delay will fall. - - - - - Category of delay. - - - - - Additional journey time needed to overcome disruption. - - - - - - -       diff --git a/xsd/zrescue/siri_situationAffects-v2.0.xsd b/xsd/zrescue/siri_situationAffects-v2.0.xsd deleted file mode 100644 index 315bca5e..00000000 --- a/xsd/zrescue/siri_situationAffects-v2.0.xsd +++ /dev/null @@ -1,1058 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - main schema - e-service developers - Waldemar Isajkin (INIT GmbH) - 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 - - - 2013-10-10 - [vdv] Added Service Condition to the AffectedVehicleJourney - [vdv] Corrected LineGroup - added PublishedLineName and changed cardinality of LineRef to 1:1 - [vdv] CallCondition - changed cardinality to allow to include multiple conditions - [vdv] AffectedCallStructure - added CallPropertyGroup - [vdv] AffectedVehicleJourneyStructure - added DestinationDisplayAtOrigin - [vdv] AffectedRouteStructure - added possibility to expose the ROUTE as a sequence of STOP POINTS with links between them - [vdv] AffectedVehicles added - - -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/}siri_model/siri_situationAffects-v2.0.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_situationServiceTypes-v1.2.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modes-v1.1.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey-v2.0.xsd - - Unclassified - - Kizoom 2000-2007, CEN 2009-2012 - - -
        -
      • Schema derived Derived from the Kizoom XTIS schema
        • -
      - - Version 2.0 Draft - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI-SX Xml Schema for PT Incidents. Common affects element subschema - Standard -       -       - SIRI-SX Situation Scope. -       - - - - Type for an SCHEDUELD STOP POINT affected by a SITUATION. - - - - - - Alternative private code of stop. - - - - - Name of SCHEDULED STOP POIHT. (Unbounded since SIRI 2.0) - - - - - Type of stop type. Normally implicit in VEHICLE mode. TPEG table pti 17_4 - - - - - Spatial coordinates of STOP POINT. Derivable from StopRef. - - - - - Modes within station/stop affected by the SITUATION. If not specified, assume all modes of that station. - - - - - Refernce to a SITE or TOPOGRAPHIC PLACE affected by the Locality of stop (In UK NPtg Locality Code). Derivable from StopRef. - - - - - Name of locality in which stop is found. Derivable from LocalityRef. (Unbounded since SIRI 2.0) - - - - - Assesment of current ACCESSIBILITY of the STOP POINT as affected by the SITUATION. - - - - - Status of STOP - - - - - CONNECTION links from stop. - - - - - - CONNECTION LINKs from stop that are affected by the SITUATION. - - - - - - - - - - - Type for TRANSPORT MODEs affecetd by a SITUATION. - - - - - All known modes for stop. - - - - - Mode affected by SITUATION. - - - - - - - - - - - Values for Area Of Interest. - - - - - - - - - - - - - Type for identifier of a ZONe. - - - - - - Type for a reference to a ZONE or locality. - - - - - - - - - - Type for a reference Information about a CONNECTION link from a given stop that is affected by a SITUATION. - - - - - Reference to a CONNECTION link affected by a SITUATION. - - - - - Name of CONNECTION link affected by a SITUATION. - - - - - - - - - Reference to other connecting STOP POINT of a CONNECTION link. 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 link. Derivable from StopRef. (Unbounded since SIRI 2.0) - - - - - Zone in which connecting stop lies. - - - - - - - Direction of SERVICE JOURNEY INTERCHANGE. Default is 'both'. - - - - - PATH LINKs affected by a SITUATION. - - - - - - - - Values for DIRECTION of CONNECTION link or SERVCIE JOURNEY INTERCHANGE. - - - - - - - - - - - Information about a CONNECTION link from a given stop affected by a SITUATION. - - - - - Identifier of CONNECTION link. - - - - - Description of Link. (Unbounded since SIRI 2.0) - - - - - Nature of CONNECTION link. - - - - - Description of a DIRECTION of CONNECTION link. - - - - - 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 SERVICE JOURNEY INTERCHANGE at CONNECTION link from a given SCHEDULED STOP POINT. - - - - - Reference to a SERVICE JOURNEY INTERCHANGE affected by a SITUATION. - - - - - 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. (Unbounded since SIRI 2.0) - - - - - Reference to connecting VEHICLE JOURNEY affected by a SITUATION. - - - - - - Reference to a CONNECTION Link affected by a SITUATION. - - - - - - - - - Type for identifier of an OPERATOR Code. - - - - - - Type for reference to an OPERATOR. - - - - - - - - Type for identifier of an OPERATOR Code. - - - - - - Type for reference to an Operatorational Unit Code. - - - - - - - - Type for Annotated reference to an OPERATOR affected by a SITUATION. - - - - - Reference to an OPERATOR. - - - - - Public Name of OPERATOR. Can be derived from OperatorRef. (Unbounded since SIRI 2.0) - - - - - Short Name for OPERATOR. Can be derived from OperatorRef. (Unbounded since SIRI 2.0) - - - - - OPERATIONAL UNIT responsible for managing services. - - - - - - - - Type for Annotated reference to a NETWORK affected by a SITUATION. - - - - - Reference to a NETWORK. - - - - - Name of NETWORK. Can be derived from NetworkRef. (Unbounded since SIRI 2.0) - - - - - - - - - Type for ideifier of a Route section. - - - - - - Type for reference to a Section. - - - - - - - - Line to which link connects. - - - - - - - - - - Type for identifier of an advisory NOTICE - - - - - - Type for reference to predefined advisory NOTICE. - - - - - - - - - - - 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. (Unbounded since SIRI 2.0) - - - - - Textual description of overall routes affected. Should correspond to any structured description in the AffectedLines element. (Unbounded since SIRI 2.0) - - - - - - - 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 specified for (i) Affected Network (ii) General Context. - - - - - - DESTINATIONs to which the LINE runs. - - - - - DIRECTIONs affected. - - - - - ROUTEs affected if LINE has multiple ROUTEs. - - - - - - Route. - - - - - - - - Sections of LINE affected. - - - - - - - - - - - - - Type for information about the sectons affected by an SITUATION. - - - - - Reference to a section of ROUTE affected by a SITUATION. - - - - - 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. - - - - - Reference to a ROUTE affected by SITUATION. - - - - - DIRECTIONS affected by SITUATION. - - - - - Sections of ROUTE affected by SITUATION. - - - - - - Sections of ROUTE that is affected by SITUATION. - - - - - - - - Stop Poins of the ROUTE. Can be either all or only affected by SITUATION. - - - - - - Indicates whether the list of STOP POINTS contains all STOP POINTS of ROUTE or only affected by SITUATION. - - - - - - Stop Point of the ROUTE - - - - - GIs projection of Link to the next provided StopPoint. NB Line here means Geometry Polyline, not Transmodel Transport Line. - - - - - - - - - ROUTE LINKs affected by SITUATION. - - - - - - - - - - - - - - Type for information about a VEHICLE JOURNEY affected by an SITUATION. - - - - - Use of simple reference is deprecated - - - - Refercence to a VEHICLE JOURENY framed by the day. SIRI 2.0 - - - - - Reference to a service VEHICLE JOURNEY affected by an SITUATION. - - - - - - Reference to a specific DATED VEHICLE JOURNEY affected by an SITUATION. - - - - - Name of journey affected by an SITUATION. (Unbounded since SIRI 2.0) - - - - - OPERATOR of LINE affected by SITUATION. - - - - - Reference to the LINE of the journey affected by an SITUATION. - - - - - - DIRECTION of LINE in which journey runs. - - - - - BLOCK which journey runs. - - - - - Origin SCHEDULED STOP POINTs from which the LINE runs. [equivalent to pti15 1 start_point route_description_type] - - - - - Destination SCHEDULED STOP POINTs to which the LINE runs. [equivalent to pti15 2 destination route_description_type] - - - - - ROUTE affected by the SITUATION. - - - - - Timetabled departure tme of journey from Origin. - - - - - Timetabled arrival time of journey at Destination. - - - - - DESTINATION name shown for journey at the origin. Can be overwritten section by section by the entry in an individual CALl. - - - - - - - CALLs making up VEHICLE JOURNEY [equivalent to TPEG pti15 3 stop, 15_5 not-stopping, 15-6 temporary stop route_description_type] - - - - - - - - - - - - - Type for information about a VEHICLE JOURNEY affected by an SITUATION. - - - - - Reference to a specific VEHICLE affected by an SITUATION. - - - - - Registration plate of VEHICLE - - - - - (Mobile) phone number on which the vehicle can be called - - - - - Internet protocol address of the VEHICLE in form 000.000.000.000 - - - - - Radio address of the VEHICLE - - - - - A reference to the DRIVER or Crew currently logged in to operate a monitored VEHICLE. May be omitted if real-time data is not available - i.e. it is timetabled data. +SIRI v2.0 - - - - - The name oo the Driver or Crew +SIRI v2.0 - - - - - Reference to VEHICLE JOURNEY that VEHICLE is making. - - - - - Location where the VEHICLE was when the situation arised - - - - - Current Location where the VEHICLE - - - - - - - - Whether the VEHICLE is in traffic congestion. If not, present, not known. - - - - - Whether the panic alarm on the VEHICLE is activated. Default is 'false'. - - - - - Whether this is a Headway Service, that is shown as operating at a prescribed interval rather than to a fixed timetable. Default is 'false'. - - - - - - - - Type for information about a CALL affected by an SITUATION. - - - - - - - Order of visit to stop within JORUNYE PATTERN of journey. - - - - - Status of CALL TPEG 13_6 - - - - - - - - - - - - - - - Elements describing the the arrival of a VEHICLE at a SCHEDULED STOP POINT. - - - - - - - - - - - Elements describing the the departure of a VEHICLE from a SCHEDULED STOP POINT. - - - - - - - - - - - - Type for annotated references to a TOPOGRAPHIC PLACE. - - - - - Reference to a SITE or TOPOGRAPHIC PLACE (Locality). - - - - - Alternative identifier of SITE or TOPOGRAPHIC PLACE - - - - - Name of SITE or TOPOGRAPHIC PLACE (locality) in which stop is found. (Unbounded since SIRI 2.0) - - - - - Spatial coordinates of STOP POINT. Derivable from StopRef. - - - - - Category of TOPGRAPHIC PLACE or SITE. - - - - - Reference to an EQUIPMENT found at location. - - - - - Changes to accessibility for SITE. - - - - - - - - - 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. (Unbounded since SIRI 2.0) - - - - - 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. (Unbounded since SIRI 2.0) - - - - - Type of Component. - - - - - - Further qualifcation of affected part of Link projection, - - - - - - - - - - Type for Information on casualties. - - - - - Number of fatalities. - - - - - Number of injured presons. - - - - - -       From b257833b8b3c6e8b158a4b2be68fa7c3c84716a6 Mon Sep 17 00:00:00 2001 From: u215619 Date: Fri, 12 Mar 2021 13:11:20 +0100 Subject: [PATCH 253/290] Add Telecabin in PtNetworkModeChoiceGroup (used in SX: AffectedModeGroup) --- xsd/siri_model/siri_modes-v1.1.xsd | 1 + 1 file changed, 1 insertion(+) diff --git a/xsd/siri_model/siri_modes-v1.1.xsd b/xsd/siri_model/siri_modes-v1.1.xsd index e3f876c2..910d9f53 100644 --- a/xsd/siri_model/siri_modes-v1.1.xsd +++ b/xsd/siri_model/siri_modes-v1.1.xsd @@ -108,6 +108,7 @@ Rail transport, Roads and road transport +       From 376eddd490d59cbc3cb51f358c20b398a7847dd5 Mon Sep 17 00:00:00 2001 From: u215619 Date: Fri, 12 Mar 2021 13:41:27 +0100 Subject: [PATCH 254/290] Add xml lang in NL element Some Comments in appinfo Added AffectedLine.Origin Improved annotations --- .../exc_connectionTimetable_response.xml | 2 +- .../exm_generalMessage_response_embed.xml | 2 +- .../ext_productionTimetable_response.xml | 2 +- .../exs_stopMonitoring_response.xml | 16 +++++++------- .../exs_stopMonitoring_response_complex.xml | 12 +++++----- xsd/siri_connectionTimetable_service.xsd | 12 +++++----- xsd/siri_discovery.xsd | 22 +++++++++---------- xsd/siri_model/siri_situation-v2.0.xsd | 4 ++-- xsd/siri_model/siri_situationActions-v2.0.xsd | 2 +- xsd/siri_model/siri_situationAffects-v2.0.xsd | 5 +++++ .../siri_situationServiceTypes-v1.0.xsd | 2 +- .../siri_targetedVehicleJourney-v2.0.xsd | 9 ++++---- .../siri_feature-v2.0.xsd | 8 +++---- .../siri_infoChannel-v2.0.xsd | 8 +++---- xsd/siri_model_discovery/siri_line-v2.0.xsd | 16 +++++++------- .../siri_stopPoint-v2.0.xsd | 12 +++++----- xsd/siri_utility/siri_location-v2.0.xsd | 8 +++---- xsd/siri_utility/siri_participant-v2.0.xsd | 7 +++--- xsd/siri_utility/siri_permissions-v2.0.xsd | 4 ++-- xsd/siri_utility/siri_types-v2.0.xsd | 4 ++-- xsd/siri_utility/siri_utility-v1.1.xsd | 2 +- 21 files changed, 81 insertions(+), 78 deletions(-) diff --git a/examples/siri_exm_CT/exc_connectionTimetable_response.xml b/examples/siri_exm_CT/exc_connectionTimetable_response.xml index c3944a86..c9ea7d58 100644 --- a/examples/siri_exm_CT/exc_connectionTimetable_response.xml +++ b/examples/siri_exm_CT/exc_connectionTimetable_response.xml @@ -17,7 +17,7 @@ 2001-12-17T09:30:47-05:00 98789 2 - Erehwon + Erehwon 123 OUT diff --git a/examples/siri_exm_GM/exm_generalMessage_response_embed.xml b/examples/siri_exm_GM/exm_generalMessage_response_embed.xml index d49a9205..f36f6b16 100644 --- a/examples/siri_exm_GM/exm_generalMessage_response_embed.xml +++ b/examples/siri_exm_GM/exm_generalMessage_response_embed.xml @@ -50,7 +50,7 @@ 490G00000011 1000011 - Baker Street + Baker Street London diff --git a/examples/siri_exm_PT/ext_productionTimetable_response.xml b/examples/siri_exm_PT/ext_productionTimetable_response.xml index b1b646c0..d3172829 100644 --- a/examples/siri_exm_PT/ext_productionTimetable_response.xml +++ b/examples/siri_exm_PT/ext_productionTimetable_response.xml @@ -92,7 +92,7 @@ 01345 HLTS00103 - Gare de Nord + Gare de Nord P5M P3M P7M diff --git a/examples/siri_exm_SM/exs_stopMonitoring_response.xml b/examples/siri_exm_SM/exs_stopMonitoring_response.xml index e7087a56..3e7e3bb6 100644 --- a/examples/siri_exm_SM/exs_stopMonitoring_response.xml +++ b/examples/siri_exm_SM/exs_stopMonitoring_response.xml @@ -89,7 +89,7 @@ HLT0010 2 - String + String false 2004-12-17T09:32:43-05:00 2004-12-17T09:32:43-05:00 @@ -116,7 +116,7 @@ HLTST012 4 - Church + Church false 2004-12-17T09:30:56-05:00 2004-12-17T09:30:56-05:00 @@ -176,21 +176,21 @@ HLT0107 002 - Library + Library false 2004-12-17T09:30:43-05:00 HLT0109 007 - Library + Library false 2004-12-17T09:32:44-05:00 HLT0110 009 - Library + Library false 2004-12-17T09:38:47-05:00 @@ -213,7 +213,7 @@ HLTST112 0012 - Hospital + Hospital false 2004-12-17T09:55:47-05:00 2004-12-17T09:56:47-05:00 @@ -222,7 +222,7 @@ HLTST113 0013 - Starbucks + Starbucks false 2004-12-17T10:07:47-05:00 2004-12-17T10:09:47-05:00 @@ -230,7 +230,7 @@ HLTST114 0014 - Station + Station false 2004-12-17T10:12:47-05:00 2004-12-17T10:33:47-05:00 diff --git a/examples/siri_exm_SM/exs_stopMonitoring_response_complex.xml b/examples/siri_exm_SM/exs_stopMonitoring_response_complex.xml index 4b48f27c..6cd3e1b1 100644 --- a/examples/siri_exm_SM/exs_stopMonitoring_response_complex.xml +++ b/examples/siri_exm_SM/exs_stopMonitoring_response_complex.xml @@ -216,7 +216,7 @@ HLT0107 002 - Library + Library false 2004-12-17T09:30:42-00:00 2004-12-17T09:30:43-05:00 @@ -224,14 +224,14 @@ HLT0109 007 - Library + Library false 2004-12-17T09:32:44-05:00 HLT0110 009 - Library + Library false 2004-12-17T09:38:47-05:00 @@ -254,7 +254,7 @@ HLTST112 0012 - Hospital + Hospital false 2004-12-17T09:55:47-05:00 2004-12-17T09:56:47-05:00 @@ -277,7 +277,7 @@ HLTST113 0013 - Starbucks + Starbucks false 2004-12-17T10:07:47-05:00 2004-12-17T10:09:47-05:00 @@ -287,7 +287,7 @@ HLTST114 0014 - Station + Station false 2004-12-17T10:12:47-05:00 onTime diff --git a/xsd/siri_connectionTimetable_service.xsd b/xsd/siri_connectionTimetable_service.xsd index c2f247fb..f72c37b4 100644 --- a/xsd/siri_connectionTimetable_service.xsd +++ b/xsd/siri_connectionTimetable_service.xsd @@ -26,23 +26,23 @@ 2005-05-11 2007-04-17 - Name Space changes + 2008-11-17 - Revise to support substitution groups + 2011-01-19 - Drop use of As Flat Groups for InterChangeJourney + 2012-03-23 - +SIRI v2.0 + 2012-04-18 - Add valid until to response +

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

      diff --git a/xsd/siri_discovery.xsd b/xsd/siri_discovery.xsd index 2870d7ff..d291d5f3 100644 --- a/xsd/siri_discovery.xsd +++ b/xsd/siri_discovery.xsd @@ -24,35 +24,35 @@ 2005-11-25 2007-04-17 - Name Space changes + 2008-11-13 - Fix cardinalities on delivery items eg LINEs, refs, facilities - MoveAbstractDiscoveryDelivery to siri_requests + 2008-11-17 - Revise to support substitution groups - Correct Type on VEHICLE features delivery structure + 2012-03-23 - +SIRI v2.0 + 2012-05-17 - +SIRI v2.0 + 2013-03-28 - +SIRI v2.0 - [FR] Addition of Connection Links Discovery +

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

      diff --git a/xsd/siri_model/siri_situation-v2.0.xsd b/xsd/siri_model/siri_situation-v2.0.xsd index 046e32cc..87e97787 100644 --- a/xsd/siri_model/siri_situation-v2.0.xsd +++ b/xsd/siri_model/siri_situation-v2.0.xsd @@ -66,8 +66,8 @@ siri_model\siri_situation-v2.0.xsd: InformationUsageOverride / D2LogicalModel:InformationUsage dropped for D2 D2LogicalModel:SourceInformation renamed to D2LogicalModel:Source D2LogicalModel:SourceInformation values wrapped in valuse tag - D2LogicalModel:Advcie dropped. - D2LogicalModel:Imppact ImpactDetails wrapper tag dropped. + D2LogicalModel:Advice dropped. + D2LogicalModel:Impact ImpactDetails wrapper tag dropped. D2 trafficResstrictionType renamed to trafficConstrictionType Correct type on easementref to normalized string. Allow translations of NLString elements diff --git a/xsd/siri_model/siri_situationActions-v2.0.xsd b/xsd/siri_model/siri_situationActions-v2.0.xsd index bac4fdd2..8184e9eb 100644 --- a/xsd/siri_model/siri_situationActions-v2.0.xsd +++ b/xsd/siri_model/siri_situationActions-v2.0.xsd @@ -679,7 +679,7 @@ Rail transport, Roads and road transport - Class of size, e.g. L (large), M (medium), S (small) + Class of size, e.g. L (large), M (medium), S (small).
      If text length for a class size varies on perspective and a PassengerInformationAction applies to several perspectives, take the smallest class             diff --git a/xsd/siri_model/siri_situationAffects-v2.0.xsd b/xsd/siri_model/siri_situationAffects-v2.0.xsd index cbabbd36..54ab6a1f 100644 --- a/xsd/siri_model/siri_situationAffects-v2.0.xsd +++ b/xsd/siri_model/siri_situationAffects-v2.0.xsd @@ -585,6 +585,11 @@ Rail transport, Roads and road transport + + + Restricts the affected scope to the specified ORIGINs + + Restricts the affected scope to the specified DESTINATIONs diff --git a/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd b/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd index 4d1b34fd..62e541b2 100644 --- a/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd +++ b/xsd/siri_model/siri_situationServiceTypes-v1.0.xsd @@ -43,7 +43,7 @@ CEN - Unclassified + Kizoom 2000-2007, CEN 2009-2020 diff --git a/xsd/siri_model/siri_targetedVehicleJourney-v2.0.xsd b/xsd/siri_model/siri_targetedVehicleJourney-v2.0.xsd index a7befe72..797bea1f 100644 --- a/xsd/siri_model/siri_targetedVehicleJourney-v2.0.xsd +++ b/xsd/siri_model/siri_targetedVehicleJourney-v2.0.xsd @@ -27,17 +27,16 @@ 2005-12-12 2007-04-17 - Name Space changes + 2007-03-26 - Drop separate flatten structure on response for stopVisit + 2008-11-17 - Revise to support substitution groups + 2012-03-23 - +SIRI v2.0 - +

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

      diff --git a/xsd/siri_model_discovery/siri_feature-v2.0.xsd b/xsd/siri_model_discovery/siri_feature-v2.0.xsd index c0757125..2044440c 100644 --- a/xsd/siri_model_discovery/siri_feature-v2.0.xsd +++ b/xsd/siri_model_discovery/siri_feature-v2.0.xsd @@ -12,13 +12,13 @@ 2012-03-23 2008-11-17 - Revise to support substitution groups - Correct Type on VEHICLE features delivery structure + 2012-03-23 - +SIRI v2.0 +

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

      diff --git a/xsd/siri_model_discovery/siri_infoChannel-v2.0.xsd b/xsd/siri_model_discovery/siri_infoChannel-v2.0.xsd index c16cfc98..1279e8d4 100644 --- a/xsd/siri_model_discovery/siri_infoChannel-v2.0.xsd +++ b/xsd/siri_model_discovery/siri_infoChannel-v2.0.xsd @@ -12,12 +12,12 @@ 2012-03-23 2008-11-17 - Revise to support substitution groups - Correct Type on VEHICLE features delivery structure + 2012-03-23 - +SIRI v2.0 - Factored out from siri_discovery +

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

      diff --git a/xsd/siri_model_discovery/siri_line-v2.0.xsd b/xsd/siri_model_discovery/siri_line-v2.0.xsd index 23ecf389..edfe6a37 100644 --- a/xsd/siri_model_discovery/siri_line-v2.0.xsd +++ b/xsd/siri_model_discovery/siri_line-v2.0.xsd @@ -12,21 +12,21 @@ 2012-03-23 2008-11-17 - Revise to support substitution groups - Correct Type on VEHICLE features delivery structure + 2012-03-23 - +SIRI v2.0 - Factored out from siri_discovery + 2012-05-10 - +SIRI v2.0 + 2012-06-12 - +SIRI v2.0 - [MTA] Add Direction to Line destination +

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

      diff --git a/xsd/siri_model_discovery/siri_stopPoint-v2.0.xsd b/xsd/siri_model_discovery/siri_stopPoint-v2.0.xsd index 9308ea8a..7747d3ef 100644 --- a/xsd/siri_model_discovery/siri_stopPoint-v2.0.xsd +++ b/xsd/siri_model_discovery/siri_stopPoint-v2.0.xsd @@ -12,18 +12,18 @@ 2012-03-23 2008-11-17 - Revise to support substitution groups - Correct Type on VEHICLE features delivery structure + 2012-03-23 - +SIRI v2.0 + 2012-06-12 - +SIRI v2.0 +

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

      diff --git a/xsd/siri_utility/siri_location-v2.0.xsd b/xsd/siri_utility/siri_location-v2.0.xsd index 1b1782fc..510b0d77 100644 --- a/xsd/siri_utility/siri_location-v2.0.xsd +++ b/xsd/siri_utility/siri_location-v2.0.xsd @@ -27,13 +27,13 @@ 2007-03-29 2012-03-23 - +SIRI v2.0 + 2012-05-10 - +SIRI v2.0 - Add Line Shape by Lines discovery +

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

      diff --git a/xsd/siri_utility/siri_participant-v2.0.xsd b/xsd/siri_utility/siri_participant-v2.0.xsd index 4af406d9..a6a576c4 100644 --- a/xsd/siri_utility/siri_participant-v2.0.xsd +++ b/xsd/siri_utility/siri_participant-v2.0.xsd @@ -16,12 +16,11 @@ 2007-05-15 2008-07-015 - drop use of partipant pair - + 2012-03-22 - SIRI 2.0 - Move Capability +

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

      diff --git a/xsd/siri_utility/siri_permissions-v2.0.xsd b/xsd/siri_utility/siri_permissions-v2.0.xsd index 8620cf55..161157df 100644 --- a/xsd/siri_utility/siri_permissions-v2.0.xsd +++ b/xsd/siri_utility/siri_permissions-v2.0.xsd @@ -12,8 +12,8 @@ 2012-03-24 2012-03-23 - +SIRI v2.0 - Add error number to Error structure +

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

      diff --git a/xsd/siri_utility/siri_types-v2.0.xsd b/xsd/siri_utility/siri_types-v2.0.xsd index 0a7b26cd..c482968b 100644 --- a/xsd/siri_utility/siri_types-v2.0.xsd +++ b/xsd/siri_utility/siri_types-v2.0.xsd @@ -21,8 +21,8 @@ 2007-04-17 2012-03-23 - +SIRI v2.0 - ADrop unused IP address type +

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

      diff --git a/xsd/siri_utility/siri_utility-v1.1.xsd b/xsd/siri_utility/siri_utility-v1.1.xsd index 80569923..bd833696 100644 --- a/xsd/siri_utility/siri_utility-v1.1.xsd +++ b/xsd/siri_utility/siri_utility-v1.1.xsd @@ -10,7 +10,7 @@ Europe First drafted for version 1.0 CEN TC278 WG3 SG9 Editor Nicholas Knowles. mailto:schemer@siri.org.uk 2008-09-307 - change any to lax / emopty + 2007-04-17 From 7f6f579a202fe2458b938191dd1c8867dba28736 Mon Sep 17 00:00:00 2001 From: u215619 Date: Fri, 12 Mar 2021 14:05:36 +0100 Subject: [PATCH 255/290] clean up sx examples --- examples/siri_exm_SX/VDV736_exm/SX_1010_first_message.xml | 4 ++-- examples/siri_exm_SX/VDV736_exm/SX_1022_main_message.xml | 4 ++-- .../siri_exm_SX/VDV736_exm/SX_1135_main_message_update.xml | 4 ++-- examples/siri_exm_SX/VDV736_exm/SX_1247_end_message.xml | 4 ++-- 4 files changed, 8 insertions(+), 8 deletions(-) diff --git a/examples/siri_exm_SX/VDV736_exm/SX_1010_first_message.xml b/examples/siri_exm_SX/VDV736_exm/SX_1010_first_message.xml index d5780f43..2caaf67c 100644 --- a/examples/siri_exm_SX/VDV736_exm/SX_1010_first_message.xml +++ b/examples/siri_exm_SX/VDV736_exm/SX_1010_first_message.xml @@ -1,5 +1,5 @@ - + 2018-10-04T10:11:00+00:00 ch:VBL @@ -26,7 +26,7 @@ 2017-05-04T10:10:00+02:00 2017-05-28T17:10:00+02:00 - fire + fire Feuerwehreinsatz in der Haldenstrasse Fire brigade action at Haldenstrasse 3 diff --git a/examples/siri_exm_SX/VDV736_exm/SX_1022_main_message.xml b/examples/siri_exm_SX/VDV736_exm/SX_1022_main_message.xml index 1afe09a5..4932ab17 100644 --- a/examples/siri_exm_SX/VDV736_exm/SX_1022_main_message.xml +++ b/examples/siri_exm_SX/VDV736_exm/SX_1022_main_message.xml @@ -1,5 +1,5 @@ - + 2018-10-16T10:22:30+00:00 ch:VBL @@ -26,7 +26,7 @@ 2017-05-28T10:10:00+02:00 2017-05-28T17:10:00+02:00 - fire + fire Feuerwehreinsatz in der Haldenstrasse Fire brigade action at Haldenstrasse 3 diff --git a/examples/siri_exm_SX/VDV736_exm/SX_1135_main_message_update.xml b/examples/siri_exm_SX/VDV736_exm/SX_1135_main_message_update.xml index 1d8d64f6..4c7ce90f 100644 --- a/examples/siri_exm_SX/VDV736_exm/SX_1135_main_message_update.xml +++ b/examples/siri_exm_SX/VDV736_exm/SX_1135_main_message_update.xml @@ -1,5 +1,5 @@ - + 2018-10-16T10:22:30+00:00 ch:VBL @@ -26,7 +26,7 @@ 2017-05-28T09:42:00+02:00 2017-05-28T17:10:00+02:00 - fire + fire Feuerwehreinsatz in der Haldenstrasse Fire brigade action at Haldenstrasse 3 diff --git a/examples/siri_exm_SX/VDV736_exm/SX_1247_end_message.xml b/examples/siri_exm_SX/VDV736_exm/SX_1247_end_message.xml index fea32f98..9cef92b5 100644 --- a/examples/siri_exm_SX/VDV736_exm/SX_1247_end_message.xml +++ b/examples/siri_exm_SX/VDV736_exm/SX_1247_end_message.xml @@ -1,5 +1,5 @@ - + 2018-10-04T12:22:00+00:00 ch:VBL @@ -27,7 +27,7 @@ 2017-05-28T12:22:00+02:00 2017-05-28T17:10:00+02:00 - fire + fire Feuerwehreinsatz in der Haldenstrasse Fire brigade action at Haldenstrasse 3 From 62078c979bbac1c93ff09847e0c31bd2070b9e94 Mon Sep 17 00:00:00 2001 From: u215619 Date: Fri, 12 Mar 2021 14:37:36 +0100 Subject: [PATCH 256/290] missing import references added --- examples/siri_exm_GM/exm_generalMessage_response_embed.xml | 2 +- xsd/gml/gmlBasic2d-extract-v3_2_1-.xsd | 2 +- xsd/ifopt/ifopt_administration-v0.3.xsd | 2 +- xsd/siri_model/siri_facility-v2.0.xsd | 3 ++- xsd/siri_model/siri_journey_support-v2.0.xsd | 1 + xsd/siri_model_discovery/siri_line-v2.0.xsd | 1 + xsd/siri_model_discovery/siri_stopPoint-v2.0.xsd | 1 + xsd/siri_wsProducer.wsdl | 4 +++- 8 files changed, 11 insertions(+), 5 deletions(-) diff --git a/examples/siri_exm_GM/exm_generalMessage_response_embed.xml b/examples/siri_exm_GM/exm_generalMessage_response_embed.xml index f36f6b16..5a89a150 100644 --- a/examples/siri_exm_GM/exm_generalMessage_response_embed.xml +++ b/examples/siri_exm_GM/exm_generalMessage_response_embed.xml @@ -28,7 +28,7 @@ 2005-08-18T10:49:00Z 2005-08-18T23:59:59Z - signalFailure + signalFailure normal false Routesection information bakerloo diff --git a/xsd/gml/gmlBasic2d-extract-v3_2_1-.xsd b/xsd/gml/gmlBasic2d-extract-v3_2_1-.xsd index fabab137..de1c38e5 100644 --- a/xsd/gml/gmlBasic2d-extract-v3_2_1-.xsd +++ b/xsd/gml/gmlBasic2d-extract-v3_2_1-.xsd @@ -78,7 +78,7 @@ The elements exterior and interior describe the surface boundary of the polygon. An abstraction of a ring to support surface boundaries of different complexity. -The AbstractRing element is the abstract head of the substituition group for all closed boundaries of a surface patch. +The AbstractRing element is the abstract head of the substitution group for all closed boundaries of a surface patch. diff --git a/xsd/ifopt/ifopt_administration-v0.3.xsd b/xsd/ifopt/ifopt_administration-v0.3.xsd index 973fc2d5..410ea73e 100644 --- a/xsd/ifopt/ifopt_administration-v0.3.xsd +++ b/xsd/ifopt/ifopt_administration-v0.3.xsd @@ -224,7 +224,7 @@ Rail transport, Roads and road transport       - Abstract Type for DATA MANAGED OBJECT, that is an object that may be assigned a RESPONSIBILITY SET dictating a responsbile ORGANISATION and/or ADMINISTRATIVE ZONE. + Abstract Type for DATA MANAGED OBJECT, that is an object that may be assigned a RESPONSIBILITY SET dictating a responsible ORGANISATION and/or ADMINISTRATIVE ZONE. diff --git a/xsd/siri_model/siri_facility-v2.0.xsd b/xsd/siri_model/siri_facility-v2.0.xsd index ec39bcef..8b169a0a 100644 --- a/xsd/siri_model/siri_facility-v2.0.xsd +++ b/xsd/siri_model/siri_facility-v2.0.xsd @@ -81,9 +81,10 @@ Rail transport, Roads and road transport + - + diff --git a/xsd/siri_model/siri_journey_support-v2.0.xsd b/xsd/siri_model/siri_journey_support-v2.0.xsd index c0b02d4e..5c9f2a4f 100644 --- a/xsd/siri_model/siri_journey_support-v2.0.xsd +++ b/xsd/siri_model/siri_journey_support-v2.0.xsd @@ -86,6 +86,7 @@ Rail transport, Roads and road transport + diff --git a/xsd/siri_model_discovery/siri_line-v2.0.xsd b/xsd/siri_model_discovery/siri_line-v2.0.xsd index edfe6a37..89bfc4d8 100644 --- a/xsd/siri_model_discovery/siri_line-v2.0.xsd +++ b/xsd/siri_model_discovery/siri_line-v2.0.xsd @@ -75,6 +75,7 @@ Rail transport, Roads and road transport + diff --git a/xsd/siri_model_discovery/siri_stopPoint-v2.0.xsd b/xsd/siri_model_discovery/siri_stopPoint-v2.0.xsd index 7747d3ef..3ec8f6b6 100644 --- a/xsd/siri_model_discovery/siri_stopPoint-v2.0.xsd +++ b/xsd/siri_model_discovery/siri_stopPoint-v2.0.xsd @@ -72,6 +72,7 @@ Rail transport, Roads and road transport + diff --git a/xsd/siri_wsProducer.wsdl b/xsd/siri_wsProducer.wsdl index fa1358ef..012500f8 100644 --- a/xsd/siri_wsProducer.wsdl +++ b/xsd/siri_wsProducer.wsdl @@ -4,7 +4,9 @@ - + + + From 07615830a80cf7fd17abb9fc856b52cf3e797a07 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Sun, 14 Mar 2021 14:55:48 +0100 Subject: [PATCH 257/290] clean-up comments in wsdl files --- xsd/siri_wsConsumer-Document.wsdl | 140 +-------------------------- xsd/siri_wsConsumer-WSDL2.wsdl | 140 +-------------------------- xsd/siri_wsConsumer.wsdl | 154 +----------------------------- xsd/siri_wsProducer-Document.wsdl | 86 +---------------- xsd/siri_wsProducer-WSDL2.wsdl | 86 +---------------- xsd/siri_wsProducer.wsdl | 85 +---------------- 6 files changed, 6 insertions(+), 685 deletions(-) diff --git a/xsd/siri_wsConsumer-Document.wsdl b/xsd/siri_wsConsumer-Document.wsdl index 48c557cf..64c6419f 100644 --- a/xsd/siri_wsConsumer-Document.wsdl +++ b/xsd/siri_wsConsumer-Document.wsdl @@ -1,4 +1,5 @@ + @@ -173,143 +174,4 @@ - - CEN, VDV, RTIG 2004-2012 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 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 - - WSDL Consumer interafce for SIRI XML schema. Service Interface for Real Time Information relating to Public Transport Operations. - Standard - - -       ---> - - CEN, VDV, RTIG 2004-2012 - - -
        -
      • SIRI is derived from the VDV, RTIGXML and Trident standards.
        • -
      - - Version 2.1 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. WSDL Client binding. - Standard - - -       - --> diff --git a/xsd/siri_wsConsumer-WSDL2.wsdl b/xsd/siri_wsConsumer-WSDL2.wsdl index 61e364dc..0873adf6 100644 --- a/xsd/siri_wsConsumer-WSDL2.wsdl +++ b/xsd/siri_wsConsumer-WSDL2.wsdl @@ -1,144 +1,6 @@ + - - CEN, VDV, RTIG 2004-2012 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 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 - - WSDL Consumer interafce for SIRI XML schema. Service Interface for Real Time Information relating to Public Transport Operations. - Standard - - - ---> - - CEN, VDV, RTIG 2004-2012 - - -
        -
      • SIRI is derived from the VDV, RTIGXML and Trident standards.
        • -
      - - Version 2.1 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. WSDL 2.0 Client binding. - Standard - - - - --> diff --git a/xsd/siri_wsConsumer.wsdl b/xsd/siri_wsConsumer.wsdl index ea8155da..c50b40f6 100644 --- a/xsd/siri_wsConsumer.wsdl +++ b/xsd/siri_wsConsumer.wsdl @@ -1,4 +1,5 @@ + @@ -196,157 +197,4 @@ - - CEN, VDV, RTIG 2004-2012 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 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 - - WSDL Consumer interafce for SIRI XML schema. Service Interface for Real Time Information relating to Public Transport Operations. - Standard - - - ---> - - CEN, VDV, RTIG 2004-2012 - - -
        -
      • SIRI is derived from the VDV, RTIGXML and Trident standards.
        • -
      - - Version 2.1 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. WSDL Client binding. - Standard - - - - -->       diff --git a/xsd/siri_wsProducer-Document.wsdl b/xsd/siri_wsProducer-Document.wsdl index a2cf7798..480acb7d 100644 --- a/xsd/siri_wsProducer-Document.wsdl +++ b/xsd/siri_wsProducer-Document.wsdl @@ -1,4 +1,5 @@ + @@ -554,89 +555,4 @@ - - 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 Server binding. - Standard - - - ---> - - - - - - - - - - - -       diff --git a/xsd/siri_wsProducer-WSDL2.wsdl b/xsd/siri_wsProducer-WSDL2.wsdl index d38a46c8..9df03668 100644 --- a/xsd/siri_wsProducer-WSDL2.wsdl +++ b/xsd/siri_wsProducer-WSDL2.wsdl @@ -1,90 +1,6 @@ + - - 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 2.0 Server binding. - Standard - - - ---> - - - - - - - - - - - - diff --git a/xsd/siri_wsProducer.wsdl b/xsd/siri_wsProducer.wsdl index 034663d2..7f83b410 100644 --- a/xsd/siri_wsProducer.wsdl +++ b/xsd/siri_wsProducer.wsdl @@ -1,4 +1,5 @@ + @@ -625,88 +626,4 @@ - - - - - - CEN, VDV, RTIG 2004-2012 - - -
        -
      • SIRI is derived from the VDV, RTIGXML and Trident standards.
        • -
      - - Version 2.1 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. WSDL Server binding. - Standard - - - - - -->       From 225319a796322d8e7c9c489ec42f03dd67c216ad Mon Sep 17 00:00:00 2001 From: u215619 Date: Mon, 15 Mar 2021 10:56:09 +0100 Subject: [PATCH 258/290] version references in DATEX, gml deleted --- xsd/Siri.spp | 228 - xsd/Siri.xpr | 202 - ...chema_2_0RC1_2_0.xsd => DATEXIISchema.xsd} | 0 ...s.xsd => DATEXIISchemaWithDefinitions.xsd} | 0 xsd/datex2/DATEXIISchema_1_0_1_0.xsd | 11639 ---------------- ..._2_1.xsd => geometryBasic0d1d-extract.xsd} | 2 +- ...extract-v3_2_1.xsd => gmlBase-extract.xsd} | 0 ...act-v3_2_1-.xsd => gmlBasic2d-extract.xsd} | 2 +- ..._3_2_1.xsd => gml_extract_all_objects.xsd} | 6 +- xsd/siri_model/siri_situation.xsd | 2 +- xsd/siri_situationExchange_service.xsd | 2 +- xsd/siri_utility/siri_location.xsd | 4 +- 12 files changed, 9 insertions(+), 12078 deletions(-) delete mode 100644 xsd/Siri.spp delete mode 100644 xsd/Siri.xpr rename xsd/datex2/{DATEXIISchema_2_0RC1_2_0.xsd => DATEXIISchema.xsd} (100%) rename xsd/datex2/{DATEXIISchema_2_0RC1_2_0 with definitions.xsd => DATEXIISchemaWithDefinitions.xsd} (100%) delete mode 100644 xsd/datex2/DATEXIISchema_1_0_1_0.xsd rename xsd/gml/{geometryBasic0d1d-extract-v3_2_1.xsd => geometryBasic0d1d-extract.xsd} (99%) rename xsd/gml/{gmlBase-extract-v3_2_1.xsd => gmlBase-extract.xsd} (100%) rename xsd/gml/{gmlBasic2d-extract-v3_2_1-.xsd => gmlBasic2d-extract.xsd} (98%) rename xsd/gml/{gml_extract_all_objects_v_3_2_1.xsd => gml_extract_all_objects.xsd} (80%) diff --git a/xsd/Siri.spp b/xsd/Siri.spp deleted file mode 100644 index 8510564f..00000000 --- a/xsd/Siri.spp +++ /dev/null @@ -1,228 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/xsd/Siri.xpr b/xsd/Siri.xpr deleted file mode 100644 index 934c8eee..00000000 --- a/xsd/Siri.xpr +++ /dev/null @@ -1,202 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \ No newline at end of file diff --git a/xsd/datex2/DATEXIISchema_2_0RC1_2_0.xsd b/xsd/datex2/DATEXIISchema.xsd similarity index 100% rename from xsd/datex2/DATEXIISchema_2_0RC1_2_0.xsd rename to xsd/datex2/DATEXIISchema.xsd diff --git a/xsd/datex2/DATEXIISchema_2_0RC1_2_0 with definitions.xsd b/xsd/datex2/DATEXIISchemaWithDefinitions.xsd similarity index 100% rename from xsd/datex2/DATEXIISchema_2_0RC1_2_0 with definitions.xsd rename to xsd/datex2/DATEXIISchemaWithDefinitions.xsd diff --git a/xsd/datex2/DATEXIISchema_1_0_1_0.xsd b/xsd/datex2/DATEXIISchema_1_0_1_0.xsd deleted file mode 100644 index b87e8071..00000000 --- a/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. - - - - - Value was added in SIRI 2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. See also 'microwaveMonitoringStation' - - - - - A caller using a mobile telephone (who may or may not be on the road network). - - - - - Emergency service patrols other than police. - - - - - Value was added in SIRI 2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. See also 'nonPoliceEmergencyServicePatrol' - - - - - 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. - - - - - Value was added in SIRI 2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. See also 'registeredMotoristObserver' - - - - - 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/xsd/gml/geometryBasic0d1d-extract-v3_2_1.xsd b/xsd/gml/geometryBasic0d1d-extract.xsd similarity index 99% rename from xsd/gml/geometryBasic0d1d-extract-v3_2_1.xsd rename to xsd/gml/geometryBasic0d1d-extract.xsd index a30fa6af..fec149d6 100644 --- a/xsd/gml/geometryBasic0d1d-extract-v3_2_1.xsd +++ b/xsd/gml/geometryBasic0d1d-extract.xsd @@ -1,6 +1,6 @@ - + geometryBasic0d1d.xsd See ISO/DIS 19136 Clause 10. diff --git a/xsd/gml/gmlBase-extract-v3_2_1.xsd b/xsd/gml/gmlBase-extract.xsd similarity index 100% rename from xsd/gml/gmlBase-extract-v3_2_1.xsd rename to xsd/gml/gmlBase-extract.xsd diff --git a/xsd/gml/gmlBasic2d-extract-v3_2_1-.xsd b/xsd/gml/gmlBasic2d-extract.xsd similarity index 98% rename from xsd/gml/gmlBasic2d-extract-v3_2_1-.xsd rename to xsd/gml/gmlBasic2d-extract.xsd index de1c38e5..a7e51919 100644 --- a/xsd/gml/gmlBasic2d-extract-v3_2_1-.xsd +++ b/xsd/gml/gmlBasic2d-extract.xsd @@ -9,7 +9,7 @@ To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . - + gml:AbstractSurfaceType is an abstraction of a surface to support the different levels of complexity. A surface is always a continuous region of a plane. diff --git a/xsd/gml/gml_extract_all_objects_v_3_2_1.xsd b/xsd/gml/gml_extract_all_objects.xsd similarity index 80% rename from xsd/gml/gml_extract_all_objects_v_3_2_1.xsd rename to xsd/gml/gml_extract_all_objects.xsd index 4f8fa068..1771bb9f 100644 --- a/xsd/gml/gml_extract_all_objects_v_3_2_1.xsd +++ b/xsd/gml/gml_extract_all_objects.xsd @@ -6,7 +6,7 @@ - - - + + + diff --git a/xsd/siri_model/siri_situation.xsd b/xsd/siri_model/siri_situation.xsd index 465aaa33..4a50d64b 100644 --- a/xsd/siri_model/siri_situation.xsd +++ b/xsd/siri_model/siri_situation.xsd @@ -18,7 +18,7 @@ siri_model\siri_situation-v2.0.xsd: - + diff --git a/xsd/siri_situationExchange_service.xsd b/xsd/siri_situationExchange_service.xsd index 7feac280..fb651880 100644 --- a/xsd/siri_situationExchange_service.xsd +++ b/xsd/siri_situationExchange_service.xsd @@ -118,7 +118,7 @@ Rail transport, Roads and road transport - + diff --git a/xsd/siri_utility/siri_location.xsd b/xsd/siri_utility/siri_location.xsd index 3cd5b1b4..d4251a7f 100644 --- a/xsd/siri_utility/siri_location.xsd +++ b/xsd/siri_utility/siri_location.xsd @@ -75,9 +75,9 @@ Rail transport, Roads and road transport SIRI Framewrok Location Types. - + - + From 36aefd1ad12f1586189594c8b7f681e77e807c2b Mon Sep 17 00:00:00 2001 From: Adrian A Date: Mon, 22 Mar 2021 19:45:24 +0100 Subject: [PATCH 259/290] clean-up Monitored annot. and remove unused ET groups --- xsd/siri_estimatedTimetable_service.xsd | 4 +-- .../siri_estimatedVehicleJourney.xsd | 28 ------------------- xsd/siri_model/siri_interchangeJourney.xsd | 6 ++-- .../siri_monitoredVehicleJourney.xsd | 8 ++++-- xsd/siri_model_discovery/siri_line.xsd | 6 ++-- 5 files changed, 13 insertions(+), 39 deletions(-) diff --git a/xsd/siri_estimatedTimetable_service.xsd b/xsd/siri_estimatedTimetable_service.xsd index d992392a..d3038d80 100644 --- a/xsd/siri_estimatedTimetable_service.xsd +++ b/xsd/siri_estimatedTimetable_service.xsd @@ -262,7 +262,7 @@ If false each subscription response will contain the full information as specifi Indicates whether actual arrival-/departure times should be delivered as incremental updates, i.e. whether RECORDED CALL updates are transmitted immediately after an event occurs. +SIRI v2.1 -- 'false': Specifies that the data producer should transmit RECORDED CALL data, in particular actual arrival-/departure information as an incremental update immediately after an event occurs (with hysteresis taken into account) as it is generally the case. +- 'false': Specifies that the data producer should transmit RECORDED CALL data, in particular actual arrival-/departure information as an incremental update immediately after an event occurs (with hysteresis taken into account) as is generally the case. The server will automatically proceed with 'false' if capability is not supported. - 'true': Can be requested if the data traffic is to be reduced and an immediate transmissions is not required in any of the consumer systems. 'true' specifies that the data producer should skip RECORDED CALL updates (if capability is supported after all), i.e., deliver them with the next update instead. @@ -272,7 +272,7 @@ The server will automatically proceed with 'false' if capability is not supporte Indicates whether ONLY actual arrival-/departure times should be delivered. In other words, whether all updates related to ESTIMATED CALL should be skipped. +SIRI v2.1 -- 'false': Specifies that the data producer should transmit ESTIMATED and RECORDED CALL data as an incremental update immediately after an event occurs (with hysteresis taken into account) as it is generally the case. +- 'false': Specifies that the data producer should transmit ESTIMATED and RECORDED CALL data as an incremental update immediately after an event occurs (with hysteresis taken into account) as is generally the case. The server will automatically proceed with 'false' if capability is not supported. - 'true': Can be requested if a consumer system is only interested in the actual times / recorded events because it only wants to check the performance for example. 'true' specifies that the data producer should only deliver RECORDED CALL udpates and skip ESTIMATED CALL updates (if capability is supported after all), i.e., deliver ESTIMATED CALL updates only with the next RECORDED CALL update. diff --git a/xsd/siri_model/siri_estimatedVehicleJourney.xsd b/xsd/siri_model/siri_estimatedVehicleJourney.xsd index ae09a240..fc94b83c 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney.xsd @@ -145,34 +145,6 @@ DEPRECATED from SIRI 2.0       - - - 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. - - - - - - - diff --git a/xsd/siri_model/siri_interchangeJourney.xsd b/xsd/siri_model/siri_interchangeJourney.xsd index e29440ff..06d08c2e 100644 --- a/xsd/siri_model/siri_interchangeJourney.xsd +++ b/xsd/siri_model/siri_interchangeJourney.xsd @@ -71,14 +71,14 @@ Rail transport, Roads and road transport - + - Whether there is real-time information available for journey; if not present, not known. + Whether there is real-time information available for journey. Default is 'true'. - On a Distributor journey , a Timetabled departure time of the VEHICLE JOURNEY from the CONNECTION LINK for the SERVICE JOURNEY INTERCHANGE. On a Feeder journey a Timetabled arrival time of the VEHICLE JOURNEY at the CONNECTION link for the SERVICE JOURNEY INTERCHANGE. + On a Distributor journey, a timetabled departure time of the VEHICLE JOURNEY from the CONNECTION LINK for the SERVICE JOURNEY INTERCHANGE. On a Feeder journey a Timetabled arrival time of the VEHICLE JOURNEY at the CONNECTION link for the SERVICE JOURNEY INTERCHANGE. diff --git a/xsd/siri_model/siri_monitoredVehicleJourney.xsd b/xsd/siri_model/siri_monitoredVehicleJourney.xsd index c3fc31f9..927d89a7 100644 --- a/xsd/siri_model/siri_monitoredVehicleJourney.xsd +++ b/xsd/siri_model/siri_monitoredVehicleJourney.xsd @@ -123,14 +123,16 @@ Rail transport, Roads and road transport Elements describing the real-time progress of a monitored VEHICLE JOURNEY. - + - Whether there is real-time information available for journey; if not present, not known. + Whether there is real-time information available for journey. Default is 'true'. +It is recommended to specify a MonitoringError if Monitored is set to 'false'. - Condition indicating nature of real-time fault. Present if VEHICLE JOURNEY is normally monitored but temporarily cannot be Monitored for a known reason. + If Monitored is 'false', a (list of) reason(s) for non-availability of real-time data. Examples are "GPS", "GPRS", "Radio" etc. +MonitoringError must not be used if Monitored is omitted or set to 'true'. diff --git a/xsd/siri_model_discovery/siri_line.xsd b/xsd/siri_model_discovery/siri_line.xsd index 274cfd58..2d6a7417 100644 --- a/xsd/siri_model_discovery/siri_line.xsd +++ b/xsd/siri_model_discovery/siri_line.xsd @@ -74,7 +74,7 @@ Rail transport, Roads and road transport Standard - SIRI subschema with view of LINE for use in Discovery service + SIRI subschema with view of LINE for use in Discovery service @@ -100,10 +100,10 @@ Rail transport, Roads and road transport - Name of LINE. (Unbounded since SIRI 2.0) + Name of LINE. (Unbounded since SIRI 2.0) - + Whether the LINE has real-time info. Default is 'true'. From a5917b1c6c03619b69379943247a15686c999a4e Mon Sep 17 00:00:00 2001 From: Adrian A Date: Mon, 22 Mar 2021 19:59:11 +0100 Subject: [PATCH 260/290] clean-up after pull#74 - add datex schema version --- xsd/datex2/DATEXIISchema.xsd | 2 +- xsd/datex2/DATEXIISchemaWithDefinitions.xsd | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/xsd/datex2/DATEXIISchema.xsd b/xsd/datex2/DATEXIISchema.xsd index 31807f20..a26f54ac 100644 --- a/xsd/datex2/DATEXIISchema.xsd +++ b/xsd/datex2/DATEXIISchema.xsd @@ -1,5 +1,5 @@ - + diff --git a/xsd/datex2/DATEXIISchemaWithDefinitions.xsd b/xsd/datex2/DATEXIISchemaWithDefinitions.xsd index fc4da495..e201e2ba 100644 --- a/xsd/datex2/DATEXIISchemaWithDefinitions.xsd +++ b/xsd/datex2/DATEXIISchemaWithDefinitions.xsd @@ -1,5 +1,5 @@ - + A traffic condition which is not normal. From cce93580c6e2a0cbfc9d72263a79f96b9d71b87c Mon Sep 17 00:00:00 2001 From: Christophe Duquesne Date: Fri, 2 Apr 2021 16:49:08 +0200 Subject: [PATCH 261/290] Update siri_facility.xsd Additional enum codes to ease the mapping with the latest GBFS --- xsd/siri_model/siri_facility.xsd | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/xsd/siri_model/siri_facility.xsd b/xsd/siri_model/siri_facility.xsd index 7b629453..d715aa7d 100644 --- a/xsd/siri_model/siri_facility.xsd +++ b/xsd/siri_model/siri_facility.xsd @@ -307,6 +307,8 @@ Rail transport, Roads and road transport + + @@ -334,6 +336,7 @@ Rail transport, Roads and road transport devices: electronic devices (audio guide, headphones, etc.) and physical devices (walking stick, wheelchair, etc.) vehicles: any type of vehicles (cycle, car, scooter, hoverboard, motorbike, etc.) kW (kiloWatt) or kWh (kiloWatt-hour): means that an available or consumed power is measured + mAh (milliAmpere per hour): typically used for battery charging level litres and cubicMeters: means that a volume is measured squareMeters: means that a surface is measured meters: means that a distance is measured @@ -355,6 +358,7 @@ Rail transport, Roads and road transport + From c3792061f8fa4040a84193c03cff6cfab640947b Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 6 Apr 2021 09:27:16 +0200 Subject: [PATCH 262/290] clean-up after pull#74: add spp&xpr project files --- Siri.spp | 237 ++++++++++++++++++++++++++++++ Siri.xpr | 228 ++++++++++++++++++++++++++++ {xsd => release-notes}/ReadMe.txt | 0 3 files changed, 465 insertions(+) create mode 100644 Siri.spp create mode 100644 Siri.xpr rename {xsd => release-notes}/ReadMe.txt (100%) diff --git a/Siri.spp b/Siri.spp new file mode 100644 index 00000000..b92ab041 --- /dev/null +++ b/Siri.spp @@ -0,0 +1,237 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/Siri.xpr b/Siri.xpr new file mode 100644 index 00000000..37df7dd1 --- /dev/null +++ b/Siri.xpr @@ -0,0 +1,228 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/xsd/ReadMe.txt b/release-notes/ReadMe.txt similarity index 100% rename from xsd/ReadMe.txt rename to release-notes/ReadMe.txt From 10b98e805b3ad14676a9d59dd6eca95d02fbf8b5 Mon Sep 17 00:00:00 2001 From: "U-NT-SBB1\\u215619" Date: Thu, 8 Apr 2021 12:59:14 +0200 Subject: [PATCH 263/290] version upgrade --- .travis.yml | 20 +- .travis/travis-ci_git-commit.sh | 126 +- .travis/xmllint-check.sh | 6 +- Siri.spp | 474 +- Siri.xpr | 454 +- examples/index.htm | 666 +- .../exa_checkStatus_request.xml | 18 +- .../exa_checkStatus_response.xml | 22 +- .../exa_dataReady_request.xml | 16 +- .../exa_dataReady_response.xml | 18 +- .../exa_dataReceived_response.xml | 20 +- .../exa_dataSupply_request.xml | 20 +- .../exa_heartbeat_request.xml | 24 +- .../exa_requestSubscription_response.xml | 46 +- ...xa_subscriptionTerminated_notification.xml | 28 +- .../exa_terminateSubscription_request.xml | 18 +- .../exa_terminateSubscription_response.xml | 28 +- ...exa_terminateSubscription_response_err.xml | 30 +- ...nnectionMonitoringDistributor_response.xml | 166 +- ...xc_connectionMonitoringFeeder_response.xml | 132 +- ...nectionMonitoring_capabilitiesResponse.xml | 142 +- .../exc_connectionMonitoring_request.xml | 60 +- ...nnectionMonitoring_subscriptionRequest.xml | 44 +- ...nnectionTimetable_capabilitiesResponse.xml | 138 +- .../exc_connectionTimetable_request.xml | 38 +- .../exc_connectionTimetable_response.xml | 126 +- ...onnectionTimetable_subscriptionRequest.xml | 52 +- ...stimatedTimetable_capabilitiesResponse.xml | 136 +- .../ext_estimatedTimetable_request.xml | 44 +- .../ext_estimatedTimetable_response.xml | 182 +- ...estimatedTimetable_subscriptionRequest.xml | 56 +- ...acilityMonitoring_capabilitiesResponse.xml | 132 +- .../exf_facilityMonitoring_request.xml | 50 +- .../exf_facilityMonitoring_response.xml | 190 +- ...facilityMonitoring_subscriptionRequest.xml | 76 +- .../exm_generalMessage_capabilityResponse.xml | 134 +- .../exm_generalMessage_request.xml | 48 +- .../exm_generalMessage_response.xml | 60 +- .../exm_generalMessage_response_embed.xml | 130 +- ...exm_generalMessage_subscriptionRequest.xml | 38 +- ...oductionTimetable_capabilitiesResponse.xml | 140 +- .../ext_productionTimetable_request.xml | 48 +- .../ext_productionTimetable_response.xml | 226 +- ...roductionTimetable_subscriptionRequest.xml | 60 +- .../exp_stopMonitoring_permissions.xml | 152 +- ...xs_stopMonitoring_capabilitiesResponse.xml | 218 +- .../exs_stopMonitoring_request.xml | 90 +- .../exs_stopMonitoring_request_simple.xml | 34 +- .../exs_stopMonitoring_response.xml | 562 +- .../exs_stopMonitoring_response_complex.xml | 682 +- .../exs_stopMonitoring_response_simple.xml | 114 +- ...exs_stopMonitoring_subscriptionRequest.xml | 130 +- ...pMonitoring_subscriptionRequest_simple.xml | 52 +- ...exs_stopTimetable_capabilitiesResponse.xml | 166 +- .../siri_exm_ST/exs_stopTimetable_request.xml | 46 +- .../exs_stopTimetable_response.xml | 94 +- .../exs_stopTimetable_subscriptionRequest.xml | 52 +- .../VDV736_exm/SX_1010_first_message.xml | 508 +- .../VDV736_exm/SX_1022_main_message.xml | 4622 ++-- .../SX_1135_main_message_update.xml | 4412 +-- .../VDV736_exm/SX_1247_end_message.xml | 794 +- .../exx_situationExchangeResponse.xml | 560 +- .../exx_situationExchange_ATOC.xml | 202 +- .../siri_exm_SX/exx_situationExchange_Pt.xml | 202 +- ...x_situationExchange_capabilityResponse.xml | 138 +- .../exx_situationExchange_request.xml | 64 +- .../exx_situationExchange_request_simple.xml | 42 +- .../exx_situationExchange_response.xml | 556 +- .../exx_situationExchange_road.xml | 408 +- ..._situationExchange_subscriptionRequest.xml | 40 +- ...vehicleMonitoring_capabilitiesResponse.xml | 160 +- .../exv_vehicleMonitoring_request.xml | 68 +- .../exv_vehicleMonitoring_request_simple.xml | 44 +- .../exv_vehicleMonitoring_response.xml | 318 +- .../exv_vehicleMonitoring_response_simple.xml | 124 +- ...exv_vehicleMonitoring_responsex_simple.xml | 124 +- ..._vehicleMonitoring_subscriptionRequest.xml | 68 +- .../exd_allServices_capabilitiesRequest.xml | 76 +- .../exd_allServices_capabilitiesResponse.xml | 988 +- .../exd_lines_discoveryRequest.xml | 20 +- .../exd_lines_discoveryResponse.xml | 154 +- ...exd_productCategories_discoveryRequest.xml | 16 +- ...xd_productCategories_discoveryResponse.xml | 26 +- .../exd_serviceFeatures_discoveryRequest.xml | 16 +- .../exd_serviceFeatures_discoveryResponse.xml | 36 +- .../exd_stopPoints_discoveryRequest.xml | 48 +- .../exd_stopPoints_discoveryResponse.xml | 94 +- .../exd_vehicleFeatures_discoveryRequest.xml | 16 +- .../exd_vehicleFeatures_discoveryResponse.xml | 34 +- release-notes/ReadMe.txt | 908 +- release-notes/SIRI_XML-2.0q_changes.txt | 112 +- xsd/acsb/acsb_accessibility.xsd | 276 +- xsd/acsb/acsb_all.xsd | 22 +- xsd/acsb/acsb_limitations.xsd | 282 +- xsd/acsb/acsb_passengerMobility.xsd | 424 +- xsd/datex2/DATEXIISchema.xsd | 7420 ++--- xsd/datex2/DATEXIISchemaWithDefinitions.xsd | 23046 ++++++++-------- xsd/gml/basicTypes.xsd | 534 +- xsd/gml/geometryBasic0d1d-extract.xsd | 542 +- xsd/gml/gmlBase-extract.xsd | 336 +- xsd/gml/gmlBasic2d-extract.xsd | 240 +- xsd/gml/gml_extract_all_objects.xsd | 24 +- xsd/ifopt/ifopt_administration.xsd | 508 +- xsd/ifopt/ifopt_allStopPlace.xsd | 66 +- xsd/ifopt/ifopt_checkpoint.xsd | 444 +- xsd/ifopt/ifopt_countries.xsd | 2640 +- xsd/ifopt/ifopt_equipment.xsd | 414 +- xsd/ifopt/ifopt_location.xsd | 562 +- xsd/ifopt/ifopt_modes.xsd | 168 +- xsd/ifopt/ifopt_modification.xsd | 346 +- xsd/ifopt/ifopt_path.xsd | 328 +- xsd/ifopt/ifopt_stop.xsd | 786 +- xsd/ifopt/ifopt_time.xsd | 262 +- xsd/ifopt/ifopt_types.xsd | 192 +- xsd/siri.xsd | 1062 +- xsd/siri/siri_all_framework.xsd | 24 +- xsd/siri/siri_base.xsd | 630 +- xsd/siri/siri_common_services.xsd | 1800 +- xsd/siri/siri_request_errorConditions.xsd | 1180 +- xsd/siri/siri_request_support.xsd | 420 +- xsd/siri/siri_requests.xsd | 2144 +- xsd/siriSg.xsd | 298 +- xsd/siri_all_functionalServices.xsd | 190 +- xsd/siri_connectionMonitoring_service.xsd | 1462 +- xsd/siri_connectionTimetable_service.xsd | 970 +- xsd/siri_discovery.xsd | 1796 +- xsd/siri_estimatedTimetable_service.xsd | 980 +- xsd/siri_facilityMonitoring_service.xsd | 986 +- xsd/siri_generalMessage_service.xsd | 966 +- xsd/siri_model/siri_all.xsd | 26 +- xsd/siri_model/siri_all_journeyModel.xsd | 42 +- xsd/siri_model/siri_all_model.xsd | 26 +- xsd/siri_model/siri_all_situation.xsd | 34 +- xsd/siri_model/siri_datedVehicleJourney.xsd | 1404 +- .../siri_estimatedVehicleJourney.xsd | 944 +- xsd/siri_model/siri_facilities.xsd | 1034 +- xsd/siri_model/siri_facility.xsd | 1520 +- xsd/siri_model/siri_feature_support.xsd | 290 +- xsd/siri_model/siri_interchangeJourney.xsd | 176 +- xsd/siri_model/siri_journey.xsd | 3806 +-- xsd/siri_model/siri_journey_support.xsd | 2044 +- xsd/siri_model/siri_modelPermissions.xsd | 676 +- xsd/siri_model/siri_modes.xsd | 1372 +- .../siri_monitoredVehicleJourney.xsd | 1276 +- xsd/siri_model/siri_operator_support.xsd | 174 +- xsd/siri_model/siri_reference.xsd | 1688 +- xsd/siri_model/siri_situation.xsd | 3068 +- xsd/siri_model/siri_situationActions.xsd | 1498 +- xsd/siri_model/siri_situationAffects.xsd | 3065 +- xsd/siri_model/siri_situationClassifiers.xsd | 860 +- xsd/siri_model/siri_situationIdentity.xsd | 494 +- xsd/siri_model/siri_situationReasons.xsd | 2738 +- xsd/siri_model/siri_situationServiceTypes.xsd | 1278 +- .../siri_targetedVehicleJourney.xsd | 272 +- xsd/siri_model/siri_time.xsd | 712 +- .../siri_connectionLink.xsd | 230 +- xsd/siri_model_discovery/siri_feature.xsd | 316 +- xsd/siri_model_discovery/siri_infoChannel.xsd | 198 +- xsd/siri_model_discovery/siri_line.xsd | 482 +- xsd/siri_model_discovery/siri_stopPoint.xsd | 316 +- xsd/siri_productionTimetable_service.xsd | 1028 +- xsd/siri_situationExchange_service.xsd | 1570 +- xsd/siri_stopMonitoring_service.xsd | 2104 +- xsd/siri_stopTimetable_service.xsd | 926 +- xsd/siri_utility/siri_all_utility.xsd | 28 +- xsd/siri_utility/siri_location.xsd | 540 +- xsd/siri_utility/siri_participant.xsd | 158 +- xsd/siri_utility/siri_permissions.xsd | 270 +- xsd/siri_utility/siri_types.xsd | 332 +- xsd/siri_utility/siri_utility.xsd | 602 +- xsd/siri_vehicleMonitoring_service.xsd | 1404 +- xsd/siri_wsConsumer-Document.wsdl | 354 +- xsd/siri_wsConsumer-WSDL2.wsdl | 192 +- xsd/siri_wsConsumer.wsdl | 400 +- xsd/siri_wsProducer-Document.wsdl | 1116 +- xsd/siri_wsProducer-WSDL2.wsdl | 458 +- xsd/siri_wsProducer.wsdl | 1258 +- xsd/wsdl_model/siri_wsConsumer-Framework.xsd | 196 +- xsd/wsdl_model/siri_wsConsumer-Services.xsd | 310 +- .../siri_wsProducer-DiscoveryCapability.xsd | 246 +- xsd/wsdl_model/siri_wsProducer-Framework.xsd | 276 +- xsd/wsdl_model/siri_wsProducer-Services.xsd | 526 +- xsd/xml/2008/09/xsd.xsl | 1994 +- xsd/xml/2009/01/XMLSchema.xsd | 572 +- 184 files changed, 63381 insertions(+), 63380 deletions(-) diff --git a/.travis.yml b/.travis.yml index 7db6ea77..95d74298 100644 --- a/.travis.yml +++ b/.travis.yml @@ -1,10 +1,10 @@ -language: minimal - -before_script: - - sudo apt-get install -qq libxml2-utils - -script: - - bash .travis/xmllint-check.sh - -after_script: - - bash .travis/travis-ci_git-commit.sh +language: minimal + +before_script: + - sudo apt-get install -qq libxml2-utils + +script: + - bash .travis/xmllint-check.sh + +after_script: + - bash .travis/travis-ci_git-commit.sh diff --git a/.travis/travis-ci_git-commit.sh b/.travis/travis-ci_git-commit.sh index 896660f6..a245fa0f 100644 --- a/.travis/travis-ci_git-commit.sh +++ b/.travis/travis-ci_git-commit.sh @@ -1,64 +1,64 @@ -#!/bin/bash -# function to make a commit on a branch in a Travis CI build -# be sure to avoid creating a Travis CI fork bomb -# see https://gist.github.com/mitchellkrogza/a296ab5102d7e7142cc3599fca634203 and https://github.com/travis-ci/travis-ci/issues/1701 -function travis-branch-commit() { - local head_ref branch_ref - head_ref=$(git rev-parse HEAD) - if [[ $? -ne 0 || ! $head_ref ]]; then - err "Failed to get HEAD reference" - return 1 - fi - branch_ref=$(git rev-parse "$TRAVIS_BRANCH") - if [[ $? -ne 0 || ! $branch_ref ]]; then - err "Failed to get $TRAVIS_BRANCH reference" - return 1 - fi - if [[ $head_ref != $branch_ref ]]; then - msg "HEAD ref ($head_ref) does not match $TRAVIS_BRANCH ref ($branch_ref)" - msg "Someone may have pushed new commits before this build cloned the repo" - return 1 - fi - if ! git checkout "$TRAVIS_BRANCH"; then - err "Failed to checkout $TRAVIS_BRANCH" - return 1 - fi - - if ! git add --all .; then - err "Failed to add modified files to git index" - return 1 - fi - # make Travis CI skip this build - if ! git commit -m "Travis CI update [skip ci]"; then - err "Failed to commit updates" - return 1 - fi - # add to your .travis.yml: `branches\n except:\n - "/travis_build-\\d+/"\n` - local git_tag=travis_build-$TRAVIS_BUILD_NUMBER - if ! git tag "$git_tag" -m "Generated tag from Travis CI build $TRAVIS_BUILD_NUMBER"; then - err "Failed to create git tag: $git_tag" - return 1 - fi - local remote=origin - if [[ $GH_TOKEN ]]; then - remote=https://$GH_TOKEN@github.com/$GH_REPO - fi - if [[ $TRAVIS_BRANCH == master ]]; then - msg "Not pushing updates to branch $TRAVIS_BRANCH" - return 0 - fi - if ! git push --quiet --follow-tags "$remote" "$TRAVIS_BRANCH" > /dev/null 2>&1; then - err "Failed to push git changes" - return 1 - fi -} - -function msg() { - echo "travis-commit: $*" -} - -function err() { - msg "$*" 1>&2 -} - +#!/bin/bash +# function to make a commit on a branch in a Travis CI build +# be sure to avoid creating a Travis CI fork bomb +# see https://gist.github.com/mitchellkrogza/a296ab5102d7e7142cc3599fca634203 and https://github.com/travis-ci/travis-ci/issues/1701 +function travis-branch-commit() { + local head_ref branch_ref + head_ref=$(git rev-parse HEAD) + if [[ $? -ne 0 || ! $head_ref ]]; then + err "Failed to get HEAD reference" + return 1 + fi + branch_ref=$(git rev-parse "$TRAVIS_BRANCH") + if [[ $? -ne 0 || ! $branch_ref ]]; then + err "Failed to get $TRAVIS_BRANCH reference" + return 1 + fi + if [[ $head_ref != $branch_ref ]]; then + msg "HEAD ref ($head_ref) does not match $TRAVIS_BRANCH ref ($branch_ref)" + msg "Someone may have pushed new commits before this build cloned the repo" + return 1 + fi + if ! git checkout "$TRAVIS_BRANCH"; then + err "Failed to checkout $TRAVIS_BRANCH" + return 1 + fi + + if ! git add --all .; then + err "Failed to add modified files to git index" + return 1 + fi + # make Travis CI skip this build + if ! git commit -m "Travis CI update [skip ci]"; then + err "Failed to commit updates" + return 1 + fi + # add to your .travis.yml: `branches\n except:\n - "/travis_build-\\d+/"\n` + local git_tag=travis_build-$TRAVIS_BUILD_NUMBER + if ! git tag "$git_tag" -m "Generated tag from Travis CI build $TRAVIS_BUILD_NUMBER"; then + err "Failed to create git tag: $git_tag" + return 1 + fi + local remote=origin + if [[ $GH_TOKEN ]]; then + remote=https://$GH_TOKEN@github.com/$GH_REPO + fi + if [[ $TRAVIS_BRANCH == master ]]; then + msg "Not pushing updates to branch $TRAVIS_BRANCH" + return 0 + fi + if ! git push --quiet --follow-tags "$remote" "$TRAVIS_BRANCH" > /dev/null 2>&1; then + err "Failed to push git changes" + return 1 + fi +} + +function msg() { + echo "travis-commit: $*" +} + +function err() { + msg "$*" 1>&2 +} + travis-branch-commit \ No newline at end of file diff --git a/.travis/xmllint-check.sh b/.travis/xmllint-check.sh index ac2f81b1..d2e0c442 100644 --- a/.travis/xmllint-check.sh +++ b/.travis/xmllint-check.sh @@ -1,4 +1,4 @@ -#!/bin/bash -/usr/bin/find . -name "*.xsd" -type f | while read i; do XMLLINT_INDENT=" " xmllint --pretty 1 "$i" > "$i.pretty"; mv "$i.pretty" "$i"; done; /usr/bin/find . -name "*.xml" -type f | while read i; do XMLLINT_INDENT=" " xmllint --pretty 1 "$i" > "$i.pretty"; mv "$i.pretty" "$i"; done; /usr/bin/find . -name "*.wsdl" -type f | while read i; do XMLLINT_INDENT=" " xmllint --pretty 1 "$i" > "$i.pretty"; mv "$i.pretty" "$i"; done; -echo "finished formatting" +#!/bin/bash +/usr/bin/find . -name "*.xsd" -type f | while read i; do XMLLINT_INDENT=" " xmllint --pretty 1 "$i" > "$i.pretty"; mv "$i.pretty" "$i"; done; /usr/bin/find . -name "*.xml" -type f | while read i; do XMLLINT_INDENT=" " xmllint --pretty 1 "$i" > "$i.pretty"; mv "$i.pretty" "$i"; done; /usr/bin/find . -name "*.wsdl" -type f | while read i; do XMLLINT_INDENT=" " xmllint --pretty 1 "$i" > "$i.pretty"; mv "$i.pretty" "$i"; done; +echo "finished formatting" find examples/ -iname "*.xml" | xargs xmllint --noout --schema xsd/siri.xsd \ No newline at end of file diff --git a/Siri.spp b/Siri.spp index b92ab041..2b2a14f1 100644 --- a/Siri.spp +++ b/Siri.spp @@ -1,237 +1,237 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/Siri.xpr b/Siri.xpr index 37df7dd1..96d29275 100644 --- a/Siri.xpr +++ b/Siri.xpr @@ -1,228 +1,228 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/examples/index.htm b/examples/index.htm index 7666a52f..5c3bbc4a 100644 --- a/examples/index.htm +++ b/examples/index.htm @@ -1,334 +1,334 @@ - - - - - - - - - - - - - - - - - - - - - - - - - -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

       
      - - + + + + + + + + + + + + + + + + + + + + + + + + + +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/examples/siri_exa_framework/exa_checkStatus_request.xml b/examples/siri_exa_framework/exa_checkStatus_request.xml index 8a3d8b7c..68843213 100644 --- a/examples/siri_exa_framework/exa_checkStatus_request.xml +++ b/examples/siri_exa_framework/exa_checkStatus_request.xml @@ -1,9 +1,9 @@ - - - - - - 2004-12-17T09:30:47-05:00 - EREWHON - - + + + + + + 2004-12-17T09:30:47-05:00 + EREWHON + + diff --git a/examples/siri_exa_framework/exa_checkStatus_response.xml b/examples/siri_exa_framework/exa_checkStatus_response.xml index cd361cad..0dd01d2e 100644 --- a/examples/siri_exa_framework/exa_checkStatus_response.xml +++ b/examples/siri_exa_framework/exa_checkStatus_response.xml @@ -1,11 +1,11 @@ - - - - - 2001-12-17T09:30:47-05:00 - true - 2004-12-17T19:30:47-05:00 - PT2M - 2004-12-17T09:30:47-05:00 - - + + + + + 2001-12-17T09:30:47-05:00 + true + 2004-12-17T19:30:47-05:00 + PT2M + 2004-12-17T09:30:47-05:00 + + diff --git a/examples/siri_exa_framework/exa_dataReady_request.xml b/examples/siri_exa_framework/exa_dataReady_request.xml index 2df43564..12486175 100644 --- a/examples/siri_exa_framework/exa_dataReady_request.xml +++ b/examples/siri_exa_framework/exa_dataReady_request.xml @@ -1,8 +1,8 @@ - - - - - 2004-12-17T09:30:47-05:00 - KUBRICK - - + + + + + 2004-12-17T09:30:47-05:00 + KUBRICK + + diff --git a/examples/siri_exa_framework/exa_dataReady_response.xml b/examples/siri_exa_framework/exa_dataReady_response.xml index 85b7899d..fcf8a014 100644 --- a/examples/siri_exa_framework/exa_dataReady_response.xml +++ b/examples/siri_exa_framework/exa_dataReady_response.xml @@ -1,9 +1,9 @@ - - - - - 2004-12-17T09:30:47-05:00 - NADER - true - - + + + + + 2004-12-17T09:30:47-05:00 + NADER + true + + diff --git a/examples/siri_exa_framework/exa_dataReceived_response.xml b/examples/siri_exa_framework/exa_dataReceived_response.xml index b9f1a160..be5f8425 100644 --- a/examples/siri_exa_framework/exa_dataReceived_response.xml +++ b/examples/siri_exa_framework/exa_dataReceived_response.xml @@ -1,10 +1,10 @@ - - - - - 2001-12-17T09:30:47-05:00 - NADER - 012225678 - true - - + + + + + 2001-12-17T09:30:47-05:00 + NADER + 012225678 + true + + diff --git a/examples/siri_exa_framework/exa_dataSupply_request.xml b/examples/siri_exa_framework/exa_dataSupply_request.xml index cebea5b8..562de3ee 100644 --- a/examples/siri_exa_framework/exa_dataSupply_request.xml +++ b/examples/siri_exa_framework/exa_dataSupply_request.xml @@ -1,10 +1,10 @@ - - - - - 2004-12-17T09:30:47-05:00 - NADER - ABCDE0 - false - - + + + + + 2004-12-17T09:30:47-05:00 + NADER + ABCDE0 + false + + diff --git a/examples/siri_exa_framework/exa_heartbeat_request.xml b/examples/siri_exa_framework/exa_heartbeat_request.xml index cfeb8d67..7becdc00 100644 --- a/examples/siri_exa_framework/exa_heartbeat_request.xml +++ b/examples/siri_exa_framework/exa_heartbeat_request.xml @@ -1,12 +1,12 @@ - - - - - 2004-12-17T09:30:47-05:00 - KUBRICK - true - 2004-12-17T09:30:47-05:00 - P1Y2M3DT10H30M - 2004-12-17T09:30:47-05:00 - - + + + + + 2004-12-17T09:30:47-05:00 + KUBRICK + true + 2004-12-17T09:30:47-05:00 + P1Y2M3DT10H30M + 2004-12-17T09:30:47-05:00 + + diff --git a/examples/siri_exa_framework/exa_requestSubscription_response.xml b/examples/siri_exa_framework/exa_requestSubscription_response.xml index ca033b8d..e4b0bf85 100644 --- a/examples/siri_exa_framework/exa_requestSubscription_response.xml +++ b/examples/siri_exa_framework/exa_requestSubscription_response.xml @@ -1,23 +1,23 @@ - - - - - 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 - - - - - - + + + + + 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 + + + + + + diff --git a/examples/siri_exa_framework/exa_subscriptionTerminated_notification.xml b/examples/siri_exa_framework/exa_subscriptionTerminated_notification.xml index 8323ca00..23e3f43e 100644 --- a/examples/siri_exa_framework/exa_subscriptionTerminated_notification.xml +++ b/examples/siri_exa_framework/exa_subscriptionTerminated_notification.xml @@ -1,14 +1,14 @@ - - - - - 2004-12-17T09:30:47-05:00 - KUBRICK - NADER - 987653 - - - Weekly restart - - - + + + + + 2004-12-17T09:30:47-05:00 + KUBRICK + NADER + 987653 + + + Weekly restart + + + diff --git a/examples/siri_exa_framework/exa_terminateSubscription_request.xml b/examples/siri_exa_framework/exa_terminateSubscription_request.xml index b8822f72..5d2cf9b8 100644 --- a/examples/siri_exa_framework/exa_terminateSubscription_request.xml +++ b/examples/siri_exa_framework/exa_terminateSubscription_request.xml @@ -1,9 +1,9 @@ - - - - - 2004-12-17T09:30:47-05:00 - NADER - - - + + + + + 2004-12-17T09:30:47-05:00 + NADER + + + diff --git a/examples/siri_exa_framework/exa_terminateSubscription_response.xml b/examples/siri_exa_framework/exa_terminateSubscription_response.xml index aebd926b..6393d0e6 100644 --- a/examples/siri_exa_framework/exa_terminateSubscription_response.xml +++ b/examples/siri_exa_framework/exa_terminateSubscription_response.xml @@ -1,14 +1,14 @@ - - - - - 2004-12-17T09:30:47-05:00 - KUBRICK - - 2004-12-17T09:30:47-05:00 - NADER - 0000456 - true - - - + + + + + 2004-12-17T09:30:47-05:00 + KUBRICK + + 2004-12-17T09:30:47-05:00 + NADER + 0000456 + true + + + diff --git a/examples/siri_exa_framework/exa_terminateSubscription_response_err.xml b/examples/siri_exa_framework/exa_terminateSubscription_response_err.xml index e26d5ec5..aac2b3fe 100644 --- a/examples/siri_exa_framework/exa_terminateSubscription_response_err.xml +++ b/examples/siri_exa_framework/exa_terminateSubscription_response_err.xml @@ -1,15 +1,15 @@ - - - - - 2004-12-17T09:30:47-05:00 - KUBRICK - - 987653 - false - - - - - - + + + + + 2004-12-17T09:30:47-05:00 + KUBRICK + + 987653 + false + + + + + + diff --git a/examples/siri_exm_CM/exc_connectionMonitoringDistributor_response.xml b/examples/siri_exm_CM/exc_connectionMonitoringDistributor_response.xml index b8975166..23c28e78 100644 --- a/examples/siri_exm_CM/exc_connectionMonitoringDistributor_response.xml +++ b/examples/siri_exm_CM/exc_connectionMonitoringDistributor_response.xml @@ -1,83 +1,83 @@ - - - - - - 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 - - - - + + + + + + 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/examples/siri_exm_CM/exc_connectionMonitoringFeeder_response.xml b/examples/siri_exm_CM/exc_connectionMonitoringFeeder_response.xml index 535e8f7a..8e2679a8 100644 --- a/examples/siri_exm_CM/exc_connectionMonitoringFeeder_response.xml +++ b/examples/siri_exm_CM/exc_connectionMonitoringFeeder_response.xml @@ -1,66 +1,66 @@ - - - - - - 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 - 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 - - - - + + + + + + 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 + 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/examples/siri_exm_CM/exc_connectionMonitoring_capabilitiesResponse.xml b/examples/siri_exm_CM/exc_connectionMonitoring_capabilitiesResponse.xml index 1f6b5161..5a0264ee 100644 --- a/examples/siri_exm_CM/exc_connectionMonitoring_capabilitiesResponse.xml +++ b/examples/siri_exm_CM/exc_connectionMonitoring_capabilitiesResponse.xml @@ -1,71 +1,71 @@ - - - - 2001-12-17T09:30:47.0Z - http://www.mytransportco.eu - true - - - - cpidId001 - - String - - - - - true - true - - - true - true - - true - true - true - true - - - PT60M - true - true - true - - - en - - - - true - true - - - true - true - true - true - - - - - - - - true - true - - - true - - - true - - - true - - - - - - + + + + 2001-12-17T09:30:47.0Z + http://www.mytransportco.eu + true + + + + cpidId001 + + String + + + + + true + true + + + true + true + + true + true + true + true + + + PT60M + true + true + true + + + en + + + + true + true + + + true + true + true + true + + + + + + + + true + true + + + true + + + true + + + true + + + + + + diff --git a/examples/siri_exm_CM/exc_connectionMonitoring_request.xml b/examples/siri_exm_CM/exc_connectionMonitoring_request.xml index 0df04e9f..86cb7ac4 100644 --- a/examples/siri_exm_CM/exc_connectionMonitoring_request.xml +++ b/examples/siri_exm_CM/exc_connectionMonitoring_request.xml @@ -1,30 +1,30 @@ - - - - - - 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 - - - - + + + + + + 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 + + + + diff --git a/examples/siri_exm_CM/exc_connectionMonitoring_subscriptionRequest.xml b/examples/siri_exm_CM/exc_connectionMonitoring_subscriptionRequest.xml index c5bea571..7d827630 100644 --- a/examples/siri_exm_CM/exc_connectionMonitoring_subscriptionRequest.xml +++ b/examples/siri_exm_CM/exc_connectionMonitoring_subscriptionRequest.xml @@ -1,22 +1,22 @@ - - - - - 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 - - - - - + + + + + 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 + + + + + diff --git a/examples/siri_exm_CT/exc_connectionTimetable_capabilitiesResponse.xml b/examples/siri_exm_CT/exc_connectionTimetable_capabilitiesResponse.xml index 27bc88cb..89effee7 100644 --- a/examples/siri_exm_CT/exc_connectionTimetable_capabilitiesResponse.xml +++ b/examples/siri_exm_CT/exc_connectionTimetable_capabilitiesResponse.xml @@ -1,69 +1,69 @@ - - - - 2001-12-17T09:30:47.0Z - http://www.mytransportco.eu - true - - - cpidId001 - - String - - - - - true - true - - - true - true - - true - true - true - true - - - true - true - - - en - - - - true - true - - - true - true - true - true - - - - - 0001 - - - - true - true - - - true - - - true - - - true - - - - - - + + + + 2001-12-17T09:30:47.0Z + http://www.mytransportco.eu + true + + + cpidId001 + + String + + + + + true + true + + + true + true + + true + true + true + true + + + true + true + + + en + + + + true + true + + + true + true + true + true + + + + + 0001 + + + + true + true + + + true + + + true + + + true + + + + + + diff --git a/examples/siri_exm_CT/exc_connectionTimetable_request.xml b/examples/siri_exm_CT/exc_connectionTimetable_request.xml index 9141bf5a..df11fec8 100644 --- a/examples/siri_exm_CT/exc_connectionTimetable_request.xml +++ b/examples/siri_exm_CT/exc_connectionTimetable_request.xml @@ -1,19 +1,19 @@ - - - - - - 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 - - - + + + + + + 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 + + + diff --git a/examples/siri_exm_CT/exc_connectionTimetable_response.xml b/examples/siri_exm_CT/exc_connectionTimetable_response.xml index c9ea7d58..69025549 100644 --- a/examples/siri_exm_CT/exc_connectionTimetable_response.xml +++ b/examples/siri_exm_CT/exc_connectionTimetable_response.xml @@ -1,63 +1,63 @@ - - - - - - 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 - - - - + + + + + + 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/examples/siri_exm_CT/exc_connectionTimetable_subscriptionRequest.xml b/examples/siri_exm_CT/exc_connectionTimetable_subscriptionRequest.xml index 70a7e386..813db8d1 100644 --- a/examples/siri_exm_CT/exc_connectionTimetable_subscriptionRequest.xml +++ b/examples/siri_exm_CT/exc_connectionTimetable_subscriptionRequest.xml @@ -1,26 +1,26 @@ - - - - - 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 - - - - + + + + + 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 + + + + diff --git a/examples/siri_exm_ET/ext_estimatedTimetable_capabilitiesResponse.xml b/examples/siri_exm_ET/ext_estimatedTimetable_capabilitiesResponse.xml index 0c019fb2..2ffca2bd 100644 --- a/examples/siri_exm_ET/ext_estimatedTimetable_capabilitiesResponse.xml +++ b/examples/siri_exm_ET/ext_estimatedTimetable_capabilitiesResponse.xml @@ -1,68 +1,68 @@ - - - - 2001-12-17T09:30:47.0Z - http://www.mytransportco.eu - true - - - cpidId001 - - String - - - - - true - true - - - true - true - - true - true - true - true - - - true - true - - - en-uk - - - - true - - - true - true - true - true - - - - - 001 - - - - true - true - - - true - - - true - - - true - - - - - - + + + + 2001-12-17T09:30:47.0Z + http://www.mytransportco.eu + true + + + cpidId001 + + 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/examples/siri_exm_ET/ext_estimatedTimetable_request.xml b/examples/siri_exm_ET/ext_estimatedTimetable_request.xml index a3e683eb..172fc6f6 100644 --- a/examples/siri_exm_ET/ext_estimatedTimetable_request.xml +++ b/examples/siri_exm_ET/ext_estimatedTimetable_request.xml @@ -1,22 +1,22 @@ - - - - - - 2004-12-17T09:30:47-05:00 - NADER - - - 2001-12-17T09:30:47-05:00 - P1Y2M3DT10H30M - 0008 - SMOOTH - - - 123 - INBOUND - - - - - + + + + + + 2004-12-17T09:30:47-05:00 + NADER + + + 2001-12-17T09:30:47-05:00 + P1Y2M3DT10H30M + 0008 + SMOOTH + + + 123 + INBOUND + + + + + diff --git a/examples/siri_exm_ET/ext_estimatedTimetable_response.xml b/examples/siri_exm_ET/ext_estimatedTimetable_response.xml index 5548ea06..b3e061d3 100644 --- a/examples/siri_exm_ET/ext_estimatedTimetable_response.xml +++ b/examples/siri_exm_ET/ext_estimatedTimetable_response.xml @@ -1,91 +1,91 @@ - - - - - - 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 - Cat274 - 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 - - - - - + + + + + + 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 + Cat274 + 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/examples/siri_exm_ET/ext_estimatedTimetable_subscriptionRequest.xml b/examples/siri_exm_ET/ext_estimatedTimetable_subscriptionRequest.xml index 7da31a1b..5e1b4f3b 100644 --- a/examples/siri_exm_ET/ext_estimatedTimetable_subscriptionRequest.xml +++ b/examples/siri_exm_ET/ext_estimatedTimetable_subscriptionRequest.xml @@ -1,28 +1,28 @@ - - - - - - 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 - - - + + + + + + 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/examples/siri_exm_FM/exf_facilityMonitoring_capabilitiesResponse.xml b/examples/siri_exm_FM/exf_facilityMonitoring_capabilitiesResponse.xml index bdd9f36f..b79580e3 100644 --- a/examples/siri_exm_FM/exf_facilityMonitoring_capabilitiesResponse.xml +++ b/examples/siri_exm_FM/exf_facilityMonitoring_capabilitiesResponse.xml @@ -1,66 +1,66 @@ - - - - 2001-12-17T09:30:47.0Z - http://www.mytransportco.eu - true - - - cpidId001 - - String - - - - - true - true - - - true - true - - true - true - true - true - - - PT60M - true - true - true - - - en-uk - - - - true - - - true - true - true - - - - - VR23 - - - - true - true - - - true - - - true - - - - - - + + + + 2001-12-17T09:30:47.0Z + http://www.mytransportco.eu + true + + + cpidId001 + + String + + + + + true + true + + + true + true + + true + true + true + true + + + PT60M + true + true + true + + + en-uk + + + + true + + + true + true + true + + + + + VR23 + + + + true + true + + + true + + + true + + + + + + diff --git a/examples/siri_exm_FM/exf_facilityMonitoring_request.xml b/examples/siri_exm_FM/exf_facilityMonitoring_request.xml index e1b5acb3..8377dd08 100644 --- a/examples/siri_exm_FM/exf_facilityMonitoring_request.xml +++ b/examples/siri_exm_FM/exf_facilityMonitoring_request.xml @@ -1,25 +1,25 @@ - - - - - - - en - P1Y2M3DT10H30M - P1Y2M3DT10H30M - direct - true - false - - - 2004-12-17T09:30:47-05:00 - NADER - - 2004-12-17T09:30:47-05:00 - - P10M - PLACE98765 - 20 - - - + + + + + + + en + P1Y2M3DT10H30M + P1Y2M3DT10H30M + direct + true + false + + + 2004-12-17T09:30:47-05:00 + NADER + + 2004-12-17T09:30:47-05:00 + + P10M + PLACE98765 + 20 + + + diff --git a/examples/siri_exm_FM/exf_facilityMonitoring_response.xml b/examples/siri_exm_FM/exf_facilityMonitoring_response.xml index a18e726e..5d440298 100644 --- a/examples/siri_exm_FM/exf_facilityMonitoring_response.xml +++ b/examples/siri_exm_FM/exf_facilityMonitoring_response.xml @@ -1,95 +1,95 @@ - - - - - - 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 - - - - - + + + + + + 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/examples/siri_exm_FM/exf_facilityMonitoring_subscriptionRequest.xml b/examples/siri_exm_FM/exf_facilityMonitoring_subscriptionRequest.xml index 33b82c74..6395c0a4 100644 --- a/examples/siri_exm_FM/exf_facilityMonitoring_subscriptionRequest.xml +++ b/examples/siri_exm_FM/exf_facilityMonitoring_subscriptionRequest.xml @@ -1,38 +1,38 @@ - - - - - 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 - - - + + + + + 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 + + + diff --git a/examples/siri_exm_GM/exm_generalMessage_capabilityResponse.xml b/examples/siri_exm_GM/exm_generalMessage_capabilityResponse.xml index ce73e525..b6160d2b 100644 --- a/examples/siri_exm_GM/exm_generalMessage_capabilityResponse.xml +++ b/examples/siri_exm_GM/exm_generalMessage_capabilityResponse.xml @@ -1,67 +1,67 @@ - - - - 2001-12-17T09:30:47-05:00 - http://www.mytransportco.eu - true - - - cpidId001 - - String - - - - - true - true - - - true - false - - true - true - false - false - - - PT60M - true - - - en-uk - - - - false - true - - - - - - - - true - true - - - true - - - - - - NADER - - - false - EMERGENCY - - - - - - - + + + + 2001-12-17T09:30:47-05:00 + http://www.mytransportco.eu + true + + + cpidId001 + + String + + + + + true + true + + + true + false + + true + true + false + false + + + PT60M + true + + + en-uk + + + + false + true + + + + + + + + true + true + + + true + + + + + + NADER + + + false + EMERGENCY + + + + + + + diff --git a/examples/siri_exm_GM/exm_generalMessage_request.xml b/examples/siri_exm_GM/exm_generalMessage_request.xml index a8710a18..74bd4ce5 100644 --- a/examples/siri_exm_GM/exm_generalMessage_request.xml +++ b/examples/siri_exm_GM/exm_generalMessage_request.xml @@ -1,24 +1,24 @@ - - - - - - - en - P1Y2M3DT10H30M - P1Y2M3DT10H30M - direct - true - false - - - 2004-12-17T09:30:47-05:00 - NADER - - 2004-12-17T09:30:47-05:00 - - WARNING - - - - + + + + + + + en + P1Y2M3DT10H30M + P1Y2M3DT10H30M + direct + true + false + + + 2004-12-17T09:30:47-05:00 + NADER + + 2004-12-17T09:30:47-05:00 + + WARNING + + + + diff --git a/examples/siri_exm_GM/exm_generalMessage_response.xml b/examples/siri_exm_GM/exm_generalMessage_response.xml index f2d8cb13..c29fbe23 100644 --- a/examples/siri_exm_GM/exm_generalMessage_response.xml +++ b/examples/siri_exm_GM/exm_generalMessage_response.xml @@ -1,30 +1,30 @@ - - - - - - 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 - - - - + + + + + + 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/examples/siri_exm_GM/exm_generalMessage_response_embed.xml b/examples/siri_exm_GM/exm_generalMessage_response_embed.xml index 5a89a150..5a8f1ed6 100644 --- a/examples/siri_exm_GM/exm_generalMessage_response_embed.xml +++ b/examples/siri_exm_GM/exm_generalMessage_response_embed.xml @@ -1,65 +1,65 @@ - - - - - - 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 - - - - - - - - - - - + + + + + + 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/examples/siri_exm_GM/exm_generalMessage_subscriptionRequest.xml b/examples/siri_exm_GM/exm_generalMessage_subscriptionRequest.xml index 51de6f07..4abf3776 100644 --- a/examples/siri_exm_GM/exm_generalMessage_subscriptionRequest.xml +++ b/examples/siri_exm_GM/exm_generalMessage_subscriptionRequest.xml @@ -1,19 +1,19 @@ - - - - - 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 - - - - + + + + + 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 + + + + diff --git a/examples/siri_exm_PT/ext_productionTimetable_capabilitiesResponse.xml b/examples/siri_exm_PT/ext_productionTimetable_capabilitiesResponse.xml index 9f4e1e5a..e30dc4aa 100644 --- a/examples/siri_exm_PT/ext_productionTimetable_capabilitiesResponse.xml +++ b/examples/siri_exm_PT/ext_productionTimetable_capabilitiesResponse.xml @@ -1,70 +1,70 @@ - - - - 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 - - - - - - + + + + 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/examples/siri_exm_PT/ext_productionTimetable_request.xml b/examples/siri_exm_PT/ext_productionTimetable_request.xml index 405f1712..061c28b8 100644 --- a/examples/siri_exm_PT/ext_productionTimetable_request.xml +++ b/examples/siri_exm_PT/ext_productionTimetable_request.xml @@ -1,24 +1,24 @@ - - - - - - 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 - - - - - + + + + + + 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/examples/siri_exm_PT/ext_productionTimetable_response.xml b/examples/siri_exm_PT/ext_productionTimetable_response.xml index d3172829..9b12116b 100644 --- a/examples/siri_exm_PT/ext_productionTimetable_response.xml +++ b/examples/siri_exm_PT/ext_productionTimetable_response.xml @@ -1,113 +1,113 @@ - - - - - - 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 - - - - - - - - + + + + + + 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/examples/siri_exm_PT/ext_productionTimetable_subscriptionRequest.xml b/examples/siri_exm_PT/ext_productionTimetable_subscriptionRequest.xml index 37885aeb..ddab7cb7 100644 --- a/examples/siri_exm_PT/ext_productionTimetable_subscriptionRequest.xml +++ b/examples/siri_exm_PT/ext_productionTimetable_subscriptionRequest.xml @@ -1,30 +1,30 @@ - - - - - - 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 - - - - - - + + + + + + 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/examples/siri_exm_SM/exp_stopMonitoring_permissions.xml b/examples/siri_exm_SM/exp_stopMonitoring_permissions.xml index 46250ea3..0bc6d396 100644 --- a/examples/siri_exm_SM/exp_stopMonitoring_permissions.xml +++ b/examples/siri_exm_SM/exp_stopMonitoring_permissions.xml @@ -1,76 +1,76 @@ - - - - - - - - true - false - - - true - - - - - false - A1 - - - - - false - Bar - - - - - - NADER - - true - true - - - true - - - - true - A1 - Foo - - - - - false - Bar - - - - - - Va - - true - true - - - true - - - true - - - - false - Bar - - - - + + + + + + + + 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/examples/siri_exm_SM/exs_stopMonitoring_capabilitiesResponse.xml b/examples/siri_exm_SM/exs_stopMonitoring_capabilitiesResponse.xml index 9aa4e8a5..23e0d5ec 100644 --- a/examples/siri_exm_SM/exs_stopMonitoring_capabilitiesResponse.xml +++ b/examples/siri_exm_SM/exs_stopMonitoring_capabilitiesResponse.xml @@ -1,109 +1,109 @@ - - - - 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 - - - - + + + + 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 + + + + diff --git a/examples/siri_exm_SM/exs_stopMonitoring_request.xml b/examples/siri_exm_SM/exs_stopMonitoring_request.xml index 429cfd27..5635dbb1 100644 --- a/examples/siri_exm_SM/exs_stopMonitoring_request.xml +++ b/examples/siri_exm_SM/exs_stopMonitoring_request.xml @@ -1,45 +1,45 @@ - - - - - - - en - P1Y2M3DT10H30M - P1Y2M3DT10H30M - direct - true - false - - - 2004-12-17T09:30:47-05:00 - MONTECHRISTO - 2B|~2B - NADER - - 2004-12-17T09:30:47-05:00 - - - P10M - EH00001 - OPERATOR22 - LINE77 - OUTBOUND - PLACE98765 - all - - true - 7 - 2 - 20 - calls - true - - - + + + + + + + en + P1Y2M3DT10H30M + P1Y2M3DT10H30M + direct + true + false + + + 2004-12-17T09:30:47-05:00 + MONTECHRISTO + 2B|~2B + NADER + + 2004-12-17T09:30:47-05:00 + + + P10M + EH00001 + OPERATOR22 + LINE77 + OUTBOUND + PLACE98765 + all + + true + 7 + 2 + 20 + calls + true + + + diff --git a/examples/siri_exm_SM/exs_stopMonitoring_request_simple.xml b/examples/siri_exm_SM/exs_stopMonitoring_request_simple.xml index 4a9166b6..3177540a 100644 --- a/examples/siri_exm_SM/exs_stopMonitoring_request_simple.xml +++ b/examples/siri_exm_SM/exs_stopMonitoring_request_simple.xml @@ -1,17 +1,17 @@ - - - - - 2004-12-17T09:30:47-05:00 - NADER - - 2004-12-17T09:30:47-05:00 - - EH00001 - - - + + + + + 2004-12-17T09:30:47-05:00 + NADER + + 2004-12-17T09:30:47-05:00 + + EH00001 + + + diff --git a/examples/siri_exm_SM/exs_stopMonitoring_response.xml b/examples/siri_exm_SM/exs_stopMonitoring_response.xml index 3e7e3bb6..4dc65be6 100644 --- a/examples/siri_exm_SM/exs_stopMonitoring_response.xml +++ b/examples/siri_exm_SM/exs_stopMonitoring_response.xml @@ -1,281 +1,281 @@ - - - - - - 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 - HLTST011 - British Museum Stop A - - - 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 - Boris Special - - Kensall Green - - true - false - false - false - reliable - - 180 - 90 - - 23 - 22 - seatsAvailable - 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 - - - true - - 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 - HLTST011 - 123 - Out - What, will the line stretch out to the crack of doom? - - - - 2004-12-17T09:30:47-05:00 - SED9843214675429 - HLTST011 - 123 - Out - - Hello Stop - - - + + + + + + 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 + HLTST011 + British Museum Stop A + + + 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 + Boris Special + + Kensall Green + + true + false + false + false + reliable + + 180 + 90 + + 23 + 22 + seatsAvailable + 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 + + + true + + 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 + HLTST011 + 123 + Out + What, will the line stretch out to the crack of doom? + + + + 2004-12-17T09:30:47-05:00 + SED9843214675429 + HLTST011 + 123 + Out + + Hello Stop + + + diff --git a/examples/siri_exm_SM/exs_stopMonitoring_response_complex.xml b/examples/siri_exm_SM/exs_stopMonitoring_response_complex.xml index 6cd3e1b1..8fe9e6dc 100644 --- a/examples/siri_exm_SM/exs_stopMonitoring_response_complex.xml +++ b/examples/siri_exm_SM/exs_stopMonitoring_response_complex.xml @@ -1,341 +1,341 @@ - - - - - - 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 - HLTST011 - British Museum Stop A - Musee Britannique Halte A - - - 2004-12-17T09:25:46-05:00 - - SED9843214675432 - 2004-12-17T10:25:46-05:00 - HLTST011 - CLR7654 - - - Line123 - Out - - 2004-12-17 - Oubound - - - 123 - - OP22 - PDCATEXPRESS - SERVCCAT551 - - PLACE21 - Highbury - - Kensall Green - - - Roman Road - - PLACE45 - Paradise Park - Parc du Paradis - Boris Special - - Kensall Green - - true - false - false - false - reliable - - 180 - 90 - - 23 - 22 - seatsAvailable - PT2M - Service running on time - inProgress - - - 1 - 3456 - 1 - - BLOCK765 - RUN765 - VEH987654 - DRV654 - N.I.Blick - - - - HLT0010 - 2 - Town Hall - Hotel de Ville - false - 2004-12-17T09:32:43-05:00 - 2004-12-17T09:32:43-05:00 - - - - 0014 - - true - - 180 - 90 - - - 2004-12-17T09:40:46-05:00 - 2004-12-17T09:40:46-05:00 - arrived - 2004-12-17T09:42:47-05:00 - 2004-12-17T09:40:47-05:00 - - arrived - Bay 5 - - - - - HLTST012 - 4 - Church - Eglise - 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 - - - true - - Hello bus for line 123 ! - Shelter - - - - 2004-12-17T09:25:46-06:00 - - SED9843214675434 - - - - Line128 - Inbound - - 2004-12-17 - ABC576 - - Rt24 - - 24 - To Library - Line128 - - OP22 - PDCATEXPRESS - SERVCCAT551 - 444 - 446 - - PLACE4675 - Chancery Lane - - Picadilly Green - - PLACE1245 - Paradise Park - - Accessiblity help available from driver - - 02134567 - - - true - 2004-12-17T09:30:42-00:00 - 2004-12-17T10:12:47-05:00 - otherService - - - - Low - Low Floo vehicler - notAvailable - - - false - palletAccess_lowFloor - - - - true - false - false - true - abcd - reliable - - 53 - 0.1 - - -PT2M - Running Early - - BLOCK6765 - RUN7865 - VEH9876555 - - - - HLT0107 - 002 - Library - false - 2004-12-17T09:30:42-00:00 - 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 - 2004-12-17T09:55:47-05:00 - - reliable - 0.9 - 2004-12-17T09:55:47-05:00 - 2004-12-17T09:58:47-05:00 - - 2004-12-17T09:55:47-05:00 - onTime - Approaching stop - 2 - PT10M - PT11M - 750 - 1 - - - HLTST113 - 0013 - Starbucks - false - 2004-12-17T10:07:47-05:00 - 2004-12-17T10:09:47-05:00 - 2000 - 2 - - - HLTST114 - 0014 - Station - false - 2004-12-17T10:12:47-05:00 - onTime - 2 - 4000 - 3 - - - - 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 - HLTST011 - 123 - Out - What, will the line stretch out to the crack of doom? - - - - 2004-12-17T09:30:47-05:00 - SED9843214675429 - HLTST011 - 123 - Out - - Hello Stop - - - + + + + + + 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 + HLTST011 + British Museum Stop A + Musee Britannique Halte A + + + 2004-12-17T09:25:46-05:00 + + SED9843214675432 + 2004-12-17T10:25:46-05:00 + HLTST011 + CLR7654 + + + Line123 + Out + + 2004-12-17 + Oubound + + + 123 + + OP22 + PDCATEXPRESS + SERVCCAT551 + + PLACE21 + Highbury + + Kensall Green + + + Roman Road + + PLACE45 + Paradise Park + Parc du Paradis + Boris Special + + Kensall Green + + true + false + false + false + reliable + + 180 + 90 + + 23 + 22 + seatsAvailable + PT2M + Service running on time + inProgress + + + 1 + 3456 + 1 + + BLOCK765 + RUN765 + VEH987654 + DRV654 + N.I.Blick + + + + HLT0010 + 2 + Town Hall + Hotel de Ville + false + 2004-12-17T09:32:43-05:00 + 2004-12-17T09:32:43-05:00 + + + + 0014 + + true + + 180 + 90 + + + 2004-12-17T09:40:46-05:00 + 2004-12-17T09:40:46-05:00 + arrived + 2004-12-17T09:42:47-05:00 + 2004-12-17T09:40:47-05:00 + + arrived + Bay 5 + + + + + HLTST012 + 4 + Church + Eglise + 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 + + + true + + Hello bus for line 123 ! + Shelter + + + + 2004-12-17T09:25:46-06:00 + + SED9843214675434 + + + + Line128 + Inbound + + 2004-12-17 + ABC576 + + Rt24 + + 24 + To Library + Line128 + + OP22 + PDCATEXPRESS + SERVCCAT551 + 444 + 446 + + PLACE4675 + Chancery Lane + + Picadilly Green + + PLACE1245 + Paradise Park + + Accessiblity help available from driver + + 02134567 + + + true + 2004-12-17T09:30:42-00:00 + 2004-12-17T10:12:47-05:00 + otherService + + + + Low + Low Floo vehicler + notAvailable + + + false + palletAccess_lowFloor + + + + true + false + false + true + abcd + reliable + + 53 + 0.1 + + -PT2M + Running Early + + BLOCK6765 + RUN7865 + VEH9876555 + + + + HLT0107 + 002 + Library + false + 2004-12-17T09:30:42-00:00 + 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 + 2004-12-17T09:55:47-05:00 + + reliable + 0.9 + 2004-12-17T09:55:47-05:00 + 2004-12-17T09:58:47-05:00 + + 2004-12-17T09:55:47-05:00 + onTime + Approaching stop + 2 + PT10M + PT11M + 750 + 1 + + + HLTST113 + 0013 + Starbucks + false + 2004-12-17T10:07:47-05:00 + 2004-12-17T10:09:47-05:00 + 2000 + 2 + + + HLTST114 + 0014 + Station + false + 2004-12-17T10:12:47-05:00 + onTime + 2 + 4000 + 3 + + + + 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 + HLTST011 + 123 + Out + What, will the line stretch out to the crack of doom? + + + + 2004-12-17T09:30:47-05:00 + SED9843214675429 + HLTST011 + 123 + Out + + Hello Stop + + + diff --git a/examples/siri_exm_SM/exs_stopMonitoring_response_simple.xml b/examples/siri_exm_SM/exs_stopMonitoring_response_simple.xml index a551c434..a2b72ff4 100644 --- a/examples/siri_exm_SM/exs_stopMonitoring_response_simple.xml +++ b/examples/siri_exm_SM/exs_stopMonitoring_response_simple.xml @@ -1,57 +1,57 @@ - - - - - - 2004-12-17T09:30:46-05:00 - KUBRICK - true - - - 2004-12-17T09:30:47-05:00 - NADER - 2004-12-17T09:30:47-05:00 - HLTST011 - - - 2004-12-17T09:25:46-05:00 - HLTST011 - - 123 - OP22 - Paradise Park - Service running on time - - 2004-12-17T09:42:47-05:00 - 2004-12-17T09:40:47-05:00 - - - - - 2004-12-17T09:25:46-06:00 - HLTST011 - - 128 - Running Early - - true - 2004-12-17T09:42:41-05:00 - 2004-12-17T09:40:41-05:00 - onTime - - - - - 2004-12-17T09:30:47-05:00 - HLTST011 - 123 - Out - Happy Easter to all our customers!? - - - - + + + + + + 2004-12-17T09:30:46-05:00 + KUBRICK + true + + + 2004-12-17T09:30:47-05:00 + NADER + 2004-12-17T09:30:47-05:00 + HLTST011 + + + 2004-12-17T09:25:46-05:00 + HLTST011 + + 123 + OP22 + Paradise Park + Service running on time + + 2004-12-17T09:42:47-05:00 + 2004-12-17T09:40:47-05:00 + + + + + 2004-12-17T09:25:46-06:00 + HLTST011 + + 128 + Running Early + + true + 2004-12-17T09:42:41-05:00 + 2004-12-17T09:40:41-05:00 + onTime + + + + + 2004-12-17T09:30:47-05:00 + HLTST011 + 123 + Out + Happy Easter to all our customers!? + + + + diff --git a/examples/siri_exm_SM/exs_stopMonitoring_subscriptionRequest.xml b/examples/siri_exm_SM/exs_stopMonitoring_subscriptionRequest.xml index 535d9b56..b74658e9 100644 --- a/examples/siri_exm_SM/exs_stopMonitoring_subscriptionRequest.xml +++ b/examples/siri_exm_SM/exs_stopMonitoring_subscriptionRequest.xml @@ -1,65 +1,65 @@ - - - - - 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 - - - + + + + + 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 + + + diff --git a/examples/siri_exm_SM/exs_stopMonitoring_subscriptionRequest_simple.xml b/examples/siri_exm_SM/exs_stopMonitoring_subscriptionRequest_simple.xml index bd736369..31fea846 100644 --- a/examples/siri_exm_SM/exs_stopMonitoring_subscriptionRequest_simple.xml +++ b/examples/siri_exm_SM/exs_stopMonitoring_subscriptionRequest_simple.xml @@ -1,26 +1,26 @@ - - - - - 2004-12-17T09:30:47-05:00 - NADER - - NADER - 000234 - 2004-12-17T09:30:47-05:00 - - 2004-12-17T15:30:47-05:00 - POIT5678 - normal - - false - PT2M - - - + + + + + 2004-12-17T09:30:47-05:00 + NADER + + NADER + 000234 + 2004-12-17T09:30:47-05:00 + + 2004-12-17T15:30:47-05:00 + POIT5678 + normal + + false + PT2M + + + diff --git a/examples/siri_exm_ST/exs_stopTimetable_capabilitiesResponse.xml b/examples/siri_exm_ST/exs_stopTimetable_capabilitiesResponse.xml index 762a7f0d..da1fe67a 100644 --- a/examples/siri_exm_ST/exs_stopTimetable_capabilitiesResponse.xml +++ b/examples/siri_exm_ST/exs_stopTimetable_capabilitiesResponse.xml @@ -1,83 +1,83 @@ - - - - 2001-12-17T09:30:47-05:00 - http://www.mytransportco.eu - true - - - cpidId001 - - Capability supported - - - - - 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 - - - - + + + + 2001-12-17T09:30:47-05:00 + http://www.mytransportco.eu + true + + + cpidId001 + + Capability supported + + + + + 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 + + + + diff --git a/examples/siri_exm_ST/exs_stopTimetable_request.xml b/examples/siri_exm_ST/exs_stopTimetable_request.xml index c1bf679a..2cb11d21 100644 --- a/examples/siri_exm_ST/exs_stopTimetable_request.xml +++ b/examples/siri_exm_ST/exs_stopTimetable_request.xml @@ -1,23 +1,23 @@ - - - - - - 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 - - - + + + + + + 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 + + + diff --git a/examples/siri_exm_ST/exs_stopTimetable_response.xml b/examples/siri_exm_ST/exs_stopTimetable_response.xml index 2b548981..eb1a8ced 100644 --- a/examples/siri_exm_ST/exs_stopTimetable_response.xml +++ b/examples/siri_exm_ST/exs_stopTimetable_response.xml @@ -1,47 +1,47 @@ - - - - - - 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 - - - - - - - + + + + + + 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 + + + + + + + diff --git a/examples/siri_exm_ST/exs_stopTimetable_subscriptionRequest.xml b/examples/siri_exm_ST/exs_stopTimetable_subscriptionRequest.xml index 4ea1d626..b178fd04 100644 --- a/examples/siri_exm_ST/exs_stopTimetable_subscriptionRequest.xml +++ b/examples/siri_exm_ST/exs_stopTimetable_subscriptionRequest.xml @@ -1,26 +1,26 @@ - - - - - 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 - - - - + + + + + 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 + + + + diff --git a/examples/siri_exm_SX/VDV736_exm/SX_1010_first_message.xml b/examples/siri_exm_SX/VDV736_exm/SX_1010_first_message.xml index 51816bee..15e3f0de 100644 --- a/examples/siri_exm_SX/VDV736_exm/SX_1010_first_message.xml +++ b/examples/siri_exm_SX/VDV736_exm/SX_1010_first_message.xml @@ -1,254 +1,254 @@ - - - - 2018-10-04T10:11:00+00:00 - ch:VBL -
      http:/server/siri/20_ums
      - t3xWB5cY3 - true - false - - 2018-10-04T10:11:00+00:00 - ch:VBL - 40599x2dsjmu8yjzy - - - 2017-05-28T10:10:00+02:00 - VBL - 5a7cf4f0-c7a5-11e8-813f-f38697968b53 - 1 - - feed - VBL - - published - - 2017-05-04T10:10:00+02:00 - 2017-05-28T17:10:00+02:00 - - fire - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - 3 - line - false - DE - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - - - ch:vbl:622 - Haldensteig - - - - - - disruption - - - - - ch:vbl:VBL006 - 6 - - - ch:vbl:VBL008 - 8 - - - ch:vbl:VBL024 - 24 - - - - - - - false - - - - - - - line - - - - - ch:vbl:VBL006 - 6 - - - ch:vbl:VBL008 - 8 - - - ch:vbl:VBL024 - 24 - - - ch:pb:PB073 - 73 - - - - - - - open - 0010 - 2017-05-28T10:10:00+02:00 - VBL - VBL - general - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Betroffen sind die Linien 6, 8, 24 und 73 - Affected lines are 6, 8, 24 and 73 - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - Es muss mit Verspätungen, Ausfällen und Umleitungen gerechnet werden. Wir werden sie rasch möglichst detaillierter informieren. - Expect delays, cancellations and diversions. More details to come soon. - - - - - - - line - - - - - ch:vbl:VBL006 - 6 - - - ch:vbl:VBL008 - 8 - - - ch:vbl:VBL024 - 24 - - - ch:pb:PB073 - 73 - - - - - - - open - 0010 - 2017-05-28T10:10:00+02:00 - VBL - VBL - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Betroffen sind die Linien 6, 8, 24 und 73 - Affected lines are 6, 8, 24 and 73 - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - Es muss mit Verspätungen, Ausfällen und Umleitungen gerechnet werden. Wir werden sie rasch möglichst detaillierter informieren. - Expect delays, cancellations and diversions. More details to come soon. - - - - - - - line - - - - - ch:vbl:VBL006 - 6 - - - ch:vbl:VBL008 - 8 - - - ch:vbl:VBL024 - 24 - - - ch:pb:PB073 - 73 - - - - - - - open - 0010 - 2017-05-28T10:10:00+02:00 - VBL - VBL - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Betroffen sind die Linien 6, 8, 24 und 73 - Affected lines are 6, 8, 24 and 73 - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - Es muss mit Verspätungen, Ausfällen und Umleitungen gerechnet werden. Wir werden sie rasch möglichst detaillierter informieren. - Expect delays, cancellations and diversions. More details to come soon. - - - - - - - - -       -       + + + + 2018-10-04T10:11:00+00:00 + ch:VBL +
      http:/server/siri/20_ums
      + t3xWB5cY3 + true + false + + 2018-10-04T10:11:00+00:00 + ch:VBL + 40599x2dsjmu8yjzy + + + 2017-05-28T10:10:00+02:00 + VBL + 5a7cf4f0-c7a5-11e8-813f-f38697968b53 + 1 + + feed + VBL + + published + + 2017-05-04T10:10:00+02:00 + 2017-05-28T17:10:00+02:00 + + fire + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + 3 + line + false + DE + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + + + ch:vbl:622 + Haldensteig + + + + + + disruption + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 24 + + + + + + + false + + + + + + + line + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 24 + + + ch:pb:PB073 + 73 + + + + + + + open + 0010 + 2017-05-28T10:10:00+02:00 + VBL + VBL + general + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Betroffen sind die Linien 6, 8, 24 und 73 + Affected lines are 6, 8, 24 and 73 + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + Es muss mit Verspätungen, Ausfällen und Umleitungen gerechnet werden. Wir werden sie rasch möglichst detaillierter informieren. + Expect delays, cancellations and diversions. More details to come soon. + + + + + + + line + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 24 + + + ch:pb:PB073 + 73 + + + + + + + open + 0010 + 2017-05-28T10:10:00+02:00 + VBL + VBL + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Betroffen sind die Linien 6, 8, 24 und 73 + Affected lines are 6, 8, 24 and 73 + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + Es muss mit Verspätungen, Ausfällen und Umleitungen gerechnet werden. Wir werden sie rasch möglichst detaillierter informieren. + Expect delays, cancellations and diversions. More details to come soon. + + + + + + + line + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 24 + + + ch:pb:PB073 + 73 + + + + + + + open + 0010 + 2017-05-28T10:10:00+02:00 + VBL + VBL + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Betroffen sind die Linien 6, 8, 24 und 73 + Affected lines are 6, 8, 24 and 73 + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + Es muss mit Verspätungen, Ausfällen und Umleitungen gerechnet werden. Wir werden sie rasch möglichst detaillierter informieren. + Expect delays, cancellations and diversions. More details to come soon. + + + + + + + + +       +       diff --git a/examples/siri_exm_SX/VDV736_exm/SX_1022_main_message.xml b/examples/siri_exm_SX/VDV736_exm/SX_1022_main_message.xml index 732fe82d..5c5cd448 100644 --- a/examples/siri_exm_SX/VDV736_exm/SX_1022_main_message.xml +++ b/examples/siri_exm_SX/VDV736_exm/SX_1022_main_message.xml @@ -1,2311 +1,2311 @@ - - - - 2018-10-16T10:22:30+00:00 - ch:VBL -
      http:/server/siri/20_ums
      - Pgfkw0GAsg - true - false - - 2018-10-16T10:22:30+00:00 - ch:VBL - 40599x2dsjmu8yjzy - - - 2017-05-28T10:22:00+02:00 - VBL - 5a7cf4f0-c7a5-11e8-813f-f38697968b53 - 2 - - feed - VBL - - published - - 2017-05-28T10:10:00+02:00 - 2017-05-28T17:10:00+02:00 - - fire - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - 3 - route - DE - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - http://www.vbl.ch/aktuelles/verkehrsmeldungen/stoerungen/20160603_13? - - - - - - - - ch:vbl:622 - Haldensteig - - - - - - disruption - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:2507::01 - Büttenhalde - - - ch:vbl:VBL006:A - Büttenhalde - - - - ch:vbl:621::01 - Casino-Palace - affectedStopplace - - - ch:vbl:615::01 - Europe - affectedStopplace - - - ch:vbl:616::01 - Dietschiberg - affectedStopplace - - - ch:vbl:617::01 - Verkehrshaus - affectedStopplace - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:601:01 - Matthof - - - ch:vbl:VBL006:B - Matthof - - - - ch:vbl:617::02 - Verkehrshaus - affectedStopplace - - - ch:vbl:616::02 - Dietschiberg - affectedStopplace - - - ch:vbl:615::02 - Europe - affectedStopplace - - - ch:vbl:621::02 - Casino-Palace - affectedStopplace - - - ch:vbl:622::02 - Haldensteig - affectedStopplace - - - - - ch:vbl:VBL008 - 8 - - ch:vbl:620:01 - Würzenbach - - - ch:vbl:VBL008:A - Würzenbach - - - - ch:vbl:621::01 - Casino-Palace - affectedStopplace - - - ch:vbl:615::01 - Europe - affectedStopplace - - - ch:vbl:616::01 - Dietschiberg - affectedStopplace - - - ch:vbl:617::01 - Verkehrshaus - affectedStopplace - - - - - ch:vbl:VBL008 - 8 - - ch:vbl:801:01 - Hirtenhof - - - ch:vbl:VBL008:B - Hirtenhof - - - - ch:vbl:617::02 - Verkehrshaus - affectedStopplace - - - ch:vbl:616::02 - Dietschiberg - affectedStopplace - - - ch:vbl:615::02 - Europe - affectedStopplace - - - ch:vbl:621::02 - Casino-Palace - affectedStopplace - - - ch:vbl:622::02 - Haldensteig - affectedStopplace - - - - - - - - true - true - - - - diverted - - - - - ch:vbl:VBL024 - 24 - - ch:vbl:2433:01 - Tschädigen - - - ch:vbl:VBL024:A - Tschädigen - - - - ch:vbl:121::02 - affectedStopplace - - - ch:vbl:621::01 - Casino-Palace - affectedStopplace - - - ch:vbl:617::01 - Verkehrshaus - affectedStopplace - - - ch:vbl:715::01 - intermediate - - - ch:vbl:716::01 - intermediate - - - ch:vbl:1405::01 - intermediate - - - ch:vbl:1406::01 - intermediate - - - ch:vbl:1407::01 - intermediate - - - ch:vbl:1408::01 - intermediate - - - ch:vbl:1409::01 - intermediate - - - ch:vbl:1410::01 - intermediate - - - ch:vbl:1411::01 - intermediate - - - ch:vbl:1412::01 - intermediate - - - - - ch:vbl:VBL024 - 24 - - ch:vbl:119:13 - Bahnhof - - - ch:vbl:VBL024:B - Bahnhof - - - - ch:vbl:617::02 - Verkehrshaus - affectedStopplace - - - ch:vbl:621::02 - affectedStopplace - - - ch:vbl:622::02 - affectedStopplace - - - ch:vbl:1412::02 - intermediate - - - ch:vbl:1411::02 - intermediate - - - ch:vbl:1410::02 - intermediate - - - ch:vbl:1409::02 - intermediate - - - ch:vbl:1408::02 - intermediate - - - ch:vbl:1407::02 - intermediate - - - ch:vbl:1406::02 - intermediate - - - ch:vbl:1405::02 - intermediate - - - ch:vbl:716::02 - intermediate - - - ch:vbl:715::01 - intermediate - - - - - - - - true - true - - - PT7M - - - - - - - line - - - - - ch:vbl:VBL006 - 6 - - - ch:vbl:VBL008 - 8 - - - ch:vbl:VBL024 - 24 - - - ch:pb:PB073 - 73 - - - - - - - open - 0020 - 2017-05-28T10:22:00+02:00 - 1 - vbl - general - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Betroffen sind die Linien 6,8, 24 und 73 - Affected lines are 6, 8, 24 and 73 - - - Linie 6 und 8 fallen zwischen Luzernerhof und Brüelstrasse aus. - Linie 24 wird zwischen Luzernerhof und Brüelstrasse via St. Anna umgeleitet. Ca. 7 Min. längere Fahrzeit. - Linie 73 wird zwischen Luzernerhof und Brüelstrasse via St. Anna umgeleitet. Ca. 6 Min. längere Fahrzeit. - Line 6 and 8 disrupted Luzernerhof and Brüelstrasse. - Line 24 diverted between Luzernerhof and Brüelstrasse via St. Anna. Approx. 7 min delay. - Line 73 diverted between Luzernerhof and Brüelstrasse via St. Anna. Approx. 6 min delay. - - - Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. - Zwischen Luzern, Bahnhof und Verkehrshaus benutzen sie die S3 oder das Schiff. - Umstiegsempfehlung für die Linien 6 und 8: Bei den Haltestellen Luzernerhof bzw. Brüelstrasse auf die umgeleiteten Linien 24 und 73, die normal verkehrende Linie 14 oder den Entlastungsbus umsteigen. - Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. - Between Luzern, Bahnhof and Verkehrshaus use the S3 or ferry. - Transfer advice for line 6 and 8: At Luzernerhof or Brüelstrasse use diverted line 24, 73, additional buses or the regular line 14 services. - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:A - Büttenenhalde - - - - ch:vbl:601::01 - Matthof - - - ch:vbl:602::01 - Schönbühl - - - ch:vbl:603::03 - Wartegg - - - ch:vbl:604::01 - Eisfeldstrasse - - - ch:vbl:605::01 - Weinbergli - - - ch:vbl:606::01 - Werkhofstrasse - - - ch:vbl:407::02 - Bundesplatz - - - ch:vbl:118::01 - Kantonalbank (C) - - - ch:vbl:119::02 - Bahnhof (B) - - - ch:vbl:120:01 - Schwanenplatz - - - - - - - - - open - 0030 - 2017-05-28T10:22:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Die Linie 6 fällt zwischen Luzernerhof und Brüelstrasse aus. - Line 6 cancelled between Luzernerhof and Brüelstrasse. - - - Reisende nach Brüelstrasse und weiter benützen die umgeleitete Linie 24 und 73 (ohne Halte zwischen Wey und Brühlstrasse) oder die normal verkehrende Linie 14 (mit Halten) und steigen an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. - Travellers to Brüelstrasse or further use the diverted line 24, 73 (direct between Wey and Brühlstrasse) or the regular line 14 services (all stop) and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - - - open - 0040 - 2017-05-28T10:22:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Die Linie 6 fällt zwischen Luzernerhof und Brüelstrasse aus. - Line 6 cancelled between Luzernerhof and Brüelstrasse. - - - Reisende nach Brüelstrasse und weiter benützen die umgeleitete Linie 24 und 73 (ohne Halte zwischen Wey und Brühlstrasse) oder die normal verkehrende Linie 14 (mit Halten) und steigen an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. - Travellers to Brüelstrasse or further use the diverted line 24, 73 (direct between Wey and Brühlstrasse) or the regular line 14 services (all stop) and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - Weitere Informationen erhalten Sie unter www.vbl.ch/stoerung/haldenstrasse - For further information, please visit www.vbl.ch/stoerung/haldenstrasse - - - www.vbl.ch/stoerung/haldenstrasse - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:A - Büttenenhalde - - - - ch:vbl:121::02 - Luzernerhof (D) - - - - - - - - - open - 0050 - 2017-05-28T10:22:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Linie 6 wendet hier - Line 6 turns here - - - Reisende zur Brühlstrasse und weiter benützen die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte zwischen Wey und Brühlstrasse) oder die normale verkehrende Linie 14 (mit Halten) ab Kante F (Wey) und steigen an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. - Travellers to Brüelstrasse or further use the diverted line 24, 73, additonal buses (direct between Wey and Brühlstrasse) or the regular line 14 services (all stop) from platform F (Wey) and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:A - Büttenenhalde - - - - ch:vbl:121::01 - Luzernerhof (C) - - - - - ch:vbl:VBL008 - 8 - - ch:vbl:VBL008:A - Würzenbach - - - - ch:vbl:121::01 - Luzernerhof (C) - - - - - - - - - open - 0060 - 2017-05-28T10:22:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Unterbruch der Linien 6 und 8 - Line 6 and 8 disrupted - - - Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die umgeleiteten Linien 24 und 73, die normal verkehrende Linie 14 oder den Entlastungsbus ab Kante F (Wey) und steigen Sie an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. - Transfer advice line 6 and 8: Use diverted line 24, 73, the regular line 14 services or the additional buses to Brüelstrasse and transfer back to line 6 and 8. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - Weitere Informationen erhalten Sie beim Auskunftspersonal. - For further information, please contact staff. - - - - - - - route - - - - - - ch:vbl:VBL014 - 14 - - ch:vbl:VBL014:A - Brüelstrasse - - - - ch:vbl:715::02 - Wey - - - - - ch:vbl:VBL024 - 24 - - ch:vbl:VBL024:A - Tschädingen - - - - ch:vbl:715::02 - Wey - - - - - ch:vbl:VBL073 - 73 - - - ch:vbl:715::02 - Wey - - - - - - - - - - open - 0070 - 2017-05-28T10:22:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Unterbruch der Linien 6 und 8; Umleitung der Linien 24 und 73 - Line 6 and 8 disrupted; Line 24 and 73 diverted - - - Benutzen Sie die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte bis Brühlstrasse) oder die normal verkehrende Linie 14 (mit Halten) bis Brüelstrasse. - Use the diverted line 24, 73, additional buses (direct to Brühlstrasse) or the regular line 14 services (all stops) to Brüelstrasse. - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:A - Büttenenhalde - - - - ch:vbl:121::02 - Luzernerhof (D) - - - - - ch:vbl:VBL008 - 8 - - ch:vbl:VBL008:A - Würzenbach - - - - ch:vbl:121::02 - Luzernerhof (D) - - - - - - - - - open - 0130 - 2017-05-28T10:22:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Linie 6 und 8 fallen bis Brüelstrasse aus. Linie 24 wird zwischen Luzernerhof und Brüelstrasse via St. Anna umgeleitet. Ca. 7 Min. längere Fahrzeit. Linie 73 wird zwischen Luzernerhof und Brüelstrasse via St. Anna umgeleitet. Ca. 6 Min. längere Fahrzeit. - Line 6 and 8 services cancelled to Brüelstrasse. Line 24 services diverted between Luzernerhof and Brüelstrasse via St. Anna. Approx. 7 min. delay. Line 73 services diverted between Luzernerhof and Brüelstrasse. Approx. 6 min delay. - - - Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte zwischen Wey und Brühlstrasse) oder die normale verkehrende Linie 14 (mit Halten) ab Kante F (Wey) und steigen Sie an der Brüelstrasse um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. - Transfer advice for line 6 and 8: To Brüelstrasse use diverted line 24, 73, additional buses (direct between Wey and Brühlstrasse) or the regular line 14 services (all stops) from platform F (Way) and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:A - Büttenenhalde - - - - ch:vbl:621::01 - Casino-Palace - - - ch:vbl:615::01 - Europe - - - ch:vbl:616::01 - Dietschiberg - - - ch:vbl:617::01 - Verkehrshaus - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:B - Matthof - - - - ch:vbl:617::02 - Verkehrshaus - - - ch:vbl:616::02 - Dietschiberg - - - ch:vbl:615::02 - Europe - - - ch:vbl:621::02 - Casino-Palace - - - ch:vbl:622::01 - Haldensteig - - - - - ch:vbl:VBL008 - 8 - - ch:vbl:VBL008:A - Würzenbach - - - - ch:vbl:621::01 - Casino-Palace - - - ch:vbl:615::01 - Europe - - - ch:vbl:616::01 - Dietschiberg - - - ch:vbl:617::01 - Verkehrshaus - - - - - ch:vbl:VBL008 - 8 - - ch:vbl:VBL008:B - Hirtenhof - - - - ch:vbl:617::02 - Verkehrshaus - - - ch:vbl:616::02 - Dietschiberg - - - ch:vbl:615::02 - Europe - - - ch:vbl:621::02 - Casino-Palace - - - ch:vbl:622::01 - Haldensteig - - - - - ch:vbl:VBL024 - 24 - - ch:vbl:VBL024:A - Tschädingen - - - - ch:vbl:621::01 - Casino-Palace - - - ch:vbl:615::01 - Europe - - - ch:vbl:616::01 - Dietschiberg - - - ch:vbl:617::01 - Verkehrshaus - - - - - ch:vbl:VBL024 - 24 - - ch:vbl:VBL024:B - Bahnhof - - - - ch:vbl:617::02 - Verkehrshaus - - - ch:vbl:616::02 - Dietschiberg - - - ch:vbl:615::02 - Europe - - - ch:vbl:621::02 - Casino-Palace - - - ch:vbl:622::01 - Haldensteig - - - - - ch:pb:PB073 - 73 - - - ch:vbl:621::01 - Casino-Palace - - - ch:vbl:615::01 - Europe - - - ch:vbl:616::01 - Dietschiberg - - - ch:vbl:617::01 - Verkehrshaus - - - ch:vbl:617::02 - Verkehrshaus - - - ch:vbl:616::02 - Dietschiberg - - - ch:vbl:615::02 - Europe - - - ch:vbl:621::02 - Casino-Palace - - - ch:vbl:622::01 - Haldensteig - - - - - - - - - open - 0140 - 2017-05-28T10:22:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Keine Bedienung der Linien 6, 8, 24 und 73 zwischen Luzernerhof und Brüelstrasse - No service for line 6, 8, 24 and 73 between Luzernerhof and Brüelstrasse - - - Reisende zwischen Luzernerhof und Brüelstrasse erreichen ihr Ziel nur zu Fuß. Ab Luzernerhof und Brüelstrasse verkehren die Linie auf den normalen Fahrwegen. - Travellers between Luzernerhof and Brüelstrasse can only reach their destination on foot. From Luzernerhof and Brüelstrasse lines will run on regular routes. - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - Fällt aus - Cancelled - - - - - - - route - - - - - ch:vbl:014 - 14 - - ch:vbl:VBL014:A - Brüelstrasse - - - - ch:vbl:618::01 - Brüelstrasse - destination - - - - - - - - - open - 0080 - 2017-05-28T10:22:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Einstieg der Linien 6 und 8 bei Kante C. Reisende nach Verkehrshaus und Dietschiberg erreichen ihr Ziel nur zu Fuß. - Board line 6 and 8 from platform C. Travellers to Verkehrshaus and Dietschiberg can only reach their destination on foot. - - - - - - - route - - - - - ch:vbl:024 - 24 - - ch:vbl:VBL024:A - Tschädingen - - - - ch:vbl:618::01 - Brüelstrasse - intermediate - - - - - ch:pb:073 - 73 - - ch:pb:PB073:A - Rotkreuz - - - - ch:vbl:618::04 - Brüelstrasse - destination - - - - - - - - - open - 0090 - 2017-05-28T10:22:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Die Umleitung endet hier - Diversion ends here - - - Umstieg auf Linie 6 und 8: Einstieg bei Kante C. Reisende nach Verkehrshaus und Dietschiberg erreichen ihr Ziel nur zu Fuß. - Transfer to line 6 and 8: Board from platform C. Travellers to Verkehrshaus and Dietschiberg can only reach their destination on foot. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:A - Büttenhalde - - - - ch:vbl:618::03 - Brüelstrasse - - - - - ch:vbl:VBL008 - 8 - - ch:vbl:VBL008:A - Würzenbach - - - - ch:vbl:618::03 - Brüelstrasse - - - - - - - - - open - 0100 - 2017-05-28T10:22:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Normale Bedienung der Linien 6 bis Büttenenhalde und 8 bis Würzenbach. - Regular line 6 services to Büttenenhalde and 8 to Würzenbach. - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - Es muss mit Verspätungen gerechnet werden. - Expect delays. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:A - Büttenhalde - - - - - ch:vbl:618::03 - Brüelstrasse(B) - - - ch:vbl:2502::01 - Giseli - intermediate - - - ch:vbl:2503::01 - Oberseeburg - intermediate - - - ch:vbl:2504::01 - Oberseeburghöhe - intermediate - - - ch:vbl:2505::01 - Eggen - intermediate - - - ch:vbl:2506::01 - Büttenen - intermediate - - - ch:vbl:2507::01 - Büttenenhalde - destination - - - - - ch:vbl:VBL008 - 8 - - ch:vbl:VBL008:A - Würzenbach - - - - - ch:vbl:618::03 - Brüelstrasse(B) - - - ch:vbl:619::01 - Würzenbachmatte - intermediate - - - ch:vbl:620::01 - Würzenbach - destination - - - - - - - - - open - 0110 - 2017-05-28T10:22:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - Es muss mit Verspätungen gerechnet werden. - Expect delays. - - - - - - - route - - - - - ch:vbl:Entlastungsbus - Entlastungsbus - - ch:vbl:VBL006:A - Büttenhalde - - - - ch:vbl:618::04 - Brüelstrasse - - - - - - - - - open - 0120 - 2017-05-28T10:22:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Diese Fahrt endet hier - This service terminates here - - - Einstieg der Linien 6 und 8 bei Kante C. Reisende nach Verkehrshaus und Dietschiberg erreichen ihr Ziel nur zu Fuß. - Board line 6 and 8 from platform C. Travellers to Verkehrshaus and Dietschiberg can only reach their destination on foot. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:B - Matthof - - - - ch:vbl:2507::01 - Büttenenhalde - origin - - - ch:vbl:2506::02 - Büttenen - intermediate - - - ch:vbl:2505::02 - Eggen - intermediate - - - ch:vbl:2504::02 - Oberseeburghöhe - intermediate - - - ch:vbl:2503::02 - Oberseeburg - intermediate - - - ch:vbl:2502::02 - Giseli - intermediate - - - - - - - - - open - 0150 - 2017-05-28T10:22:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Die Linie 6 fällt zwischen Brüelstrasse und Luzernerhof aus. - Line 6 cancelled between Brüelstrasse and Luzernerhof. - - - Reisende nach Luzernerhof oder weiter benützen die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte zwischen Brühlstrasse und Luzernerhof) oder die normal verkehrende Linie 14 (mit Halten) bis Luzernerhof und steigen dort wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. - Travellers to Luzernerhof or further use the diverted lines 24, 73 and the additional bus (direct between Brühlstrasse and Luzernerhof) or the regular line 14 services (all stop) to Luzernhof and transfer there. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:B - Matthof - - - - ch:vbl:2507::01 - Büttenenhalde - origin - - - ch:vbl:2506::02 - Büttenen - intermediate - - - ch:vbl:2505::02 - Eggen - intermediate - - - ch:vbl:2504::02 - Oberseeburghöhe - intermediate - - - ch:vbl:2503::02 - Oberseeburg - intermediate - - - ch:vbl:2502::02 - Giseli - intermediate - - - - - - - - - open - 0160 - 2017-05-28T10:22:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Die Linie 6 fällt zwischen Brüelstrasse und Luzernerhof aus. - Line 6 cancelled between Brüelstrasse and Luzernerhof. - - - Reisende nach Luzernerhof oder weiter benützen die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte zwischen Brühlstrasse und Luzernerhof) oder die normal verkehrende Linie 14 (mit Halten) bis Luzernerhof und steigen dort wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. - Travellers to Luzernerhof or further use the diverted lines 24, 73 and the additional bus (direct between Brühlstrasse and Luzernerhof) or the regular line 14 services (all stop) to Luzernhof and transfer there. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:B - Matthof - - - - ch:vbl:618::02 - Brüelstrasse - destination - - - - - - - - - open - 0170 - 2017-05-28T10:22:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Linie 6 wendet hier - Line 6 turns here - - - Reisende zum Luzernerhof oder weiter benützen die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte bis Luzernerhof) oder die normal verkehrende Linie 14 (mit Halten) ab Kante D und steigen beim Luzernerhof wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. - Travellers to Luzernerhof or further use the diverted lines 24, 73, addintionl buses (direct to Luzernerhof) or the regular line 14 services (all stops) from platform D and transfer back to line 6 and 8 at Luzernerhof. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:B - Matthof - - - - ch:vbl:618::02 - Brüelstrasse - destination - - - - - ch:vbl:VBL008 - 8 - - ch:vbl:VBL008:B - Hirtenhof - - - - ch:vbl:618::02 - Brüelstrasse - destination - - - - - - - - - open - 0180 - 2017-05-28T10:22:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Unterbruch der Linien 6 und 8 - Line 6 and 8 disrupted - - - Reisende zum Luzernerhof oder weiter benützen die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte bis Luzernerhof) oder die normal verkehrende Linie 14 (mit Halten) ab Kante D und steigen beim Luzernerhof wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. - Travellers to Luzernerhof or further use the diverted lines 24, 73, addintionl buses (direct to Luzernerhof) or the regular line 14 services (all stops) from platform D and transfer back to line 6 and 8 at Luzernerhof. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. - - - - - - - route - - - - - ch:vbl:VBL014 - 14 - - ch:vbl:VBL014:A - Brühlstrasse - - - - ch:vbl:618::04 - Brühlstrasse - destination - - - - - - - ch:vbl:VBL024 - 24 - - ch:vbl:VBL024:B - Bahnhof - - - - ch:vbl:618::04 - Brühlstrasse - destination - - - - - - - - - open - 0190 - 2017-05-28T10:22:00+02:00 - 1 - vbl - stopPoint - - L - - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Unterbruch der Linien 6 und 8; Umleitung der Linien 24 und 73. - Line 6 and 8 disrupted; Line 24 and 73 diverted. - - - Benutzen Sie die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte bis Luzernerhof) oder die normal verkehrende Linie 14 (mit Halten) bis Luzernerhof. - Use diverted line 24, 73, additional buses (direct ot Luzernhof) or the regular line 14 services (all stops) to Luzernhof. - - - - - - - route - - - - - - ch:vbl:VBLEBUS - EBUS - - ch:vbl:VBLEBUS:B - Luzernerhof - - - - ch:vbl:121::xx - Luzernerhof - destination - - - - - - - - - open - 0200 - 2017-05-28T10:22:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Die Umleitung endet hier - Diversion ends here - - - Einstieg der Linien 6 und 8 bei Kante A. Reisende nach Haldensteig, Casino-Palace und Europe erreichen ihr Ziel nur zu Fuß. - Board line 6 and 8 from platform A. Travellers to Haldensteig, Casino-Palace and Europe can only reach their destination on foot. - - - - - - - route - - - - - ch:vbl:VBL014 - 14 - - ch:vbl:VBL014:B - Horw Zentrum - - - - ch:vbl:121::03 - Luzernerhof - intermediate - - - - - - - - - open - 0210 - 2017-05-28T10:22:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Einstieg der Linien 6 und 8 bei Kante A. Reisende nach Haldensteig, Casino-Palace und Europe erreichen ihr Ziel nur zu Fuß. - Board line 6 and 8 from platform A. Travellers to Haldensteig, Casino-Palace and Europe can only reach their destination on foot. - - - - - - - route - - - - - ch:vbl:VBL024 - 24 - - ch:vbl:VBL024:B - Bahnhof - - - - ch:vbl:121::3 - Luzernerhof - origin - - - - - ch:vbl:VBL073 - 73 - - ch:vbl:VBL073:B - Bahnhof - - - - ch:vbl:121::3 - Luzernerhof - origin - - - - - - - - - open - 0215 - 2017-05-28T10:22:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Die Umleitung endet hier - Diversion ends here - - - Einstieg der Linien 6 und 8 bei Kante A. Reisende nach Haldensteig, Casino-Palace und Europe erreichen ihr Ziel nur zu Fuß. - Board line 6 and 8 from platform A. Travellers to Haldensteig, Casino-Palace and Europe can only reach their destination on foot. - - - - - - - route - - - - - ch:vbl:VBL024 - 24 - - ch:vbl:VBL024:B - Bahnhof - - - - ch:vbl:121::3 - Luzernerhof - origin - - - - - - - - - open - 0220 - 2017-05-28T10:22:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Die Umleitung endet hier - Diversion ends here - - - Umstieg auf die Linien 6 und 8: Einstieg bei Kante A. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. - Transfer to line 6 and 8: Board from platform A. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:B - Matthof - - - - ch:vbl:121::04 - Luzernerhof - origin - - - - - ch:vbl:VBL008 - 8 - - ch:vbl:VBL008:B - Hirtenhof - - - - ch:vbl:121::04 - Luzernerhof - origin - - - - - - - - - open - 0230 - 2017-05-28T10:22:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Normale Bedienung der Linien 6 bis Matthof und 8 bis Hirtenhof. - Regular service on line 6 to Matthof and line 8 to Hirtenhof. - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - Es muss mit Verspätungen gerechnet werden. - Expect delays. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:B - Matthof - - - - ch:vbl:120::02 - Schwanenplatz - intermediate - - - ch:vbl:119::01 - Bahnhof - intermediate - - - ch:vbl:118::02 - Kantonalbank - intermediate - - - ch:vbl:407::03 - Bundesplatz - intermediate - - - ch:vbl:606::02 - Werkhofstrasse - intermediate - - - ch:vbl:605::02 - Weinbergli - intermediate - - - ch:vbl:604::02 - Eisfeldstrasse - intermediate - - - ch:vbl:603::02 - Wartegg - intermediate - - - ch:vbl:602::02 - Schönbühl - intermediate - - - ch:vbl:601::01 - Matthof - destination - - - - - - - - - open - 0240 - 2017-05-28T10:22:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Es muss mit Verspätungen gerechnet werden. - Expect delays. - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - - - - - route - - - - - ch:vbl:VBL02A - 2 - - - ch:vbl:119::06 - Luzern Bahnhof - - - - - - - - - open - 0245 - 2017-05-28T10:22:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Unterbruch der Linien 6 und 8 - Line 6 and 8 disrupted - - - Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die umgeleitete Linie 73 oder die normal verkehrende Linie 14 und steigen Sie an der Brüelstrasse wieder um. Reisende nach dem Verkehrshaus benutzen die S3 oder das Schiff. - Transfer advice for line 6 and 8: Use diverted line 73 or the regular line 14 services to Brüelstrasse and transfer back to line 6 and 8. Travellers to Verkehrshaus use the S3 or ferry. - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - - - - - route - - - - - ch:vbl:VBL014A - 14 - - ch:vbl:VBL014:A - Brüelstrasse - - - - ch:vbl:119::08 - Luzern Bahnhof - - - - - - - - - open - 0246 - 2017-05-28T10:22:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Unterbruch der Linien 6 und 8 - Line 6 and 8 disrupted - - - Empfehlung für Linien 6 und 8: Für Fahrten zur Brüelstrasse und weiter bleiben Sie in der Linie 14 und steigen Sie an der Brüelstrasse um. Reisende nach dem Verkehrshaus benutzen ab dem Bahnhof die S3 oder das Schiff. - Advice for line 6 and 8: For services to Brüelstrasse and further, stay on line 14 and transfer at Brüelstrasse. Travellers after Verkehrshaus use the S3 or ferry from main station. - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - - - - - - -       -       + + + + 2018-10-16T10:22:30+00:00 + ch:VBL +
      http:/server/siri/20_ums
      + Pgfkw0GAsg + true + false + + 2018-10-16T10:22:30+00:00 + ch:VBL + 40599x2dsjmu8yjzy + + + 2017-05-28T10:22:00+02:00 + VBL + 5a7cf4f0-c7a5-11e8-813f-f38697968b53 + 2 + + feed + VBL + + published + + 2017-05-28T10:10:00+02:00 + 2017-05-28T17:10:00+02:00 + + fire + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + 3 + route + DE + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + http://www.vbl.ch/aktuelles/verkehrsmeldungen/stoerungen/20160603_13? + + + + + + + + ch:vbl:622 + Haldensteig + + + + + + disruption + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:2507::01 + Büttenhalde + + + ch:vbl:VBL006:A + Büttenhalde + + + + ch:vbl:621::01 + Casino-Palace + affectedStopplace + + + ch:vbl:615::01 + Europe + affectedStopplace + + + ch:vbl:616::01 + Dietschiberg + affectedStopplace + + + ch:vbl:617::01 + Verkehrshaus + affectedStopplace + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:601:01 + Matthof + + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:617::02 + Verkehrshaus + affectedStopplace + + + ch:vbl:616::02 + Dietschiberg + affectedStopplace + + + ch:vbl:615::02 + Europe + affectedStopplace + + + ch:vbl:621::02 + Casino-Palace + affectedStopplace + + + ch:vbl:622::02 + Haldensteig + affectedStopplace + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:620:01 + Würzenbach + + + ch:vbl:VBL008:A + Würzenbach + + + + ch:vbl:621::01 + Casino-Palace + affectedStopplace + + + ch:vbl:615::01 + Europe + affectedStopplace + + + ch:vbl:616::01 + Dietschiberg + affectedStopplace + + + ch:vbl:617::01 + Verkehrshaus + affectedStopplace + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:801:01 + Hirtenhof + + + ch:vbl:VBL008:B + Hirtenhof + + + + ch:vbl:617::02 + Verkehrshaus + affectedStopplace + + + ch:vbl:616::02 + Dietschiberg + affectedStopplace + + + ch:vbl:615::02 + Europe + affectedStopplace + + + ch:vbl:621::02 + Casino-Palace + affectedStopplace + + + ch:vbl:622::02 + Haldensteig + affectedStopplace + + + + + + + + true + true + + + + diverted + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:2433:01 + Tschädigen + + + ch:vbl:VBL024:A + Tschädigen + + + + ch:vbl:121::02 + affectedStopplace + + + ch:vbl:621::01 + Casino-Palace + affectedStopplace + + + ch:vbl:617::01 + Verkehrshaus + affectedStopplace + + + ch:vbl:715::01 + intermediate + + + ch:vbl:716::01 + intermediate + + + ch:vbl:1405::01 + intermediate + + + ch:vbl:1406::01 + intermediate + + + ch:vbl:1407::01 + intermediate + + + ch:vbl:1408::01 + intermediate + + + ch:vbl:1409::01 + intermediate + + + ch:vbl:1410::01 + intermediate + + + ch:vbl:1411::01 + intermediate + + + ch:vbl:1412::01 + intermediate + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:119:13 + Bahnhof + + + ch:vbl:VBL024:B + Bahnhof + + + + ch:vbl:617::02 + Verkehrshaus + affectedStopplace + + + ch:vbl:621::02 + affectedStopplace + + + ch:vbl:622::02 + affectedStopplace + + + ch:vbl:1412::02 + intermediate + + + ch:vbl:1411::02 + intermediate + + + ch:vbl:1410::02 + intermediate + + + ch:vbl:1409::02 + intermediate + + + ch:vbl:1408::02 + intermediate + + + ch:vbl:1407::02 + intermediate + + + ch:vbl:1406::02 + intermediate + + + ch:vbl:1405::02 + intermediate + + + ch:vbl:716::02 + intermediate + + + ch:vbl:715::01 + intermediate + + + + + + + + true + true + + + PT7M + + + + + + + line + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 24 + + + ch:pb:PB073 + 73 + + + + + + + open + 0020 + 2017-05-28T10:22:00+02:00 + 1 + vbl + general + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Betroffen sind die Linien 6,8, 24 und 73 + Affected lines are 6, 8, 24 and 73 + + + Linie 6 und 8 fallen zwischen Luzernerhof und Brüelstrasse aus. + Linie 24 wird zwischen Luzernerhof und Brüelstrasse via St. Anna umgeleitet. Ca. 7 Min. längere Fahrzeit. + Linie 73 wird zwischen Luzernerhof und Brüelstrasse via St. Anna umgeleitet. Ca. 6 Min. längere Fahrzeit. + Line 6 and 8 disrupted Luzernerhof and Brüelstrasse. + Line 24 diverted between Luzernerhof and Brüelstrasse via St. Anna. Approx. 7 min delay. + Line 73 diverted between Luzernerhof and Brüelstrasse via St. Anna. Approx. 6 min delay. + + + Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Zwischen Luzern, Bahnhof und Verkehrshaus benutzen sie die S3 oder das Schiff. + Umstiegsempfehlung für die Linien 6 und 8: Bei den Haltestellen Luzernerhof bzw. Brüelstrasse auf die umgeleiteten Linien 24 und 73, die normal verkehrende Linie 14 oder den Entlastungsbus umsteigen. + Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + Between Luzern, Bahnhof and Verkehrshaus use the S3 or ferry. + Transfer advice for line 6 and 8: At Luzernerhof or Brüelstrasse use diverted line 24, 73, additional buses or the regular line 14 services. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:A + Büttenenhalde + + + + ch:vbl:601::01 + Matthof + + + ch:vbl:602::01 + Schönbühl + + + ch:vbl:603::03 + Wartegg + + + ch:vbl:604::01 + Eisfeldstrasse + + + ch:vbl:605::01 + Weinbergli + + + ch:vbl:606::01 + Werkhofstrasse + + + ch:vbl:407::02 + Bundesplatz + + + ch:vbl:118::01 + Kantonalbank (C) + + + ch:vbl:119::02 + Bahnhof (B) + + + ch:vbl:120:01 + Schwanenplatz + + + + + + + + + open + 0030 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Linie 6 fällt zwischen Luzernerhof und Brüelstrasse aus. + Line 6 cancelled between Luzernerhof and Brüelstrasse. + + + Reisende nach Brüelstrasse und weiter benützen die umgeleitete Linie 24 und 73 (ohne Halte zwischen Wey und Brühlstrasse) oder die normal verkehrende Linie 14 (mit Halten) und steigen an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Travellers to Brüelstrasse or further use the diverted line 24, 73 (direct between Wey and Brühlstrasse) or the regular line 14 services (all stop) and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + + + open + 0040 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Linie 6 fällt zwischen Luzernerhof und Brüelstrasse aus. + Line 6 cancelled between Luzernerhof and Brüelstrasse. + + + Reisende nach Brüelstrasse und weiter benützen die umgeleitete Linie 24 und 73 (ohne Halte zwischen Wey und Brühlstrasse) oder die normal verkehrende Linie 14 (mit Halten) und steigen an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Travellers to Brüelstrasse or further use the diverted line 24, 73 (direct between Wey and Brühlstrasse) or the regular line 14 services (all stop) and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + Weitere Informationen erhalten Sie unter www.vbl.ch/stoerung/haldenstrasse + For further information, please visit www.vbl.ch/stoerung/haldenstrasse + + + www.vbl.ch/stoerung/haldenstrasse + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:A + Büttenenhalde + + + + ch:vbl:121::02 + Luzernerhof (D) + + + + + + + + + open + 0050 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Linie 6 wendet hier + Line 6 turns here + + + Reisende zur Brühlstrasse und weiter benützen die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte zwischen Wey und Brühlstrasse) oder die normale verkehrende Linie 14 (mit Halten) ab Kante F (Wey) und steigen an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Travellers to Brüelstrasse or further use the diverted line 24, 73, additonal buses (direct between Wey and Brühlstrasse) or the regular line 14 services (all stop) from platform F (Wey) and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:A + Büttenenhalde + + + + ch:vbl:121::01 + Luzernerhof (C) + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:A + Würzenbach + + + + ch:vbl:121::01 + Luzernerhof (C) + + + + + + + + + open + 0060 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8 + Line 6 and 8 disrupted + + + Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die umgeleiteten Linien 24 und 73, die normal verkehrende Linie 14 oder den Entlastungsbus ab Kante F (Wey) und steigen Sie an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Transfer advice line 6 and 8: Use diverted line 24, 73, the regular line 14 services or the additional buses to Brüelstrasse and transfer back to line 6 and 8. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + Weitere Informationen erhalten Sie beim Auskunftspersonal. + For further information, please contact staff. + + + + + + + route + + + + + + ch:vbl:VBL014 + 14 + + ch:vbl:VBL014:A + Brüelstrasse + + + + ch:vbl:715::02 + Wey + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:VBL024:A + Tschädingen + + + + ch:vbl:715::02 + Wey + + + + + ch:vbl:VBL073 + 73 + + + ch:vbl:715::02 + Wey + + + + + + + + + + open + 0070 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8; Umleitung der Linien 24 und 73 + Line 6 and 8 disrupted; Line 24 and 73 diverted + + + Benutzen Sie die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte bis Brühlstrasse) oder die normal verkehrende Linie 14 (mit Halten) bis Brüelstrasse. + Use the diverted line 24, 73, additional buses (direct to Brühlstrasse) or the regular line 14 services (all stops) to Brüelstrasse. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:A + Büttenenhalde + + + + ch:vbl:121::02 + Luzernerhof (D) + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:A + Würzenbach + + + + ch:vbl:121::02 + Luzernerhof (D) + + + + + + + + + open + 0130 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Linie 6 und 8 fallen bis Brüelstrasse aus. Linie 24 wird zwischen Luzernerhof und Brüelstrasse via St. Anna umgeleitet. Ca. 7 Min. längere Fahrzeit. Linie 73 wird zwischen Luzernerhof und Brüelstrasse via St. Anna umgeleitet. Ca. 6 Min. längere Fahrzeit. + Line 6 and 8 services cancelled to Brüelstrasse. Line 24 services diverted between Luzernerhof and Brüelstrasse via St. Anna. Approx. 7 min. delay. Line 73 services diverted between Luzernerhof and Brüelstrasse. Approx. 6 min delay. + + + Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte zwischen Wey und Brühlstrasse) oder die normale verkehrende Linie 14 (mit Halten) ab Kante F (Wey) und steigen Sie an der Brüelstrasse um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Transfer advice for line 6 and 8: To Brüelstrasse use diverted line 24, 73, additional buses (direct between Wey and Brühlstrasse) or the regular line 14 services (all stops) from platform F (Way) and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:A + Büttenenhalde + + + + ch:vbl:621::01 + Casino-Palace + + + ch:vbl:615::01 + Europe + + + ch:vbl:616::01 + Dietschiberg + + + ch:vbl:617::01 + Verkehrshaus + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:617::02 + Verkehrshaus + + + ch:vbl:616::02 + Dietschiberg + + + ch:vbl:615::02 + Europe + + + ch:vbl:621::02 + Casino-Palace + + + ch:vbl:622::01 + Haldensteig + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:A + Würzenbach + + + + ch:vbl:621::01 + Casino-Palace + + + ch:vbl:615::01 + Europe + + + ch:vbl:616::01 + Dietschiberg + + + ch:vbl:617::01 + Verkehrshaus + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:B + Hirtenhof + + + + ch:vbl:617::02 + Verkehrshaus + + + ch:vbl:616::02 + Dietschiberg + + + ch:vbl:615::02 + Europe + + + ch:vbl:621::02 + Casino-Palace + + + ch:vbl:622::01 + Haldensteig + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:VBL024:A + Tschädingen + + + + ch:vbl:621::01 + Casino-Palace + + + ch:vbl:615::01 + Europe + + + ch:vbl:616::01 + Dietschiberg + + + ch:vbl:617::01 + Verkehrshaus + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:VBL024:B + Bahnhof + + + + ch:vbl:617::02 + Verkehrshaus + + + ch:vbl:616::02 + Dietschiberg + + + ch:vbl:615::02 + Europe + + + ch:vbl:621::02 + Casino-Palace + + + ch:vbl:622::01 + Haldensteig + + + + + ch:pb:PB073 + 73 + + + ch:vbl:621::01 + Casino-Palace + + + ch:vbl:615::01 + Europe + + + ch:vbl:616::01 + Dietschiberg + + + ch:vbl:617::01 + Verkehrshaus + + + ch:vbl:617::02 + Verkehrshaus + + + ch:vbl:616::02 + Dietschiberg + + + ch:vbl:615::02 + Europe + + + ch:vbl:621::02 + Casino-Palace + + + ch:vbl:622::01 + Haldensteig + + + + + + + + + open + 0140 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Keine Bedienung der Linien 6, 8, 24 und 73 zwischen Luzernerhof und Brüelstrasse + No service for line 6, 8, 24 and 73 between Luzernerhof and Brüelstrasse + + + Reisende zwischen Luzernerhof und Brüelstrasse erreichen ihr Ziel nur zu Fuß. Ab Luzernerhof und Brüelstrasse verkehren die Linie auf den normalen Fahrwegen. + Travellers between Luzernerhof and Brüelstrasse can only reach their destination on foot. From Luzernerhof and Brüelstrasse lines will run on regular routes. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + Fällt aus + Cancelled + + + + + + + route + + + + + ch:vbl:014 + 14 + + ch:vbl:VBL014:A + Brüelstrasse + + + + ch:vbl:618::01 + Brüelstrasse + destination + + + + + + + + + open + 0080 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Einstieg der Linien 6 und 8 bei Kante C. Reisende nach Verkehrshaus und Dietschiberg erreichen ihr Ziel nur zu Fuß. + Board line 6 and 8 from platform C. Travellers to Verkehrshaus and Dietschiberg can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:024 + 24 + + ch:vbl:VBL024:A + Tschädingen + + + + ch:vbl:618::01 + Brüelstrasse + intermediate + + + + + ch:pb:073 + 73 + + ch:pb:PB073:A + Rotkreuz + + + + ch:vbl:618::04 + Brüelstrasse + destination + + + + + + + + + open + 0090 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Umleitung endet hier + Diversion ends here + + + Umstieg auf Linie 6 und 8: Einstieg bei Kante C. Reisende nach Verkehrshaus und Dietschiberg erreichen ihr Ziel nur zu Fuß. + Transfer to line 6 and 8: Board from platform C. Travellers to Verkehrshaus and Dietschiberg can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:A + Büttenhalde + + + + ch:vbl:618::03 + Brüelstrasse + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:A + Würzenbach + + + + ch:vbl:618::03 + Brüelstrasse + + + + + + + + + open + 0100 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Normale Bedienung der Linien 6 bis Büttenenhalde und 8 bis Würzenbach. + Regular line 6 services to Büttenenhalde and 8 to Würzenbach. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + Es muss mit Verspätungen gerechnet werden. + Expect delays. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:A + Büttenhalde + + + + + ch:vbl:618::03 + Brüelstrasse(B) + + + ch:vbl:2502::01 + Giseli + intermediate + + + ch:vbl:2503::01 + Oberseeburg + intermediate + + + ch:vbl:2504::01 + Oberseeburghöhe + intermediate + + + ch:vbl:2505::01 + Eggen + intermediate + + + ch:vbl:2506::01 + Büttenen + intermediate + + + ch:vbl:2507::01 + Büttenenhalde + destination + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:A + Würzenbach + + + + + ch:vbl:618::03 + Brüelstrasse(B) + + + ch:vbl:619::01 + Würzenbachmatte + intermediate + + + ch:vbl:620::01 + Würzenbach + destination + + + + + + + + + open + 0110 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + Es muss mit Verspätungen gerechnet werden. + Expect delays. + + + + + + + route + + + + + ch:vbl:Entlastungsbus + Entlastungsbus + + ch:vbl:VBL006:A + Büttenhalde + + + + ch:vbl:618::04 + Brüelstrasse + + + + + + + + + open + 0120 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Diese Fahrt endet hier + This service terminates here + + + Einstieg der Linien 6 und 8 bei Kante C. Reisende nach Verkehrshaus und Dietschiberg erreichen ihr Ziel nur zu Fuß. + Board line 6 and 8 from platform C. Travellers to Verkehrshaus and Dietschiberg can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:2507::01 + Büttenenhalde + origin + + + ch:vbl:2506::02 + Büttenen + intermediate + + + ch:vbl:2505::02 + Eggen + intermediate + + + ch:vbl:2504::02 + Oberseeburghöhe + intermediate + + + ch:vbl:2503::02 + Oberseeburg + intermediate + + + ch:vbl:2502::02 + Giseli + intermediate + + + + + + + + + open + 0150 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Linie 6 fällt zwischen Brüelstrasse und Luzernerhof aus. + Line 6 cancelled between Brüelstrasse and Luzernerhof. + + + Reisende nach Luzernerhof oder weiter benützen die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte zwischen Brühlstrasse und Luzernerhof) oder die normal verkehrende Linie 14 (mit Halten) bis Luzernerhof und steigen dort wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. + Travellers to Luzernerhof or further use the diverted lines 24, 73 and the additional bus (direct between Brühlstrasse and Luzernerhof) or the regular line 14 services (all stop) to Luzernhof and transfer there. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:2507::01 + Büttenenhalde + origin + + + ch:vbl:2506::02 + Büttenen + intermediate + + + ch:vbl:2505::02 + Eggen + intermediate + + + ch:vbl:2504::02 + Oberseeburghöhe + intermediate + + + ch:vbl:2503::02 + Oberseeburg + intermediate + + + ch:vbl:2502::02 + Giseli + intermediate + + + + + + + + + open + 0160 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Linie 6 fällt zwischen Brüelstrasse und Luzernerhof aus. + Line 6 cancelled between Brüelstrasse and Luzernerhof. + + + Reisende nach Luzernerhof oder weiter benützen die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte zwischen Brühlstrasse und Luzernerhof) oder die normal verkehrende Linie 14 (mit Halten) bis Luzernerhof und steigen dort wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. + Travellers to Luzernerhof or further use the diverted lines 24, 73 and the additional bus (direct between Brühlstrasse and Luzernerhof) or the regular line 14 services (all stop) to Luzernhof and transfer there. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:618::02 + Brüelstrasse + destination + + + + + + + + + open + 0170 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Linie 6 wendet hier + Line 6 turns here + + + Reisende zum Luzernerhof oder weiter benützen die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte bis Luzernerhof) oder die normal verkehrende Linie 14 (mit Halten) ab Kante D und steigen beim Luzernerhof wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. + Travellers to Luzernerhof or further use the diverted lines 24, 73, addintionl buses (direct to Luzernerhof) or the regular line 14 services (all stops) from platform D and transfer back to line 6 and 8 at Luzernerhof. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:618::02 + Brüelstrasse + destination + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:B + Hirtenhof + + + + ch:vbl:618::02 + Brüelstrasse + destination + + + + + + + + + open + 0180 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8 + Line 6 and 8 disrupted + + + Reisende zum Luzernerhof oder weiter benützen die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte bis Luzernerhof) oder die normal verkehrende Linie 14 (mit Halten) ab Kante D und steigen beim Luzernerhof wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. + Travellers to Luzernerhof or further use the diverted lines 24, 73, addintionl buses (direct to Luzernerhof) or the regular line 14 services (all stops) from platform D and transfer back to line 6 and 8 at Luzernerhof. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL014 + 14 + + ch:vbl:VBL014:A + Brühlstrasse + + + + ch:vbl:618::04 + Brühlstrasse + destination + + + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:VBL024:B + Bahnhof + + + + ch:vbl:618::04 + Brühlstrasse + destination + + + + + + + + + open + 0190 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8; Umleitung der Linien 24 und 73. + Line 6 and 8 disrupted; Line 24 and 73 diverted. + + + Benutzen Sie die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte bis Luzernerhof) oder die normal verkehrende Linie 14 (mit Halten) bis Luzernerhof. + Use diverted line 24, 73, additional buses (direct ot Luzernhof) or the regular line 14 services (all stops) to Luzernhof. + + + + + + + route + + + + + + ch:vbl:VBLEBUS + EBUS + + ch:vbl:VBLEBUS:B + Luzernerhof + + + + ch:vbl:121::xx + Luzernerhof + destination + + + + + + + + + open + 0200 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Umleitung endet hier + Diversion ends here + + + Einstieg der Linien 6 und 8 bei Kante A. Reisende nach Haldensteig, Casino-Palace und Europe erreichen ihr Ziel nur zu Fuß. + Board line 6 and 8 from platform A. Travellers to Haldensteig, Casino-Palace and Europe can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL014 + 14 + + ch:vbl:VBL014:B + Horw Zentrum + + + + ch:vbl:121::03 + Luzernerhof + intermediate + + + + + + + + + open + 0210 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Einstieg der Linien 6 und 8 bei Kante A. Reisende nach Haldensteig, Casino-Palace und Europe erreichen ihr Ziel nur zu Fuß. + Board line 6 and 8 from platform A. Travellers to Haldensteig, Casino-Palace and Europe can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:VBL024:B + Bahnhof + + + + ch:vbl:121::3 + Luzernerhof + origin + + + + + ch:vbl:VBL073 + 73 + + ch:vbl:VBL073:B + Bahnhof + + + + ch:vbl:121::3 + Luzernerhof + origin + + + + + + + + + open + 0215 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Umleitung endet hier + Diversion ends here + + + Einstieg der Linien 6 und 8 bei Kante A. Reisende nach Haldensteig, Casino-Palace und Europe erreichen ihr Ziel nur zu Fuß. + Board line 6 and 8 from platform A. Travellers to Haldensteig, Casino-Palace and Europe can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:VBL024:B + Bahnhof + + + + ch:vbl:121::3 + Luzernerhof + origin + + + + + + + + + open + 0220 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Umleitung endet hier + Diversion ends here + + + Umstieg auf die Linien 6 und 8: Einstieg bei Kante A. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Transfer to line 6 and 8: Board from platform A. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:121::04 + Luzernerhof + origin + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:B + Hirtenhof + + + + ch:vbl:121::04 + Luzernerhof + origin + + + + + + + + + open + 0230 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Normale Bedienung der Linien 6 bis Matthof und 8 bis Hirtenhof. + Regular service on line 6 to Matthof and line 8 to Hirtenhof. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + Es muss mit Verspätungen gerechnet werden. + Expect delays. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:120::02 + Schwanenplatz + intermediate + + + ch:vbl:119::01 + Bahnhof + intermediate + + + ch:vbl:118::02 + Kantonalbank + intermediate + + + ch:vbl:407::03 + Bundesplatz + intermediate + + + ch:vbl:606::02 + Werkhofstrasse + intermediate + + + ch:vbl:605::02 + Weinbergli + intermediate + + + ch:vbl:604::02 + Eisfeldstrasse + intermediate + + + ch:vbl:603::02 + Wartegg + intermediate + + + ch:vbl:602::02 + Schönbühl + intermediate + + + ch:vbl:601::01 + Matthof + destination + + + + + + + + + open + 0240 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Es muss mit Verspätungen gerechnet werden. + Expect delays. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + + + + + route + + + + + ch:vbl:VBL02A + 2 + + + ch:vbl:119::06 + Luzern Bahnhof + + + + + + + + + open + 0245 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8 + Line 6 and 8 disrupted + + + Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die umgeleitete Linie 73 oder die normal verkehrende Linie 14 und steigen Sie an der Brüelstrasse wieder um. Reisende nach dem Verkehrshaus benutzen die S3 oder das Schiff. + Transfer advice for line 6 and 8: Use diverted line 73 or the regular line 14 services to Brüelstrasse and transfer back to line 6 and 8. Travellers to Verkehrshaus use the S3 or ferry. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + + + + + route + + + + + ch:vbl:VBL014A + 14 + + ch:vbl:VBL014:A + Brüelstrasse + + + + ch:vbl:119::08 + Luzern Bahnhof + + + + + + + + + open + 0246 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8 + Line 6 and 8 disrupted + + + Empfehlung für Linien 6 und 8: Für Fahrten zur Brüelstrasse und weiter bleiben Sie in der Linie 14 und steigen Sie an der Brüelstrasse um. Reisende nach dem Verkehrshaus benutzen ab dem Bahnhof die S3 oder das Schiff. + Advice for line 6 and 8: For services to Brüelstrasse and further, stay on line 14 and transfer at Brüelstrasse. Travellers after Verkehrshaus use the S3 or ferry from main station. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + + + + + + +       +       diff --git a/examples/siri_exm_SX/VDV736_exm/SX_1135_main_message_update.xml b/examples/siri_exm_SX/VDV736_exm/SX_1135_main_message_update.xml index 7c47cba3..d3327f51 100644 --- a/examples/siri_exm_SX/VDV736_exm/SX_1135_main_message_update.xml +++ b/examples/siri_exm_SX/VDV736_exm/SX_1135_main_message_update.xml @@ -1,2206 +1,2206 @@ - - - - 2018-10-16T10:22:30+00:00 - ch:VBL -
      http:/server/siri/20_ums
      - Pgfkw0GAsg - true - false - - 2018-10-16T10:22:30+00:00 - ch:VBL - 40599x2dsjmu8yjzy - - - 2017-05-28T09:42:00+02:00 - VBL - 5a7cf4f0-c7a5-11e8-813f-f38697968b53 - 2 - - feed - VBL - - published - - 2017-05-28T09:42:00+02:00 - 2017-05-28T17:10:00+02:00 - - fire - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - 3 - route - DE - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - http://www.vbl.ch/aktuelles/verkehrsmeldungen/stoerungen/20160603_13? - - - - - - - - ch:vbl:622 - Haldensteig - - - - - - disruption - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:2507::01 - Büttenhalde - - - ch:vbl:VBL006:A - Büttenhalde - - - - ch:vbl:621::01 - Casino-Palace - affectedStopplace - - - ch:vbl:615::01 - Europe - affectedStopplace - - - ch:vbl:616::01 - Dietschiberg - affectedStopplace - - - ch:vbl:617::01 - Verkehrshaus - affectedStopplace - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:601:01 - Matthof - - - ch:vbl:VBL006:B - Matthof - - - - ch:vbl:617::02 - Verkehrshaus - affectedStopplace - - - ch:vbl:616::02 - Dietschiberg - affectedStopplace - - - ch:vbl:615::02 - Europe - affectedStopplace - - - ch:vbl:621::02 - Casino-Palace - affectedStopplace - - - ch:vbl:622::02 - Haldensteig - affectedStopplace - - - - - ch:vbl:VBL008 - 8 - - ch:vbl:620:01 - Würzenbach - - - ch:vbl:VBL008:A - Würzenbach - - - - ch:vbl:621::01 - Casino-Palace - affectedStopplace - - - ch:vbl:615::01 - Europe - affectedStopplace - - - ch:vbl:616::01 - Dietschiberg - affectedStopplace - - - ch:vbl:617::01 - Verkehrshaus - affectedStopplace - - - - - ch:vbl:VBL008 - 8 - - ch:vbl:801:01 - Hirtenhof - - - ch:vbl:VBL008:B - Hirtenhof - - - - ch:vbl:617::02 - Verkehrshaus - affectedStopplace - - - ch:vbl:616::02 - Dietschiberg - affectedStopplace - - - ch:vbl:615::02 - Europe - affectedStopplace - - - ch:vbl:621::02 - Casino-Palace - affectedStopplace - - - ch:vbl:622::02 - Haldensteig - affectedStopplace - - - - - - - - true - true - - - - diverted - - - - - ch:vbl:VBL024 - 24 - - ch:vbl:2433:01 - Tschädigen - - - ch:vbl:VBL024:A - Tschädigen - - - - ch:vbl:121::02 - affectedStopplace - - - ch:vbl:621::01 - Casino-Palace - affectedStopplace - - - ch:vbl:617::01 - Verkehrshaus - affectedStopplace - - - ch:vbl:715::01 - intermediate - - - ch:vbl:716::01 - intermediate - - - ch:vbl:1405::01 - intermediate - - - ch:vbl:1406::01 - intermediate - - - ch:vbl:1407::01 - intermediate - - - ch:vbl:1408::01 - intermediate - - - ch:vbl:1409::01 - intermediate - - - ch:vbl:1410::01 - intermediate - - - ch:vbl:1411::01 - intermediate - - - ch:vbl:1412::01 - intermediate - - - - - ch:vbl:VBL024 - 24 - - ch:vbl:119:13 - Bahnhof - - - ch:vbl:VBL024:B - Bahnhof - - - - ch:vbl:617::02 - Verkehrshaus - affectedStopplace - - - ch:vbl:621::02 - affectedStopplace - - - ch:vbl:622::02 - affectedStopplace - - - ch:vbl:1412::02 - intermediate - - - ch:vbl:1411::02 - intermediate - - - ch:vbl:1410::02 - intermediate - - - ch:vbl:1409::02 - intermediate - - - ch:vbl:1408::02 - intermediate - - - ch:vbl:1407::02 - intermediate - - - ch:vbl:1406::02 - intermediate - - - ch:vbl:1405::02 - intermediate - - - ch:vbl:716::02 - intermediate - - - ch:vbl:715::01 - Wey Auch? - intermediate - - - - - - - - true - true - - - PT7M - - - - - - - line - - - - - ch:vbl:VBL006 - 6 - - - ch:vbl:VBL008 - 8 - - - ch:vbl:VBL024 - 24 - - - - - - - open - 0250 - 2017-05-28T09:42:00+02:00 - 1 - vbl - general - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Betroffen sind die Linien 6, 8 und 24 - Affected lines are 6, 8 and 24 - - - Linie 6 und 8 fallen zwischen Luzernerhof und Brüelstrasse aus. - Linie 24 wird zwischen Luzernerhof und Brüelstrasse via St. Anna umgeleitet. Ca. 7 Min. längere Fahrzeit. - Line 6 and 8 services cancelled between Luzernerhof and Brüelstrasse. - Line 24 divirted between Luzernerhof and Brüelstrasse via St. Anna. Approx. 7 min delay. - - - Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. - Zwischen Luzern, Bahnhof und Verkehrshaus benutzen sie die S3 oder das Schiff. - Umstiegsempfehlung für die Linien 6 und 8: Bei den Haltestellen Luzernerhof bzw. Brüelstrasse auf die umgeleitete Linie 24, die normal verkehrenden Linien 14 und 73 oder den Entlastungsbus umsteigen. - Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. - Between Luzern, Bahnhof and Verkehrshaus use the S3 or ferry. - Transfer advice for line 6 and 8: At Luzernerhof or Brüelstrasse use diverted line 24, 73, additional buses or the regular line 14 services. - - - Die Störung dauert bis ca.12:30 Uhr. - Disruption duration until 12:30pm. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:A - Büttenenhalde - - - - ch:vbl:601::01 - Matthof - - - ch:vbl:602::01 - Schönbühl - - - ch:vbl:603::03 - Wartegg - - - ch:vbl:604::01 - Eisfeldstrasse - - - ch:vbl:605::01 - Weinbergli - - - ch:vbl:606::01 - Werkhofstrasse - - - ch:vbl:407::02 - Bundesplatz - - - ch:vbl:118::01 - Kantonalbank (C) - - - ch:vbl:119::02 - Bahnhof (B) - - - ch:vbl:120::01 - Schwanenplatz - - - - - - - - - open - 0260 - 2017-05-28T09:42:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Die Linie 6 fällt zwischen Luzernerhof und Brüelstrasse aus. - Line 6 cancelled between Luzernerhof and Brüelstrasse. - - - Reisende nach Brüelstrasse und weiter benützen die umgeleitete Linie 24 (ohne Halte zwischen Wey und Brüelstrasse) oder die normal verkehrenden Linien 14 und 73 und steigen an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. - Travellers to Brüelstrasse or further use the diverted line 24 (direct between Wey and Brühlstrasse) or the regular line 14 or 73 services and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. - - - Die Störung dauert bis ca.12:30 Uhr. - Disruption duration until 12:30pm. - - - - - open - 0270 - 2017-05-28T09:42:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Die Linie 6 fällt zwischen Luzernerhof und Brüelstrasse aus. - Line 6 cancelled between Luzernerhof and Brüelstrasse. - - - Reisende nach Brüelstrasse und weiter benützen die umgeleitete Linie 24 (ohne Halte zwischen Wey und Brüelstrasse) oder die normal verkehrenden Linien 14 und 73 und steigen an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. - Travellers to Brüelstrasse or further use the diverted line 24 (direct between Wey and Brühlstrasse) or the regular services of line 14 or 73 and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. - - - Die Störung dauert bis ca.12:30 Uhr. - Disruption duration until 12:30pm. - - - Weitere Informationen erhalten Sie unter www.vbl.ch/stoerung/haldenstrasse - For further information, please visit www.vbl.ch/stoerung/haldenstrasse - - - www.vbl.ch/stoerung/haldenstrasse - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - - ch:vbl:121::02 - Luzernerhof (B) - - - - - - - - - open - 0280 - 2017-05-28T09:42:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Linie 6 wendet hier - Line 6 turns here - - - Reisende zur Brüelstrasse und weiter benützen die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte zwischen Wey und Brüelstrasse) oder die normale verkehrende Linie 14 (mit Halten) ab Kante F (Wey) oder die Linie 73 ab Kante D und steigen an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. - Travellers to Brüelstrasse or further use the diverted line 24, additonal buses (direct between Wey and Brüelstrasse), the regular services of line 14 (all stops) from platform F (Way) or line 73 from platform D and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - - ch:vbl:121::01 - Luzernerhof (C) - - - ch:vbl:121::02 - Luzernerhof (D) - - - - - ch:vbl:VBL008 - 8 - - - ch:vbl:121::01 - Luzernerhof (C) - - - ch:vbl:121::02 - Luzernerhof (D) - - - - - - - - - open - 0290 - 2017-05-28T09:42:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Unterbruch der Linien 6 und 8 - Line 6 and 8 disrupted - - - Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die umgeleitete Linie 24, die normal verkehrende Linie 14 und den Entlastungsbus ab Kante F (Wey) oder die Linie 73 ab Kante D und steigen Sie an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. - Transfer advice line 6 and 8: To Brüelstrasse use diverted line 24, the regular line 14 services or the additional buses from platform F (Wey) or line 73 from platform D and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. - - - Die Störung dauert bis ca.12:30 Uhr. - Disruption duration until 12:30pm. - - - Weitere Informationen erhalten Sie beim Auskunftspersonal. - For further information, please contact staff. - - - - - - - route - - - - - ch:vbl:Entlastungsbusse - - - ch:vbl:715::01 - Wey - - - - - ch:vbl:VBL014 - 14 - - - ch:vbl:715::01 - Wey - - - - - ch:vbl:VBL24 - 24 - - - ch:vbl:715::01 - Wey - - - - - - - - - open - 0300 - 2017-05-28T09:42:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Unterbruch der Linien 6 und 8; Umleitung der Linien 24. - Line 6 and 8 disrupted; Line 24 diverted. - - - Benutzen Sie die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte bis Brüelstrasse) oder die normal verkehrenden Linie 14 (mit Halten) und 73 bis Brüelstrasse. - Use diverted line 24, additional buses (direct to Brüelstrasse), regular services of line 14 (all stops) or 73 to Brüelstrasse. - - - Die Störung dauert bis ca.12:30 Uhr. - Disruption duration until 12:30pm. - - - - - - - route - - - - - ch:vbl:VBL006 - 06 - - ch:vbl:VBL006:A - Büttenenhalde - - - - ch:vbl:121::02 - Luzernerhof (D) - - - - - ch:vbl:VBL008 - 08 - - ch:vbl:VBL008:A - Würzenbach - - - - ch:vbl:121::02 - Luzernerhof (D) - - - - - - - - - open - 0370 - 2017-05-28T09:42:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Linie 6 und 8 fallen bis Brüelstrasse aus. Linie 24 wird zwischen Luzernerhof und Brüel via St. Anna umgeleitet. Ca. 7 Min. längere Fahrzeit. Linie 73 verkehrt wieder normal. - Line 6 and 8 cancelled services to Brüelstrasse. Line 24 services diverted between Luzernerhof and Brüel via St. Anna. Approx. 7 min delay. Line 73 back to regular service. - - - Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte zwischen Wey und Brüelstrasse) oder die normale verkehrende Linie 14 (mit Halten) ab Kante F (Wey) oder die Linie 73 ab Kante D und steigen Sie an der Brüelstrasse um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. - Transfer advice for line 6 and 8: Use diverted line 73, additonal buses (direct between Wey and Brüelstrasse), the regular line 14 services (all stops) from platform F (Wey) or line 73 from platform D and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. - - - Die Störung dauert bis ca.12:30 Uhr. - Disruption duration until 12:30pm. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:A - Büttenenhalde - - - - ch:vbl:621::01 - Casino-Palace - - - ch:vbl:615::01 - Europe - - - ch:vbl:616::01 - Dietschiberg - - - ch:vbl:617::01 - Verkehrshaus - - - - - ch:vbl:VBL008 - 8 - - ch:vbl:VBL008:A - Würzenbach - - - - ch:vbl:621::01 - Casino-Palace - - - ch:vbl:615::01 - Europe - - - ch:vbl:616::01 - Dietschiberg - - - ch:vbl:617::01 - Verkehrshaus - - - - - ch:vbl:VBL024 - 24 - - ch:vbl:VBL024:A - Tschädingen - - - - ch:vbl:621::01 - Casino-Palace - - - ch:vbl:615::01 - Europe - - - ch:vbl:616::01 - Dietschiberg - - - ch:vbl:617::01 - Verkehrshaus - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:B - Matthof - - - - ch:vbl:617::02 - Verkehrshaus - - - ch:vbl:616::02 - Dietschiberg - - - ch:vbl:615::02 - Europe - - - ch:vbl:621::02 - Casino-Palace - - - ch:vbl:622::01 - Haldensteig - - - - - ch:vbl:VBL008 - 8 - - ch:vbl:VBL008:B - Hirtenhof - - - - ch:vbl:617::02 - Verkehrshaus - - - ch:vbl:616::02 - Dietschiberg - - - ch:vbl:615::02 - Europe - - - ch:vbl:621::02 - Casino-Palace - - - ch:vbl:622::01 - Haldensteig - - - - - ch:vbl:VBL024 - 24 - - ch:vbl:VBL024:B - Bahnhof - - - - ch:vbl:617::02 - Verkehrshaus - - - ch:vbl:616::02 - Dietschiberg - - - ch:vbl:615::02 - Europe - - - ch:vbl:621::02 - Casino-Palace - - - ch:vbl:622::01 - Haldensteig - - - - - - - - - open - 0380 - 2017-05-28T09:42:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Keine Bedienung der Linien 6, 8 und 24 zwischen Luzernerhof und Brüelstrasse - Line 6, 8 and 24 no service between Luzernerhof and Brüelstrasse - - - Reisende zwischen Luzernerhof und Brüelstrasse erreichen ihr Ziel nur zu Fuß. Ab Luzernerhof und Brüelstrasse verkehren die Linie auf den normalen Fahrwegen. - Travellers between Luzernerhof and Brüelstrasse can only reach their destination on foot. From Luzernerhof and Brüelstrasse lines will run on regular routes. - - - Die Störung dauert bis ca.12:30 Uhr. - Disruption duration until 12:30pm. - - - Fällt aus - Cancelled - - - - - - - route - - - - - ch:vbl:014 - 14 - - ch:vbl:VBL014:A - Brüelstrasse - - - - ch:vbl:618::01 - Brüelstrasse - destination - - - - - - - - - open - 0310 - 2017-05-28T09:42:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Die Fahrt endet hier - Service terminates here - - - Einstieg der Linien 6 und 8 bei Kante C. Reisende nach Verkehrshaus und Dietschiberg erreichen ihr Ziel nur zu Fuß. - Board line 6 and 8 from platform C. Travellers to Verkehrshaus and Dietschiberg can only reach their destination on foot. - - - - - - - route - - - - - ch:vbl:024 - 24 - - ch:vbl:VBL014:A - Brüelstrasse - - - - ch:vbl:618::04 - Brüelstrasse - destination - - - - - - - - - open - 0320 - 2017-05-28T09:42:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Die Umleitung endet hier - Diversion ends here - - - Umstieg auf Linie 6 und 8: Einstieg bei Kante C. Reisende nach Verkehrshaus und Dietschiberg erreichen ihr Ziel nur zu Fuß. - Transfer to line 6 and 8: Board from platform C. Travellers to Verkehrshaus and Dietschiberg can only reach their destination on foot. - - - - - - - route - - - - - ch:vbl:VBL006 - 06 - - ch:vbl:VBL006:A - Büttenenhalde - - - - ch:vbl:618::03 - Brüelstrasse - - - - - ch:vbl:VBL008 - 08 - - ch:vbl:VBL008:A - Würzenbach - - - - ch:vbl:618::03 - Brüelstrasse - - - - - - - - - open - 0330 - 2017-05-28T09:42:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Normale Bedienung der Linien 6 bis Büttenenhalde und 8 bis Würzenbach. Es muss mit Verspätungen gerechnet werden. - Regular service on line 6 to Büttenenhalde and 8 to Würzenbach. Expect delays. - - - Die Störung dauert bis ca.12:30 Uhr. - Disruption duration until 12:30pm. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:A - Büttenhalde - - - - ch:vbl:2502::01 - Giseli - - - ch:vbl:2503::01 - Oberseeburg - intermediate - - - ch:vbl:2504::01 - Oberseeburghöhe - intermediate - - - ch:vbl:2505::01 - Eggen - intermediate - - - ch:vbl:2506::01 - Büttenen - intermediate - - - ch:vbl:2507::01 - Büttenenhalde - destination - - - - - ch:vbl:VBL008 - 8 - - ch:vbl:VBL008:A - Würzenbach - - - - ch:vbl:619::01 - Würzenbachmatte - intermediate - - - ch:vbl:620::01 - Würzenbach - destination - - - - - - - - - open - 0340 - 2017-05-28T09:42:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Es muss mit Verspätungen gerechnet werden. - Expect delays. - - - Die Störung dauert bis ca. 12:30 Uhr. - Disruption duration until 12:30pm. - - - - - - - route - - - - - ch:vbl:Entlastungsbus - Entlastungsbus - - ch:vbl:VBL006:A - Büttenhalde - - - - ch:vbl:618::04 - Brüelstrasse - - - - - - - - - open - 0350 - 2017-05-28T10:22:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Diese Fahrt endet hier - This service terminates here - - - Einstieg der Linien 6 und 8 bei Kante C. Reisende nach Verkehrshaus und Dietschiberg erreichen ihr Ziel nur zu Fuß. - Board line 6 and 8 from platform C. Travellers to Verkehrshaus and Dietschiberg can only reach their destination on foot. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:B - Matthof - - - - ch:vbl:2507::01 - Büttenenhalde - origin - - - ch:vbl:2506::02 - Büttenen - intermediate - - - ch:vbl:2505::02 - Eggen - intermediate - - - ch:vbl:2504::02 - Oberseeburghöhe - intermediate - - - ch:vbl:2503::02 - Oberseeburg - intermediate - - - ch:vbl:2502::02 - Giseli - intermediate - - - - - - - - - open - 0390 - 2017-05-28T09:42:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Die Linie 6 fällt zwischen Brüelstrasse und Luzernerhof aus. - Line 6 cancelled between Brüelstrasse and Luzernerhof. - - - Reisende nach Luzernerhof oder weiter benützen die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte zwischen Brüelstrasse und Luzernerhof) oder die normal verkehrenden Linien 14 (mit Halten) und 73 bis Luzernerhof und steigen dort wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. - Travellers to Luzernerhof or further use the diverted line 24, additional buses (direct between Brühlstrasse and Luzernerhof), the regular line 14 services (all stop) or line 73 to Luzernhof and transfer there. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. - - - Die Störung dauert bis ca. 12:30 Uhr. - Disruption duration until 12:30pm. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:B - Matthof - - - - ch:vbl:2507::01 - Büttenenhalde - origin - - - ch:vbl:2506::02 - Büttenen - intermediate - - - ch:vbl:2505::02 - Eggen - intermediate - - - ch:vbl:2504::02 - Oberseeburghöhe - intermediate - - - ch:vbl:2503::02 - Oberseeburg - intermediate - - - ch:vbl:2502::02 - Giseli - intermediate - - - - - - - - - open - 0400 - 2017-05-28T09:42:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Die Linie 6 fällt zwischen Brüelstrasse und Luzernerhof aus. - Line 6 cancelled between Brüelstrasse and Luzernerhof. - - - Reisende nach Luzernerhof oder weiter benützen die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte zwischen Brüelstrasse und Luzernerhof) oder die normal verkehrenden Linien 14 (mit Halten) und 73 bis Luzernerhof und steigen dort wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. - Travellers to Luzernerhof or further use the diverted line 24, the additional buses (direct between Brühlstrasse and Luzernerhof), the regular line 14 services (all stop) or line 73 to Luzernhof and transfer there. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. - - - Die Störung dauert bis ca. 12:30 Uhr. - Disruption duration until 12:30pm. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:B - Matthof - - - - ch:vbl:618::02 - Brüelstrasse - - - - - - - - - open - 0410 - 2017-05-28T09:42:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Linie 6 wendet hier - Line 6 turns here - - - Reisende zum Luzernerhof oder weiter benützen die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte bis Luzernerhof) oder die normal verkehrende Linie 14 (mit Halten) oder 73 ab Kante D und steigen beim Luzernerhof wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. - Travellers to Luzernerhof or further use the diverted line 24, addintional buses (direct to Luzernerhof), the regular line 14 services (all stops) or line 73 from platform D and transfer back to Luzernerhof. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:B - Matthof - - - - ch:vbl:618::02 - Brüelstrasse - - - - - - - - - open - 0420 - 2017-05-28T09:42:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Unterbruch der Linien 6 und 8 - Line 6 and 8 disrupted - - - Reisende zum Luzernerhof oder weiter benützen die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte bis Luzernerhof) ab Kante D oder die normal verkehrenden Linien 14 (mit Halten) ab Kante D und 73 ab Kante C und steigen beim Luzernerhof wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. - Travellers to Luzernerhof or further use the diverted line 24, addintional buses (direct to Luzernerhof) from platform D, the regular line 14 services (all stops) from platform D or line 73 from platform C and transfer back to Luzernerhof. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. - - - Die Störung dauert bis ca. 12:30 Uhr. - Disruption duration until 12:30pm. - - - - - - - route - - - - - ch:vbl:Entlastungsbus - Entlastungsbus - - ch:vbl:VBL006:A - Büttenhalde - - - - ch:vbl:VBL014 - 14 - - ch:vbl:VBL014:A - Brühlstrasse - - - - ch:vbl:618::01 - Brühlstrasse - destination - - - - - - - ch:vbl:VBL024 - 24 - - ch:vbl:VBL024:B - Bahnhof - - - - ch:vbl:618::01 - Brühlstrasse - destination - - - - - - - - - open - 0430 - 2017-05-28T09:42:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Unterbruch der Linien 6 und 8; Umleitung der Linien 24. - Line 6 and 8 disrupted; Line 24 diverted. - - - Benutzen Sie die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte bis Luzernerhof) oder die normal verkehrenden Linien 14 (mit Halten) und 73 bis Luzernerhof. - Use diverted line 24 and additional buses (direct to Luzernerhof) or the regular line 14 (all stops) and line 73 to Luzernerhof. - - - Die Störung dauert bis ca. 12:30 Uhr. - Disruption duration until 12:30pm. - - - - - - - route - - - - - ch:vbl:Entlastungsbus - Entlastungsbus - - ch:vbl:VBL006:A - Büttenhalde - - - - ch:vbl:121::03 - Luzernerhof - - - - - - - - - open - 0440 - 2017-05-28T09:42:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Diese Fahrt endet hier - This service terminates here - - - Einstieg der Linien 6 und 8 bei Kante A. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. - Board line 6 and 8 from platform A. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. - - - Die Störung dauert bis ca. 12:30 Uhr. - Disruption duration until 12:30pm. - - - - - - - route - - - - - ch:vbl:VBL024 - 24 - - ch:vbl:VBL024:B - Bahnhof - - - - ch:vbl:121::04 - Luzernerhof - origin - - - - - - - - - open - 0450 - 2017-05-28T09:42:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Die Umleitung endet hier - Diversion ends here - - - Umstieg auf Linie 6 und 8: Einstieg bei Kante A. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. - Transfer to line 6 and 8: Board from platform A. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. - - - - - - - route - - - - - ch:vbl:VBL014 - 14 - - ch:vbl:VBL014:B - Horw Zentrum - - - - ch:vbl:121::03 - Luzernerhof - intermediate - - - - - - - - - open - 0455 - 2017-05-28T09:42:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - - - Umstieg auf Linie 6 und 8: Einstieg bei Kante A. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. - - - - - - - route - - - - - ch:vbl:VBL024 - 24 - - ch:vbl:VBL024:B - Bahnhof - - - - ch:vbl:121::03 - Luzernerhof - origin - - - - - - - - - open - 0460 - 2017-05-28T09:42:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Die Umleitung endet hier - Diversion ends here - - - Umstieg auf die Linien 6 und 8: Einstieg bei Kante A. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. - Transfer to line 6 and 8: Board from platform A. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:B - Matthof - - - - ch:vbl:121::04 - Luzernerhof - origin - - - - - ch:vbl:VBL008 - 8 - - ch:vbl:VBL008:B - Hiertenhof - - - - ch:vbl:121::04 - Luzernerhof - origin - - - - - - - - - open - 0470 - 2017-05-28T09:42:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Normale Bedienung der Linien 6 bis Matthof und 8 bis Hirtenhof. Es muss mit Verspätungen gerechnet werden. - Regular service on line 6 to Matthof and line 8 to Hirtenhof. Expect delays. - - - Die Störung dauert bis ca. 12:30 Uhr. - Disruption duration until 12:30pm. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:B - Matthof - - - - ch:vbl:120::02 - Schwanenplatz - intermediate - - - ch:vbl:119::01 - Bahnhof - intermediate - - - ch:vbl:118::02 - Kantonalbank - intermediate - - - ch:vbl:407::03 - Bundesplatz - intermediate - - - ch:vbl:606::02 - Werkhofstrasse - intermediate - - - ch:vbl:605::02 - Weinbergli - intermediate - - - ch:vbl:604::02 - Eisfeldstrasse - intermediate - - - ch:vbl:603::02 - Wartegg - intermediate - - - ch:vbl:602::02 - Schönbühl - intermediate - - - ch:vbl:601::01 - Matthof - destination - - - - - - - - - open - 0480 - 2017-05-28T09:42:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Es muss mit Verspätungen gerechnet werden. - Expect delays. - - - Die Störung dauert bis ca. 12:30 Uhr. - Disruption duration until 12:30pm. - - - - - - - line - - - - - ch:vbl:VBL002 - 2 - - - ch:vbl:VBL002:A - Bahnhof - - - - ch:vbl:119::06 - Bahnhof - destination - - - - - - - - - open - 0481 - 2017-05-28T09:42:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Unterbruch der Linien 6 und 8 - Line 6 and 8 disrupted - - - Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die Linien 14 oder 73 und steigen Sie an der Brüelstrasse wieder um. Reisende nach dem Verkehrshaus benutzen die S3 oder das Schiff. - Transfer advice line 6 and 8: Use line 14 or 73 to Brüelstrasse and transfer back to line 6 and 8. Travellers to Verkehrshaus use the S3 or ferry. - - - Die Störung dauert bis ca. 12:30 Uhr. - Disruption duration until 12:30pm. - - - - - - - route - - - - - ch:vbl:VBL014 - 14 - - ch:vbl:VBL014:A - Brüelstrasse - - - - ch:vbl:119::08 - Bahnhof - intermediate - - - - - - - - - open - 0482 - 2017-05-28T09:42:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Unterbruch der Linien 6 und 8 - Line 6 and 8 disrupted - - - Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die Linien 14 oder 73 und steigen Sie an der Brüelstrasse wieder um. Reisende nach dem Verkehrshaus benutzen die S3 oder das Schiff. - Transfer advice line 6 and 8: Use line 14 or 73 to Brüelstrasse and transfer back to line 6 and 8. Travellers to Verkehrshaus use the S3 or ferry. - - - Die Störung dauert bis ca. 12:30 Uhr. - Disruption duration until 12:30pm. - - - - - - - - -       -       + + + + 2018-10-16T10:22:30+00:00 + ch:VBL +
      http:/server/siri/20_ums
      + Pgfkw0GAsg + true + false + + 2018-10-16T10:22:30+00:00 + ch:VBL + 40599x2dsjmu8yjzy + + + 2017-05-28T09:42:00+02:00 + VBL + 5a7cf4f0-c7a5-11e8-813f-f38697968b53 + 2 + + feed + VBL + + published + + 2017-05-28T09:42:00+02:00 + 2017-05-28T17:10:00+02:00 + + fire + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + 3 + route + DE + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + http://www.vbl.ch/aktuelles/verkehrsmeldungen/stoerungen/20160603_13? + + + + + + + + ch:vbl:622 + Haldensteig + + + + + + disruption + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:2507::01 + Büttenhalde + + + ch:vbl:VBL006:A + Büttenhalde + + + + ch:vbl:621::01 + Casino-Palace + affectedStopplace + + + ch:vbl:615::01 + Europe + affectedStopplace + + + ch:vbl:616::01 + Dietschiberg + affectedStopplace + + + ch:vbl:617::01 + Verkehrshaus + affectedStopplace + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:601:01 + Matthof + + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:617::02 + Verkehrshaus + affectedStopplace + + + ch:vbl:616::02 + Dietschiberg + affectedStopplace + + + ch:vbl:615::02 + Europe + affectedStopplace + + + ch:vbl:621::02 + Casino-Palace + affectedStopplace + + + ch:vbl:622::02 + Haldensteig + affectedStopplace + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:620:01 + Würzenbach + + + ch:vbl:VBL008:A + Würzenbach + + + + ch:vbl:621::01 + Casino-Palace + affectedStopplace + + + ch:vbl:615::01 + Europe + affectedStopplace + + + ch:vbl:616::01 + Dietschiberg + affectedStopplace + + + ch:vbl:617::01 + Verkehrshaus + affectedStopplace + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:801:01 + Hirtenhof + + + ch:vbl:VBL008:B + Hirtenhof + + + + ch:vbl:617::02 + Verkehrshaus + affectedStopplace + + + ch:vbl:616::02 + Dietschiberg + affectedStopplace + + + ch:vbl:615::02 + Europe + affectedStopplace + + + ch:vbl:621::02 + Casino-Palace + affectedStopplace + + + ch:vbl:622::02 + Haldensteig + affectedStopplace + + + + + + + + true + true + + + + diverted + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:2433:01 + Tschädigen + + + ch:vbl:VBL024:A + Tschädigen + + + + ch:vbl:121::02 + affectedStopplace + + + ch:vbl:621::01 + Casino-Palace + affectedStopplace + + + ch:vbl:617::01 + Verkehrshaus + affectedStopplace + + + ch:vbl:715::01 + intermediate + + + ch:vbl:716::01 + intermediate + + + ch:vbl:1405::01 + intermediate + + + ch:vbl:1406::01 + intermediate + + + ch:vbl:1407::01 + intermediate + + + ch:vbl:1408::01 + intermediate + + + ch:vbl:1409::01 + intermediate + + + ch:vbl:1410::01 + intermediate + + + ch:vbl:1411::01 + intermediate + + + ch:vbl:1412::01 + intermediate + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:119:13 + Bahnhof + + + ch:vbl:VBL024:B + Bahnhof + + + + ch:vbl:617::02 + Verkehrshaus + affectedStopplace + + + ch:vbl:621::02 + affectedStopplace + + + ch:vbl:622::02 + affectedStopplace + + + ch:vbl:1412::02 + intermediate + + + ch:vbl:1411::02 + intermediate + + + ch:vbl:1410::02 + intermediate + + + ch:vbl:1409::02 + intermediate + + + ch:vbl:1408::02 + intermediate + + + ch:vbl:1407::02 + intermediate + + + ch:vbl:1406::02 + intermediate + + + ch:vbl:1405::02 + intermediate + + + ch:vbl:716::02 + intermediate + + + ch:vbl:715::01 + Wey Auch? + intermediate + + + + + + + + true + true + + + PT7M + + + + + + + line + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 24 + + + + + + + open + 0250 + 2017-05-28T09:42:00+02:00 + 1 + vbl + general + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Betroffen sind die Linien 6, 8 und 24 + Affected lines are 6, 8 and 24 + + + Linie 6 und 8 fallen zwischen Luzernerhof und Brüelstrasse aus. + Linie 24 wird zwischen Luzernerhof und Brüelstrasse via St. Anna umgeleitet. Ca. 7 Min. längere Fahrzeit. + Line 6 and 8 services cancelled between Luzernerhof and Brüelstrasse. + Line 24 divirted between Luzernerhof and Brüelstrasse via St. Anna. Approx. 7 min delay. + + + Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Zwischen Luzern, Bahnhof und Verkehrshaus benutzen sie die S3 oder das Schiff. + Umstiegsempfehlung für die Linien 6 und 8: Bei den Haltestellen Luzernerhof bzw. Brüelstrasse auf die umgeleitete Linie 24, die normal verkehrenden Linien 14 und 73 oder den Entlastungsbus umsteigen. + Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + Between Luzern, Bahnhof and Verkehrshaus use the S3 or ferry. + Transfer advice for line 6 and 8: At Luzernerhof or Brüelstrasse use diverted line 24, 73, additional buses or the regular line 14 services. + + + Die Störung dauert bis ca.12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:A + Büttenenhalde + + + + ch:vbl:601::01 + Matthof + + + ch:vbl:602::01 + Schönbühl + + + ch:vbl:603::03 + Wartegg + + + ch:vbl:604::01 + Eisfeldstrasse + + + ch:vbl:605::01 + Weinbergli + + + ch:vbl:606::01 + Werkhofstrasse + + + ch:vbl:407::02 + Bundesplatz + + + ch:vbl:118::01 + Kantonalbank (C) + + + ch:vbl:119::02 + Bahnhof (B) + + + ch:vbl:120::01 + Schwanenplatz + + + + + + + + + open + 0260 + 2017-05-28T09:42:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Linie 6 fällt zwischen Luzernerhof und Brüelstrasse aus. + Line 6 cancelled between Luzernerhof and Brüelstrasse. + + + Reisende nach Brüelstrasse und weiter benützen die umgeleitete Linie 24 (ohne Halte zwischen Wey und Brüelstrasse) oder die normal verkehrenden Linien 14 und 73 und steigen an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Travellers to Brüelstrasse or further use the diverted line 24 (direct between Wey and Brühlstrasse) or the regular line 14 or 73 services and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + Die Störung dauert bis ca.12:30 Uhr. + Disruption duration until 12:30pm. + + + + + open + 0270 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Linie 6 fällt zwischen Luzernerhof und Brüelstrasse aus. + Line 6 cancelled between Luzernerhof and Brüelstrasse. + + + Reisende nach Brüelstrasse und weiter benützen die umgeleitete Linie 24 (ohne Halte zwischen Wey und Brüelstrasse) oder die normal verkehrenden Linien 14 und 73 und steigen an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Travellers to Brüelstrasse or further use the diverted line 24 (direct between Wey and Brühlstrasse) or the regular services of line 14 or 73 and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + Die Störung dauert bis ca.12:30 Uhr. + Disruption duration until 12:30pm. + + + Weitere Informationen erhalten Sie unter www.vbl.ch/stoerung/haldenstrasse + For further information, please visit www.vbl.ch/stoerung/haldenstrasse + + + www.vbl.ch/stoerung/haldenstrasse + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:121::02 + Luzernerhof (B) + + + + + + + + + open + 0280 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Linie 6 wendet hier + Line 6 turns here + + + Reisende zur Brüelstrasse und weiter benützen die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte zwischen Wey und Brüelstrasse) oder die normale verkehrende Linie 14 (mit Halten) ab Kante F (Wey) oder die Linie 73 ab Kante D und steigen an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Travellers to Brüelstrasse or further use the diverted line 24, additonal buses (direct between Wey and Brüelstrasse), the regular services of line 14 (all stops) from platform F (Way) or line 73 from platform D and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:121::01 + Luzernerhof (C) + + + ch:vbl:121::02 + Luzernerhof (D) + + + + + ch:vbl:VBL008 + 8 + + + ch:vbl:121::01 + Luzernerhof (C) + + + ch:vbl:121::02 + Luzernerhof (D) + + + + + + + + + open + 0290 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8 + Line 6 and 8 disrupted + + + Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die umgeleitete Linie 24, die normal verkehrende Linie 14 und den Entlastungsbus ab Kante F (Wey) oder die Linie 73 ab Kante D und steigen Sie an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Transfer advice line 6 and 8: To Brüelstrasse use diverted line 24, the regular line 14 services or the additional buses from platform F (Wey) or line 73 from platform D and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + Die Störung dauert bis ca.12:30 Uhr. + Disruption duration until 12:30pm. + + + Weitere Informationen erhalten Sie beim Auskunftspersonal. + For further information, please contact staff. + + + + + + + route + + + + + ch:vbl:Entlastungsbusse + + + ch:vbl:715::01 + Wey + + + + + ch:vbl:VBL014 + 14 + + + ch:vbl:715::01 + Wey + + + + + ch:vbl:VBL24 + 24 + + + ch:vbl:715::01 + Wey + + + + + + + + + open + 0300 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8; Umleitung der Linien 24. + Line 6 and 8 disrupted; Line 24 diverted. + + + Benutzen Sie die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte bis Brüelstrasse) oder die normal verkehrenden Linie 14 (mit Halten) und 73 bis Brüelstrasse. + Use diverted line 24, additional buses (direct to Brüelstrasse), regular services of line 14 (all stops) or 73 to Brüelstrasse. + + + Die Störung dauert bis ca.12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:VBL006 + 06 + + ch:vbl:VBL006:A + Büttenenhalde + + + + ch:vbl:121::02 + Luzernerhof (D) + + + + + ch:vbl:VBL008 + 08 + + ch:vbl:VBL008:A + Würzenbach + + + + ch:vbl:121::02 + Luzernerhof (D) + + + + + + + + + open + 0370 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Linie 6 und 8 fallen bis Brüelstrasse aus. Linie 24 wird zwischen Luzernerhof und Brüel via St. Anna umgeleitet. Ca. 7 Min. längere Fahrzeit. Linie 73 verkehrt wieder normal. + Line 6 and 8 cancelled services to Brüelstrasse. Line 24 services diverted between Luzernerhof and Brüel via St. Anna. Approx. 7 min delay. Line 73 back to regular service. + + + Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte zwischen Wey und Brüelstrasse) oder die normale verkehrende Linie 14 (mit Halten) ab Kante F (Wey) oder die Linie 73 ab Kante D und steigen Sie an der Brüelstrasse um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Transfer advice for line 6 and 8: Use diverted line 73, additonal buses (direct between Wey and Brüelstrasse), the regular line 14 services (all stops) from platform F (Wey) or line 73 from platform D and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + Die Störung dauert bis ca.12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:A + Büttenenhalde + + + + ch:vbl:621::01 + Casino-Palace + + + ch:vbl:615::01 + Europe + + + ch:vbl:616::01 + Dietschiberg + + + ch:vbl:617::01 + Verkehrshaus + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:A + Würzenbach + + + + ch:vbl:621::01 + Casino-Palace + + + ch:vbl:615::01 + Europe + + + ch:vbl:616::01 + Dietschiberg + + + ch:vbl:617::01 + Verkehrshaus + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:VBL024:A + Tschädingen + + + + ch:vbl:621::01 + Casino-Palace + + + ch:vbl:615::01 + Europe + + + ch:vbl:616::01 + Dietschiberg + + + ch:vbl:617::01 + Verkehrshaus + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:617::02 + Verkehrshaus + + + ch:vbl:616::02 + Dietschiberg + + + ch:vbl:615::02 + Europe + + + ch:vbl:621::02 + Casino-Palace + + + ch:vbl:622::01 + Haldensteig + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:B + Hirtenhof + + + + ch:vbl:617::02 + Verkehrshaus + + + ch:vbl:616::02 + Dietschiberg + + + ch:vbl:615::02 + Europe + + + ch:vbl:621::02 + Casino-Palace + + + ch:vbl:622::01 + Haldensteig + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:VBL024:B + Bahnhof + + + + ch:vbl:617::02 + Verkehrshaus + + + ch:vbl:616::02 + Dietschiberg + + + ch:vbl:615::02 + Europe + + + ch:vbl:621::02 + Casino-Palace + + + ch:vbl:622::01 + Haldensteig + + + + + + + + + open + 0380 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Keine Bedienung der Linien 6, 8 und 24 zwischen Luzernerhof und Brüelstrasse + Line 6, 8 and 24 no service between Luzernerhof and Brüelstrasse + + + Reisende zwischen Luzernerhof und Brüelstrasse erreichen ihr Ziel nur zu Fuß. Ab Luzernerhof und Brüelstrasse verkehren die Linie auf den normalen Fahrwegen. + Travellers between Luzernerhof and Brüelstrasse can only reach their destination on foot. From Luzernerhof and Brüelstrasse lines will run on regular routes. + + + Die Störung dauert bis ca.12:30 Uhr. + Disruption duration until 12:30pm. + + + Fällt aus + Cancelled + + + + + + + route + + + + + ch:vbl:014 + 14 + + ch:vbl:VBL014:A + Brüelstrasse + + + + ch:vbl:618::01 + Brüelstrasse + destination + + + + + + + + + open + 0310 + 2017-05-28T09:42:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Fahrt endet hier + Service terminates here + + + Einstieg der Linien 6 und 8 bei Kante C. Reisende nach Verkehrshaus und Dietschiberg erreichen ihr Ziel nur zu Fuß. + Board line 6 and 8 from platform C. Travellers to Verkehrshaus and Dietschiberg can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:024 + 24 + + ch:vbl:VBL014:A + Brüelstrasse + + + + ch:vbl:618::04 + Brüelstrasse + destination + + + + + + + + + open + 0320 + 2017-05-28T09:42:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Umleitung endet hier + Diversion ends here + + + Umstieg auf Linie 6 und 8: Einstieg bei Kante C. Reisende nach Verkehrshaus und Dietschiberg erreichen ihr Ziel nur zu Fuß. + Transfer to line 6 and 8: Board from platform C. Travellers to Verkehrshaus and Dietschiberg can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL006 + 06 + + ch:vbl:VBL006:A + Büttenenhalde + + + + ch:vbl:618::03 + Brüelstrasse + + + + + ch:vbl:VBL008 + 08 + + ch:vbl:VBL008:A + Würzenbach + + + + ch:vbl:618::03 + Brüelstrasse + + + + + + + + + open + 0330 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Normale Bedienung der Linien 6 bis Büttenenhalde und 8 bis Würzenbach. Es muss mit Verspätungen gerechnet werden. + Regular service on line 6 to Büttenenhalde and 8 to Würzenbach. Expect delays. + + + Die Störung dauert bis ca.12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:A + Büttenhalde + + + + ch:vbl:2502::01 + Giseli + + + ch:vbl:2503::01 + Oberseeburg + intermediate + + + ch:vbl:2504::01 + Oberseeburghöhe + intermediate + + + ch:vbl:2505::01 + Eggen + intermediate + + + ch:vbl:2506::01 + Büttenen + intermediate + + + ch:vbl:2507::01 + Büttenenhalde + destination + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:A + Würzenbach + + + + ch:vbl:619::01 + Würzenbachmatte + intermediate + + + ch:vbl:620::01 + Würzenbach + destination + + + + + + + + + open + 0340 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Es muss mit Verspätungen gerechnet werden. + Expect delays. + + + Die Störung dauert bis ca. 12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:Entlastungsbus + Entlastungsbus + + ch:vbl:VBL006:A + Büttenhalde + + + + ch:vbl:618::04 + Brüelstrasse + + + + + + + + + open + 0350 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Diese Fahrt endet hier + This service terminates here + + + Einstieg der Linien 6 und 8 bei Kante C. Reisende nach Verkehrshaus und Dietschiberg erreichen ihr Ziel nur zu Fuß. + Board line 6 and 8 from platform C. Travellers to Verkehrshaus and Dietschiberg can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:2507::01 + Büttenenhalde + origin + + + ch:vbl:2506::02 + Büttenen + intermediate + + + ch:vbl:2505::02 + Eggen + intermediate + + + ch:vbl:2504::02 + Oberseeburghöhe + intermediate + + + ch:vbl:2503::02 + Oberseeburg + intermediate + + + ch:vbl:2502::02 + Giseli + intermediate + + + + + + + + + open + 0390 + 2017-05-28T09:42:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Linie 6 fällt zwischen Brüelstrasse und Luzernerhof aus. + Line 6 cancelled between Brüelstrasse and Luzernerhof. + + + Reisende nach Luzernerhof oder weiter benützen die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte zwischen Brüelstrasse und Luzernerhof) oder die normal verkehrenden Linien 14 (mit Halten) und 73 bis Luzernerhof und steigen dort wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. + Travellers to Luzernerhof or further use the diverted line 24, additional buses (direct between Brühlstrasse and Luzernerhof), the regular line 14 services (all stop) or line 73 to Luzernhof and transfer there. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. + + + Die Störung dauert bis ca. 12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:2507::01 + Büttenenhalde + origin + + + ch:vbl:2506::02 + Büttenen + intermediate + + + ch:vbl:2505::02 + Eggen + intermediate + + + ch:vbl:2504::02 + Oberseeburghöhe + intermediate + + + ch:vbl:2503::02 + Oberseeburg + intermediate + + + ch:vbl:2502::02 + Giseli + intermediate + + + + + + + + + open + 0400 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Linie 6 fällt zwischen Brüelstrasse und Luzernerhof aus. + Line 6 cancelled between Brüelstrasse and Luzernerhof. + + + Reisende nach Luzernerhof oder weiter benützen die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte zwischen Brüelstrasse und Luzernerhof) oder die normal verkehrenden Linien 14 (mit Halten) und 73 bis Luzernerhof und steigen dort wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. + Travellers to Luzernerhof or further use the diverted line 24, the additional buses (direct between Brühlstrasse and Luzernerhof), the regular line 14 services (all stop) or line 73 to Luzernhof and transfer there. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. + + + Die Störung dauert bis ca. 12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:618::02 + Brüelstrasse + + + + + + + + + open + 0410 + 2017-05-28T09:42:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Linie 6 wendet hier + Line 6 turns here + + + Reisende zum Luzernerhof oder weiter benützen die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte bis Luzernerhof) oder die normal verkehrende Linie 14 (mit Halten) oder 73 ab Kante D und steigen beim Luzernerhof wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. + Travellers to Luzernerhof or further use the diverted line 24, addintional buses (direct to Luzernerhof), the regular line 14 services (all stops) or line 73 from platform D and transfer back to Luzernerhof. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:618::02 + Brüelstrasse + + + + + + + + + open + 0420 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8 + Line 6 and 8 disrupted + + + Reisende zum Luzernerhof oder weiter benützen die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte bis Luzernerhof) ab Kante D oder die normal verkehrenden Linien 14 (mit Halten) ab Kante D und 73 ab Kante C und steigen beim Luzernerhof wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. + Travellers to Luzernerhof or further use the diverted line 24, addintional buses (direct to Luzernerhof) from platform D, the regular line 14 services (all stops) from platform D or line 73 from platform C and transfer back to Luzernerhof. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. + + + Die Störung dauert bis ca. 12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:Entlastungsbus + Entlastungsbus + + ch:vbl:VBL006:A + Büttenhalde + + + + ch:vbl:VBL014 + 14 + + ch:vbl:VBL014:A + Brühlstrasse + + + + ch:vbl:618::01 + Brühlstrasse + destination + + + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:VBL024:B + Bahnhof + + + + ch:vbl:618::01 + Brühlstrasse + destination + + + + + + + + + open + 0430 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8; Umleitung der Linien 24. + Line 6 and 8 disrupted; Line 24 diverted. + + + Benutzen Sie die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte bis Luzernerhof) oder die normal verkehrenden Linien 14 (mit Halten) und 73 bis Luzernerhof. + Use diverted line 24 and additional buses (direct to Luzernerhof) or the regular line 14 (all stops) and line 73 to Luzernerhof. + + + Die Störung dauert bis ca. 12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:Entlastungsbus + Entlastungsbus + + ch:vbl:VBL006:A + Büttenhalde + + + + ch:vbl:121::03 + Luzernerhof + + + + + + + + + open + 0440 + 2017-05-28T09:42:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Diese Fahrt endet hier + This service terminates here + + + Einstieg der Linien 6 und 8 bei Kante A. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Board line 6 and 8 from platform A. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + Die Störung dauert bis ca. 12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:VBL024:B + Bahnhof + + + + ch:vbl:121::04 + Luzernerhof + origin + + + + + + + + + open + 0450 + 2017-05-28T09:42:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Umleitung endet hier + Diversion ends here + + + Umstieg auf Linie 6 und 8: Einstieg bei Kante A. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Transfer to line 6 and 8: Board from platform A. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL014 + 14 + + ch:vbl:VBL014:B + Horw Zentrum + + + + ch:vbl:121::03 + Luzernerhof + intermediate + + + + + + + + + open + 0455 + 2017-05-28T09:42:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + + + Umstieg auf Linie 6 und 8: Einstieg bei Kante A. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + + + + + + + route + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:VBL024:B + Bahnhof + + + + ch:vbl:121::03 + Luzernerhof + origin + + + + + + + + + open + 0460 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Umleitung endet hier + Diversion ends here + + + Umstieg auf die Linien 6 und 8: Einstieg bei Kante A. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Transfer to line 6 and 8: Board from platform A. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:121::04 + Luzernerhof + origin + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:B + Hiertenhof + + + + ch:vbl:121::04 + Luzernerhof + origin + + + + + + + + + open + 0470 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Normale Bedienung der Linien 6 bis Matthof und 8 bis Hirtenhof. Es muss mit Verspätungen gerechnet werden. + Regular service on line 6 to Matthof and line 8 to Hirtenhof. Expect delays. + + + Die Störung dauert bis ca. 12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:120::02 + Schwanenplatz + intermediate + + + ch:vbl:119::01 + Bahnhof + intermediate + + + ch:vbl:118::02 + Kantonalbank + intermediate + + + ch:vbl:407::03 + Bundesplatz + intermediate + + + ch:vbl:606::02 + Werkhofstrasse + intermediate + + + ch:vbl:605::02 + Weinbergli + intermediate + + + ch:vbl:604::02 + Eisfeldstrasse + intermediate + + + ch:vbl:603::02 + Wartegg + intermediate + + + ch:vbl:602::02 + Schönbühl + intermediate + + + ch:vbl:601::01 + Matthof + destination + + + + + + + + + open + 0480 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Es muss mit Verspätungen gerechnet werden. + Expect delays. + + + Die Störung dauert bis ca. 12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + line + + + + + ch:vbl:VBL002 + 2 + + + ch:vbl:VBL002:A + Bahnhof + + + + ch:vbl:119::06 + Bahnhof + destination + + + + + + + + + open + 0481 + 2017-05-28T09:42:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8 + Line 6 and 8 disrupted + + + Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die Linien 14 oder 73 und steigen Sie an der Brüelstrasse wieder um. Reisende nach dem Verkehrshaus benutzen die S3 oder das Schiff. + Transfer advice line 6 and 8: Use line 14 or 73 to Brüelstrasse and transfer back to line 6 and 8. Travellers to Verkehrshaus use the S3 or ferry. + + + Die Störung dauert bis ca. 12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:VBL014 + 14 + + ch:vbl:VBL014:A + Brüelstrasse + + + + ch:vbl:119::08 + Bahnhof + intermediate + + + + + + + + + open + 0482 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8 + Line 6 and 8 disrupted + + + Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die Linien 14 oder 73 und steigen Sie an der Brüelstrasse wieder um. Reisende nach dem Verkehrshaus benutzen die S3 oder das Schiff. + Transfer advice line 6 and 8: Use line 14 or 73 to Brüelstrasse and transfer back to line 6 and 8. Travellers to Verkehrshaus use the S3 or ferry. + + + Die Störung dauert bis ca. 12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + + +       +       diff --git a/examples/siri_exm_SX/VDV736_exm/SX_1247_end_message.xml b/examples/siri_exm_SX/VDV736_exm/SX_1247_end_message.xml index d8319ff2..ec713b1a 100644 --- a/examples/siri_exm_SX/VDV736_exm/SX_1247_end_message.xml +++ b/examples/siri_exm_SX/VDV736_exm/SX_1247_end_message.xml @@ -1,397 +1,397 @@ - - - - 2018-10-04T12:22:00+00:00 - ch:VBL -
      http:/server/siri/20_ums
      - JFI2d2mWP - true - false - - 2018-10-04T12:22:00+00:00 - ch:VBL - 40599x2dsjmu8yjzy - - - 2017-05-28T12:22:00+02:00 - VBL - 1 - 5 - - feed - VBL - - closing - - - 2017-05-28T12:22:00+02:00 - 2017-05-28T17:10:00+02:00 - - fire - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - 3 - line - false - DE - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line interruption between Luzernerhof and Verkehrshaus - - - - ch:vbl:622 - Haldensteig - - - - - - disturbanceRectified - - - - - ch:vbl:VBL006 - 6 - - - ch:vbl:VBL008 - 8 - - - ch:vbl:VBL024 - 24 - - - - - - false - - - - - - - line - - - - - ch:vbl:VBL006 - 6 - - - ch:vbl:VBL008 - 8 - - - ch:vbl:VBL024 - 14 - - - ch:vbl:VBL024 - 24 - - - ch:vbl:VBL024 - 73 - - - - - - - open - 0510 - 2017-05-28T12:22:00+02:00 - 1 - vbl - VBL - general - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line interruption between Luzernerhof and Verkehrshaus - - - Der Streckenunterbruch zwischen Luzernerhof und Brüelstrasse ist behoben. - The route disruption between Luzernerhof and Brüelstrasse is resolved. - - - Die Linien 6, 8, 24 und 73 verkehren wieder gemäß Fahrplan. - Line 6, 8, 24 and 73 are back to regular service. - - - - - - - line - - - - - ch:vbl:VBL006 - 6 - - - ch:vbl:VBL008 - 8 - - - ch:vbl:VBL024 - 14 - - - ch:vbl:VBL024 - 24 - - - ch:vbl:VBL024 - 73 - - - - - - - open - 0510 - 2017-05-28T12:22:00+02:00 - 1 - vbl - VBL - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line interruption between Luzernerhof and Verkehrshaus - - - Der Streckenunterbruch zwischen Luzernerhof und Brüelstrasse ist behoben. - The route disruption between Luzernerhof and Brüelstrasse is resolved. - - - Die Linien 6, 8, 24 und 73 verkehren wieder gemäß Fahrplan. - Line 6, 8, 24 and 73 are back to regular service. - - - - - - - line - - - - - ch:vbl:VBL006 - 6 - - - ch:vbl:VBL008 - 8 - - - ch:vbl:VBL024 - 14 - - - ch:vbl:VBL024 - 24 - - - ch:vbl:VBL024 - 73 - - - - - - - open - 0510 - 2017-05-28T12:22:00+02:00 - 1 - vbl - VBL - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line interruption between Luzernerhof and Verkehrshaus - - - Der Streckenunterbruch zwischen Luzernerhof und Brüelstrasse ist behoben. - The route disruption between Luzernerhof and Brüelstrasse is resolved. - - - Die Linien 6, 8, 24 und 73 verkehren wieder gemäß Fahrplan. - Line 6, 8, 24 and 73 are back to regular service. - - - - - - - line - - - - - ch:vbl:VBL006 - 6 - - - ch:vbl:VBL008 - 8 - - - ch:vbl:VBL024 - 24 - - - - - - - open - - 2017-05-28T12:47:00+02:00 - 2017-05-28T13:15:00+02:00 - - 0510 - 2017-05-28T12:47:00+02:00 - 1 - vbl - VBL - general - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line interruption between Luzernerhof and Verkehrshaus - - - Der Streckenunterbruch zwischen Luzernerhof und Brüelstrasse ist behoben. - The route disruption between Luzernerhof and Brüelstrasse is resolved. - - - Die Linien 6, 8, 24 und 73 verkehren wieder gemäß Fahrplan. - Line 6, 8, 24 and 73 are back to regular service. - - - - - - - line - - - - - ch:vbl:VBL006 - 6 - - - ch:vbl:VBL008 - 8 - - - ch:vbl:VBL024 - 24 - - - - - - - open - - 2017-05-28T12:47:00+02:00 - 2017-05-28T13:15:00+02:00 - - 0510 - 2017-05-28T12:47:00+02:00 - 1 - vbl - VBL - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line interruption between Luzernerhof and Verkehrshaus - - - Der Streckenunterbruch zwischen Luzernerhof und Brüelstrasse ist behoben. - The route disruption between Luzernerhof and Brüelstrasse is resolved. - - - Die Linien 6, 8, 24 und 73 verkehren wieder gemäß Fahrplan. - Line 6, 8, 24 and 73 are back to regular service. - - - - - - - line - - - - - ch:vbl:VBL006 - 6 - - - ch:vbl:VBL008 - 8 - - - ch:vbl:VBL024 - 24 - - - - - - - open - - 2017-05-28T12:47:00+02:00 - 2017-05-28T13:15:00+02:00 - - 0510 - 2017-05-28T12:47:00+02:00 - 1 - vbl - VBL - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line interruption between Luzernerhof and Verkehrshaus - - - Der Streckenunterbruch zwischen Luzernerhof und Brüelstrasse ist behoben. - The route disruption between Luzernerhof and Brüelstrasse is resolved. - - - Die Linien 6, 8, 24 und 73 verkehren wieder gemäß Fahrplan. - Line 6, 8, 24 and 73 are back to regular service. - - - - - - - - -       -       + + + + 2018-10-04T12:22:00+00:00 + ch:VBL +
      http:/server/siri/20_ums
      + JFI2d2mWP + true + false + + 2018-10-04T12:22:00+00:00 + ch:VBL + 40599x2dsjmu8yjzy + + + 2017-05-28T12:22:00+02:00 + VBL + 1 + 5 + + feed + VBL + + closing + + + 2017-05-28T12:22:00+02:00 + 2017-05-28T17:10:00+02:00 + + fire + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + 3 + line + false + DE + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line interruption between Luzernerhof and Verkehrshaus + + + + ch:vbl:622 + Haldensteig + + + + + + disturbanceRectified + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 24 + + + + + + false + + + + + + + line + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 14 + + + ch:vbl:VBL024 + 24 + + + ch:vbl:VBL024 + 73 + + + + + + + open + 0510 + 2017-05-28T12:22:00+02:00 + 1 + vbl + VBL + general + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line interruption between Luzernerhof and Verkehrshaus + + + Der Streckenunterbruch zwischen Luzernerhof und Brüelstrasse ist behoben. + The route disruption between Luzernerhof and Brüelstrasse is resolved. + + + Die Linien 6, 8, 24 und 73 verkehren wieder gemäß Fahrplan. + Line 6, 8, 24 and 73 are back to regular service. + + + + + + + line + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 14 + + + ch:vbl:VBL024 + 24 + + + ch:vbl:VBL024 + 73 + + + + + + + open + 0510 + 2017-05-28T12:22:00+02:00 + 1 + vbl + VBL + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line interruption between Luzernerhof and Verkehrshaus + + + Der Streckenunterbruch zwischen Luzernerhof und Brüelstrasse ist behoben. + The route disruption between Luzernerhof and Brüelstrasse is resolved. + + + Die Linien 6, 8, 24 und 73 verkehren wieder gemäß Fahrplan. + Line 6, 8, 24 and 73 are back to regular service. + + + + + + + line + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 14 + + + ch:vbl:VBL024 + 24 + + + ch:vbl:VBL024 + 73 + + + + + + + open + 0510 + 2017-05-28T12:22:00+02:00 + 1 + vbl + VBL + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line interruption between Luzernerhof and Verkehrshaus + + + Der Streckenunterbruch zwischen Luzernerhof und Brüelstrasse ist behoben. + The route disruption between Luzernerhof and Brüelstrasse is resolved. + + + Die Linien 6, 8, 24 und 73 verkehren wieder gemäß Fahrplan. + Line 6, 8, 24 and 73 are back to regular service. + + + + + + + line + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 24 + + + + + + + open + + 2017-05-28T12:47:00+02:00 + 2017-05-28T13:15:00+02:00 + + 0510 + 2017-05-28T12:47:00+02:00 + 1 + vbl + VBL + general + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line interruption between Luzernerhof and Verkehrshaus + + + Der Streckenunterbruch zwischen Luzernerhof und Brüelstrasse ist behoben. + The route disruption between Luzernerhof and Brüelstrasse is resolved. + + + Die Linien 6, 8, 24 und 73 verkehren wieder gemäß Fahrplan. + Line 6, 8, 24 and 73 are back to regular service. + + + + + + + line + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 24 + + + + + + + open + + 2017-05-28T12:47:00+02:00 + 2017-05-28T13:15:00+02:00 + + 0510 + 2017-05-28T12:47:00+02:00 + 1 + vbl + VBL + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line interruption between Luzernerhof and Verkehrshaus + + + Der Streckenunterbruch zwischen Luzernerhof und Brüelstrasse ist behoben. + The route disruption between Luzernerhof and Brüelstrasse is resolved. + + + Die Linien 6, 8, 24 und 73 verkehren wieder gemäß Fahrplan. + Line 6, 8, 24 and 73 are back to regular service. + + + + + + + line + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 24 + + + + + + + open + + 2017-05-28T12:47:00+02:00 + 2017-05-28T13:15:00+02:00 + + 0510 + 2017-05-28T12:47:00+02:00 + 1 + vbl + VBL + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line interruption between Luzernerhof and Verkehrshaus + + + Der Streckenunterbruch zwischen Luzernerhof und Brüelstrasse ist behoben. + The route disruption between Luzernerhof and Brüelstrasse is resolved. + + + Die Linien 6, 8, 24 und 73 verkehren wieder gemäß Fahrplan. + Line 6, 8, 24 and 73 are back to regular service. + + + + + + + + +       +       diff --git a/examples/siri_exm_SX/exx_situationExchangeResponse.xml b/examples/siri_exm_SX/exx_situationExchangeResponse.xml index c07a9368..d43b823a 100644 --- a/examples/siri_exm_SX/exx_situationExchangeResponse.xml +++ b/examples/siri_exm_SX/exx_situationExchangeResponse.xml @@ -1,280 +1,280 @@ - - - - - - 2004-12-17T09:30:46-05:00 - KUBRICK - true - false - - - 2004-12-17T09:30:46-05:00 - - - 2001-12-17T09:30:47.0Z - de - RAILCO01 - 000354 - 0 - - - 2001-12-17T09:30:47.0Z - de - RAILCO01 - 000354 - 0 - - - - de - phone - 01223333337654 - 03274 - 2001-12-17T09:30:47.0Z - - verified - open - certain - - 2001-12-17T09:30:47.0Z - 2001-12-17T10:30:47.0Z - - bombExplosion - severe - 3 - public - point - Bomb at Barchester station - Building evacuated. Avoid station until further notice - - - - - - - BAAR0003 - Barchester Station - unknown - - -180 - -90 - 1 - - - - - - BArF001 - - - BAR00021 - Platfrom 3 - - - - - - - - - 2001-12-17T09:30:47.0Z - 2001-12-17T10:30:47.0Z - - unknown - unknown - - true - true - - - noAlighting - noBoarding - - - - - - true - true - false - - - true - false - - - true - true - true - - - - - - 2001-12-17T09:30:47.0Z - de - RAILCO01 - 000354 - 0 - - - 2001-12-17T09:30:47.0Z - de - RAILCO01 - 000354 - 0 - - - - de - phone - 01223333337654 - 03274 - 2001-12-17T09:30:47.0Z - - verified - open - certain - - 2001-12-17T09:30:47.0Z - 2001-12-17T10:30:47.0Z - - bombExplosion - severe - 3 - public - point - Jam on the access road to Barchester Station - Grislock and panic - - - - - - - BAAR0003 - Barchester Station - unknown - - -180 - -90 - 1 - - - - - - BArF001 - - - BAR00021 - Platfrom 3 - - - - - - - - - 2001-12-17T09:30:47.0Z - 2001-12-17T10:30:47.0Z - - delay - severe - - - - - true - true - false - - - true - false - - - true - true - true - - - - - - - - - + + + + + + 2004-12-17T09:30:46-05:00 + KUBRICK + true + false + + + 2004-12-17T09:30:46-05:00 + + + 2001-12-17T09:30:47.0Z + de + RAILCO01 + 000354 + 0 + + + 2001-12-17T09:30:47.0Z + de + RAILCO01 + 000354 + 0 + + + + de + phone + 01223333337654 + 03274 + 2001-12-17T09:30:47.0Z + + verified + open + certain + + 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z + + bombExplosion + severe + 3 + public + point + Bomb at Barchester station + Building evacuated. Avoid station until further notice + + + + + + + BAAR0003 + Barchester Station + unknown + + -180 + -90 + 1 + + + + + + BArF001 + + + BAR00021 + Platfrom 3 + + + + + + + + + 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z + + unknown + unknown + + true + true + + + noAlighting + noBoarding + + + + + + true + true + false + + + true + false + + + true + true + true + + + + + + 2001-12-17T09:30:47.0Z + de + RAILCO01 + 000354 + 0 + + + 2001-12-17T09:30:47.0Z + de + RAILCO01 + 000354 + 0 + + + + de + phone + 01223333337654 + 03274 + 2001-12-17T09:30:47.0Z + + verified + open + certain + + 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z + + bombExplosion + severe + 3 + public + point + Jam on the access road to Barchester Station + Grislock and panic + + + + + + + BAAR0003 + Barchester Station + unknown + + -180 + -90 + 1 + + + + + + BArF001 + + + BAR00021 + Platfrom 3 + + + + + + + + + 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z + + delay + severe + + + + + true + true + false + + + true + false + + + true + true + true + + + + + + + + + diff --git a/examples/siri_exm_SX/exx_situationExchange_ATOC.xml b/examples/siri_exm_SX/exx_situationExchange_ATOC.xml index 24dcd168..8318ce35 100644 --- a/examples/siri_exm_SX/exx_situationExchange_ATOC.xml +++ b/examples/siri_exm_SX/exx_situationExchange_ATOC.xml @@ -1,101 +1,101 @@ - - - - 2001-12-17T09:30:47.0Z - de - RAILCO01 - 000354 - 0 - - - 2001-12-17T09:30:47.0Z - de - RAILCO01 - 000354 - 0 - - - - de - phone - 01223333337654 - 03274 - 2001-12-17T09:30:47.0Z - - verified - open - certain - - 2001-12-17T09:30:47.0Z - 2001-12-17T10:30:47.0Z - - bombExplosion - severe - 3 - public - point - Bomb at Barchester station - Building evacuated. Avoid station until further notice - - - - - - - BAAR0003 - Barchester Station - unknown - - -180 - -90 - 1 - - - - - - BArF001 - - - BAR00021 - Platform 3 - - - - - - - - - 2001-12-17T09:30:47.0Z - 2001-12-17T10:30:47.0Z - - delay - severe - - true - true - - - noAlighting - noBoarding - - - - - - true - true - false - - - true - false - - - true - true - true - - - + + + + 2001-12-17T09:30:47.0Z + de + RAILCO01 + 000354 + 0 + + + 2001-12-17T09:30:47.0Z + de + RAILCO01 + 000354 + 0 + + + + de + phone + 01223333337654 + 03274 + 2001-12-17T09:30:47.0Z + + verified + open + certain + + 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z + + bombExplosion + severe + 3 + public + point + Bomb at Barchester station + Building evacuated. Avoid station until further notice + + + + + + + BAAR0003 + Barchester Station + unknown + + -180 + -90 + 1 + + + + + + BArF001 + + + BAR00021 + Platform 3 + + + + + + + + + 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z + + delay + severe + + true + true + + + noAlighting + noBoarding + + + + + + true + true + false + + + true + false + + + true + true + true + + + diff --git a/examples/siri_exm_SX/exx_situationExchange_Pt.xml b/examples/siri_exm_SX/exx_situationExchange_Pt.xml index cb32c9a3..89b9dba4 100644 --- a/examples/siri_exm_SX/exx_situationExchange_Pt.xml +++ b/examples/siri_exm_SX/exx_situationExchange_Pt.xml @@ -1,101 +1,101 @@ - - - - 2001-12-17T09:30:47.0Z - de - RAILCO01 - 000354 - 0 - - - 2001-12-17T09:30:47.0Z - de - RAILCO01 - 000354 - 0 - - - - de - phone - 01223333337654 - 03274 - 2001-12-17T09:30:47.0Z - - verified - open - certain - - 2001-12-17T09:30:47.0Z - 2001-12-17T10:30:47.0Z - - bombExplosion - severe - 3 - public - point - Bomb at Barchester station - Building evacuated. Avoid station until further notice - - - - - - - BAAR0003 - Barchester Station - unknown - - -180 - -90 - 1 - - - - - - BArF001 - - - BAR00021 - Platfrom 3 - - - - - - - - - 2001-12-17T09:30:47.0Z - 2001-12-17T10:30:47.0Z - - delay - severe - - true - true - - - noAlighting - noBoarding - - - - - - true - true - false - - - true - false - - - true - true - true - - - + + + + 2001-12-17T09:30:47.0Z + de + RAILCO01 + 000354 + 0 + + + 2001-12-17T09:30:47.0Z + de + RAILCO01 + 000354 + 0 + + + + de + phone + 01223333337654 + 03274 + 2001-12-17T09:30:47.0Z + + verified + open + certain + + 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z + + bombExplosion + severe + 3 + public + point + Bomb at Barchester station + Building evacuated. Avoid station until further notice + + + + + + + BAAR0003 + Barchester Station + unknown + + -180 + -90 + 1 + + + + + + BArF001 + + + BAR00021 + Platfrom 3 + + + + + + + + + 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z + + delay + severe + + true + true + + + noAlighting + noBoarding + + + + + + true + true + false + + + true + false + + + true + true + true + + + diff --git a/examples/siri_exm_SX/exx_situationExchange_capabilityResponse.xml b/examples/siri_exm_SX/exx_situationExchange_capabilityResponse.xml index 5c224c5f..f54f6856 100644 --- a/examples/siri_exm_SX/exx_situationExchange_capabilityResponse.xml +++ b/examples/siri_exm_SX/exx_situationExchange_capabilityResponse.xml @@ -1,69 +1,69 @@ - - - - 2001-12-17T09:30:47-05:00 - http://www.mytransportco.eu - true - - - cpidId001 - - String - - - - - true - true - - - true - false - - true - true - false - false - - - PT60M - false - true - true - - - en-uk - - - - false - - - - - - - - true - true - - - true - - - true - - - - - NADER - - true - - - true - - - - - + + + + 2001-12-17T09:30:47-05:00 + http://www.mytransportco.eu + true + + + cpidId001 + + String + + + + + true + true + + + true + false + + true + true + false + false + + + PT60M + false + true + true + + + en-uk + + + + false + + + + + + + + true + true + + + true + + + true + + + + + NADER + + true + + + true + + + + + diff --git a/examples/siri_exm_SX/exx_situationExchange_request.xml b/examples/siri_exm_SX/exx_situationExchange_request.xml index b17fdad1..4749cd84 100644 --- a/examples/siri_exm_SX/exx_situationExchange_request.xml +++ b/examples/siri_exm_SX/exx_situationExchange_request.xml @@ -1,32 +1,32 @@ - - - - - - - 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 - - - - + + + + + + + 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 + + + + diff --git a/examples/siri_exm_SX/exx_situationExchange_request_simple.xml b/examples/siri_exm_SX/exx_situationExchange_request_simple.xml index f1e2158d..5ed7ee31 100644 --- a/examples/siri_exm_SX/exx_situationExchange_request_simple.xml +++ b/examples/siri_exm_SX/exx_situationExchange_request_simple.xml @@ -1,21 +1,21 @@ - - - - - 2004-12-17T09:30:47-05:00 - NADER - - 2004-12-17T09:30:47-05:00 - - line - 52 - - - - + + + + + 2004-12-17T09:30:47-05:00 + NADER + + 2004-12-17T09:30:47-05:00 + + line + 52 + + + + diff --git a/examples/siri_exm_SX/exx_situationExchange_response.xml b/examples/siri_exm_SX/exx_situationExchange_response.xml index 431a5e05..bb15c8a8 100644 --- a/examples/siri_exm_SX/exx_situationExchange_response.xml +++ b/examples/siri_exm_SX/exx_situationExchange_response.xml @@ -1,278 +1,278 @@ - - - - - - 2004-12-17T09:30:46-05:00 - KUBRICK - true - false - - - 2004-12-17T09:30:46-05:00 - - - 2001-12-17T09:30:47.0Z - de - RAILCO01 - 000354 - 0 - - - 2001-12-17T09:30:47.0Z - de - RAILCO01 - 000354 - 0 - - - - de - phone - 01223333337654 - 03274 - 2001-12-17T09:30:47.0Z - - verified - open - certain - - 2001-12-17T09:30:47.0Z - 2001-12-17T10:30:47.0Z - - bombExplosion - severe - 3 - public - point - Bomb at Barchester station - Building evacuated. Avoid station until further notice - - - - - - - BAAR0003 - Barchester Station - unknown - - -180 - -90 - 1 - - - - - - BArF001 - - - BAR00021 - Platfrom 3 - - - - - - - - - 2001-12-17T09:30:47.0Z - 2001-12-17T10:30:47.0Z - - unknown - unknown - - true - true - - - noAlighting - noBoarding - - - - - - true - true - false - - - true - false - - - true - true - true - - - - - - 2001-12-17T09:30:47.0Z - de - RAILCO01 - 000354 - 0 - - - 2001-12-17T09:30:47.0Z - de - RAILCO01 - 000354 - 0 - - - - de - phone - 01223333337654 - 03274 - 2001-12-17T09:30:47.0Z - - verified - open - certain - - 2001-12-17T09:30:47.0Z - 2001-12-17T10:30:47.0Z - - bombExplosion - severe - 3 - public - point - Jam on the access road to Barchester Station - Grislock and panic - - - - - - - BAAR0003 - Barchester Station - unknown - - -180 - -90 - 1 - - - - - - BArF001 - - - BAR00021 - Platfrom 3 - - - - - - - - - 2001-12-17T09:30:47.0Z - 2001-12-17T10:30:47.0Z - - delay - severe - - - - - true - true - false - - - true - false - - - true - true - true - - - - - - - - - + + + + + + 2004-12-17T09:30:46-05:00 + KUBRICK + true + false + + + 2004-12-17T09:30:46-05:00 + + + 2001-12-17T09:30:47.0Z + de + RAILCO01 + 000354 + 0 + + + 2001-12-17T09:30:47.0Z + de + RAILCO01 + 000354 + 0 + + + + de + phone + 01223333337654 + 03274 + 2001-12-17T09:30:47.0Z + + verified + open + certain + + 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z + + bombExplosion + severe + 3 + public + point + Bomb at Barchester station + Building evacuated. Avoid station until further notice + + + + + + + BAAR0003 + Barchester Station + unknown + + -180 + -90 + 1 + + + + + + BArF001 + + + BAR00021 + Platfrom 3 + + + + + + + + + 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z + + unknown + unknown + + true + true + + + noAlighting + noBoarding + + + + + + true + true + false + + + true + false + + + true + true + true + + + + + + 2001-12-17T09:30:47.0Z + de + RAILCO01 + 000354 + 0 + + + 2001-12-17T09:30:47.0Z + de + RAILCO01 + 000354 + 0 + + + + de + phone + 01223333337654 + 03274 + 2001-12-17T09:30:47.0Z + + verified + open + certain + + 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z + + bombExplosion + severe + 3 + public + point + Jam on the access road to Barchester Station + Grislock and panic + + + + + + + BAAR0003 + Barchester Station + unknown + + -180 + -90 + 1 + + + + + + BArF001 + + + BAR00021 + Platfrom 3 + + + + + + + + + 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z + + delay + severe + + + + + true + true + false + + + true + false + + + true + true + true + + + + + + + + + diff --git a/examples/siri_exm_SX/exx_situationExchange_road.xml b/examples/siri_exm_SX/exx_situationExchange_road.xml index e8bfb7d0..6560d66c 100644 --- a/examples/siri_exm_SX/exx_situationExchange_road.xml +++ b/examples/siri_exm_SX/exx_situationExchange_road.xml @@ -1,204 +1,204 @@ - - - - 2001-12-17T09:30:47.0Z - de - RAILCO01 - 000354 - 0 - - - 2001-12-17T09:30:47.0Z - de - RAILCO01 - 000354 - 0 - - - - de - phone - 01223333337654 - 03274 - 2001-12-17T09:30:47.0Z - - verified - open - certain - - 2001-12-17T09:30:47.0Z - 2001-12-17T10:30:47.0Z - - bombExplosion - severe - 3 - public - point - Jam on the access road to Barchester Station - Grislock and panic - - - - - - - BAAR0003 - Barchester Station - unknown - - -180 - -90 - 1 - - - - - - BArF001 - - - BAR00021 - Platfrom 3 - - - - - - - - - 2001-12-17T09:30:47.0Z - 2001-12-17T10:30:47.0Z - - delay - severe - - - - - true - true - false - - - true - false - - - true - true - true - - - - + + + + 2001-12-17T09:30:47.0Z + de + RAILCO01 + 000354 + 0 + + + 2001-12-17T09:30:47.0Z + de + RAILCO01 + 000354 + 0 + + + + de + phone + 01223333337654 + 03274 + 2001-12-17T09:30:47.0Z + + verified + open + certain + + 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z + + bombExplosion + severe + 3 + public + point + Jam on the access road to Barchester Station + Grislock and panic + + + + + + + BAAR0003 + Barchester Station + unknown + + -180 + -90 + 1 + + + + + + BArF001 + + + BAR00021 + Platfrom 3 + + + + + + + + + 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z + + delay + severe + + + + + true + true + false + + + true + false + + + true + true + true + + + + diff --git a/examples/siri_exm_SX/exx_situationExchange_subscriptionRequest.xml b/examples/siri_exm_SX/exx_situationExchange_subscriptionRequest.xml index 0faa2997..7670c3cf 100644 --- a/examples/siri_exm_SX/exx_situationExchange_subscriptionRequest.xml +++ b/examples/siri_exm_SX/exx_situationExchange_subscriptionRequest.xml @@ -1,20 +1,20 @@ - - - - - 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 - - - - + + + + + 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 + + + + diff --git a/examples/siri_exm_VM/exv_vehicleMonitoring_capabilitiesResponse.xml b/examples/siri_exm_VM/exv_vehicleMonitoring_capabilitiesResponse.xml index 997d3fd4..1d45773f 100644 --- a/examples/siri_exm_VM/exv_vehicleMonitoring_capabilitiesResponse.xml +++ b/examples/siri_exm_VM/exv_vehicleMonitoring_capabilitiesResponse.xml @@ -1,80 +1,80 @@ - - - - 2001-12-17T09:30:47.0Z - http://www.mytransportco.eu - true - - - cpidId001 - - 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 - - - - - - + + + + 2001-12-17T09:30:47.0Z + http://www.mytransportco.eu + true + + + cpidId001 + + 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/examples/siri_exm_VM/exv_vehicleMonitoring_request.xml b/examples/siri_exm_VM/exv_vehicleMonitoring_request.xml index 663b72fb..5461b910 100644 --- a/examples/siri_exm_VM/exv_vehicleMonitoring_request.xml +++ b/examples/siri_exm_VM/exv_vehicleMonitoring_request.xml @@ -1,34 +1,34 @@ - - - - - - - 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 - true - - - + + + + + + + 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 + true + + + diff --git a/examples/siri_exm_VM/exv_vehicleMonitoring_request_simple.xml b/examples/siri_exm_VM/exv_vehicleMonitoring_request_simple.xml index d8b582e5..0d67ca33 100644 --- a/examples/siri_exm_VM/exv_vehicleMonitoring_request_simple.xml +++ b/examples/siri_exm_VM/exv_vehicleMonitoring_request_simple.xml @@ -1,22 +1,22 @@ - - - - - - 2004-12-17T09:30:47-05:00 - NADER - - 2004-12-17T09:30:47-05:00 - - VEHPT55 - - basic - - - + + + + + + 2004-12-17T09:30:47-05:00 + NADER + + 2004-12-17T09:30:47-05:00 + + VEHPT55 + + basic + + + diff --git a/examples/siri_exm_VM/exv_vehicleMonitoring_response.xml b/examples/siri_exm_VM/exv_vehicleMonitoring_response.xml index f795043c..b9a14d7e 100644 --- a/examples/siri_exm_VM/exv_vehicleMonitoring_response.xml +++ b/examples/siri_exm_VM/exv_vehicleMonitoring_response.xml @@ -1,159 +1,159 @@ - - - - - - 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 - VEH987659 - - - - HLTST012 - Church - - - - - - - 2004-12-17T09:30:47-05:00 - 9876542 - - 2001-12-17 - 09867 - - Line123 - Out - Gone home - - hello delivery - - - + + + + + + 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 + VEH987659 + + + + HLTST012 + Church + + + + + + + 2004-12-17T09:30:47-05:00 + 9876542 + + 2001-12-17 + 09867 + + Line123 + Out + Gone home + + hello delivery + + + diff --git a/examples/siri_exm_VM/exv_vehicleMonitoring_response_simple.xml b/examples/siri_exm_VM/exv_vehicleMonitoring_response_simple.xml index 2eb28333..acec57c4 100644 --- a/examples/siri_exm_VM/exv_vehicleMonitoring_response_simple.xml +++ b/examples/siri_exm_VM/exv_vehicleMonitoring_response_simple.xml @@ -1,62 +1,62 @@ - - - - - - 2004-12-17T09:30:47-05:00 - NADER - - - 2004-12-17T09:30:47-05:00 - NADER - 00047 - - 2004-12-17T09:30:47-05:00 - 2004-12-17T09:30:47-05:00 - ACT019456 - - - Line123 - - 2004-12-17 - 987675 - - 123 - - 0.1 - 53.55 - - 123 - VEH987654 - - - - - 2004-12-17T09:30:47-05:00 - 2004-12-17T09:30:47-05:00 - MYACACT - - - - Line123 - - 2004-12-17 - Outbound - - - 0 - 53.5 - - 70 - VEH987659 - - - - - + + + + + + 2004-12-17T09:30:47-05:00 + NADER + + + 2004-12-17T09:30:47-05:00 + NADER + 00047 + + 2004-12-17T09:30:47-05:00 + 2004-12-17T09:30:47-05:00 + ACT019456 + + + Line123 + + 2004-12-17 + 987675 + + 123 + + 0.1 + 53.55 + + 123 + VEH987654 + + + + + 2004-12-17T09:30:47-05:00 + 2004-12-17T09:30:47-05:00 + MYACACT + + + + Line123 + + 2004-12-17 + Outbound + + + 0 + 53.5 + + 70 + VEH987659 + + + + + diff --git a/examples/siri_exm_VM/exv_vehicleMonitoring_responsex_simple.xml b/examples/siri_exm_VM/exv_vehicleMonitoring_responsex_simple.xml index 2eb28333..acec57c4 100644 --- a/examples/siri_exm_VM/exv_vehicleMonitoring_responsex_simple.xml +++ b/examples/siri_exm_VM/exv_vehicleMonitoring_responsex_simple.xml @@ -1,62 +1,62 @@ - - - - - - 2004-12-17T09:30:47-05:00 - NADER - - - 2004-12-17T09:30:47-05:00 - NADER - 00047 - - 2004-12-17T09:30:47-05:00 - 2004-12-17T09:30:47-05:00 - ACT019456 - - - Line123 - - 2004-12-17 - 987675 - - 123 - - 0.1 - 53.55 - - 123 - VEH987654 - - - - - 2004-12-17T09:30:47-05:00 - 2004-12-17T09:30:47-05:00 - MYACACT - - - - Line123 - - 2004-12-17 - Outbound - - - 0 - 53.5 - - 70 - VEH987659 - - - - - + + + + + + 2004-12-17T09:30:47-05:00 + NADER + + + 2004-12-17T09:30:47-05:00 + NADER + 00047 + + 2004-12-17T09:30:47-05:00 + 2004-12-17T09:30:47-05:00 + ACT019456 + + + Line123 + + 2004-12-17 + 987675 + + 123 + + 0.1 + 53.55 + + 123 + VEH987654 + + + + + 2004-12-17T09:30:47-05:00 + 2004-12-17T09:30:47-05:00 + MYACACT + + + + Line123 + + 2004-12-17 + Outbound + + + 0 + 53.5 + + 70 + VEH987659 + + + + + diff --git a/examples/siri_exm_VM/exv_vehicleMonitoring_subscriptionRequest.xml b/examples/siri_exm_VM/exv_vehicleMonitoring_subscriptionRequest.xml index d385ae88..76bbfaba 100644 --- a/examples/siri_exm_VM/exv_vehicleMonitoring_subscriptionRequest.xml +++ b/examples/siri_exm_VM/exv_vehicleMonitoring_subscriptionRequest.xml @@ -1,34 +1,34 @@ - - - - - - 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 - - - + + + + + + 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 + + + diff --git a/examples/siri_exu_capability/exd_allServices_capabilitiesRequest.xml b/examples/siri_exu_capability/exd_allServices_capabilitiesRequest.xml index 40f13a4c..5db39348 100644 --- a/examples/siri_exu_capability/exd_allServices_capabilitiesRequest.xml +++ b/examples/siri_exu_capability/exd_allServices_capabilitiesRequest.xml @@ -1,38 +1,38 @@ - - - - - 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 - - - + + + + + 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/examples/siri_exu_capability/exd_allServices_capabilitiesResponse.xml b/examples/siri_exu_capability/exd_allServices_capabilitiesResponse.xml index 74143dac..17ef992e 100644 --- a/examples/siri_exu_capability/exd_allServices_capabilitiesResponse.xml +++ b/examples/siri_exu_capability/exd_allServices_capabilitiesResponse.xml @@ -1,494 +1,494 @@ - - - - - 2004-12-17T09:30:47-05:00 - KUBRICK - - 2004-12-17T09:30:47-05:00 - true - - - - true - false - - - true - false - - false - true - false - true - false - - - httpPost - none - - - true - true - true - true - - - en - wgs84 - - - true - - - false - false - false - false - - - - - 2004-12-17T09:30:47-05:00 - true - - - - true - false - - - true - false - - false - true - false - true - false - - - httpPost - none - - - true - true - - - en - WGS84 - - - true - true - - - false - false - false - false - - - - - - 2004-12-17T09:30:47-05:00 - my123 - true - - - - true - false - - - true - false - - false - true - false - true - false - - - httpPost - none - - - true - true - true - - - en - WGS84 - true - true - - - false - false - false - false - - - - - 2004-12-17T09:30:47-05:00 - my123 - true - - - - true - false - - - true - false - - false - true - false - true - false - - - httpPost - none - - - PT60M - true - true - true - true - false - false - - - en - WGS84 - true - true - true - calls - true - true - true - true - true - - - true - true - - - false - false - false - false - - - true - - - - - 2004-12-17T09:30:47-05:00 - abcde - true - - - - true - false - - - true - false - - false - true - false - true - false - - - httpPost - none - - - PT60M - true - true - true - true - - - en - WGS84 - true - normal - true - true - true - true - - - false - true - - - false - false - false - false - - - false - false - - - - - 2004-12-17T09:30:47-05:00 - abcde - true - - - - true - false - - - true - false - - false - true - false - true - false - - - httpPost - none - - - true - true - - - en - WGS84 - false - - - false - false - - - false - false - false - false - - - - - 2004-12-17T09:30:47-05:00 - abcde - true - - - - true - false - - - true - false - - false - true - false - true - false - - - httpPost - none - - - true - true - - - en - WGS84 - false - - - false - false - - - false - false - false - false - - - - - 2004-12-17T09:30:47-05:00 - abcde - true - - - - true - false - - - true - false - - false - true - false - true - false - - - httpPost - none - - - PT10M - true - - - en - WGS84 - - - false - false - - - - - 2004-12-17T09:30:47-05:00 - abcde - true - - - - true - false - - - true - false - - false - true - false - true - false - - - httpPost - none - - - PT60M - true - true - true - true - true - true - false - false - true - - - en - WHS84 - true - - - false - false - - - false - false - false - - - true - true - - - - - 2004-12-17T09:30:47-05:00 - abcde - true - - - - true - false - - - true - false - - false - true - false - true - false - - - httpPost - none - - - - true - true - true - - - true - true - true - true - - - en - WGS84 - true - - - true - true - - - false - false - false - - - - - - + + + + + 2004-12-17T09:30:47-05:00 + KUBRICK + + 2004-12-17T09:30:47-05:00 + true + + + + true + false + + + true + false + + false + true + false + true + false + + + httpPost + none + + + true + true + true + true + + + en + wgs84 + + + true + + + false + false + false + false + + + + + 2004-12-17T09:30:47-05:00 + true + + + + true + false + + + true + false + + false + true + false + true + false + + + httpPost + none + + + true + true + + + en + WGS84 + + + true + true + + + false + false + false + false + + + + + + 2004-12-17T09:30:47-05:00 + my123 + true + + + + true + false + + + true + false + + false + true + false + true + false + + + httpPost + none + + + true + true + true + + + en + WGS84 + true + true + + + false + false + false + false + + + + + 2004-12-17T09:30:47-05:00 + my123 + true + + + + true + false + + + true + false + + false + true + false + true + false + + + httpPost + none + + + PT60M + true + true + true + true + false + false + + + en + WGS84 + true + true + true + calls + true + true + true + true + true + + + true + true + + + false + false + false + false + + + true + + + + + 2004-12-17T09:30:47-05:00 + abcde + true + + + + true + false + + + true + false + + false + true + false + true + false + + + httpPost + none + + + PT60M + true + true + true + true + + + en + WGS84 + true + normal + true + true + true + true + + + false + true + + + false + false + false + false + + + false + false + + + + + 2004-12-17T09:30:47-05:00 + abcde + true + + + + true + false + + + true + false + + false + true + false + true + false + + + httpPost + none + + + true + true + + + en + WGS84 + false + + + false + false + + + false + false + false + false + + + + + 2004-12-17T09:30:47-05:00 + abcde + true + + + + true + false + + + true + false + + false + true + false + true + false + + + httpPost + none + + + true + true + + + en + WGS84 + false + + + false + false + + + false + false + false + false + + + + + 2004-12-17T09:30:47-05:00 + abcde + true + + + + true + false + + + true + false + + false + true + false + true + false + + + httpPost + none + + + PT10M + true + + + en + WGS84 + + + false + false + + + + + 2004-12-17T09:30:47-05:00 + abcde + true + + + + true + false + + + true + false + + false + true + false + true + false + + + httpPost + none + + + PT60M + true + true + true + true + true + true + false + false + true + + + en + WHS84 + true + + + false + false + + + false + false + false + + + true + true + + + + + 2004-12-17T09:30:47-05:00 + abcde + true + + + + true + false + + + true + false + + false + true + false + true + false + + + httpPost + none + + + + true + true + true + + + true + true + true + true + + + en + WGS84 + true + + + true + true + + + false + false + false + + + + + + diff --git a/examples/siri_exu_discovery/exd_lines_discoveryRequest.xml b/examples/siri_exu_discovery/exd_lines_discoveryRequest.xml index 8c7afd68..5212c22f 100644 --- a/examples/siri_exu_discovery/exd_lines_discoveryRequest.xml +++ b/examples/siri_exu_discovery/exd_lines_discoveryRequest.xml @@ -1,10 +1,10 @@ - - - - - 2004-12-17T09:30:47-05:00 - NADER - MYAGENCY - full - - + + + + + 2004-12-17T09:30:47-05:00 + NADER + MYAGENCY + full + + diff --git a/examples/siri_exu_discovery/exd_lines_discoveryResponse.xml b/examples/siri_exu_discovery/exd_lines_discoveryResponse.xml index e19c8b51..f3eaa311 100644 --- a/examples/siri_exu_discovery/exd_lines_discoveryResponse.xml +++ b/examples/siri_exu_discovery/exd_lines_discoveryResponse.xml @@ -1,77 +1,77 @@ - - - - - 2004-12-17T09:30:47-05:00 - true - - Line564 - 564 - true - - - PLace45 - Paradise - - - - - DIR01 - Outbound - - - - - ST001 - Alpha Road - - Line564 - 22 - - - 0.11 - 53.01 - - 1 - - - ST002 - Beta Street - - Line564 - - - 0.12 - 53.02 - - 2 - - - ST003 - Charley Square - SA2001 - - - Line564 - NORTH - - 44 - - - 0.13 - 53.03 - - 3 - - - - - - - DIR02 - Inbound - - - - - + + + + + 2004-12-17T09:30:47-05:00 + true + + Line564 + 564 + true + + + PLace45 + Paradise + + + + + DIR01 + Outbound + + + + + ST001 + Alpha Road + + Line564 + 22 + + + 0.11 + 53.01 + + 1 + + + ST002 + Beta Street + + Line564 + + + 0.12 + 53.02 + + 2 + + + ST003 + Charley Square + SA2001 + + + Line564 + NORTH + + 44 + + + 0.13 + 53.03 + + 3 + + + + + + + DIR02 + Inbound + + + + + diff --git a/examples/siri_exu_discovery/exd_productCategories_discoveryRequest.xml b/examples/siri_exu_discovery/exd_productCategories_discoveryRequest.xml index f44cc2e2..dd3a984a 100644 --- a/examples/siri_exu_discovery/exd_productCategories_discoveryRequest.xml +++ b/examples/siri_exu_discovery/exd_productCategories_discoveryRequest.xml @@ -1,8 +1,8 @@ - - - - - 2004-12-17T09:30:47-05:00 - NADER - - + + + + + 2004-12-17T09:30:47-05:00 + NADER + + diff --git a/examples/siri_exu_discovery/exd_productCategories_discoveryResponse.xml b/examples/siri_exu_discovery/exd_productCategories_discoveryResponse.xml index 8807ea06..dc643c66 100644 --- a/examples/siri_exu_discovery/exd_productCategories_discoveryResponse.xml +++ b/examples/siri_exu_discovery/exd_productCategories_discoveryResponse.xml @@ -1,13 +1,13 @@ - - - - - 2004-12-17T09:30:47-05:00 - true - - CAT1 - Express - http://www.speedy.com - - - + + + + + 2004-12-17T09:30:47-05:00 + true + + CAT1 + Express + http://www.speedy.com + + + diff --git a/examples/siri_exu_discovery/exd_serviceFeatures_discoveryRequest.xml b/examples/siri_exu_discovery/exd_serviceFeatures_discoveryRequest.xml index a92f5f99..6c9980b4 100644 --- a/examples/siri_exu_discovery/exd_serviceFeatures_discoveryRequest.xml +++ b/examples/siri_exu_discovery/exd_serviceFeatures_discoveryRequest.xml @@ -1,8 +1,8 @@ - - - - - 2004-12-17T09:30:47-05:00 - NADER - - + + + + + 2004-12-17T09:30:47-05:00 + NADER + + diff --git a/examples/siri_exu_discovery/exd_serviceFeatures_discoveryResponse.xml b/examples/siri_exu_discovery/exd_serviceFeatures_discoveryResponse.xml index 22158bed..8a1a6a26 100644 --- a/examples/siri_exu_discovery/exd_serviceFeatures_discoveryResponse.xml +++ b/examples/siri_exu_discovery/exd_serviceFeatures_discoveryResponse.xml @@ -1,18 +1,18 @@ - - - - - 2004-12-17T09:30:47-05:00 - true - - CAT01 - Express - express.gif - - - CAT021 - School - school.gif - - - + + + + + 2004-12-17T09:30:47-05:00 + true + + CAT01 + Express + express.gif + + + CAT021 + School + school.gif + + + diff --git a/examples/siri_exu_discovery/exd_stopPoints_discoveryRequest.xml b/examples/siri_exu_discovery/exd_stopPoints_discoveryRequest.xml index 1561c216..b447e1cd 100644 --- a/examples/siri_exu_discovery/exd_stopPoints_discoveryRequest.xml +++ b/examples/siri_exu_discovery/exd_stopPoints_discoveryRequest.xml @@ -1,24 +1,24 @@ - - - - - 2004-12-17T09:30:47-05:00 - NADER - - - - 0.1 - 53.1 - - - 0.2 - 53.2 - - - - + + + + + 2004-12-17T09:30:47-05:00 + NADER + + + + 0.1 + 53.1 + + + 0.2 + 53.2 + + + + diff --git a/examples/siri_exu_discovery/exd_stopPoints_discoveryResponse.xml b/examples/siri_exu_discovery/exd_stopPoints_discoveryResponse.xml index 3e0be18e..a31cd8e2 100644 --- a/examples/siri_exu_discovery/exd_stopPoints_discoveryResponse.xml +++ b/examples/siri_exu_discovery/exd_stopPoints_discoveryResponse.xml @@ -1,47 +1,47 @@ - - - - - 2004-12-17T09:30:47-05:00 - true - - HLTS0001 - true - Stop 101 - - - S123 - Shelter - http://www.mybus.org/shelter.jpg - - - - A23 - - - 0.1 - 53 - - - - HLTS0002 - true - Stop 102 - - - S123 - Shelter - http://www.mybus.org/shelter.jpg - - - - A23 - A24 - - - 0.12 - 53.1 - - - - + + + + + 2004-12-17T09:30:47-05:00 + true + + HLTS0001 + true + Stop 101 + + + S123 + Shelter + http://www.mybus.org/shelter.jpg + + + + A23 + + + 0.1 + 53 + + + + HLTS0002 + true + Stop 102 + + + S123 + Shelter + http://www.mybus.org/shelter.jpg + + + + A23 + A24 + + + 0.12 + 53.1 + + + + diff --git a/examples/siri_exu_discovery/exd_vehicleFeatures_discoveryRequest.xml b/examples/siri_exu_discovery/exd_vehicleFeatures_discoveryRequest.xml index cd5e5274..5d2cd9d8 100644 --- a/examples/siri_exu_discovery/exd_vehicleFeatures_discoveryRequest.xml +++ b/examples/siri_exu_discovery/exd_vehicleFeatures_discoveryRequest.xml @@ -1,8 +1,8 @@ - - - - - 2004-12-17T09:30:47-05:00 - NADER - - + + + + + 2004-12-17T09:30:47-05:00 + NADER + + diff --git a/examples/siri_exu_discovery/exd_vehicleFeatures_discoveryResponse.xml b/examples/siri_exu_discovery/exd_vehicleFeatures_discoveryResponse.xml index 90bc4337..348c9e71 100644 --- a/examples/siri_exu_discovery/exd_vehicleFeatures_discoveryResponse.xml +++ b/examples/siri_exu_discovery/exd_vehicleFeatures_discoveryResponse.xml @@ -1,17 +1,17 @@ - - - - - 2004-12-17T09:30:47-05:00 - - VF01 - Low doors - lowdoors.gif - - - VF02 - Wheelkchair - spastic.gif - - - + + + + + 2004-12-17T09:30:47-05:00 + + VF01 + Low doors + lowdoors.gif + + + VF02 + Wheelkchair + spastic.gif + + + diff --git a/release-notes/ReadMe.txt b/release-notes/ReadMe.txt index 0c64160f..a2201ff4 100644 --- a/release-notes/ReadMe.txt +++ b/release-notes/ReadMe.txt @@ -1,454 +1,454 @@ -Server Interface for Real-time Information -============================================ - -v2.0 As CEN draft European Standard - prCEN/EN EN 00278181 - prCEN/EN EN 15531 - -v1.0 As CEN Technical Standard - CEN/TS 00278181 - CEN/TS 15531 - -(C) Copyright CEN SIRI 2004-2013 - -=========================================== -This ReadMe describes Changes to the SIRI schema up to v2.0 version 2.0 since v1.3 (2012/03/30) - - -======================== - Future: handbook UML DIagrams -======================== -Changes to SIRI schema v2.0 since v1.4 - - 2015.05.13 Bug fix (from french feedback) SIRI 2.0p - * replacement of "NotifyExtension" (appearing 10 times) with "SiriExtension" in siri_wsConsumer.wsdl in order to ensure compatibility with the Document version - - 2015.05.13 Bug fix (from SG7 feedback) SIRI 2.0o - * update annotation in siri.xsd and and siri_all_functionalService.xsd (to add siri__facilityMonitoring_service.xsd ...) - * siri.xsd: move of a SituationExchangeDelivery, renamed IncludedSituationExchangeDelivery, before other complemented service deliveries. - * siri_situationExchange_service.xsd: addition of IncludedSituationExchangeDelivery element - - 2015.05.11 Bug fix (from SG7 skype meeting on May 11th 2015) SIRI 2.0o - * Allow multiple tags within an extension (reapply lost chnage from 2012.06.18 SIRI 2.0d) - siri_utility.xsd - * siri_estimatedVehicleJourney.xsd : in EstimatedTimetableAlterationGroup, addition of FramedVehicleJourneyRef as an alternative to DatedVehicleJourneyRef (choice) and deprecation of DatedVehicleJourneyRef and EstimatedVehicleJourneyCode - * siri_datedVehicleJourney.xsd : DatedVehicleJourneyCode is now optional - * siri.xsd: SituationExchangeDelivery now can be provided as a complement to any other Service delivery (and can still be provided standalone)... note that the SituationExchangeDelivery must be after the other Delivery to get a validating, non-ambiguous XSD. - * siri_estimatedVehicleJourney.xsd : EstimatedVehicleJourneyStructure brought back to SIRI 2.0k situation - * Replacement of EstimatedJourneyInfoGroup by JourneyEndTimesGroup - * Replacement of inclusion of siri_journey.xsd by siri_monitoredVehicleJourney.xsd - * Replacement of EstimatedRealtimeInfoGroup by journeyProgressGroup - * Replacement of OperationalInfoGroup by TrainOperationalInfoGroup - - - 2015.02.10 Bug fix (from french feedback) - * [fr] siri_wsProducer-Framework.xsd: use of siri:CheckStatusRequestStructure instead of siri:RequestStructure for checkStatus (one addition non mandatory version attribute) - * [fr] siri_wsProducer.wsdl: use of siri:CheckStatusRequestStructure instead of siri:RequestStructure for checkStatus (one addition non mandatory version attribute) - * [fr] siri_wsConsumer-Framework.xsd: update type of NotifySubscriptionTerminated to siri:SubscriptionTerminatedNotificationStructure (instead of TerminateSubbscriptionREquest !) - - 2014.11.17 Correction (from french feedback) - * [fr] fix RPC-Document compatibility issue for GetSiri in Document WSDL (siri_wsProducer-Services.xsd): addition of Request/Answer wrapper - * [fr] fix WSDL Document issue: GetCapability was using Answer instead of Request (siri_wsProducer-DiscoveryCapability.xsd) - * [fr] fix RPC-Document compatibility issue for LinesDiscovery,ConnectionLinksDiscovery,StopPointsDiscovery in Document WSDL (siri_wsProducer-DiscoveryCapability.xsd): deletion of useless «xxxAnswerInfo» wrapper - - 2014.06.20 Correction and revisions from Stenungsund - [Part2] - * [fx] Document SubscriptionTerminatedNotification and add error code. (siri-requests.xsd) - * [fx] StopDiscovery response. Add RouteDirection. Rename JourneyPattern/Stops to JourneyPattern/StopsInPattern SubscriptionTerminatedNotification and add error code. (siri-requests.xsd) - * [de] Add Extensions to discovery requests. (siri_discovery.xsd) - - [Part3] - * [ch] Add origin display whereever destination display as per Cologne meeting (siri-Journey.xsd, siri-DatedVehicleJourney.xsd, - * [xh[ Add OriginAtDestination wherever destination display as per Cologne meeting (siri-Journey.xsd) - * [fx] Set default on new DetailLevels on ConnectionMonitoring and EstimatedJourney for backwards compatability. (siri_connectionMonitoring_ervice.xsd siri_EstimatedTimetable_service.xsd - * [ch] Add recordedCall to Estimated jouernesy to allow times for passed stops to be included. iri_EstimatedVehicleJourney.xsd - [Part5 SituationExchange] - * [de] Add missing AffectedFacility that was in document but missing from schema. VehicleJourney, STop & StopComponent siri_situationAffects.xsd. -emporal filter siri_situationExchaneg_service.xsd. - * [de] Add temporal filter to request with ValidityPeriod in siri_situationExchange_service.xsd. - * [se] Add end time precision to halfopen time rangefor input a siri_time.xsd. - * [se] Add end time status to halfopen time range output siri_time.xsd. - * [fr] Add additional small delay bands siri_situation.xsd - * [de] Add IncludeOnly-IfInPublicationWindow to situation request temporal filter siri_situationExchange_service.xsd. - * [fx] StopPlaceFilterGroup: add missing component ref and facility that was in doc but missing from schema siri_situationExchange_service.xsd. - * [fx] Add missing AccessFeature type to AFfectedStopPlaceComponent siri_situationAffects.xsd. - * [fx] Correct cardinality on FacilitRef on request to match doc siri_situationExchaneg_service.xsd. - * [fx] Correct spec to include projection attributes for AFfectedStopPlaceComponent doc. - * [doc] Document FacilityRef as part of request doc - * [doc] Document Access Mode as part of request doc - * [doc] Document Scope as part of request doc - * [doc] Document RoadFilter and Accessibility need filter as part of request doc - * [doc] Correct Documentation of AfFfectedRoads as part of Delivery doc - * [doc/fx] Correct Documentation of capability Matrix and update in schemas well siri_situationExchange_service.xsd. - * [doc/fx] Correct Documentation of Reason codes and correct in schema siri_reasons.xsd - * [doc] Add Annex D to Doc on GTFS real-time mapping - - 2014.05.26 Changes to answer comment from the EU ballot - * [fr] Addition of SubscriptionTerminatedNotification (XSD and WSDL SOAP Web Services(RPC/Document & WSDL2)) - - File siri_common_services.xsd: Addition of SubscriptionTerminatedNotification (SubscriptionTerminatedNotification element + SubscriptionTerminatedNotificationStructure ) - - File siri.xsd: addition of SubscriptionTerminatedNotification in servicesResponseGroup - - Update of siri_wsConsumer-Document.wsdl, siri_wsConsumer.wsdl, siri_wsConsumer-WSDL2.wsdl to add a NotifyTerminateSubscription - - File siri_wsConsumer-Framework.xsd: Addition of WsSubscriptionTerminatedNotificationStructure and NotifySubscriptionTerminated - * [fr] Added ParameterName [0..*] to ParametersIgnoredErrorStructure (siri_request_errorConditions.xsd) - * [fr] Added ExtensionName [0..*] to UnknownExtensionsErrorStructure (siri_request_errorConditions.xsd) - * [fr] Added InvalidRef [0..*] to InvalidDataReferencesErrorStructure (siri_request_errorConditions.xsd) - * [fr] Added Vesion attribute (non mandatory) to CheckStatus request (siri_common_services.xsd) - * [fr] ChangeBeforeUpdates not anymore mandatory in EstimatedTimetableSubscriptionPolicyGroup - * [fr] added optional RecordedAtTime to EstimatedVehicleJourney - * [fr] added ConnectionLinksDiscovery service to WSDL (RPC/Document & WSDL2) (and siri_wsProducerDicoveryCapability.xsd) - - - 2013.06.26 French comments (compatibility issue) - * [fr] Change SOAP Web Service namesapce to http://wsdl.siri.org.uk (previously http://wsdl.siri.org.uk/siri) - - * [fr] update EstimatedVehicleJourney in order to have it consistent with MonitoredVehicleJourney and Siri 2.0 - - use JourneyEndTimesGroup in place of EstimatedJourneyInfoGroup - - use JourneyProgressGroup in place of EstimatedRealtimeInfoGroup - - use TrainOperationalInfoGroup in place of OperationalInfoGroup - - addCallRailGroup (containing PlateformTraversal ) and CallRealTime to EstimatedCall - 2013.02.20 WG3 SG meeting Munich - * [se] Add JourneyEndNamesInfoGroup to EstimatedDirectionAtStop to DestinationDisplayAtStop - This makes destination name available on EstimatedJourney. - * [us] Rename ProgrssStatusEnumeration to CallStatusENumeration to avoid confusion. - * [fr} Add FramedVehicleJourney references as alternative wherever a simple VehicleJourneyRef exists and deprecate use of simple reference. - - DatedVehicleJourney - identifier group. - - FacilityMonitoring - FacilityLocation. - - SituationExchangeService - SituationFilterGroup. - - SituationExchangeService - AffectedVehicleJourneyRef. - * [ch] StopTimeTableCancellation - Add Reason code to be consistet with St opMonitoring. - * [de] ArrivalTimesDepartureGroup - add ExpectedArrivalPredictionQuality element. - * [fr] MonitoredStopVisit Cancellation make VisitNo LineRef DirectionRef optional. - * [fr] EstimatedTimetable, COnnectionMonitoring add detailed level to reqyest - - * [fr] Make AdditionalVersionRefS to OperationalInfoGroup. - * [fr] Add JourneyPatternName The JourneyPatternInfoGroup. - - 2013.02.11 - * [SE] Align documentation and XSD. See comments in individual xsd-files. - * [SE] Add StopNotice and StopNoticeCancellation to StopMonitoringDelivery. - * [SE] Revise ProductionTimetableDelviery to correct ServcieJourneyInterchange to include visit numbers. - * [FR] Updated with latest WDSL from CD. - - - 2012.08.01 - SIRI 2.0e.1. - * [DE] Align documentation and XSD using GT's amendments. - * [FR] Update WDSL and add WSDL2.. Add WSDl chapter by CD to gudie.. - * [DE] Add Delegation elements to more mesages. - * [US] Revise Siri Lite chapter. - *[DE] Revise commends on Prediction quality based on CB's comments - - 2012.06.18 - SIRI 2.0d.2. - * [CH] Allow multiple tags within an extension - * [CH] Make most NL String elements unbounded to allow for NL translations. x dx - Add IncludeTranslations to RequestPolicy. - Add Translations to Cpabilities - * [DE] Add PredictionQuality elements to MonitoredVehicleJourney Onward Call. & EstimatedVehcielJourney - * [FR] Add GroupOfLinesRef to JourneyPattenrInforGroup on MonitoredVehcile Joruney and elsewhere - * [FR] Add Extensions tag to EstimatedTimetableSubscriptionRequest x tx - * [FR] Add Extensions tag to FacilityMonitoringSubscriptionRequest x - * [FR] Add Extensions tag to SituationExchangeSubscriptionRequest x - * [FR] Add Extensions tag to ConnectionMonitoringSubscriptionRequest x tx - * [FR] Add Extensions tag to Connection|TimetableSubscriptionRequest x tx - * [FR] Add Extensions tag to VehicleMonitoringSubscriptionRequest x tx - * [FR] Add Extensions tag to Terminate SubscriptionRequest x tx - * [DE] Correct EstimatedTimetable EstimatedServiceJourneyInterchange x tx - *[US] Add SIRILite chapter to manual. - * [DE] Add DelegatorAddress and DelegatorRef to servicerequest and service response. x tx - * [SE] Correct latestExopectedArrivalTime - * [SE] Add Vehicle Status add additional arrival and departure states - - - 2012.05.31 - SIRI 2.0d.1. - * [MTA] Discovery Revise StopLine discovery to include line direction x - * [MTA] Discovery Revise Line discovery to include Direction/Line x - * [MTA] Correcct typo in name of RouteDirection x - * [Init] Add DriverRef to vehiclejourney x tx - - SIRI 2.0c.1. - 2012.06.11 - SIRI 2.0c - Relax typing on NotifcationRef to be normalized string x - Add wsdl subdirectory for wsd .xsds x - - 2012.06.08 - WSDL [FR] x - In siri-wsProducer-Document.xsd rename StopMonitoringType and StopMonitoringMultipleType to StopMonitoringRequestType to StopMonitoringMultipleRequestType (for more consistent naming) - Add comment to point out that usage of SOAP Fault are now deprecated - Add comment to point out that usage of MultipleStopMonitoring is now deprecated (utilise GetSiriService) - Addition of a Document Wrapped encoding style fully compatible with the RPC Style (Producer and Consumer) - Add GetSiriService in RPC and Document Wrapped mode - Addition of StopDiscovery and LineDiscovery - Cleaning of xmlns:xxx in siri_wsProducer-Document - Suppression of comments on and (for http://www.validwsdl.com/ compliance) .. in poducer and producer-Document WSDL - Rename of Port/Binding/Service in order to clearly diffirentiate them - Change to + - - 2012.05.17 - SIRI 2.0b.3 - [MTA] Add filtering to StopPoints and Lines Discovery requests by point + radius x - [MTA] Add filtering to Lines Discovery request by LineRef and Direction x - [MTA] Add stops in pattern to Lines Discovery, with OnwardLinkShap and LineDetailParameter x - [NeTEx] Add StopAreaRef & url to annotated stop on StopDiscovery x - [General] Correct capability definition - - 2012.04.18 - SIRI 2.0b.2 - [VDV] Add ValidUntil to individual SIRI-CM MonitoredFeederArrival x e - [VDV] Add ValidUntil to individual SIRI-SM MonitoredStopVisit x e - - - [MTA] Add DistanceFromStop and NumberOfStopsAway to to MonitoredCall & OnwardsCall x tx - - 2012.03.23 - SIRI 2.0b.1 - [MTA] Add filtering to StopPoints request by point + radius - - 2012.03.23 - WDSL - Add explicit namespace to body x - Use a SIRI namespace http://wsdl.siri.org.uk/siri x - Correct GetStopTimentable to have soapAction x - Turn annotations into comments x - Use FaultLiteral x - - SIRI 2.0a - Changes to framework - [VDV] Add DataReady to CheckStatus response x. tx. - - JourneyInfo group SIRI-ST SIRI-SM SIRI-VM SIRI-PT SIRI-ET MonitoredJourney, etc - [VDV] Add PublicContact & Operations contact to JourneyInfo group in x tx - [VDV] Add ViaPriority to ViaNames using a new ViaNameStructure x tx - [VDV] at DirectionAtOrigin name to JourneyInfo SIRI-PT, SIRI-ET, SIRI-SM. SIRI-VM - - [VDV] Add EstimatedServiceInterchange to EstimatedTimetableDelivery x tx. - [VDV] Add ServiceJourneyInterchange to ProductionTimetableDelivery SIRI PT x tx - - Changes to MonitoredVehicleJourney SIRI-SM SIRI-VM - [VDV, SE] Add EarliestExpectedArrivalTimeForVehicle to Arrival Times Group x tx - [VDV] Add ProvisionalExpectedDepartureTime to Departure Times Group x tx - [VDV, SE] Add latesExpectedArrivalTimeForVehicle to Departure Times Group x tx - [SE] Add Aimed and expected Platform assignments to CALLs including a reference code. - - [FR] Add FirstOrLastJourney to JourneyTimesGroup x.tx. - [FR] add ArrivalOperatorRefs and DepartureOperatorRefs to Call arrival and Departure - [VDV] Add Velocity to MonitoredVehicleJourney JoueyProgerssGroup SIRI-SM and SIRI-VM - - [FR] Add AimedLatestPassengerAccessTime to MonitoredCall & OnwardsCall x tx - [MTA,FR,UK] Add ArrivalProximityText & DepartureProximityText to MonitoredCall & OnwardsCall x tx - [FR, MTA] Add Velocity to Journey & VelocityType x tx - - StopMonitoringRequest SIRI-SM - [VDV] Add Minimum-StopVisits¬PerVia to STopMonitoringRequestPolicy x tx - [VDV] Add HasMinimum-StopVisits¬Via to STopMonitoringCapabilities x tx - - StopMonitoringDelivery SIRI-SM - [FR] Add Service Exception element - [VDV] Add delivery variant to LineNote - [MTA] Add MaximumNumberOfCalls to VehiclelMonitoring request - - StopMonitoringDelivery SIRI-SX - Upgrade to DatexII - - ConnectionMonitoringDelivery SIRI-CM - [VDV] Add SuggestedWaitDecisionTime to MonitoredFeederArrival SIRI-CM x tx - - Enabling SIRI Lite - [MTA, UK] Add optional authenitication Key to Servce Request TODO - [MTA, UK] Add optional name to StopMonitoring response x tx - [MTA, UK] Add optional name to VehicleMonitoring response x tx - - Discovery services - [Fr] Add location to stop discovery x. - - General Framework - [VDV] Add ErrorNumber to Error Structure SIRI - All - - [VDV] Add new error conditions - - UnknownParticipant Recipient for a message to be distributed is unknown. +SIRI v2.0 - UnknownEndpoint Endpoint to which a message is to be distributed is unknown. +SIRI v2.0 - EndpointDeniedAccess Distribution message could not be delivered because not authorised.. +SIRI v2.0 - EndpointNotAvailable Recipient of a message to be distributed is not available. +SIRI v2.0 - UnapprovedKey User authorisation Key is not enabled. +SIRI v2.0 - - InvalidDataReferences Request contains references to identifiers that are not known. +SIRI v2.0 - ParametersIgnored Request contained parameters that were not supported by the producer. A response has been provided but some parameters have been ignored. +SIRI v2.0 - UnknownExtensions Request contained extensions that were not supported bu the producer. A response has been provided but some or all extensions have been ignored.. +SIRI v2.0 - - [FR] Add DistanceUnits & Velocity Units to ServiceRequestContext x tx - - General improvements to internal structure maintainability - Tidy up comments. x tx. - Improve modularisation (eg permissions/model permissions) to avoid circuloar refs x - Separate subdirectories for common request, model and core elements x - Separate out some model elements into separate packages x - Separate out model journeys from SIRI service packagaes x - Separate out discovery models from discovery services x - - Start of v2,0 ==> - -Changes to SIRI schema v1.4a since v1.3 -============================ - -2011-04-18 Corrections - New cumulative fix version 1.4a - Minor corrections 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 x - (ii) and siri_generalMessage_service.xsd subscription structure x - (iii) Missing type: Assign a type of normalizedString to formatRef x dx - - (b) siri_requests.xsd (line 814) ErrorConditionStructure should not be abstract . Fix from RV ixxi.biz- - made abstract x - - (c) siri_journey.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 x ?? - - (d) siri_productionTimetable_service.xsd Type on request ValidityPeriod start and end should be datetime not time - - Change to ClosedTimestampRange instead of ClosedDateeRange x tx. - - Fix Subscription request to be an element and to have IncrementalUpdate parameter Extensions x - - (e) siri_situation.xsd AffectedVehicleJourney should allow multiple journeys. Brian Ferris onebusaway.org>, x - - (f) ifopt_location.xsd Correct siri: namespace x - - (g) Fix up examples - (i) correct estimated timetable request, production timetable request, stop monitoring request, stop monitoring eprmissions. drop flat examples tx. - (ii) Add examples for facility monitorign and situation exchange ex - - (h) Drop vestigial As Flatgroup alternative coding tx - siri_connectionTimetable_service.xsd InterchangeHourneys x tx - siri_estimatedTimetable_service.xsd EstimatedCalls --> x tx - siri_productionTimetable_service.xsd DatedCalls --> x tx - - (i) Add missing type - siri_requests.xsd formatRef x - DATEXIISchema_1_0_1_0.xsd modelBaseversion - - (j)siri_facility.xsd TidyUp empty ValidityConditionGroup x - - (g) Add xmlSPy project spp. x - -====================== -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 x - (b) siriSg.xsd Remove unnecessary groups for decoupled version x tx. - -2009-03-31 Corrections - (a) StopMonitoring - Change the element type of MaximumNumberOfCalls.Previous, MaximumNumberOfCalls.Onwards from xsd:positiveInteger to xsd:nonNegativeInteger x tx. - - and clarify handling of - - MaximumNumberOfCalls : If calls are to be returned, maximum number of calls to include in response. If absent, exclude all calls. tx. - - Previous : Maximum number of previous calls to include. Zero for none. Only applies if MaximumNumberOfCalls specified. Zero for none. If MaximumNumber of Calls specified but MaximumNumberOfCalls.previous absent, include all previous calls. tx. - - Onwards : Maximum number of onwards calls to include. Zero for none. Only applies if MaximumNumberOfCalls specified. Zero for none. If MaximumNumber of Calls specified but MaximumNumberOfCalls.Onwards absent, include all onwards calls. tx. - -___________________________________________________________________________ - - (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 x - (b) siriSg.xsd Correct cardinality on servcierequest & subscription request to be many x - -2009-09-18 Siricommon - allow empty Terminate subscription response x - (a) Relax mandatory on in siri_common x - -2008-11-18 Revise FM servics - (a) Revise daytypes in siri_time.xsd x - -2008-11-17 Revise to support substitution groups - (a) Make all requests subtypes of abstract request. Add Subst elements x - - (b) Introduce AbstractFunctionalServiceRequest, AbstractCapabilityServiceRequest, AbstractDiscoveryRequest - as common supertypes. revised versiosn of siri_requests.xsd, siri_journey.xsd and siri_permissions.xsd, siri-All and siribase - - (c) add SiriSg and Siri_base.xsd packages -2008-11-12 Corrections to the Caridnailities on the siri_discovery services x - - (a) Change min maxes on >LineRef, StopPoints, Features etc etc x - -2008-10-08 Corrections to the SIRI service - (a) Add SubscriberRef to TerminateSubscriptionRequest x tx. - -2008-10-06 Corrections to the SIRI service - (a) Correct StopTimetable SubscriptionRequest to use group x - (b) Correct cardinality on AnnotatedStopPointRef in StopPointDelivery x - -2008-10-01 Corrections to the SIRI-SX service - (a) Add StatusFilterGroup to SIRI-SX request with Verification, Progress and Reality - (b) add 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 - (c) Allow a link projection & Offset on connection Link via AffectedPathLink - (d) Add an AfFfectedRoad 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 Corrections 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--> x - (c) Allow zero PT or Road Situation elements in a delivery x - (d) Affects Line group corrected to ref a lineref and not a route ref x - (e) Add missing scopeType to Situation classifier group x - (f) Add other subreasons x - (g) add secondary reasons x - -2008 05 08 StopMonitoring service - (a) Correct type on FeatureRef in Stop monitoring x - (b) Add StopMonitoringMultipleRequest x tx - (c) Add optional MonitoringRef to StopMonitoringDelivery so that can return id even if no data x tx. - -2008 03 27 - Fix up ifopt & ACSB version numbers to match ifopt 0.4 x - - -2008-03-26 EstimatedTimetable Production Timetable Service Service - Add wrapper tag for Line + Direction to help binding to Axisx x tx. - Wraps multiple instances x - ** Note this will break strict Compaptibility with 1.0 - -2008 03 12 - Add comments for elements and arrtributes that lacked them x - Correct wdsl errors x - Strip out degree character x - BeyondHorizon type corrected x - -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. x tx - Added a siri_all.xsd, ifopt_allStopPlace.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 x - Change name space : http://www.siri.org.uk/ to www.siri.org.uk/siri x.tx. - - harmonise Facility Monitoring - Revise SpecialNeeds to use acsb package x. - Use Ifopt facility etc x. - Factor out Extensions to utility file x. - -2007 04 V1.2 -======================================= +Server Interface for Real-time Information +============================================ + +v2.0 As CEN draft European Standard + prCEN/EN EN 00278181 + prCEN/EN EN 15531 + +v1.0 As CEN Technical Standard + CEN/TS 00278181 + CEN/TS 15531 + +(C) Copyright CEN SIRI 2004-2013 + +=========================================== +This ReadMe describes Changes to the SIRI schema up to v2.0 version 2.0 since v1.3 (2012/03/30) + + +======================== + Future: handbook UML DIagrams +======================== +Changes to SIRI schema v2.0 since v1.4 + + 2015.05.13 Bug fix (from french feedback) SIRI 2.0p + * replacement of "NotifyExtension" (appearing 10 times) with "SiriExtension" in siri_wsConsumer.wsdl in order to ensure compatibility with the Document version + + 2015.05.13 Bug fix (from SG7 feedback) SIRI 2.0o + * update annotation in siri.xsd and and siri_all_functionalService.xsd (to add siri__facilityMonitoring_service.xsd ...) + * siri.xsd: move of a SituationExchangeDelivery, renamed IncludedSituationExchangeDelivery, before other complemented service deliveries. + * siri_situationExchange_service.xsd: addition of IncludedSituationExchangeDelivery element + + 2015.05.11 Bug fix (from SG7 skype meeting on May 11th 2015) SIRI 2.0o + * Allow multiple tags within an extension (reapply lost chnage from 2012.06.18 SIRI 2.0d) - siri_utility.xsd + * siri_estimatedVehicleJourney.xsd : in EstimatedTimetableAlterationGroup, addition of FramedVehicleJourneyRef as an alternative to DatedVehicleJourneyRef (choice) and deprecation of DatedVehicleJourneyRef and EstimatedVehicleJourneyCode + * siri_datedVehicleJourney.xsd : DatedVehicleJourneyCode is now optional + * siri.xsd: SituationExchangeDelivery now can be provided as a complement to any other Service delivery (and can still be provided standalone)... note that the SituationExchangeDelivery must be after the other Delivery to get a validating, non-ambiguous XSD. + * siri_estimatedVehicleJourney.xsd : EstimatedVehicleJourneyStructure brought back to SIRI 2.0k situation + * Replacement of EstimatedJourneyInfoGroup by JourneyEndTimesGroup + * Replacement of inclusion of siri_journey.xsd by siri_monitoredVehicleJourney.xsd + * Replacement of EstimatedRealtimeInfoGroup by journeyProgressGroup + * Replacement of OperationalInfoGroup by TrainOperationalInfoGroup + + + 2015.02.10 Bug fix (from french feedback) + * [fr] siri_wsProducer-Framework.xsd: use of siri:CheckStatusRequestStructure instead of siri:RequestStructure for checkStatus (one addition non mandatory version attribute) + * [fr] siri_wsProducer.wsdl: use of siri:CheckStatusRequestStructure instead of siri:RequestStructure for checkStatus (one addition non mandatory version attribute) + * [fr] siri_wsConsumer-Framework.xsd: update type of NotifySubscriptionTerminated to siri:SubscriptionTerminatedNotificationStructure (instead of TerminateSubbscriptionREquest !) + + 2014.11.17 Correction (from french feedback) + * [fr] fix RPC-Document compatibility issue for GetSiri in Document WSDL (siri_wsProducer-Services.xsd): addition of Request/Answer wrapper + * [fr] fix WSDL Document issue: GetCapability was using Answer instead of Request (siri_wsProducer-DiscoveryCapability.xsd) + * [fr] fix RPC-Document compatibility issue for LinesDiscovery,ConnectionLinksDiscovery,StopPointsDiscovery in Document WSDL (siri_wsProducer-DiscoveryCapability.xsd): deletion of useless «xxxAnswerInfo» wrapper + + 2014.06.20 Correction and revisions from Stenungsund + [Part2] + * [fx] Document SubscriptionTerminatedNotification and add error code. (siri-requests.xsd) + * [fx] StopDiscovery response. Add RouteDirection. Rename JourneyPattern/Stops to JourneyPattern/StopsInPattern SubscriptionTerminatedNotification and add error code. (siri-requests.xsd) + * [de] Add Extensions to discovery requests. (siri_discovery.xsd) + + [Part3] + * [ch] Add origin display whereever destination display as per Cologne meeting (siri-Journey.xsd, siri-DatedVehicleJourney.xsd, + * [xh[ Add OriginAtDestination wherever destination display as per Cologne meeting (siri-Journey.xsd) + * [fx] Set default on new DetailLevels on ConnectionMonitoring and EstimatedJourney for backwards compatability. (siri_connectionMonitoring_ervice.xsd siri_EstimatedTimetable_service.xsd + * [ch] Add recordedCall to Estimated jouernesy to allow times for passed stops to be included. iri_EstimatedVehicleJourney.xsd + [Part5 SituationExchange] + * [de] Add missing AffectedFacility that was in document but missing from schema. VehicleJourney, STop & StopComponent siri_situationAffects.xsd. +emporal filter siri_situationExchaneg_service.xsd. + * [de] Add temporal filter to request with ValidityPeriod in siri_situationExchange_service.xsd. + * [se] Add end time precision to halfopen time rangefor input a siri_time.xsd. + * [se] Add end time status to halfopen time range output siri_time.xsd. + * [fr] Add additional small delay bands siri_situation.xsd + * [de] Add IncludeOnly-IfInPublicationWindow to situation request temporal filter siri_situationExchange_service.xsd. + * [fx] StopPlaceFilterGroup: add missing component ref and facility that was in doc but missing from schema siri_situationExchange_service.xsd. + * [fx] Add missing AccessFeature type to AFfectedStopPlaceComponent siri_situationAffects.xsd. + * [fx] Correct cardinality on FacilitRef on request to match doc siri_situationExchaneg_service.xsd. + * [fx] Correct spec to include projection attributes for AFfectedStopPlaceComponent doc. + * [doc] Document FacilityRef as part of request doc + * [doc] Document Access Mode as part of request doc + * [doc] Document Scope as part of request doc + * [doc] Document RoadFilter and Accessibility need filter as part of request doc + * [doc] Correct Documentation of AfFfectedRoads as part of Delivery doc + * [doc/fx] Correct Documentation of capability Matrix and update in schemas well siri_situationExchange_service.xsd. + * [doc/fx] Correct Documentation of Reason codes and correct in schema siri_reasons.xsd + * [doc] Add Annex D to Doc on GTFS real-time mapping + + 2014.05.26 Changes to answer comment from the EU ballot + * [fr] Addition of SubscriptionTerminatedNotification (XSD and WSDL SOAP Web Services(RPC/Document & WSDL2)) + - File siri_common_services.xsd: Addition of SubscriptionTerminatedNotification (SubscriptionTerminatedNotification element + SubscriptionTerminatedNotificationStructure ) + - File siri.xsd: addition of SubscriptionTerminatedNotification in servicesResponseGroup + - Update of siri_wsConsumer-Document.wsdl, siri_wsConsumer.wsdl, siri_wsConsumer-WSDL2.wsdl to add a NotifyTerminateSubscription + - File siri_wsConsumer-Framework.xsd: Addition of WsSubscriptionTerminatedNotificationStructure and NotifySubscriptionTerminated + * [fr] Added ParameterName [0..*] to ParametersIgnoredErrorStructure (siri_request_errorConditions.xsd) + * [fr] Added ExtensionName [0..*] to UnknownExtensionsErrorStructure (siri_request_errorConditions.xsd) + * [fr] Added InvalidRef [0..*] to InvalidDataReferencesErrorStructure (siri_request_errorConditions.xsd) + * [fr] Added Vesion attribute (non mandatory) to CheckStatus request (siri_common_services.xsd) + * [fr] ChangeBeforeUpdates not anymore mandatory in EstimatedTimetableSubscriptionPolicyGroup + * [fr] added optional RecordedAtTime to EstimatedVehicleJourney + * [fr] added ConnectionLinksDiscovery service to WSDL (RPC/Document & WSDL2) (and siri_wsProducerDicoveryCapability.xsd) + + + 2013.06.26 French comments (compatibility issue) + * [fr] Change SOAP Web Service namesapce to http://wsdl.siri.org.uk (previously http://wsdl.siri.org.uk/siri) + + * [fr] update EstimatedVehicleJourney in order to have it consistent with MonitoredVehicleJourney and Siri 2.0 + - use JourneyEndTimesGroup in place of EstimatedJourneyInfoGroup + - use JourneyProgressGroup in place of EstimatedRealtimeInfoGroup + - use TrainOperationalInfoGroup in place of OperationalInfoGroup + - addCallRailGroup (containing PlateformTraversal ) and CallRealTime to EstimatedCall + 2013.02.20 WG3 SG meeting Munich + * [se] Add JourneyEndNamesInfoGroup to EstimatedDirectionAtStop to DestinationDisplayAtStop + This makes destination name available on EstimatedJourney. + * [us] Rename ProgrssStatusEnumeration to CallStatusENumeration to avoid confusion. + * [fr} Add FramedVehicleJourney references as alternative wherever a simple VehicleJourneyRef exists and deprecate use of simple reference. + - DatedVehicleJourney - identifier group. + - FacilityMonitoring - FacilityLocation. + - SituationExchangeService - SituationFilterGroup. + - SituationExchangeService - AffectedVehicleJourneyRef. + * [ch] StopTimeTableCancellation - Add Reason code to be consistet with St opMonitoring. + * [de] ArrivalTimesDepartureGroup - add ExpectedArrivalPredictionQuality element. + * [fr] MonitoredStopVisit Cancellation make VisitNo LineRef DirectionRef optional. + * [fr] EstimatedTimetable, COnnectionMonitoring add detailed level to reqyest + + * [fr] Make AdditionalVersionRefS to OperationalInfoGroup. + * [fr] Add JourneyPatternName The JourneyPatternInfoGroup. + + 2013.02.11 + * [SE] Align documentation and XSD. See comments in individual xsd-files. + * [SE] Add StopNotice and StopNoticeCancellation to StopMonitoringDelivery. + * [SE] Revise ProductionTimetableDelviery to correct ServcieJourneyInterchange to include visit numbers. + * [FR] Updated with latest WDSL from CD. + + + 2012.08.01 + SIRI 2.0e.1. + * [DE] Align documentation and XSD using GT's amendments. + * [FR] Update WDSL and add WSDL2.. Add WSDl chapter by CD to gudie.. + * [DE] Add Delegation elements to more mesages. + * [US] Revise Siri Lite chapter. + *[DE] Revise commends on Prediction quality based on CB's comments + + 2012.06.18 + SIRI 2.0d.2. + * [CH] Allow multiple tags within an extension + * [CH] Make most NL String elements unbounded to allow for NL translations. x dx + Add IncludeTranslations to RequestPolicy. + Add Translations to Cpabilities + * [DE] Add PredictionQuality elements to MonitoredVehicleJourney Onward Call. & EstimatedVehcielJourney + * [FR] Add GroupOfLinesRef to JourneyPattenrInforGroup on MonitoredVehcile Joruney and elsewhere + * [FR] Add Extensions tag to EstimatedTimetableSubscriptionRequest x tx + * [FR] Add Extensions tag to FacilityMonitoringSubscriptionRequest x + * [FR] Add Extensions tag to SituationExchangeSubscriptionRequest x + * [FR] Add Extensions tag to ConnectionMonitoringSubscriptionRequest x tx + * [FR] Add Extensions tag to Connection|TimetableSubscriptionRequest x tx + * [FR] Add Extensions tag to VehicleMonitoringSubscriptionRequest x tx + * [FR] Add Extensions tag to Terminate SubscriptionRequest x tx + * [DE] Correct EstimatedTimetable EstimatedServiceJourneyInterchange x tx + *[US] Add SIRILite chapter to manual. + * [DE] Add DelegatorAddress and DelegatorRef to servicerequest and service response. x tx + * [SE] Correct latestExopectedArrivalTime + * [SE] Add Vehicle Status add additional arrival and departure states + + + 2012.05.31 + SIRI 2.0d.1. + * [MTA] Discovery Revise StopLine discovery to include line direction x + * [MTA] Discovery Revise Line discovery to include Direction/Line x + * [MTA] Correcct typo in name of RouteDirection x + * [Init] Add DriverRef to vehiclejourney x tx + + SIRI 2.0c.1. + 2012.06.11 + SIRI 2.0c + Relax typing on NotifcationRef to be normalized string x + Add wsdl subdirectory for wsd .xsds x + + 2012.06.08 + WSDL [FR] x + In siri-wsProducer-Document.xsd rename StopMonitoringType and StopMonitoringMultipleType to StopMonitoringRequestType to StopMonitoringMultipleRequestType (for more consistent naming) + Add comment to point out that usage of SOAP Fault are now deprecated + Add comment to point out that usage of MultipleStopMonitoring is now deprecated (utilise GetSiriService) + Addition of a Document Wrapped encoding style fully compatible with the RPC Style (Producer and Consumer) + Add GetSiriService in RPC and Document Wrapped mode + Addition of StopDiscovery and LineDiscovery + Cleaning of xmlns:xxx in siri_wsProducer-Document + Suppression of comments on and (for http://www.validwsdl.com/ compliance) .. in poducer and producer-Document WSDL + Rename of Port/Binding/Service in order to clearly diffirentiate them + Change to + + + 2012.05.17 + SIRI 2.0b.3 + [MTA] Add filtering to StopPoints and Lines Discovery requests by point + radius x + [MTA] Add filtering to Lines Discovery request by LineRef and Direction x + [MTA] Add stops in pattern to Lines Discovery, with OnwardLinkShap and LineDetailParameter x + [NeTEx] Add StopAreaRef & url to annotated stop on StopDiscovery x + [General] Correct capability definition + + 2012.04.18 + SIRI 2.0b.2 + [VDV] Add ValidUntil to individual SIRI-CM MonitoredFeederArrival x e + [VDV] Add ValidUntil to individual SIRI-SM MonitoredStopVisit x e + + + [MTA] Add DistanceFromStop and NumberOfStopsAway to to MonitoredCall & OnwardsCall x tx + + 2012.03.23 + SIRI 2.0b.1 + [MTA] Add filtering to StopPoints request by point + radius + + 2012.03.23 + WDSL + Add explicit namespace to body x + Use a SIRI namespace http://wsdl.siri.org.uk/siri x + Correct GetStopTimentable to have soapAction x + Turn annotations into comments x + Use FaultLiteral x + + SIRI 2.0a + Changes to framework + [VDV] Add DataReady to CheckStatus response x. tx. + + JourneyInfo group SIRI-ST SIRI-SM SIRI-VM SIRI-PT SIRI-ET MonitoredJourney, etc + [VDV] Add PublicContact & Operations contact to JourneyInfo group in x tx + [VDV] Add ViaPriority to ViaNames using a new ViaNameStructure x tx + [VDV] at DirectionAtOrigin name to JourneyInfo SIRI-PT, SIRI-ET, SIRI-SM. SIRI-VM + + [VDV] Add EstimatedServiceInterchange to EstimatedTimetableDelivery x tx. + [VDV] Add ServiceJourneyInterchange to ProductionTimetableDelivery SIRI PT x tx + + Changes to MonitoredVehicleJourney SIRI-SM SIRI-VM + [VDV, SE] Add EarliestExpectedArrivalTimeForVehicle to Arrival Times Group x tx + [VDV] Add ProvisionalExpectedDepartureTime to Departure Times Group x tx + [VDV, SE] Add latesExpectedArrivalTimeForVehicle to Departure Times Group x tx + [SE] Add Aimed and expected Platform assignments to CALLs including a reference code. + + [FR] Add FirstOrLastJourney to JourneyTimesGroup x.tx. + [FR] add ArrivalOperatorRefs and DepartureOperatorRefs to Call arrival and Departure + [VDV] Add Velocity to MonitoredVehicleJourney JoueyProgerssGroup SIRI-SM and SIRI-VM + + [FR] Add AimedLatestPassengerAccessTime to MonitoredCall & OnwardsCall x tx + [MTA,FR,UK] Add ArrivalProximityText & DepartureProximityText to MonitoredCall & OnwardsCall x tx + [FR, MTA] Add Velocity to Journey & VelocityType x tx + + StopMonitoringRequest SIRI-SM + [VDV] Add Minimum-StopVisits¬PerVia to STopMonitoringRequestPolicy x tx + [VDV] Add HasMinimum-StopVisits¬Via to STopMonitoringCapabilities x tx + + StopMonitoringDelivery SIRI-SM + [FR] Add Service Exception element + [VDV] Add delivery variant to LineNote + [MTA] Add MaximumNumberOfCalls to VehiclelMonitoring request + + StopMonitoringDelivery SIRI-SX + Upgrade to DatexII + + ConnectionMonitoringDelivery SIRI-CM + [VDV] Add SuggestedWaitDecisionTime to MonitoredFeederArrival SIRI-CM x tx + + Enabling SIRI Lite + [MTA, UK] Add optional authenitication Key to Servce Request TODO + [MTA, UK] Add optional name to StopMonitoring response x tx + [MTA, UK] Add optional name to VehicleMonitoring response x tx + + Discovery services + [Fr] Add location to stop discovery x. + + General Framework + [VDV] Add ErrorNumber to Error Structure SIRI - All + + [VDV] Add new error conditions + + UnknownParticipant Recipient for a message to be distributed is unknown. +SIRI v2.0 + UnknownEndpoint Endpoint to which a message is to be distributed is unknown. +SIRI v2.0 + EndpointDeniedAccess Distribution message could not be delivered because not authorised.. +SIRI v2.0 + EndpointNotAvailable Recipient of a message to be distributed is not available. +SIRI v2.0 + UnapprovedKey User authorisation Key is not enabled. +SIRI v2.0 + + InvalidDataReferences Request contains references to identifiers that are not known. +SIRI v2.0 + ParametersIgnored Request contained parameters that were not supported by the producer. A response has been provided but some parameters have been ignored. +SIRI v2.0 + UnknownExtensions Request contained extensions that were not supported bu the producer. A response has been provided but some or all extensions have been ignored.. +SIRI v2.0 + + [FR] Add DistanceUnits & Velocity Units to ServiceRequestContext x tx + + General improvements to internal structure maintainability + Tidy up comments. x tx. + Improve modularisation (eg permissions/model permissions) to avoid circuloar refs x + Separate subdirectories for common request, model and core elements x + Separate out some model elements into separate packages x + Separate out model journeys from SIRI service packagaes x + Separate out discovery models from discovery services x + + Start of v2,0 ==> + +Changes to SIRI schema v1.4a since v1.3 +============================ + +2011-04-18 Corrections - New cumulative fix version 1.4a + Minor corrections 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 x + (ii) and siri_generalMessage_service.xsd subscription structure x + (iii) Missing type: Assign a type of normalizedString to formatRef x dx + + (b) siri_requests.xsd (line 814) ErrorConditionStructure should not be abstract . Fix from RV ixxi.biz- + made abstract x + + (c) siri_journey.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 x ?? + + (d) siri_productionTimetable_service.xsd Type on request ValidityPeriod start and end should be datetime not time + - Change to ClosedTimestampRange instead of ClosedDateeRange x tx. + - Fix Subscription request to be an element and to have IncrementalUpdate parameter Extensions x + + (e) siri_situation.xsd AffectedVehicleJourney should allow multiple journeys. Brian Ferris onebusaway.org>, x + + (f) ifopt_location.xsd Correct siri: namespace x + + (g) Fix up examples + (i) correct estimated timetable request, production timetable request, stop monitoring request, stop monitoring eprmissions. drop flat examples tx. + (ii) Add examples for facility monitorign and situation exchange ex + + (h) Drop vestigial As Flatgroup alternative coding tx + siri_connectionTimetable_service.xsd InterchangeHourneys x tx + siri_estimatedTimetable_service.xsd EstimatedCalls --> x tx + siri_productionTimetable_service.xsd DatedCalls --> x tx + + (i) Add missing type + siri_requests.xsd formatRef x + DATEXIISchema_1_0_1_0.xsd modelBaseversion + + (j)siri_facility.xsd TidyUp empty ValidityConditionGroup x + + (g) Add xmlSPy project spp. x + +====================== +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 x + (b) siriSg.xsd Remove unnecessary groups for decoupled version x tx. + +2009-03-31 Corrections + (a) StopMonitoring + Change the element type of MaximumNumberOfCalls.Previous, MaximumNumberOfCalls.Onwards from xsd:positiveInteger to xsd:nonNegativeInteger x tx. + + and clarify handling of + + MaximumNumberOfCalls : If calls are to be returned, maximum number of calls to include in response. If absent, exclude all calls. tx. + + Previous : Maximum number of previous calls to include. Zero for none. Only applies if MaximumNumberOfCalls specified. Zero for none. If MaximumNumber of Calls specified but MaximumNumberOfCalls.previous absent, include all previous calls. tx. + + Onwards : Maximum number of onwards calls to include. Zero for none. Only applies if MaximumNumberOfCalls specified. Zero for none. If MaximumNumber of Calls specified but MaximumNumberOfCalls.Onwards absent, include all onwards calls. tx. + +___________________________________________________________________________ + + (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 x + (b) siriSg.xsd Correct cardinality on servcierequest & subscription request to be many x + +2009-09-18 Siricommon - allow empty Terminate subscription response x + (a) Relax mandatory on in siri_common x + +2008-11-18 Revise FM servics + (a) Revise daytypes in siri_time.xsd x + +2008-11-17 Revise to support substitution groups + (a) Make all requests subtypes of abstract request. Add Subst elements x + + (b) Introduce AbstractFunctionalServiceRequest, AbstractCapabilityServiceRequest, AbstractDiscoveryRequest + as common supertypes. revised versiosn of siri_requests.xsd, siri_journey.xsd and siri_permissions.xsd, siri-All and siribase + + (c) add SiriSg and Siri_base.xsd packages +2008-11-12 Corrections to the Caridnailities on the siri_discovery services x + + (a) Change min maxes on >LineRef, StopPoints, Features etc etc x + +2008-10-08 Corrections to the SIRI service + (a) Add SubscriberRef to TerminateSubscriptionRequest x tx. + +2008-10-06 Corrections to the SIRI service + (a) Correct StopTimetable SubscriptionRequest to use group x + (b) Correct cardinality on AnnotatedStopPointRef in StopPointDelivery x + +2008-10-01 Corrections to the SIRI-SX service + (a) Add StatusFilterGroup to SIRI-SX request with Verification, Progress and Reality + (b) add 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 + (c) Allow a link projection & Offset on connection Link via AffectedPathLink + (d) Add an AfFfectedRoad 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 Corrections 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--> x + (c) Allow zero PT or Road Situation elements in a delivery x + (d) Affects Line group corrected to ref a lineref and not a route ref x + (e) Add missing scopeType to Situation classifier group x + (f) Add other subreasons x + (g) add secondary reasons x + +2008 05 08 StopMonitoring service + (a) Correct type on FeatureRef in Stop monitoring x + (b) Add StopMonitoringMultipleRequest x tx + (c) Add optional MonitoringRef to StopMonitoringDelivery so that can return id even if no data x tx. + +2008 03 27 + Fix up ifopt & ACSB version numbers to match ifopt 0.4 x + + +2008-03-26 EstimatedTimetable Production Timetable Service Service + Add wrapper tag for Line + Direction to help binding to Axisx x tx. + Wraps multiple instances x + ** Note this will break strict Compaptibility with 1.0 + +2008 03 12 + Add comments for elements and arrtributes that lacked them x + Correct wdsl errors x + Strip out degree character x + BeyondHorizon type corrected x + +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. x tx + Added a siri_all.xsd, ifopt_allStopPlace.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 x + Change name space : http://www.siri.org.uk/ to www.siri.org.uk/siri x.tx. + + harmonise Facility Monitoring + Revise SpecialNeeds to use acsb package x. + Use Ifopt facility etc x. + Factor out Extensions to utility file x. + +2007 04 V1.2 +======================================= diff --git a/release-notes/SIRI_XML-2.0q_changes.txt b/release-notes/SIRI_XML-2.0q_changes.txt index e77e475d..6630a699 100644 --- a/release-notes/SIRI_XML-2.0q_changes.txt +++ b/release-notes/SIRI_XML-2.0q_changes.txt @@ -1,57 +1,57 @@ -Changes made against SIRI 2.0p for SIRI 2.0q by VDV-Ums -2018-11-13 - D. Rubli, K. Grimme - -ifopt\ifopt_stop-v0.3.xsd -- Enum "ferrytPort" in StopPlaceTypeEnumeration changed to "ferryPort" - -siri_model\siri_reference-v2.0.xsd -- "PublishedLineName" inside "PublishedLineGroup" changed to "unbounded" to allow multiple definitions for different languages due to the xml:lang-Attribute -- "DestinationName" inside "PublishedLineGroup" changed to "unbounded" to allow multiple definitions for different languages due to the xml:lang-Attribute - -siri_model\siri_situationActions-v2.0.xsd: -- ActionsStructure.ActionsGroup.PublishToTvAction changed to unbounded -- ActionsStructure.ActionsGroup.NotifyBySmsAction changed to unbounded -- PublishToDisplayAction added to ActionsGroup -- ActionsStructure.ActionsGroup.PublishToTvAction.Ceefax and Teletext: annotation switched - -siri_model\siri_situationAffects-v2.0.xsd -- Wrapped "AffectedInterchanges" node around AffectedInterchange in AffectedCallStructure -- "PublishedLineName" inside "LineGroup" and "AffectedVehicleJourneyStructure" changed to "unbounded" to allow multiple definitions for different languages due to the xml:lang-Attribute -- "Route" inside "AffectedVehicleJourneyStructure" is now optional since all of its content are optional - -siri_model\siri_situationReasons-v2.0.xsd: -- MiscellaneousReasonEnumeration TPEC-code of "altercation" changed from pti19_1_Alias_6 to pti19_1_Alias_7 because TPEC-code pti19_1_Alias_6 was wrongly doubled in use for "emergencyServicesCall" and "altercation" -- MiscellaneousReasonEnumeration TPEC-code of "illVehicleOccupants" changed from pti19_1_Alias_7 to pti19_1_Alias_8 -- MiscellaneousReasonEnumeration TPEC-code of "undefinedProblem" changed from pti19_27 to pti19_255 -- MiscellaneousSubReasonEnumeration TPEC-code value "assault" added according to recommendation document and Datex2 -- EquipmentReasonEnumeration TPEC-code pti21_6_Alias_2 "defectiveTrain" added according to recommendation document -- EquipmentReasonEnumeration TPEC-code pti21_8_Alias_10 "leveCrossingFailure" changed to "levelCrossingFailure" according to recommendation document -- EquipmentReasonEnumeration TPEC-code pti21_8_Alias_11 "trafficManagementSystemFailure" added according to recommendation document -- EquipmentReasonEnumeration TPEC-code pti21_12_Alias_1 value changed from "oveheadWireFailure" to "overheadWireFailure" according to recommendation document -- EquipmentSubReasonEnumeration TPEC-code value "defectiveTrain" added according to recommendation document -- EquipmentSubReasonEnumeration TPEC-code value "leveCrossingFailure" changed to "levelCrossingFailure" according to recommendation document -- EquipmentSubReasonEnumeration TPEC-code value "trafficManagementSystemFailure" added according to recommendation document -- EquipmentSubReasonEnumeration TPEC-code value "oveheadWireFailure" changed to "overheadWireFailure" according to recommendation document -- EnvironmentReasonEnumeration TPEC-code pti22_13_Alias_1 "flashFloods" added according to recommendation document -- EnvironmentReasonEnumeration TPEC-code pti22_19_Alias_1 "mudslide" added according to recommendation document -- EnvironmentReasonEnumeration TPEC-code pti22_19_Alias_2 "rockfalls" added according to recommendation document -- EnvironmentReasonEnumeration TPEC-code pti22_19_Alias_3 "subsidence" added according to recommendation document -- EnvironmentReasonEnumeration TPEC-code pti22_19_Alias_4 "earthquakeDamage" added according to recommendation document -- EnvironmentReasonEnumeration TPEC-code pti22_3_Alias_3 "avalanches" added according to TPEG document -- EnvironmentReasonEnumeration TPEC-code pti22_13_Alias_1 "flashFloods" added according to recommendation document -- EnvironmentSubReasonEnumeration TPEC-code value "lighteningStrike" changed to "lightningStrike" according to recommendation document -- EnvironmentSubReasonEnumeration TPEC-code value "mudslip" changed to "mudslide" according to recommendation document and Datex2 - -siri_model\siri_situationServiceTypes-v1.0.xsd: -- ReportTypeEnumeration TPEC-code "2_27_1_Alias_2" changed to "27_1_Alias_2" according to recommendation document -- ReportTypeEnumeration TPEC-code "2_27_1_Alias_3" changed to "27_1_Alias_3" according to recommendation document - -siri_model\siri_situation-v2.0.xsd: -- RelatedToEnumeration Enum value "correctionTo" added according to recommendation document -- WorkflowStatusEnumeration Enum value "pendingApproval" added according to recommendation document -- AudienceEnumeration Enum value "authorities" added according to recommendation document -- AudienceEnumeration Enum value "transportOperators" added according to recommendation document -- Severity changed from mandatory to optional as mentioned in XSD annotation and recommendation - -xsd\siri_situationExchange_service.xsd: +Changes made against SIRI 2.0p for SIRI 2.0q by VDV-Ums +2018-11-13 - D. Rubli, K. Grimme + +ifopt\ifopt_stop-v0.3.xsd +- Enum "ferrytPort" in StopPlaceTypeEnumeration changed to "ferryPort" + +siri_model\siri_reference-v2.0.xsd +- "PublishedLineName" inside "PublishedLineGroup" changed to "unbounded" to allow multiple definitions for different languages due to the xml:lang-Attribute +- "DestinationName" inside "PublishedLineGroup" changed to "unbounded" to allow multiple definitions for different languages due to the xml:lang-Attribute + +siri_model\siri_situationActions-v2.0.xsd: +- ActionsStructure.ActionsGroup.PublishToTvAction changed to unbounded +- ActionsStructure.ActionsGroup.NotifyBySmsAction changed to unbounded +- PublishToDisplayAction added to ActionsGroup +- ActionsStructure.ActionsGroup.PublishToTvAction.Ceefax and Teletext: annotation switched + +siri_model\siri_situationAffects-v2.0.xsd +- Wrapped "AffectedInterchanges" node around AffectedInterchange in AffectedCallStructure +- "PublishedLineName" inside "LineGroup" and "AffectedVehicleJourneyStructure" changed to "unbounded" to allow multiple definitions for different languages due to the xml:lang-Attribute +- "Route" inside "AffectedVehicleJourneyStructure" is now optional since all of its content are optional + +siri_model\siri_situationReasons-v2.0.xsd: +- MiscellaneousReasonEnumeration TPEC-code of "altercation" changed from pti19_1_Alias_6 to pti19_1_Alias_7 because TPEC-code pti19_1_Alias_6 was wrongly doubled in use for "emergencyServicesCall" and "altercation" +- MiscellaneousReasonEnumeration TPEC-code of "illVehicleOccupants" changed from pti19_1_Alias_7 to pti19_1_Alias_8 +- MiscellaneousReasonEnumeration TPEC-code of "undefinedProblem" changed from pti19_27 to pti19_255 +- MiscellaneousSubReasonEnumeration TPEC-code value "assault" added according to recommendation document and Datex2 +- EquipmentReasonEnumeration TPEC-code pti21_6_Alias_2 "defectiveTrain" added according to recommendation document +- EquipmentReasonEnumeration TPEC-code pti21_8_Alias_10 "leveCrossingFailure" changed to "levelCrossingFailure" according to recommendation document +- EquipmentReasonEnumeration TPEC-code pti21_8_Alias_11 "trafficManagementSystemFailure" added according to recommendation document +- EquipmentReasonEnumeration TPEC-code pti21_12_Alias_1 value changed from "oveheadWireFailure" to "overheadWireFailure" according to recommendation document +- EquipmentSubReasonEnumeration TPEC-code value "defectiveTrain" added according to recommendation document +- EquipmentSubReasonEnumeration TPEC-code value "leveCrossingFailure" changed to "levelCrossingFailure" according to recommendation document +- EquipmentSubReasonEnumeration TPEC-code value "trafficManagementSystemFailure" added according to recommendation document +- EquipmentSubReasonEnumeration TPEC-code value "oveheadWireFailure" changed to "overheadWireFailure" according to recommendation document +- EnvironmentReasonEnumeration TPEC-code pti22_13_Alias_1 "flashFloods" added according to recommendation document +- EnvironmentReasonEnumeration TPEC-code pti22_19_Alias_1 "mudslide" added according to recommendation document +- EnvironmentReasonEnumeration TPEC-code pti22_19_Alias_2 "rockfalls" added according to recommendation document +- EnvironmentReasonEnumeration TPEC-code pti22_19_Alias_3 "subsidence" added according to recommendation document +- EnvironmentReasonEnumeration TPEC-code pti22_19_Alias_4 "earthquakeDamage" added according to recommendation document +- EnvironmentReasonEnumeration TPEC-code pti22_3_Alias_3 "avalanches" added according to TPEG document +- EnvironmentReasonEnumeration TPEC-code pti22_13_Alias_1 "flashFloods" added according to recommendation document +- EnvironmentSubReasonEnumeration TPEC-code value "lighteningStrike" changed to "lightningStrike" according to recommendation document +- EnvironmentSubReasonEnumeration TPEC-code value "mudslip" changed to "mudslide" according to recommendation document and Datex2 + +siri_model\siri_situationServiceTypes-v1.0.xsd: +- ReportTypeEnumeration TPEC-code "2_27_1_Alias_2" changed to "27_1_Alias_2" according to recommendation document +- ReportTypeEnumeration TPEC-code "2_27_1_Alias_3" changed to "27_1_Alias_3" according to recommendation document + +siri_model\siri_situation-v2.0.xsd: +- RelatedToEnumeration Enum value "correctionTo" added according to recommendation document +- WorkflowStatusEnumeration Enum value "pendingApproval" added according to recommendation document +- AudienceEnumeration Enum value "authorities" added according to recommendation document +- AudienceEnumeration Enum value "transportOperators" added according to recommendation document +- Severity changed from mandatory to optional as mentioned in XSD annotation and recommendation + +xsd\siri_situationExchange_service.xsd: - SituationExchangeServiceCapabilitiesStructure.TopicFiltering "FilterByKeword" changed to "FilterByKeyword" according to recommendation document \ No newline at end of file diff --git a/xsd/acsb/acsb_accessibility.xsd b/xsd/acsb/acsb_accessibility.xsd index f708f6d5..fcaf5102 100644 --- a/xsd/acsb/acsb_accessibility.xsd +++ b/xsd/acsb/acsb_accessibility.xsd @@ -1,138 +1,138 @@ - - - - - - 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.siri.org.uk/schema/2.0/ifopt}ifopt_accessibility.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, Crown Copyright 2006-2020 - - -
        -
      • Derived from the SIRI standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 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. - - - - - Identifier of LIMITATION. - - - - - Validty condition governing applicability of LIMITATION. - - - - - - - - - - - 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. - - - - - - - - - -       + + + + + + 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.siri.org.uk/schema/2.0/ifopt}ifopt_accessibility.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + CEN, Crown Copyright 2006-2021 + + +
        +
      • Derived from the SIRI standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 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. + + + + + Identifier of LIMITATION. + + + + + Validty condition governing applicability of LIMITATION. + + + + + + + + + + + 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. + + + + + + + + + +       diff --git a/xsd/acsb/acsb_all.xsd b/xsd/acsb/acsb_all.xsd index 358a9a71..3b33ce70 100644 --- a/xsd/acsb/acsb_all.xsd +++ b/xsd/acsb/acsb_all.xsd @@ -1,11 +1,11 @@ - - - - - - - - + + + + + + + + diff --git a/xsd/acsb/acsb_limitations.xsd b/xsd/acsb/acsb_limitations.xsd index 77457381..7da189ad 100644 --- a/xsd/acsb/acsb_limitations.xsd +++ b/xsd/acsb/acsb_limitations.xsd @@ -1,141 +1,141 @@ - - - - - - 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.siri.org.uk/schema/2.0/ifopt}ifopt_accessibility.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, Crown Copyright 2006-2020 - - -
        -
      • Derived from the SIRI standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG6 - - IFOPT Fixed Objects in Public Transport - accessibility Types. - Standard -       -       - Fixed Objects accessibility limitation types for IFOPT Fixed Objects in Public Transport. -       - - - - - Group of mobility LIMITATIONs. - - - - - - - - - - - Enumeration of values for an accessibility value. - - - - - - - - - - Group of sensory LIMITATIONs. - - - - - Whether a PLACE / SITE ELEMENT has Audible signals for the viusally impaired. - - - - - Whether a PLACE / SITE ELEMENT has Visual signals for the hearing impaired. - - - - - - - - Type for accessibility. - - - - - - - - Whether a PLACE / SITE ELEMENT is wheelchair accessible. - - - - - Whether a PLACE / SITE ELEMENT has step free access. - - - - - Whether a PLACE / SITE ELEMENT has escalator free access. - - - - - Whether a PLACE / SITE ELEMENT has lift free access. - - - - - Whether a PLACE / SITE ELEMENT is wheelchair accessible. - - - - - Whether a PLACE / SITE ELEMENT has Visual signals availble for the free access. - - - - - Whether a PLACE / SITE ELEMENT allows guide dog access. - - - -       + + + + + + 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.siri.org.uk/schema/2.0/ifopt}ifopt_accessibility.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + CEN, Crown Copyright 2006-2021 + + +
        +
      • Derived from the SIRI standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG6 + + IFOPT Fixed Objects in Public Transport - accessibility Types. + Standard +       +       + Fixed Objects accessibility limitation types for IFOPT Fixed Objects in Public Transport. +       + + + + + Group of mobility LIMITATIONs. + + + + + + + + + + + Enumeration of values for an accessibility value. + + + + + + + + + + Group of sensory LIMITATIONs. + + + + + Whether a PLACE / SITE ELEMENT has Audible signals for the viusally impaired. + + + + + Whether a PLACE / SITE ELEMENT has Visual signals for the hearing impaired. + + + + + + + + Type for accessibility. + + + + + + + + Whether a PLACE / SITE ELEMENT is wheelchair accessible. + + + + + Whether a PLACE / SITE ELEMENT has step free access. + + + + + Whether a PLACE / SITE ELEMENT has escalator free access. + + + + + Whether a PLACE / SITE ELEMENT has lift free access. + + + + + Whether a PLACE / SITE ELEMENT is wheelchair accessible. + + + + + Whether a PLACE / SITE ELEMENT has Visual signals availble for the free access. + + + + + Whether a PLACE / SITE ELEMENT allows guide dog access. + + + +       diff --git a/xsd/acsb/acsb_passengerMobility.xsd b/xsd/acsb/acsb_passengerMobility.xsd index 29ce46b0..304546d5 100644 --- a/xsd/acsb/acsb_passengerMobility.xsd +++ b/xsd/acsb/acsb_passengerMobility.xsd @@ -1,212 +1,212 @@ - - - - - - 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.siri.org.uk/schema/2.0/ifopt}ifopt_accessibility.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, Crown Copyright 2006-2020 - - -
        -
      • Derived from the SIRI standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 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 choice 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. Default is 'included'. - - - - - Relative ranking of USER NEED on a sclae 1-5 - - - - - Extensions to USETR NEED. - - - - - - - - - Passenger mobility USER NEED for which SUITABILITY is specified. - - - - - Passenger mobility USER NEED for which SUITABILITY is specified. - - - - - Passenger medical USER NEED for which SUITABILITY is specified. - - - - - - - - Passenger enceumbrance USER NEED for which SUITABILITY is specified. - - - - - - - - Identification of mobility USER NEEDs. - - - - - - - - - - - - - - Enumeration of specific psychosensory USER NEEDs. - - - - - - - - - - - - - - - - Enumeration of specific Medical USER NEEDs. - - - - - - - - - - - Enumeration of specific encumbrances USER NEEDs. - - - - - - - - - - - - - - - Type for of a specific SUITABILITY. - - - - - Whether the Facility is suitable. - - - - - USER NEED for which SUITABILITY is specified. - - - - - - - Identification of specific SUITABILITY. - - - - - - - -       + + + + + + 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.siri.org.uk/schema/2.0/ifopt}ifopt_accessibility.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + CEN, Crown Copyright 2006-2021 + + +
        +
      • Derived from the SIRI standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 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 choice 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. Default is 'included'. + + + + + Relative ranking of USER NEED on a sclae 1-5 + + + + + Extensions to USETR NEED. + + + + + + + + + Passenger mobility USER NEED for which SUITABILITY is specified. + + + + + Passenger mobility USER NEED for which SUITABILITY is specified. + + + + + Passenger medical USER NEED for which SUITABILITY is specified. + + + + + + + + Passenger enceumbrance USER NEED for which SUITABILITY is specified. + + + + + + + + Identification of mobility USER NEEDs. + + + + + + + + + + + + + + Enumeration of specific psychosensory USER NEEDs. + + + + + + + + + + + + + + + + Enumeration of specific Medical USER NEEDs. + + + + + + + + + + + Enumeration of specific encumbrances USER NEEDs. + + + + + + + + + + + + + + + Type for of a specific SUITABILITY. + + + + + Whether the Facility is suitable. + + + + + USER NEED for which SUITABILITY is specified. + + + + + + + Identification of specific SUITABILITY. + + + + + + + +       diff --git a/xsd/datex2/DATEXIISchema.xsd b/xsd/datex2/DATEXIISchema.xsd index a26f54ac..9064f4d8 100644 --- a/xsd/datex2/DATEXIISchema.xsd +++ b/xsd/datex2/DATEXIISchema.xsd @@ -1,3710 +1,3710 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/xsd/datex2/DATEXIISchemaWithDefinitions.xsd b/xsd/datex2/DATEXIISchemaWithDefinitions.xsd index e201e2ba..368a1e05 100644 --- a/xsd/datex2/DATEXIISchemaWithDefinitions.xsd +++ b/xsd/datex2/DATEXIISchemaWithDefinitions.xsd @@ -1,11523 +1,11523 @@ - - - - - A traffic condition which is not normal. - - - - - - - A characterization 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. - - - - - Assessment of the traffic flow conditions relative to normally expected conditions at this date/time. - - - - - A characterization of the traffic flow. - - - - - A characterization 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 stationary, or very near stationary, at the specified location (i.e. average speed is less than 10% of its free-flow level). - - - - - Traffic is queuing at the specified location, although there is still some traffic movement (i.e. average speed is between 10% and 25% of its free-flow level). - - - - - Traffic is slow moving at the specified location, but not yet forming queues (i.e. average speed is between 25% and 75% of its free-flow level). - - - - - Traffic is heavy at the specified location (i.e. average speed is between 75% and 90% of its free-flow level). - - - - - There are abnormal traffic conditions of an unspecified nature at the specified location. - - - - - Other than as defined in this enumeration. - - - - - - - Accidents are events where one or more vehicles are involved in collisions or in leaving the roadway. These include collisions between vehicles or with other road users or obstacles. - - - - - - - A descriptor indicating the most significant factor causing an accident. - - - - - A characterization of the nature of the accident. - - - - - The total number of people that are involved. - - - - - The total number of vehicles that are involved. - - - - - The vehicle involved in the 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 impaired visibility. - - - - - Not keeping a safe distance from the vehicle in front. - - - - - 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. - - - - - 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 mass transit vehicle. - - - - - Includes all accidents involving at least one moped. - - - - - Includes all accidents involving at least one motorcycle. - - - - - Accident involving radioactive material. - - - - - 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 action external to the traffic stream or roadway which could disrupt traffic. - - - - - - - Mobility of the activity. - - - - - - - - - - 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. EN ISO 14819-3 for the allocation of a location table number. - - - - - Version number associated with an ALERT-C table reference. - - - - - Area location defined by a specific Alert-C location. - - - - - - - - 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 (i.e. valid only for ring roads) the sense in which navigation should be made from the primary location to the secondary location, to avoid ambiguity. TRUE indicates positive RDS direction, i.e. direction of coding of 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. EN ISO 14819-3 for the allocation of a location table number. - - - - - Version number associated with 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. - - - - - - - - Linear location defined by a specific Alert-C location. - - - - - - - - - - Identification of a specific point, linear or area location in an ALERT-C location table. - - - - - Name of ALERT-C location. - - - - - Unique code within the ALERT-C location table which identifies the specific point, linear or area location. - - - - - - - - A positive integer number (between 1 and 63,487) which uniquely identifies a pre-defined Alert C location defined within an Alert-C table. - - - - - - 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. EN ISO 14819-3 for the allocation of a location table number. - - - - - Version number associated with an ALERT-C table reference. - - - - - - - - An integer number representing an angle in whole degrees between 0 and 359. - - - - - - 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 discrimination (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. - - - - - - - Authority initiated operation or activity that could disrupt traffic. - - - - - - - Type of authority initiated operation or activity that could disrupt traffic. - - - - - - - - - - Types of authority operations. - - - - - An operation involving authorised investigation work connected to an earlier reported accident. - - - - - An operation where a bomb squad is in action to deal with suspected or actual explosive or incendiary devices which 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 permanent or temporary operation established by customs and excise authorities on or adjacent to the carriageway. - - - - - An operation involving the juridical reconstruction of events for the purposes of judicial or legal proceedings. - - - - - 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 use by the road operator, such as for survey or inspection purposes, but not for traffic management purposes. - - - - - A permanent or temporary operation established by authorities on or adjacent to the carriageway for the purpose of gathering statistics or other traffic related information. - - - - - An operation to transport one or more VIPs. - - - - - An authority activity of undefined type. - - - - - A permanent or temporary operation established on or adjacent to the carriageway for inspection of vehicles by authorities (e.g. vehicle safety checks and tachograph checks). - - - - - A permanent or temporary operation established on or adjacent to the carriageway for weighing of vehicles by authorities. - - - - - A permanent or temporary facility established by authorities on the carriageway for weighing vehicles while in motion. - - - - - 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 the interval between the axles of the individual vehicle from front to back (e.g. 1, 2, 3...). This cannot exceed (numberOfAxles -1) if the numberOfAxles is also given as part of the VehicleCharacteristics. - - - - - - - - Vehicle axles per hour. - - - - - - The weight details of a specific axle on the vehicle. - - - - - Indicates the position of the axle on the vehicle numbered from front to back (i.e. 1, 2, 3...). This cannot exceed the numberOfAxles if provided as part of VehicleCharacteristics. - - - - - The weight of the specific axle, indicated by the axleSequenceIdentifier, on the vehicle numbered from front to back of the vehicle. - - - - - The maximum permitted weight of this specific axle on the vehicle. - - - - - - - - Generic data value(s) of either measured or elaborated data. Where values of different type are given in a single instance the metadata contained in the BasicDataValue must be applicable to all, otherwise separate instances must be given. - - - - - The extent to which the 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. 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. - - - - - The location (e.g. the stretch of road or area) to which the data value is pertinent/relevant. This may be different from the location of the measurement equipment (i.e. the measurement site location). - - - - - - - - Boolean has the value space required to support the mathematical concept of binary-valued logic: {true, false}. - - - - - - 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 (duration) 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, i.e. the section of road passing over another. - - - - - On the left hand feeder road. - - - - - On the left hand parallel 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, i.e. the section of road passing under another. - - - - - - - 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. - - - - - An earlier accident. - - - - - An earlier event. - - - - - An earlier incident. - - - - - Failure of roadside equipment. - - - - - Excessive heat. - - - - - Frost. - - - - - Holiday traffic. - - - - - Failure of road infrastructure. - - - - - Large numbers of visitors. - - - - - Obstruction (of unspecified type) on the roadway. - - - - - An alert relating to dangerous levels of pollution. - - - - - 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. - - - - - Radioactive leak alert. - - - - - A roadside event (of unspecified nature) whether planned or not. - - - - - Drivers being distracted and turning to look at an accident or other roadside event. - - - - - A security incident. - - - - - Shear weight of traffic. - - - - - Technical problems. - - - - - A terrorist incident. - - - - - An alert relating to the release of toxic gases and/or particulates. - - - - - A vandalism incident. - - - - - Other than as defined in this enumeration. - - - - - - - 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 un-coded observations/information. - - - - - A free text comment that can be used by the operator to convey un-coded 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 "greater than or equal to". - - - - - Logical comparison operator of "less than". - - - - - Logical comparison operator of "less than or equal to". - - - - - - - Types of compliance. - - - - - Advisory compliance . - - - - - Mandatory compliance. - - - - - - - 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. - - - - - - - Concentration defined in grams per cubic centimetre. - - - - - - A measure of concentration defined in µg/m3 (microgrammes/cubic metre). - - - - - - A measure of traffic density defined in number of vehicles per kilometre of road. - - - - - - 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). - - - - - Restricted for use only by authorities, traffic operators, publishers (service providers) and variable message signs. - - - - - - - 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. - - - - - Road widening work at the specified location - - - - - - - List of countries. - - - - - Austria - - - - - Belgium - - - - - Bulgaria - - - - - Switzerland - - - - - Serbia and Montenegro - - - - - Cyprus - - - - - Czech Republic - - - - - Germany - - - - - Denmark - - - - - Estonia - - - - - Spain - - - - - Finland - - - - - Faroe Islands - - - - - France - - - - - Great Britain - - - - - Guernsey - - - - - Gibraltar - - - - - 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. - - - - - - - A volumetric measure defined in cubic metres. - - - - - - - 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. - - - - - - - A combination of integer-valued year, month, day, hour, minute properties, a decimal-valued second property and a timezone property from which it is possible to determine the local time, the equivalent UTC time and the timezone offset from UTC. - - - - - - 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. - - - - - - - Specification of periods defined by the intersection of days, weeks and months. - - - - - Applicable day of the week. "All days of the week" is expressed by non-inclusion of this attribute. - - - - - Applicable week of the month (1 to 5). "All weeks of the month" is expressed by non-inclusion of this attribute. - - - - - Applicable month of the year. "All months of the year" is expressed by non-inclusion of this attribute. - - - - - - - - Classifications of a delay banded by length (i.e. the additional travel time). - - - - - Negligible delay. - - - - - Delay up to ten minutes. - - - - - Delay between ten minutes and thirty minutes. - - - - - Delay between thirty minutes and one hour. - - - - - Delay between one hour and three hours. - - - - - Delay between three hours and six hours. - - - - - Delay longer than six hours. - - - - - - - The details of the delays being caused by the situation element defined in the situation record. It is recommended to only use one of the optional attributes to avoid confusion. - - - - - The time band within which the additional travel time due to adverse travel conditions of any kind falls, when compared to "normal conditions". - - - - - Coarse 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. - - - - - Anticlockwise direction of travel on a ring road. - - - - - Clockwise direction of travel on a ring road. - - - - - North bound direction of travel. - - - - - North east bound direction of travel. - - - - - East bound direction of travel. - - - - - South east bound direction of travel. - - - - - South bound direction of travel. - - - - - South west bound direction of travel. - - - - - West bound direction of travel. - - - - - North west bound direction of travel. - - - - - Heading towards town centre direction of travel. - - - - - Heading out of or away from the town centre direction of travel. - - - - - - - Deliberate human action of either a public disorder nature or of a situation alert type which could disrupt traffic. - - - - - - - Includes all situations of a public disorder type or of an alert type, with potential to disrupt traffic. - - - - - - - - - - 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 an attack on a vehicle or its occupants has taken place. - - - - - A manned blockade or barrier across a road stopping vehicles passing. - - - - - An alert to a situation where suspected or actual explosive or incendiary devices may cause disruption to traffic. - - - - - 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 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. - - - - - A situation of public disorder, with potential to disrupt traffic. - - - - - An alert to a radioactive leak which may endanger the public and hence may cause traffic disruption. - - - - - A situation of public disorder involving violent behaviour and/or destruction of property with the potential to disrupt traffic. - - - - - A situation resulting from any act of sabotage. - - - - - An official alert 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 stolen. - - - - - An alert to a toxic release of gases and/or particulates into the environment which may endanger the public and hence may cause traffic disruption. - - - - - An alert to a perceived or actual threat of an unspecified nature, which could disrupt traffic. - - - - - 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. - - - - - - - An 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 snow slides. - - - - - 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. - - - - - Falling ice off trees, power lines or structures which may cause traffic disruption. - - - - - Falling light ice or snow off trees, power lines or structures which may cause traffic disruption. - - - - - 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 forest fire adjacent to the roadway. - - - - - 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 is obstructed or partially obstructed by overflows from one or more sewers. - - - - - 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. - - - - - Smoke or fumes which may hinder driving conditions or distract drivers. - - - - - 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. - - - - - - - Equipment or system which is faulty, malfunctioning or not in a fully operational state that may be of interest or concern to road operators and road users. - - - - - - - Failure, malfunction or non operational condition of equipment or system. - - - - - The type of equipment or system which is faulty, malfunctioning or not in a fully operational state. - - - - - - - - - - Types of fault, malfunctioning or non operational conditions of equipment or systems. - - - - - Not working or functioning. - - - - - Out of service (usually for operational reasons). - - - - - Working incorrectly. - - - - - Working intermittently. - - - - - - - Types of equipment and systems used to support the operation of the road network. - - - - - Automated toll system. - - - - - Emergency roadside telephones. - - - - - Gallery lights. - - - - - Signs used to control lane usage (e.g. in tidal flow systems or hard shoulder running). - - - - - Level crossing (barriers and signals). - - - - - Matrix signs. These normally comprise a symbol display area surrounded by four lights (usually amber) which flash when a symbol is displayed. - - - - - Ramp control equipment. - - - - - Roadside communications system which is used by one or more roadside equipments or systems. - - - - - Roadside power system which is used by one or more roadside equipments or systems. - - - - - Signs used to control traffic speed. - - - - - Street or road lighting. - - - - - Temporary traffic lights. - - - - - Toll gates. - - - - - Sets of traffic lights. - - - - - Traffic signals. - - - - - Tunnel lights. - - - - - Tunnel ventilation system. - - - - - Variable message signs. - - - - - Other than as defined in this enumeration. - - - - - - - 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. - - - - - For "Client Pull" exchange mode (operating mode 3 - snapshot) it defines the date/time at which the snapshot was produced. - - - - - For "Client Pull" exchange mode (operating mode 3 - snapshot) it defines the date/time after which the snapshot is no longer considered valid. - - - - - Indicator that this exchange is due to "keep alive" functionality. - - - - - The type 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. - - - - - - - - - - - - - - - - - - A location defined by reference to an external/other referencing system. - - - - - A code in the external referencing system which defines the location. - - - - - Identification of the external/other location referencing system. - - - - - - - - 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. - - - - - - - - A floating point number whose value space consists of the values m × 2^e, where m is an integer whose absolute value is less than 2^24, and e is an integer between -149 and 104, inclusive. - - - - - - Type of fuel used by a vehicle. - - - - - Battery. - - - - - Biodiesel. - - - - - Diesel. - - - - - Diesel and battery hybrid. - - - - - Ethanol. - - - - - Hydrogen. - - - - - Liquid gas of any type including LPG. - - - - - Liquid petroleum gas. - - - - - Methane gas. - - - - - Petrol. - - - - - Petrol and battery hybrid. - - - - - - - General instruction that is issued by the network/road operator which is applicable to drivers and sometimes passengers. - - - - - - - General instruction that is issued by the network/road operator which is applicable to drivers and sometimes passengers. - - - - - - - - - - General instructions that may be issued to road users (specifically drivers and sometimes passengers) by an operator or operational system in support of network management activities. - - - - - Allow emergency vehicles to pass. - - - - - Approach with care. - - - - - Drivers are to avoid the area. - - - - - Close all windows and turn off heater and vents. - - - - - Cross junction with care. - - - - - Do not allow unnecessary gaps. - - - - - Do not leave your vehicle. - - - - - Do not throw out any burning objects. - - - - - Do not use navigation systems to determine routing. - - - - - Drive carefully. - - - - - Drive with extreme caution. - - - - - Flash your lights to warn oncoming traffic of hazard ahead. - - - - - Follow the vehicle in front, smoothly. - - - - - Increase normal following distance. - - - - - In emergency, wait for patrol service (either road operator or police patrol service). - - - - - Keep your distance. - - - - - Leave your vehicle and proceed to next safe place. - - - - - No naked flames. - - - - - No overtaking on the specified section of road. - - - - - No smoking. - - - - - No stopping. - - - - - No U-turns. - - - - - Observe signals. - - - - - Observe signs. - - - - - Only travel if absolutely necessary. - - - - - Overtake with care. - - - - - 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 bus service. - - - - - Use fog lights. - - - - - Use hazard warning lights. - - - - - Use headlights. - - - - - Use rail service. - - - - - Use tram service. - - - - - Use underground service. - - - - - Wait for escort vehicle. - - - - - Other than as defined in this enumeration. - - - - - - - Network management action that is instigated either manually or automatically by the network/road operator. Compliance with any resulting control may be advisory or mandatory. - - - - - - - The type of traffic management action instigated by the network/road operator. - - - - - Type of person that is manually directing traffic (applicable if generalNetworkManagementType is set to "trafficBeingManuallyDirected"). - - - - - - - - - - Types of network management actions. - - - - - The bridge at the specified location has swung or lifted and is therefore temporarily closed to traffic. - - - - - A convoy service is in operation. - - - - - Signs are being put out before or around an obstacle to protect drivers. - - - - - Ramp metering is now active at the specified location. - - - - - Traffic is being controlled by temporary traffic lights (red-yellow-green or red-green). - - - - - Toll gates are open with no fee collection at the specified location. - - - - - Traffic is being manually directed. - - - - - Traffic in the specified direction is temporarily held up due to an unplanned event (e.g. for clearance of wreckage following an accident). - - - - - Other than as defined in this enumeration. - - - - - - - Any stationary or moving obstacle of a physical nature, other than of an animal, vehicle, environmental, or damaged equipment nature. - - - - - - - Characterization of the type of general obstruction. - - - - - - - - - - - A publication used to make level B extensions at the publication level. - - - - - - - The name of the generic publication. - - - - - - - - - - A generic SituationRecord for use when adding level B extensions at the SituationRecord level. - - - - - - - The name of the GenericSituationRecord. - - - - - - - - - - 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. - - - - - - - - - - A group of one or more physically separate locations which have no specific order. - - - - - - - Location contained in a non ordered group of locations. - - - - - - - - - - Group of people involved in the event having common characteristics and/or status. - - - - - The number of people of this group that are involved. - - - - - The injury status of the people involved. - - - - - The involvement role of the people. - - - - - The category of persons involved. - - - - - - - - Group of the vehicles involved having common characteristics and/or status. - - - - - The number of vehicles of this group that are involved. - - - - - Vehicle status. - - - - - - - - - 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 of the geographic area 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 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. - - - - - - - - Details of atmospheric humidity. - - - - - The amount of water vapour in the air, as a percentage of the amount of water vapour in saturated air at the same temperature and at atmospheric pressure. The measurement is taken between 1.5 and 2 m above the ground and behind a meteo screen. - - - - - - - - Measurements of atmospheric humidity. - - - - - - - - - - - - - An assessment of the impact that an event or operator action defined by the situation record has on the driving conditions. - - - - - The ratio of current capacity to the normal (free flow) 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 usable lanes on the carriageway which are now restricted either fully or partially (this may include the hard shoulder if it is normally available for operational use, e.g. in hard shoulder running schemes). - - - - - The number of usable lanes in the specified direction which remain fully operational (this may include the hard shoulder if it is being used as an operational lane). - - - - - The normal number of usable lanes in the specified direction that the carriageway has before reduction due to roadworks or traffic events. - - - - - The total width of the combined operational lanes in the specified direction. - - - - - The type of constriction to which traffic is subjected as a result of an event or operator action. - - - - - - - - - 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. - - - - - - - An obstruction on the road resulting from the failure or damage of infrastructure on, under, above or close to the road. - - - - - - - Characterization of an obstruction on the road resulting from the failure or damage of infrastructure on, under, above or close to the road. - - - - - - - - - - Types of infrastructure 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 surface has sunken or collapsed in places due to sewer failure. - - - - - Damage to a bridge that may cause traffic disruption. - - - - - Damage to a crash barrier that may cause traffic disruption. - - - - - Damage to an elevated section of the carriageway over another carriageway that may cause traffic disruption. - - - - - Damage to a gallery that may cause traffic disruption. - - - - - Damage to a gantry above the roadway that may cause traffic disruption. - - - - - Damage to the road surface that may cause traffic disruption. - - - - - Damage to a tunnel that may cause traffic disruption. - - - - - Damage to a viaduct that may cause traffic disruption. - - - - - 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. - - - - - Weak bridge capable of carrying a reduced load, typically with a reduced weight limit restriction imposed. - - - - - Other than as defined in this enumeration. - - - - - - - Types of injury status of people. - - - - - Dead. - - - - - Injured requiring medical treatment. - - - - - Seriously injured requiring urgent hospital treatment. - - - - - Slightly injured requiring medical treatment. - - - - - Uninjured. - - - - - Injury status unknown. - - - - - - - A measure of the quantity of application of a substance to an area defined in kilogrammes per square metre. - - - - - - A measure of precipitation intensity defined in millimetres per hour. - - - - - - 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. - - - - - - - A group of one or more physically separate locations arranged as an ordered set that defines an itinerary or route. The index indicates the order. - - - - - - - Location contained in an itinerary (i.e. an ordered set of locations defining a route or itinerary). - - - - - - - - - - - - Destination of a route or final location in an itinerary. - - - - - - - - - - A measure of speed defined in kilometres per hour. - - - - - - 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 carriageways 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. - - - - - - - A language datatype, identifies a specified language. - - - - - - 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 (true) or not (false). If finished (i.e. end is true) then the overallEndTime in the OverallPeriod class associated with the SituationRecord must be populated. - - - - - - - - A linear section along a single road with optional directionality defined between two points on the same 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. - - - - - No load. - - - - - 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. - - - - - Any goods of a commercial nature. - - - - - Materials classed as being of a hazardous nature. - - - - - Liquid of an unspecified 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. - - - - - Materials classed as being dangerous when exposed to water (e.g. materials which may react exothermically with water). - - - - - 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 or petroleum. - - - - - 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 which may be used by clients for visual display on user interfaces. - - - - - - - - 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. - - - - - On the carriageway or lane which is inbound towards the centre of the town or city. - - - - - In gallery. - - - - - 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 elevated section of road. - - - - - On flyover, i.e. on section of road over another road. - - - - - 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. - - - - - On underground section of road. - - - - - On underpass, i.e. section of road which passes under another road. - - - - - On the carriageway or lane which is outbound from the centre of the town or city. - - - - - Over the crest of a hill. - - - - - On the main carriageway within a junction between exit slip road and entry slip road. - - - - - - - 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. - - - - - - - Details of the maintenance vehicles involved in the roadworks activity. - - - - - 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. - - - - - - - - Roadworks involving the maintenance or installation of infrastructure. - - - - - - - The type of road maintenance or installation work at the specified location. - - - - - - - - - - A cause of this situation record which is managed by the publication creator, i.e. one which is represented by another situation record produced by the same publication creator. - - - - - - - A reference to another situation record produced by the same publication creator which defines a cause of the event defined here. - - - - - - - - - - Information relating to the management of the situation record. - - - - - - - - - - Types of matrix sign faults. - - - - - Comunications failure affecting matrix sign. - - - - - Incorrect aspect (face) is being displayed. - - - - - Not currently in service (e.g. intentionally disconnected or switched off during roadworks). - - - - - 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 individual vehicle measurements. - - - - - 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 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. - - - - - Measured or derived visibility information. - - - - - Measured or derived wind information. - - - - - - - Contains optional characteristics for the specific measured value (indexed to correspond with the defined characteristics of the measurement at the referenced measurement site) which override the static characteristics defined in the MeasurementSiteTable. - - - - - 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. - - - - - The version of the measurement site record, managed by systems external to DATEX II. - - - - - The date/time that this version of the measurement site record was defined. This is managed by systems external to DATEX II. - - - - - 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. - - - - - Composition to the indexed measurement specific characteristics associated with the measurement site. The index uniquely associates the measurement characteristics with the corresponding indexed measurement values for the measurement site. - - - - - - - - - - - - - - - - - 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 identification 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 value 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 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. 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. - - - - - - - - - A measure of distance defined in metres in a floating point format. - - - - - - A measure of distance defined in metres in a non negative integer format. - - - - - - An indication of whether the associated instance of a SituationRecord is mobile (e.g. a march or parade moving along a road) or stationary. - - - - - An indication of whether the associated instance of a SituationRecord is mobile (e.g. a march or parade moving along a road) or stationary. - - - - - - - - Types of mobility relating to a situation element defined by a SituationReord. - - - - - The described element of a situation is moving. - - - - - The described element of a situation is stationary. - - - - - The mobility of the described element of a situation 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). - - - - - - - - - - - - - - Network management action which is applicable to the road network and its users. - - - - - - - Defines whether the network management instruction or the control resulting from a network management action is advisory or mandatory. - - - - - The ultimate traffic direction to which the network management is applicable. - - - - - The type of traffic to which the network management is applicable. - - - - - Places, in generic terms, at which the network management applies. - - - - - Defines whether the network management is initiated by an automatic system. - - - - - The characteristics of those vehicles for which the network management is applicable. - - - - - - - - - - A cause of this situation record which is not managed by the publication creator, i.e. one which is not represented by another situation record produced by the same publication creator. - - - - - - - Description of a cause which is not managed by the publication creator (e.g. an off network cause). - - - - - Indicates an external influence that may be the causation of components of a situation. - - - - - - - - - - An integer number whose value space is the set {0, 1, 2, ..., 2147483645, 2147483646, 2147483647}. - - - - - - 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 diesel on the road. - - - - - 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 petrol on road. - - - - - The road surface is damaged, severely rutted or potholed (i.e. it is in a poor state of repair). - - - - - The road surface is slippery due to an unspecified cause. - - - - - Other than as defined in this enumeration. - - - - - - - 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. - - - - - The mobility of the obstruction. - - - - - - - - - - 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. - - - - - Scattered fragments of wreckage or other material on the road. - - - - - 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. - - - - - Unspecified hazard(s) on the road 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. - - - - - Industrial accident near the roadway 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 hazard 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. - - - - - "Subscription Management Mechanism" - a specialized operating mode to handle subscriptions. - - - - - "Publisher Push on Occurrence" operating mode. - - - - - "Publisher Push Periodic" operating mode. - - - - - "Client Pull" operating mode. - - - - - - - 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. - - - - - - - - - - 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. - - - - - A request, either internal or external, has been received to implement an action. It has neither been approved nor has any activity yet been undertaken to implement the action. - - - - - The action has been approved by the recipient of the request but activity to implement the action has not yet commenced. - - - - - The action is in the process of being implemented. - - - - - The action is fully implemented. - - - - - The action has been rejected by the recipient of the request and hence is not implemented. - - - - - A request, either internal or external, has been received to terminate the action, but activity to terminate the action has not yet commenced. - - - - - The action is in the process of being terminated either because the action has reached the end of its validity period or because new circumstances have arisen and its termination has been requested, e.g. because of a traffic jam on the alternative route. - - - - - - - A continuous or discontinuous 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 single time period, a recurring time period or a set of different recurring time periods during which validity is true. - - - - - A single time period, a recurring time period or a set of different recurring time periods during which validity is false. - - - - - - - - Levels of severity of a situation as whole assessed by the impact that the situation 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 medium level. - - - - - Perceived by supplier as being of a low level. - - - - - Perceived by supplier as being of the lowest discernible level. - - - - - Perceived by supplier as having a severity rating of none. - - - - - Perceived by supplier as being of an unknown level. - - - - - - - Passenger car units per hour. - - - - - - 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 description of the information which is to be found in the publications originating from the particular feed (URL). - - - - - 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. - - - - - - - - The default language used throughout the payload publications, specified by an ISO 639-2 3-alpha code. - - - - - - A measure of percentage. - - - - - - 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. - - - - - A recurring period of a day. - - - - - A recurring period defined in terms of days of the week, weeks of the month and months of the year. - - - - - - - - Categories of person. - - - - - Adult. - - - - - Child (age 4 to 17). - - - - - A member of the emergency services, other than the police. - - - - - A member of the fire service. - - - - - Infant (age 0 to 3). - - - - - A member of the medical service. - - - - - A member of the general public. - - - - - 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 member of the local traffic warden service. - - - - - A very important person. - - - - - - - List of types of places. - - - - - Around bends in the road. - - - - - At customs posts. - - - - - At high altitudes. - - - - - At toll plazas. - - - - - In galleries. - - - - - In low lying areas. - - - - - In roadworks areas. - - - - - In shaded areas. - - - - - In the city centre. - - - - - In the inner city areas. - - - - - In tunnels. - - - - - On bridges. - - - - - On elevated sections of the road. - - - - - On entering or leaving tunnels. - - - - - On entry into the country. - - - - - On flyover sections of the road, i.e. sections of the road which pass over another road. - - - - - On leaving the country. - - - - - On motorways. - - - - - On non motorways. - - - - - On roundabouts. - - - - - On slip roads. - - - - - On underground sections of the road. - - - - - On underpasses, i.e. sections of the road which pass under another road. - - - - - Over the crest of hills. - - - - - 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). - - - - - Polycyclic aromatic hydrocarbons. - - - - - 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. - - - - - 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. - - - - - Pollution of an unspecified nature. - - - - - 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. - - - - - - - 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. - - - - - - - Indication of whether precipitation is present or not. True indicates there is no precipitation. - - - - - - - - - - - Types of precipitation. - - - - - Light, fine rain. - - - - - Freezing 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 assigned to the 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 the set of predefined locations. - - - - - The version of the predefined location set. - - - - - - - - - - A publication containing one or more sets of predefined locations. - - - - - - - - - - - - - - Levels of confidence that the sender has in the information, ordered {certain, probable, risk of}. - - - - - The source is completely 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. - - - - - - - Organised public event which could disrupt traffic. - - - - - - - Type of public event which could disrupt traffic. - - - - - - - - - - Type of public event (Datex2 PublicEventTypeEnum and PublicEventType2Enum combined) - - - - - Unknown - - - - - Agricultural show or event which could disrupt traffic. - - - - - Air show or other aeronautical event which could disrupt traffic. - - - - - Art event that could disrupt traffic. - - - - - Athletics event that could disrupt traffic. - - - - - Beer festival 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. - - - - - Boat show which 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. - - - - - Commercial event which could disrupt traffic. - - - - - Concert event that could disrupt traffic. - - - - - Cricket match that could disrupt traffic. - - - - - Cultural event which 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 festival that could disrupt traffic. - - - - - Film or TV making event which could disrupt traffic. - - - - - Fireworks display that could disrupt traffic. - - - - - Flower event that could disrupt traffic. - - - - - Food festival that could disrupt traffic. - - - - - Football match that could disrupt traffic. - - - - - Periodic (e.g. annual), often traditional, gathering for entertainment, which could disrupt traffic. - - - - - Gardening and/or flower show or event 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 show which could disrupt traffic. - - - - - Motor sport race meeting that could disrupt traffic. - - - - - Open air concert that could disrupt traffic. - - - - - Formal display or organised procession which could disrupt traffic. - - - - - An 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. - - - - - Sound and light show 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. - - - - - Street festival that could disrupt traffic. - - - - - Tennis tournament that could disrupt traffic. - - - - - Theatrical event that could disrupt traffic. - - - - - Sporting event or series of events of unspecified type lasting more than one day which could disrupt traffic. - - - - - A periodic (e.g. annual), often traditional, gathering for trade promotion, which could disrupt traffic. - - - - - Water sports meeting that could disrupt traffic. - - - - - Wine festival that could disrupt traffic. - - - - - Winter sports meeting or event (e.g. skiing, ski jumping, skating) that could disrupt traffic. - - - - - Other than as defined in this enumeration. - - - - - - - A reference to an identifiable object instance (e.g. a GUID reference). - - - - - - Directions of traffic flow relative to sequential numbering scheme of reference points. 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. - - - - - - - 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 assessment 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 flow is normal at the specified location at this date/time. - - - - - Traffic is lighter than normally expected at the specified location at this date/time. - - - - - Traffic is very much 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. - - - - - A request for the supplier's catalogue. - - - - - A request for the client's filter as currently stored by the supplier. - - - - - A request for current data. - - - - - A request for historical data, i.e. data which was valid within an historical time window. - - - - - A request for a client's subscription as currently held by a supplier. - - - - - - - Rerouting management action that is issued by the network/road operator. - - - - - - - Type of rerouting management action instigated by operator. - - - - - A description of the rerouting itinerary. - - - - - Indication of whether the rerouting is signed. - - - - - The specified entry on to another road at which the alternative route commences. - - - - - The specified exit from the normal route/road at which the alternative route commences. - - - - - The intersecting road or the junction at which the alternative route commences. - - - - - The definition of the alternative route (rerouting) specified as an ordered set of locations (itinerary) which may be specific to one or more defined destinations. - - - - - - - - - - Management actions relating to rerouting. - - - - - Do not follow diversion signs. - - - - - Rerouted traffic is not to use the specified entry onto the identified road to commence the alternative route. - - - - - Rerouted traffic is not to use the specified exit from the identified road to commence the alternative route. - - - - - Rerouted traffic is not to use the specified intersection or junction. - - - - - Rerouted traffic is to follow the diversion signs. - - - - - Rerouted traffic is to follow local diversion. - - - - - Rerouted traffic is to follow the special diversion markers. - - - - - 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. - - - - - An acknowledgement that the supplier has received and complied with the client's request. - - - - - A notification that the supplier has denied the client's request for a catalogue. - - - - - A notification that the supplier has denied the client's request for a filter. - - - - - A notification that the supplier has denied the client's request for a data. - - - - - A notification that the supplier has denied the client's request for a subscription. - - - - - - - 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 an unspecified nature. - - - - - Controlled avalanche work. - - - - - Installation of new equipments or systems on or along-side the roadway. - - - - - Grass cutting work. - - - - - Maintenance of road, associated infrastructure or equipments. - - - - - Works which are overhead of the carriageway. - - - - - 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. - - - - - Spreading of salt and / or grit on the road surface to prevent or melt snow or ice. - - - - - Snowploughs or other similar mechanical devices in use to clear snow from the road. - - - - - Tree and vegetation cutting work adjacent to the roadway. - - - - - Other than as defined in this enumeration. - - - - - - - Details of disruption to normal road operator services - - - - - - - The type of road operator service which is disrupted. - - - - - - - - - - Types of disruption to road operator services relevant to road users. - - - - - Emergency telephone number for use by public to report incidents is out of service. - - - - - Road information service telephone number is out of service. - - - - - No traffic officer patrol service is operating. - - - - - - - Road, carriageway or lane management action that is instigated by the network/road operator. - - - - - - - Type of road, carriageway or lane management action instigated by operator. - - - - - The minimum number of persons required in a vehicle in order for it to be allowed to transit the specified road section. - - - - - The carriageway which is the subject of the management action. - - - - - The lane which is the subject of the management action. - - - - - - - - - - Management actions relating to road, carriageway or lane usage. - - - - - Dedicated car pool lane(s) are in operation for vehicles carrying at least the specified number of occupants. - - - - - Carriageway closures are in operation at the specified location. - - - - - Clear a lane for emergency vehicles. - - - - - Clear a lane for snow ploughs and gritting vehicles. - - - - - 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. - - - - - Do not use the specified lane(s) or carriageway(s). - - - - - The hard shoulder is open as an operational lane. - - - - - Road closures occur intermittently on the specified road in the specified direction for short durations. - - - - - Keep to the left. - - - - - Keep to the right. - - - - - Lane closures are in operation at the specified location for vehicles with the specified characteristics or all, if none defined, in the specified direction. - - - - - Lane deviations are in operation at the specified location. - - - - - Normal lane widths are temporarily reduced. - - - - - A new layout of lanes/carriageway has been implemented associated with roadworks. - - - - - 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. - - - - - The road has been cleared of earlier reported problems. - - - - - The road is closed to vehicles with the specified characteristics or all, if none defined, in the specified direction. - - - - - Traffic officers or police are driving slowly in front of a queue of traffic to create a gap in the traffic to allow for clearance activities to take place in safety on the road ahead. - - - - - 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. - - - - - Dedicated tidal flow lane(s) are in operation in the specified direction. - - - - - Traffic is being directed back down the opposite carriageway, possibly requiring the temporary removal of the central crash barrier. - - - - - The specified lane(s) or carriageway(s) may be used. The normal lane(s) or carriageway(s) restrictions are not currently in force. - - - - - Use the specified lane(s) or carriageway(s). - - - - - Vehicles are being stored on the roadway and/or at a rest area or service area at the specified location. - - - - - Other than as defined in this enumeration. - - - - - - - Details of road side assistance required or being given. - - - - - - - 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. - - - - - - - One of a sequence of roadside reference points along a road, normally spaced at regular intervals along each carriageway with a sequence of identification from a known starting point. - - - - - Roadside reference point identifier, unique on the specified road. - - - - - Identification of the road administration area which contains the reference point. - - - - - Name of a road. - - - - - 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 roadside reference point. - - - - - The distance of the roadside reference point from the starting point of the sequence on the road. - - - - - - - - A linear section along a single road defined between two points on the same road identified by roadside reference points. - - - - - - - - - - The point (called Primary point) which is at the downstream end of a linear road section. The point is identified by a roadside reference point. - - - - - - - - - The point (called Secondary point) which is at the upstream end of a linear road section. The point is identified by a roadside reference point. - - - - - - - - - Details of disruption to normal roadside services (e.g. specific services at a service areas). - - - - - - - The type of roadside service which is disrupted. - - - - - - - - - - Types of disruption to roadside 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. - - - - - - - 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. - - - - - - - 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 under traffic or not under traffic. 'True' indicates the road is under traffic. - - - - - 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. - - - - - - - Seconds. - - - - - - 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. - - - - - Composition to the indexed measured value associated with the measurement site. The index uniquely associates the measurement value with the corresponding indexed measurement characteristics defined for the measurement site. - - - - - - - - - - - - - - - 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. - - - - - Each situation may iterate through a series of versions during its life time. The situation version uniquely identifies the version of the situation. It is generated and used by systems external to DATEX II. - - - - - The date/time that this current version of the Situation was written into the database of the supplier which is involved in the data exchange. - - - - - - - - - - - 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 II. - - - - - 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. - - - - - The extent to which the related information may be circulated, according to the recipient type. Recipients must comply with this confidentiality statement. This overrides any confidentiality defined for the situation as a whole in the header information. - - - - - An assessment of the degree of likelihood that the reported event will occur. - - - - - - - - - A comment which may be freely distributed to the general public - - - - - A comment which should not be distributed to the general public. - - - - - - - - - - - - Details of the source from which the information was obtained. - - - - - ISO 3166-1 two character country code of the source of the information. - - - - - Identifier 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. - - - - - - - Speed management action that is instigated by the network/road operator. - - - - - - - Type of speed management action instigated by operator. - - - - - Temporary limit defining the maximum advisory or mandatory speed of vehicles. - - - - - - - - - - Management actions relating to speed. - - - - - Automatic speed control measures are in place at the specified location, whereby speed limits are set by an automatic system which is triggered by traffic sensing equipment. - - - - - Do not slow down unnecessarily. - - - - - Observe speed limit. - - - - - Police speed checks are in operation. - - - - - Reduce your speed. - - - - - Other than as defined in this enumeration. - - - - - - - Details of percentage (from an observation set) of vehicles whose speeds fall below a stated value. - - - - - The percentage of vehicles from the observation set whose speeds fall below the stated speed (speedPercentile). - - - - - The speed below which the associated percentage of vehicles in the measurement set are travelling at. - - - - - - - - A character string whose value space is the set of finite-length sequences of characters. Every character has a corresponding Universal Character Set code point (as defined in ISO/IEC 10646), which is an integer. - - - - - - - - The subjects with which the roadworks are associated. - - - - - The subject type 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. - - - - - Crash barrier. - - - - - Gallery. - - - - - Gantry over or above the roadway. - - - - - Gas mains. - - - - - Motorway or major road interchange. - - - - - Motorway or major road junction. - - - - - Level-crossing or associated equipment. - - - - - Road lighting system. - - - - - Equipment used for determining traffic measurements. - - - - - Installations along the roadway designed to reduce road noise in the surrounding environment. - - - - - Road. - - - - - Roadside drains. - - - - - Roadside embankment. - - - - - Roadside equipment. - - - - - Road signs. - - - - - Roundabout. - - - - - Toll gate. - - - - - 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. - - - - - The client's subscription as registered with a supplier is currently active. - - - - - The client's subscription as registered with a supplier is currently suspended. - - - - - - - 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. - - - - - Indicates that the location is given with a precision which is better than the stated value in metres. - - - - - The sequential number of an exit/entrance ramp from a given location in a given direction (normally used to indicate a specific exit/entrance in a complex junction/intersection). - - - - - - - - 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. - - - - - - - - A measure of temperature defined in degrees Celsius. - - - - - - Measurements of atmospheric temperature. - - - - - - - - - - - - - An instant of time that recurs every day. The value space of time is the space of time of day values as defined in § 5.3 of [ISO 8601]. Specifically, it is a set of zero-duration daily time instances. - - - - - - 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. - - - - - - - - A measure of weight defined in metric tonnes. - - - - - - A descriptor for describing an area location. - - - - - - - The nature of the descriptor used to define the location 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 discrimination. - - - - - The type of TPEG location. - - - - - - - - - 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. - - - - - - - - A point on the road network which is framed between two other points on the same road. - - - - - - - The type of TPEG location. - - - - - A single non junction point on the road network which is framed between two other specified points on the road network. - - - - - The location at the down stream end of the section of road which frames the TPEGFramedPoint. - - - - - The location at the up stream end of the section of road which frames the TPEGFramedPoint. - - - - - - - - - - A geometric area defined by a centre point and a radius. - - - - - - - The radius of the geometric area identified. - - - - - Centre point of a circular geometric area. - - - - - Name of area. - - - - - - - - - - Height information which provides additional discrimination 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 location under consideration (derived from the TPEG Loc table 03). - - - - - - - - - - A point on the road network which is a road junction point. - - - - - - - - A name which identifies a junction point on the road network - - - - - A descriptor for describing a junction by identifying the intersecting roads at a road junction. - - - - - A descriptive name which helps to identify the junction point. - - - - - - - - - - A descriptor for describing a point at a junction on a road network. - - - - - - - The nature of the descriptor used to define the location under consideration (derived from the TPEG Loc table 03). - - - - - - - - - - A linear section along a single road defined between two points on the same road by a TPEG-Loc structure. - - - - - The direction of traffic flow. - - - - - The type of TPEG location. - - - - - The location at the down stream end of the linear section of road. - - - - - The location at the up stream end of the linear section of road. - - - - - - - - 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 an area. - - - - - Name of a county (administrative sub-division). - - - - - Name of a lake. - - - - - Name of a 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 administrative area. - - - - - Reference name by which an administrative area is known. - - - - - Name of an airport. - - - - - Name of an area. - - - - - 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 county (administrative sub-division). - - - - - 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 nation (e.g. Wales) which is a sub-division of a ISO recognised country. - - - - - 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 a general point of interest. - - - - - Name of a railway station. - - - - - Name of a geographic region. - - - - - 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. - - - - - - - Name of area. - - - - - - - - - - A point on the road network which is not a road junction point. - - - - - - - - A descriptive name which helps to identify the non junction point. At least one descriptor must identify the road on which the point is located, i.e. must be of type 'linkName' or 'localLinkName'. - - - - - - - - - - General descriptor for describing a point. - - - - - - - The nature of the descriptor used to define the location under consideration (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. - - - - - - - - A point on the road network which is not bounded by any other points on the road network. - - - - - - - The type of TPEG location. - - - - - A single point defined by a coordinate set and TPEG decriptors. - - - - - - - - - - Averaged measurements of traffic concentration. - - - - - - - An averaged measurement of the concentration of vehicles at the specified measurement site. - - - - - An averaged measurement of the percentage of time that a section of road at the specified measurement site is occuppied by vehicles. - - - - - - - - - - Types of constriction 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. - - - - - 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. - - - - - - - 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 site. - - - - - An averaged measurement of flow rate defined in terms of the number of passenger car units passing the specified measurement site. - - - - - An averaged measurement of the percentage of long vehicles contained in the traffic flow at the specified measurement site. - - - - - An averaged measurement of flow rate defined in terms of the number of vehicles passing the specified measurement site. - - - - - - - - - - A collection of terms for describing the characteristics of traffic flow. - - - - - Traffic flow is of an irregular nature, subject to sudden changes in rates. - - - - - Traffic flow is smooth. - - - - - Traffic flow is of a stop and go nature with queues forming and ending continuously on the specified section of road. - - - - - Traffic is blocked at the specified location and in the specified direction due to an unplanned event. - - - - - - - Averaged measurements of traffic headway, i.e. the distance or time interval 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 site. - - - - - 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 site. - - - - - - - - - - Averaged measurements of traffic speed. - - - - - - - An averaged measurement of the speed of vehicles at the specified measurement site. - - - - - - - - - - - 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 characterization 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. - - - - - - - Types of traffic, mostly classified by its destination type. - - - - - Traffic destined for local access only. - - - - - Traffic destined for the airport. - - - - - Traffic destined for airport arrivals. - - - - - Traffic destined for airport departures. - - - - - Traffic destined for the ferry service. - - - - - Traffic destined for the rail service. - - - - - Traffic heading towards holiday destinations. - - - - - Traffic heading towards local destinations. - - - - - Traffic heading towards destinations which are a long distance away. - - - - - Traffic heading towards local regional destinations. - - - - - Local residents only traffic. - - - - - Traffic which is not for local access, i.e. traffic not destined for local town, city or built up area but for transit though the area. - - - - - Traffic heading towards local visitor attraction. - - - - - - - Measured or derived values relating to traffic or individual vehicle movements on a specific section or at a specific point on the road network. - - - - - - - Used to define the vehicle characteristics to which the TrafficValue is applicable primarily in Elaborated Data Publications, but may also be used in Measured Data Publications to override vehicle characteristics defined for the measurement site. - - - - - - - - - - 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 which shall comprise at most one instance of each of the following: OperatorAction, TrafficElement, ElaboratedData and CCTVImages. - - - - - 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 flotsam. - - - - - The departure of the specified service is on schedule. - - - - - The ferry service has been replaced by an ice road. - - - - - A shuttle service is operating at no charge between specified locations until the specified time. - - - - - The information service relating to the specified transport system is not currently available. - - - - - The specified service is subject to irregular delays. - - - - - The load capacity for the specified service has been changed. - - - - - 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 until the specified time. - - - - - 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. - - - - - Vehicle type. - - - - - - - - - - The types of updates of situations that may be requested by a client. - - - - - The client has currently requested that all situation elements are sent when one or more component elements are updated. - - - - - The client has currently requested that only the individual elements of a situation that have changed are sent when updated. - - - - - The client has requested that all situations and their elements which are valid at the time of request be sent together, i.e. a snapshot in time of all valid situations. - - - - - - - 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. - - - - - - - A Uniform Resource Locator (URL) address comprising a compact string of characters for a resource available on the Internet. - - - - - - Details of a Uniform Resource Locator (URL) address pointing to a resource available on the Internet from where further relevant information may be obtained. - - - - - A Uniform Resource Locator (URL) address pointing to a resource available on the Internet from where further relevant information may be obtained. - - - - - Description of the relevant information available on the Internet from the URL link. - - - - - Details of the type of relevant information available on the Internet from the URL link. - - - - - - - - Types of URL links. - - - - - URL link to a pdf document. - - - - - URL link to an html page. - - - - - URL link to an image. - - - - - URL link to an RSS feed. - - - - - URL link to a video stream. - - - - - URL link to a voice stream. - - - - - Other than as defined in this enumeration. - - - - - - - Specification of validity, either explicitly or by a validity time period specification which may be discontinuous. - - - - - Specification of validity, either explicitly overriding the validity time specification or confirming it. - - - - - The activity or action described by the SituationRecord is still in progress, overrunning its planned duration as indicated in a previous version of this record. - - - - - A specification of periods of validity defined by overall bounding start and end times and the possible intersection of valid periods with exception periods (exception periods overriding valid periods). - - - - - - - - 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. - - - - - - - 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. - - - - - - - - - - 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 which is updated by the ISO 3166 Maintenance Agency. - - - - - A vehicle identification number (VIN) comprising 17 characters that is based on either ISO 3779 or ISO 3780 and uniquely identifies the individual vehicle. This is normally securely attached to the vehicle chassis. - - - - - Indicates the stated manufacturer of the vehicle i.e. Ford. - - - - - Indicates the model (or range name) of the vehicle i.e. Ford Mondeo. - - - - - An identifier or code displayed on a vehicle registration plate attached to the vehicle used for official identification purposes. The registration identifier is numeric or alphanumeric and is unique within the issuing authority's region. - - - - - Vehicle status. - - - - - - The spacing between axles on the vehicles. - - - - - The weight details relating to a specific axle on the vehicle. - - - - - Details of hazardous goods carried by the vehicle. - - - - - - - - The characteristics 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. - - - - - Vehicle type. - - - - - 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 site. - - - - - 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 distance 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 site. - - - - - The measured distance between the front (respectively back) of this vehicle and the front (respectively back) of the preceding vehicle at the specified measurement site. - - - - - - - - An obstruction on the road caused by one or more vehicles. - - - - - - - Characterization of an obstruction on the road caused by one or more vehicles. - - - - - The obstructing vehicle. - - - - - - - - - - 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 experiencing difficulties (e.g. manoeuvring or propulsion difficulties) which may cause traffic disruption. - - - - - A vehicle is travelling the wrong way along a divided highway (i.e. on the wrong side). - - - - - 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 over-height 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. - - - - - - - Measurement of individual vehicle speed. - - - - - The measured speed of the individual vehicle at the specified measurement site. - - - - - - - - Vehicles per hour. - - - - - - 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. - - - - - Bicycle. - - - - - Bus. - - - - - Car. - - - - - Caravan. - - - - - Car or light vehicle. - - - - - Car towing a caravan. - - - - - Car towing a trailer. - - - - - Four wheel drive vehicle. - - - - - High sided vehicle. - - - - - Lorry of any type. - - - - - Moped (a two wheeled motor vehicle characterized by a small engine typically less than 50cc and by normally having pedals). - - - - - Motorcycle. - - - - - Three wheeled vehicle comprising a motorcycle with an attached side car. - - - - - Motor scooter (a two wheeled motor vehicle characterized by a step-through frame and small diameter wheels). - - - - - Vehicle with large tank for carrying bulk liquids. - - - - - Three wheeled vehicle of unspecified type. - - - - - Trailer. - - - - - Tram. - - - - - 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 usage of a vehicle. - - - - - Vehicle used for agricultural purposes. - - - - - Vehicle which is limited to non-private usage or public transport usage. - - - - - 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. road operator or automobile association patrol vehicle. - - - - - 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. - - - - - - - Details of atmospheric visibility. - - - - - The minimum 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. - - - - - Not currently in service (e.g. intentionally disconnected or switched off during roadworks). - - - - - 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. - - - - - - - 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 that is related to the weather 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). - - - - - 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 (with little or no traffic yet) 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. - - - - - The road surface is slippery due to bad weather conditions. - - - - - 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. - - - - - Water is resting on the roadway which provides an increased hazard to vehicles. - - - - - 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. - - - - - 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). - - - - - - - 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. - - - - - - - - - - - - - Winter driving management action that is instigated by the network/road operator. - - - - - - - Type of winter equipment management action instigated by operator. - - - - - - - - - - Instructions relating to the use of winter equipment. - - - - - Do not use stud tyres. - - - - - Use snow chains. - - - - - Use snow chains or snow tyres. - - - - - Use snow tyres. - - - - - The carrying of winter equipment (snow chains and/or snow tyres) is required. - - - - - Other than as defined in this enumeration. - - - - - + + + + + A traffic condition which is not normal. + + + + + + + A characterization 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. + + + + + Assessment of the traffic flow conditions relative to normally expected conditions at this date/time. + + + + + A characterization of the traffic flow. + + + + + A characterization 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 stationary, or very near stationary, at the specified location (i.e. average speed is less than 10% of its free-flow level). + + + + + Traffic is queuing at the specified location, although there is still some traffic movement (i.e. average speed is between 10% and 25% of its free-flow level). + + + + + Traffic is slow moving at the specified location, but not yet forming queues (i.e. average speed is between 25% and 75% of its free-flow level). + + + + + Traffic is heavy at the specified location (i.e. average speed is between 75% and 90% of its free-flow level). + + + + + There are abnormal traffic conditions of an unspecified nature at the specified location. + + + + + Other than as defined in this enumeration. + + + + + + + Accidents are events where one or more vehicles are involved in collisions or in leaving the roadway. These include collisions between vehicles or with other road users or obstacles. + + + + + + + A descriptor indicating the most significant factor causing an accident. + + + + + A characterization of the nature of the accident. + + + + + The total number of people that are involved. + + + + + The total number of vehicles that are involved. + + + + + The vehicle involved in the 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 impaired visibility. + + + + + Not keeping a safe distance from the vehicle in front. + + + + + 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. + + + + + 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 mass transit vehicle. + + + + + Includes all accidents involving at least one moped. + + + + + Includes all accidents involving at least one motorcycle. + + + + + Accident involving radioactive material. + + + + + 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 action external to the traffic stream or roadway which could disrupt traffic. + + + + + + + Mobility of the activity. + + + + + + + + + + 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. EN ISO 14819-3 for the allocation of a location table number. + + + + + Version number associated with an ALERT-C table reference. + + + + + Area location defined by a specific Alert-C location. + + + + + + + + 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 (i.e. valid only for ring roads) the sense in which navigation should be made from the primary location to the secondary location, to avoid ambiguity. TRUE indicates positive RDS direction, i.e. direction of coding of 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. EN ISO 14819-3 for the allocation of a location table number. + + + + + Version number associated with 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. + + + + + + + + Linear location defined by a specific Alert-C location. + + + + + + + + + + Identification of a specific point, linear or area location in an ALERT-C location table. + + + + + Name of ALERT-C location. + + + + + Unique code within the ALERT-C location table which identifies the specific point, linear or area location. + + + + + + + + A positive integer number (between 1 and 63,487) which uniquely identifies a pre-defined Alert C location defined within an Alert-C table. + + + + + + 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. EN ISO 14819-3 for the allocation of a location table number. + + + + + Version number associated with an ALERT-C table reference. + + + + + + + + An integer number representing an angle in whole degrees between 0 and 359. + + + + + + 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 discrimination (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. + + + + + + + Authority initiated operation or activity that could disrupt traffic. + + + + + + + Type of authority initiated operation or activity that could disrupt traffic. + + + + + + + + + + Types of authority operations. + + + + + An operation involving authorised investigation work connected to an earlier reported accident. + + + + + An operation where a bomb squad is in action to deal with suspected or actual explosive or incendiary devices which 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 permanent or temporary operation established by customs and excise authorities on or adjacent to the carriageway. + + + + + An operation involving the juridical reconstruction of events for the purposes of judicial or legal proceedings. + + + + + 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 use by the road operator, such as for survey or inspection purposes, but not for traffic management purposes. + + + + + A permanent or temporary operation established by authorities on or adjacent to the carriageway for the purpose of gathering statistics or other traffic related information. + + + + + An operation to transport one or more VIPs. + + + + + An authority activity of undefined type. + + + + + A permanent or temporary operation established on or adjacent to the carriageway for inspection of vehicles by authorities (e.g. vehicle safety checks and tachograph checks). + + + + + A permanent or temporary operation established on or adjacent to the carriageway for weighing of vehicles by authorities. + + + + + A permanent or temporary facility established by authorities on the carriageway for weighing vehicles while in motion. + + + + + 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 the interval between the axles of the individual vehicle from front to back (e.g. 1, 2, 3...). This cannot exceed (numberOfAxles -1) if the numberOfAxles is also given as part of the VehicleCharacteristics. + + + + + + + + Vehicle axles per hour. + + + + + + The weight details of a specific axle on the vehicle. + + + + + Indicates the position of the axle on the vehicle numbered from front to back (i.e. 1, 2, 3...). This cannot exceed the numberOfAxles if provided as part of VehicleCharacteristics. + + + + + The weight of the specific axle, indicated by the axleSequenceIdentifier, on the vehicle numbered from front to back of the vehicle. + + + + + The maximum permitted weight of this specific axle on the vehicle. + + + + + + + + Generic data value(s) of either measured or elaborated data. Where values of different type are given in a single instance the metadata contained in the BasicDataValue must be applicable to all, otherwise separate instances must be given. + + + + + The extent to which the 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. 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. + + + + + The location (e.g. the stretch of road or area) to which the data value is pertinent/relevant. This may be different from the location of the measurement equipment (i.e. the measurement site location). + + + + + + + + Boolean has the value space required to support the mathematical concept of binary-valued logic: {true, false}. + + + + + + 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 (duration) 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, i.e. the section of road passing over another. + + + + + On the left hand feeder road. + + + + + On the left hand parallel 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, i.e. the section of road passing under another. + + + + + + + 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. + + + + + An earlier accident. + + + + + An earlier event. + + + + + An earlier incident. + + + + + Failure of roadside equipment. + + + + + Excessive heat. + + + + + Frost. + + + + + Holiday traffic. + + + + + Failure of road infrastructure. + + + + + Large numbers of visitors. + + + + + Obstruction (of unspecified type) on the roadway. + + + + + An alert relating to dangerous levels of pollution. + + + + + 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. + + + + + Radioactive leak alert. + + + + + A roadside event (of unspecified nature) whether planned or not. + + + + + Drivers being distracted and turning to look at an accident or other roadside event. + + + + + A security incident. + + + + + Shear weight of traffic. + + + + + Technical problems. + + + + + A terrorist incident. + + + + + An alert relating to the release of toxic gases and/or particulates. + + + + + A vandalism incident. + + + + + Other than as defined in this enumeration. + + + + + + + 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 un-coded observations/information. + + + + + A free text comment that can be used by the operator to convey un-coded 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 "greater than or equal to". + + + + + Logical comparison operator of "less than". + + + + + Logical comparison operator of "less than or equal to". + + + + + + + Types of compliance. + + + + + Advisory compliance . + + + + + Mandatory compliance. + + + + + + + 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. + + + + + + + Concentration defined in grams per cubic centimetre. + + + + + + A measure of concentration defined in µg/m3 (microgrammes/cubic metre). + + + + + + A measure of traffic density defined in number of vehicles per kilometre of road. + + + + + + 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). + + + + + Restricted for use only by authorities, traffic operators, publishers (service providers) and variable message signs. + + + + + + + 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. + + + + + Road widening work at the specified location + + + + + + + List of countries. + + + + + Austria + + + + + Belgium + + + + + Bulgaria + + + + + Switzerland + + + + + Serbia and Montenegro + + + + + Cyprus + + + + + Czech Republic + + + + + Germany + + + + + Denmark + + + + + Estonia + + + + + Spain + + + + + Finland + + + + + Faroe Islands + + + + + France + + + + + Great Britain + + + + + Guernsey + + + + + Gibraltar + + + + + 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. + + + + + + + A volumetric measure defined in cubic metres. + + + + + + + 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. + + + + + + + A combination of integer-valued year, month, day, hour, minute properties, a decimal-valued second property and a timezone property from which it is possible to determine the local time, the equivalent UTC time and the timezone offset from UTC. + + + + + + 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. + + + + + + + Specification of periods defined by the intersection of days, weeks and months. + + + + + Applicable day of the week. "All days of the week" is expressed by non-inclusion of this attribute. + + + + + Applicable week of the month (1 to 5). "All weeks of the month" is expressed by non-inclusion of this attribute. + + + + + Applicable month of the year. "All months of the year" is expressed by non-inclusion of this attribute. + + + + + + + + Classifications of a delay banded by length (i.e. the additional travel time). + + + + + Negligible delay. + + + + + Delay up to ten minutes. + + + + + Delay between ten minutes and thirty minutes. + + + + + Delay between thirty minutes and one hour. + + + + + Delay between one hour and three hours. + + + + + Delay between three hours and six hours. + + + + + Delay longer than six hours. + + + + + + + The details of the delays being caused by the situation element defined in the situation record. It is recommended to only use one of the optional attributes to avoid confusion. + + + + + The time band within which the additional travel time due to adverse travel conditions of any kind falls, when compared to "normal conditions". + + + + + Coarse 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. + + + + + Anticlockwise direction of travel on a ring road. + + + + + Clockwise direction of travel on a ring road. + + + + + North bound direction of travel. + + + + + North east bound direction of travel. + + + + + East bound direction of travel. + + + + + South east bound direction of travel. + + + + + South bound direction of travel. + + + + + South west bound direction of travel. + + + + + West bound direction of travel. + + + + + North west bound direction of travel. + + + + + Heading towards town centre direction of travel. + + + + + Heading out of or away from the town centre direction of travel. + + + + + + + Deliberate human action of either a public disorder nature or of a situation alert type which could disrupt traffic. + + + + + + + Includes all situations of a public disorder type or of an alert type, with potential to disrupt traffic. + + + + + + + + + + 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 an attack on a vehicle or its occupants has taken place. + + + + + A manned blockade or barrier across a road stopping vehicles passing. + + + + + An alert to a situation where suspected or actual explosive or incendiary devices may cause disruption to traffic. + + + + + 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 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. + + + + + A situation of public disorder, with potential to disrupt traffic. + + + + + An alert to a radioactive leak which may endanger the public and hence may cause traffic disruption. + + + + + A situation of public disorder involving violent behaviour and/or destruction of property with the potential to disrupt traffic. + + + + + A situation resulting from any act of sabotage. + + + + + An official alert 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 stolen. + + + + + An alert to a toxic release of gases and/or particulates into the environment which may endanger the public and hence may cause traffic disruption. + + + + + An alert to a perceived or actual threat of an unspecified nature, which could disrupt traffic. + + + + + 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. + + + + + + + An 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 snow slides. + + + + + 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. + + + + + Falling ice off trees, power lines or structures which may cause traffic disruption. + + + + + Falling light ice or snow off trees, power lines or structures which may cause traffic disruption. + + + + + 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 forest fire adjacent to the roadway. + + + + + 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 is obstructed or partially obstructed by overflows from one or more sewers. + + + + + 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. + + + + + Smoke or fumes which may hinder driving conditions or distract drivers. + + + + + 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. + + + + + + + Equipment or system which is faulty, malfunctioning or not in a fully operational state that may be of interest or concern to road operators and road users. + + + + + + + Failure, malfunction or non operational condition of equipment or system. + + + + + The type of equipment or system which is faulty, malfunctioning or not in a fully operational state. + + + + + + + + + + Types of fault, malfunctioning or non operational conditions of equipment or systems. + + + + + Not working or functioning. + + + + + Out of service (usually for operational reasons). + + + + + Working incorrectly. + + + + + Working intermittently. + + + + + + + Types of equipment and systems used to support the operation of the road network. + + + + + Automated toll system. + + + + + Emergency roadside telephones. + + + + + Gallery lights. + + + + + Signs used to control lane usage (e.g. in tidal flow systems or hard shoulder running). + + + + + Level crossing (barriers and signals). + + + + + Matrix signs. These normally comprise a symbol display area surrounded by four lights (usually amber) which flash when a symbol is displayed. + + + + + Ramp control equipment. + + + + + Roadside communications system which is used by one or more roadside equipments or systems. + + + + + Roadside power system which is used by one or more roadside equipments or systems. + + + + + Signs used to control traffic speed. + + + + + Street or road lighting. + + + + + Temporary traffic lights. + + + + + Toll gates. + + + + + Sets of traffic lights. + + + + + Traffic signals. + + + + + Tunnel lights. + + + + + Tunnel ventilation system. + + + + + Variable message signs. + + + + + Other than as defined in this enumeration. + + + + + + + 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. + + + + + For "Client Pull" exchange mode (operating mode 3 - snapshot) it defines the date/time at which the snapshot was produced. + + + + + For "Client Pull" exchange mode (operating mode 3 - snapshot) it defines the date/time after which the snapshot is no longer considered valid. + + + + + Indicator that this exchange is due to "keep alive" functionality. + + + + + The type 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. + + + + + + + + + + + + + + + + + + A location defined by reference to an external/other referencing system. + + + + + A code in the external referencing system which defines the location. + + + + + Identification of the external/other location referencing system. + + + + + + + + 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. + + + + + + + + A floating point number whose value space consists of the values m × 2^e, where m is an integer whose absolute value is less than 2^24, and e is an integer between -149 and 104, inclusive. + + + + + + Type of fuel used by a vehicle. + + + + + Battery. + + + + + Biodiesel. + + + + + Diesel. + + + + + Diesel and battery hybrid. + + + + + Ethanol. + + + + + Hydrogen. + + + + + Liquid gas of any type including LPG. + + + + + Liquid petroleum gas. + + + + + Methane gas. + + + + + Petrol. + + + + + Petrol and battery hybrid. + + + + + + + General instruction that is issued by the network/road operator which is applicable to drivers and sometimes passengers. + + + + + + + General instruction that is issued by the network/road operator which is applicable to drivers and sometimes passengers. + + + + + + + + + + General instructions that may be issued to road users (specifically drivers and sometimes passengers) by an operator or operational system in support of network management activities. + + + + + Allow emergency vehicles to pass. + + + + + Approach with care. + + + + + Drivers are to avoid the area. + + + + + Close all windows and turn off heater and vents. + + + + + Cross junction with care. + + + + + Do not allow unnecessary gaps. + + + + + Do not leave your vehicle. + + + + + Do not throw out any burning objects. + + + + + Do not use navigation systems to determine routing. + + + + + Drive carefully. + + + + + Drive with extreme caution. + + + + + Flash your lights to warn oncoming traffic of hazard ahead. + + + + + Follow the vehicle in front, smoothly. + + + + + Increase normal following distance. + + + + + In emergency, wait for patrol service (either road operator or police patrol service). + + + + + Keep your distance. + + + + + Leave your vehicle and proceed to next safe place. + + + + + No naked flames. + + + + + No overtaking on the specified section of road. + + + + + No smoking. + + + + + No stopping. + + + + + No U-turns. + + + + + Observe signals. + + + + + Observe signs. + + + + + Only travel if absolutely necessary. + + + + + Overtake with care. + + + + + 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 bus service. + + + + + Use fog lights. + + + + + Use hazard warning lights. + + + + + Use headlights. + + + + + Use rail service. + + + + + Use tram service. + + + + + Use underground service. + + + + + Wait for escort vehicle. + + + + + Other than as defined in this enumeration. + + + + + + + Network management action that is instigated either manually or automatically by the network/road operator. Compliance with any resulting control may be advisory or mandatory. + + + + + + + The type of traffic management action instigated by the network/road operator. + + + + + Type of person that is manually directing traffic (applicable if generalNetworkManagementType is set to "trafficBeingManuallyDirected"). + + + + + + + + + + Types of network management actions. + + + + + The bridge at the specified location has swung or lifted and is therefore temporarily closed to traffic. + + + + + A convoy service is in operation. + + + + + Signs are being put out before or around an obstacle to protect drivers. + + + + + Ramp metering is now active at the specified location. + + + + + Traffic is being controlled by temporary traffic lights (red-yellow-green or red-green). + + + + + Toll gates are open with no fee collection at the specified location. + + + + + Traffic is being manually directed. + + + + + Traffic in the specified direction is temporarily held up due to an unplanned event (e.g. for clearance of wreckage following an accident). + + + + + Other than as defined in this enumeration. + + + + + + + Any stationary or moving obstacle of a physical nature, other than of an animal, vehicle, environmental, or damaged equipment nature. + + + + + + + Characterization of the type of general obstruction. + + + + + + + + + + + A publication used to make level B extensions at the publication level. + + + + + + + The name of the generic publication. + + + + + + + + + + A generic SituationRecord for use when adding level B extensions at the SituationRecord level. + + + + + + + The name of the GenericSituationRecord. + + + + + + + + + + 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. + + + + + + + + + + A group of one or more physically separate locations which have no specific order. + + + + + + + Location contained in a non ordered group of locations. + + + + + + + + + + Group of people involved in the event having common characteristics and/or status. + + + + + The number of people of this group that are involved. + + + + + The injury status of the people involved. + + + + + The involvement role of the people. + + + + + The category of persons involved. + + + + + + + + Group of the vehicles involved having common characteristics and/or status. + + + + + The number of vehicles of this group that are involved. + + + + + Vehicle status. + + + + + + + + + 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 of the geographic area 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 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. + + + + + + + + Details of atmospheric humidity. + + + + + The amount of water vapour in the air, as a percentage of the amount of water vapour in saturated air at the same temperature and at atmospheric pressure. The measurement is taken between 1.5 and 2 m above the ground and behind a meteo screen. + + + + + + + + Measurements of atmospheric humidity. + + + + + + + + + + + + + An assessment of the impact that an event or operator action defined by the situation record has on the driving conditions. + + + + + The ratio of current capacity to the normal (free flow) 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 usable lanes on the carriageway which are now restricted either fully or partially (this may include the hard shoulder if it is normally available for operational use, e.g. in hard shoulder running schemes). + + + + + The number of usable lanes in the specified direction which remain fully operational (this may include the hard shoulder if it is being used as an operational lane). + + + + + The normal number of usable lanes in the specified direction that the carriageway has before reduction due to roadworks or traffic events. + + + + + The total width of the combined operational lanes in the specified direction. + + + + + The type of constriction to which traffic is subjected as a result of an event or operator action. + + + + + + + + + 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. + + + + + + + An obstruction on the road resulting from the failure or damage of infrastructure on, under, above or close to the road. + + + + + + + Characterization of an obstruction on the road resulting from the failure or damage of infrastructure on, under, above or close to the road. + + + + + + + + + + Types of infrastructure 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 surface has sunken or collapsed in places due to sewer failure. + + + + + Damage to a bridge that may cause traffic disruption. + + + + + Damage to a crash barrier that may cause traffic disruption. + + + + + Damage to an elevated section of the carriageway over another carriageway that may cause traffic disruption. + + + + + Damage to a gallery that may cause traffic disruption. + + + + + Damage to a gantry above the roadway that may cause traffic disruption. + + + + + Damage to the road surface that may cause traffic disruption. + + + + + Damage to a tunnel that may cause traffic disruption. + + + + + Damage to a viaduct that may cause traffic disruption. + + + + + 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. + + + + + Weak bridge capable of carrying a reduced load, typically with a reduced weight limit restriction imposed. + + + + + Other than as defined in this enumeration. + + + + + + + Types of injury status of people. + + + + + Dead. + + + + + Injured requiring medical treatment. + + + + + Seriously injured requiring urgent hospital treatment. + + + + + Slightly injured requiring medical treatment. + + + + + Uninjured. + + + + + Injury status unknown. + + + + + + + A measure of the quantity of application of a substance to an area defined in kilogrammes per square metre. + + + + + + A measure of precipitation intensity defined in millimetres per hour. + + + + + + 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. + + + + + + + A group of one or more physically separate locations arranged as an ordered set that defines an itinerary or route. The index indicates the order. + + + + + + + Location contained in an itinerary (i.e. an ordered set of locations defining a route or itinerary). + + + + + + + + + + + + Destination of a route or final location in an itinerary. + + + + + + + + + + A measure of speed defined in kilometres per hour. + + + + + + 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 carriageways 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. + + + + + + + A language datatype, identifies a specified language. + + + + + + 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 (true) or not (false). If finished (i.e. end is true) then the overallEndTime in the OverallPeriod class associated with the SituationRecord must be populated. + + + + + + + + A linear section along a single road with optional directionality defined between two points on the same 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. + + + + + No load. + + + + + 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. + + + + + Any goods of a commercial nature. + + + + + Materials classed as being of a hazardous nature. + + + + + Liquid of an unspecified 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. + + + + + Materials classed as being dangerous when exposed to water (e.g. materials which may react exothermically with water). + + + + + 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 or petroleum. + + + + + 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 which may be used by clients for visual display on user interfaces. + + + + + + + + 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. + + + + + On the carriageway or lane which is inbound towards the centre of the town or city. + + + + + In gallery. + + + + + 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 elevated section of road. + + + + + On flyover, i.e. on section of road over another road. + + + + + 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. + + + + + On underground section of road. + + + + + On underpass, i.e. section of road which passes under another road. + + + + + On the carriageway or lane which is outbound from the centre of the town or city. + + + + + Over the crest of a hill. + + + + + On the main carriageway within a junction between exit slip road and entry slip road. + + + + + + + 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. + + + + + + + Details of the maintenance vehicles involved in the roadworks activity. + + + + + 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. + + + + + + + + Roadworks involving the maintenance or installation of infrastructure. + + + + + + + The type of road maintenance or installation work at the specified location. + + + + + + + + + + A cause of this situation record which is managed by the publication creator, i.e. one which is represented by another situation record produced by the same publication creator. + + + + + + + A reference to another situation record produced by the same publication creator which defines a cause of the event defined here. + + + + + + + + + + Information relating to the management of the situation record. + + + + + + + + + + Types of matrix sign faults. + + + + + Comunications failure affecting matrix sign. + + + + + Incorrect aspect (face) is being displayed. + + + + + Not currently in service (e.g. intentionally disconnected or switched off during roadworks). + + + + + 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 individual vehicle measurements. + + + + + 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 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. + + + + + Measured or derived visibility information. + + + + + Measured or derived wind information. + + + + + + + Contains optional characteristics for the specific measured value (indexed to correspond with the defined characteristics of the measurement at the referenced measurement site) which override the static characteristics defined in the MeasurementSiteTable. + + + + + 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. + + + + + The version of the measurement site record, managed by systems external to DATEX II. + + + + + The date/time that this version of the measurement site record was defined. This is managed by systems external to DATEX II. + + + + + 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. + + + + + Composition to the indexed measurement specific characteristics associated with the measurement site. The index uniquely associates the measurement characteristics with the corresponding indexed measurement values for the measurement site. + + + + + + + + + + + + + + + + + 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 identification 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 value 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 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. 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. + + + + + + + + + A measure of distance defined in metres in a floating point format. + + + + + + A measure of distance defined in metres in a non negative integer format. + + + + + + An indication of whether the associated instance of a SituationRecord is mobile (e.g. a march or parade moving along a road) or stationary. + + + + + An indication of whether the associated instance of a SituationRecord is mobile (e.g. a march or parade moving along a road) or stationary. + + + + + + + + Types of mobility relating to a situation element defined by a SituationReord. + + + + + The described element of a situation is moving. + + + + + The described element of a situation is stationary. + + + + + The mobility of the described element of a situation 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). + + + + + + + + + + + + + + Network management action which is applicable to the road network and its users. + + + + + + + Defines whether the network management instruction or the control resulting from a network management action is advisory or mandatory. + + + + + The ultimate traffic direction to which the network management is applicable. + + + + + The type of traffic to which the network management is applicable. + + + + + Places, in generic terms, at which the network management applies. + + + + + Defines whether the network management is initiated by an automatic system. + + + + + The characteristics of those vehicles for which the network management is applicable. + + + + + + + + + + A cause of this situation record which is not managed by the publication creator, i.e. one which is not represented by another situation record produced by the same publication creator. + + + + + + + Description of a cause which is not managed by the publication creator (e.g. an off network cause). + + + + + Indicates an external influence that may be the causation of components of a situation. + + + + + + + + + + An integer number whose value space is the set {0, 1, 2, ..., 2147483645, 2147483646, 2147483647}. + + + + + + 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 diesel on the road. + + + + + 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 petrol on road. + + + + + The road surface is damaged, severely rutted or potholed (i.e. it is in a poor state of repair). + + + + + The road surface is slippery due to an unspecified cause. + + + + + Other than as defined in this enumeration. + + + + + + + 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. + + + + + The mobility of the obstruction. + + + + + + + + + + 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. + + + + + Scattered fragments of wreckage or other material on the road. + + + + + 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. + + + + + Unspecified hazard(s) on the road 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. + + + + + Industrial accident near the roadway 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 hazard 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. + + + + + "Subscription Management Mechanism" - a specialized operating mode to handle subscriptions. + + + + + "Publisher Push on Occurrence" operating mode. + + + + + "Publisher Push Periodic" operating mode. + + + + + "Client Pull" operating mode. + + + + + + + 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. + + + + + + + + + + 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. + + + + + A request, either internal or external, has been received to implement an action. It has neither been approved nor has any activity yet been undertaken to implement the action. + + + + + The action has been approved by the recipient of the request but activity to implement the action has not yet commenced. + + + + + The action is in the process of being implemented. + + + + + The action is fully implemented. + + + + + The action has been rejected by the recipient of the request and hence is not implemented. + + + + + A request, either internal or external, has been received to terminate the action, but activity to terminate the action has not yet commenced. + + + + + The action is in the process of being terminated either because the action has reached the end of its validity period or because new circumstances have arisen and its termination has been requested, e.g. because of a traffic jam on the alternative route. + + + + + + + A continuous or discontinuous 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 single time period, a recurring time period or a set of different recurring time periods during which validity is true. + + + + + A single time period, a recurring time period or a set of different recurring time periods during which validity is false. + + + + + + + + Levels of severity of a situation as whole assessed by the impact that the situation 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 medium level. + + + + + Perceived by supplier as being of a low level. + + + + + Perceived by supplier as being of the lowest discernible level. + + + + + Perceived by supplier as having a severity rating of none. + + + + + Perceived by supplier as being of an unknown level. + + + + + + + Passenger car units per hour. + + + + + + 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 description of the information which is to be found in the publications originating from the particular feed (URL). + + + + + 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. + + + + + + + + The default language used throughout the payload publications, specified by an ISO 639-2 3-alpha code. + + + + + + A measure of percentage. + + + + + + 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. + + + + + A recurring period of a day. + + + + + A recurring period defined in terms of days of the week, weeks of the month and months of the year. + + + + + + + + Categories of person. + + + + + Adult. + + + + + Child (age 4 to 17). + + + + + A member of the emergency services, other than the police. + + + + + A member of the fire service. + + + + + Infant (age 0 to 3). + + + + + A member of the medical service. + + + + + A member of the general public. + + + + + 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 member of the local traffic warden service. + + + + + A very important person. + + + + + + + List of types of places. + + + + + Around bends in the road. + + + + + At customs posts. + + + + + At high altitudes. + + + + + At toll plazas. + + + + + In galleries. + + + + + In low lying areas. + + + + + In roadworks areas. + + + + + In shaded areas. + + + + + In the city centre. + + + + + In the inner city areas. + + + + + In tunnels. + + + + + On bridges. + + + + + On elevated sections of the road. + + + + + On entering or leaving tunnels. + + + + + On entry into the country. + + + + + On flyover sections of the road, i.e. sections of the road which pass over another road. + + + + + On leaving the country. + + + + + On motorways. + + + + + On non motorways. + + + + + On roundabouts. + + + + + On slip roads. + + + + + On underground sections of the road. + + + + + On underpasses, i.e. sections of the road which pass under another road. + + + + + Over the crest of hills. + + + + + 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). + + + + + Polycyclic aromatic hydrocarbons. + + + + + 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. + + + + + 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. + + + + + Pollution of an unspecified nature. + + + + + 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. + + + + + + + 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. + + + + + + + Indication of whether precipitation is present or not. True indicates there is no precipitation. + + + + + + + + + + + Types of precipitation. + + + + + Light, fine rain. + + + + + Freezing 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 assigned to the 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 the set of predefined locations. + + + + + The version of the predefined location set. + + + + + + + + + + A publication containing one or more sets of predefined locations. + + + + + + + + + + + + + + Levels of confidence that the sender has in the information, ordered {certain, probable, risk of}. + + + + + The source is completely 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. + + + + + + + Organised public event which could disrupt traffic. + + + + + + + Type of public event which could disrupt traffic. + + + + + + + + + + Type of public event (Datex2 PublicEventTypeEnum and PublicEventType2Enum combined) + + + + + Unknown + + + + + Agricultural show or event which could disrupt traffic. + + + + + Air show or other aeronautical event which could disrupt traffic. + + + + + Art event that could disrupt traffic. + + + + + Athletics event that could disrupt traffic. + + + + + Beer festival 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. + + + + + Boat show which 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. + + + + + Commercial event which could disrupt traffic. + + + + + Concert event that could disrupt traffic. + + + + + Cricket match that could disrupt traffic. + + + + + Cultural event which 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 festival that could disrupt traffic. + + + + + Film or TV making event which could disrupt traffic. + + + + + Fireworks display that could disrupt traffic. + + + + + Flower event that could disrupt traffic. + + + + + Food festival that could disrupt traffic. + + + + + Football match that could disrupt traffic. + + + + + Periodic (e.g. annual), often traditional, gathering for entertainment, which could disrupt traffic. + + + + + Gardening and/or flower show or event 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 show which could disrupt traffic. + + + + + Motor sport race meeting that could disrupt traffic. + + + + + Open air concert that could disrupt traffic. + + + + + Formal display or organised procession which could disrupt traffic. + + + + + An 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. + + + + + Sound and light show 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. + + + + + Street festival that could disrupt traffic. + + + + + Tennis tournament that could disrupt traffic. + + + + + Theatrical event that could disrupt traffic. + + + + + Sporting event or series of events of unspecified type lasting more than one day which could disrupt traffic. + + + + + A periodic (e.g. annual), often traditional, gathering for trade promotion, which could disrupt traffic. + + + + + Water sports meeting that could disrupt traffic. + + + + + Wine festival that could disrupt traffic. + + + + + Winter sports meeting or event (e.g. skiing, ski jumping, skating) that could disrupt traffic. + + + + + Other than as defined in this enumeration. + + + + + + + A reference to an identifiable object instance (e.g. a GUID reference). + + + + + + Directions of traffic flow relative to sequential numbering scheme of reference points. 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. + + + + + + + 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 assessment 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 flow is normal at the specified location at this date/time. + + + + + Traffic is lighter than normally expected at the specified location at this date/time. + + + + + Traffic is very much 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. + + + + + A request for the supplier's catalogue. + + + + + A request for the client's filter as currently stored by the supplier. + + + + + A request for current data. + + + + + A request for historical data, i.e. data which was valid within an historical time window. + + + + + A request for a client's subscription as currently held by a supplier. + + + + + + + Rerouting management action that is issued by the network/road operator. + + + + + + + Type of rerouting management action instigated by operator. + + + + + A description of the rerouting itinerary. + + + + + Indication of whether the rerouting is signed. + + + + + The specified entry on to another road at which the alternative route commences. + + + + + The specified exit from the normal route/road at which the alternative route commences. + + + + + The intersecting road or the junction at which the alternative route commences. + + + + + The definition of the alternative route (rerouting) specified as an ordered set of locations (itinerary) which may be specific to one or more defined destinations. + + + + + + + + + + Management actions relating to rerouting. + + + + + Do not follow diversion signs. + + + + + Rerouted traffic is not to use the specified entry onto the identified road to commence the alternative route. + + + + + Rerouted traffic is not to use the specified exit from the identified road to commence the alternative route. + + + + + Rerouted traffic is not to use the specified intersection or junction. + + + + + Rerouted traffic is to follow the diversion signs. + + + + + Rerouted traffic is to follow local diversion. + + + + + Rerouted traffic is to follow the special diversion markers. + + + + + 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. + + + + + An acknowledgement that the supplier has received and complied with the client's request. + + + + + A notification that the supplier has denied the client's request for a catalogue. + + + + + A notification that the supplier has denied the client's request for a filter. + + + + + A notification that the supplier has denied the client's request for a data. + + + + + A notification that the supplier has denied the client's request for a subscription. + + + + + + + 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 an unspecified nature. + + + + + Controlled avalanche work. + + + + + Installation of new equipments or systems on or along-side the roadway. + + + + + Grass cutting work. + + + + + Maintenance of road, associated infrastructure or equipments. + + + + + Works which are overhead of the carriageway. + + + + + 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. + + + + + Spreading of salt and / or grit on the road surface to prevent or melt snow or ice. + + + + + Snowploughs or other similar mechanical devices in use to clear snow from the road. + + + + + Tree and vegetation cutting work adjacent to the roadway. + + + + + Other than as defined in this enumeration. + + + + + + + Details of disruption to normal road operator services + + + + + + + The type of road operator service which is disrupted. + + + + + + + + + + Types of disruption to road operator services relevant to road users. + + + + + Emergency telephone number for use by public to report incidents is out of service. + + + + + Road information service telephone number is out of service. + + + + + No traffic officer patrol service is operating. + + + + + + + Road, carriageway or lane management action that is instigated by the network/road operator. + + + + + + + Type of road, carriageway or lane management action instigated by operator. + + + + + The minimum number of persons required in a vehicle in order for it to be allowed to transit the specified road section. + + + + + The carriageway which is the subject of the management action. + + + + + The lane which is the subject of the management action. + + + + + + + + + + Management actions relating to road, carriageway or lane usage. + + + + + Dedicated car pool lane(s) are in operation for vehicles carrying at least the specified number of occupants. + + + + + Carriageway closures are in operation at the specified location. + + + + + Clear a lane for emergency vehicles. + + + + + Clear a lane for snow ploughs and gritting vehicles. + + + + + 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. + + + + + Do not use the specified lane(s) or carriageway(s). + + + + + The hard shoulder is open as an operational lane. + + + + + Road closures occur intermittently on the specified road in the specified direction for short durations. + + + + + Keep to the left. + + + + + Keep to the right. + + + + + Lane closures are in operation at the specified location for vehicles with the specified characteristics or all, if none defined, in the specified direction. + + + + + Lane deviations are in operation at the specified location. + + + + + Normal lane widths are temporarily reduced. + + + + + A new layout of lanes/carriageway has been implemented associated with roadworks. + + + + + 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. + + + + + The road has been cleared of earlier reported problems. + + + + + The road is closed to vehicles with the specified characteristics or all, if none defined, in the specified direction. + + + + + Traffic officers or police are driving slowly in front of a queue of traffic to create a gap in the traffic to allow for clearance activities to take place in safety on the road ahead. + + + + + 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. + + + + + Dedicated tidal flow lane(s) are in operation in the specified direction. + + + + + Traffic is being directed back down the opposite carriageway, possibly requiring the temporary removal of the central crash barrier. + + + + + The specified lane(s) or carriageway(s) may be used. The normal lane(s) or carriageway(s) restrictions are not currently in force. + + + + + Use the specified lane(s) or carriageway(s). + + + + + Vehicles are being stored on the roadway and/or at a rest area or service area at the specified location. + + + + + Other than as defined in this enumeration. + + + + + + + Details of road side assistance required or being given. + + + + + + + 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. + + + + + + + One of a sequence of roadside reference points along a road, normally spaced at regular intervals along each carriageway with a sequence of identification from a known starting point. + + + + + Roadside reference point identifier, unique on the specified road. + + + + + Identification of the road administration area which contains the reference point. + + + + + Name of a road. + + + + + 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 roadside reference point. + + + + + The distance of the roadside reference point from the starting point of the sequence on the road. + + + + + + + + A linear section along a single road defined between two points on the same road identified by roadside reference points. + + + + + + + + + + The point (called Primary point) which is at the downstream end of a linear road section. The point is identified by a roadside reference point. + + + + + + + + + The point (called Secondary point) which is at the upstream end of a linear road section. The point is identified by a roadside reference point. + + + + + + + + + Details of disruption to normal roadside services (e.g. specific services at a service areas). + + + + + + + The type of roadside service which is disrupted. + + + + + + + + + + Types of disruption to roadside 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. + + + + + + + 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. + + + + + + + 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 under traffic or not under traffic. 'True' indicates the road is under traffic. + + + + + 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. + + + + + + + Seconds. + + + + + + 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. + + + + + Composition to the indexed measured value associated with the measurement site. The index uniquely associates the measurement value with the corresponding indexed measurement characteristics defined for the measurement site. + + + + + + + + + + + + + + + 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. + + + + + Each situation may iterate through a series of versions during its life time. The situation version uniquely identifies the version of the situation. It is generated and used by systems external to DATEX II. + + + + + The date/time that this current version of the Situation was written into the database of the supplier which is involved in the data exchange. + + + + + + + + + + + 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 II. + + + + + 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. + + + + + The extent to which the related information may be circulated, according to the recipient type. Recipients must comply with this confidentiality statement. This overrides any confidentiality defined for the situation as a whole in the header information. + + + + + An assessment of the degree of likelihood that the reported event will occur. + + + + + + + + + A comment which may be freely distributed to the general public + + + + + A comment which should not be distributed to the general public. + + + + + + + + + + + + Details of the source from which the information was obtained. + + + + + ISO 3166-1 two character country code of the source of the information. + + + + + Identifier 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. + + + + + + + Speed management action that is instigated by the network/road operator. + + + + + + + Type of speed management action instigated by operator. + + + + + Temporary limit defining the maximum advisory or mandatory speed of vehicles. + + + + + + + + + + Management actions relating to speed. + + + + + Automatic speed control measures are in place at the specified location, whereby speed limits are set by an automatic system which is triggered by traffic sensing equipment. + + + + + Do not slow down unnecessarily. + + + + + Observe speed limit. + + + + + Police speed checks are in operation. + + + + + Reduce your speed. + + + + + Other than as defined in this enumeration. + + + + + + + Details of percentage (from an observation set) of vehicles whose speeds fall below a stated value. + + + + + The percentage of vehicles from the observation set whose speeds fall below the stated speed (speedPercentile). + + + + + The speed below which the associated percentage of vehicles in the measurement set are travelling at. + + + + + + + + A character string whose value space is the set of finite-length sequences of characters. Every character has a corresponding Universal Character Set code point (as defined in ISO/IEC 10646), which is an integer. + + + + + + + + The subjects with which the roadworks are associated. + + + + + The subject type 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. + + + + + Crash barrier. + + + + + Gallery. + + + + + Gantry over or above the roadway. + + + + + Gas mains. + + + + + Motorway or major road interchange. + + + + + Motorway or major road junction. + + + + + Level-crossing or associated equipment. + + + + + Road lighting system. + + + + + Equipment used for determining traffic measurements. + + + + + Installations along the roadway designed to reduce road noise in the surrounding environment. + + + + + Road. + + + + + Roadside drains. + + + + + Roadside embankment. + + + + + Roadside equipment. + + + + + Road signs. + + + + + Roundabout. + + + + + Toll gate. + + + + + 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. + + + + + The client's subscription as registered with a supplier is currently active. + + + + + The client's subscription as registered with a supplier is currently suspended. + + + + + + + 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. + + + + + Indicates that the location is given with a precision which is better than the stated value in metres. + + + + + The sequential number of an exit/entrance ramp from a given location in a given direction (normally used to indicate a specific exit/entrance in a complex junction/intersection). + + + + + + + + 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. + + + + + + + + A measure of temperature defined in degrees Celsius. + + + + + + Measurements of atmospheric temperature. + + + + + + + + + + + + + An instant of time that recurs every day. The value space of time is the space of time of day values as defined in § 5.3 of [ISO 8601]. Specifically, it is a set of zero-duration daily time instances. + + + + + + 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. + + + + + + + + A measure of weight defined in metric tonnes. + + + + + + A descriptor for describing an area location. + + + + + + + The nature of the descriptor used to define the location 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 discrimination. + + + + + The type of TPEG location. + + + + + + + + + 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. + + + + + + + + A point on the road network which is framed between two other points on the same road. + + + + + + + The type of TPEG location. + + + + + A single non junction point on the road network which is framed between two other specified points on the road network. + + + + + The location at the down stream end of the section of road which frames the TPEGFramedPoint. + + + + + The location at the up stream end of the section of road which frames the TPEGFramedPoint. + + + + + + + + + + A geometric area defined by a centre point and a radius. + + + + + + + The radius of the geometric area identified. + + + + + Centre point of a circular geometric area. + + + + + Name of area. + + + + + + + + + + Height information which provides additional discrimination 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 location under consideration (derived from the TPEG Loc table 03). + + + + + + + + + + A point on the road network which is a road junction point. + + + + + + + + A name which identifies a junction point on the road network + + + + + A descriptor for describing a junction by identifying the intersecting roads at a road junction. + + + + + A descriptive name which helps to identify the junction point. + + + + + + + + + + A descriptor for describing a point at a junction on a road network. + + + + + + + The nature of the descriptor used to define the location under consideration (derived from the TPEG Loc table 03). + + + + + + + + + + A linear section along a single road defined between two points on the same road by a TPEG-Loc structure. + + + + + The direction of traffic flow. + + + + + The type of TPEG location. + + + + + The location at the down stream end of the linear section of road. + + + + + The location at the up stream end of the linear section of road. + + + + + + + + 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 an area. + + + + + Name of a county (administrative sub-division). + + + + + Name of a lake. + + + + + Name of a 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 administrative area. + + + + + Reference name by which an administrative area is known. + + + + + Name of an airport. + + + + + Name of an area. + + + + + 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 county (administrative sub-division). + + + + + 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 nation (e.g. Wales) which is a sub-division of a ISO recognised country. + + + + + 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 a general point of interest. + + + + + Name of a railway station. + + + + + Name of a geographic region. + + + + + 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. + + + + + + + Name of area. + + + + + + + + + + A point on the road network which is not a road junction point. + + + + + + + + A descriptive name which helps to identify the non junction point. At least one descriptor must identify the road on which the point is located, i.e. must be of type 'linkName' or 'localLinkName'. + + + + + + + + + + General descriptor for describing a point. + + + + + + + The nature of the descriptor used to define the location under consideration (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. + + + + + + + + A point on the road network which is not bounded by any other points on the road network. + + + + + + + The type of TPEG location. + + + + + A single point defined by a coordinate set and TPEG decriptors. + + + + + + + + + + Averaged measurements of traffic concentration. + + + + + + + An averaged measurement of the concentration of vehicles at the specified measurement site. + + + + + An averaged measurement of the percentage of time that a section of road at the specified measurement site is occuppied by vehicles. + + + + + + + + + + Types of constriction 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. + + + + + 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. + + + + + + + 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 site. + + + + + An averaged measurement of flow rate defined in terms of the number of passenger car units passing the specified measurement site. + + + + + An averaged measurement of the percentage of long vehicles contained in the traffic flow at the specified measurement site. + + + + + An averaged measurement of flow rate defined in terms of the number of vehicles passing the specified measurement site. + + + + + + + + + + A collection of terms for describing the characteristics of traffic flow. + + + + + Traffic flow is of an irregular nature, subject to sudden changes in rates. + + + + + Traffic flow is smooth. + + + + + Traffic flow is of a stop and go nature with queues forming and ending continuously on the specified section of road. + + + + + Traffic is blocked at the specified location and in the specified direction due to an unplanned event. + + + + + + + Averaged measurements of traffic headway, i.e. the distance or time interval 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 site. + + + + + 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 site. + + + + + + + + + + Averaged measurements of traffic speed. + + + + + + + An averaged measurement of the speed of vehicles at the specified measurement site. + + + + + + + + + + + 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 characterization 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. + + + + + + + Types of traffic, mostly classified by its destination type. + + + + + Traffic destined for local access only. + + + + + Traffic destined for the airport. + + + + + Traffic destined for airport arrivals. + + + + + Traffic destined for airport departures. + + + + + Traffic destined for the ferry service. + + + + + Traffic destined for the rail service. + + + + + Traffic heading towards holiday destinations. + + + + + Traffic heading towards local destinations. + + + + + Traffic heading towards destinations which are a long distance away. + + + + + Traffic heading towards local regional destinations. + + + + + Local residents only traffic. + + + + + Traffic which is not for local access, i.e. traffic not destined for local town, city or built up area but for transit though the area. + + + + + Traffic heading towards local visitor attraction. + + + + + + + Measured or derived values relating to traffic or individual vehicle movements on a specific section or at a specific point on the road network. + + + + + + + Used to define the vehicle characteristics to which the TrafficValue is applicable primarily in Elaborated Data Publications, but may also be used in Measured Data Publications to override vehicle characteristics defined for the measurement site. + + + + + + + + + + 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 which shall comprise at most one instance of each of the following: OperatorAction, TrafficElement, ElaboratedData and CCTVImages. + + + + + 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 flotsam. + + + + + The departure of the specified service is on schedule. + + + + + The ferry service has been replaced by an ice road. + + + + + A shuttle service is operating at no charge between specified locations until the specified time. + + + + + The information service relating to the specified transport system is not currently available. + + + + + The specified service is subject to irregular delays. + + + + + The load capacity for the specified service has been changed. + + + + + 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 until the specified time. + + + + + 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. + + + + + Vehicle type. + + + + + + + + + + The types of updates of situations that may be requested by a client. + + + + + The client has currently requested that all situation elements are sent when one or more component elements are updated. + + + + + The client has currently requested that only the individual elements of a situation that have changed are sent when updated. + + + + + The client has requested that all situations and their elements which are valid at the time of request be sent together, i.e. a snapshot in time of all valid situations. + + + + + + + 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. + + + + + + + A Uniform Resource Locator (URL) address comprising a compact string of characters for a resource available on the Internet. + + + + + + Details of a Uniform Resource Locator (URL) address pointing to a resource available on the Internet from where further relevant information may be obtained. + + + + + A Uniform Resource Locator (URL) address pointing to a resource available on the Internet from where further relevant information may be obtained. + + + + + Description of the relevant information available on the Internet from the URL link. + + + + + Details of the type of relevant information available on the Internet from the URL link. + + + + + + + + Types of URL links. + + + + + URL link to a pdf document. + + + + + URL link to an html page. + + + + + URL link to an image. + + + + + URL link to an RSS feed. + + + + + URL link to a video stream. + + + + + URL link to a voice stream. + + + + + Other than as defined in this enumeration. + + + + + + + Specification of validity, either explicitly or by a validity time period specification which may be discontinuous. + + + + + Specification of validity, either explicitly overriding the validity time specification or confirming it. + + + + + The activity or action described by the SituationRecord is still in progress, overrunning its planned duration as indicated in a previous version of this record. + + + + + A specification of periods of validity defined by overall bounding start and end times and the possible intersection of valid periods with exception periods (exception periods overriding valid periods). + + + + + + + + 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. + + + + + + + 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. + + + + + + + + + + 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 which is updated by the ISO 3166 Maintenance Agency. + + + + + A vehicle identification number (VIN) comprising 17 characters that is based on either ISO 3779 or ISO 3780 and uniquely identifies the individual vehicle. This is normally securely attached to the vehicle chassis. + + + + + Indicates the stated manufacturer of the vehicle i.e. Ford. + + + + + Indicates the model (or range name) of the vehicle i.e. Ford Mondeo. + + + + + An identifier or code displayed on a vehicle registration plate attached to the vehicle used for official identification purposes. The registration identifier is numeric or alphanumeric and is unique within the issuing authority's region. + + + + + Vehicle status. + + + + + + The spacing between axles on the vehicles. + + + + + The weight details relating to a specific axle on the vehicle. + + + + + Details of hazardous goods carried by the vehicle. + + + + + + + + The characteristics 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. + + + + + Vehicle type. + + + + + 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 site. + + + + + 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 distance 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 site. + + + + + The measured distance between the front (respectively back) of this vehicle and the front (respectively back) of the preceding vehicle at the specified measurement site. + + + + + + + + An obstruction on the road caused by one or more vehicles. + + + + + + + Characterization of an obstruction on the road caused by one or more vehicles. + + + + + The obstructing vehicle. + + + + + + + + + + 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 experiencing difficulties (e.g. manoeuvring or propulsion difficulties) which may cause traffic disruption. + + + + + A vehicle is travelling the wrong way along a divided highway (i.e. on the wrong side). + + + + + 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 over-height 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. + + + + + + + Measurement of individual vehicle speed. + + + + + The measured speed of the individual vehicle at the specified measurement site. + + + + + + + + Vehicles per hour. + + + + + + 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. + + + + + Bicycle. + + + + + Bus. + + + + + Car. + + + + + Caravan. + + + + + Car or light vehicle. + + + + + Car towing a caravan. + + + + + Car towing a trailer. + + + + + Four wheel drive vehicle. + + + + + High sided vehicle. + + + + + Lorry of any type. + + + + + Moped (a two wheeled motor vehicle characterized by a small engine typically less than 50cc and by normally having pedals). + + + + + Motorcycle. + + + + + Three wheeled vehicle comprising a motorcycle with an attached side car. + + + + + Motor scooter (a two wheeled motor vehicle characterized by a step-through frame and small diameter wheels). + + + + + Vehicle with large tank for carrying bulk liquids. + + + + + Three wheeled vehicle of unspecified type. + + + + + Trailer. + + + + + Tram. + + + + + 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 usage of a vehicle. + + + + + Vehicle used for agricultural purposes. + + + + + Vehicle which is limited to non-private usage or public transport usage. + + + + + 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. road operator or automobile association patrol vehicle. + + + + + 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. + + + + + + + Details of atmospheric visibility. + + + + + The minimum 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. + + + + + Not currently in service (e.g. intentionally disconnected or switched off during roadworks). + + + + + 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. + + + + + + + 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 that is related to the weather 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). + + + + + 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 (with little or no traffic yet) 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. + + + + + The road surface is slippery due to bad weather conditions. + + + + + 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. + + + + + Water is resting on the roadway which provides an increased hazard to vehicles. + + + + + 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. + + + + + 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). + + + + + + + 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. + + + + + + + + + + + + + Winter driving management action that is instigated by the network/road operator. + + + + + + + Type of winter equipment management action instigated by operator. + + + + + + + + + + Instructions relating to the use of winter equipment. + + + + + Do not use stud tyres. + + + + + Use snow chains. + + + + + Use snow chains or snow tyres. + + + + + Use snow tyres. + + + + + The carrying of winter equipment (snow chains and/or snow tyres) is required. + + + + + Other than as defined in this enumeration. + + + + + diff --git a/xsd/gml/basicTypes.xsd b/xsd/gml/basicTypes.xsd index 463203ca..4ad5c991 100644 --- a/xsd/gml/basicTypes.xsd +++ b/xsd/gml/basicTypes.xsd @@ -1,267 +1,267 @@ - - - - basicTypes.xsd - See ISO/DIS 19136 8.2. -W3C XML Schema provides a set of built-in "simple" types which define methods for representing values as literals without internal markup. These are described in W3C XML Schema Part 2:2001. Because GML is an XML encoding in which instances are described using XML Schema, these simple types shall be used as far as possible and practical for the representation of data types. W3C XML Schema also provides methods for defining -- new simple types by restriction and combination of the built-in types, and -- complex types, with simple content, but which also have XML attributes. -In many places where a suitable built-in simple type is not available, simple content types derived using the XML Schema mechanisms are used for the representation of data types in GML. -A set of these simple content types that are required by several GML components are defined in the basicTypes schema, as well as some elements based on them. These are primarily based around components needed to record amounts, counts, flags and terms, together with support for exceptions or null values. - -GML is an OGC Standard. -Copyright (c) 2007,2010 Open Geospatial Consortium, Inc. All Rights Reserved. -To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . - - - - - gml:NilReasonType defines a content model that allows recording of an explanation for a void value or other exception. -gml:NilReasonType is a union of the following enumerated values: -- inapplicable there is no value -- missing the correct value is not readily available to the sender of this data. Furthermore, a correct value may not exist -- template the value will be available later -- unknown the correct value is not known to, and not computable by, the sender of this data. However, a correct value probably exists -- withheld the value is not divulged -- other:text other brief explanation, where text is a string of two or more characters with no included spaces -and -- anyURI which should refer to a resource which describes the reason for the exception -A particular community may choose to assign more detailed semantics to the standard values provided. Alternatively, the URI method enables a specific or more complete explanation for the absence of a value to be provided elsewhere and indicated by-reference in an instance document. -gml:NilReasonType is used as a member of a union in a number of simple content types where it is necessary to permit a value from the NilReasonType union as an alternative to the primary type. - - - - - - - - - - - - - - - - - - - - - - - - gml:SignType is a convenience type with values "+" (plus) and "-" (minus). - - - - - - - - - Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. - - - - - - Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. - - - - - - Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. - - - - - - Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. - - - - - - Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. - - - - - - gml:CodeType is a generalized type to be used for a term, keyword or name. -It adds a XML attribute codeSpace to a term, where the value of the codeSpace attribute (if present) shall indicate a dictionary, thesaurus, classification scheme, authority, or pattern for the term. - - - - - - - - - - gml:CodeWithAuthorityType requires that the codeSpace attribute is provided in an instance. - - - - - - - - - - gml:MeasureType supports recording an amount encoded as a value of XML Schema double, together with a units of measure indicated by an attribute uom, short for "units of measure". The value of the uom attribute identifies a reference system for the amount, usually a ratio or interval scale. - - - - - - - - - - The simple type gml:Uomidentifier defines the syntax and value space of the unit of measure identifier. - - - - - - This type specifies a character string of length at least one, and restricted such that it must not contain any of the following characters: ":" (colon), " " (space), (newline), (carriage return), (tab). This allows values corresponding to familiar abbreviations, such as "kg", "m/s", etc. -It is recommended that the symbol be an identifier for a unit of measure as specified in the "Unified Code of Units of Measure" (UCUM) (http://aurora.regenstrief.org/UCUM). This provides a set of symbols and a grammar for constructing identifiers for units of measure that are unique, and may be easily entered with a keyboard supporting the limited character set known as 7-bit ASCII. ISO 2955 formerly provided a specification with this scope, but was withdrawn in 2001. UCUM largely follows ISO 2955 with modifications to remove ambiguities and other problems. - - - - - - - - This type specifies a URI, restricted such that it must start with one of the following sequences: "#", "./", "../", or a string of characters followed by a ":". These patterns ensure that the most common URI forms are supported, including absolute and relative URIs and URIs that are simple fragment identifiers, but prohibits certain forms of relative URI that could be mistaken for unit of measure symbol . -NOTE It is possible to re-write such a relative URI to conform to the restriction (e.g. "./m/s"). -In an instance document, on elements of type gml:MeasureType the mandatory uom attribute shall carry a value corresponding to either -- a conventional unit of measure symbol, -- a link to a definition of a unit of measure that does not have a conventional symbol, or when it is desired to indicate a precise or variant definition. - - - - - - - - This type is deprecated for tuples with ordinate values that are numbers. -CoordinatesType is a text string, intended to be used to record an array of tuples or coordinates. -While it is not possible to enforce the internal structure of the string through schema validation, some optional attributes have been provided in previous versions of GML to support a description of the internal structure. These attributes are deprecated. The attributes were intended to be used as follows: -Decimal symbol used for a decimal point (default="." a stop or period) -cs symbol used to separate components within a tuple or coordinate string (default="," a comma) -ts symbol used to separate tuples or coordinate strings (default=" " a space) -Since it is based on the XML Schema string type, CoordinatesType may be used in the construction of tables of tuples or arrays of tuples, including ones that contain mixed text and numeric values. - - - - - - - - - - - - A type for a list of values of the respective simple type. - - - - - - A type for a list of values of the respective simple type. - - - - - - A type for a list of values of the respective simple type. - - - - - - A type for a list of values of the respective simple type. - - - - - - A type for a list of values of the respective simple type. - - - - - - A type for a list of values of the respective simple type. - - - - - - A type for a list of values of the respective simple type. - - - - - - A type for a list of values of the respective simple type. - - - - - - A type for a list of values of the respective simple type. - - - - - - A type for a list of values of the respective simple type. - - - - - - gml:CodeListType provides for lists of terms. The values in an instance element shall all be valid according to the rules of the dictionary, classification scheme, or authority identified by the value of its codeSpace attribute. - - - - - - - - - - gml:CodeOrNilReasonListType provides for lists of terms. The values in an instance element shall all be valid according to the rules of the dictionary, classification scheme, or authority identified by the value of its codeSpace attribute. An instance element may also include embedded values from NilReasonType. It is intended to be used in situations where a term or classification is expected, but the value may be absent for some reason. - - - - - - - - - - gml:MeasureListType provides for a list of quantities. - - - - - - - - - - gml:MeasureOrNilReasonListType provides for a list of quantities. An instance element may also include embedded values from NilReasonType. It is intended to be used in situations where a value is expected, but the value may be absent for some reason. - - - - - - - - + + + + basicTypes.xsd + See ISO/DIS 19136 8.2. +W3C XML Schema provides a set of built-in "simple" types which define methods for representing values as literals without internal markup. These are described in W3C XML Schema Part 2:2001. Because GML is an XML encoding in which instances are described using XML Schema, these simple types shall be used as far as possible and practical for the representation of data types. W3C XML Schema also provides methods for defining +- new simple types by restriction and combination of the built-in types, and +- complex types, with simple content, but which also have XML attributes. +In many places where a suitable built-in simple type is not available, simple content types derived using the XML Schema mechanisms are used for the representation of data types in GML. +A set of these simple content types that are required by several GML components are defined in the basicTypes schema, as well as some elements based on them. These are primarily based around components needed to record amounts, counts, flags and terms, together with support for exceptions or null values. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium, Inc. All Rights Reserved. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + gml:NilReasonType defines a content model that allows recording of an explanation for a void value or other exception. +gml:NilReasonType is a union of the following enumerated values: +- inapplicable there is no value +- missing the correct value is not readily available to the sender of this data. Furthermore, a correct value may not exist +- template the value will be available later +- unknown the correct value is not known to, and not computable by, the sender of this data. However, a correct value probably exists +- withheld the value is not divulged +- other:text other brief explanation, where text is a string of two or more characters with no included spaces +and +- anyURI which should refer to a resource which describes the reason for the exception +A particular community may choose to assign more detailed semantics to the standard values provided. Alternatively, the URI method enables a specific or more complete explanation for the absence of a value to be provided elsewhere and indicated by-reference in an instance document. +gml:NilReasonType is used as a member of a union in a number of simple content types where it is necessary to permit a value from the NilReasonType union as an alternative to the primary type. + + + + + + + + + + + + + + + + + + + + + + + + gml:SignType is a convenience type with values "+" (plus) and "-" (minus). + + + + + + + + + Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. + + + + + + Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. + + + + + + Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. + + + + + + Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. + + + + + + Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. + + + + + + gml:CodeType is a generalized type to be used for a term, keyword or name. +It adds a XML attribute codeSpace to a term, where the value of the codeSpace attribute (if present) shall indicate a dictionary, thesaurus, classification scheme, authority, or pattern for the term. + + + + + + + + + + gml:CodeWithAuthorityType requires that the codeSpace attribute is provided in an instance. + + + + + + + + + + gml:MeasureType supports recording an amount encoded as a value of XML Schema double, together with a units of measure indicated by an attribute uom, short for "units of measure". The value of the uom attribute identifies a reference system for the amount, usually a ratio or interval scale. + + + + + + + + + + The simple type gml:Uomidentifier defines the syntax and value space of the unit of measure identifier. + + + + + + This type specifies a character string of length at least one, and restricted such that it must not contain any of the following characters: ":" (colon), " " (space), (newline), (carriage return), (tab). This allows values corresponding to familiar abbreviations, such as "kg", "m/s", etc. +It is recommended that the symbol be an identifier for a unit of measure as specified in the "Unified Code of Units of Measure" (UCUM) (http://aurora.regenstrief.org/UCUM). This provides a set of symbols and a grammar for constructing identifiers for units of measure that are unique, and may be easily entered with a keyboard supporting the limited character set known as 7-bit ASCII. ISO 2955 formerly provided a specification with this scope, but was withdrawn in 2001. UCUM largely follows ISO 2955 with modifications to remove ambiguities and other problems. + + + + + + + + This type specifies a URI, restricted such that it must start with one of the following sequences: "#", "./", "../", or a string of characters followed by a ":". These patterns ensure that the most common URI forms are supported, including absolute and relative URIs and URIs that are simple fragment identifiers, but prohibits certain forms of relative URI that could be mistaken for unit of measure symbol . +NOTE It is possible to re-write such a relative URI to conform to the restriction (e.g. "./m/s"). +In an instance document, on elements of type gml:MeasureType the mandatory uom attribute shall carry a value corresponding to either +- a conventional unit of measure symbol, +- a link to a definition of a unit of measure that does not have a conventional symbol, or when it is desired to indicate a precise or variant definition. + + + + + + + + This type is deprecated for tuples with ordinate values that are numbers. +CoordinatesType is a text string, intended to be used to record an array of tuples or coordinates. +While it is not possible to enforce the internal structure of the string through schema validation, some optional attributes have been provided in previous versions of GML to support a description of the internal structure. These attributes are deprecated. The attributes were intended to be used as follows: +Decimal symbol used for a decimal point (default="." a stop or period) +cs symbol used to separate components within a tuple or coordinate string (default="," a comma) +ts symbol used to separate tuples or coordinate strings (default=" " a space) +Since it is based on the XML Schema string type, CoordinatesType may be used in the construction of tables of tuples or arrays of tuples, including ones that contain mixed text and numeric values. + + + + + + + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + gml:CodeListType provides for lists of terms. The values in an instance element shall all be valid according to the rules of the dictionary, classification scheme, or authority identified by the value of its codeSpace attribute. + + + + + + + + + + gml:CodeOrNilReasonListType provides for lists of terms. The values in an instance element shall all be valid according to the rules of the dictionary, classification scheme, or authority identified by the value of its codeSpace attribute. An instance element may also include embedded values from NilReasonType. It is intended to be used in situations where a term or classification is expected, but the value may be absent for some reason. + + + + + + + + + + gml:MeasureListType provides for a list of quantities. + + + + + + + + + + gml:MeasureOrNilReasonListType provides for a list of quantities. An instance element may also include embedded values from NilReasonType. It is intended to be used in situations where a value is expected, but the value may be absent for some reason. + + + + + + + + diff --git a/xsd/gml/geometryBasic0d1d-extract.xsd b/xsd/gml/geometryBasic0d1d-extract.xsd index fec149d6..d66cf9d5 100644 --- a/xsd/gml/geometryBasic0d1d-extract.xsd +++ b/xsd/gml/geometryBasic0d1d-extract.xsd @@ -1,271 +1,271 @@ - - - - - geometryBasic0d1d.xsd - See ISO/DIS 19136 Clause 10. -Any geometry element that inherits the semantics of AbstractGeometryType may be viewed as a set of direct positions. -All of the classes derived from AbstractGeometryType inherit an optional association to a coordinate reference system. All direct positions shall directly or indirectly be associated with a coordinate reference system. When geometry elements are aggregated in another geometry element (such as a MultiGeometry or GeometricComplex), which already has a coordinate reference system specified, then these elements are assumed to be in that same coordinate reference system unless otherwise specified. -The geometry model distinguishes geometric primitives, aggregates and complexes. -Geometric primitives, i.e. instances of a subtype of AbstractGeometricPrimitiveType, will be open, that is, they will not contain their boundary points; curves will not contain their end points, surfaces will not contain their boundary curves, and solids will not contain their bounding surfaces. - -GML is an OGC Standard. -Copyright (c) 2007,2010 Open Geospatial Consortium, Inc. All Rights Reserved. -To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . - - - - - - All geometry elements are derived directly or indirectly from this abstract supertype. A geometry element may have an identifying attribute (gml:id), one or more names (elements identifier and name) and a description (elements description and descriptionReference) . It may be associated with a spatial reference system (attribute group gml:SRSReferenceGroup). -The following rules shall be adhered to: -- Every geometry type shall derive from this abstract type. -- Every geometry element (i.e. an element of a geometry type) shall be directly or indirectly in the substitution group of AbstractGeometry. - - - - - - - - - - The attribute group SRSReferenceGroup is an optional reference to the CRS used by this geometry, with optional additional information to simplify the processing of the coordinates when a more complete definition of the CRS is not needed. -In general the attribute srsName points to a CRS instance of gml:AbstractCoordinateReferenceSystem. For well-known references it is not required that the CRS description exists at the location the URI points to. -If no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of. - - - - - - - - The attributes uomLabels and axisLabels, defined in the SRSInformationGroup attribute group, are optional additional and redundant information for a CRS to simplify the processing of the coordinate values when a more complete definition of the CRS is not needed. This information shall be the same as included in the complete definition of the CRS, referenced by the srsName attribute. When the srsName attribute is included, either both or neither of the axisLabels and uomLabels attributes shall be included. When the srsName attribute is omitted, both of these attributes shall be omitted. -The attribute axisLabels is an ordered list of labels for all the axes of this CRS. The gml:axisAbbrev value should be used for these axis labels, after spaces and forbidden characters are removed. When the srsName attribute is included, this attribute is optional. When the srsName attribute is omitted, this attribute shall also be omitted. -The attribute uomLabels is an ordered list of unit of measure (uom) labels for all the axes of this CRS. The value of the string in the gml:catalogSymbol should be used for this uom labels, after spaces and forbidden characters are removed. When the axisLabels attribute is included, this attribute shall also be included. When the axisLabels attribute is omitted, this attribute shall also be omitted. - - - - - The AbstractGeometry element is the abstract head of the substitution group for all geometry elements of GML. This includes pre-defined and user-defined geometry elements. Any geometry element shall be a direct or indirect extension/restriction of AbstractGeometryType and shall be directly or indirectly in the substitution group of AbstractGeometry. - - - - - A geometric property may either be any geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same or another document). Note that either the reference or the contained element shall be given, but not both or none. -If a feature has a property that takes a geometry element as its value, this is called a geometry property. A generic type for such a geometry property is GeometryPropertyType. - - - - - - - - - - If a feature has a property which takes an array of geometry elements as its value, this is called a geometry array property. A generic type for such a geometry property is GeometryArrayPropertyType. -The elements are always contained inline in the array property, referencing geometry elements or arrays of geometry elements via XLinks is not supported. - - - - - - - - - Direct position instances hold the coordinates for a position within some coordinate reference system (CRS). Since direct positions, as data types, will often be included in larger objects (such as geometry elements) that have references to CRS, the srsName attribute will in general be missing, if this particular direct position is included in a larger element with such a reference to a CRS. In this case, the CRS is implicitly assumed to take on the value of the containing object's CRS. -if no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of, typically a geometric object like a point, curve, etc. - - - - - - - - - - - posList instances (and other instances with the content model specified by DirectPositionListType) hold the coordinates for a sequence of direct positions within the same coordinate reference system (CRS). -if no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of, typically a geometric object like a point, curve, etc. -The optional attribute count specifies the number of direct positions in the list. If the attribute count is present then the attribute srsDimension shall be present, too. -The number of entries in the list is equal to the product of the dimensionality of the coordinate reference system (i.e. it is a derived value of the coordinate reference system definition) and the number of direct positions. - - - - - - - - - - - - GML supports two different ways to specify a geometric position: either by a direct position (a data type) or a point (a geometric object). -pos elements are positions that are "owned" by the geometric primitive encapsulating this geometric position. -pointProperty elements contain a point that may be referenced from other geometry elements or reference another point defined elsewhere (reuse of existing points). - - - - - - - - - GML supports two different ways to specify a list of geometric positions: either by a sequence of geometric positions (by reusing the group definition) or a sequence of direct positions (element posList). -The posList element allows for a compact way to specify the coordinates of the positions, if all positions are represented in the same coordinate reference system. - - - - - - - - - For some applications the components of the position may be adjusted to yield a unit vector. - - - - - - - - - - - - - - - deprecated - - - - - - - - Envelope defines an extent using a pair of positions defining opposite corners in arbitrary dimensions. The first direct position is the "lower corner" (a coordinate position consisting of all the minimal ordinates for each dimension for all points within the envelope), the second one the "upper corner" (a coordinate position consisting of all the maximal ordinates for each dimension for all points within the envelope). -The use of the properties "coordinates" and "pos" has been deprecated. The explicitly named properties "lowerCorner" and "upperCorner" shall be used instead. - - - - - gml:AbstractGeometricPrimitiveType is the abstract root type of the geometric primitives. A geometric primitive is a geometric object that is not decomposed further into other primitives in the system. All primitives are oriented in the direction implied by the sequence of their coordinate tuples. - - - - - - - - The AbstractGeometricPrimitive element is the abstract head of the substitution group for all (pre- and user-defined) geometric primitives. - - - - - A property that has a geometric primitive as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. - - - - - - - - - - - - - - - - - - - - - A Point is defined by a single coordinate tuple. The direct position of a point is specified by the pos element which is of type DirectPositionType. - - - - - A property that has a point as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. - - - - - - - - - - This property element either references a point via the XLink-attributes or contains the point element. pointProperty is the predefined property which may be used by GML Application Schemas whenever a GML feature has a property with a value that is substitutable for Point. - - - - - gml:PointArrayPropertyType is a container for an array of points. The elements are always contained inline in the array property, referencing geometry elements or arrays of geometry elements via XLinks is not supported. - - - - - - - - - gml:AbstractCurveType is an abstraction of a curve to support the different levels of complexity. The curve may always be viewed as a geometric primitive, i.e. is continuous. - - - - - - - - The AbstractCurve element is the abstract head of the substitution group for all (continuous) curve elements. - - - - - A property that has a curve as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. - - - - - - - - - - This property element either references a curve via the XLink-attributes or contains the curve element. curveProperty is the predefined property which may be used by GML Application Schemas whenever a GML feature has a property with a value that is substitutable for AbstractCurve. - - - - - A container for an array of curves. The elements are always contained in the array property, referencing geometry elements or arrays of geometry elements via XLinks is not supported. - - - - - - - - - - - - - - - - - - - - - - - - A LineString is a special curve that consists of a single segment with linear interpolation. It is defined by two or more coordinate tuples, with linear interpolation between them. The number of direct positions in the list shall be at least two. - - - + + + + + geometryBasic0d1d.xsd + See ISO/DIS 19136 Clause 10. +Any geometry element that inherits the semantics of AbstractGeometryType may be viewed as a set of direct positions. +All of the classes derived from AbstractGeometryType inherit an optional association to a coordinate reference system. All direct positions shall directly or indirectly be associated with a coordinate reference system. When geometry elements are aggregated in another geometry element (such as a MultiGeometry or GeometricComplex), which already has a coordinate reference system specified, then these elements are assumed to be in that same coordinate reference system unless otherwise specified. +The geometry model distinguishes geometric primitives, aggregates and complexes. +Geometric primitives, i.e. instances of a subtype of AbstractGeometricPrimitiveType, will be open, that is, they will not contain their boundary points; curves will not contain their end points, surfaces will not contain their boundary curves, and solids will not contain their bounding surfaces. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium, Inc. All Rights Reserved. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + All geometry elements are derived directly or indirectly from this abstract supertype. A geometry element may have an identifying attribute (gml:id), one or more names (elements identifier and name) and a description (elements description and descriptionReference) . It may be associated with a spatial reference system (attribute group gml:SRSReferenceGroup). +The following rules shall be adhered to: +- Every geometry type shall derive from this abstract type. +- Every geometry element (i.e. an element of a geometry type) shall be directly or indirectly in the substitution group of AbstractGeometry. + + + + + + + + + + The attribute group SRSReferenceGroup is an optional reference to the CRS used by this geometry, with optional additional information to simplify the processing of the coordinates when a more complete definition of the CRS is not needed. +In general the attribute srsName points to a CRS instance of gml:AbstractCoordinateReferenceSystem. For well-known references it is not required that the CRS description exists at the location the URI points to. +If no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of. + + + + + + + + The attributes uomLabels and axisLabels, defined in the SRSInformationGroup attribute group, are optional additional and redundant information for a CRS to simplify the processing of the coordinate values when a more complete definition of the CRS is not needed. This information shall be the same as included in the complete definition of the CRS, referenced by the srsName attribute. When the srsName attribute is included, either both or neither of the axisLabels and uomLabels attributes shall be included. When the srsName attribute is omitted, both of these attributes shall be omitted. +The attribute axisLabels is an ordered list of labels for all the axes of this CRS. The gml:axisAbbrev value should be used for these axis labels, after spaces and forbidden characters are removed. When the srsName attribute is included, this attribute is optional. When the srsName attribute is omitted, this attribute shall also be omitted. +The attribute uomLabels is an ordered list of unit of measure (uom) labels for all the axes of this CRS. The value of the string in the gml:catalogSymbol should be used for this uom labels, after spaces and forbidden characters are removed. When the axisLabels attribute is included, this attribute shall also be included. When the axisLabels attribute is omitted, this attribute shall also be omitted. + + + + + The AbstractGeometry element is the abstract head of the substitution group for all geometry elements of GML. This includes pre-defined and user-defined geometry elements. Any geometry element shall be a direct or indirect extension/restriction of AbstractGeometryType and shall be directly or indirectly in the substitution group of AbstractGeometry. + + + + + A geometric property may either be any geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same or another document). Note that either the reference or the contained element shall be given, but not both or none. +If a feature has a property that takes a geometry element as its value, this is called a geometry property. A generic type for such a geometry property is GeometryPropertyType. + + + + + + + + + + If a feature has a property which takes an array of geometry elements as its value, this is called a geometry array property. A generic type for such a geometry property is GeometryArrayPropertyType. +The elements are always contained inline in the array property, referencing geometry elements or arrays of geometry elements via XLinks is not supported. + + + + + + + + + Direct position instances hold the coordinates for a position within some coordinate reference system (CRS). Since direct positions, as data types, will often be included in larger objects (such as geometry elements) that have references to CRS, the srsName attribute will in general be missing, if this particular direct position is included in a larger element with such a reference to a CRS. In this case, the CRS is implicitly assumed to take on the value of the containing object's CRS. +if no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of, typically a geometric object like a point, curve, etc. + + + + + + + + + + + posList instances (and other instances with the content model specified by DirectPositionListType) hold the coordinates for a sequence of direct positions within the same coordinate reference system (CRS). +if no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of, typically a geometric object like a point, curve, etc. +The optional attribute count specifies the number of direct positions in the list. If the attribute count is present then the attribute srsDimension shall be present, too. +The number of entries in the list is equal to the product of the dimensionality of the coordinate reference system (i.e. it is a derived value of the coordinate reference system definition) and the number of direct positions. + + + + + + + + + + + + GML supports two different ways to specify a geometric position: either by a direct position (a data type) or a point (a geometric object). +pos elements are positions that are "owned" by the geometric primitive encapsulating this geometric position. +pointProperty elements contain a point that may be referenced from other geometry elements or reference another point defined elsewhere (reuse of existing points). + + + + + + + + + GML supports two different ways to specify a list of geometric positions: either by a sequence of geometric positions (by reusing the group definition) or a sequence of direct positions (element posList). +The posList element allows for a compact way to specify the coordinates of the positions, if all positions are represented in the same coordinate reference system. + + + + + + + + + For some applications the components of the position may be adjusted to yield a unit vector. + + + + + + + + + + + + + + + deprecated + + + + + + + + Envelope defines an extent using a pair of positions defining opposite corners in arbitrary dimensions. The first direct position is the "lower corner" (a coordinate position consisting of all the minimal ordinates for each dimension for all points within the envelope), the second one the "upper corner" (a coordinate position consisting of all the maximal ordinates for each dimension for all points within the envelope). +The use of the properties "coordinates" and "pos" has been deprecated. The explicitly named properties "lowerCorner" and "upperCorner" shall be used instead. + + + + + gml:AbstractGeometricPrimitiveType is the abstract root type of the geometric primitives. A geometric primitive is a geometric object that is not decomposed further into other primitives in the system. All primitives are oriented in the direction implied by the sequence of their coordinate tuples. + + + + + + + + The AbstractGeometricPrimitive element is the abstract head of the substitution group for all (pre- and user-defined) geometric primitives. + + + + + A property that has a geometric primitive as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + + + + + + + + + + + + A Point is defined by a single coordinate tuple. The direct position of a point is specified by the pos element which is of type DirectPositionType. + + + + + A property that has a point as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + This property element either references a point via the XLink-attributes or contains the point element. pointProperty is the predefined property which may be used by GML Application Schemas whenever a GML feature has a property with a value that is substitutable for Point. + + + + + gml:PointArrayPropertyType is a container for an array of points. The elements are always contained inline in the array property, referencing geometry elements or arrays of geometry elements via XLinks is not supported. + + + + + + + + + gml:AbstractCurveType is an abstraction of a curve to support the different levels of complexity. The curve may always be viewed as a geometric primitive, i.e. is continuous. + + + + + + + + The AbstractCurve element is the abstract head of the substitution group for all (continuous) curve elements. + + + + + A property that has a curve as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + This property element either references a curve via the XLink-attributes or contains the curve element. curveProperty is the predefined property which may be used by GML Application Schemas whenever a GML feature has a property with a value that is substitutable for AbstractCurve. + + + + + A container for an array of curves. The elements are always contained in the array property, referencing geometry elements or arrays of geometry elements via XLinks is not supported. + + + + + + + + + + + + + + + + + + + + + + + + A LineString is a special curve that consists of a single segment with linear interpolation. It is defined by two or more coordinate tuples, with linear interpolation between them. The number of direct positions in the list shall be at least two. + + + diff --git a/xsd/gml/gmlBase-extract.xsd b/xsd/gml/gmlBase-extract.xsd index a870b6d7..bc2308e9 100644 --- a/xsd/gml/gmlBase-extract.xsd +++ b/xsd/gml/gmlBase-extract.xsd @@ -1,168 +1,168 @@ - - - - gmlBase.xsd - See ISO/DIS 19136 7.2. -The gmlBase schema components establish the GML model and syntax, in particular -- a root XML type from which XML types for all GML objects should be derived, -- a pattern and components for GML properties, -- patterns for collections and arrays, and components for generic collections and arrays, -- components for associating metadata with GML objects, -- components for constructing definitions and dictionaries. - -GML is an OGC Standard. -Copyright (c) 2007,2010 Open Geospatial Consortium, Inc. All Rights Reserved. -To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . - - - - - - - This element has no type defined, and is therefore implicitly (according to the rules of W3C XML Schema) an XML Schema anyType. It is used as the head of an XML Schema substitution group which unifies complex content and certain simple content elements used for datatypes in GML, including the gml:AbstractGML substitution group. - - - - - The abstract element gml:AbstractGML is "any GML object having identity". It acts as the head of an XML Schema substitution group, which may include any element which is a GML feature, or other object, with identity. This is used as a variable in content models in GML core and application schemas. It is effectively an abstract superclass for all GML objects. - - - - - - - - - - - - - - - - - - XLink components are the standard method to support hypertext referencing in XML. An XML Schema attribute group, gml:AssociationAttributeGroup, is provided to support the use of Xlinks as the method for indicating the value of a property by reference in a uniform manner in GML. - - - - - - Applying this pattern shall restrict the multiplicity of objects in a property element using this content model to exactly one. An instance of this type shall contain an element representing an object, or serve as a pointer to a remote object. -Applying the pattern to define an application schema specific property type allows to restrict -- the inline object to specified object types, -- the encoding to "by-reference only" (see 7.2.3.7), -- the encoding to "inline only" (see 7.2.3.8). - - - - - - - - - - - - Encoding a GML property inline vs. by-reference shall not imply anything about the "ownership" of the contained or referenced GML Object, i.e. the encoding style shall not imply any "deep-copy" or "deep-delete" semantics. To express ownership over the contained or referenced GML Object, the gml:OwnershipAttributeGroup attribute group may be added to object-valued property elements. If the attribute group is not part of the content model of such a property element, then the value may not be "owned". -When the value of the owns attribute is "true", the existence of inline or referenced object(s) depends upon the existence of the parent object. - - - - - - This element shows how an element - declaration may include a Schematron constraint to limit the property to act - in either inline or by-reference mode, but not both. - - - - - gml:abstractReference may be used as the head of a subtitution group of more specific elements providing a value by-reference. - - - - - gml:ReferenceType is intended to be used in application schemas directly, if a property element shall use a "by-reference only" encoding. - - - - - - - gml:abstractInlineProperty may be used as the head of a subtitution group of more specific elements providing a value inline. - - - - - - - - - - - If the value of an object property is another object and that object contains also a property for the association between the two objects, then this name of the reverse property may be encoded in a gml:reversePropertyName element in an appinfo annotation of the property element to document the constraint between the two properties. The value of the element shall contain the qualified name of the property element. - - - - - The value of this property is a remote text description of the object. The xlink:href attribute of the gml:descriptionReference property references the external description. - - - - - The gml:name property provides a label or identifier for the object, commonly a descriptive name. An object may have several names, typically assigned by different authorities. gml:name uses the gml:CodeType content model. The authority for a name is indicated by the value of its (optional) codeSpace attribute. The name may or may not be unique, as determined by the rules of the organization responsible for the codeSpace. In common usage there will be one name per authority, so a processing application may select the name from its preferred codeSpace. - - - - - Often, a special identifier is assigned to an object by the maintaining authority with the intention that it is used in references to the object For such cases, the codeSpace shall be provided. That identifier is usually unique either globally or within an application domain. gml:identifier is a pre-defined property for such identifiers. - - - - - The attribute gml:id supports provision of a handle for the XML element representing a GML Object. Its use is mandatory for all GML objects. It is of XML type ID, so is constrained to be unique in the XML document within which it occurs. - - - - - To create a collection of GML Objects that are not all features, a property type shall be derived by extension from gml:AbstractMemberType. -This abstract property type is intended to be used only in object types where software shall be able to identify that an instance of such an object type is to be interpreted as a collection of objects. -By default, this abstract property type does not imply any ownership of the objects in the collection. The owns attribute of gml:OwnershipAttributeGroup may be used on a property element instance to assert ownership of an object in the collection. A collection shall not own an object already owned by another object. - - - - - - - A GML Object Collection is any GML Object with a property element in its content model whose content model is derived by extension from gml:AbstractMemberType. -In addition, the complex type describing the content model of the GML Object Collection may also include a reference to the attribute group gml:AggregationAttributeGroup to provide additional information about the semantics of the object collection. This information may be used by applications to group GML objects, and optionally to order and index them. -The allowed values for the aggregationType attribute are defined by gml:AggregationType. See 8.4 of ISO/IEC 11404:1996 for the meaning of the values in the enumeration. - - - - - - - - - - - - - - - - To associate metadata described by any XML Schema with a GML object, a property element shall be defined whose content model is derived by extension from gml:AbstractMetadataPropertyType. -The value of such a property shall be metadata. The content model of such a property type, i.e. the metadata application schema shall be specified by the GML Application Schema. -By default, this abstract property type does not imply any ownership of the metadata. The owns attribute of gml:OwnershipAttributeGroup may be used on a metadata property element instance to assert ownership of the metadata. -If metadata following the conceptual model of ISO 19115 is to be encoded in a GML document, the corresponding Implementation Specification specified in ISO/TS 19139 shall be used to encode the metadata information. - - - - - - - - - + + + + gmlBase.xsd + See ISO/DIS 19136 7.2. +The gmlBase schema components establish the GML model and syntax, in particular +- a root XML type from which XML types for all GML objects should be derived, +- a pattern and components for GML properties, +- patterns for collections and arrays, and components for generic collections and arrays, +- components for associating metadata with GML objects, +- components for constructing definitions and dictionaries. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium, Inc. All Rights Reserved. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + + This element has no type defined, and is therefore implicitly (according to the rules of W3C XML Schema) an XML Schema anyType. It is used as the head of an XML Schema substitution group which unifies complex content and certain simple content elements used for datatypes in GML, including the gml:AbstractGML substitution group. + + + + + The abstract element gml:AbstractGML is "any GML object having identity". It acts as the head of an XML Schema substitution group, which may include any element which is a GML feature, or other object, with identity. This is used as a variable in content models in GML core and application schemas. It is effectively an abstract superclass for all GML objects. + + + + + + + + + + + + + + + + + + XLink components are the standard method to support hypertext referencing in XML. An XML Schema attribute group, gml:AssociationAttributeGroup, is provided to support the use of Xlinks as the method for indicating the value of a property by reference in a uniform manner in GML. + + + + + + Applying this pattern shall restrict the multiplicity of objects in a property element using this content model to exactly one. An instance of this type shall contain an element representing an object, or serve as a pointer to a remote object. +Applying the pattern to define an application schema specific property type allows to restrict +- the inline object to specified object types, +- the encoding to "by-reference only" (see 7.2.3.7), +- the encoding to "inline only" (see 7.2.3.8). + + + + + + + + + + + + Encoding a GML property inline vs. by-reference shall not imply anything about the "ownership" of the contained or referenced GML Object, i.e. the encoding style shall not imply any "deep-copy" or "deep-delete" semantics. To express ownership over the contained or referenced GML Object, the gml:OwnershipAttributeGroup attribute group may be added to object-valued property elements. If the attribute group is not part of the content model of such a property element, then the value may not be "owned". +When the value of the owns attribute is "true", the existence of inline or referenced object(s) depends upon the existence of the parent object. + + + + + + This element shows how an element + declaration may include a Schematron constraint to limit the property to act + in either inline or by-reference mode, but not both. + + + + + gml:abstractReference may be used as the head of a subtitution group of more specific elements providing a value by-reference. + + + + + gml:ReferenceType is intended to be used in application schemas directly, if a property element shall use a "by-reference only" encoding. + + + + + + + gml:abstractInlineProperty may be used as the head of a subtitution group of more specific elements providing a value inline. + + + + + + + + + + + If the value of an object property is another object and that object contains also a property for the association between the two objects, then this name of the reverse property may be encoded in a gml:reversePropertyName element in an appinfo annotation of the property element to document the constraint between the two properties. The value of the element shall contain the qualified name of the property element. + + + + + The value of this property is a remote text description of the object. The xlink:href attribute of the gml:descriptionReference property references the external description. + + + + + The gml:name property provides a label or identifier for the object, commonly a descriptive name. An object may have several names, typically assigned by different authorities. gml:name uses the gml:CodeType content model. The authority for a name is indicated by the value of its (optional) codeSpace attribute. The name may or may not be unique, as determined by the rules of the organization responsible for the codeSpace. In common usage there will be one name per authority, so a processing application may select the name from its preferred codeSpace. + + + + + Often, a special identifier is assigned to an object by the maintaining authority with the intention that it is used in references to the object For such cases, the codeSpace shall be provided. That identifier is usually unique either globally or within an application domain. gml:identifier is a pre-defined property for such identifiers. + + + + + The attribute gml:id supports provision of a handle for the XML element representing a GML Object. Its use is mandatory for all GML objects. It is of XML type ID, so is constrained to be unique in the XML document within which it occurs. + + + + + To create a collection of GML Objects that are not all features, a property type shall be derived by extension from gml:AbstractMemberType. +This abstract property type is intended to be used only in object types where software shall be able to identify that an instance of such an object type is to be interpreted as a collection of objects. +By default, this abstract property type does not imply any ownership of the objects in the collection. The owns attribute of gml:OwnershipAttributeGroup may be used on a property element instance to assert ownership of an object in the collection. A collection shall not own an object already owned by another object. + + + + + + + A GML Object Collection is any GML Object with a property element in its content model whose content model is derived by extension from gml:AbstractMemberType. +In addition, the complex type describing the content model of the GML Object Collection may also include a reference to the attribute group gml:AggregationAttributeGroup to provide additional information about the semantics of the object collection. This information may be used by applications to group GML objects, and optionally to order and index them. +The allowed values for the aggregationType attribute are defined by gml:AggregationType. See 8.4 of ISO/IEC 11404:1996 for the meaning of the values in the enumeration. + + + + + + + + + + + + + + + + To associate metadata described by any XML Schema with a GML object, a property element shall be defined whose content model is derived by extension from gml:AbstractMetadataPropertyType. +The value of such a property shall be metadata. The content model of such a property type, i.e. the metadata application schema shall be specified by the GML Application Schema. +By default, this abstract property type does not imply any ownership of the metadata. The owns attribute of gml:OwnershipAttributeGroup may be used on a metadata property element instance to assert ownership of the metadata. +If metadata following the conceptual model of ISO 19115 is to be encoded in a GML document, the corresponding Implementation Specification specified in ISO/TS 19139 shall be used to encode the metadata information. + + + + + + + + + diff --git a/xsd/gml/gmlBasic2d-extract.xsd b/xsd/gml/gmlBasic2d-extract.xsd index a7e51919..386b5b4b 100644 --- a/xsd/gml/gmlBasic2d-extract.xsd +++ b/xsd/gml/gmlBasic2d-extract.xsd @@ -1,120 +1,120 @@ - - - - geometryBasic2d.xsd - See ISO/DIS 19136 Clause 10. - - GML is an OGC Standard. - Copyright (c) 2007,2010 Open Geospatial Consortium, Inc. All Rights Reserved. - To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . - - - - - - gml:AbstractSurfaceType is an abstraction of a surface to support the different levels of complexity. A surface is always a continuous region of a plane. - - - - - - - - The AbstractSurface element is the abstract head of the substitution group for all (continuous) surface elements. - - - - - A property that has a surface as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. - - - - - - - - - - This property element either references a surface via the XLink-attributes or contains the surface element. surfaceProperty is the predefined property which may be used by GML Application Schemas whenever a GML feature has a property with a value that is substitutable for AbstractSurface. - - - - - gml:SurfaceArrayPropertyType is a container for an array of surfaces. The elements are always contained in the array property, referencing geometry elements or arrays of geometry elements via XLinks is not supported. - - - - - - - - - - - - - - - - - - - A Polygon is a special surface that is defined by a single surface patch (see D.3.6). The boundary of this patch is coplanar and the polygon uses planar interpolation in its interior. -The elements exterior and interior describe the surface boundary of the polygon. - - - - - A boundary of a surface consists of a number of rings. In the normal 2D case, one of these rings is distinguished as being the exterior boundary. In a general manifold this is not always possible, in which case all boundaries shall be listed as interior boundaries, and the exterior will be empty. - - - - - A boundary of a surface consists of a number of rings. The "interior" rings separate the surface / surface patch from the area enclosed by the rings. - - - - - - - An abstraction of a ring to support surface boundaries of different complexity. -The AbstractRing element is the abstract head of the substitution group for all closed boundaries of a surface patch. - - - - - A property with the content model of gml:AbstractRingPropertyType encapsulates a ring to represent the surface boundary property of a surface. - - - - - - - - - - - - - - - - - - - - - - - A LinearRing is defined by four or more coordinate tuples, with linear interpolation between them; the first and last coordinates shall be coincident. The number of direct positions in the list shall be at least four. - - - - - A property with the content model of gml:LinearRingPropertyType encapsulates a linear ring to represent a component of a surface boundary. - - - - - - + + + + geometryBasic2d.xsd + See ISO/DIS 19136 Clause 10. + + GML is an OGC Standard. + Copyright (c) 2007,2010 Open Geospatial Consortium, Inc. All Rights Reserved. + To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + gml:AbstractSurfaceType is an abstraction of a surface to support the different levels of complexity. A surface is always a continuous region of a plane. + + + + + + + + The AbstractSurface element is the abstract head of the substitution group for all (continuous) surface elements. + + + + + A property that has a surface as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + This property element either references a surface via the XLink-attributes or contains the surface element. surfaceProperty is the predefined property which may be used by GML Application Schemas whenever a GML feature has a property with a value that is substitutable for AbstractSurface. + + + + + gml:SurfaceArrayPropertyType is a container for an array of surfaces. The elements are always contained in the array property, referencing geometry elements or arrays of geometry elements via XLinks is not supported. + + + + + + + + + + + + + + + + + + + A Polygon is a special surface that is defined by a single surface patch (see D.3.6). The boundary of this patch is coplanar and the polygon uses planar interpolation in its interior. +The elements exterior and interior describe the surface boundary of the polygon. + + + + + A boundary of a surface consists of a number of rings. In the normal 2D case, one of these rings is distinguished as being the exterior boundary. In a general manifold this is not always possible, in which case all boundaries shall be listed as interior boundaries, and the exterior will be empty. + + + + + A boundary of a surface consists of a number of rings. The "interior" rings separate the surface / surface patch from the area enclosed by the rings. + + + + + + + An abstraction of a ring to support surface boundaries of different complexity. +The AbstractRing element is the abstract head of the substitution group for all closed boundaries of a surface patch. + + + + + A property with the content model of gml:AbstractRingPropertyType encapsulates a ring to represent the surface boundary property of a surface. + + + + + + + + + + + + + + + + + + + + + + + A LinearRing is defined by four or more coordinate tuples, with linear interpolation between them; the first and last coordinates shall be coincident. The number of direct positions in the list shall be at least four. + + + + + A property with the content model of gml:LinearRingPropertyType encapsulates a linear ring to represent a component of a surface boundary. + + + + + + diff --git a/xsd/gml/gml_extract_all_objects.xsd b/xsd/gml/gml_extract_all_objects.xsd index 1771bb9f..cd6227d3 100644 --- a/xsd/gml/gml_extract_all_objects.xsd +++ b/xsd/gml/gml_extract_all_objects.xsd @@ -1,12 +1,12 @@ - - - - - - - - - - - - + + + + + + + + + + + + diff --git a/xsd/ifopt/ifopt_administration.xsd b/xsd/ifopt/ifopt_administration.xsd index 7431e95b..bb098f19 100644 --- a/xsd/ifopt/ifopt_administration.xsd +++ b/xsd/ifopt/ifopt_administration.xsd @@ -1,254 +1,254 @@ - - - - - - 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.siri.org.uk/schema/2.0/ifopt}ifopt_administration.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, Crown Copyright 2006-2020 - - -
        -
      • Derived from the SIRI standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG6 - - IFOPT Fixed Objects in Public Transport - Base Types. - Standard -       -       - Data administration types for IFOPT Fixed Objects in Public Transport. -       - - - - - - - Type for identifier of an ORGANISATION with administrative responsibility. - - - - - - Type for a reference to an ORGANISATION with administrative responsibility. - - - - - - - - Type for a versioned reference to an ORGANISATION with administrative responsibility. - - - - - - - - - - - Type for identifier of ADMINISTRATIVE ZONE. - - - - - - - - Type for a reference to an ADMINISTRATIVE ZONE. - - - - - - - - Type for a versioned reference to anADMINISTRATIVE ZONE. - - - - - - - - - - Type for a collection of one or more references to ADMINISTRATIVE ZONEs. - - - - - Reference to the identifier of an ADMINISTRATIVE ZONE. - - - - - - - - Enumeration of allowed values for RESPONSIBILITY ROLEs. - - - - - - - - - - - - - - Type for identifier of type of Namespace. - - - - - - Type for a reference to an Namespace. - - - - - - - - The type for identifier of Namespace. - - - - - - Type for a value of a namespace. - - - - - - - Type for a Identifier of Region. - - - - - - Type for a Reference to identifier of Region. - - - - - - - - - Type for identifier of AUTHORITY. - - - - - - - - Type for a reference to an AUTHORITY. - - - - - - - - - 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 DATA MANAGED OBJECT, that is an object that may be assigned a RESPONSIBILITY SET dictating a responsible ORGANISATION and/or ADMINISTRATIVE ZONE. - - - - - - - - - - - - Elements for a DATA MANAGED OBJECT. - - - - - ADMINISTRATIVE ZONEthat manages object. If absent then manager same as for containing parent of object. - - - - - Collection of URL's associated with object. - - - - -       + + + + + + 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.siri.org.uk/schema/2.0/ifopt}ifopt_administration.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + CEN, Crown Copyright 2006-2021 + + +
        +
      • Derived from the SIRI standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG6 + + IFOPT Fixed Objects in Public Transport - Base Types. + Standard +       +       + Data administration types for IFOPT Fixed Objects in Public Transport. +       + + + + + + + Type for identifier of an ORGANISATION with administrative responsibility. + + + + + + Type for a reference to an ORGANISATION with administrative responsibility. + + + + + + + + Type for a versioned reference to an ORGANISATION with administrative responsibility. + + + + + + + + + + + Type for identifier of ADMINISTRATIVE ZONE. + + + + + + + + Type for a reference to an ADMINISTRATIVE ZONE. + + + + + + + + Type for a versioned reference to anADMINISTRATIVE ZONE. + + + + + + + + + + Type for a collection of one or more references to ADMINISTRATIVE ZONEs. + + + + + Reference to the identifier of an ADMINISTRATIVE ZONE. + + + + + + + + Enumeration of allowed values for RESPONSIBILITY ROLEs. + + + + + + + + + + + + + + Type for identifier of type of Namespace. + + + + + + Type for a reference to an Namespace. + + + + + + + + The type for identifier of Namespace. + + + + + + Type for a value of a namespace. + + + + + + + Type for a Identifier of Region. + + + + + + Type for a Reference to identifier of Region. + + + + + + + + + Type for identifier of AUTHORITY. + + + + + + + + Type for a reference to an AUTHORITY. + + + + + + + + + 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 DATA MANAGED OBJECT, that is an object that may be assigned a RESPONSIBILITY SET dictating a responsible ORGANISATION and/or ADMINISTRATIVE ZONE. + + + + + + + + + + + + Elements for a DATA MANAGED OBJECT. + + + + + ADMINISTRATIVE ZONEthat manages object. If absent then manager same as for containing parent of object. + + + + + Collection of URL's associated with object. + + + + +       diff --git a/xsd/ifopt/ifopt_allStopPlace.xsd b/xsd/ifopt/ifopt_allStopPlace.xsd index bd231b33..b164f96e 100644 --- a/xsd/ifopt/ifopt_allStopPlace.xsd +++ b/xsd/ifopt/ifopt_allStopPlace.xsd @@ -1,33 +1,33 @@ - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + diff --git a/xsd/ifopt/ifopt_checkpoint.xsd b/xsd/ifopt/ifopt_checkpoint.xsd index 7cc8e5f8..e56f494a 100644 --- a/xsd/ifopt/ifopt_checkpoint.xsd +++ b/xsd/ifopt/ifopt_checkpoint.xsd @@ -1,222 +1,222 @@ - - - - - - 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 CHECK CONSTRAINT types.

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_accessibility.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, Crown Copyright 2006-2020 - - -
        -
      • Derived from the IFOPT standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG6 - - IFOPT Fixed Objects in Public Transport - CHECK CONSTRAINT Types. - Standard -       -       - Fixed Objects CHECK CONSTRAINT types for IFOPT Fixed Objects in Public Transport. -       - - - - - - Type for identifier of a CHECK CONSTRAINT.within a STOP PLACE. - - - - - - Type for reference to am identifier of a hazard within a STOP PLACE. - - - - - - - - - Type for a CHECK CONSTRAINT Hazard that can be associated with. - - - - - Identifier of CHECK CONSTRAINt. - - - - - - - - - - - Validty condition governing applicability of CHECK CONSTRAINT. - - - - - Type of process that may occur at CHECK CONSTRAINt. - - - - - Type of process that may occur at CHECK CONSTRAINt. - - - - - Type of physical featrue that may slow use of CHECK CONSTRAINt. - - - - - Type of crowding that may slow use of CHECK CONSTRAINt. - - - - - Classification of feature of CHECK CONSTRAINT. - - - - - - - Allowed values for a CHECK CONSTRAINT. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Allowed values for a CHECK CONSTRAINT. - - - - - - - - - - Allowed values for a CHECK CONSTRAINT. - - - - - - - - - - - - - - - - - - - - - Allowed values for a CHECK CONSTRAINT. - - - - - - - - - - - Group of delays found at a stop group. Duratiosn relate to given validity condition. - - - - - Minimum duration needed to pass through CHECK CONSTRAINT. - - - - - Average duration expected to pass through CHECK CONSTRAINT. - - - - - Maximum duration expected to pass through CHECK CONSTRAINT. - - - - - -       + + + + + + 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 CHECK CONSTRAINT types.

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_accessibility.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + CEN, Crown Copyright 2006-2021 + + +
        +
      • Derived from the IFOPT standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG6 + + IFOPT Fixed Objects in Public Transport - CHECK CONSTRAINT Types. + Standard +       +       + Fixed Objects CHECK CONSTRAINT types for IFOPT Fixed Objects in Public Transport. +       + + + + + + Type for identifier of a CHECK CONSTRAINT.within a STOP PLACE. + + + + + + Type for reference to am identifier of a hazard within a STOP PLACE. + + + + + + + + + Type for a CHECK CONSTRAINT Hazard that can be associated with. + + + + + Identifier of CHECK CONSTRAINt. + + + + + + + + + + + Validty condition governing applicability of CHECK CONSTRAINT. + + + + + Type of process that may occur at CHECK CONSTRAINt. + + + + + Type of process that may occur at CHECK CONSTRAINt. + + + + + Type of physical featrue that may slow use of CHECK CONSTRAINt. + + + + + Type of crowding that may slow use of CHECK CONSTRAINt. + + + + + Classification of feature of CHECK CONSTRAINT. + + + + + + + Allowed values for a CHECK CONSTRAINT. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Allowed values for a CHECK CONSTRAINT. + + + + + + + + + + Allowed values for a CHECK CONSTRAINT. + + + + + + + + + + + + + + + + + + + + + Allowed values for a CHECK CONSTRAINT. + + + + + + + + + + + Group of delays found at a stop group. Duratiosn relate to given validity condition. + + + + + Minimum duration needed to pass through CHECK CONSTRAINT. + + + + + Average duration expected to pass through CHECK CONSTRAINT. + + + + + Maximum duration expected to pass through CHECK CONSTRAINT. + + + + + +       diff --git a/xsd/ifopt/ifopt_countries.xsd b/xsd/ifopt/ifopt_countries.xsd index 257fd611..a52b6449 100644 --- a/xsd/ifopt/ifopt_countries.xsd +++ b/xsd/ifopt/ifopt_countries.xsd @@ -1,1320 +1,1320 @@ - - - - - - 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.siri.org.uk/schema/2.0/ifopt}ifopt_countries.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, Crown Copyright 2006-2020 - - -
        -
      • Derived from the SIRI standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 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. - - - - - -       + + + + + + 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.siri.org.uk/schema/2.0/ifopt}ifopt_countries.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + CEN, Crown Copyright 2006-2021 + + +
        +
      • Derived from the SIRI standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 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/xsd/ifopt/ifopt_equipment.xsd b/xsd/ifopt/ifopt_equipment.xsd index 61272dc3..e8d1319c 100644 --- a/xsd/ifopt/ifopt_equipment.xsd +++ b/xsd/ifopt/ifopt_equipment.xsd @@ -1,207 +1,207 @@ - - - - - - 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.siri.org.uk/schema/2.0/ifopt}ifopt_equipment.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, Crown Copyright 2006-2020 - - -
        -
      • Derived from the TransModel standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG6 - - IFOPT Fixed Objects in Public Transport - Equipment Base Types. - Standard -       -       - Equipment types for IFOPT Fixed Objects in Public Transport. -       - - - - - - - - Type for identifier of EQUIPMENT. - - - - - - Type for reference to a EQUIPMENT. - - - - - - - - - Type for a identifier of EQUIPMENT. - - - - - - Type for TYPE OF EQUIPMENT. - - - - - - - - - Availabilityload status of a EQUIPMENT. - - - - - - - - - - - Coomon Elements for EQUIPMENt. - - - - - Identifer of EQUIPMENT. - - - - - Name of EQUIPMENT. - - - - - Type for reference to TYPE OF EQUIPMENT. - - - - - - - Type for abstract EQUIPMENT. - - - - - - - - - - - - Type for INSTALLED EQUIPMENT. - - - - - - - - - Type for SITE EQUIPMENT. - - - - - - - - - - - - EQUIPMENT. that may be in a fixed within a SITe. - - - - - - LOCAL SERVICe. - - - - - Element for LOCAL SERVICe. - - - - - Conditison governing availability of serevice. - - - - - Classification of features. - - - - - - Features of LOCAL SERVICe. - - - - - - - - - - Type for LOCAL SERVICE. - - - - - - - - - - -       + + + + + + 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.siri.org.uk/schema/2.0/ifopt}ifopt_equipment.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + CEN, Crown Copyright 2006-2021 + + +
        +
      • Derived from the TransModel standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG6 + + IFOPT Fixed Objects in Public Transport - Equipment Base Types. + Standard +       +       + Equipment types for IFOPT Fixed Objects in Public Transport. +       + + + + + + + + Type for identifier of EQUIPMENT. + + + + + + Type for reference to a EQUIPMENT. + + + + + + + + + Type for a identifier of EQUIPMENT. + + + + + + Type for TYPE OF EQUIPMENT. + + + + + + + + + Availabilityload status of a EQUIPMENT. + + + + + + + + + + + Coomon Elements for EQUIPMENt. + + + + + Identifer of EQUIPMENT. + + + + + Name of EQUIPMENT. + + + + + Type for reference to TYPE OF EQUIPMENT. + + + + + + + Type for abstract EQUIPMENT. + + + + + + + + + + + + Type for INSTALLED EQUIPMENT. + + + + + + + + + Type for SITE EQUIPMENT. + + + + + + + + + + + + EQUIPMENT. that may be in a fixed within a SITe. + + + + + + LOCAL SERVICe. + + + + + Element for LOCAL SERVICe. + + + + + Conditison governing availability of serevice. + + + + + Classification of features. + + + + + + Features of LOCAL SERVICe. + + + + + + + + + + Type for LOCAL SERVICE. + + + + + + + + + + +       diff --git a/xsd/ifopt/ifopt_location.xsd b/xsd/ifopt/ifopt_location.xsd index 80473c52..0f53d84d 100644 --- a/xsd/ifopt/ifopt_location.xsd +++ b/xsd/ifopt/ifopt_location.xsd @@ -1,281 +1,281 @@ - - - - - - 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 03 23 Revise projections - - - 2007-06-12 - - 2011-04-19 - Correct siri: namespace - - -

      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.siri.org.uk/schema/2.0/ifopt}ifopt_location.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, Crown Copyright 2006-2020 - - -
        -
      • Derived from the SIRI standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 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 FEATURE in a GIS data system. - - - - - - - - - - Type for reference to a FEATURE. - - - - - Unique identfiier of referenced element, eg TOId. - - - - - Type for identifier of FEATURE. - - - - - - - Type for identifier of a GIS FEATURe. - - - - - - Type for reference to a GIS FEATURe. - - - - - - - - - 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 Coordinates. - - - - - 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 onto 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. - - - - - - - - - - - - - -       + + + + + + 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 03 23 Revise projections + + + 2007-06-12 + + 2011-04-19 + Correct siri: namespace + + +

      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.siri.org.uk/schema/2.0/ifopt}ifopt_location.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + CEN, Crown Copyright 2006-2021 + + +
        +
      • Derived from the SIRI standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 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 FEATURE in a GIS data system. + + + + + + + + + + Type for reference to a FEATURE. + + + + + Unique identfiier of referenced element, eg TOId. + + + + + Type for identifier of FEATURE. + + + + + + + Type for identifier of a GIS FEATURe. + + + + + + Type for reference to a GIS FEATURe. + + + + + + + + + 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 Coordinates. + + + + + 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 onto 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. + + + + + + + + + + + + + +       diff --git a/xsd/ifopt/ifopt_modes.xsd b/xsd/ifopt/ifopt_modes.xsd index c23af381..15c88525 100644 --- a/xsd/ifopt/ifopt_modes.xsd +++ b/xsd/ifopt/ifopt_modes.xsd @@ -1,84 +1,84 @@ - - - - - - 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.siri.org.uk/schema/2.0/ifopt}ifopt_modes.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, Crown Copyright 2006-2020 - - -
        -
      • Derived from the SIRI standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG6 - - IFOPT Fixed Objects in Public Transport - mode Types. - Standard -       -       - Mode types for IFOPT Fixed Objects in Public Transport. -       - - - - - Allowed categories of stop place. - - - - - - - - - - - - - - - - - Allowed categroies of access to stop place. - - - - - - - - - -       + + + + + + 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.siri.org.uk/schema/2.0/ifopt}ifopt_modes.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + CEN, Crown Copyright 2006-2021 + + +
        +
      • Derived from the SIRI standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG6 + + IFOPT Fixed Objects in Public Transport - mode Types. + Standard +       +       + Mode types for IFOPT Fixed Objects in Public Transport. +       + + + + + Allowed categories of stop place. + + + + + + + + + + + + + + + + + Allowed categroies of access to stop place. + + + + + + + + + +       diff --git a/xsd/ifopt/ifopt_modification.xsd b/xsd/ifopt/ifopt_modification.xsd index a429ac32..a4fca7dd 100644 --- a/xsd/ifopt/ifopt_modification.xsd +++ b/xsd/ifopt/ifopt_modification.xsd @@ -1,173 +1,173 @@ - - - - - - - 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.siri.org.uk/schema/2.0/ifopt}ifopt_modification.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, Crown Copyright 2006-2020 - - -
        -
      • Derived from the SIRI standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 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. - - - -       + + + + + + + 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.siri.org.uk/schema/2.0/ifopt}ifopt_modification.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + CEN, Crown Copyright 2006-2021 + + +
        +
      • Derived from the SIRI standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 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/xsd/ifopt/ifopt_path.xsd b/xsd/ifopt/ifopt_path.xsd index 8a932c7c..5f1040c5 100644 --- a/xsd/ifopt/ifopt_path.xsd +++ b/xsd/ifopt/ifopt_path.xsd @@ -1,164 +1,164 @@ - - - - - - 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.siri.org.uk/schema/2.0/ifopt}ifopt_types.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, Crown Copyright 2006-2020 - - -
        -
      • Derived from the SIRI standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG6 - - IFOPT Fixed Objects in Public Transport - Stop place Base Types. - Standard -       -       - Basic link types for IFOPT Fixed Objects in Public Transport. -       - - - - Type for identifier of PATH JUNCTION. - - - - - - Reference to a PATH JUNCTION. - - - - - Type for reference to a PATH JUNCTION. - - - - - - - - - - - Type for identifier of an ACCESS link. - - - - - - Reference to an ACCESS link. - - - - - Type for reference to an ACCESS link. - - - - - - - - - Type for identifier of NAVIGATION PATH. - - - - - - Reference to a NAVIGATION PATH. - - - - - Type for reference to a NAVIGATION PATH. - - - - - - - - - Values for flow DIRECTION along PATH LINk. - - - - - - - - - Values for path heading. - - - - - - - - - - - - - Values for path heading. - - - - - - - - - - - Values for NAVIGATION PATH. type. - - - - - - - - - - - - -       + + + + + + 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.siri.org.uk/schema/2.0/ifopt}ifopt_types.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + CEN, Crown Copyright 2006-2021 + + +
        +
      • Derived from the SIRI standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG6 + + IFOPT Fixed Objects in Public Transport - Stop place Base Types. + Standard +       +       + Basic link types for IFOPT Fixed Objects in Public Transport. +       + + + + Type for identifier of PATH JUNCTION. + + + + + + Reference to a PATH JUNCTION. + + + + + Type for reference to a PATH JUNCTION. + + + + + + + + + + + Type for identifier of an ACCESS link. + + + + + + Reference to an ACCESS link. + + + + + Type for reference to an ACCESS link. + + + + + + + + + Type for identifier of NAVIGATION PATH. + + + + + + Reference to a NAVIGATION PATH. + + + + + Type for reference to a NAVIGATION PATH. + + + + + + + + + Values for flow DIRECTION along PATH LINk. + + + + + + + + + Values for path heading. + + + + + + + + + + + + + Values for path heading. + + + + + + + + + + + Values for NAVIGATION PATH. type. + + + + + + + + + + + + +       diff --git a/xsd/ifopt/ifopt_stop.xsd b/xsd/ifopt/ifopt_stop.xsd index 89f65807..69295671 100644 --- a/xsd/ifopt/ifopt_stop.xsd +++ b/xsd/ifopt/ifopt_stop.xsd @@ -1,393 +1,393 @@ - - - - - - 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 - - 2012-03-12 - Change IdentifertYpe to normalizedString - - 2018-11-13 - [vdv] Enum "ferrytPort" in StopPlaceTypeEnumeration changed to "ferryPort" - - -

      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.siri.org.uk/schema/2.0/ifopt}ifopt_types.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, Crown Copyright 2006-2020 - - -
        -
      • Derived from the SIRI standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 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 identifier of STOP PLACE. - - - - - - Reference to a STOP PLACE. - - - - - Type for reference to a STOP PLACE. - - - - - - - - Type for a collection of one or more references to a STOP PLACE. - - - - - - - - - Type for identifier of STOP PLACE. - - - - - - Type for reference to STOP PLACE. - - - - - - - - Type for reference to STOP PLACE Space. - - - - - - - - Type for reference to QUAY. - - - - - - - - Type for reference to ACCESS SPACe. - - - - - - - - Type for reference to BOARDING POSITION. - - - - - - - - Type for reference to STOP PLACE Entrance. - - - - - - - - Type for reference to VEHICLE STOPPING PLACe. - - - - - - - - Type for reference to VEHICLE STOPPING POSITION. - - - - - - - - - Type for identifier of a building LEVEL within a STOP PLACE. - - - - - - Type for reference to identifier of LEVEL. - - - - - - - - - Type for reference to identifier of PATHLINK. - - - - - - - - Type for reference to STOP PLACE Space. - - - - - - - - - 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 identifying the stop by SMS and other self-service channels. - - - - - A private code that 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 SITE COMPONENT Types. - - - - - - - - - - - - Enumeration of QUAY Types. - - - - - - - - - - - - - - - - - - - Enumeration of ACCESS SPACE Types. - - - - - - - - - - - - - - - - - - - - Enumeration of Passage Types. - - - - - - - - - - - - - - Enumeration of BOARDING POSITION Types. - - - - - - - - - - - - - - - - - - - - Enumeration of Relation to VEHICLE of STOPPING POSITION. - - - - - - - - - - - - - Enumeration of Interchange Weighting. - - - - - - - - - -       + + + + + + 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 + + 2012-03-12 + Change IdentifertYpe to normalizedString + + 2018-11-13 + [vdv] Enum "ferrytPort" in StopPlaceTypeEnumeration changed to "ferryPort" + + +

      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.siri.org.uk/schema/2.0/ifopt}ifopt_types.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + CEN, Crown Copyright 2006-2021 + + +
        +
      • Derived from the SIRI standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 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 identifier of STOP PLACE. + + + + + + Reference to a STOP PLACE. + + + + + Type for reference to a STOP PLACE. + + + + + + + + Type for a collection of one or more references to a STOP PLACE. + + + + + + + + + Type for identifier of STOP PLACE. + + + + + + Type for reference to STOP PLACE. + + + + + + + + Type for reference to STOP PLACE Space. + + + + + + + + Type for reference to QUAY. + + + + + + + + Type for reference to ACCESS SPACe. + + + + + + + + Type for reference to BOARDING POSITION. + + + + + + + + Type for reference to STOP PLACE Entrance. + + + + + + + + Type for reference to VEHICLE STOPPING PLACe. + + + + + + + + Type for reference to VEHICLE STOPPING POSITION. + + + + + + + + + Type for identifier of a building LEVEL within a STOP PLACE. + + + + + + Type for reference to identifier of LEVEL. + + + + + + + + + Type for reference to identifier of PATHLINK. + + + + + + + + Type for reference to STOP PLACE Space. + + + + + + + + + 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 identifying the stop by SMS and other self-service channels. + + + + + A private code that 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 SITE COMPONENT Types. + + + + + + + + + + + + Enumeration of QUAY Types. + + + + + + + + + + + + + + + + + + + Enumeration of ACCESS SPACE Types. + + + + + + + + + + + + + + + + + + + + Enumeration of Passage Types. + + + + + + + + + + + + + + Enumeration of BOARDING POSITION Types. + + + + + + + + + + + + + + + + + + + + Enumeration of Relation to VEHICLE of STOPPING POSITION. + + + + + + + + + + + + + Enumeration of Interchange Weighting. + + + + + + + + + +       diff --git a/xsd/ifopt/ifopt_time.xsd b/xsd/ifopt/ifopt_time.xsd index d9612247..83b12812 100644 --- a/xsd/ifopt/ifopt_time.xsd +++ b/xsd/ifopt/ifopt_time.xsd @@ -1,131 +1,131 @@ - - - - - - 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.siri.org.uk/schema/2.0/ifopt}ifopt_types.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, Crown Copyright 2006-2020 - - -
        -
      • Derived from the SIRI standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG6 - - IFOPT Fixed Objects in Public Transport - Time Base Types. - Standard -       -       - Basic Time types for IFOPT Fixed Objects in Public Transport. -       - - - - - - 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 specifed by the EndTimeStatus - - - - - - - - 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. - - - - - -       + + + + + + 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.siri.org.uk/schema/2.0/ifopt}ifopt_types.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + CEN, Crown Copyright 2006-2021 + + +
        +
      • Derived from the SIRI standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG6 + + IFOPT Fixed Objects in Public Transport - Time Base Types. + Standard +       +       + Basic Time types for IFOPT Fixed Objects in Public Transport. +       + + + + + + 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 specifed by the EndTimeStatus + + + + + + + + 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. + + + + + +       diff --git a/xsd/ifopt/ifopt_types.xsd b/xsd/ifopt/ifopt_types.xsd index 7cd86466..8fe51ed1 100644 --- a/xsd/ifopt/ifopt_types.xsd +++ b/xsd/ifopt/ifopt_types.xsd @@ -1,96 +1,96 @@ - - - - - - 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.siri.org.uk/schema/2.0/ifopt}ifopt_types.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, Crown Copyright 2006-2020 - - -
        -
      • Derived from the SIRI standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 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. - - - -       + + + + + + 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.siri.org.uk/schema/2.0/ifopt}ifopt_types.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + CEN, Crown Copyright 2006-2021 + + +
        +
      • Derived from the SIRI standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 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. + + + +       diff --git a/xsd/siri.xsd b/xsd/siri.xsd index 5ceee4c5..09aba650 100644 --- a/xsd/siri.xsd +++ b/xsd/siri.xsd @@ -1,531 +1,531 @@ - - - - - - main schema - e-service developers - - Dipl.-Kfm. Winfried Bruns, Verband Deutscher, Köln, de v1.0 - Mark Cartwright, Centaur Consulting Limited, Guildford, uk v1.0 - Christophe Duquesne, PDG Consultant en systémes, Dryade Guyancourt, fr v1.0 - Stefan Fjällemark, HUR - Hovedstadens, Valby, dk v1.0 - Jonas Jäderberg, Columna, Borlänge, fi v1.0 - Dipl.-Ing. Sven Juergens psitrans juergens@psitrans.de v1.0 - Nicholas Knowles, KIZOOM Limited, London EC4A 1LT, uk v1.0 - Werner Kohl, Mentz Datenverarbeitung GmbH, München,de v1.0 - Peter Miller, ACIS Research and Development, Cambridge CB4 0DL, uk v1.0 - Dr. Martin Siczkowski, West Yorkshire PTE, Leeds, uk v1.0 - Gustav Thiessen BLIC thi@BLIC.DE, de v1.0 - Dr Bartak, bartak@apex-jesenice.cz v1.0 - Dr. Franz-Josef Czuka, Beratungsgesellschaft für, Düsseldorf, de v1.0 - Dr.-Ing. Klaus-Peter Heynert, PSI Transportation GmbH, Berlin, de v1.0 - Jean-Laurant Franchineau, CONNEX-EUROLUM, PARIS, fr v1.0 - Dipl.-Ing. (FH) Rainer Ganninger, init innovation in, Karlsruhe, de v1.0 - Dipl.-Ing. HTL Peter Machalek, Siemens Transit, Neuhausen am Rheinfall, ch v1.0 - El Ing. Ernst Pfister, Siemens Transit, Neuhausen am Rheinfall, ch v1.0 - Dipl.-Ing. Berthold Radermacher, Verband Deutscher, Köln, de v1.0 - Dr. Friedemann Weik, Hamburger Berater Team GmbH, Hamburg, de v1.0 - - Robin Vettier, ixxi.com, fr v1.3 - Ofer Porat, fr v1.3 - Burt Alexander', sigtec.com - Michelle Etienne, Dryade, Paris fr, v1.3 - Brian Ferris onebusaway.org, us, v1.3 - Manuem Mahne Siemens.com - - Ulf Bjersing, Hogia - Stenungsgrund, se v2.0 - Dipl.-Math Christoph Blendinger, DB, Frankfort, de v2.0 - Dipl.-Kfm. Winfried Bruns, Verband Deutscher, Köln, de v2.0 - Christophe Duquesne, PDG Consultant en systémes, Auriga, fr v2.0 - Gerald Dury, Trapeze Neuhausen am Rhein, ch, fr v2.0 - Michelle Etienne, Dryade, Paris fr v2.0 - Michael Frumin, MTA, us, v2.0 - Nicholas Knowles, Trapeze Limited, London, uk v2.0 - Werner Kohl, Mentz Datenverarbeitung GmbH, München, de v2.0 - Davide Lallouche, RATP, Paris, fr v2.0 - Jeff Maki, us, v2.0 - Daniel Rubli, Trapeze Neuhausen am Rhein, ch, fr v2.0 - Gustav Thiessen BLIC thi@BLIC.DE, de 2.0 v1.0 - Europe - >Drafted for version 1.0 & Version 2.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. -mailto:schemer@siri.org.uk - - 2004-09-29 - - - 2004-10-01 - - - 2005-02-14 - - - 2005-02-20 - - - 2005-05-11 - - - 2007-02-02 - - 2007-04-17 - Name Space changes - - 2008-11-17 - Change to use common 1_2. Add in mussing StopMonitoringMultipelRequest - Rename groups to identify common SIRI elements - - 2009-03-03 - Corrrect cardinality on facility and Service Monitoring Delivery request - - 2011-04-18 - Updated journey, request and other subpackages - see readme - - 2012-03-23 - SIRI Version 2.0 - Model subpackages Refactored to improve modularisation. - [SIRI-LITE] Add authentication Key - See Readme.txt for list of changes - - 2012-05-18 - SIRI Version 2.0 - Correct error in SituationExchangeCapabilitiesReponse include - - 2012-08-01 - SIRI Version 2.0 - Correct delegation elements - - 2014-03-31 - +SIRI v2.0 Comments - - Add terminate subscription notification - - -

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

      -

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

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

      -

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

      -

      SIRI includes common mechanisms and messages for system status management.

      -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/}siri.xsd - [ISO 639-2/B] ENG - Kizoom Software Ltd 16 High Holborn, London WC1V 6BX - - http://www.siri.org.uk/schema/2.0/xsd/siri__common_services.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__estimatedTimetable_service.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__productionTimetable_service.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__stopMonitoring_service.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__vehicleMonitoring_service.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__connectionTimetable_service.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__connectionMonitoring_service.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__generalMessage_service.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__discovery.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__situationExchange_service.xsd - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.0 Version with cumulative fixes - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport. - - CEN TC278 WG3 SG7 - - SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. - Standard -       -       - SIRI Service Interface for Real-time Information relating to Public Transport Operations. - XML Schema with explicit functional services -       - - - - - - - SIRI Service Interface for Real-time Operation. - - - - - - - - - - - - - - SIRI All Requests. - - - - - - - - - - - - Request from Consumer to Producer for immediate delivery of data. Answered with a ServiceDelivery (or a DataReadyRequest) - - - - - - - - - - Requests for service provision. - - - - - - - - - - SIRI Service Request. - - - - - - - - - - SIRI Functional Service Concrete Requests. - - - - - - - - - - - - - - - - - - - Request from Subscriber to Producer for a subscription. Answered with a SubscriptionResponse. - - - - - - - - - - - Type for SIRI Subscription Request. - - - - - - - - - - - - Type for SIRI Functional Service Subscription types. Used for WSDL exchanges. - - - - - - - - SIRI Functional Service Subscription types. For a given SubscriptionRequest, must all be of the same service type. - - - - - - - - - - - - - - - - - - SIRI Service Responses. - - - - - - - - - - - Responses to requests other than deliveries and status information. - - - - - - - - - - - Responses that deliver payload content. - - - - - - - - - - - Response from Producer to Consumer to deliver payload data. Either answers a direct ServiceRequest, or asynchronously satisfies a subscription. May be sent directly in one step, or fetched in response to a DataSupply Request. - - - - - - - - - - Type for SIRI Service Delivery. - - - - - - - - - Default gml coordinate format for eny location elements in response; applies if Coordinates element is used to specify points. May be overridden on individual points. - - - - - - - - Type for SIRI Service Delivery Body.. - - - - - - - Default gml coordinate format for eny location elements in response; applies if Coordinates element is used to specify points. May be overridden on individual points. - - - - - - Elements for SIRI Service Delivery. - - - - - - Whether there is a further delivery message with more current updates that follows this one. Default is 'false'. - - - - - - - - Type for a SIRI SIRI Functional Service Delivery types.Used for WSDL. - - - - - - - - SIRI Functional Service Delivery types. - - - - - - - - - - - Delivery for Stop Event service. - - - - - Delivery for Vehicle Activity Service. - - - - - - Delivery for Connection Protection Fetcher Service. - - - - - Delivery for Connection Protection Fetcher Service. - - - - - Delivery for general Message service. - - - - - - - - - - - - Requests for reference data for use in SIRI Functional Service requests. - - - - - - - - - Responses with reference data for use in SIRI Functional Service requests. - - - - - Responses with the capabilities of an implementation. Answers a CapabilityRequest. - - - - - - - - - - Requests a the current capabilities of the server. Answred with a CpabailitiesResponse. - - - - - Type for Requests for capabilities of the current system. - - - - - - - Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. - - - - - - If request has been proxied by an intermediate aggregating system, tracking information relating to the original requestor. This allows the aggregation to be stateless - - - - - - - - - - - Defines the capabilities of an individual SIRI service request functions. - - - - - - - - - - - - - - - - - - Responses with the capabilities of an implementation. - - - - - Type for the capabilities of an implementation. - - - - - - - - - - - - - Defines the capabilities of an individual SIRI service response functions. - - - - - - - - - - - - - - - -       + + + + + + main schema + e-service developers + + Dipl.-Kfm. Winfried Bruns, Verband Deutscher, Köln, de v1.0 + Mark Cartwright, Centaur Consulting Limited, Guildford, uk v1.0 + Christophe Duquesne, PDG Consultant en systémes, Dryade Guyancourt, fr v1.0 + Stefan Fjällemark, HUR - Hovedstadens, Valby, dk v1.0 + Jonas Jäderberg, Columna, Borlänge, fi v1.0 + Dipl.-Ing. Sven Juergens psitrans juergens@psitrans.de v1.0 + Nicholas Knowles, KIZOOM Limited, London EC4A 1LT, uk v1.0 + Werner Kohl, Mentz Datenverarbeitung GmbH, München,de v1.0 + Peter Miller, ACIS Research and Development, Cambridge CB4 0DL, uk v1.0 + Dr. Martin Siczkowski, West Yorkshire PTE, Leeds, uk v1.0 + Gustav Thiessen BLIC thi@BLIC.DE, de v1.0 + Dr Bartak, bartak@apex-jesenice.cz v1.0 + Dr. Franz-Josef Czuka, Beratungsgesellschaft für, Düsseldorf, de v1.0 + Dr.-Ing. Klaus-Peter Heynert, PSI Transportation GmbH, Berlin, de v1.0 + Jean-Laurant Franchineau, CONNEX-EUROLUM, PARIS, fr v1.0 + Dipl.-Ing. (FH) Rainer Ganninger, init innovation in, Karlsruhe, de v1.0 + Dipl.-Ing. HTL Peter Machalek, Siemens Transit, Neuhausen am Rheinfall, ch v1.0 + El Ing. Ernst Pfister, Siemens Transit, Neuhausen am Rheinfall, ch v1.0 + Dipl.-Ing. Berthold Radermacher, Verband Deutscher, Köln, de v1.0 + Dr. Friedemann Weik, Hamburger Berater Team GmbH, Hamburg, de v1.0 + + Robin Vettier, ixxi.com, fr v1.3 + Ofer Porat, fr v1.3 + Burt Alexander', sigtec.com + Michelle Etienne, Dryade, Paris fr, v1.3 + Brian Ferris onebusaway.org, us, v1.3 + Manuem Mahne Siemens.com + + Ulf Bjersing, Hogia - Stenungsgrund, se v2.0 + Dipl.-Math Christoph Blendinger, DB, Frankfort, de v2.0 + Dipl.-Kfm. Winfried Bruns, Verband Deutscher, Köln, de v2.0 + Christophe Duquesne, PDG Consultant en systémes, Auriga, fr v2.0 + Gerald Dury, Trapeze Neuhausen am Rhein, ch, fr v2.0 + Michelle Etienne, Dryade, Paris fr v2.0 + Michael Frumin, MTA, us, v2.0 + Nicholas Knowles, Trapeze Limited, London, uk v2.0 + Werner Kohl, Mentz Datenverarbeitung GmbH, München, de v2.0 + Davide Lallouche, RATP, Paris, fr v2.0 + Jeff Maki, us, v2.0 + Daniel Rubli, Trapeze Neuhausen am Rhein, ch, fr v2.0 + Gustav Thiessen BLIC thi@BLIC.DE, de 2.0 v1.0 + Europe + >Drafted for version 1.0 & Version 2.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. +mailto:schemer@siri.org.uk + + 2004-09-29 + + + 2004-10-01 + + + 2005-02-14 + + + 2005-02-20 + + + 2005-05-11 + + + 2007-02-02 + + 2007-04-17 + Name Space changes + + 2008-11-17 + Change to use common 1_2. Add in mussing StopMonitoringMultipelRequest + Rename groups to identify common SIRI elements + + 2009-03-03 + Corrrect cardinality on facility and Service Monitoring Delivery request + + 2011-04-18 + Updated journey, request and other subpackages - see readme + + 2012-03-23 + SIRI Version 2.0 + Model subpackages Refactored to improve modularisation. + [SIRI-LITE] Add authentication Key + See Readme.txt for list of changes + + 2012-05-18 + SIRI Version 2.0 + Correct error in SituationExchangeCapabilitiesReponse include + + 2012-08-01 + SIRI Version 2.0 + Correct delegation elements + + 2014-03-31 + +SIRI v2.0 Comments + - Add terminate subscription notification + + +

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

      +

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

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

      +

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

      +

      SIRI includes common mechanisms and messages for system status management.

      +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}siri.xsd + [ISO 639-2/B] ENG + Kizoom Software Ltd 16 High Holborn, London WC1V 6BX + + http://www.siri.org.uk/schema/2.0/xsd/siri__common_services.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__estimatedTimetable_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__productionTimetable_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__stopMonitoring_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__vehicleMonitoring_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__connectionTimetable_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__connectionMonitoring_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__generalMessage_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__discovery.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__situationExchange_service.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG XML and Trident standards.
        • +
      + + Version 2.0 Version with cumulative fixes + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport. + + CEN TC278 WG3 SG7 + + SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. + Standard +       +       + SIRI Service Interface for Real-time Information relating to Public Transport Operations. - XML Schema with explicit functional services +       + + + + + + + SIRI Service Interface for Real-time Operation. + + + + + + + + + + + + + + SIRI All Requests. + + + + + + + + + + + + Request from Consumer to Producer for immediate delivery of data. Answered with a ServiceDelivery (or a DataReadyRequest) + + + + + + + + + + Requests for service provision. + + + + + + + + + + SIRI Service Request. + + + + + + + + + + SIRI Functional Service Concrete Requests. + + + + + + + + + + + + + + + + + + + Request from Subscriber to Producer for a subscription. Answered with a SubscriptionResponse. + + + + + + + + + + + Type for SIRI Subscription Request. + + + + + + + + + + + + Type for SIRI Functional Service Subscription types. Used for WSDL exchanges. + + + + + + + + SIRI Functional Service Subscription types. For a given SubscriptionRequest, must all be of the same service type. + + + + + + + + + + + + + + + + + + SIRI Service Responses. + + + + + + + + + + + Responses to requests other than deliveries and status information. + + + + + + + + + + + Responses that deliver payload content. + + + + + + + + + + + Response from Producer to Consumer to deliver payload data. Either answers a direct ServiceRequest, or asynchronously satisfies a subscription. May be sent directly in one step, or fetched in response to a DataSupply Request. + + + + + + + + + + Type for SIRI Service Delivery. + + + + + + + + + Default gml coordinate format for eny location elements in response; applies if Coordinates element is used to specify points. May be overridden on individual points. + + + + + + + + Type for SIRI Service Delivery Body.. + + + + + + + Default gml coordinate format for eny location elements in response; applies if Coordinates element is used to specify points. May be overridden on individual points. + + + + + + Elements for SIRI Service Delivery. + + + + + + Whether there is a further delivery message with more current updates that follows this one. Default is 'false'. + + + + + + + + Type for a SIRI SIRI Functional Service Delivery types.Used for WSDL. + + + + + + + + SIRI Functional Service Delivery types. + + + + + + + + + + + Delivery for Stop Event service. + + + + + Delivery for Vehicle Activity Service. + + + + + + Delivery for Connection Protection Fetcher Service. + + + + + Delivery for Connection Protection Fetcher Service. + + + + + Delivery for general Message service. + + + + + + + + + + + + Requests for reference data for use in SIRI Functional Service requests. + + + + + + + + + Responses with reference data for use in SIRI Functional Service requests. + + + + + Responses with the capabilities of an implementation. Answers a CapabilityRequest. + + + + + + + + + + Requests a the current capabilities of the server. Answred with a CpabailitiesResponse. + + + + + Type for Requests for capabilities of the current system. + + + + + + + Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. + + + + + + If request has been proxied by an intermediate aggregating system, tracking information relating to the original requestor. This allows the aggregation to be stateless + + + + + + + + + + + Defines the capabilities of an individual SIRI service request functions. + + + + + + + + + + + + + + + + + + Responses with the capabilities of an implementation. + + + + + Type for the capabilities of an implementation. + + + + + + + + + + + + + Defines the capabilities of an individual SIRI service response functions. + + + + + + + + + + + + + + + +       diff --git a/xsd/siri/siri_all_framework.xsd b/xsd/siri/siri_all_framework.xsd index f1b3f959..dfa55d89 100644 --- a/xsd/siri/siri_all_framework.xsd +++ b/xsd/siri/siri_all_framework.xsd @@ -1,12 +1,12 @@ - - - - - - - - - + + + + + + + + + diff --git a/xsd/siri/siri_base.xsd b/xsd/siri/siri_base.xsd index 853e6564..8f002003 100644 --- a/xsd/siri/siri_base.xsd +++ b/xsd/siri/siri_base.xsd @@ -1,315 +1,315 @@ - - - - - - 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 Limited, 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 - - 2012-06-17 - - - - 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 that 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/schema/2.0/xsd/}siri.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri__common_services.xsd - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport. - - CEN TC278 WG3 SG7 - - SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations Generic base schema. - Standard -       -       - SIRI Common Request Fra,mework -       - - - - - - - - - - - - - - - SIRI Requests. - - - - - - - - - - - Requests for service provision. - - - - - - - - - - - Request from Consumer to Producer for immediate delivery of data. Answered with a ServiceDelivery (or a DataReadyRequest) - - - - - - - - - - - - - - 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. - - - - - - - - - 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. - - - - - - Elements 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. - - - - - - - - - - -       + + + + + + 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 Limited, 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 + + 2012-06-17 + + + + 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 that 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/schema/2.0/xsd/}siri.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri__common_services.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG XML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport. + + CEN TC278 WG3 SG7 + + SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations Generic base schema. + Standard +       +       + SIRI Common Request Fra,mework +       + + + + + + + + + + + + + + + SIRI Requests. + + + + + + + + + + + Requests for service provision. + + + + + + + + + + + Request from Consumer to Producer for immediate delivery of data. Answered with a ServiceDelivery (or a DataReadyRequest) + + + + + + + + + + + + + + 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. + + + + + + + + + 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. + + + + + + Elements 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/xsd/siri/siri_common_services.xsd b/xsd/siri/siri_common_services.xsd index 2014eeb9..e04f0893 100644 --- a/xsd/siri/siri_common_services.xsd +++ b/xsd/siri/siri_common_services.xsd @@ -1,900 +1,900 @@ - - - - - - main schema - e-service developers - CEN TC278 WG3 SG7 Team - Europe - First drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2004-09-29 - - - 2005-02-14 - - - 2005-02-20 - - - 2005-05-11 - - 2007-04-17 - - Name Space changes - - 2008-10-09 - -- Add Subscriber ref to TermninateSubscription Request - - 2008-11-17 - -- Revise for substitution groups and move down to siri subdirectory - - 2012-03-23 - +SIRI v2.0 - - Add DataReady to Check Status - - Add DistanceUnits and VelocityUnits to ServiceRequestContext - - [FR] Add Extensions tag to Terminate SubscriptionRequest - - 2014-03-31 - +SIRI v2.0 Comments - - Add terminate subscription notification - - 2014-06-23 - +SIRI v2.0 Comments - - Revise terminate subscription erroc condition to be consistent with other services - - -

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

      -

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

      -

      It contains the following request

      -
        -
      • GS: Terminate Subscription Resquest
        • -
      • GS: Terminate Subscription Response
        • -
      • GS: Subscription Response
        • -
      • GS: Data Ready Notification
        • -
      • GS: Data Ready Acknowledgement
        • -
      • GS: Data Supply Request
        • -
      • GS: Data Received Response
        • -
      • GS: Check Status Request
        • -
      • GS: Check Status Response
        • -
      • GS: Heartbeat Request
        • -
      -

      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/schema/2.0/xsd/siri/}siri_common_services.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI XML schema. Service Interface for Real-time Information. Common Requests - Standard -       -       - SIRI Framework - Common Requests. -       - - - - - - - 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. - - - - - - - - - - - Address elements 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. - - - - - - - Address elements 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 is ' 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 languages 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. - - - - - - Units for Distance Type. Default is metres. +SIRI v2.0 - - - - - Units for Distance Type. Default is metres per second. +SIRI v2.0 - - - - - - - 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 a subscription or subscriptions. - - - - - - - - If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 - - - - - - - - - - - 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. - - - - - - - - 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. - - - - - - - - - - - - Type for Status of termination response. - - - - - - - - - Description of any error or warning condition. - - - - - - - - - - - - Text description of error. - - - - - - - - - - - Notification from Subscriber to Subscription Manager to terminate a subscription. - - - - - Type for Notification to terminate a subscription or subscriptions. - - - - - - - - Text description providing additional information about the reason for the subscription termination. - - - - - - - - - - - Responses that infrom about the service status. - - - - - - - - Type for Response Status. - - - - - - - - - - Description of any error or warning condition. - - - - - - - - - - Contains infromation about the processing of a an individual service subscription - either success info or an error condition. (VDV Acknowledgement). - - - - - - 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. - - - - - - - - - General requests for fetched data delivery. - - - - - - - - - - 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. - - - - - - - - - - - - - - - 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. - - - - - - - - - - - - Specifies content to be included in data supply. - - - - - Reference to a 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. - - - - - - - - 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. - - - - - - - - - - - - Elements identifying data Consumer, i.e. requestor, if synchronous delivery or subscriber if asynchronous. - - - - - - Reference to an arbitrary unique reference associated with the request which gave rise to this response. - - - - - - - - Request from Consumer to Producer to check whether services is working. Answers a CheckStatusRequest. - - - - - Type for check status request. - - - - - - - - - Version number of request. - - - - - - - - - Data received AcknowledgementService Status Check Request content. - - - - - - Whether data delivery is ready to be fetched SIRI v 2.0 - - - - - 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. - - - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + First drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2004-09-29 + + + 2005-02-14 + + + 2005-02-20 + + + 2005-05-11 + + 2007-04-17 + - Name Space changes + + 2008-10-09 + -- Add Subscriber ref to TermninateSubscription Request + + 2008-11-17 + -- Revise for substitution groups and move down to siri subdirectory + + 2012-03-23 + +SIRI v2.0 + - Add DataReady to Check Status + - Add DistanceUnits and VelocityUnits to ServiceRequestContext + - [FR] Add Extensions tag to Terminate SubscriptionRequest + + 2014-03-31 + +SIRI v2.0 Comments + - Add terminate subscription notification + + 2014-06-23 + +SIRI v2.0 Comments + - Revise terminate subscription erroc condition to be consistent with other services + + +

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

      +

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

      +

      It contains the following request

      +
        +
      • GS: Terminate Subscription Resquest
        • +
      • GS: Terminate Subscription Response
        • +
      • GS: Subscription Response
        • +
      • GS: Data Ready Notification
        • +
      • GS: Data Ready Acknowledgement
        • +
      • GS: Data Supply Request
        • +
      • GS: Data Received Response
        • +
      • GS: Check Status Request
        • +
      • GS: Check Status Response
        • +
      • GS: Heartbeat Request
        • +
      +

      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/schema/2.0/xsd/siri/}siri_common_services.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG XML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI XML schema. Service Interface for Real-time Information. Common Requests + Standard +       +       + SIRI Framework - Common Requests. +       + + + + + + + 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. + + + + + + + + + + + Address elements 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. + + + + + + + Address elements 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 is ' 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 languages 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. + + + + + + Units for Distance Type. Default is metres. +SIRI v2.0 + + + + + Units for Distance Type. Default is metres per second. +SIRI v2.0 + + + + + + + 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 a subscription or subscriptions. + + + + + + + + If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 + + + + + + + + + + + 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. + + + + + + + + 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. + + + + + + + + + + + + Type for Status of termination response. + + + + + + + + + Description of any error or warning condition. + + + + + + + + + + + + Text description of error. + + + + + + + + + + + Notification from Subscriber to Subscription Manager to terminate a subscription. + + + + + Type for Notification to terminate a subscription or subscriptions. + + + + + + + + Text description providing additional information about the reason for the subscription termination. + + + + + + + + + + + Responses that infrom about the service status. + + + + + + + + Type for Response Status. + + + + + + + + + + Description of any error or warning condition. + + + + + + + + + + Contains infromation about the processing of a an individual service subscription - either success info or an error condition. (VDV Acknowledgement). + + + + + + 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. + + + + + + + + + General requests for fetched data delivery. + + + + + + + + + + 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. + + + + + + + + + + + + + + + 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. + + + + + + + + + + + + Specifies content to be included in data supply. + + + + + Reference to a 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. + + + + + + + + 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. + + + + + + + + + + + + Elements identifying data Consumer, i.e. requestor, if synchronous delivery or subscriber if asynchronous. + + + + + + Reference to an arbitrary unique reference associated with the request which gave rise to this response. + + + + + + + + Request from Consumer to Producer to check whether services is working. Answers a CheckStatusRequest. + + + + + Type for check status request. + + + + + + + + + Version number of request. + + + + + + + + + Data received AcknowledgementService Status Check Request content. + + + + + + Whether data delivery is ready to be fetched SIRI v 2.0 + + + + + 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/xsd/siri/siri_request_errorConditions.xsd b/xsd/siri/siri_request_errorConditions.xsd index e8e678bf..c1505496 100644 --- a/xsd/siri/siri_request_errorConditions.xsd +++ b/xsd/siri/siri_request_errorConditions.xsd @@ -1,590 +1,590 @@ - - - - - - - - - main schema - e-service developers - CEN TC278 WG3 SG7 Team - Europe - First drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2012-03-24 - - - - 2009-03-31 - - - - 2011-04-18 - - - - 2012-03-23 - - - -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri/}siri_requests_errorConditions.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri_uility/siri_types.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_uility/siri_participant.xsd - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIGXML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI XML schema. Common Request Error Conditions - Standard -       -       - SIRI Framework Error COnditions. -       - - - - Description of error or warning condition associated with response. - - - - - Type for RequestErrorCondition. - - - - - - - - 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. - - - - - - - - Element fror an erroc condition (for use in WSDL.) - - - - - Type for Standard ErrorConditions for Service request. - - - - - - - - - Text description of error. - - - - - - - Type for Description of an error. - - - - - - - - - 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. - - - - - - Error code number associated with 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. - - - - - - - - - - Errors that may arise in the execution of a delegated distribution request. +SIRI v2.0 - - - - - - Error: Recipient for a message to be distributed is unknown. I.e. delegatior is found, but +SIRI v2.0 - - - - - - - - - - - Error:Recipient of a message to be distributed is not available. +SIRI v2.0 - - - - - Type for Error: UnapprovedKey +SIRI v2.0 - - - - - - - User key. - - - - - - - - - - Error: Recipient for a message to be distributed is unknown. +SIRI v2.0 - - - - - Type for Error: Unknown Participant. +SIRI v2.0 - - - - - - - Reference to Participant who is unknown. + SIRI v2.0 - - - - - - - - - - Error: Recipient for a message to be distributed is unknown. +SIRI v2.0 - - - - - Type for Error: Unknown Endpoint +SIRI v2.0 - - - - - - - Endpoint that is noit known. + SIRI v2.0 - - - - - - - - - - Error:Endpoint to which a message is to be distributed did not allow access by the cloient. +SIRI v2.0 - - - - - Type for Error: EndpointDeniedAccess +SIRI v2.0 - - - - - - - Endpoint that was denied access + SIRI v2.0 - - - - - - - - - - Error:Recipient of a message to be distributed is not available. +SIRI v2.0 - - - - - Type for Error: EndpointNotAvailable +SIRI v2.0 - - - - - - - Endpoint that is noit available. + SIRI v2.0 - - - - - - - - - - - Errors that may arise in the execution of a request. - - - - - - - - - Error: Data period or subscription period is outside of period covered by service. +SIRI v2.0. - - - - - - - Error: Request contained extensions that were not supported by the producer. A response has been provided but some or all extensions have been ignored. +SIRI v2.0. - - - - - - - - - - Error: Functional service is not available to use (but it is still capable of giving this response). - - - - - Type for Service Not Available error. - - - - - - - Expected time fro reavailability of servcie. +SIRI v2.0 - - - - - - - - - - Error: Service does not support the 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:Access Not Allowed. - - - - - - - - - Error: Valid request was made but service does not hold any data for the requested topic. expression. - - - - - Type for Error: No Info for Topic - - - - - - - - - Error: Request contains references to identifiers that are not known. +SIRI v2.0. - - - - - Type for InvalidDataReferencesError:. +SIRI v2.0. - - - - - - - Invalid reference values encoountered. - - - - - - - - - - Error: Request contained parameters that were not supported by the producer. A response has been provided but some parameters have been ignored. +SIRI v2.0. - - - - - Type for Parameters Ignored Error:. +SIRI v2.0. - - - - - - - Name of the unsupported parameter. - - - - - - - - - - Error: Request contained extensions that were not supported by the producer. A response has been provided but some or all extensions have been ignored.. +SIRI v2.0. - - - - - Type for Unknown Extensions Error:. +SIRI v2.0. - - - - - - - Name of the unknown encountered extensions. - - - - - - - - - - Error: Valid request was made but request would exceed the permitted resource usage of the client. - - - - - Type for error. AllowedResourceUsageExceeded. - - - - - - - - - - - Error: Subscriber not found. - - - - - Type for Error: Subscriber not found. - - - - - - - Id of capabiliuty that is noit supported. + SIRI v2.0 - - - - - - - - - - - Error: Subscription not found. - - - - - Type for Error: Subscription not found. - - - - - - - Ubscription code that could not be found. + SIRI v2.0 - - - - - - - - - - Error: Error type other than the well defined codes. - - - - - Type for error. - - - - - - -       + + + + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + First drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2012-03-24 + + + + 2009-03-31 + + + + 2011-04-18 + + + + 2012-03-23 + + + +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/siri/}siri_requests_errorConditions.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri_uility/siri_types.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_uility/siri_participant.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIGXML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI XML schema. Common Request Error Conditions + Standard +       +       + SIRI Framework Error COnditions. +       + + + + Description of error or warning condition associated with response. + + + + + Type for RequestErrorCondition. + + + + + + + + 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. + + + + + + + + Element fror an erroc condition (for use in WSDL.) + + + + + Type for Standard ErrorConditions for Service request. + + + + + + + + + Text description of error. + + + + + + + Type for Description of an error. + + + + + + + + + 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. + + + + + + Error code number associated with 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. + + + + + + + + + + Errors that may arise in the execution of a delegated distribution request. +SIRI v2.0 + + + + + + Error: Recipient for a message to be distributed is unknown. I.e. delegatior is found, but +SIRI v2.0 + + + + + + + + + + + Error:Recipient of a message to be distributed is not available. +SIRI v2.0 + + + + + Type for Error: UnapprovedKey +SIRI v2.0 + + + + + + + User key. + + + + + + + + + + Error: Recipient for a message to be distributed is unknown. +SIRI v2.0 + + + + + Type for Error: Unknown Participant. +SIRI v2.0 + + + + + + + Reference to Participant who is unknown. + SIRI v2.0 + + + + + + + + + + Error: Recipient for a message to be distributed is unknown. +SIRI v2.0 + + + + + Type for Error: Unknown Endpoint +SIRI v2.0 + + + + + + + Endpoint that is noit known. + SIRI v2.0 + + + + + + + + + + Error:Endpoint to which a message is to be distributed did not allow access by the cloient. +SIRI v2.0 + + + + + Type for Error: EndpointDeniedAccess +SIRI v2.0 + + + + + + + Endpoint that was denied access + SIRI v2.0 + + + + + + + + + + Error:Recipient of a message to be distributed is not available. +SIRI v2.0 + + + + + Type for Error: EndpointNotAvailable +SIRI v2.0 + + + + + + + Endpoint that is noit available. + SIRI v2.0 + + + + + + + + + + + Errors that may arise in the execution of a request. + + + + + + + + + Error: Data period or subscription period is outside of period covered by service. +SIRI v2.0. + + + + + + + Error: Request contained extensions that were not supported by the producer. A response has been provided but some or all extensions have been ignored. +SIRI v2.0. + + + + + + + + + + Error: Functional service is not available to use (but it is still capable of giving this response). + + + + + Type for Service Not Available error. + + + + + + + Expected time fro reavailability of servcie. +SIRI v2.0 + + + + + + + + + + Error: Service does not support the 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:Access Not Allowed. + + + + + + + + + Error: Valid request was made but service does not hold any data for the requested topic. expression. + + + + + Type for Error: No Info for Topic + + + + + + + + + Error: Request contains references to identifiers that are not known. +SIRI v2.0. + + + + + Type for InvalidDataReferencesError:. +SIRI v2.0. + + + + + + + Invalid reference values encoountered. + + + + + + + + + + Error: Request contained parameters that were not supported by the producer. A response has been provided but some parameters have been ignored. +SIRI v2.0. + + + + + Type for Parameters Ignored Error:. +SIRI v2.0. + + + + + + + Name of the unsupported parameter. + + + + + + + + + + Error: Request contained extensions that were not supported by the producer. A response has been provided but some or all extensions have been ignored.. +SIRI v2.0. + + + + + Type for Unknown Extensions Error:. +SIRI v2.0. + + + + + + + Name of the unknown encountered extensions. + + + + + + + + + + Error: Valid request was made but request would exceed the permitted resource usage of the client. + + + + + Type for error. AllowedResourceUsageExceeded. + + + + + + + + + + + Error: Subscriber not found. + + + + + Type for Error: Subscriber not found. + + + + + + + Id of capabiliuty that is noit supported. + SIRI v2.0 + + + + + + + + + + + Error: Subscription not found. + + + + + Type for Error: Subscription not found. + + + + + + + Ubscription code that could not be found. + SIRI v2.0 + + + + + + + + + + Error: Error type other than the well defined codes. + + + + + Type for error. + + + + + + +       diff --git a/xsd/siri/siri_request_support.xsd b/xsd/siri/siri_request_support.xsd index 7c026811..53093910 100644 --- a/xsd/siri/siri_request_support.xsd +++ b/xsd/siri/siri_request_support.xsd @@ -1,210 +1,210 @@ - - - - - - - main schema - e-service developers - CEN TC278 WG3 SG7 Team - Europe - First drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2012-03-29 - - - 2012-03-23 - - - -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri/}siri_request_support.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the SIRI 1.0 standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI XML schema. Common Request identifier types - Standard -       -       - SIRI Common Framework basic identifier types. -       - - - - - Unique identifier of a message within SIRI functional service type and participant. - - - - - - - - Type for reference to a message. - - - - - - - - Type for unique identifier of Subscription within Participant. - - - - - - - - Type for reference to a subscription. - - - - - - - - Type for unique identifier of Subscription filter within Participant. - - - - - - - - Type for unique identifier of Subscription filter within Participant. - - - - - - - - - Timestamp on request. - - - - - Reference to a requestor - Participant Code. - - - - - Type for a endpoint. - - - - - - Time individual response element was created. - - - - - - Type for identifier of an Item. A transient reference for efficient handling of events. - - - - - - Type for reference to an Item. - - - - - - - - - Whether additional translations of text names are to be included in elements. If 'false', then only one element should be returned. Default is 'false'. -Where multiple values are returned The first element returned will be used as the default value. - - - - - Whether SERVICE JOURNEY INTERCHANGE data is to be transmitted or not. Default is 'true'. +SIRI v2.1 - - - - - Whether JOURNEY RELATION data is to be transmitted or not. Default is 'true'. +SIRI v2.1 - - - - - Whether TRAIN (ELEMENT), COMPOUND TRAIN and TRAIN STOP ASSIGNMENT data is to be transmitted or not. Default is 'true'. +SIRI v2.1 - - - - - - Type for capability ref. - - - - - - - - Type for capability code. - - - - - - - Enumeration of communications transport method usage. - - - - - - - - - - - - - Enumeration of compression usage. - - - - - - - -       + + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + First drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2012-03-29 + + + 2012-03-23 + + + +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/siri/}siri_request_support.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the SIRI 1.0 standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI XML schema. Common Request identifier types + Standard +       +       + SIRI Common Framework basic identifier types. +       + + + + + Unique identifier of a message within SIRI functional service type and participant. + + + + + + + + Type for reference to a message. + + + + + + + + Type for unique identifier of Subscription within Participant. + + + + + + + + Type for reference to a subscription. + + + + + + + + Type for unique identifier of Subscription filter within Participant. + + + + + + + + Type for unique identifier of Subscription filter within Participant. + + + + + + + + + Timestamp on request. + + + + + Reference to a requestor - Participant Code. + + + + + Type for a endpoint. + + + + + + Time individual response element was created. + + + + + + Type for identifier of an Item. A transient reference for efficient handling of events. + + + + + + Type for reference to an Item. + + + + + + + + + Whether additional translations of text names are to be included in elements. If 'false', then only one element should be returned. Default is 'false'. +Where multiple values are returned The first element returned will be used as the default value. + + + + + Whether SERVICE JOURNEY INTERCHANGE data is to be transmitted or not. Default is 'true'. +SIRI v2.1 + + + + + Whether JOURNEY RELATION data is to be transmitted or not. Default is 'true'. +SIRI v2.1 + + + + + Whether TRAIN (ELEMENT), COMPOUND TRAIN and TRAIN STOP ASSIGNMENT data is to be transmitted or not. Default is 'true'. +SIRI v2.1 + + + + + + Type for capability ref. + + + + + + + + Type for capability code. + + + + + + + Enumeration of communications transport method usage. + + + + + + + + + + + + + Enumeration of compression usage. + + + + + + + +       diff --git a/xsd/siri/siri_requests.xsd b/xsd/siri/siri_requests.xsd index eddb38b4..023ba1f7 100644 --- a/xsd/siri/siri_requests.xsd +++ b/xsd/siri/siri_requests.xsd @@ -1,1072 +1,1072 @@ - - - - - - main schema - e-service developers - CEN TC278 WG3 SG7 Team - Europe - First drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 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 - - - - 2012-03-23 - - - - 2012-06-17 - - - - 2013-02-11 - - - -

      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/schema/2.0/xsd/siri/}siri_requests.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIGXML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry transport, -Roads and road transport - CEN TC278 WG3 SG7 - - SIRI XML schema. Common Request elements. - Standard -       -       - SIRI Common Request Framework. -       - - - - - - - - - Subsititutable type for a timestamped SIRI request. - - - - - Type for General SIRI Request. - - - - - - - - - Subsititutable type for an authenticated request Authenticated. - - - - - Type for Authticated SIRI Request. - - - - - - - - - - Elemenst for authecticiation. +SIRI v2.0 - - - - - Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . +SIRI v2.0 - - - - - Authentication key for request. May be used to authenticate requests from a particular account. +SIRI v2.0 - - - - - - - - Type for General SIRI Request. - - - - - - - - If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 - - - - - - - - - Elements relating to system that sent request. - - - - - 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 in subsequent interactions. - - - - - - - If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. - - - - - Address of original Consumer, i.e. requesting system to which delegating response is to be returned. +SIRI 2.0 - - - - - Identifier of delegating system that originated message. +SIRI 2.0 - - - - - - - - Subsititutable type for a SIRI request with requestor dteials tracked. - - - - - - Substitutable 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. - - - - - By using this element, the subscriber asks the data provider for an extension of the InitialTerminationTime of the subscription. -If SubscriptionRenewal is omitted, this request is to be treated as a re-subscription and therefore all data corresponding to the SubscriptionRequest must be sent in the initial response (or a portion of the data if MoreData is set to 'true'). +SIRI v2.1 - - - - - - - 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. Specific 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. - - - - - - - - If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 - - - - - - - - - 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. - - - - - - - - - - - If request has been proxied by an intermediate aggregating system, tracking information relating to the original requestor. This allows the aggregation to be stateless. - - - - - - - - - - - Common defaults. - - - - - Default language for text elements. - - - - - - - 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. - - - - - Reference to a Subscription 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. - - - - - Reference to a service subscription: unique within Service and Subscriber. - - - - - - - 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. - - - - - - - Whether the request was processed successfully or not. Default is 'true'. - - - - - - 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. - - - - - - - - If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 - - - - - - - - - Unique reference to this 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. - - - - - - - - If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 - - - - - - - - - - - Type for Unique reference to request to the producer. May be used to reference request in subsequent interactions. Used for WSDL. - - - - - - - - If request has been proxied by an intermediate aggregating system, tracking information relating to the original requestor. This allows the aggregation to be stateless. - - - - - - - - - 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 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. - - - - - - - - If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 - - - - - - - - - Unique reference to reponse from producer. May be used to reference request in subsequent interactions. - - - - - Unique identifier of Producer - Participant reference. - - - - - Endpoint Address to which acknowledgements to confirm delivery 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 an Activity. - - - - - Time at which data was recorded. - - - - - - - Type for an Activity that can be referenced. - - - - - - - Identifier of item. - - - - - - - - - Type for an Activity that can be referenced. - - - - - - - Identifier of item. - - - - - - - - - Type for an Activity that references a previous Activity. - - - - - - - Reference to an Activity Element of a delivery. - - - - - - - - - Type for an Activity that references a previous Activity. - - - - - - - Reference to an Activity Element of a delivery. - - - - - - - - - - - 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. - - - - - - - - If request has been proxied by an intermediate aggregating system, tracking information relating to the original requestor. This allows the aggregation to be stateless. - - - - - - - - - - - - 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 service supports Publish Subscribe Interaction. Default is 'true'. - - - - - - - - Delivery capabilities. - - - - - - Whether the service supports Direct delivery. - - - - - Whether the service 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. Default is ' false'. - - - - - Whether the service supports Delivery confirm. - - - - - Whether the 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. - - - - - Whether producer can provide multiple translations of NL text elements +SIRI 2.0 - - - - - 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 is ' true'. - - - - - Whether change threshold can be specified for updates. Default is 'true'. - - - - - - - - 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'. - - - - - - - - Abstract Discovery request. - - - - - Requests for stop reference data for use in service requests. - - - - - - - - - - - - Abstract type for a discovery delivery. - - - - - Abstract supertype fro discovery responses. - - - - - - - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + First drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 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 + + + + 2012-03-23 + + + + 2012-06-17 + + + + 2013-02-11 + + + +

      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/schema/2.0/xsd/siri/}siri_requests.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIGXML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry transport, +Roads and road transport + CEN TC278 WG3 SG7 + + SIRI XML schema. Common Request elements. + Standard +       +       + SIRI Common Request Framework. +       + + + + + + + + + Subsititutable type for a timestamped SIRI request. + + + + + Type for General SIRI Request. + + + + + + + + + Subsititutable type for an authenticated request Authenticated. + + + + + Type for Authticated SIRI Request. + + + + + + + + + + Elemenst for authecticiation. +SIRI v2.0 + + + + + Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . +SIRI v2.0 + + + + + Authentication key for request. May be used to authenticate requests from a particular account. +SIRI v2.0 + + + + + + + + Type for General SIRI Request. + + + + + + + + If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 + + + + + + + + + Elements relating to system that sent request. + + + + + 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 in subsequent interactions. + + + + + + + If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. + + + + + Address of original Consumer, i.e. requesting system to which delegating response is to be returned. +SIRI 2.0 + + + + + Identifier of delegating system that originated message. +SIRI 2.0 + + + + + + + + Subsititutable type for a SIRI request with requestor dteials tracked. + + + + + + Substitutable 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. + + + + + By using this element, the subscriber asks the data provider for an extension of the InitialTerminationTime of the subscription. +If SubscriptionRenewal is omitted, this request is to be treated as a re-subscription and therefore all data corresponding to the SubscriptionRequest must be sent in the initial response (or a portion of the data if MoreData is set to 'true'). +SIRI v2.1 + + + + + + + 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. Specific 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. + + + + + + + + If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 + + + + + + + + + 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. + + + + + + + + + + + If request has been proxied by an intermediate aggregating system, tracking information relating to the original requestor. This allows the aggregation to be stateless. + + + + + + + + + + + Common defaults. + + + + + Default language for text elements. + + + + + + + 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. + + + + + Reference to a Subscription 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. + + + + + Reference to a service subscription: unique within Service and Subscriber. + + + + + + + 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. + + + + + + + Whether the request was processed successfully or not. Default is 'true'. + + + + + + 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. + + + + + + + + If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 + + + + + + + + + Unique reference to this 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. + + + + + + + + If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 + + + + + + + + + + + Type for Unique reference to request to the producer. May be used to reference request in subsequent interactions. Used for WSDL. + + + + + + + + If request has been proxied by an intermediate aggregating system, tracking information relating to the original requestor. This allows the aggregation to be stateless. + + + + + + + + + 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 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. + + + + + + + + If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 + + + + + + + + + Unique reference to reponse from producer. May be used to reference request in subsequent interactions. + + + + + Unique identifier of Producer - Participant reference. + + + + + Endpoint Address to which acknowledgements to confirm delivery 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 an Activity. + + + + + Time at which data was recorded. + + + + + + + Type for an Activity that can be referenced. + + + + + + + Identifier of item. + + + + + + + + + Type for an Activity that can be referenced. + + + + + + + Identifier of item. + + + + + + + + + Type for an Activity that references a previous Activity. + + + + + + + Reference to an Activity Element of a delivery. + + + + + + + + + Type for an Activity that references a previous Activity. + + + + + + + Reference to an Activity Element of a delivery. + + + + + + + + + + + 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. + + + + + + + + If request has been proxied by an intermediate aggregating system, tracking information relating to the original requestor. This allows the aggregation to be stateless. + + + + + + + + + + + + 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 service supports Publish Subscribe Interaction. Default is 'true'. + + + + + + + + Delivery capabilities. + + + + + + Whether the service supports Direct delivery. + + + + + Whether the service 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. Default is ' false'. + + + + + Whether the service supports Delivery confirm. + + + + + Whether the 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. + + + + + Whether producer can provide multiple translations of NL text elements +SIRI 2.0 + + + + + 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 is ' true'. + + + + + Whether change threshold can be specified for updates. Default is 'true'. + + + + + + + + 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'. + + + + + + + + Abstract Discovery request. + + + + + Requests for stop reference data for use in service requests. + + + + + + + + + + + + Abstract type for a discovery delivery. + + + + + Abstract supertype fro discovery responses. + + + + + + + + + +       diff --git a/xsd/siriSg.xsd b/xsd/siriSg.xsd index cbd28b12..3e8933a2 100644 --- a/xsd/siriSg.xsd +++ b/xsd/siriSg.xsd @@ -1,149 +1,149 @@ - - - - - - main schema - e-service developers - - Dipl.-Kfm. Winfried Bruns, Verband Deutscher, Köln, de v1.0 - Mark Cartwright, Centaur Consulting Limited, Guildford, uk v1.0 - Christophe Duquesne, PDG Consultant en systémes, Dryade Guyancourt, fr v1.0 - Stefan Fjällemark, HUR - Hovedstadens, Valby, dk v1.0 - Jonas Jäderberg, Columna, Borlänge, fi v1.0 - Dipl.-Ing. Sven Juergens psitrans juergens@psitrans.de v1.0 - Nicholas Knowles, KIZOOM Limited, London EC4A 1LT, uk v1.0 - Werner Kohl, Mentz Datenverarbeitung GmbH, München,de v1.0 - Peter Miller, ACIS Research and Development, Cambridge CB4 0DL, uk v1.0 - Dr. Martin Siczkowski, West Yorkshire PTE, Leeds, uk v1.0 - Gustav Thiessen BLIC thi@BLIC.DE, de v1.0 - Dr Bartak, bartak@apex-jesenice.cz v1.0 - Dr. Franz-Josef Czuka, Beratungsgesellschaft für, Düsseldorf, de v1.0 - Dr.-Ing. Klaus-Peter Heynert, PSI Transportation GmbH, Berlin, de v1.0 - Jean-Laurant Franchineau, CONNEX-EUROLUM, PARIS, fr v1.0 - Dipl.-Ing. (FH) Rainer Ganninger, init innovation in, Karlsruhe, de v1.0 - Dipl.-Ing. HTL Peter Machalek, Siemens Transit, Neuhausen am Rheinfall, ch v1.0 - El Ing. Ernst Pfister, Siemens Transit, Neuhausen am Rheinfall, ch v1.0 - Dipl.-Ing. Berthold Radermacher, Verband Deutscher, Köln, de v1.0 - Dr. Friedemann Weik, Hamburger Berater Team GmbH, Hamburg, de v1.0 - - Robin Vettier, ixxi.com, fr v1.3 - Ofer Porat, fr v1.3 - Burt Alexander', sigtec.com - Michelle Etienne, Dryade, Paris fr, v1.3 - Brian Ferris onebusaway.org, us, v1.3 - Manuem Mahne Siemens.com - - Ulf Bjersing, Hogia - Stenungsgrund, se v2.0 - Dipl.-Math Christoph Blendinger, DB, Frankfort, de v2.0 - Dipl.-Kfm. Winfried Bruns, Verband Deutscher, Köln, de v2.0 - Christophe Duquesne, PDG Consultant en systémes, Auriga, fr v2.0 - Gerald Dury, Trapeze Neuhausen am Rhein, ch, fr v2.0 - Michelle Etienne, Dryade, Paris fr v2.0 - Michael Frumin, MTA, us, v2.0 - Nicholas Knowles, Trapeze Limited, London, uk v2.0 - Werner Kohl, Mentz Datenverarbeitung GmbH, München, de v2.0 - Davide Lallouche, RATP, Paris, fr v2.0 - Jeff Makkie, us, v2.0 - Daniel Rubli, Trapeze Neuhausen am Rhein, ch, fr v2.0 - Gustav Thiessen BLIC thi@BLIC.DE, de 2.0 v1.0 - Jeff Maki, openplans, us, v2.0 - Europe - >Drafted for version 1.0 & Version 2.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2008-11-17 - - - - 2008-04-18 - - - - 2009-03-30 - - - - 2011-04-18 - - - - 2012-03-23 - - - -

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

      -

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

      -

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

      -

      SIRI includes common mechanisms and messages for system status management.

      -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/}siriSg.xsd - [ISO 639-2/B] ENG - Kizoom Software Ltd 16 High Holborn, London WC1V 6BX - - http://www.siri.org.uk/schema/2.0/xsd/siri__base.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__allFunctionalServices.xsd - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      • Derived from the SIRI Version 1.0
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport. - - CEN TC278 WG3 SG7 - - SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Generic Substitution groups version - Standard -       -       - SIRI Service Interface for Real-time Information relating to Public Transport Operations. XML Schema with loosely coupled functional services, -       - - - - - - - - - - - Service Interface for Real-time Operation. - - - - - - - - - - - -       + + + + + + main schema + e-service developers + + Dipl.-Kfm. Winfried Bruns, Verband Deutscher, Köln, de v1.0 + Mark Cartwright, Centaur Consulting Limited, Guildford, uk v1.0 + Christophe Duquesne, PDG Consultant en systémes, Dryade Guyancourt, fr v1.0 + Stefan Fjällemark, HUR - Hovedstadens, Valby, dk v1.0 + Jonas Jäderberg, Columna, Borlänge, fi v1.0 + Dipl.-Ing. Sven Juergens psitrans juergens@psitrans.de v1.0 + Nicholas Knowles, KIZOOM Limited, London EC4A 1LT, uk v1.0 + Werner Kohl, Mentz Datenverarbeitung GmbH, München,de v1.0 + Peter Miller, ACIS Research and Development, Cambridge CB4 0DL, uk v1.0 + Dr. Martin Siczkowski, West Yorkshire PTE, Leeds, uk v1.0 + Gustav Thiessen BLIC thi@BLIC.DE, de v1.0 + Dr Bartak, bartak@apex-jesenice.cz v1.0 + Dr. Franz-Josef Czuka, Beratungsgesellschaft für, Düsseldorf, de v1.0 + Dr.-Ing. Klaus-Peter Heynert, PSI Transportation GmbH, Berlin, de v1.0 + Jean-Laurant Franchineau, CONNEX-EUROLUM, PARIS, fr v1.0 + Dipl.-Ing. (FH) Rainer Ganninger, init innovation in, Karlsruhe, de v1.0 + Dipl.-Ing. HTL Peter Machalek, Siemens Transit, Neuhausen am Rheinfall, ch v1.0 + El Ing. Ernst Pfister, Siemens Transit, Neuhausen am Rheinfall, ch v1.0 + Dipl.-Ing. Berthold Radermacher, Verband Deutscher, Köln, de v1.0 + Dr. Friedemann Weik, Hamburger Berater Team GmbH, Hamburg, de v1.0 + + Robin Vettier, ixxi.com, fr v1.3 + Ofer Porat, fr v1.3 + Burt Alexander', sigtec.com + Michelle Etienne, Dryade, Paris fr, v1.3 + Brian Ferris onebusaway.org, us, v1.3 + Manuem Mahne Siemens.com + + Ulf Bjersing, Hogia - Stenungsgrund, se v2.0 + Dipl.-Math Christoph Blendinger, DB, Frankfort, de v2.0 + Dipl.-Kfm. Winfried Bruns, Verband Deutscher, Köln, de v2.0 + Christophe Duquesne, PDG Consultant en systémes, Auriga, fr v2.0 + Gerald Dury, Trapeze Neuhausen am Rhein, ch, fr v2.0 + Michelle Etienne, Dryade, Paris fr v2.0 + Michael Frumin, MTA, us, v2.0 + Nicholas Knowles, Trapeze Limited, London, uk v2.0 + Werner Kohl, Mentz Datenverarbeitung GmbH, München, de v2.0 + Davide Lallouche, RATP, Paris, fr v2.0 + Jeff Makkie, us, v2.0 + Daniel Rubli, Trapeze Neuhausen am Rhein, ch, fr v2.0 + Gustav Thiessen BLIC thi@BLIC.DE, de 2.0 v1.0 + Jeff Maki, openplans, us, v2.0 + Europe + >Drafted for version 1.0 & Version 2.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2008-11-17 + + + + 2008-04-18 + + + + 2009-03-30 + + + + 2011-04-18 + + + + 2012-03-23 + + + +

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

      +

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

      +

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

      +

      SIRI includes common mechanisms and messages for system status management.

      +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}siriSg.xsd + [ISO 639-2/B] ENG + Kizoom Software Ltd 16 High Holborn, London WC1V 6BX + + http://www.siri.org.uk/schema/2.0/xsd/siri__base.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__allFunctionalServices.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG XML and Trident standards.
        • +
      • Derived from the SIRI Version 1.0
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport. + + CEN TC278 WG3 SG7 + + SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Generic Substitution groups version + Standard +       +       + SIRI Service Interface for Real-time Information relating to Public Transport Operations. XML Schema with loosely coupled functional services, +       + + + + + + + + + + + Service Interface for Real-time Operation. + + + + + + + + + + + +       diff --git a/xsd/siri_all_functionalServices.xsd b/xsd/siri_all_functionalServices.xsd index b29bbe37..0b49cb7e 100644 --- a/xsd/siri_all_functionalServices.xsd +++ b/xsd/siri_all_functionalServices.xsd @@ -1,95 +1,95 @@ - - - - - - main schema - e-service developers - Europe - >Drafted for Version 2.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - 2012-03-29 - Facrore dout from Siri.xsd - - 2012-03-29 - SIRI Version 2.0 - Refactored to improve modularisation - - -

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

      -

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

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

      -

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

      -

      SIRI includes common mechanisms and messages for system status management.

      -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/}all_functionalServices.xsd - [ISO 639-2/B] ENG - Kizoom Software Ltd 16 High Holborn, London WC1V 6BX - - http://www.siri.org.uk/schema/2.0/xsd/siri__base.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__estimatedTimetable_service.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__productionTimetable_service.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__stopMonitoring_service.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__vehicleMonitoring_service.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__connectionTimetable_service.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__connectionMonitoring_service.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__generalMessage_service.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__discovery.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__situationExchange_service.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__facilityMonitoring_service.xsd - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      • Derived from the SIRI Version 1.0.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport. - - CEN TC278 WG3 SG7 - - SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Current SIRI functional servics - Standard -       -       -       - - - - - - - - - - - - - - - - -       + + + + + + main schema + e-service developers + Europe + >Drafted for Version 2.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + 2012-03-29 + Facrore dout from Siri.xsd + + 2012-03-29 + SIRI Version 2.0 + Refactored to improve modularisation + + +

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

      +

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

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

      +

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

      +

      SIRI includes common mechanisms and messages for system status management.

      +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}all_functionalServices.xsd + [ISO 639-2/B] ENG + Kizoom Software Ltd 16 High Holborn, London WC1V 6BX + + http://www.siri.org.uk/schema/2.0/xsd/siri__base.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__estimatedTimetable_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__productionTimetable_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__stopMonitoring_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__vehicleMonitoring_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__connectionTimetable_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__connectionMonitoring_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__generalMessage_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__discovery.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__situationExchange_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__facilityMonitoring_service.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG XML and Trident standards.
        • +
      • Derived from the SIRI Version 1.0.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport. + + CEN TC278 WG3 SG7 + + SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Current SIRI functional servics + Standard +       +       +       + + + + + + + + + + + + + + + + +       diff --git a/xsd/siri_connectionMonitoring_service.xsd b/xsd/siri_connectionMonitoring_service.xsd index 1c666afe..607c12c1 100644 --- a/xsd/siri_connectionMonitoring_service.xsd +++ b/xsd/siri_connectionMonitoring_service.xsd @@ -1,731 +1,731 @@ - - - - - - main schema - e-service developers - CEN TC278 WG3 SG7 Team - Dipl.-Ing. Sven Juergens psitrans juergens@psitrans.de - Gustav Thiessen BLIC thi@BLIC.DE - Europe - Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2004-09-10 - - - 2004-10-01 - - - 2005-02-14 - - - 2005-02-20 - - - 2005-05-11 - - 2007-04-17 - Name Space changes - - 2008-11-17 - Revise to support substitution groups - - 2012-03-23 - +SIRI v2.0 - Add SuggestedWaitDecisionTime to MonitoredArrival - - 2012-04-18 - +SIRI v2.0 - Add ValidUntil Time to MonitoredFeederArrival - - * [FR] Add Extensions tag to ConnectionMonitoringSubscriptionRequest - [DE] Correct Capabilities matrix - - 2013-01-24 - WB: insert the AimedArrivalTime in MonitoredFeederArrival; insert the ArrivalPlatformName into MonitoredFeederArrival - - -

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

      -

      This sub-schema describes the Connection Monitoring Service.

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

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

      +

      This sub-schema describes the Connection Monitoring Service.

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

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

      -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/siri/2.0/xsd/}siri_connectionTimetable_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - -SIRI-CT schema. Service Interface for Real-time Information. Connection Timetable Service. - Standard -       -       - SIRI-CT Connection Timetable Service. -       - - - - - - - Convenience artifact to pick out main elements of the Connection Timetable Service. - - - - - - - - - - - - - - - - Request for information about timetabled connections at a stop. - - - - - Parameters that specify the content to be returned. - - - - - Earliest and latest time. If absent, default to the data horizon of the service. - - - - - CONNECTION link for which data is to be supplied. - - - - - Feeder LINE for which data is to be supplied. - - - - - Feeder DIRECTION for which data is to be supplied. - - - - - - - Type for Request for Connection Timetable Service. - - - - - - - - - - - Version number of request. Fixed - - - - - - - - - Parameters that affect the request processing. - - - - - Preferred languages in which to return text values. - - - - - - - - - Parameters that affect the subscription processing. - - - - - - Subscription Request for information about Timetabled connections at a stop. - - - - - Type for Subscription Request for Connection Protection. - - - - - - - - - - - - - - - Delivery for Connection Timetable Service. - - - - - Type for Delivery for Connection Protection. - - - - - - - - - - Version number of response. Fixed - - - - - - - - - Feeder delivery payload content. - - - - - - - - - - Fedder/Fetcher SERVICE JOURNEY INTERCHANGE Activity. - - - - - Type for an SERVICE JOURNEY INTERCHANGE feeder Activity. - - - - - - - Time until when data is valid. +SIRI 2.0 - - - - - - - - - - Elements identifying CALL at CONNECTION link of SERVICE JORUNEY INTERCHANGE of Feeder Journey . - - - - - Reference to the the SERVICE JOURNEY INTERCHANGE between two journeys for which data is being returned. - - - - - Reference to the CONNECTION link or ACCESS ZONE for which data is to be returned. i.e. associated with known feeder arrival and distributor departure STOP POINTs. - - - - - - - - - A feeder arrival at the arrival SCHEDUELD STOP POINT of the CONNECTION link . - - - - - Type for incoming visit by feeder journey to SERVICE JOURNEY NTERCHANGE - - - - - - - Information about the feeder journey. - - - - - Planned arrival time at the connection point. - - - - - - - - - - Cancellation of a previously issued Feeder Arrival. - - - - - Type for Timetabled Deletion of a feeder connection. - - - - - - - - Reference to a LINE. - - - - - Reference to a DIRECTION, typically outward or return. - - - - - Reference to a VEHICLE JOURNEY. - - - - - - Reason for deletion. (Unbounded since SIRI 2.0) - - - - - - - - - - - - Type for Deliveries for Connection Timetable Service. Used in WSDl. - - - - - - - - - - Request for information about Connection Timetable Service Capabilities. Answered with a ConnectionTimetableCapabilitiesResponse. - - - - - Capabilities for Connection Timetable Service. Answers a ConnectionTimetableCapabilitiesRequest. - - - - - - Type for Delivery for Connection TimetableService. - - - - - - - - Participant's permissions to use the service, Only returned if requested. - - - - - - - - Permission for a single participant or all participants to use an aspect of the service. - - - - - - - - - - - - -Version number of response. Fixed - - - - - - - - - Type for capability request. - - - - - - - Whether results returns foreign journeys only. - - - - - - - - - Capabilities of Connection Timetable Service. - - - - - Type for Connection Timetable Capabilities. - - - - - - - Filtering Capabilities. - - - - - - - Whether results can be filtered by Connection link. Default is ' true'. - - - - - - - - Request Policy capabilities. - - - - - - - - Whether service returns only foreign journeys. Default is 'false'. - - - - - - - - - - Subscription Policy capabilities. - - - - - Optional Access control capabilities. - - - - - - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Dipl.-Ing. Sven Juergens psitrans juergens@psitrans.de + Gustav Thiessen BLIC thi@BLIC.DE + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2004-09-10 + + + 2004-10-01 + + + 2005-02-14 + + + 2005-02-20 + + + 2005-05-11 + + + 2007-04-17 + + + + 2008-11-17 + + + + 2011-01-19 + + + + 2012-03-23 + + + + 2012-04-18 + + + +

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

      +

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

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

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

      -

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

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/}siri_discovery.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference.xsd - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Discovery services Derived from the NaPTAN standard .
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI_DS XML schema. Service Interface for Real-time Information. Discovery subschema. - Standard -       -       - SIRI DIscovery Services for SCHEDULED STOP POINTs, LINEs,OPERATORs, FACILITies and feature TYPE OF VALUE codes. -       - - - - - - - - - - - - Convenience artifact to pick out main elements of the Estimated Timetable Service. - - - - - - - - - Requests for reference data for use in service requests. - - - - - - - - - - - - - - - - - - Responses with reference data for use in service requests. - - - - - - - - - - - - - - - - - Requests a list of the STOP POINTs and places covered by a Producer. - - - - - - - - - - Requests for stop reference data for use in service requests. - - - - - - - Parameters that specify the content to be returned. (+SIRI v2.0) - - - - - Parameters that affect the request processing. Mostly act to reduce the number of stops returned. (+SIRI v2.0) - - - - - - - Version number of request. Fixed - - - - - - - - - Parameters that specify the STOP POINTs to be returned. +SIRI v2.0 - - - - - - Rectangle containing stops be returned. (+SIRI v2.0) - - - - - Circle containing stops be returned. Point indicates centre, precision indicates radius (+SIRI v2.0) - - - - - Filter the results to include only stops associated with the PLACE . (+SIRI v2.0) - - - - - - Filter the results to include only stops run by the specified OPERATOR. (+SIRI v2.0) - - - - - Filter the results to include only stops for the given LINE. (+SIRI v2.0) - - - - - - - Parameters that affect the request processing. Mostly act to reduce the number of stops returned. +SIRI v2.0 - - - - - Preferred languages in which to return text values. +SIRI v2.0 - - - - - Level of detail to include in response. Default is 'normal'. +SIRI v2.0 - - - - - - - Detail Levels for Stop Points Discovery Request. +SIRI v2.0 - - - - - Return only the name and identifier of the stop. - - - - - Return name, dientifier and coordinates of the stop. - - - - - Return all available data for each stop. - - - - - - - - Returns basic details about the STOP POINTs/places covered by a service. Answers a StopPointsRequest. - - - - - Response with STOP POINTs available to make requests. - - - - - - - - - - Version number of response. Fixed - - - - - - - - - - - Requests a list of the LINEs covered by a Producer. - - - - - Requests for LINE data for use in service requests. - - - - - - - - - - - Version number of request. Fixed - - - - - - - - - Parameters that specify the LINEs to be returned. +SIRI v2.0 - - - - - - - Rectangle containing stops of lines be returned. (+SIRI v2.0) - - - - - Circle containing stops for lines be returned. Point indicates centre, precision indicates radius (+SIRI v2.0) - - - - - Filter the results to include only lines for stops assoicated with the place . (+SIRI v2.0) - - - - - - Reference to line for which details are to be returned (v2.0) - - - - - - Filter the results to include only Stop d run by the specified OPERATOR. (+SIRI v2.0) - - - - - - - Parameters that affect the request processing. Mostly act to reduce the number of Linesreturned. +SIRI v2.0 - - - - - Preferred languages in which to return text values. +SIRI v2.0 - - - - - Level of detail to include in response. Default is 'normal'. +SIRI v2.0 - - - - - - - Detail Levels for Lines Discovery Request. +SIRI v2.0 - - - - - Return only the name and identifier of the stop. - - - - - Return name, dientifier and coordinates of the stop. - - - - - - Return all available data for each stop. - - - - - - - - Returns the LINEs covered by a web service. Answers a LINEsRequest. - - - - - Response with LINEs available to make requests. - - - - - - - - - - Version number of response. Fixed. - - - - - - - - - - Requests a list of the Product Categories covered by a Producer. - - - - - Requests for TYPE OF PRODUCT CATEGORY reference data for use in service requests. - - - - - - - - - - Version number of request. Fixed - - - - - - - - - Parameters that affect the request processing. Mostly act to reduce the number of Facilities returned. +SIRI v2.0 - - - - - Preferred languages in which to return text values. +SIRI v2.0 - - - - - - - - Returns the Product Categories covered by a service. Answers a ProductCategoriesRequest. - - - - - Type for Response with Product Categories available to make requests. - - - - - - - - - - Version number of response. Fixed. - - - - - - - - - - Requests a list of the Vehicle Features covered by a Producer. - - - - - Requests for VEHICLE feature data for use in service requests. - - - - - - - - - - Version number of request. Fixed - - - - - - - - - Parameters that affect the request processing. Mostly act to reduce the number of Facilities returned. +SIRI v2.0 - - - - - Preferred languages in which to return text values. +SIRI v2.0 - - - - - - - - Returns the Vehicle Features covered by a service. Answers a VehicleFeaturesRequest. - - - - - Type for Response with Vehicle Features available to make requests. - - - - - - - - - - Version number of response. Fixed. - - - - - - - - - - Requests a list of the Info Channels covered by a Producer. - - - - - Requests for info channels for use in service requests. - - - - - - - - - Version number of request. Fixed - - - - - - - - - - Returns the Info Channels covered by a service. Answers a InfoChannelRequest. - - - - - Type for Response with Info channels categories available to make requests. - - - - - - - - - - Version number of response. Fixed. - - - - - - - - - - Requests a list of the Facilities covered by a Producer. - - - - - Requests for info channels for use in service requests. - - - - - - - - - - - Version number of request. Fixed - - - - - - - - - Parameters that specify the Facilities to be returned. +SIRI v2.0 - - - - - - Rectangle containing Facilities be returned. (+SIRI v2.0) - - - - - Filter the results to include only Facilities associated with the TOPOGRAPHIC PLACE . (+SIRI v2.0) - - - - - - Filter the results to include only Facilities run by the specified OPERATOR. (+SIRI v2.0) - - - - - Filter the results to include only Facilities for the given LINE. (+SIRI v2.0) - - - - - - - Parameters that affect the request processing. Mostly act to reduce the number of Facilities returned. +SIRI v2.0 - - - - - Preferred languages in which to return text values. +SIRI v2.0 - - - - - Level of detail to include in response. Default is 'normal'. +SIRI v2.0 - - - - - - - Detail Levels for Facility Points Request. +SIRI v2.0 - - - - - Return only the name and identifier of the Facility. - - - - - Return name, identifier and coordinates of the Facility. - - - - - Return all available data for each Facility. - - - - - - - - Returns the Facilities covered by a service. Answers a StopPointsRequest. - - - - - Response with Facilities available to make requests. - - - - - - - Facility Definition. - - - - - - - Version number of response. Fixed. - - - - - - - - - - - Requests a list of the Service Features covered by a Producer. - - - - - - - - - - Type for equests for TYPE OF PRODUCT CATEGORY reference data for use in service requests. - - - - - - - - - Version number of request. Fixed - - - - - - - - - - Returns the SERVICE FEATUREs covered by a service. Answers a ServiceFeaturesRequest. - - - - - Type for Response with SERVICE FEATUREs available to make requests. - - - - - - - - - Version number of response. Fixed. - - - - - - - - - - Requests a list of the CONNECTION LINKs covered by a Producer. +SIRI v2.0 - - - - - Requests for CONNECTION LINK data for use in service requests. +SIRI v2.0 - - - - - - - - - - - Version number of request. Fixed - - - - - - - - Parameters that specify the CONNECTION LINKs to be returned. +SIRI v2.0 - - - - - - - Rectangle containing stops of ConnectionLinks be returned. - - - - - Circle containing stops for ConnectionLinks be returned. Point indicates centre, precision indicates radius - - - - - Filter the results to include only ConnectionLinks for stops assoicated with the place . - - - - - - - Filter the results to include only ConnectionLinks for stops assoicated with the specified line. - - - - - Filter the results to include only Stop d run by the specified OPERATOR. - - - - - - - Parameters that affect the request processing. Mostly act to reduce the number of ConnectionLinks returned. +SIRI v2.0 - - - - - Preferred languages in which to return text values. +SIRI v2.0 - - - - - Level of detail to include in response. Default is 'normal'. +SIRI v2.0 - - - - - - - Detail Levels for CONNECTION LINKs Discovery Request. +SIRI v2.0 - - - - - Return only the name and identifier of the connection link. - - - - - Return name, identifier of the connection link and connected stops's identifiers. - - - - - Return all available data for each connection link. - - - - - - - - Returns the CONNECTION LINKs covered by a web service. Answers a LINEsRequest. +Siri v2.0 - - - - - Response with CONNECTION LINKs available to make requests. +SIR v2.0 - - - - - - - - - - Version number of response. Fixed. - - - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2004-09-29 + + + 2005-02-14 + + + 2005-02-20 + + + 2005-05-04 + + + 2005-11-25 + + + 2007-04-17 + + + + 2008-11-13 + + + + 2008-11-17 + + + + 2012-03-23 + + + + 2012-05-17 + + + + 2013-03-28 + + + +

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

      +

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

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

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

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

      -

      This sub-schema describes the Estimated Timetable Service.

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/}siri_estimatedTimetable_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_estimatedVehicleJourney.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions.xsd - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI-ET XML schema. Service Interface for Real-time Information. Estimated Timetable Service. - Standard -       -       - SIRI-ET Estimated Timetable Service. -       - - - - - - - - Convenience artifact to pick out main elements of the Estimated Timetable Service. - - - - - - - - - - - - - - - - - Request for information about the estimated timetable. - - - - - Type for Type for Functional Service Request for Estimated Timetable. - - - - - - - - - - - Version number of request. Fixed - - - - - - - - - Parameters that specify the content to be returned. - - - - - Forward duration for which journeys should be included. For subscriptions, this duration is a continuously rolling window from the present time. For immediate requests, this duration is measured from the time of the request. - - - - - Communicate only differences to the timetable specified by this version of the timetable. - - - - - Filter the results to include journeys for only the specified OPERATORs. - - - - - Filter the results to include only VEHICLEs along the given LINEs. - - - - - - Include only vehicles along the given LINE. - - - - - - - - Filter the results to include only journeys of the specified VEHICLE MODE. +SIRI v2.1 - - - - - Filter the results to include only journeys of the specified TYPE OF PRODUCT CATEGORY. +SIRI v2.1 - - - - - Filter the results to include only journeys with a CALL at the specified STOP POINT. +SIRI v2.1 - - - - - - - Parameters that affect the request processing. Mostly act to reduce the number of messages exchanged. - - - - - Preferred languages in which to return text values. - - - - - - - - - Level of detail to include in response. Default is 'normal'. (SIRI 2.0) - - - - - - - Detail Levels for Estimated Timetable Request. - - - - - Return only the minimum amount of optional data for each Stop Visit to provide a display, A time at stop, LINE name and destination name. - - - - - Return minimum and other available basic details for each Stop Visit. Do not include data on times at next stop or destination. - - - - - Return all basic data, and also origin VIA points and destination. - - - - - Return in addition to normal data, the estimated call data i . - - - - - Return all available data for each including calls. - - - - - - - - Request for a subscription to the Estimated Timetable Service. - - - - - Parameters that affect the subscription publishing and notification processing. - - - - - Whether the producer should return the complete set of data, or only provide updates to the previously returned data i.e. changes to the expected deviation (delay or early time). Default is 'true'. If true only changes at the first stop will be returned and the client must interpolate the -If false each subscription response will contain the full information as specified in this request (++SIRI 2.0). - - - - - The amount of change to the arrival or departure time that can happen before an update is sent (i.e. if ChangeBeforeUpdate is set to 2 minutes, the subscriber will not be told that a timetable is changed by 30 seconds - an update will only be sent when the timetable is changed by at least least 2 minutes. (OPtional from SIRI 2.0) - - - - - Indicates whether actual arrival-/departure times should be delivered as incremental updates, i.e. whether RECORDED CALL updates are transmitted immediately after an event occurs. +SIRI v2.1 -- 'false': Specifies that the data producer should transmit RECORDED CALL data, in particular actual arrival-/departure information as an incremental update immediately after an event occurs (with hysteresis taken into account) as is generally the case. -The server will automatically proceed with 'false' if capability is not supported. -- 'true': Can be requested if the data traffic is to be reduced and an immediate transmissions is not required in any of the consumer systems. -'true' specifies that the data producer should skip RECORDED CALL updates (if capability is supported after all), i.e., deliver them with the next update instead. -- No specification: Default value 'false' applies (don't skip updates of recorded data). - - - - - Indicates whether ONLY actual arrival-/departure times should be delivered. In other words, whether all updates related to ESTIMATED CALL should be skipped. +SIRI v2.1 -- 'false': Specifies that the data producer should transmit ESTIMATED and RECORDED CALL data as an incremental update immediately after an event occurs (with hysteresis taken into account) as is generally the case. -The server will automatically proceed with 'false' if capability is not supported. -- 'true': Can be requested if a consumer system is only interested in the actual times / recorded events because it only wants to check the performance for example. -'true' specifies that the data producer should only deliver RECORDED CALL udpates and skip ESTIMATED CALL updates (if capability is supported after all), i.e., deliver ESTIMATED CALL updates only with the next RECORDED CALL update. -- No specification: Default value 'false' applies (don't skip updates of estimated data). - - - - - - - Subscription Request for the Estimated Timetable Service. - - - - - - - - - - - - - - - - - - Delivery for Estimated Timetable Service. - - - - - Type for Delivery for Real-time Timetable Service. - - - - - - - - - Version number of response. Fixed - - - - - - - - - Type for version frame structure. - - - - - - - - - Connection parameters for a monitored SERVICE JOURNEY INTERCHANGE between a feeder and distributor journey. SIRI 2.0 - - - - - - - - - Payload part of Estimated Timetable Delivery. - - - - - Estimated Journeys of a common TIMETABLE VERSION FRAME, grouped by timetable version. - - - - - - - - - - Type for Deliveries for Real-time Timetable Service. Used in WSDL. - - - - - - - - - - Request for information about Estimated Timetable Service Capabilities. Answered with a EstimatedTimetableCapabilitiesResponse. - - - - - - Capabilities for Estimated Timetable Service. Answers a EstimatedTimetableCapabilitiesRequest. - - - - - Type for Delivery for Estimated Timetable Capability. - - - - - - - - - - - - - - - Type for Estimated Timetable Capability Request Policy. - - - - - - - Whether results returns foreign journeys only. - - - - - - - - - Capabilities of Estimated TimetableService. - - - - - Type for Estimated Timetable Capabilities. - - - - - - - Filtering Capabilities. - - - - - - Preview interval available for estimations. - - - - - - - - - - Whether results can be filtered by TIMETABLE VERSION Default is 'true'. - - - - - - - - Request Policy capabilities. - - - - - - - - - - Subscription Policy capabilities. - - - - - Optional Access control capabilities. - - - - - - - - - - - Participant's permissions to use the service. - - - - - - - - Permission for a single participant or all participants to use an aspect of the service. - - - - - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Werner Kohl MDV + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2003-02-10 + + + 2004-10-31 + + + 2005-02-14 + + + 2005-02-20 + + + 2005-05-11 + + 2007-04-17 + Name Space changes + + 2008-03-26 + Add wrapper tag for Line DIRECTION to help binding to Axis + + 2008-11-17 + Revise to support substitution groups + + 2011-01-19 + Drop use of As Flat Groups for EstimatedCalls + + 2012-03-23 + +SIRI v2.0 + - Add EstimatedServiceJourneyInterchange (i.e. Estimated Connection of VEHICLE) to EstimatedTimetableDelivery + - [FR] Add Extensions tag to EstimatedTimetableSubscriptionRequest + - [DE] Add ExpectedDeparturePredictionQuality to OnwardVehicleDepartureTimes + [DE] Correct capabilites matrix to matx doc. Add defauklt preview intervakl and versionref + + +

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

      +

      This sub-schema describes the Estimated Timetable Service.

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

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

      -

      This sub-schema describes the Facility Monitoring Service.

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/}sir_facilityMonitoring_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_reference.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions.xsd - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI-FM XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Facility Monitoring Subschema - Standard -       -       - SIRI-FM Facility Monitoring Service. -       - - - - - - - - - - - - - - - - - Convenience artifact to pick out main elements of the Facility Monitoring Service. - - - - - - - - - - - - - - - - Request for information about Facilities status. - - - - - Type for Functional Service Request for Facility Monitoring Service. - - - - - - - - - - - Version number of request. Fixed - - - - - - - - - Parameters that specify the content to be returned. - - - - - Forward duration for which Facilities status change: only status change which will occur within this time span will be returned. - - - - - Start time for PreviewInterval. If absent, then current time is assumed. - - - - - Parameters to filter Facility Monitoring requests, based on the facility location. Parameter value will be logically ANDed together. Multiple values fro the same parameter will be logically ORed. - - - - - Filter only for facility changes that affect the following accessibility needs. - - - - - - - Type for information about Accessibility Facilities status. - - - - - User need to be monitored. - - - - - - - Parameters to filter Facility Monitoring requests, based on the facility location . - - - - - - - - - - Use of simple reference is deprecated - - - - Refercence to a VEHICLE JOURNEY framed by the day. SIRI 2.0 - - - - - - - - - Reference to a stop place. - - - - - Reference to a stop place component. - - - - - Reference to a Site. - - - - - - - Parameters that affect the request processing. - - - - - Preferred languages in which to return text values. - - - - - - The maximum number of facility status in a given delivery. The most recent n Events within the look ahead window are included. - - - - - - - - Request for a subscription to the Vehicle Monitoring Service. - - - - - Parameters that affect the subscription publishing and notification processing. - - - - - Whether the producer will return the complete set of current data, or only provide updates to this data, i.e. additions, modifications and deletions. -If false or omitted, each subscription response will contain the full information as specified in this request. - - - - - - - Type for Subscription Request for Vehicle Monitoring Service. - - - - - - - - - - - - - - - - Delivery for Vehicle Monitoring Service. - - - - - Payload part of Vehicle Monitoring delivery. - - - - - - - - Type for Delivery for Vehicle Monitoring Service. Provides information about one or more vehicles; each has its own VEHICLE activity element. - - - - - - - Payload part of Facility Monitoring delivery. - - - - - - - Version number of response. Fixed - - - - - - - - - Condition of a Facility that is being monitored. - - - - - - - - Type for Deliveries for VEHICLE monitoring services Used in WSDL. - - - - - Delivery for Vehicle Activity Service. - - - - - - - - - Request for information about Vehicle Monitoring Service Capabilities. Answered with a VehicleMontoringCapabilitiesResponse. - - - - - - Capabilities for Vehicle Monitoring Service. Answers a VehicleMontoringCapabilitiesRequest. - - - - - Type for Delivery for Vehicle Monitoring Service. - - - - - - - - - - - Version number of response. Fixed - - - - - - - - - Capabilities of Vehicle Monitoring Service. - - - - - Type for Vehicle Monitoring Capabilities. - - - - - - - Filtering Capabilities. - - - - - - Default preview interval. Default is 60 minutes. - - - - - - Whether results can be filtered by location. Fixed as 'true'. - - - - - - - - - - - Whether results can be filtered by Specific Needs. Default is 'true'. - - - - - - - - Request Policy capabilities. - - - - - - - - - - - - - - Subscription Policy capabilities. - - - - - Optional Access control capabilities. - - - - - - - - - - - - - - - Optional Response capabilities. - - - - - - Whether result supports remedy information. Default is 'false' - - - - - Whether result supports facility location information. Default is 'true'. - - - - - - - - - - - - - Elements for volume control. - - - - - Whether a maximum number of Facility Status to include can be specified. Default is 'false'. - - - - - - - - Participant's permissions to use the service. - - - - - - - - - - - - - - Type for Facility Monitoring Service Permissions. - - - - - - - - - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + Drafted for version 1.1 CEN TC278 WG3 SG7 Editor Christophe Duquesne Dryade mailto:christophe.duquesne@dryade.net + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + + 2007-01-22 + + + 2007-01-22 + + 2007-04-17 + Name Space changes + + 2008-11-17 + Revise to support substitution groups + + 2008-11-18 + Revise in line with FM spec - add filters + + 2012-03-23 + +SIRI v2.0 + Add Extensions tag to FacilityMonitoringSubscriptionRequest + + +

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

      +

      This sub-schema describes the Facility Monitoring Service.

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

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

      -

      This sub-schema describes the General Message Service.

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/}siri_generalMessage_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_reference.xsd - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI-GM XML schema. Service Interface for Real-time Information. SubSchema for General Message Service - Standard -       -       - SIRI-GM General Message Service. -       - - - - - - - Convenience artefact to pick out main elements of the General Message Service. - - - - - - - - - - - - - - - - - Request for information about general information messages affecting stops, vehicles or services. - - - - - Service Request for General Messages. - - - - - - - - - - - Version number of request. Fixed - - - - - - - - - Parameters that affect the request processing. - - - - - Referenceto an Info Channel for which messages are to be returned. - - - - - - - Parameters that affect the request processing. - - - - - Preferred languages in which to return text values. - - - - - - - Request for a subscription to General Message Service. - - - - - Subscription for General Message Service. - - - - - - - - - - - - - - - Delivery for General Message Service. - - - - - General Message payload content. - - - - - - - - - Delivery for General Message. - - - - - - - - - - Version number of response. Fixed - - - - - - - - - - An informative message. - - - - - Type for an Info Message. @formatRef. - - - - - - - - Time until when message is valid. If absent unopen ended. - - - - - - Message Content. Format is specified by Format Ref. - - - - - - - - - Reference to a format of the Content. If absent, free text. - - - - - - - - Extra information provided on general message notifcation that can be used to filter messages. - - - - - Unique identifier of message. - - - - - Optional version number of update to previosu message. - - - - - Info Channel to which message belongs. - - - - - - - A revocation of a previous message. - - - - - Type for Revocation of a previous message. - - - - - - - Identifier of message. Unique within service and Producer participant. - - - - - Info Channel to which message belongs. - - - - - - - - - - - Type for identifier of an Info Message. - - - - - - Type for reference to an Info Message. - - - - - - - - - - Type for Deliveries. Used in WSDL. - - - - - Delivery for general Message service. - - - - - - - - - Request for information about General Message Service Capabilities. Answered with a GeneralMessageCapabilitiesResponse. - - - - - - Capabilities for General Message Service. Answers a GeneralMessageCapabilitiesResponse. - - - - - Type for Delivery for General MessageService. - - - - - - - - - - - -Version number of response. Fixed - - - - - - - - - Capabilities of General Message Service. - - - - - Type for General Message Capabilities. - - - - - - - Filtering Capabilities. - - - - - - Default preview interval. Default is 60 minutes. - - - - - Whether results can be filtered by InfoChannel, departures. Default is 'true'. - - - - - - - - Request Policiy capabilities. - - - - - Optional Access control capabilities. - - - - - - - - - - Participant's permissions to use the service. - - - - - - - - Permission or a single particpant or all participants. - - - - - - - - - - Type for General MessageService Permission. - - - - - - - The monitoring points that the participant may access. - - - - - - - Participant's permission for this InfoChannel. - - - - - - - - - - - - - Type for access control. - - - - - - - If access control is supported, whether access control by LINE is supported. Default is 'true'. - - - - - - - - - Type for Info Channel Permission. - - - - - - - Reference to an Info Channel to which permission applies. - - - - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Gustav Thiessen BLIC thi@BLIC.DE + Europe + >Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2004-09-29 + + + 2004-10-01 + + + 2005-02-14 + + + 2005-02-20 + + + 2005-05-11 + + + 2007-04-17 + + + + 2008-11-17 + + + + 2011-04-18 + + + + 2012-03-23 + + + +

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

      +

      This sub-schema describes the General Message Service.

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}siri_generalMessage_service.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_reference.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG XML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI-GM XML schema. Service Interface for Real-time Information. SubSchema for General Message Service + Standard +       +       + SIRI-GM General Message Service. +       + + + + + + + Convenience artefact to pick out main elements of the General Message Service. + + + + + + + + + + + + + + + + + Request for information about general information messages affecting stops, vehicles or services. + + + + + Service Request for General Messages. + + + + + + + + + + + Version number of request. Fixed + + + + + + + + + Parameters that affect the request processing. + + + + + Referenceto an Info Channel for which messages are to be returned. + + + + + + + Parameters that affect the request processing. + + + + + Preferred languages in which to return text values. + + + + + + + Request for a subscription to General Message Service. + + + + + Subscription for General Message Service. + + + + + + + + + + + + + + + Delivery for General Message Service. + + + + + General Message payload content. + + + + + + + + + Delivery for General Message. + + + + + + + + + + Version number of response. Fixed + + + + + + + + + + An informative message. + + + + + Type for an Info Message. @formatRef. + + + + + + + + Time until when message is valid. If absent unopen ended. + + + + + + Message Content. Format is specified by Format Ref. + + + + + + + + + Reference to a format of the Content. If absent, free text. + + + + + + + + Extra information provided on general message notifcation that can be used to filter messages. + + + + + Unique identifier of message. + + + + + Optional version number of update to previosu message. + + + + + Info Channel to which message belongs. + + + + + + + A revocation of a previous message. + + + + + Type for Revocation of a previous message. + + + + + + + Identifier of message. Unique within service and Producer participant. + + + + + Info Channel to which message belongs. + + + + + + + + + + + Type for identifier of an Info Message. + + + + + + Type for reference to an Info Message. + + + + + + + + + + Type for Deliveries. Used in WSDL. + + + + + Delivery for general Message service. + + + + + + + + + Request for information about General Message Service Capabilities. Answered with a GeneralMessageCapabilitiesResponse. + + + + + + Capabilities for General Message Service. Answers a GeneralMessageCapabilitiesResponse. + + + + + Type for Delivery for General MessageService. + + + + + + + + + + + +Version number of response. Fixed + + + + + + + + + Capabilities of General Message Service. + + + + + Type for General Message Capabilities. + + + + + + + Filtering Capabilities. + + + + + + Default preview interval. Default is 60 minutes. + + + + + Whether results can be filtered by InfoChannel, departures. Default is 'true'. + + + + + + + + Request Policiy capabilities. + + + + + Optional Access control capabilities. + + + + + + + + + + Participant's permissions to use the service. + + + + + + + + Permission or a single particpant or all participants. + + + + + + + + + + Type for General MessageService Permission. + + + + + + + The monitoring points that the participant may access. + + + + + + + Participant's permission for this InfoChannel. + + + + + + + + + + + + + Type for access control. + + + + + + + If access control is supported, whether access control by LINE is supported. Default is 'true'. + + + + + + + + + Type for Info Channel Permission. + + + + + + + Reference to an Info Channel to which permission applies. + + + + + + +       diff --git a/xsd/siri_model/siri_all.xsd b/xsd/siri_model/siri_all.xsd index 0ab0d00f..62625177 100644 --- a/xsd/siri_model/siri_all.xsd +++ b/xsd/siri_model/siri_all.xsd @@ -1,13 +1,13 @@ - - - - - - - - - - + + + + + + + + + + diff --git a/xsd/siri_model/siri_all_journeyModel.xsd b/xsd/siri_model/siri_all_journeyModel.xsd index 48079667..25648414 100644 --- a/xsd/siri_model/siri_all_journeyModel.xsd +++ b/xsd/siri_model/siri_all_journeyModel.xsd @@ -1,21 +1,21 @@ - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + diff --git a/xsd/siri_model/siri_all_model.xsd b/xsd/siri_model/siri_all_model.xsd index 984702ec..80ada732 100644 --- a/xsd/siri_model/siri_all_model.xsd +++ b/xsd/siri_model/siri_all_model.xsd @@ -1,13 +1,13 @@ - - - - - - - - - - + + + + + + + + + + diff --git a/xsd/siri_model/siri_all_situation.xsd b/xsd/siri_model/siri_all_situation.xsd index 2c0f6a2c..a2fc4d7f 100644 --- a/xsd/siri_model/siri_all_situation.xsd +++ b/xsd/siri_model/siri_all_situation.xsd @@ -1,17 +1,17 @@ - - - - - - - - - - - - - - + + + + + + + + + + + + + + diff --git a/xsd/siri_model/siri_datedVehicleJourney.xsd b/xsd/siri_model/siri_datedVehicleJourney.xsd index a5d179af..b34038f5 100644 --- a/xsd/siri_model/siri_datedVehicleJourney.xsd +++ b/xsd/siri_model/siri_datedVehicleJourney.xsd @@ -1,702 +1,702 @@ - - - - - - main schema - e-service developers - CEN TC278 WG3 SG7 Team - Werner Kohl MDV - Europe - Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2003-02-10 - - - 2004-10-31 - - - 2005-02-14 - - - 2005-02-20 - - - 2005-05-11 - - 2007-04-17 - Name Space changes - - 2008-03-26 - Add wrapper tag for Line DIRECTION to help binding to Axis - - 2008-11-17 - Revise to support substitution groups - - 2011-04-18 - - siri_productionTimetable_service.xsd Type on request ValidiyPeriod start and end should be datetime not time .. - - Change to ClosedTimestampRange instead of ClosedTimeRange. - Fix Subscription request to be an element and have extensions . - - 2011-01-19 - SIRI 1.3 Drop use of As Flat Groups for DatedCalls. - - 2012-03-23 - Factor out fropm ProductionTimetable package - +SIRI v2.0 Add ServiceJourneyInterchange (i.e. Monitored Connection) - [VDV] Add additional times to TargetedServiceInterchange MinimumTransferTime, MaximimTransferTime, StandardTransferTime, MaximumAUtomaticWaitTime, StandardWaitTime. - [VDV] Add Public and Contact Details to JourneyInfo - [VDV] Add AimedLatestPassengerAccessTime to TargetedCall - - - 2013-02-11 - SIRI v2.0 Modified ServiceJourneyInterchange SIRI:PT - - -

      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/schema/2.0/xsd/siri_model/}siri_datedVehicleJourney.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI_PT XML schema. Service Interface for Real-time Information. Production Timetable Service. - Standard -       -       - SIRI-Model Dated Vehicle Joruney. -       - - - - - - A planned VEHICLE JOURNEY taking place on a particular date. - - - - - Type for Planned VEHICLE JOURNEY (Production Timetable Service). - - - - - Identifier for a VEHICLE JOURNEY. - - - - - - - - - - - - - Complete sequence of stops along the route path, in calling order. - - - - - - - - - - Relations of the journey with other journeys, e.g., in case a joining/splitting takes place or the journey substitutes for another one etc. - - - - - - - - Type for previously planned VEHICLE JOURNEY that is removed from the data producer when using incremental updates. +SIRI v2.1 - - - - - A reference to the DATED VEHICLE JOURNEY from a previous PT delivery that is removed by the data producer. - - - - - Optionally identify the VEHICLE JOURNEY indirectly by origin and destination and the scheduled times at these stops. - - - - - TRAIN NUMBERs for journey. - - - - - - TRAIN NUMBER assigned to VEHICLE JOURNEY. - - - - - - - - - - - General info elements that apply to all journeys of timetable version unless overriden. - - - - - Description of the origin stop (vehicle signage) to show on vehicle, Can be overwritten for a journey, and then also section by section by the entry in an Individual Call. (+SIRI 2.0) - - - - - Description of the 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. (Unbounded since SIRI 2.0) - - - - - Additional Text associated with LINE. (Unbounded since SIRI 2.0) - - - - - Whether journey is first or last jouurney of day. +SIRI v2.0 - - - - - - - If the journey is an alteration to a timetable, indicates the original journey, and the nature of the difference. - - - - - Use of simple reference is deprecated - - - - Refecence to a VEHICLE JOURNEY framed by the day. SIRI 2.0 - - - - - - - - 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 cancellation of a journey in the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the journey is not cancelled. - - - - - - - - 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 SERVICE JOURNEY INTERCHANGE between two journeys. +SIRI v2.0 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A planned SERVICE JOURNEY INTERCHANGE from a journey. +SIRI v2.0 - - - - - - - - - - - - - - - - - - - - - - - - - - - A planned SERVICE JOURNEY INTERCHANGE to a journey. +SIRI v2.0 - - - - - - - - - - - - - - - - - - - - - - - - - - - A planned SERVICE JOURNEY INTERCHANGE between two journeys. +SIRI v2.0 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Type for a previously planned SERVICE JOURNEY INTERCHANGE that a data producer wants to silently remove from the plan (because it is erroneous data). Careful: Removal is different from Cancellation. +SIRI v2.1 - - - - - - - - - - - - - - - - - - - - - - - - - - Time Elements for SERVICE JOURNEY INTERCHANGE. - - - - - Elements for INTERCHANGE WAIT TIME. - - - - - - - - Elements for INTERCHANGE TRANSFER duration. - - - - - Standard transfer duration for INTERCHANGE. SIRI v2,0 - - - - - Minimum transfer duration for INTERCHANGE. SIRI v2,0 - - - - - Maximum transfer duration for INTERCHANGE. SIRI v2,0 - - - - - - - Elements for INTERCHANGE WAIT TIME. - - - - - Standard wait time for INTERCHANGE. SIRI v2,0 - - - - - Maximum time that Distributor will wait for Feeder for INTERCHANGE. SIRI v1.0 - - - - - Maximum automatic wait time that Distributor will wait for Feeder for INTERCHANGE. +SIRI v2.0 - - - - - - - - Complete sequence of stops along the route path, in calling order. - - - - - Type for Planned VEHICLE JOURNEY Stop (Production Timetable Service). - - - - - - - Whether this DATED CALL is an addition to the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to false: the journey is not an addition. - - - - - Whether this DATED CALL is a cancellation of a previously announced call (or planned according to the long-term timetable). Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the journey is not cancelled. - - - - - - - Text annotation that applies to this call. - - - - - - - Information on any planned distributor connections (deprecated from SIRI V2.0 ... see 2 next attributes) - - - - - Information on any planned feeder connections. SIRI 2.0 - - - - - Information on any planned distributor connections. SIRI 2.0 - - - - - - - - - Planned Connection between two VEHICLE JOURNEYs. - - - - - - - Reference to a (dated) distributor VEHICLE JOURNEY. - - - - - - Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY 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. - - - - - - - - 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. - - - - - - - - - Connection between two stops within a connection area. Used within the context of one or other end. - - - - - Identifier of CONNECTION LINk. - - - - - - - - - - Times for making SERVICE JOURNEY INTERCHANGE. - - - - - Default time (Duration) needeed to traverse SERVICE JOURNEY INTERCHANGE from feeder to distributor. - - - - - Time needeed by a traveller whis is familiar with SERVICE JOURNEY INTERCHANGE to traverse it. If absent, use DefaultDuration. - - - - - Time needeed by a traveller whis is not familiar with SERVICE JOURNEY INTERCHANGE to traverse it. If absent, use DefaultDuration and a standard weighting. - - - - - Time needeed by a traveller wos is mobility impaired to traverse SERVICE JOURNEY INTERCHANGE. If absent, use DefaultDuration and a standard impaired travel speed. - - - - - - - Properties of SERVICE JOURNEY INTERCHANGE. - - - - - Whether the passenger can remain in VEHICLE (i.e. BLOCKlinking). Default is 'false': the passenger must change vehicles for this connection. - - - - - Whether the SERVICE JOURNEY INTERCHANGE is guaranteed. Default is 'false'; SERVICE JOURNEY INTERCHANGE is not guaranteed. - - - - - Whether the SERVICE JOURNEY 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. - - - - - - - - Identifier of SERVICE JOURNEY INTERCHANGE. +SIRI v2.0 - - - - - Whether this interchange is an addition to the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the interchange is not an addition. +SIRI v2.1 - - - - - Whether this interchange is a cancellation of a previously announced interchange (or planned according to the long-term timetable. -Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the interchange is not cancelled. +SIRI v2.1 - - - - - - The data producer must provide a reason, e.g. type of error and description, in case he wants to silently remove (instead of cancel) a journey or an interchange from the plan. +SIRI v2.1 - - - - - Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 - - - - - SCHEDULED STOP POINT at which feeder journey arrives. +SIRI v2.0 - - - - - Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. - - - - - For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. -ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 - - - - - Planned time at which feeder VEHICLE is scheduled to arrive. SIRI v2.1 - - - - - Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 - - - - - SCHEDULED STOP POINT at which distributor journet departs. +SIRI v2.0 - - - - - Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. - - - - - For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. -ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 - - - - - Planned time at which distributor VEHICLE is scheduled to depart. SIRI v2.1 - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Werner Kohl MDV + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2003-02-10 + + + 2004-10-31 + + + 2005-02-14 + + + 2005-02-20 + + + 2005-05-11 + + 2007-04-17 + Name Space changes + + 2008-03-26 + Add wrapper tag for Line DIRECTION to help binding to Axis + + 2008-11-17 + Revise to support substitution groups + + 2011-04-18 + - siri_productionTimetable_service.xsd Type on request ValidiyPeriod start and end should be datetime not time .. + - Change to ClosedTimestampRange instead of ClosedTimeRange. + Fix Subscription request to be an element and have extensions . + + 2011-01-19 + SIRI 1.3 Drop use of As Flat Groups for DatedCalls. + + 2012-03-23 + Factor out fropm ProductionTimetable package + +SIRI v2.0 Add ServiceJourneyInterchange (i.e. Monitored Connection) + [VDV] Add additional times to TargetedServiceInterchange MinimumTransferTime, MaximimTransferTime, StandardTransferTime, MaximumAUtomaticWaitTime, StandardWaitTime. + [VDV] Add Public and Contact Details to JourneyInfo + [VDV] Add AimedLatestPassengerAccessTime to TargetedCall + + + 2013-02-11 + SIRI v2.0 Modified ServiceJourneyInterchange SIRI:PT + + +

      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/schema/2.0/xsd/siri_model/}siri_datedVehicleJourney.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG XML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI_PT XML schema. Service Interface for Real-time Information. Production Timetable Service. + Standard +       +       + SIRI-Model Dated Vehicle Joruney. +       + + + + + + A planned VEHICLE JOURNEY taking place on a particular date. + + + + + Type for Planned VEHICLE JOURNEY (Production Timetable Service). + + + + + Identifier for a VEHICLE JOURNEY. + + + + + + + + + + + + + Complete sequence of stops along the route path, in calling order. + + + + + + + + + + Relations of the journey with other journeys, e.g., in case a joining/splitting takes place or the journey substitutes for another one etc. + + + + + + + + Type for previously planned VEHICLE JOURNEY that is removed from the data producer when using incremental updates. +SIRI v2.1 + + + + + A reference to the DATED VEHICLE JOURNEY from a previous PT delivery that is removed by the data producer. + + + + + Optionally identify the VEHICLE JOURNEY indirectly by origin and destination and the scheduled times at these stops. + + + + + TRAIN NUMBERs for journey. + + + + + + TRAIN NUMBER assigned to VEHICLE JOURNEY. + + + + + + + + + + + General info elements that apply to all journeys of timetable version unless overriden. + + + + + Description of the origin stop (vehicle signage) to show on vehicle, Can be overwritten for a journey, and then also section by section by the entry in an Individual Call. (+SIRI 2.0) + + + + + Description of the 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. (Unbounded since SIRI 2.0) + + + + + Additional Text associated with LINE. (Unbounded since SIRI 2.0) + + + + + Whether journey is first or last jouurney of day. +SIRI v2.0 + + + + + + + If the journey is an alteration to a timetable, indicates the original journey, and the nature of the difference. + + + + + Use of simple reference is deprecated + + + + Refecence to a VEHICLE JOURNEY framed by the day. SIRI 2.0 + + + + + + + + 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 cancellation of a journey in the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the journey is not cancelled. + + + + + + + + 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 SERVICE JOURNEY INTERCHANGE between two journeys. +SIRI v2.0 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + A planned SERVICE JOURNEY INTERCHANGE from a journey. +SIRI v2.0 + + + + + + + + + + + + + + + + + + + + + + + + + + + A planned SERVICE JOURNEY INTERCHANGE to a journey. +SIRI v2.0 + + + + + + + + + + + + + + + + + + + + + + + + + + + A planned SERVICE JOURNEY INTERCHANGE between two journeys. +SIRI v2.0 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Type for a previously planned SERVICE JOURNEY INTERCHANGE that a data producer wants to silently remove from the plan (because it is erroneous data). Careful: Removal is different from Cancellation. +SIRI v2.1 + + + + + + + + + + + + + + + + + + + + + + + + + + Time Elements for SERVICE JOURNEY INTERCHANGE. + + + + + Elements for INTERCHANGE WAIT TIME. + + + + + + + + Elements for INTERCHANGE TRANSFER duration. + + + + + Standard transfer duration for INTERCHANGE. SIRI v2,0 + + + + + Minimum transfer duration for INTERCHANGE. SIRI v2,0 + + + + + Maximum transfer duration for INTERCHANGE. SIRI v2,0 + + + + + + + Elements for INTERCHANGE WAIT TIME. + + + + + Standard wait time for INTERCHANGE. SIRI v2,0 + + + + + Maximum time that Distributor will wait for Feeder for INTERCHANGE. SIRI v1.0 + + + + + Maximum automatic wait time that Distributor will wait for Feeder for INTERCHANGE. +SIRI v2.0 + + + + + + + + Complete sequence of stops along the route path, in calling order. + + + + + Type for Planned VEHICLE JOURNEY Stop (Production Timetable Service). + + + + + + + Whether this DATED CALL is an addition to the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to false: the journey is not an addition. + + + + + Whether this DATED CALL is a cancellation of a previously announced call (or planned according to the long-term timetable). Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the journey is not cancelled. + + + + + + + Text annotation that applies to this call. + + + + + + + Information on any planned distributor connections (deprecated from SIRI V2.0 ... see 2 next attributes) + + + + + Information on any planned feeder connections. SIRI 2.0 + + + + + Information on any planned distributor connections. SIRI 2.0 + + + + + + + + + Planned Connection between two VEHICLE JOURNEYs. + + + + + + + Reference to a (dated) distributor VEHICLE JOURNEY. + + + + + + Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY 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. + + + + + + + + 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. + + + + + + + + + Connection between two stops within a connection area. Used within the context of one or other end. + + + + + Identifier of CONNECTION LINk. + + + + + + + + + + Times for making SERVICE JOURNEY INTERCHANGE. + + + + + Default time (Duration) needeed to traverse SERVICE JOURNEY INTERCHANGE from feeder to distributor. + + + + + Time needeed by a traveller whis is familiar with SERVICE JOURNEY INTERCHANGE to traverse it. If absent, use DefaultDuration. + + + + + Time needeed by a traveller whis is not familiar with SERVICE JOURNEY INTERCHANGE to traverse it. If absent, use DefaultDuration and a standard weighting. + + + + + Time needeed by a traveller wos is mobility impaired to traverse SERVICE JOURNEY INTERCHANGE. If absent, use DefaultDuration and a standard impaired travel speed. + + + + + + + Properties of SERVICE JOURNEY INTERCHANGE. + + + + + Whether the passenger can remain in VEHICLE (i.e. BLOCKlinking). Default is 'false': the passenger must change vehicles for this connection. + + + + + Whether the SERVICE JOURNEY INTERCHANGE is guaranteed. Default is 'false'; SERVICE JOURNEY INTERCHANGE is not guaranteed. + + + + + Whether the SERVICE JOURNEY 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. + + + + + + + + Identifier of SERVICE JOURNEY INTERCHANGE. +SIRI v2.0 + + + + + Whether this interchange is an addition to the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the interchange is not an addition. +SIRI v2.1 + + + + + Whether this interchange is a cancellation of a previously announced interchange (or planned according to the long-term timetable. +Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the interchange is not cancelled. +SIRI v2.1 + + + + + + The data producer must provide a reason, e.g. type of error and description, in case he wants to silently remove (instead of cancel) a journey or an interchange from the plan. +SIRI v2.1 + + + + + Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 + + + + + SCHEDULED STOP POINT at which feeder journey arrives. +SIRI v2.0 + + + + + Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. + + + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. +ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 + + + + + Planned time at which feeder VEHICLE is scheduled to arrive. SIRI v2.1 + + + + + Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 + + + + + SCHEDULED STOP POINT at which distributor journet departs. +SIRI v2.0 + + + + + Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. + + + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. +ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 + + + + + Planned time at which distributor VEHICLE is scheduled to depart. SIRI v2.1 + + + +       diff --git a/xsd/siri_model/siri_estimatedVehicleJourney.xsd b/xsd/siri_model/siri_estimatedVehicleJourney.xsd index fc94b83c..88933aa7 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney.xsd @@ -1,472 +1,472 @@ - - - - - - main schema - e-service developers - CEN TC278 WG3 SG7 Team - Werner Kohl MDV - Europe - Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2003-02-10 - - - 2004-10-31 - - - 2005-02-14 - - - 2005-02-20 - - - 2005-05-11 - - - 2007-04-17 - - - - 2008-03-26 - - - - 2008-11-17 - - - - 2011-01-19 - - - - 2012-03-23 - - - -

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

      -

      This sub-schema describes the Estimated Timetable Service.

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

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

      +

      This sub-schema describes the Estimated Timetable Service.

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

      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/schema/2.0/xsd/siri_model/}siri_facility.xsd - [ISO 639-2/B] ENG - CEN - - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from TransModel and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Common Facility Elements - Standard -       -       - SIRi Facility model elemenys -       - - - - - - - - - - - - - - - - - Type for identifier of a Faclility. - - - - - - Reference to a Facility. - - - - - Type for reference to a Faclility. - - - - - - - - - - Type for description of the MONITORED FACILITY itself. - - - - - Identfier of Facility. - - - - - Textual description of the facility. (Unbounded since SIRI 2.0) - - - - - 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 the 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 category of a facility. - - - - - - - - - - - - - - - - - - Summary information about Facility. Used in DISCOVERY. - - - - - - Whether real-time data is available for the stop. Default is 'true'. - - - - - Description of the facility (without its status) - - - - - - - - Allowed values for the status of a MONITORED FACILITY. - - - - - - - - - - - - - Allowed values for changes to the status of a facility. - - - - - - - - - - Allowed values for TypeOfCounting. - - - - - - - - - - - - - - - Allowed values for trend of a counting. - - - - - - - - - - - - - - - - Allowed values for units of what is counted - bay: parking bay for cars, bicycle, scooter, etc - otherSpaces: any other kind of spaces: lockers, standing spaces, toilets, etc. - devices: electronic devices (audio guide, headphones, etc.) and physical devices (walking stick, wheelchair, etc.) - vehicles: any type of vehicles (cycle, car, scooter, hoverboard, motorbike, etc.) - kW (kiloWatt) or kWh (kiloWatt-hour): means that an available or consumed power is measured - mAh (milliAmpere per hour): typically used for battery charging level - litres and cubicMeters: means that a volume is measured - squareMeters: means that a surface is measured - meters: means that a distance is measured - kg (kilogram): means that a mass is measured - A (Ampere): means that an electric current is measured - C (degree Celsius): means that a temperature is measured - other: use of "other" requires the additional open ended TypeOfCountedFeature (monitoredCountingStructure) to be filled - - - - - - - - - - - - - - - - - - - - - - - - - Description of the status of a MONITORED FACILITY. - - - - - Status of the facility. - - - - - Description of the facility Status. (Unbounded since SIRI 2.0) - - - - - Accessibility of the facility. - - - - - - - - Location of the MONITORED FACILITY. - - - - - Group of Facility accessibility elements. - - - - - Group of Facility accessibility elements. - - - - - - - - Monitored counted values. - - - - - Nature of what is counted. - - - - - Unit of type for what is being counted - - - - - Open ended type or refined classification of what is counted (complement to the information coming from the facility type itself) - - - - - - Counted value - - - - - Value as a percentage (0.0 to 100.0) of the maximum possible value - - - - - - Trend of the count - - - - - Accuracy of the count, as a percentage (0.0 to 100.0), the percentage being a + or - maximum deviation from the provided value - - - - - Description of what is counted - - - - - List of the IDs of the counted items: usefull mainly for reservation and detailed information purposes - - - - - - IDs of a counted item - - - - - - - - - - - - Description of any change concerning a MONITORED FACILITY New structure defined in SIRI XSD 1.1 for Facilities Management. - - - - - Description of any change concerning a MONITORED FACILITY New structure defined in SIRI XSD 1.1 for Facilities Management. - - - - - - Facility affected by condition. - - - - - - - Status of Facility. - - - - - - - - - - - - New position of the Facility referenced by the FacilityRef or described in the FacilityStructure - - - - - - 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. - - - - - - - - - Allowed values for actions to remedy a facility 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. (Unbounded since SIRI 2.0) - - - - - Validity period for the remedy - - - - - - - - - - Allowed values for the monitoring conditions (frequency of measurement, etc): an automatic monitoring of the status of a lift with pushed alert in case of incident is very different from a daily manual/visual check. - - - - - Mean time interval between two measurements. - - - - - How monitoring is automatic, manual, etc. - - - - - When the monitoring is in effect. If absent always. - - - - - - - - Allowed values for the types of monitoring: automatic or manual - describing the hardware transducer (video, GPS/Radio, in-road sensors, etc.) doesn't seeme useful for SIRI. - - - - - - - - - - Allowed values for the type for Description of the monitoring conditions (frequency of mesurement, etc): an automatic monitoring of the status of a lift with pushed alert in case of incident is very different from a daily manual/visual check. - - - - - Date and tme 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. - - - - - - - - A change to the availaibility of EQUIPMENT. Basic structure defined in the first 1.0 SIRI XSd. - - - - - Type for Availaibility Change of EQUIPMENT. - - - - - Reference to an EQUIPMENT. - - - - - Description of EQUIPMENT. (Unbounded since SIRI 2.0) - - - - - Reference to a TYPE OF EQUIPMENT. - - - - - Period for which change to EQUIPMENT status applies applies. If omitted, indefinite period. - - - - - Availability status of the EQUIPMENT. Default is 'notAvailable'. - - - - - 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. - - - - - - - - - Type for 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 or more MobilityFacility instances to specify which types of mobility access are available (true) or not available (false). For example suitableForWheelChair, or stepFreeAccess. - - - - - Classification of Mobility Facility type - Based on Tpeg pti23. - - - - - - - Elements describing nature of disruption. - - - - - Information about a change of the formation (e.g. TRAIN composition) or changes of vehicles within the formation. +SIRI v2.1 - - - - - Information about a change of Equipment availability at stop or on vehicle that may affect access or use. - - - - - This sequence is here only for compatibility reasons between Siri 1.0 and Siri 1.1 - - - - - - - - - - Classification of vehicle energy type. See Transmodel TypeOfFuel. +SIRI v2.1 - - - - - Values for vehicle fuel type. Use of 'other' requires the additional open ended OtherTypeOfFuel to be filled. - - - - - An arbitrary vehicle fuel classification. - - - - -       + + + + + + 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 + + + + 2012-03-23 + + + +

      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/schema/2.0/xsd/siri_model/}siri_facility.xsd + [ISO 639-2/B] ENG + CEN + + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from TransModel and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Common Facility Elements + Standard +       +       + SIRi Facility model elemenys +       + + + + + + + + + + + + + + + + + Type for identifier of a Faclility. + + + + + + Reference to a Facility. + + + + + Type for reference to a Faclility. + + + + + + + + + + Type for description of the MONITORED FACILITY itself. + + + + + Identfier of Facility. + + + + + Textual description of the facility. (Unbounded since SIRI 2.0) + + + + + 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 the 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 category of a facility. + + + + + + + + + + + + + + + + + + Summary information about Facility. Used in DISCOVERY. + + + + + + Whether real-time data is available for the stop. Default is 'true'. + + + + + Description of the facility (without its status) + + + + + + + + Allowed values for the status of a MONITORED FACILITY. + + + + + + + + + + + + + Allowed values for changes to the status of a facility. + + + + + + + + + + Allowed values for TypeOfCounting. + + + + + + + + + + + + + + + Allowed values for trend of a counting. + + + + + + + + + + + + + + + + Allowed values for units of what is counted + bay: parking bay for cars, bicycle, scooter, etc + otherSpaces: any other kind of spaces: lockers, standing spaces, toilets, etc. + devices: electronic devices (audio guide, headphones, etc.) and physical devices (walking stick, wheelchair, etc.) + vehicles: any type of vehicles (cycle, car, scooter, hoverboard, motorbike, etc.) + kW (kiloWatt) or kWh (kiloWatt-hour): means that an available or consumed power is measured + mAh (milliAmpere per hour): typically used for battery charging level + litres and cubicMeters: means that a volume is measured + squareMeters: means that a surface is measured + meters: means that a distance is measured + kg (kilogram): means that a mass is measured + A (Ampere): means that an electric current is measured + C (degree Celsius): means that a temperature is measured + other: use of "other" requires the additional open ended TypeOfCountedFeature (monitoredCountingStructure) to be filled + + + + + + + + + + + + + + + + + + + + + + + + + Description of the status of a MONITORED FACILITY. + + + + + Status of the facility. + + + + + Description of the facility Status. (Unbounded since SIRI 2.0) + + + + + Accessibility of the facility. + + + + + + + + Location of the MONITORED FACILITY. + + + + + Group of Facility accessibility elements. + + + + + Group of Facility accessibility elements. + + + + + + + + Monitored counted values. + + + + + Nature of what is counted. + + + + + Unit of type for what is being counted + + + + + Open ended type or refined classification of what is counted (complement to the information coming from the facility type itself) + + + + + + Counted value + + + + + Value as a percentage (0.0 to 100.0) of the maximum possible value + + + + + + Trend of the count + + + + + Accuracy of the count, as a percentage (0.0 to 100.0), the percentage being a + or - maximum deviation from the provided value + + + + + Description of what is counted + + + + + List of the IDs of the counted items: usefull mainly for reservation and detailed information purposes + + + + + + IDs of a counted item + + + + + + + + + + + + Description of any change concerning a MONITORED FACILITY New structure defined in SIRI XSD 1.1 for Facilities Management. + + + + + Description of any change concerning a MONITORED FACILITY New structure defined in SIRI XSD 1.1 for Facilities Management. + + + + + + Facility affected by condition. + + + + + + + Status of Facility. + + + + + + + + + + + + New position of the Facility referenced by the FacilityRef or described in the FacilityStructure + + + + + + 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. + + + + + + + + + Allowed values for actions to remedy a facility 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. (Unbounded since SIRI 2.0) + + + + + Validity period for the remedy + + + + + + + + + + Allowed values for the monitoring conditions (frequency of measurement, etc): an automatic monitoring of the status of a lift with pushed alert in case of incident is very different from a daily manual/visual check. + + + + + Mean time interval between two measurements. + + + + + How monitoring is automatic, manual, etc. + + + + + When the monitoring is in effect. If absent always. + + + + + + + + Allowed values for the types of monitoring: automatic or manual - describing the hardware transducer (video, GPS/Radio, in-road sensors, etc.) doesn't seeme useful for SIRI. + + + + + + + + + + Allowed values for the type for Description of the monitoring conditions (frequency of mesurement, etc): an automatic monitoring of the status of a lift with pushed alert in case of incident is very different from a daily manual/visual check. + + + + + Date and tme 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. + + + + + + + + A change to the availaibility of EQUIPMENT. Basic structure defined in the first 1.0 SIRI XSd. + + + + + Type for Availaibility Change of EQUIPMENT. + + + + + Reference to an EQUIPMENT. + + + + + Description of EQUIPMENT. (Unbounded since SIRI 2.0) + + + + + Reference to a TYPE OF EQUIPMENT. + + + + + Period for which change to EQUIPMENT status applies applies. If omitted, indefinite period. + + + + + Availability status of the EQUIPMENT. Default is 'notAvailable'. + + + + + 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. + + + + + + + + + Type for 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 or more MobilityFacility instances to specify which types of mobility access are available (true) or not available (false). For example suitableForWheelChair, or stepFreeAccess. + + + + + Classification of Mobility Facility type - Based on Tpeg pti23. + + + + + + + Elements describing nature of disruption. + + + + + Information about a change of the formation (e.g. TRAIN composition) or changes of vehicles within the formation. +SIRI v2.1 + + + + + Information about a change of Equipment availability at stop or on vehicle that may affect access or use. + + + + + This sequence is here only for compatibility reasons between Siri 1.0 and Siri 1.1 + + + + + + + + + + Classification of vehicle energy type. See Transmodel TypeOfFuel. +SIRI v2.1 + + + + + Values for vehicle fuel type. Use of 'other' requires the additional open ended OtherTypeOfFuel to be filled. + + + + + An arbitrary vehicle fuel classification. + + + + +       diff --git a/xsd/siri_model/siri_feature_support.xsd b/xsd/siri_model/siri_feature_support.xsd index a5a88e83..f553ac1d 100644 --- a/xsd/siri_model/siri_feature_support.xsd +++ b/xsd/siri_model/siri_feature_support.xsd @@ -1,145 +1,145 @@ - - - - - - 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 - - - 2012-03-22 - - - -

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

      -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_feature.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIG CML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Common DomainModel elements. - Standard -       -       -       - - - - Type for identifier of a TYPE OF PRODUCT CATEGORY. - - - - - - Type for reference to a TYPE OF PRODUCT CATEGORY. - - - - - - - - - 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. - - - - - Type for reference to a ServiceCategory. - - - - - - - - - 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. - - - - - - 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. - - - - - 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. - - - - - - Type for reference to a Feature Code. - - - - - - -       + + + + + + 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 + + + 2012-03-22 + + + +

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

      +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_feature.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG CML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Common DomainModel elements. + Standard +       +       +       + + + + Type for identifier of a TYPE OF PRODUCT CATEGORY. + + + + + + Type for reference to a TYPE OF PRODUCT CATEGORY. + + + + + + + + + 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. + + + + + Type for reference to a ServiceCategory. + + + + + + + + + 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. + + + + + + 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. + + + + + 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. + + + + + + Type for reference to a Feature Code. + + + + + + +       diff --git a/xsd/siri_model/siri_interchangeJourney.xsd b/xsd/siri_model/siri_interchangeJourney.xsd index 06d08c2e..4a092281 100644 --- a/xsd/siri_model/siri_interchangeJourney.xsd +++ b/xsd/siri_model/siri_interchangeJourney.xsd @@ -1,88 +1,88 @@ - - - - - - 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 - 2012-03-29 - Factored out of conection timnetable servcie - - 2012-03-20 - +SIRI v2.0 - - -

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

      -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/siri/2.0/xsd/}siri_connectionTimetable_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - -SIRI-CT Interchange journey for Service Interface for Real-time Information. Connection Timetable Service. - Standard -       -       - SIRI-CT Interchange journey Connection Timetable Service. -       - - - - - - Type for feeder or Distributor Journey info about a VEHICLE JOURNEY. - - - - - - - - - - Whether there is real-time information available for journey. Default is 'true'. - - - - - On a Distributor journey, a timetabled departure time of the VEHICLE JOURNEY from the CONNECTION LINK for the SERVICE JOURNEY INTERCHANGE. On a Feeder journey a Timetabled arrival time of the VEHICLE JOURNEY at the CONNECTION link for the SERVICE JOURNEY INTERCHANGE. - - - - - - -       + + + + + + 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 + 2012-03-29 + Factored out of conection timnetable servcie + + 2012-03-20 + +SIRI v2.0 + + +

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

      +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/siri/2.0/xsd/}siri_connectionTimetable_service.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG XML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + -SIRI-CT Interchange journey for Service Interface for Real-time Information. Connection Timetable Service. + Standard +       +       + SIRI-CT Interchange journey Connection Timetable Service. +       + + + + + + Type for feeder or Distributor Journey info about a VEHICLE JOURNEY. + + + + + + + + + + Whether there is real-time information available for journey. Default is 'true'. + + + + + On a Distributor journey, a timetabled departure time of the VEHICLE JOURNEY from the CONNECTION LINK for the SERVICE JOURNEY INTERCHANGE. On a Feeder journey a Timetabled arrival time of the VEHICLE JOURNEY at the CONNECTION link for the SERVICE JOURNEY INTERCHANGE. + + + + + + +       diff --git a/xsd/siri_model/siri_journey.xsd b/xsd/siri_model/siri_journey.xsd index 3371c55c..6f240fa8 100644 --- a/xsd/siri_model/siri_journey.xsd +++ b/xsd/siri_model/siri_journey.xsd @@ -1,1903 +1,1903 @@ - - - - - - main schema - e-service developers - Cen TC278 WG3 SG7 Team - Europe - Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2004-03-05 - - - 2004-10-06 - - - 2005-05-11 - - - 2005-11-15 - - - 2007-03-29 - - - 2008-11-13 - - - - 2011-04-18 - - - - 2012-03-22 - - - - 2012-04-27 - - - - 2013-01-25 - - - - 2013-02-11 - - - - 2014-06-20 - - - -

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

      -

      This subschema defines common journey elements.

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri/}siri_journey.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd - - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIG CML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of common Journey elements - Standard -       -       - SIRI Common Journey Model. -       - - - - - - - - - - - - - - - - Elements describing a VEHICLE JOURNEY. Values for these elements can be specified on an annual schedule and will be inherited, unless overriden, onto the production timetable and then onto the individul DATED VEHICLE JOURNEYs of the timetable. Each real-time journey (e.g. ESTIMATED VEHICLE JOURNEY or MONITORED VEHICLE JORUNEY) takes its values from the DATED VEHICLE JOURNEY that it follows. The absence of a value on an entity at a given level indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity. - - - - - For train services with named journeys. Train name, e.g. “West Coast Express”. If omitted: No train name. Inherited property. (Unbounded since SIRI 2.0) - - - - - - Contact details for use by members of public. +SIRI v2.0 - - - - - Contact details for use by operational staff. +SIRI v2.0 - - - - - - - Type for Simple Contact Details. - - - - - Phone number +SIRI v2.0 - - - - - Url for contact +SIRI v2.0 - - - - - - - - Common information about a VEHICLE JOURNEY. (Similar to VDV TripInfo) - - - - - - - - - - - End names for journey. - - - - - - Name of the origin of the journey. (Unbounded since SIRI 2.0) - - - - - Short name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as Origin Name. - - - - - DIRECTION name shown for jurney at the origin. +SIRI v2.0 - - - - - Names of VIA points, used to help identify the LINE, for example, Luton to Luton via Sutton. Currently 3 in VDV. Should only be included if the detail level was requested. - - - - - Reference to a DESTINATION. - - - - - Description of the destination stop (vehicle signage), Can be overwritten for a journey, and then also section by section by the entry in an individual CALl. (Unbounded since SIRI 2.0) - - - - - Short name of the DESTINATION.of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as DestinationName. (Unbounded since SIRI 2.0) - - - - - Origin name shown for jourey at the destination +SIRI v2.0 - - - - - - - Type for VIA NAMes structure. - - - - - - - Relative priority to give to VIA name in displays. 1=high. Default is 2. +SIRI v2.0 - - - - - - - - - - Type for Information about a DESTINATION. - - - - - Identifer of Destinatioin - - - - - Name of Destination - - - - - - - The name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. - - - - - Names of VIA points, used to help identify the LINEfor example, Luton to Luton via Sutton. Currently 3 in VDV. Should only be included if the detail level was requested. - - - - - The name of the DESTINATION of the journey; used to help identify the VEHICLE to the public. Note when used in a CALL, this is the Dynamic Destination Display: since vehicles can change their destination during a journey, the destination included here should be what the VEHICLE will display when it reaches the stop. - - - - - - Call times for journey. - - - - - Whether this is a Headway Service, that is shown as operating at a prescribed interval rather than to a fixed timetable. Default is 'false'. - - - - - Timetabled departure time from Origin. - - - - - Timetabled arrival time at Destination. - - - - - - - - Whether journey is first or last journey of day. +SIRI v2.0 - - - - - Additional descriptive text associated with journey. Inherited property. - - - - - Description of a DIRECTION. - - - - - Type for DIRECTION. - - - - - Identifer of DIRECTION, - - - - - Description of DIRECTION. (Unbounded since SIRI 2.0) - - - - - - - - Operational information about the monitored VEHICLE JOURNEY. - - - - - - - - Refercence to other VEHICLE Journeys (+SIRI v2.0) - - - - - A reference to the DRIVER or Crew currently logged in to operate a monitored VEHICLE. May be omitted if real-time data is not available - i.e. it is timetabled data. +SIRI v2.0 - - - - - The name oo the Driver or Crew +SIRI v2.0 - - - - - - - Operational information about the monitored VEHICLE JOURNEY. - - - - - - - - - Operational information about the monitored VEHICLE JOURNEY. - - - - - BLOCK that VEHICLE is running. - - - - - COURSE OF JOURNEY ('Run') that VEHICLE is running. - - - - - - - Type for Progress between stops. - - - - - The total distance in metres between the previous stop and the next stop. - - - - - Percentage along link that VEHICLE has travelled. - - - - - - - - - Type for Abstract CALL at stop. - - - - - - - - - Elements describing the targeted CALL of a VEHICLE at a stop. - - - - - - - - - - - Elements describing the arrival of a VEHICLE at a stop. - - - - - - - - Assignment of planned arrival at scheduled STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. +SIRI v2.0. - - - - - - - - - Elements describing the departure of a VEHICLE from a stop. - - - - - - - - - - - - - - Type for Abstract CALL at stop. - - - - - - - - Elements describing the arrival status of a VEHICLE at a stop. - - - - - - - - - - Assignment of planned, expected and/or recorded arrival at STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. +SIRI v2.0. - - - - - - - - - - Elements describing the departure status of a VEHICLE from a stop. - - - - - - - - - - - - - - - - - - - Elements describing the CALL Properties Values for these elements can be specified on an production VEHICLE JOURNEY CALL. Each real-time journey CALL takes its values from the corresponding dated VEHICLE JOURNEY CALL. The absence of a value on an real-time CALL l indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity. - - - - - - Whether this is a Hail and Ride Stop. Default is 'false'. - - - - - Whether Vehicle stops only if requested explicitly by passenger. Default is 'false'. - - - - - Origin to show for the VEHICLE at the specific stop (vehicle signage), if different to the Origin Name for the full journey. (+Siri 2.0) - - - - - Destination to show for the VEHICLE at the specific stop (vehicle signage), if different to the Destination Name for the full journey. - - - - - - - Annotations of the CALL. - - - - - Text annotation that applies to this CALL. - - - - - - - - Type for CALLing pattern for JOURNEY PATTERN. - - - - - - - - Type Onwards CALLs at stop. - - - - - - - - - - - - - - - - - Elements describing the CALL. Values for these elements can be specified on an production VEHICLE JOURNEY CALL. Each real-time journey CALL takes its values from the corresponding dated VEHICLE JOURNEY CALL. The absence of a value on an real-time CALL l indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity. - - - - - - - - - - - - - - Elements for Arrival in onward CALl. - - - - - - - - - Latest time at which a VEHICLE will arrive at stop. +SIRI v2.1 - - - - - Prediction quality, either as approximate level, or more quantitative percentile range of predictions that will fall within a given range of times. +SIRI v2.0 - - - - - - If the producer is (temporarily) not able to deliver real-time predictions (e.g. because of a connection loss), he has various options (and combinations of them) to inform the consumer: -(i) set Monitored to 'false' -(ii) transmit ExpectedArrivalTime together with "PredictionInaccurate=true" -(iii) drop/omit ExpectedArrivalTime -(iv) set ArrivalStatus to 'noReport' -However, this might introduce ambiguity: e.g. option (iii) might be interpreted as "on time" by one consumer, but also as "indefinite delay" by another consumer. -To avoid this, the producer should transmit xxxPredictionUnknown instead of any expected times. +SIRI v2.1 - - - - - - - - Elements for departure in ONWARD CALL. - - - - - - - - - Expected departure time of VEHICLE without waiting time due to operational actions. For people at stop this would normally be shown if different from Expected departure time. So if servcie decides not to wait may leave earler than expected departure time +SIRI v2.0. - - - - - Earliest time at which VEHICLE may leave the stop. Used to secure connections. Used for passenger announcements. Passengers must be at boarding point by this time to be sure of catching VEHICLE. i.e. "Vehicle will not leave before this time" - may be revised from original aimed time. +SIRI v2.0 - - - - - Prediction quality, either as approximate level, or more quantitative percentile range of predictions that will fall within a given range of times. +SIRI v2.0 - - - - - - If the producer is (temporarily) not able to deliver real-time predictions (e.g. because of a connection loss), he has various options (and combinations of them) to inform the consumer: -(i) set Monitored to 'false' -(ii) transmit ExpectedDepartureTime together with "PredictionInaccurate=true" -(iii) drop/omit ExpectedDepartureTime -(iv) set DepartureStatus to 'noReport' -However, this might introduce ambiguity: e.g. option (iii) might be interpreted as "on time" by one consumer, but also as "indefinite delay" by another consumer. -To avoid this, the producer should transmit xxxPredictionUnknown instead of any expected times. +SIRI v2.1 - - - - - - - - Elements describing the HEADWAY INTERVALs. - - - - - - - - - Elements describing the distance from the stop of a VEHICLE. +SIRI v2.0. - - - - - Distance of VEHICLE from stop of CALL as measured along ROUTE track. Only shown if detail level is 'calls' or higher. Positive value denotes distance before stop. +SIRI v2.0. - - - - - Count of stops along SERVICE PATTERN between current position of VEHICLE and stop of CALL as measured along ROUTE track. Only shown if detail level is 'calls' or higher. +SIRI v2.0. - - - - - - - Type for Prediction Quality quantifcation. - - - - - An approxiimate characterisation of prediction quality as one of five values. +SIRI v2.0 - - - - - - Percentile associated with range as specified by lower and upper bound. +SIRI v2.0 - - - - - Lower bound on time of prediction for confidence level if different from defaults. +SIRI v2.0 - - - - - Upper bound on time of prediction for confidence level if different from defaults. +SIRI v2.0 - - - - - - - - - Area that encompasses the scheduled flexible stop locations according to the planned timetable. +SIRI v2.1 - - - - - Reference to the scheduled location or flexible area. +SIRI v2.1 - - - - - Name or description (e.g. address) of the scheduled location or flexible area. +SIRI v2.1 - - - - - - Elements for location of flexible stops or service that allows pickup anywhere in a designated area. +SIRI v2.1 - - - - - - - - Area that encompasses the expected flexible stop locations according to the real-time prediction. - - - - - - Name or description (e.g. address) of the expected location or flexible area. - - - - - Area that encompasses the actually recorded flexible stop locations. - - - - - - Name or description (e.g. address) of the actually recorded location or flexible area. - - - - - - - - Elements for assignment of a SCHEDULED STOP POINT to a specific QUAY or platform. +SIRI v2.1 - - - - - Physical QUAY to use according to the planned timetable. +SIRI v2.0 - - - - - Scheduled Platform name. Can be used to indicate platfrom change. +SIRI v2.0 - - - - - Physical QUAY to use according to the real-time prediction. +SIRI v2.0 - - - - - Expected Platform name. Can be used to indicate real-time prediction. +SIRI v2.1 - - - - - Physical QUAY actually used. +SIRI v2.0 - - - - - Actual Platform name. Can be used to indicate recorded platform. +SIRI v2.1 - - - - - - - - - Elements for assignment of a SCHEDULED STOP POINT to a specific BOARDING POSITION or location on a QUAY. +SIRI v2.1 - - - - - Physical BOARDING POSITION to use according to the planned timetable. - - - - - Scheduled BOARDING POSITION name. Can be used to indicate boarding position change. - - - - - Physical BOARDING POSITION to use according to the real-time prediction. - - - - - Expected BOARDING POSITION name. Can be used to indicate real-time prediction. - - - - - Actually recorded BOARDING POSITION. Can be used to indicate the actually used boarding position. - - - - - Recorded BOARDING POSITION name. Can be used to indicate the actually used boarding position. - - - - - - - - Type for assignment of a SCHEDULED STOP POINT to a physical location, in particular to a QUAY or BOARDING POSITION. +SIRI v2.0. - - - - - - - - - - - - - Type for assignment of a SCHEDULED STOP POINT to a physical location, in particular to a QUAY or BOARDING POSITION, according to the planned timetable. +SIRI v2.0. - - - - - - - Physical QUAY to use according to the planned timetable. +SIRI v2.0 - - - - - Scheduled Platform name. +SIRI v2.0 - - - - - - - - Physical BOARDING POSITION to use according to the planned timetable. +SIRI v2.1 - - - - - Scheduled BOARDING POSITION name. +SIRI v2.1 - - - - - - - - - - - - - Indicates the type of a nested QUAY in case of detailed STOP PLACE models. -A QUAY may be part of a group of QUAYs, or may be divided into sectors, i.e., smaller sub-QUAYs. +SIRI v2.1 - - - - - - Whether the prediction for a specific stop or the whole journey is considered to be of a useful accuracy or not. Default is 'false', i.e. prediction is considered to be accurate. -If prediction is degraded, e.g. because of a situation, PredictionInaccurate is used to indicate a lowered quality of data. Inherited property. PredictionInaccurate can be used in combination with InCongestion, but is more general. - - - - - Can be used to inform the passenger about the reason for a change of the prediction (in)accuracy in case PredictionInaccurate is set to 'true'. +SIRI v2.1 - - - - - An approximate figure of how occupied the journey is after departing from a given stop, e.g. 'manySeatsAvailable' or 'standingRoomOnly'. If omitted: Passenger load is unknown. -Occupancies and capacities for individual VEHICLEs, e.g. parts of a COMPOUND TRAIN, can also be specified in more detail for the departure on CALL level. - - - - - - Target arrival time of VEHICLE at stop according to latest working timetable. - - - - - Observed time of arrival of VEHICLE at stop. - - - - - Estimated time of arriival of VEHICLE at stop . - - - - - Classification of the timeliness of the visit according to a fixed list of values. If not specified, same as DepartureStatus. - - - - - Text annotation to be used in cases where ArrivalStatus is set to 'cancelled'. +SIRI v2.1 - - - - - Arbitrary text string to show to indicate the status of the departure of the VEHICLE for example, “Enroute”, “5 Km”, “Approaching”. May depend on the policy of the OPERATOR, for example show “Approaching” if less than 200metres away from stop. +SIRI v2.0 - - - - - Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicle to arrive at. -Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is: -(i) any arrival platform on any related dated timetable element, -(ii) any departure platform name on this estimated element; -(iii) any departure platform name on any related dated timetable CALL. - - - - - Type of boarding and alighting allowed at stop. Default is 'Alighting'. - - - - - Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). If not given, assume same as for departure. +SIRI v2.1 - - - - - Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. +SIRI v2.1 -Examples: -- "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle arriving at sector A first when approaching the QUAY with sectors A-B-C-D. If the arriving vehicle is represented as an arrow, "towards A" would be abstracted as "=> A-B-C-D". -- "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle arriving at this reference point first when approaching the QUAY. If the arriving vehicle is represented as an arrow, "towards 0" would be abstracted as "=> 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). -It is advised to specify a reference point that is meaningful for passengers on location. - - - - - - OPERATORs of of service up until arrival. May change for departure. +SIRI v2.0. - - - - - - Arrival times for CALL. - - - - - - - - - - - - - Target departure time of VEHICLE from stop according to latest working timetable. - - - - - Observed time of departure of VEHICLE from stop. - - - - - Estimated time of departure of VEHICLE from stop, most likely taking into account all control actions such as waiting. - - - - - Latest target time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. +SIRI 2.0 - - - - - Latest expected time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. +SIRI 2.0 - - - - - Classification of the timeliness of the departure part of the CALL, according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are still classified as on-time. Applications may use this to guide their own presentation of times. - - - - - Text annotation to be used in cases where DepartureStatus is set to 'cancelled'. +SIRI v2.1 - - - - - Arbitrary text string to show to indicate the status of the departure of the vehicle, for example, “Boarding”, “GatesClosed”. +SIRI v2.0 - - - - - Departure QUAY (bay or platform) name. Default taken from planned timetable. - - - - - Nature of boarding allowed at stop. Default is 'Boarding'. - - - - - Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). +SIRI v2.1 - - - - - Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. +SIRI v2.1 -Examples: -- "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle departing in the direction of sector A on a QUAY with sectors A-B-C-D. If the departing vehicle is represented as an arrow, "towards A" would be abstracted as "<= A-B-C-D". -- "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle departing in the direction of this reference point. If the departing vehicle is represented as an arrow, "towards 0" would be abstracted as "<= 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). -It is advised to specify a reference point that is meaningful for passengers on location. - - - - - Real-time occupancies of a VEHICLE and reservations after departing from a given stop. +SIRI v2.1 - - - - - Real-time capacities (number of available seats) of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. +SIRI v2.1 - - - - - OPERATORs of service for departure and onwards. May change from that for arrival. +SIRI v2.0. - - - - - Recorded occupancies of a VEHICLE and reserved seats after departing from a given stop. +SIRI v2.1 - - - - - Recorded capacities of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. +SIRI v2.1 - - - - - - Departure times for CALL. - - - - - - - - - - - - Passenger arrival times at STOP PLACE in order to meet VEHICLE departure times for CALL. - - - - - - - - - - For frequency based services, target interval between vehicles at stop. - - - - - For frequency based services, expected interval between vehicles at stop. - - - - - For frequency based services, observed interval between vehicles at stop. - - - - - - Provides information about relations to other journeys. +SIRI v2.1 - - - - - - - - - - Specifies the type of the relation, e.g., joining, splitting, replacement etc. +SIRI v2.1 - - - - - - - - - Specifies which CALL or JOURNEY PART of the JOURNEY has a JOURNEY RELATION. +SIRI v2.1 - - - - - - Information about the stop at which the JOURNEY is related to another JOURNEY. +SIRI v2.1 - - - - - Information about the JOURNEY PARTs for which the JOURNEY has a JOURNEY RELATION. +SIRI v2.1 - - - - - - Information about related parts of JOURNEY. +SIRI v2.1 - - - - - - - - - - - The JOURNEY RELATION refers to this CALL. +SIRI v2.1 - - - - - - - - - - - - - The JOURNEY RELATION refers to this JOURNEY PART. +SIRI v2.1 - - - - - - - - Refers to the JOURNEY to which the current JOURNEY is related. +SIRI v2.1 - - - - - - - - - - - - - - - Groups relevant elements of the formation model that are used on JOURNEY level. -The TRAIN conceptual model represents VEHICLE TYPE properties that are peculiar to TRAINs. A TRAIN may comprise not just a single VEHICLE but a chain of carriages, TRAIN ELEMENTS, assembled as TRAIN COMPONENTs. -Groups of carriages may be managed as sections by composing TRAINs into a COMPOUND TRAIN made up of multiple TRAIN IN COMPOUND TRAIN, for example in a train that joins or splits. +SIRI v2.1 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. +SIRI v2.1 -Examples: -- "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle arriving or departing in the direction of sector A on a QUAY with sectors A-B-C-D. If the arriving vehicle is represented as an arrow, "towards A" would be abstracted as "=> A-B-C-D". If the departing vehicle is represented as an arrow, "towards A" would be abstracted as "<= A-B-C-D". -- "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle arriving or departing in the direction of this reference point. If the arriving vehicle is represented as an arrow, "towards 0" would be abstracted as "=> 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). If the departing vehicle is represented as an arrow, "towards 0" would be abstracted as "<= 0...100". -It is advised to specify a reference point that is meaningful for passengers on location. - - - - - - - - Assignment of the arrival/departure of a VEHICLE within a formation, e.g. carriage in a TRAIN composition, to a physical QUAY or nested QUAY (i.e. platform or sector of a platform). +SIRI v2.1 - - - - - - Information about a change of a VEHICLE within the formation, e.g., whether a VEHICLE is open, booked or has defective doors. - - - - - References to the QUAY on which the particular VEHICLE, i.e., component of the formation, arrives or departs from. -If a QUAY is divided into sub-QUAYs or sectors (with the help of STOP ASSIGNMENTs), and a TRAIN COMPONENT spans over multiple sectors of the QUAY, the FORMATION ASSIGNMENT must reference all of them (in multiple STOP ASSIGNMENTs). - - - - - - - Information about a change of the formation (e.g. TRAIN composition) or changes of vehicles within the formation. +SIRI v2.1 - - - - - Type for FORMATION CONDITION. +SIRI v2.1 - - - - - - - Status of formation, e.g., whether it has changed compared to the plan, certain VEHICLEs or features are missing or extra VEHICLEs are added. - - - - - Status of a VEHICLE within formation, e.g., whether a VEHICLE is open, booked or has defective doors. - - - - - - - Information on recommendations for passengers on how to deal with the formation change. - - - - - - - - Description of the status of a monitored formation. - - - - - Status of the formation. - - - - - - - - Description of the status of a monitored vehicle. - - - - - Status of vehicle. - - - - - - - - Elements for FormationStatus that further describe the status of the formation, e.g. whether the accessibility has changed. +SIRI v2.1 - - - - - Description of the status of a formation or a vehicle within the formation. - - - - - Accessibility of the formation or a vehicle within the formation. - - - - - - - - Description of the recommended action for passengers on how to deal with changes, for example of the TRAIN formation. - - - - - Type of the recommendation, e.g. 'unknown', 'replacement' or 'otherRoute'. - - - - - Description of the recommended action in natural language. - - - - - - - - - Elements for a PASSENGER CAPACITY. Used to indicate the maximum capacities of a TRAIN ELEMENT or the estimated/recorded capacities of a VEHICLE at a given stop, i.e., the number of seats available. +SIRI v2.1 - - - - - The total capacity of the vehicle in number of passengers. - - - - - The seating capacity of the vehicle in number of passengers. - - - - - The standing capacity of the vehicle in number of passengers. - - - - - The number of special places on the vehicle, e.g. seats for the disabled or lounge seats. - - - - - The number of push chair places on the vehicle. - - - - - The number of wheelchair places on the vehicle. - - - - - The number of places on the vehicle that are suitable for prams. - - - - - The number of bicycle racks on the vehicle. - - - - - - - The intersection of supplied elements describes the extent that the Occupancy values applies to. +SIRI v2.1 -Only vehicle-centric filter (measurement in a part or at an entrance of a TRAIN) are available here, but a stop-centric filtering (measurement in a sector or at a position on a QUAY) can be achieved indirectly via Arrival-/DepartureFormationAssignment. - - - - - - Fare class in VEHICLE for which occupancy or capacities are specified. - - - - - Adult, child, wheelchair etc. - - - - - - - Occupancy values applying to indicated scope. +SIRI v2.1 - - - - - An approximate figure of how occupied or full a VEHICLE and its parts are, e.g. 'manySeatsAvailable' or 'standingRoomOnly'. -More accurate data can be provided by the individual occupancies or capacities below. - - - - - Utilised percentage of maximum payload after departing the STOP POINT. - - - - - Total number of alighting passengers for this vehicle journey at this STOP POINT. - - - - - Total number of boarding passengers for this vehicle journey at this STOP POINT. - - - - - Total number of passengers on-board after departing the STOP POINT. - - - - - Total number of special places, e.g. seats for the disabled or lounge seats, that are occupied after departing the STOP POINT. - - - - - Total number of pushchairs on-board after departing the STOP POINT. - - - - - Total number of wheelchairs on-board after departing the STOP POINT. - - - - - Total number of prams on-board after departing the STOP POINT. - - - - - Total number of bicycles on-board, i.e., number of bicycle racks that are occupied after departing the STOP POINT. - - - - - - - Used to specify that a travel group has booked a section of the vehicle for a part of the journey, and if so under what name. +SIRI v2.1 - - - - - Name for which the travel group has made the reservation. - - - - - Number of seats that the group has booked. - - - - - - - Real-time occupancies of a VEHICLE (by fare class). Could be feedback from an automatic passenger counting system (APC) or estimated values from statistics. +SIRI v2.1 - - - - - - - Total number of booked seats from individual and group reservations. - - - - - Reservations of travel groups, i.e., name of group and number of seats booked. - - - - - - - Real-time capacities of a VEHICLE (by fare class), i.e., number of available seats. Alternative way to communicate occupancy measurements. +SIRI v2.1 - - - - - - - - - - An elementary component of a TRAIN, e.g. wagon or locomotive. +SIRI v2.1 - - - - - Type for TRAIN ELEMENT. +SIRI v2.1 - - - - - Identifier for TRAIN ELEMENT. - - - - - - - - - Elements for a TRAIN ELEMENT. +SIRI v2.1 - - - - - Type of TRAIN ELEMENT. - - - - - Denotes the official "registration number" of the vehicle or wagon/coach. In rail transport VEHICLE NUMBER would be equal to the 12-digit UIC wagon/coach number, possibly followed by other combinations of letters, e.g. by the UIC classification of railway coaches. - - - - - - - - - Specifies the order of a certain TRAIN ELEMENT within a TRAIN and how the TRAIN ELEMENT is labeled in that context. +SIRI v2.1 - - - - - Type for TRAIN COMPONENT. +SIRI v2.1 - - - - - Identifier for TRAIN COMPONENT. - - - - - Specifies the order of the TRAIN ELEMENT within the TRAIN. The locomotive would ideally have ORDER '1', the first wagon/coach attached to the locomotive ORDER '2' and so on. - - - - - - - - Elements for a TRAIN COMPONENT. +SIRI v2.1 - - - - - Specifies how the TRAIN ELEMENT is labeled within the context of the TRAIN. This advertised label or number, e.g. "Carriage B" or "23", can be used for seat reservations and passenger orientation. - - - - - Description of TRAIN COMPONENT, e.g. "Front Carriage 1st Class". - - - - - - - - - Whether orientation of TRAIN ELEMENT within TRAIN is reversed or not. Default is 'false', i.e., they have the same orientation (usually forward in the direction of travel). - - - - - - - - A vehicle composed of TRAIN ELEMENTs assembled in a certain order (so called TRAIN COMPONENTs), i.e. wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 - - - - - Type for TRAIN. +SIRI v2.1 - - - - - Identifier for TRAIN. - - - - - - - - - Elements for TRAIN. +SIRI v2.1 - - - - - Number of cars needed in TRAIN. - - - - - Nature of TRAIN size, e.g "short", "long", "normal". Default is "normal". - - - - - Ordered collection of TRAIN COMPONENTs making up the TRAIN. - - - - - - - - - - - - - - Groups of carriages may be managed as sections by composing TRAINs into a COMPOUND TRAIN, for example if a TRAIN joins (or splits from) another TRAIN. +SIRI v2.1 -TRAINs within a COMPOUND TRAIN may have different origins and destinations due to joining/splitting. A COMPOUND TRAIN may be stable for one or multiple JOURNEY PARTs and change at a certain STOP POINT due to planned joining/splitting, despatching alterations or a situation. - - - - - Type for COMPOUND TRAIN. +SIRI v2.1 - - - - - Identifier for COMPOUND TRAIN. - - - - - - Ordered collection of TRAINs making up the COMPOUND TRAIN. - - - - - - - - - - - - - Specifies the order of a certain TRAIN within a COMPOUND TRAIN and how the TRAIN is labeled in that context. +SIRI v2.1 - - - - - Type for a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 - - - - - Identifier for TRAIN IN COMPOUND TRAIN. - - - - - Specifies the order of the TRAIN within the COMPOUND TRAIN. - - - - - - - - Elements for a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 - - - - - Specifies how the TRAIN is labeled within the context of the COMPOUND TRAIN. This advertised label or number, e.g. the individual TRAIN NUMBER, can be used for seat reservations and passenger orientation. - - - - - Description of TRAIN IN COMPOUND TRAIN. - - - - - - - - - - Whether orientation of TRAIN within COMPOUND TRAIN is reversed or not. Default is 'false', i.e., they have the same orientation (usually forward in the direction of travel). - - - - - Specifies whether a passage from/to an adjacent TRAIN is possible for passengers. - - - - - - - - - - - - Indicates whether passengers have access to adjacent TRAINs or TRAIN COMPONENTs within a COMPOUND TRAIN, i.e., whether passage between those wagons/coaches is possible. +SIRI v2.1 - - - - - - - - - - - Elements for a VEHICLE TYPE. +SIRI v2.1 - - - - - Name of VEHICLE TYPE. - - - - - Short Name of VEHICLE TYPE. - - - - - Description of VEHICLE TYPE. - - - - - - - Facilities of VEHICLE TYPE. - - - - - - - - - - - - - - - - Property elements for the abstract VEHICLE TYPE. +SIRI v2.1 - - - - - Whether vehicles of the type have a reversing direction. - - - - - Whether vehicles of the type are self-propelled. - - - - - The type of fuel used by a vehicle of the type. - - - - - Euroclass of the vehicle type. Corresponds to the 12-digit European Identification Number (EIN). - - - - - Break down of capacities by FARE CLASS, i.e., maximum number of passengers that TRAIN ELEMENT can carry. - - - - - - - - - - - - - - Elements specifying Requirement properties of VEHICLE TYPE. Vehicle should satisfy these requirements. +SIRI v2.1 - - - - - Whether Vehicle is low floor to facilitate access by the mobility impaired. - - - - - Whether vehicle has lift or ramp to facilitate wheelchair access. - - - - - Whether vehicle has hoist for wheelchair access. - - - - - - - Dimension elements for a VEHICLE TYPE. +SIRI v2.1 - - - - - The length of a VEHICLE of the type. - - - - - The width of a VEHICLE of the type. - - - - - The length of a VEHICLE of the type. - - - - - The weight of a VEHICLE of the type. - - - - - -       + + + + + + main schema + e-service developers + Cen TC278 WG3 SG7 Team + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2004-03-05 + + + 2004-10-06 + + + 2005-05-11 + + + 2005-11-15 + + + 2007-03-29 + + + 2008-11-13 + + + + 2011-04-18 + + + + 2012-03-22 + + + + 2012-04-27 + + + + 2013-01-25 + + + + 2013-02-11 + + + + 2014-06-20 + + + +

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

      +

      This subschema defines common journey elements.

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/siri/}siri_journey.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd + + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG CML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of common Journey elements + Standard +       +       + SIRI Common Journey Model. +       + + + + + + + + + + + + + + + + Elements describing a VEHICLE JOURNEY. Values for these elements can be specified on an annual schedule and will be inherited, unless overriden, onto the production timetable and then onto the individul DATED VEHICLE JOURNEYs of the timetable. Each real-time journey (e.g. ESTIMATED VEHICLE JOURNEY or MONITORED VEHICLE JORUNEY) takes its values from the DATED VEHICLE JOURNEY that it follows. The absence of a value on an entity at a given level indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity. + + + + + For train services with named journeys. Train name, e.g. “West Coast Express”. If omitted: No train name. Inherited property. (Unbounded since SIRI 2.0) + + + + + + Contact details for use by members of public. +SIRI v2.0 + + + + + Contact details for use by operational staff. +SIRI v2.0 + + + + + + + Type for Simple Contact Details. + + + + + Phone number +SIRI v2.0 + + + + + Url for contact +SIRI v2.0 + + + + + + + + Common information about a VEHICLE JOURNEY. (Similar to VDV TripInfo) + + + + + + + + + + + End names for journey. + + + + + + Name of the origin of the journey. (Unbounded since SIRI 2.0) + + + + + Short name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as Origin Name. + + + + + DIRECTION name shown for jurney at the origin. +SIRI v2.0 + + + + + Names of VIA points, used to help identify the LINE, for example, Luton to Luton via Sutton. Currently 3 in VDV. Should only be included if the detail level was requested. + + + + + Reference to a DESTINATION. + + + + + Description of the destination stop (vehicle signage), Can be overwritten for a journey, and then also section by section by the entry in an individual CALl. (Unbounded since SIRI 2.0) + + + + + Short name of the DESTINATION.of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as DestinationName. (Unbounded since SIRI 2.0) + + + + + Origin name shown for jourey at the destination +SIRI v2.0 + + + + + + + Type for VIA NAMes structure. + + + + + + + Relative priority to give to VIA name in displays. 1=high. Default is 2. +SIRI v2.0 + + + + + + + + + + Type for Information about a DESTINATION. + + + + + Identifer of Destinatioin + + + + + Name of Destination + + + + + + + The name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. + + + + + Names of VIA points, used to help identify the LINEfor example, Luton to Luton via Sutton. Currently 3 in VDV. Should only be included if the detail level was requested. + + + + + The name of the DESTINATION of the journey; used to help identify the VEHICLE to the public. Note when used in a CALL, this is the Dynamic Destination Display: since vehicles can change their destination during a journey, the destination included here should be what the VEHICLE will display when it reaches the stop. + + + + + + Call times for journey. + + + + + Whether this is a Headway Service, that is shown as operating at a prescribed interval rather than to a fixed timetable. Default is 'false'. + + + + + Timetabled departure time from Origin. + + + + + Timetabled arrival time at Destination. + + + + + + + + Whether journey is first or last journey of day. +SIRI v2.0 + + + + + Additional descriptive text associated with journey. Inherited property. + + + + + Description of a DIRECTION. + + + + + Type for DIRECTION. + + + + + Identifer of DIRECTION, + + + + + Description of DIRECTION. (Unbounded since SIRI 2.0) + + + + + + + + Operational information about the monitored VEHICLE JOURNEY. + + + + + + + + Refercence to other VEHICLE Journeys (+SIRI v2.0) + + + + + A reference to the DRIVER or Crew currently logged in to operate a monitored VEHICLE. May be omitted if real-time data is not available - i.e. it is timetabled data. +SIRI v2.0 + + + + + The name oo the Driver or Crew +SIRI v2.0 + + + + + + + Operational information about the monitored VEHICLE JOURNEY. + + + + + + + + + Operational information about the monitored VEHICLE JOURNEY. + + + + + BLOCK that VEHICLE is running. + + + + + COURSE OF JOURNEY ('Run') that VEHICLE is running. + + + + + + + Type for Progress between stops. + + + + + The total distance in metres between the previous stop and the next stop. + + + + + Percentage along link that VEHICLE has travelled. + + + + + + + + + Type for Abstract CALL at stop. + + + + + + + + + Elements describing the targeted CALL of a VEHICLE at a stop. + + + + + + + + + + + Elements describing the arrival of a VEHICLE at a stop. + + + + + + + + Assignment of planned arrival at scheduled STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. +SIRI v2.0. + + + + + + + + + Elements describing the departure of a VEHICLE from a stop. + + + + + + + + + + + + + + Type for Abstract CALL at stop. + + + + + + + + Elements describing the arrival status of a VEHICLE at a stop. + + + + + + + + + + Assignment of planned, expected and/or recorded arrival at STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. +SIRI v2.0. + + + + + + + + + + Elements describing the departure status of a VEHICLE from a stop. + + + + + + + + + + + + + + + + + + + Elements describing the CALL Properties Values for these elements can be specified on an production VEHICLE JOURNEY CALL. Each real-time journey CALL takes its values from the corresponding dated VEHICLE JOURNEY CALL. The absence of a value on an real-time CALL l indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity. + + + + + + Whether this is a Hail and Ride Stop. Default is 'false'. + + + + + Whether Vehicle stops only if requested explicitly by passenger. Default is 'false'. + + + + + Origin to show for the VEHICLE at the specific stop (vehicle signage), if different to the Origin Name for the full journey. (+Siri 2.0) + + + + + Destination to show for the VEHICLE at the specific stop (vehicle signage), if different to the Destination Name for the full journey. + + + + + + + Annotations of the CALL. + + + + + Text annotation that applies to this CALL. + + + + + + + + Type for CALLing pattern for JOURNEY PATTERN. + + + + + + + + Type Onwards CALLs at stop. + + + + + + + + + + + + + + + + + Elements describing the CALL. Values for these elements can be specified on an production VEHICLE JOURNEY CALL. Each real-time journey CALL takes its values from the corresponding dated VEHICLE JOURNEY CALL. The absence of a value on an real-time CALL l indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity. + + + + + + + + + + + + + + Elements for Arrival in onward CALl. + + + + + + + + + Latest time at which a VEHICLE will arrive at stop. +SIRI v2.1 + + + + + Prediction quality, either as approximate level, or more quantitative percentile range of predictions that will fall within a given range of times. +SIRI v2.0 + + + + + + If the producer is (temporarily) not able to deliver real-time predictions (e.g. because of a connection loss), he has various options (and combinations of them) to inform the consumer: +(i) set Monitored to 'false' +(ii) transmit ExpectedArrivalTime together with "PredictionInaccurate=true" +(iii) drop/omit ExpectedArrivalTime +(iv) set ArrivalStatus to 'noReport' +However, this might introduce ambiguity: e.g. option (iii) might be interpreted as "on time" by one consumer, but also as "indefinite delay" by another consumer. +To avoid this, the producer should transmit xxxPredictionUnknown instead of any expected times. +SIRI v2.1 + + + + + + + + Elements for departure in ONWARD CALL. + + + + + + + + + Expected departure time of VEHICLE without waiting time due to operational actions. For people at stop this would normally be shown if different from Expected departure time. So if servcie decides not to wait may leave earler than expected departure time +SIRI v2.0. + + + + + Earliest time at which VEHICLE may leave the stop. Used to secure connections. Used for passenger announcements. Passengers must be at boarding point by this time to be sure of catching VEHICLE. i.e. "Vehicle will not leave before this time" - may be revised from original aimed time. +SIRI v2.0 + + + + + Prediction quality, either as approximate level, or more quantitative percentile range of predictions that will fall within a given range of times. +SIRI v2.0 + + + + + + If the producer is (temporarily) not able to deliver real-time predictions (e.g. because of a connection loss), he has various options (and combinations of them) to inform the consumer: +(i) set Monitored to 'false' +(ii) transmit ExpectedDepartureTime together with "PredictionInaccurate=true" +(iii) drop/omit ExpectedDepartureTime +(iv) set DepartureStatus to 'noReport' +However, this might introduce ambiguity: e.g. option (iii) might be interpreted as "on time" by one consumer, but also as "indefinite delay" by another consumer. +To avoid this, the producer should transmit xxxPredictionUnknown instead of any expected times. +SIRI v2.1 + + + + + + + + Elements describing the HEADWAY INTERVALs. + + + + + + + + + Elements describing the distance from the stop of a VEHICLE. +SIRI v2.0. + + + + + Distance of VEHICLE from stop of CALL as measured along ROUTE track. Only shown if detail level is 'calls' or higher. Positive value denotes distance before stop. +SIRI v2.0. + + + + + Count of stops along SERVICE PATTERN between current position of VEHICLE and stop of CALL as measured along ROUTE track. Only shown if detail level is 'calls' or higher. +SIRI v2.0. + + + + + + + Type for Prediction Quality quantifcation. + + + + + An approxiimate characterisation of prediction quality as one of five values. +SIRI v2.0 + + + + + + Percentile associated with range as specified by lower and upper bound. +SIRI v2.0 + + + + + Lower bound on time of prediction for confidence level if different from defaults. +SIRI v2.0 + + + + + Upper bound on time of prediction for confidence level if different from defaults. +SIRI v2.0 + + + + + + + + + Area that encompasses the scheduled flexible stop locations according to the planned timetable. +SIRI v2.1 + + + + + Reference to the scheduled location or flexible area. +SIRI v2.1 + + + + + Name or description (e.g. address) of the scheduled location or flexible area. +SIRI v2.1 + + + + + + Elements for location of flexible stops or service that allows pickup anywhere in a designated area. +SIRI v2.1 + + + + + + + + Area that encompasses the expected flexible stop locations according to the real-time prediction. + + + + + + Name or description (e.g. address) of the expected location or flexible area. + + + + + Area that encompasses the actually recorded flexible stop locations. + + + + + + Name or description (e.g. address) of the actually recorded location or flexible area. + + + + + + + + Elements for assignment of a SCHEDULED STOP POINT to a specific QUAY or platform. +SIRI v2.1 + + + + + Physical QUAY to use according to the planned timetable. +SIRI v2.0 + + + + + Scheduled Platform name. Can be used to indicate platfrom change. +SIRI v2.0 + + + + + Physical QUAY to use according to the real-time prediction. +SIRI v2.0 + + + + + Expected Platform name. Can be used to indicate real-time prediction. +SIRI v2.1 + + + + + Physical QUAY actually used. +SIRI v2.0 + + + + + Actual Platform name. Can be used to indicate recorded platform. +SIRI v2.1 + + + + + + + + + Elements for assignment of a SCHEDULED STOP POINT to a specific BOARDING POSITION or location on a QUAY. +SIRI v2.1 + + + + + Physical BOARDING POSITION to use according to the planned timetable. + + + + + Scheduled BOARDING POSITION name. Can be used to indicate boarding position change. + + + + + Physical BOARDING POSITION to use according to the real-time prediction. + + + + + Expected BOARDING POSITION name. Can be used to indicate real-time prediction. + + + + + Actually recorded BOARDING POSITION. Can be used to indicate the actually used boarding position. + + + + + Recorded BOARDING POSITION name. Can be used to indicate the actually used boarding position. + + + + + + + + Type for assignment of a SCHEDULED STOP POINT to a physical location, in particular to a QUAY or BOARDING POSITION. +SIRI v2.0. + + + + + + + + + + + + + Type for assignment of a SCHEDULED STOP POINT to a physical location, in particular to a QUAY or BOARDING POSITION, according to the planned timetable. +SIRI v2.0. + + + + + + + Physical QUAY to use according to the planned timetable. +SIRI v2.0 + + + + + Scheduled Platform name. +SIRI v2.0 + + + + + + + + Physical BOARDING POSITION to use according to the planned timetable. +SIRI v2.1 + + + + + Scheduled BOARDING POSITION name. +SIRI v2.1 + + + + + + + + + + + + + Indicates the type of a nested QUAY in case of detailed STOP PLACE models. +A QUAY may be part of a group of QUAYs, or may be divided into sectors, i.e., smaller sub-QUAYs. +SIRI v2.1 + + + + + + Whether the prediction for a specific stop or the whole journey is considered to be of a useful accuracy or not. Default is 'false', i.e. prediction is considered to be accurate. +If prediction is degraded, e.g. because of a situation, PredictionInaccurate is used to indicate a lowered quality of data. Inherited property. PredictionInaccurate can be used in combination with InCongestion, but is more general. + + + + + Can be used to inform the passenger about the reason for a change of the prediction (in)accuracy in case PredictionInaccurate is set to 'true'. +SIRI v2.1 + + + + + An approximate figure of how occupied the journey is after departing from a given stop, e.g. 'manySeatsAvailable' or 'standingRoomOnly'. If omitted: Passenger load is unknown. +Occupancies and capacities for individual VEHICLEs, e.g. parts of a COMPOUND TRAIN, can also be specified in more detail for the departure on CALL level. + + + + + + Target arrival time of VEHICLE at stop according to latest working timetable. + + + + + Observed time of arrival of VEHICLE at stop. + + + + + Estimated time of arriival of VEHICLE at stop . + + + + + Classification of the timeliness of the visit according to a fixed list of values. If not specified, same as DepartureStatus. + + + + + Text annotation to be used in cases where ArrivalStatus is set to 'cancelled'. +SIRI v2.1 + + + + + Arbitrary text string to show to indicate the status of the departure of the VEHICLE for example, “Enroute”, “5 Km”, “Approaching”. May depend on the policy of the OPERATOR, for example show “Approaching” if less than 200metres away from stop. +SIRI v2.0 + + + + + Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicle to arrive at. +Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is: +(i) any arrival platform on any related dated timetable element, +(ii) any departure platform name on this estimated element; +(iii) any departure platform name on any related dated timetable CALL. + + + + + Type of boarding and alighting allowed at stop. Default is 'Alighting'. + + + + + Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). If not given, assume same as for departure. +SIRI v2.1 + + + + + Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. +SIRI v2.1 +Examples: +- "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle arriving at sector A first when approaching the QUAY with sectors A-B-C-D. If the arriving vehicle is represented as an arrow, "towards A" would be abstracted as "=> A-B-C-D". +- "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle arriving at this reference point first when approaching the QUAY. If the arriving vehicle is represented as an arrow, "towards 0" would be abstracted as "=> 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). +It is advised to specify a reference point that is meaningful for passengers on location. + + + + + + OPERATORs of of service up until arrival. May change for departure. +SIRI v2.0. + + + + + + Arrival times for CALL. + + + + + + + + + + + + + Target departure time of VEHICLE from stop according to latest working timetable. + + + + + Observed time of departure of VEHICLE from stop. + + + + + Estimated time of departure of VEHICLE from stop, most likely taking into account all control actions such as waiting. + + + + + Latest target time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. +SIRI 2.0 + + + + + Latest expected time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. +SIRI 2.0 + + + + + Classification of the timeliness of the departure part of the CALL, according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are still classified as on-time. Applications may use this to guide their own presentation of times. + + + + + Text annotation to be used in cases where DepartureStatus is set to 'cancelled'. +SIRI v2.1 + + + + + Arbitrary text string to show to indicate the status of the departure of the vehicle, for example, “Boarding”, “GatesClosed”. +SIRI v2.0 + + + + + Departure QUAY (bay or platform) name. Default taken from planned timetable. + + + + + Nature of boarding allowed at stop. Default is 'Boarding'. + + + + + Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). +SIRI v2.1 + + + + + Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. +SIRI v2.1 +Examples: +- "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle departing in the direction of sector A on a QUAY with sectors A-B-C-D. If the departing vehicle is represented as an arrow, "towards A" would be abstracted as "<= A-B-C-D". +- "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle departing in the direction of this reference point. If the departing vehicle is represented as an arrow, "towards 0" would be abstracted as "<= 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). +It is advised to specify a reference point that is meaningful for passengers on location. + + + + + Real-time occupancies of a VEHICLE and reservations after departing from a given stop. +SIRI v2.1 + + + + + Real-time capacities (number of available seats) of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. +SIRI v2.1 + + + + + OPERATORs of service for departure and onwards. May change from that for arrival. +SIRI v2.0. + + + + + Recorded occupancies of a VEHICLE and reserved seats after departing from a given stop. +SIRI v2.1 + + + + + Recorded capacities of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. +SIRI v2.1 + + + + + + Departure times for CALL. + + + + + + + + + + + + Passenger arrival times at STOP PLACE in order to meet VEHICLE departure times for CALL. + + + + + + + + + + For frequency based services, target interval between vehicles at stop. + + + + + For frequency based services, expected interval between vehicles at stop. + + + + + For frequency based services, observed interval between vehicles at stop. + + + + + + Provides information about relations to other journeys. +SIRI v2.1 + + + + + + + + + + Specifies the type of the relation, e.g., joining, splitting, replacement etc. +SIRI v2.1 + + + + + + + + + Specifies which CALL or JOURNEY PART of the JOURNEY has a JOURNEY RELATION. +SIRI v2.1 + + + + + + Information about the stop at which the JOURNEY is related to another JOURNEY. +SIRI v2.1 + + + + + Information about the JOURNEY PARTs for which the JOURNEY has a JOURNEY RELATION. +SIRI v2.1 + + + + + + Information about related parts of JOURNEY. +SIRI v2.1 + + + + + + + + + + + The JOURNEY RELATION refers to this CALL. +SIRI v2.1 + + + + + + + + + + + + + The JOURNEY RELATION refers to this JOURNEY PART. +SIRI v2.1 + + + + + + + + Refers to the JOURNEY to which the current JOURNEY is related. +SIRI v2.1 + + + + + + + + + + + + + + + Groups relevant elements of the formation model that are used on JOURNEY level. +The TRAIN conceptual model represents VEHICLE TYPE properties that are peculiar to TRAINs. A TRAIN may comprise not just a single VEHICLE but a chain of carriages, TRAIN ELEMENTS, assembled as TRAIN COMPONENTs. +Groups of carriages may be managed as sections by composing TRAINs into a COMPOUND TRAIN made up of multiple TRAIN IN COMPOUND TRAIN, for example in a train that joins or splits. +SIRI v2.1 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. +SIRI v2.1 +Examples: +- "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle arriving or departing in the direction of sector A on a QUAY with sectors A-B-C-D. If the arriving vehicle is represented as an arrow, "towards A" would be abstracted as "=> A-B-C-D". If the departing vehicle is represented as an arrow, "towards A" would be abstracted as "<= A-B-C-D". +- "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle arriving or departing in the direction of this reference point. If the arriving vehicle is represented as an arrow, "towards 0" would be abstracted as "=> 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). If the departing vehicle is represented as an arrow, "towards 0" would be abstracted as "<= 0...100". +It is advised to specify a reference point that is meaningful for passengers on location. + + + + + + + + Assignment of the arrival/departure of a VEHICLE within a formation, e.g. carriage in a TRAIN composition, to a physical QUAY or nested QUAY (i.e. platform or sector of a platform). +SIRI v2.1 + + + + + + Information about a change of a VEHICLE within the formation, e.g., whether a VEHICLE is open, booked or has defective doors. + + + + + References to the QUAY on which the particular VEHICLE, i.e., component of the formation, arrives or departs from. +If a QUAY is divided into sub-QUAYs or sectors (with the help of STOP ASSIGNMENTs), and a TRAIN COMPONENT spans over multiple sectors of the QUAY, the FORMATION ASSIGNMENT must reference all of them (in multiple STOP ASSIGNMENTs). + + + + + + + Information about a change of the formation (e.g. TRAIN composition) or changes of vehicles within the formation. +SIRI v2.1 + + + + + Type for FORMATION CONDITION. +SIRI v2.1 + + + + + + + Status of formation, e.g., whether it has changed compared to the plan, certain VEHICLEs or features are missing or extra VEHICLEs are added. + + + + + Status of a VEHICLE within formation, e.g., whether a VEHICLE is open, booked or has defective doors. + + + + + + + Information on recommendations for passengers on how to deal with the formation change. + + + + + + + + Description of the status of a monitored formation. + + + + + Status of the formation. + + + + + + + + Description of the status of a monitored vehicle. + + + + + Status of vehicle. + + + + + + + + Elements for FormationStatus that further describe the status of the formation, e.g. whether the accessibility has changed. +SIRI v2.1 + + + + + Description of the status of a formation or a vehicle within the formation. + + + + + Accessibility of the formation or a vehicle within the formation. + + + + + + + + Description of the recommended action for passengers on how to deal with changes, for example of the TRAIN formation. + + + + + Type of the recommendation, e.g. 'unknown', 'replacement' or 'otherRoute'. + + + + + Description of the recommended action in natural language. + + + + + + + + + Elements for a PASSENGER CAPACITY. Used to indicate the maximum capacities of a TRAIN ELEMENT or the estimated/recorded capacities of a VEHICLE at a given stop, i.e., the number of seats available. +SIRI v2.1 + + + + + The total capacity of the vehicle in number of passengers. + + + + + The seating capacity of the vehicle in number of passengers. + + + + + The standing capacity of the vehicle in number of passengers. + + + + + The number of special places on the vehicle, e.g. seats for the disabled or lounge seats. + + + + + The number of push chair places on the vehicle. + + + + + The number of wheelchair places on the vehicle. + + + + + The number of places on the vehicle that are suitable for prams. + + + + + The number of bicycle racks on the vehicle. + + + + + + + The intersection of supplied elements describes the extent that the Occupancy values applies to. +SIRI v2.1 +Only vehicle-centric filter (measurement in a part or at an entrance of a TRAIN) are available here, but a stop-centric filtering (measurement in a sector or at a position on a QUAY) can be achieved indirectly via Arrival-/DepartureFormationAssignment. + + + + + + Fare class in VEHICLE for which occupancy or capacities are specified. + + + + + Adult, child, wheelchair etc. + + + + + + + Occupancy values applying to indicated scope. +SIRI v2.1 + + + + + An approximate figure of how occupied or full a VEHICLE and its parts are, e.g. 'manySeatsAvailable' or 'standingRoomOnly'. +More accurate data can be provided by the individual occupancies or capacities below. + + + + + Utilised percentage of maximum payload after departing the STOP POINT. + + + + + Total number of alighting passengers for this vehicle journey at this STOP POINT. + + + + + Total number of boarding passengers for this vehicle journey at this STOP POINT. + + + + + Total number of passengers on-board after departing the STOP POINT. + + + + + Total number of special places, e.g. seats for the disabled or lounge seats, that are occupied after departing the STOP POINT. + + + + + Total number of pushchairs on-board after departing the STOP POINT. + + + + + Total number of wheelchairs on-board after departing the STOP POINT. + + + + + Total number of prams on-board after departing the STOP POINT. + + + + + Total number of bicycles on-board, i.e., number of bicycle racks that are occupied after departing the STOP POINT. + + + + + + + Used to specify that a travel group has booked a section of the vehicle for a part of the journey, and if so under what name. +SIRI v2.1 + + + + + Name for which the travel group has made the reservation. + + + + + Number of seats that the group has booked. + + + + + + + Real-time occupancies of a VEHICLE (by fare class). Could be feedback from an automatic passenger counting system (APC) or estimated values from statistics. +SIRI v2.1 + + + + + + + Total number of booked seats from individual and group reservations. + + + + + Reservations of travel groups, i.e., name of group and number of seats booked. + + + + + + + Real-time capacities of a VEHICLE (by fare class), i.e., number of available seats. Alternative way to communicate occupancy measurements. +SIRI v2.1 + + + + + + + + + + An elementary component of a TRAIN, e.g. wagon or locomotive. +SIRI v2.1 + + + + + Type for TRAIN ELEMENT. +SIRI v2.1 + + + + + Identifier for TRAIN ELEMENT. + + + + + + + + + Elements for a TRAIN ELEMENT. +SIRI v2.1 + + + + + Type of TRAIN ELEMENT. + + + + + Denotes the official "registration number" of the vehicle or wagon/coach. In rail transport VEHICLE NUMBER would be equal to the 12-digit UIC wagon/coach number, possibly followed by other combinations of letters, e.g. by the UIC classification of railway coaches. + + + + + + + + + Specifies the order of a certain TRAIN ELEMENT within a TRAIN and how the TRAIN ELEMENT is labeled in that context. +SIRI v2.1 + + + + + Type for TRAIN COMPONENT. +SIRI v2.1 + + + + + Identifier for TRAIN COMPONENT. + + + + + Specifies the order of the TRAIN ELEMENT within the TRAIN. The locomotive would ideally have ORDER '1', the first wagon/coach attached to the locomotive ORDER '2' and so on. + + + + + + + + Elements for a TRAIN COMPONENT. +SIRI v2.1 + + + + + Specifies how the TRAIN ELEMENT is labeled within the context of the TRAIN. This advertised label or number, e.g. "Carriage B" or "23", can be used for seat reservations and passenger orientation. + + + + + Description of TRAIN COMPONENT, e.g. "Front Carriage 1st Class". + + + + + + + + + Whether orientation of TRAIN ELEMENT within TRAIN is reversed or not. Default is 'false', i.e., they have the same orientation (usually forward in the direction of travel). + + + + + + + + A vehicle composed of TRAIN ELEMENTs assembled in a certain order (so called TRAIN COMPONENTs), i.e. wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 + + + + + Type for TRAIN. +SIRI v2.1 + + + + + Identifier for TRAIN. + + + + + + + + + Elements for TRAIN. +SIRI v2.1 + + + + + Number of cars needed in TRAIN. + + + + + Nature of TRAIN size, e.g "short", "long", "normal". Default is "normal". + + + + + Ordered collection of TRAIN COMPONENTs making up the TRAIN. + + + + + + + + + + + + + + Groups of carriages may be managed as sections by composing TRAINs into a COMPOUND TRAIN, for example if a TRAIN joins (or splits from) another TRAIN. +SIRI v2.1 +TRAINs within a COMPOUND TRAIN may have different origins and destinations due to joining/splitting. A COMPOUND TRAIN may be stable for one or multiple JOURNEY PARTs and change at a certain STOP POINT due to planned joining/splitting, despatching alterations or a situation. + + + + + Type for COMPOUND TRAIN. +SIRI v2.1 + + + + + Identifier for COMPOUND TRAIN. + + + + + + Ordered collection of TRAINs making up the COMPOUND TRAIN. + + + + + + + + + + + + + Specifies the order of a certain TRAIN within a COMPOUND TRAIN and how the TRAIN is labeled in that context. +SIRI v2.1 + + + + + Type for a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 + + + + + Identifier for TRAIN IN COMPOUND TRAIN. + + + + + Specifies the order of the TRAIN within the COMPOUND TRAIN. + + + + + + + + Elements for a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 + + + + + Specifies how the TRAIN is labeled within the context of the COMPOUND TRAIN. This advertised label or number, e.g. the individual TRAIN NUMBER, can be used for seat reservations and passenger orientation. + + + + + Description of TRAIN IN COMPOUND TRAIN. + + + + + + + + + + Whether orientation of TRAIN within COMPOUND TRAIN is reversed or not. Default is 'false', i.e., they have the same orientation (usually forward in the direction of travel). + + + + + Specifies whether a passage from/to an adjacent TRAIN is possible for passengers. + + + + + + + + + + + + Indicates whether passengers have access to adjacent TRAINs or TRAIN COMPONENTs within a COMPOUND TRAIN, i.e., whether passage between those wagons/coaches is possible. +SIRI v2.1 + + + + + + + + + + + Elements for a VEHICLE TYPE. +SIRI v2.1 + + + + + Name of VEHICLE TYPE. + + + + + Short Name of VEHICLE TYPE. + + + + + Description of VEHICLE TYPE. + + + + + + + Facilities of VEHICLE TYPE. + + + + + + + + + + + + + + + + Property elements for the abstract VEHICLE TYPE. +SIRI v2.1 + + + + + Whether vehicles of the type have a reversing direction. + + + + + Whether vehicles of the type are self-propelled. + + + + + The type of fuel used by a vehicle of the type. + + + + + Euroclass of the vehicle type. Corresponds to the 12-digit European Identification Number (EIN). + + + + + Break down of capacities by FARE CLASS, i.e., maximum number of passengers that TRAIN ELEMENT can carry. + + + + + + + + + + + + + + Elements specifying Requirement properties of VEHICLE TYPE. Vehicle should satisfy these requirements. +SIRI v2.1 + + + + + Whether Vehicle is low floor to facilitate access by the mobility impaired. + + + + + Whether vehicle has lift or ramp to facilitate wheelchair access. + + + + + Whether vehicle has hoist for wheelchair access. + + + + + + + Dimension elements for a VEHICLE TYPE. +SIRI v2.1 + + + + + The length of a VEHICLE of the type. + + + + + The width of a VEHICLE of the type. + + + + + The length of a VEHICLE of the type. + + + + + The weight of a VEHICLE of the type. + + + + + +       diff --git a/xsd/siri_model/siri_journey_support.xsd b/xsd/siri_model/siri_journey_support.xsd index 9bd39479..c36a2902 100644 --- a/xsd/siri_model/siri_journey_support.xsd +++ b/xsd/siri_model/siri_journey_support.xsd @@ -1,1022 +1,1022 @@ - - - - - - main schema - e-service developers - Cen TC278 WG3 SG7 Team - Europe - Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2004-03-05 - - - 2004-10-06 - - - 2005-05-11 - - - 2005-11-15 - - - 2007-03-29 - - - 2008-11-13 - - - - 2011-04-18 - - - - 2012-03-22 - - - - 2013-02-11 - - - -

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

      -

      This subschema defines identifer definitions for common journey elements.

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_journey_support.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_types.xsd - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIG CML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of identifers common journey elements - Standard -       -       - SIRI Journey Model Identifiers. -       - - - - - - - Elements identifying VEHICLE JOURNEY. - - - - - Reference to a LINE. - - - - - Reference to a DIRECTION, typically outward or return. - - - - - A reference to the dated VEHICLE JOURNEY that the VEHICLE is making. - - - - - - - Elements identifying a VEHICLE JOURNEY. LINE and DIRECTION will be same as for journey unless overridden. - - - - - Reference to LINE of journey. - - - - - Reference to DIRECTION of journey. - - - - - A reference to the DATED VEHICLE JOURNEY that the VEHICLE is making, unique with the data horizon of the service. - - - - - - - - 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. - - - - - - Type for Origin and Destination stop of a VEHICLE JOURNEY. - - - - - The origin is used to help identify the VEHICLE JOURNEY. - - - - - Departure time from origin SCHEDULED STOP POINT. - - - - - The destination is used to help identify the VEHICLE JOURNEY. - - - - - Arrival time at destination SCHEDULED STOP POINT. - - - - - - - - Type for a reference to a connecting journey. - - - - - A reference to the DATE VEHICLE JOURNEY that the VEHICLE is making, unique with the data horizon of the service. - - - - - Identify a VEHICLE JOURNEY indirectly by origin and destination as well as the scheduled times at these stops. - - - - - Reference to LINE of journey. - - - - - Reference to TRAIN NUMBER of journey. - - - - - Reference to OPERATOR of journey. - - - - - PARTICIPANT reference that identifies data producer of journey. - - - - - - - - Type for identifer of a SERVICE JOURNEY INTERCHANGE. - - - - - - Type for reference to a SERVICE JOURNEY INTERCHANGE. - - - - - - - - Reference to a SERVICE JOURNEY INTERCHANGE. - - - - - - Type for identifer of a VEHICLE JOURNEY within data Horizon of a service. - - - - - identifier of data frame within particpant service. Used to ensure that the Reference to a DATED VEGICLE JOURNEY 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 identifier of a data VERSION FRAME. - - - - - - Type for identifier of a data VERSION FRAME. - - - - - - - - - Type for identifier of Train Part. - - - - - - Type for reference to a Train Part. - - - - - - - - - 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). - - - - - - - - - Type for identifier of an JOURNEY PART - - - - - - Type for reference to a JOURNEY PART - - - - - - - - Type for identifier of an TRAIN NUMBER - - - - - - Type for reference to a TRAIN NUMBER - - - - - - - - Type for identifier of a TRAIN ELEMENT. An elementary component of a TRAIN (e.g. wagon, locomotive etc.). +SIRI v2.1 - - - - - - Type for reference to a TRAIN ELEMENT. +SIRI v2.1 - - - - - - - - Reference to a TRAIN ELEMENT. +SIRI v2.1 - - - - - Type for identifier of a TRAIN COMPONENT. A TRAIN ELEMENT with a specific order within a TRAIN. +SIRI v2.1 - - - - - - Type for reference to a TRAIN COMPONENT. +SIRI v2.1 - - - - - - - - Reference to a TRAIN COMPONENT. +SIRI v2.1 - - - - - Type for identifier of a TRAIN. An ordered sequence of TRAIN ELEMENTs or TRAIN COMPONENTs respectively. +SIRI v2.1 - - - - - - Type for reference to a TRAIN. +SIRI v2.1 - - - - - - - - Reference to a TRAIN. +SIRI v2.1 - - - - - Type for identifier of a COMPOUND TRAIN. An ordered sequence of TRAINs or TRAIN IN COMPOUND TRAINs respectively. +SIRI v2.1 - - - - - - Type for reference to a COMPOUND TRAIN. +SIRI v2.1 - - - - - - - - Reference to a COMPOUND TRAIN. +SIRI v2.1 - - - - - Type for identifier of a TRAIN IN COMPOUND TRAIN. A TRAIN with a specific order within a COMPOUND TRAIN. +SIRI v2.1 - - - - - - Type for reference to a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 - - - - - - - - Reference to a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 - - - - - Type for identifier of an ENTRANCE TO VEHICLE, e.g. a door of a TRAIN ELEMENT. +SIRI v2.1 - - - - - - Type for reference to an ENTRANCE TO VEHICLE. +SIRI v2.1 - - - - - - - - Reference to an ENTRANCE TO VEHICLE. +SIRI v2.1 - - - - - - Groups together the relevant references needed in a formation. +SIRI v2.1 -Has the following uses: -- Either the smallest part of a formation, a TRAIN COMPONENT, is referenced or the TRAIN itself. The former is ideally used in a FORMATION ASSIGNMENT, i.e. QUAY (sector) assignment, to provide the highest level of detail for passenger orientation. -- If the formation consists of multiple coupled TRAINs, a reference to the COMPOUND TRAIN is also possible. This might be used in a FORMATION CONDITION to signal a change of the train composition. -- In case alighting/boarding data from an automatic passenger counting system is available, the respective vehicle entrances may be referenced. - - - - - - - - - - - - - Allowed types activity for Boarding and Alighting. - - - - - - - - - - - Allowed types activity for Alighting. - - - - - - - - - - Allowed types activity for Boarding. - - - - - - - - - - - - Reference to the origin SCHEDULED STOP POINT of the journey. - - - - - Reference to a SCHEDULED STOP POINT that is a VIA point on the journey. - - - - - Reference to the destination SCHEDULED STOP POINT of the journey. - - - - - Type for reference to a DESTINATION. - - - - - - - - - Information that classifies journey. - - - - - OPERATOR of a VEHICLE JOURNEY. Note that the operator may change over the course of a journey. This shoudl show teh operator for the curent point in the journey. Use Journey Parts tp record all the operators in the whole journeyh. - - - - - Product Classification of VEHICLE 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. -Corresponds to NeTEX TYPE OF SERVICe. - - - - - - - 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. - - - - - - - - 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 still 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 cancelled. - - - - - Service has arrived. - - - - - - - There is no information about the service. - - - - - Service is not expected to call this stop. For instance a flexible service that has not yet been preordered. - - - - - - - Classification of the State of the VEHICLE JOURNEY according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are still classified as on-time. Applications may use this to guide their own presentation of times. - - - - - Service is expected to be performed. - - - - - Service is not expected to be run. For instance a flexible service that has not yet been preordered. - - - - - - - - - Service has departed from first stop. - - - - - - - It has been detected that the Service was completed. - - - - - It is assumed that the Service has completed. - - - - - - - - Classification of the quality of the prediction 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). - - - - - - - Allowed types activity for FirstOrLastJourney. - - - - - - - - - - - - Allowed values for PredictionInaccurateReason, i.e., possible reasons for a change in prediction (in)accuracy. - - - - - Prediction is inaccurate because of a traffic jam. - - - - - Prediction is inaccurate because of technical problems. - - - - - Prediction is inaccurate because of a despatching alteration. - - - - - Prediction is inaccurate because communication errors have prevented any updates. - - - - - Prediction is inaccurate but the reason for an inaccurate prediction is unknown. - - - - - - - - Allowed types of relation between JOURNEYs. - - - - - The journey is a continuation of the specified RelatedJourney at the stop point given in CallInfo. -Passengers don't need to change vehicles. The new journey is not communicated as an interchange. - - - - - The journey is continued by the specified RelatedJourney at the stop point given in CallInfo. -Passengers don't need to change vehicles. The new journey is not communicated as an interchange. - - - - - The journey splits into multiple RelatedJourneys at the stop point given in CallInfo. - - - - - The journey is a continuation of a single RelatedJourney splitting into multiple journeys at the stop point given in CallInfo. - - - - - The journey is the continuation of multiple RelatedJourneys joining together at the stop point given in CallInfo. - - - - - The journey is continued by a single RelatedJourney after joining other journeys at the stop point given in CallInfo. - - - - - The journey replaces one or more partially or fully cancelled RelatedJourneys during the JourneyPart defined or referenced in JourneyPartInfo. - - - - - The partially or fully cancelled journey is replaced by one or more RelatedJourneys during the JourneyPart defined or referenced in JourneyPartInfo. - - - - - The journey partially or fully supports one or more RelatedJourneys during the JourneyPart defined or referenced in JourneyPartInfo. - - - - - The journey is partially or fully supported by one or more RelatedJourneys during the JourneyPart defined or referenced in JourneyPartInfo. - - - - - - - - Allowed values for characterisation of nested QUAYs as part of a STOP ASSIGNMENT. +SIRI v2.1 - - - - - A type of QUAY that consists of multiple QUAYs of type 'platform'. Examples of such groups would be the lower and upper level of a station. - - - - - A type of QUAY that consists of at least two child QUAYs of type 'platformEdge'. - - - - - A type of QUAY which allows direct access to a VEHICLE, e.g. an on-street bus stop, or consists of multiple child QUAYs of type 'platformSector'. - - - - - A QUAY of type 'platformEdge' may be divided into multiple sectors, e.g. "A", "B", "C" etc., to help passengers find a specific part of a vehicle. -The first class carriage of a TRAIN might, for example, be assigned to sector "A" of a QUAY. - - - - - - - - Allowed values for TYPE OF TRAIN ELEMENT. +SIRI v2.1 - - - - - - - - - - - - - - - Allowed values for TRAIN SIZE. +SIRI v2.1 - - - - - - - - - - Allowed values for TYPE OF FUEL. +SIRI v2.1 - - - - - - - - - - - - - - - Classification of FARE CLASSes. +SIRI v2.1 - - - - - List of FARE CLASSes. +SIRI v2.1 - - - - - List of values for FARE CLASSes. +SIRI v2.1 - - - - - - Values for Fare Class Facility. +SIRI v2.1 - - - - - pti23_0 - - - - - pti23_6 - - - - - pti23_7 - - - - - pti23_8 - - - - - - pti23_6_1 - - - - - Business Class - pti23_10 - - - - - Standard class Add pti23_7 - - - - - - pti23_9 - - - - - - - - Allowed values for VEHICLE IN FORMATION STATUS CODE. +SIRI v2.1 - - - - - - - - - - - - - - - - - - Allowed values for FORMATION CHANGE CODE. +SIRI v2.1 - - - - - - - - - - - - - - - - -       + + + + + + main schema + e-service developers + Cen TC278 WG3 SG7 Team + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2004-03-05 + + + 2004-10-06 + + + 2005-05-11 + + + 2005-11-15 + + + 2007-03-29 + + + 2008-11-13 + + + + 2011-04-18 + + + + 2012-03-22 + + + + 2013-02-11 + + + +

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

      +

      This subschema defines identifer definitions for common journey elements.

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_journey_support.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_types.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG CML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of identifers common journey elements + Standard +       +       + SIRI Journey Model Identifiers. +       + + + + + + + Elements identifying VEHICLE JOURNEY. + + + + + Reference to a LINE. + + + + + Reference to a DIRECTION, typically outward or return. + + + + + A reference to the dated VEHICLE JOURNEY that the VEHICLE is making. + + + + + + + Elements identifying a VEHICLE JOURNEY. LINE and DIRECTION will be same as for journey unless overridden. + + + + + Reference to LINE of journey. + + + + + Reference to DIRECTION of journey. + + + + + A reference to the DATED VEHICLE JOURNEY that the VEHICLE is making, unique with the data horizon of the service. + + + + + + + + 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. + + + + + + Type for Origin and Destination stop of a VEHICLE JOURNEY. + + + + + The origin is used to help identify the VEHICLE JOURNEY. + + + + + Departure time from origin SCHEDULED STOP POINT. + + + + + The destination is used to help identify the VEHICLE JOURNEY. + + + + + Arrival time at destination SCHEDULED STOP POINT. + + + + + + + + Type for a reference to a connecting journey. + + + + + A reference to the DATE VEHICLE JOURNEY that the VEHICLE is making, unique with the data horizon of the service. + + + + + Identify a VEHICLE JOURNEY indirectly by origin and destination as well as the scheduled times at these stops. + + + + + Reference to LINE of journey. + + + + + Reference to TRAIN NUMBER of journey. + + + + + Reference to OPERATOR of journey. + + + + + PARTICIPANT reference that identifies data producer of journey. + + + + + + + + Type for identifer of a SERVICE JOURNEY INTERCHANGE. + + + + + + Type for reference to a SERVICE JOURNEY INTERCHANGE. + + + + + + + + Reference to a SERVICE JOURNEY INTERCHANGE. + + + + + + Type for identifer of a VEHICLE JOURNEY within data Horizon of a service. + + + + + identifier of data frame within particpant service. Used to ensure that the Reference to a DATED VEGICLE JOURNEY 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 identifier of a data VERSION FRAME. + + + + + + Type for identifier of a data VERSION FRAME. + + + + + + + + + Type for identifier of Train Part. + + + + + + Type for reference to a Train Part. + + + + + + + + + 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). + + + + + + + + + Type for identifier of an JOURNEY PART + + + + + + Type for reference to a JOURNEY PART + + + + + + + + Type for identifier of an TRAIN NUMBER + + + + + + Type for reference to a TRAIN NUMBER + + + + + + + + Type for identifier of a TRAIN ELEMENT. An elementary component of a TRAIN (e.g. wagon, locomotive etc.). +SIRI v2.1 + + + + + + Type for reference to a TRAIN ELEMENT. +SIRI v2.1 + + + + + + + + Reference to a TRAIN ELEMENT. +SIRI v2.1 + + + + + Type for identifier of a TRAIN COMPONENT. A TRAIN ELEMENT with a specific order within a TRAIN. +SIRI v2.1 + + + + + + Type for reference to a TRAIN COMPONENT. +SIRI v2.1 + + + + + + + + Reference to a TRAIN COMPONENT. +SIRI v2.1 + + + + + Type for identifier of a TRAIN. An ordered sequence of TRAIN ELEMENTs or TRAIN COMPONENTs respectively. +SIRI v2.1 + + + + + + Type for reference to a TRAIN. +SIRI v2.1 + + + + + + + + Reference to a TRAIN. +SIRI v2.1 + + + + + Type for identifier of a COMPOUND TRAIN. An ordered sequence of TRAINs or TRAIN IN COMPOUND TRAINs respectively. +SIRI v2.1 + + + + + + Type for reference to a COMPOUND TRAIN. +SIRI v2.1 + + + + + + + + Reference to a COMPOUND TRAIN. +SIRI v2.1 + + + + + Type for identifier of a TRAIN IN COMPOUND TRAIN. A TRAIN with a specific order within a COMPOUND TRAIN. +SIRI v2.1 + + + + + + Type for reference to a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 + + + + + + + + Reference to a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 + + + + + Type for identifier of an ENTRANCE TO VEHICLE, e.g. a door of a TRAIN ELEMENT. +SIRI v2.1 + + + + + + Type for reference to an ENTRANCE TO VEHICLE. +SIRI v2.1 + + + + + + + + Reference to an ENTRANCE TO VEHICLE. +SIRI v2.1 + + + + + + Groups together the relevant references needed in a formation. +SIRI v2.1 +Has the following uses: +- Either the smallest part of a formation, a TRAIN COMPONENT, is referenced or the TRAIN itself. The former is ideally used in a FORMATION ASSIGNMENT, i.e. QUAY (sector) assignment, to provide the highest level of detail for passenger orientation. +- If the formation consists of multiple coupled TRAINs, a reference to the COMPOUND TRAIN is also possible. This might be used in a FORMATION CONDITION to signal a change of the train composition. +- In case alighting/boarding data from an automatic passenger counting system is available, the respective vehicle entrances may be referenced. + + + + + + + + + + + + + Allowed types activity for Boarding and Alighting. + + + + + + + + + + + Allowed types activity for Alighting. + + + + + + + + + + Allowed types activity for Boarding. + + + + + + + + + + + + Reference to the origin SCHEDULED STOP POINT of the journey. + + + + + Reference to a SCHEDULED STOP POINT that is a VIA point on the journey. + + + + + Reference to the destination SCHEDULED STOP POINT of the journey. + + + + + Type for reference to a DESTINATION. + + + + + + + + + Information that classifies journey. + + + + + OPERATOR of a VEHICLE JOURNEY. Note that the operator may change over the course of a journey. This shoudl show teh operator for the curent point in the journey. Use Journey Parts tp record all the operators in the whole journeyh. + + + + + Product Classification of VEHICLE 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. +Corresponds to NeTEX TYPE OF SERVICe. + + + + + + + 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. + + + + + + + + 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 still 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 cancelled. + + + + + Service has arrived. + + + + + + + There is no information about the service. + + + + + Service is not expected to call this stop. For instance a flexible service that has not yet been preordered. + + + + + + + Classification of the State of the VEHICLE JOURNEY according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are still classified as on-time. Applications may use this to guide their own presentation of times. + + + + + Service is expected to be performed. + + + + + Service is not expected to be run. For instance a flexible service that has not yet been preordered. + + + + + + + + + Service has departed from first stop. + + + + + + + It has been detected that the Service was completed. + + + + + It is assumed that the Service has completed. + + + + + + + + Classification of the quality of the prediction 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). + + + + + + + Allowed types activity for FirstOrLastJourney. + + + + + + + + + + + + Allowed values for PredictionInaccurateReason, i.e., possible reasons for a change in prediction (in)accuracy. + + + + + Prediction is inaccurate because of a traffic jam. + + + + + Prediction is inaccurate because of technical problems. + + + + + Prediction is inaccurate because of a despatching alteration. + + + + + Prediction is inaccurate because communication errors have prevented any updates. + + + + + Prediction is inaccurate but the reason for an inaccurate prediction is unknown. + + + + + + + + Allowed types of relation between JOURNEYs. + + + + + The journey is a continuation of the specified RelatedJourney at the stop point given in CallInfo. +Passengers don't need to change vehicles. The new journey is not communicated as an interchange. + + + + + The journey is continued by the specified RelatedJourney at the stop point given in CallInfo. +Passengers don't need to change vehicles. The new journey is not communicated as an interchange. + + + + + The journey splits into multiple RelatedJourneys at the stop point given in CallInfo. + + + + + The journey is a continuation of a single RelatedJourney splitting into multiple journeys at the stop point given in CallInfo. + + + + + The journey is the continuation of multiple RelatedJourneys joining together at the stop point given in CallInfo. + + + + + The journey is continued by a single RelatedJourney after joining other journeys at the stop point given in CallInfo. + + + + + The journey replaces one or more partially or fully cancelled RelatedJourneys during the JourneyPart defined or referenced in JourneyPartInfo. + + + + + The partially or fully cancelled journey is replaced by one or more RelatedJourneys during the JourneyPart defined or referenced in JourneyPartInfo. + + + + + The journey partially or fully supports one or more RelatedJourneys during the JourneyPart defined or referenced in JourneyPartInfo. + + + + + The journey is partially or fully supported by one or more RelatedJourneys during the JourneyPart defined or referenced in JourneyPartInfo. + + + + + + + + Allowed values for characterisation of nested QUAYs as part of a STOP ASSIGNMENT. +SIRI v2.1 + + + + + A type of QUAY that consists of multiple QUAYs of type 'platform'. Examples of such groups would be the lower and upper level of a station. + + + + + A type of QUAY that consists of at least two child QUAYs of type 'platformEdge'. + + + + + A type of QUAY which allows direct access to a VEHICLE, e.g. an on-street bus stop, or consists of multiple child QUAYs of type 'platformSector'. + + + + + A QUAY of type 'platformEdge' may be divided into multiple sectors, e.g. "A", "B", "C" etc., to help passengers find a specific part of a vehicle. +The first class carriage of a TRAIN might, for example, be assigned to sector "A" of a QUAY. + + + + + + + + Allowed values for TYPE OF TRAIN ELEMENT. +SIRI v2.1 + + + + + + + + + + + + + + + Allowed values for TRAIN SIZE. +SIRI v2.1 + + + + + + + + + + Allowed values for TYPE OF FUEL. +SIRI v2.1 + + + + + + + + + + + + + + + Classification of FARE CLASSes. +SIRI v2.1 + + + + + List of FARE CLASSes. +SIRI v2.1 + + + + + List of values for FARE CLASSes. +SIRI v2.1 + + + + + + Values for Fare Class Facility. +SIRI v2.1 + + + + + pti23_0 + + + + + pti23_6 + + + + + pti23_7 + + + + + pti23_8 + + + + + + pti23_6_1 + + + + + Business Class - pti23_10 + + + + + Standard class Add pti23_7 + + + + + + pti23_9 + + + + + + + + Allowed values for VEHICLE IN FORMATION STATUS CODE. +SIRI v2.1 + + + + + + + + + + + + + + + + + + Allowed values for FORMATION CHANGE CODE. +SIRI v2.1 + + + + + + + + + + + + + + + + +       diff --git a/xsd/siri_model/siri_modelPermissions.xsd b/xsd/siri_model/siri_modelPermissions.xsd index c8ff6856..51e9e4bf 100644 --- a/xsd/siri_model/siri_modelPermissions.xsd +++ b/xsd/siri_model/siri_modelPermissions.xsd @@ -1,338 +1,338 @@ - - - - - - - - - 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/schema/2.0/xsd/siri_model}siri_modelPermissions.xsd - [ISO 639-2/B] ENG - CEN - - http://www.siri.org.uk/schema/2.0/xsd/siri_types.xsd - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIGXML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI XML schema. Common Permission elements. - Standard -       -       -       - - - Type for abstract permissions. - - - - - Version of permission set. - - - - - - - - - The LINEs that the participant may access. - - - - - - - Participant's permission for this LINE. - - - - - - - - Type for Line Permission. - - - - - - - Reference to a LINE. whose data participant is allowed to access. - - - - - Reference to a DIRECTION of LINE. that participant is allowed to access. - - - - - - - - - The OPERATOR data that the participant may access. - - - - - - - Participant's permission for this OPERATOR. - - - - - - - - Type for OPERATOR Permission. - - - - - - - Reference to an OPERATOR whose data participant is allowed to access. - - - - - - - - - The CONNECTION links that the participant may access. - - - - - - - Participant's permission for this CONNECTION link. - - - - - - - - Type for CONNECTION link Permission. - - - - - - - Reference to a CONNECTION link for which permission is made. - - - - - - - - - Type for Monitoring Point (LOGICAL DISPLAY) Permission. - - - - - - - Reference to a Stop Monitoring point (LOGICAL DISPLAY) to which permission applies. - - - - - - - - - - Whether results can be filtered by VALIDITY PERIOD. 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 (LOGICAL DISPLAY). 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 SCHEDULED STOP POINT. Default is 'true'. - - - - - Whether results can be filtered by SERVICE JOURNEY INTERCHANGE. Default is 'false'. - - - - - Whether results can be filtered by VEHICLE JOURNEY. Default is 'false'. - - - - - Whether results can be filtered by Facility (EQUIPMENT). Default is 'true'. - - - - - Whether results can be filtered by VEHICLE MODE. Default is 'true'. +SIRI v2.1 - - - - - Whether results can be filtered by PRODUCT CATEGORY. Default is 'true'. +SIRI v2.1 - - - - - - Type for Monitoring Service Capability access control. - - - - - - - - - - - - - - - Permission for a single participant or all participants to use an aspect of the service. - - - - - Type for Monitoring Service Permission. - - - - - - - - - - - - - - - Abstract type for 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 (LOGICAL DISPLAY) is supported. Default is 'true'. - - - - - If access control is supported, whether access control by CONNECTION link is supported. Default is 'true'. - - -       + + + + + + + + + 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/schema/2.0/xsd/siri_model}siri_modelPermissions.xsd + [ISO 639-2/B] ENG + CEN + + http://www.siri.org.uk/schema/2.0/xsd/siri_types.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIGXML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI XML schema. Common Permission elements. + Standard +       +       +       + + + Type for abstract permissions. + + + + + Version of permission set. + + + + + + + + + The LINEs that the participant may access. + + + + + + + Participant's permission for this LINE. + + + + + + + + Type for Line Permission. + + + + + + + Reference to a LINE. whose data participant is allowed to access. + + + + + Reference to a DIRECTION of LINE. that participant is allowed to access. + + + + + + + + + The OPERATOR data that the participant may access. + + + + + + + Participant's permission for this OPERATOR. + + + + + + + + Type for OPERATOR Permission. + + + + + + + Reference to an OPERATOR whose data participant is allowed to access. + + + + + + + + + The CONNECTION links that the participant may access. + + + + + + + Participant's permission for this CONNECTION link. + + + + + + + + Type for CONNECTION link Permission. + + + + + + + Reference to a CONNECTION link for which permission is made. + + + + + + + + + Type for Monitoring Point (LOGICAL DISPLAY) Permission. + + + + + + + Reference to a Stop Monitoring point (LOGICAL DISPLAY) to which permission applies. + + + + + + + + + + Whether results can be filtered by VALIDITY PERIOD. 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 (LOGICAL DISPLAY). 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 SCHEDULED STOP POINT. Default is 'true'. + + + + + Whether results can be filtered by SERVICE JOURNEY INTERCHANGE. Default is 'false'. + + + + + Whether results can be filtered by VEHICLE JOURNEY. Default is 'false'. + + + + + Whether results can be filtered by Facility (EQUIPMENT). Default is 'true'. + + + + + Whether results can be filtered by VEHICLE MODE. Default is 'true'. +SIRI v2.1 + + + + + Whether results can be filtered by PRODUCT CATEGORY. Default is 'true'. +SIRI v2.1 + + + + + + Type for Monitoring Service Capability access control. + + + + + + + + + + + + + + + Permission for a single participant or all participants to use an aspect of the service. + + + + + Type for Monitoring Service Permission. + + + + + + + + + + + + + + + Abstract type for 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 (LOGICAL DISPLAY) is supported. Default is 'true'. + + + + + If access control is supported, whether access control by CONNECTION link is supported. Default is 'true'. + + +       diff --git a/xsd/siri_model/siri_modes.xsd b/xsd/siri_model/siri_modes.xsd index 09304d9e..c2a8f264 100644 --- a/xsd/siri_model/siri_modes.xsd +++ b/xsd/siri_model/siri_modes.xsd @@ -1,686 +1,686 @@ - - - - - - main schema - e-service developers - Add names - Europe - >Drafted for version 1.0 Kizoom Incident Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk - - 2004-09-29 - - - 2004-10-01 - - - 2005-02-14 - - - 2007-03-29 - - -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_modes.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - - Kizoom 2000-2005, CEN 2009-2020 - - -
        -
      • Schema derived Derived from the Kizoom XTIS schema
        • -
      • Derived from the TPEG Categories schema
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of common Mode elements - Standard -       -       - SIRI TRANSPORT MODEs -       - - - - - Transport Sub Modes. - - - - - - - - - PT Transport Sub Modes. - - - - - - - - - - - - - - - - Non PT Road Submodes. - - - - - - - - - Submode of mode. - - - - - - - - - - - - - - - - Vehicle mode- 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. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - DEPRECATED since SIRI 2.1 - - - - - - - - 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. - - - - - - - - - - - - - - - - - - -       + + + + + + main schema + e-service developers + Add names + Europe + >Drafted for version 1.0 Kizoom Incident Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk + + 2004-09-29 + + + 2004-10-01 + + + 2005-02-14 + + + 2007-03-29 + + +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_modes.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + + Kizoom 2000-2005, CEN 2009-2021 + + +
        +
      • Schema derived Derived from the Kizoom XTIS schema
        • +
      • Derived from the TPEG Categories schema
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of common Mode elements + Standard +       +       + SIRI TRANSPORT MODEs +       + + + + + Transport Sub Modes. + + + + + + + + + PT Transport Sub Modes. + + + + + + + + + + + + + + + + Non PT Road Submodes. + + + + + + + + + Submode of mode. + + + + + + + + + + + + + + + + Vehicle mode- 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. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + DEPRECATED since SIRI 2.1 + + + + + + + + TPEG pti03 Coach submodes. + + + + + Values for Coach ModesOfTransport: TPEG pti_table_03. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + TPEG pti04 Metro submodes. + + + + + Values for Metro ModesOfTransport: TPEG pti_table_04. + + + + + + + + + + + + + + + + + + + + TPEG pti05 Bus submodes. + + + + + Values for Bus ModesOfTransport: TPEG pti_table_05, loc_table_10. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + TPEG pti06 Tram submodes. + + + + + Values for Tram ModesOfTransport: TPEG pti_table_06, loc_table_12. + + + + + + + + + + + + + + + + + + + + + + + + + + + + TPEG pti07 Water submodes. + + + + + Values for Water ModesOfTransport: TPEG pti_table_07. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + TPEG pti08 Air submodes. + + + + + Values for Air ModesOfTransport: TPEG pti_table_08. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + TPEG pti09 Telecabin submodes. + + + + + Values for Telecabin ModesOfTransport: TPEG pti_table_09, loc_table_14. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + TPEG pti10 Funicular submodes. + + + + + Values for Funicular ModesOfTransport: TPEG pti_table_10. + + + + + + + + + + + + + + + + + TPEG pti11 Taxi submodes. + + + + + Values for Taxi ModesOfTransport: TPEG pti_table_11. + + + + + + + + + + + + + + + + + + + + + + + + + + TPEG pti12 SelfDrive submodes. + + + + + Values for SelfDrive ModesOfTransport: TPEG pti_table_12. + + + + + + + + + + + + + + + + + + +       diff --git a/xsd/siri_model/siri_monitoredVehicleJourney.xsd b/xsd/siri_model/siri_monitoredVehicleJourney.xsd index 927d89a7..6b52473c 100644 --- a/xsd/siri_model/siri_monitoredVehicleJourney.xsd +++ b/xsd/siri_model/siri_monitoredVehicleJourney.xsd @@ -1,638 +1,638 @@ - - - - - - main schema - e-service developers - Cen TC278 WG3 SG7 Team - Europe - Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2004-03-05 - - - 2004-10-06 - - - 2005-05-11 - - - 2005-11-15 - - - 2007-03-29 - - 2008-11-13 - - - 2011-04-18 - - - 2012-03-22 - - - 2012-04-27 - - - 2012-04-27 - - - -

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

      -

      This subschema defines common journey elements.

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_monitoredVehicleJourney.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd - - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIG CML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of common Journey elements - Standard -       -       - SIRI MONITORED VEHICLE JOURNEY Model. -       - - - - - - Type for Monitored VEHICLE JOURNEY. - - - - - - - - - - - - - - Elements describing the real-time progress of a monitored VEHICLE JOURNEY. - - - - - Whether there is real-time information available for journey. Default is 'true'. -It is recommended to specify a MonitoringError if Monitored is set to 'false'. - - - - - If Monitored is 'false', a (list of) reason(s) for non-availability of real-time data. Examples are "GPS", "GPRS", "Radio" etc. -MonitoringError must not be used if Monitored is omitted or set to 'true'. - - - - - - - - - Elements describing the qua;ity of real-time progress data of a journey. - - - - - Whether the VEHICLE iis 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, default is 'false'. - - - - - - - System originating real-time data. Can be used to make judgements of relative quality and accuracy compared to other feeds. - - - - - Confidence QUALITY LEVEL of data. Default is 'reliable'. - - - - - - - Elements describing the real-time progress of a journey. - - - - - Current geospatial location of VEHICLE. Measured to front of vehicle. - - - - - Time at which location was recorded. If not present assume that the recorded at time on the containing delivery. - - - - - Bearing in compass degrees in which VEHICLE is heading. - - - - - Rate of progress of VEHICLE. Default is 'normal' - - - - - Velocity of VEHICLE. EIther actual speed or average speed may be used. +SIRI v2.0 - - - - - Whether the engine of the vehicle is on. Default is 'true' (+SIRI 2.0) - - - - - - Delay of VEHICLE against schedule, to a precision in seconds. Early times are shown as negative values. - - - - - An arbitrary textual status description of the running of this VEHICLE JOURNEY. (Unbounded 0:* since SIRI 2.0) - - - - - An classification of the progress state of running of this VEHICLE JOURNEY. +SIRI 2.0 - - - - - - - Elements describing the main places bewteen which a VEHICLE JOURNEY runs. - - - - - Origin of the VEHICLE JOURNEY. - - - - - - - - - - - VIA points for VEHICLE JOURNEY - - - - - - - - Relative priority for incliding via in displays. 1 Is high 3 is low. +SIRI v2.0 - - - - - - - - Destination of VEHICLE 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. -For SIRI-SM this is the stop for which data is requested. -For SIRI-VM this is the most recent stop visited by the VEHICLE. - - - - - 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. Default is 'false'. - - - - - - - - Type for a reference to JOURNEY PART. +SIRI v2.0 - - - - - Reference to a JOURNEY part. +SIRI v2.0 - - - - - Train Number for JOURNEY PART +SIRI v2.0 - - - - - Operator of JOURNEY PART. +SIRI v2.0 - - - - - Reference to COMPOUND TRAIN that represents the train formation/composition as a whole (for this JOURNEY PART). +SIRI v2.1 -A journey does always have one or more JOURNEY PARTs for which the train formation/composition remains unchanged. - - - - - - - - Type for a reference to JOURNEY PART. +SIRI v2.1 - - - - - Reference to a JOURNEY part. - - - - - Train Number for JOURNEY PART. - - - - - Operator of JOURNEY PART. - - - - - Reference to COMPOUND TRAIN that represents the train formation/composition as a whole (for this JOURNEY PART). +SIRI v2.1 -A journey does always have one or more JOURNEY PARTs for which the train formation/composition remains unchanged. - - - - - - - - - If no JOURNEY PART reference is available (or in addition to the reference), identify it indirectly by From-/ToStopPointRef and Start-/EndTime (i.e. the scheduled times at these stops). +SIRI v2.1 - - - - - Reference to the SCHEDULED STOP POINT at which the related JOURNEY PART begins. - - - - - Reference to the SCHEDULED STOP POINT at which the related JOURNEY PART ends. - - - - - Time at which the related JOURNEY PART begins. - - - - - Time at which the related JOURNEY PART ends. - - - - - - - - Type for BLOCK part elements of VEHICLE JOURNEY. - - - - - Total number of BLOCK parts making up the train of which this is part. - - - - - Reference to a 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 BLOCKparts, there will be a separate delivery for each BLOCKp art and this element will indicate the vehicles that the journey part uses. - - - - - - TRAIN NUMBERs for journey. +SIRI v2.0 - - - - - - TRAIN NUMBER assigned to VEHICLE JOURNEY. +SIRI 2.0 - - - - - - - - JOURNEY PARTs making up JOURNEY +SIRIv2.0 e. - - - - - - Information about Parts of JOURNEY +SIRI v2.0 - - - - - - - - - - - Operational information about the monitored VEHICLE JOURNEY. - - - - - If a VEHICLE JOURNEY is a coupled journey, i.e. comprises several coupled BLOCKparts, there will be a separate delivery for each BLOCKp art and this element will indicate the vehicles that the journey part uses. - - - - - - TRAIN NUMBERs for journey. +SIRI v2.0 - - - - - - TRAIN NUMBER assigned to VEHICLE JOURNEY. +SIRI 2.0 - - - - - - - - JOURNEY PARTs making up JOURNEY +SIRIv2.0 e. - - - - - - Information about Parts of JOURNEY +SIRI v2.0 - - - - - - - - - - - - - Type for Ordered list of CALLs at previous stop. - - - - - - - - Type for CALL at previous stop. - - - - - - - - - - - - - - - - Type for Current CALL at stop. - - - - - - - - - - - - - Elements for a monitored CALL. - - - - - - - - - - - - - - - - Elements describing the Real-time CALL properties. - - - - - - Exact location that VEHICLE will take up / or has taken at STOP POINT. - - - - - - - Elements describing theProperties specific to a 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. - - - - - - - Elements describing the the arrival of a VEHICLE at a stop. - - - - - - - - - Arrival times for CALL. - - - - - - Latest time at which a VEHICLE will arrive at stop. +SIRI v2.0 - - - - - - - Elements describing the the departure of a VEHICLE from a stop. - - - - - - - - - - Departure times for CALL. - - - - - - Expected departure time of VEHICLE without waiting time due to operational actions. For people at stop this would normally be shown if different from Expected Departure time. +SIRI v2.0. - - - - - Earliest time at which VEHICLE may leave the stop. Used to secure connections. Passengers must be at boarding point by this time to be sure of catching VEHICLE. +SIRI v2.0 - - - - - Prediction quality, either as approcimate level, or more quantitatyive percentile range of predictions will fall within a given range of times. +SIRI v2.0 - - - - - -       + + + + + + main schema + e-service developers + Cen TC278 WG3 SG7 Team + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2004-03-05 + + + 2004-10-06 + + + 2005-05-11 + + + 2005-11-15 + + + 2007-03-29 + + 2008-11-13 + + + 2011-04-18 + + + 2012-03-22 + + + 2012-04-27 + + + 2012-04-27 + + + +

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

      +

      This subschema defines common journey elements.

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_monitoredVehicleJourney.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd + + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG CML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of common Journey elements + Standard +       +       + SIRI MONITORED VEHICLE JOURNEY Model. +       + + + + + + Type for Monitored VEHICLE JOURNEY. + + + + + + + + + + + + + + Elements describing the real-time progress of a monitored VEHICLE JOURNEY. + + + + + Whether there is real-time information available for journey. Default is 'true'. +It is recommended to specify a MonitoringError if Monitored is set to 'false'. + + + + + If Monitored is 'false', a (list of) reason(s) for non-availability of real-time data. Examples are "GPS", "GPRS", "Radio" etc. +MonitoringError must not be used if Monitored is omitted or set to 'true'. + + + + + + + + + Elements describing the qua;ity of real-time progress data of a journey. + + + + + Whether the VEHICLE iis 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, default is 'false'. + + + + + + + System originating real-time data. Can be used to make judgements of relative quality and accuracy compared to other feeds. + + + + + Confidence QUALITY LEVEL of data. Default is 'reliable'. + + + + + + + Elements describing the real-time progress of a journey. + + + + + Current geospatial location of VEHICLE. Measured to front of vehicle. + + + + + Time at which location was recorded. If not present assume that the recorded at time on the containing delivery. + + + + + Bearing in compass degrees in which VEHICLE is heading. + + + + + Rate of progress of VEHICLE. Default is 'normal' + + + + + Velocity of VEHICLE. EIther actual speed or average speed may be used. +SIRI v2.0 + + + + + Whether the engine of the vehicle is on. Default is 'true' (+SIRI 2.0) + + + + + + Delay of VEHICLE against schedule, to a precision in seconds. Early times are shown as negative values. + + + + + An arbitrary textual status description of the running of this VEHICLE JOURNEY. (Unbounded 0:* since SIRI 2.0) + + + + + An classification of the progress state of running of this VEHICLE JOURNEY. +SIRI 2.0 + + + + + + + Elements describing the main places bewteen which a VEHICLE JOURNEY runs. + + + + + Origin of the VEHICLE JOURNEY. + + + + + + + + + + + VIA points for VEHICLE JOURNEY + + + + + + + + Relative priority for incliding via in displays. 1 Is high 3 is low. +SIRI v2.0 + + + + + + + + Destination of VEHICLE 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. +For SIRI-SM this is the stop for which data is requested. +For SIRI-VM this is the most recent stop visited by the VEHICLE. + + + + + 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. Default is 'false'. + + + + + + + + Type for a reference to JOURNEY PART. +SIRI v2.0 + + + + + Reference to a JOURNEY part. +SIRI v2.0 + + + + + Train Number for JOURNEY PART +SIRI v2.0 + + + + + Operator of JOURNEY PART. +SIRI v2.0 + + + + + Reference to COMPOUND TRAIN that represents the train formation/composition as a whole (for this JOURNEY PART). +SIRI v2.1 +A journey does always have one or more JOURNEY PARTs for which the train formation/composition remains unchanged. + + + + + + + + Type for a reference to JOURNEY PART. +SIRI v2.1 + + + + + Reference to a JOURNEY part. + + + + + Train Number for JOURNEY PART. + + + + + Operator of JOURNEY PART. + + + + + Reference to COMPOUND TRAIN that represents the train formation/composition as a whole (for this JOURNEY PART). +SIRI v2.1 +A journey does always have one or more JOURNEY PARTs for which the train formation/composition remains unchanged. + + + + + + + + + If no JOURNEY PART reference is available (or in addition to the reference), identify it indirectly by From-/ToStopPointRef and Start-/EndTime (i.e. the scheduled times at these stops). +SIRI v2.1 + + + + + Reference to the SCHEDULED STOP POINT at which the related JOURNEY PART begins. + + + + + Reference to the SCHEDULED STOP POINT at which the related JOURNEY PART ends. + + + + + Time at which the related JOURNEY PART begins. + + + + + Time at which the related JOURNEY PART ends. + + + + + + + + Type for BLOCK part elements of VEHICLE JOURNEY. + + + + + Total number of BLOCK parts making up the train of which this is part. + + + + + Reference to a 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 BLOCKparts, there will be a separate delivery for each BLOCKp art and this element will indicate the vehicles that the journey part uses. + + + + + + TRAIN NUMBERs for journey. +SIRI v2.0 + + + + + + TRAIN NUMBER assigned to VEHICLE JOURNEY. +SIRI 2.0 + + + + + + + + JOURNEY PARTs making up JOURNEY +SIRIv2.0 e. + + + + + + Information about Parts of JOURNEY +SIRI v2.0 + + + + + + + + + + + Operational information about the monitored VEHICLE JOURNEY. + + + + + If a VEHICLE JOURNEY is a coupled journey, i.e. comprises several coupled BLOCKparts, there will be a separate delivery for each BLOCKp art and this element will indicate the vehicles that the journey part uses. + + + + + + TRAIN NUMBERs for journey. +SIRI v2.0 + + + + + + TRAIN NUMBER assigned to VEHICLE JOURNEY. +SIRI 2.0 + + + + + + + + JOURNEY PARTs making up JOURNEY +SIRIv2.0 e. + + + + + + Information about Parts of JOURNEY +SIRI v2.0 + + + + + + + + + + + + + Type for Ordered list of CALLs at previous stop. + + + + + + + + Type for CALL at previous stop. + + + + + + + + + + + + + + + + Type for Current CALL at stop. + + + + + + + + + + + + + Elements for a monitored CALL. + + + + + + + + + + + + + + + + Elements describing the Real-time CALL properties. + + + + + + Exact location that VEHICLE will take up / or has taken at STOP POINT. + + + + + + + Elements describing theProperties specific to a 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. + + + + + + + Elements describing the the arrival of a VEHICLE at a stop. + + + + + + + + + Arrival times for CALL. + + + + + + Latest time at which a VEHICLE will arrive at stop. +SIRI v2.0 + + + + + + + Elements describing the the departure of a VEHICLE from a stop. + + + + + + + + + + Departure times for CALL. + + + + + + Expected departure time of VEHICLE without waiting time due to operational actions. For people at stop this would normally be shown if different from Expected Departure time. +SIRI v2.0. + + + + + Earliest time at which VEHICLE may leave the stop. Used to secure connections. Passengers must be at boarding point by this time to be sure of catching VEHICLE. +SIRI v2.0 + + + + + Prediction quality, either as approcimate level, or more quantitatyive percentile range of predictions will fall within a given range of times. +SIRI v2.0 + + + + + +       diff --git a/xsd/siri_model/siri_operator_support.xsd b/xsd/siri_model/siri_operator_support.xsd index 47d3b61e..ca28a2d9 100644 --- a/xsd/siri_model/siri_operator_support.xsd +++ b/xsd/siri_model/siri_operator_support.xsd @@ -1,87 +1,87 @@ - - - - - - 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 - Add organisation cidoe - - -

      SIRI Real-time server interface. This subschema defines transport OPERATOR base types.

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_operator_support.xsd - [ISO 639-2/B] ENG - CEN - Add POSTAL ADDRESS - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the SIRI standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI Server Interface for Real-tiem Info - OPERATOR Types. - Standard -       -       - OPERATOR types for SIRi. -       - - - - Reference to an OPERATOR. - - - - - - - - Type for identifier of an OPERATOR Code. - - - - - - - Reference to an Organisation. - - - - - - - - Type for identifier of an OrganisationCode. - - - - -       + + + + + + 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 + Add organisation cidoe + + +

      SIRI Real-time server interface. This subschema defines transport OPERATOR base types.

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_operator_support.xsd + [ISO 639-2/B] ENG + CEN - Add POSTAL ADDRESS + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the SIRI standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI Server Interface for Real-tiem Info - OPERATOR Types. + Standard +       +       + OPERATOR types for SIRi. +       + + + + Reference to an OPERATOR. + + + + + + + + Type for identifier of an OPERATOR Code. + + + + + + + Reference to an Organisation. + + + + + + + + Type for identifier of an OrganisationCode. + + + + +       diff --git a/xsd/siri_model/siri_reference.xsd b/xsd/siri_model/siri_reference.xsd index c2a30990..d0b9ab61 100644 --- a/xsd/siri_model/siri_reference.xsd +++ b/xsd/siri_model/siri_reference.xsd @@ -1,844 +1,844 @@ - - - - - - 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 - - - 2012-03-22 - - - - 2012-06-22 - - - - 2013-02-11 - - - - 2018-11-08 - - - - 2020-01-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/schema/2.0/xsd/siri/utility/}siri_reference.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIG CML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Common DomainModel elements. - Standard -       -       -       - - - - - - - - - - Version Identifier. - - - - - Type for identifier of a Version. - - - - - - Type for reference Timetable Version. - - - - - - - - - Type for identifier of a SCHEDULED STOP POINT. - - - - - - Reference to a SCHEDULED STOP POINT. - - - - - - - - Sequence of visit to SCHEDULED STOP POINT.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. - - - - - Elements for a SCHEDULED STOP POINT. - - - - - Reference to a SCHEDULED STOP POINT. - Reference to a STOP POINT. - - - - - Name of SCHEDULED STOP POINT. (Unbounded since SIRI 2.0) - - - - - - - Reference to a SCHEDULED STOP POINT. - Reference to a STOP POINT. - - - - - Name of SCHEDULED STOP POINT. - - - - - Elements identifying an ordered visit to a SCHEDULED STOP POINT within a SERVICE PATTERN. - - - - - - - - Name of SCHEDULED STOP POINT. (Unbounded since SIRI 2.0) - - - - - - - Elements identifying Ordered visit to a stop within calling sequence of a SERVICE PATTERN. - - - - - - - - Name of SCHEDULED STOP POINT. (Unbounded since SIRI 2.0) - - - - - - - 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. - - - - - - - - - Type for identifier of a STOP AREA. - - - - - - Reference to a STOP AREA. - - - - - - - - - Type for identifier of a QUAY (Platform, Bay, etc). - - - - - - Type for reference to a QUAY. - - - - - - - - - Type for identifier of a BOARDING POSITION (location on a QUAY where passengers can actually board/alight). - - - - - - Type for reference to a BOARDING POSITION. - - - - - - - - - Type for identifier of a FLEXIBLE AREA (area that encompasses the stop location of a flexible service). - - - - - - Type for reference to a FLEXIBLE AREA. - - - - - - - - - Identifier of a monitoring point. May correspond to a SCHEDULED STOP POINT or represent a group of Stops other Timing Points (i.e. LOGICAL DISPLAY) - - - - - - Type for reference to a monitoring point (LOGICAL DISPLAY). - - - - - - - - - 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. Default is false (xml default added from SIRI 2.0) - - - - - - Type for identifier of a CONNECTION link - - - - - - Reference to a CONNECTION link - - - - - Type for reference to a CONNECTION link - - - - - - - - - MODEs of transport applicable to timetabled public transport. - - - - - - - - - - - - - - - MODEs of transport applicable to private and non-timetabled transport. - - - - - - - - - - - - - - Union of VEHICLE and continuous MODEs. - - - - - - - - - - - - - - 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 JOURNEY PATTERN Identfiers associated with a journey. - - - - - - - Elements describing the LINE, ROUTE and DIRECTION of a VEHICLE JOURNEYwhich are derived from the JOURNEY PATTERN associated with the 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. - - - - - Name of Joruney Pattern - - - - - A means of transportation such as bus, rail, etc. - - - - - Identifier of ROUTE that journey follows. - - - - - Name or Number by which the LINE is known to the public. (Unbounded since SIRI 2.0) - - - - - Reference to a GROUP OF LINEs to which journey belongs. SIRI 2.0 - - - - - Description of the DIRECTION. May correspond to a DESTINATION DISPLAY. (Unbounded since SIRI 2.0) - - - - - Alternative identifier of LINE that an external system may associate with journey. - - - - - - Reference to a BRANDING. +SIRI v2.1 - - - - - An arbitrary marketing classification. +SIRI v2.1 - - - - - - - - Elements for identifying a LINE and DIRECTION. - - - - - Reference to a LINE. - - - - - Reference to a LINE DIRECTION DIRECTION, typically outward or return. - - - - - - - Type for LINEand DIRECTION. - - - - - - Elements for a LINE and DIRECTION. - - - - - Line Reference. - - - - - Direction Reference. - - - - - - - Type for identifier of a LINE - - - - - - Reference to a LINE. - - - - - Type for reference to a LINE. - - - - - - - - Elements describing the LINEand DESTINATION of a journey. Values for these elements can be specified on an annual schedule and will be inherited, unless overriden, onto the production timetable and then onto the individul dated VEHICLE JOURNEYs of the timetable. Each real-time journey takes its values from the dated VEHICLE JOURNEY that it follows. The absence of a value on an entity at a given level indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity. - - - - - - Description of the destination stop (vehicle signage), if different from the that in timetable - the DESTINATION DISPLAY. Can be overwritten section by section by the entry in an individual CALL. - - - - - - - Name or Number by which the LINEis known to the public. - - - - - Identifier of a GROUP OF LINEs - - - - - - Reference to a GROUP OF LINEs - - - - - - - - - Type for 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. - - - - - - - - Identifier of a ROUTE LINk. - - - - - - Reference to a ROUTE LINk. - - - - - - - - - Type for identifier of a DESTINATION. - - - - - - Reference 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. - - - - - Reference to a TOPOGRAPHIC PLACE. - - - - - Names of place used to help identify the LINE. - - - - - Short name of TOPOGRAPHIC PLACE. Should only be included if the detail level was requested. - - - - - - - - Identifier of a VEHICLE. - - - - - - Reference to a VEHICLE. - - - - - - - - Reference to a VEHICLE. - - - - - Passenger load status of a VEHICLE - GTFS-R / TPEG Pts045 - - - - - TPEG Pts45_0, unknown - - - - - GTFS-R "EMPTY" - The vehicle is considered empty by most measures, and has few or no passengers onboard, but is still accepting passengers. - - - - - GTFS-R "MANY_SEATS_AVAILABLE" / TPEG Pts45_1, many seats available - The vehicle has a large percentage of seats available. What percentage of free seats out of the total seats available is to be considered large enough to fall into this category is determined at the discretion of the producer. - - - - - GTFS-R "FEW_SEATS_AVAILABLE" / TPEG Pts45_2, few seats available - The vehicle has a small percentage of seats available. What percentage of free seats out of the total seats available is to be considered small enough to fall into this category is determined at the discretion of the producer. - - - - - GTFS-R "STANDING_ROOM_ONLY" / TPEG Pts45_4, standing room only (and TPEG Pts45_3, no seats available) - The vehicle can currently accommodate only standing passengers. - - - - - GTFS-R "CRUSHED_STANDING_ROOM_ONLY" - The vehicle can currently accommodate only standing passengers and has limited space for them. - - - - - GTFS-R "FULL" / TPEG Pts45_5, full - - - - - GTFS-R "NOT_ACCEPTING_PASSENGERS" - The vehicle cannot accept passengers. - - - - - TPEG Pts45_255, undefined occupancy - - - - - (SIRI 2.1) deprecated - use a more specific value - - - - - (SIRI 2.1) deprecated - use a more specific value - - - - - - - Identifier of a DRIVER - - - - - - Reference to a DRIVER. - - - - - - - - - DataType for a NOTICe. - - - - - - - - Text annotation that applies to an element. - - - - - - - - Type for identifier of an Info Channel. - - - - - - Type for reference to an Info Channel. - - - - - - - - - Type for identifier of a BRANDING. +SIRI v2.1 - - - - - - Type for reference to a BRANDING. +SIRI v2.1 - - - - - - - - An arbitrary marketing classification. +SIRI v2.1 - - - - - Identity of BRANDING. - - - - - - - - - Identifier of a SITE - - - - - - Reference to a SITE - - - - - - - - Reference to a SITE - - -       + + + + + + 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 + + + 2012-03-22 + + + + 2012-06-22 + + + + 2013-02-11 + + + + 2018-11-08 + + + + 2020-01-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/schema/2.0/xsd/siri/utility/}siri_reference.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG CML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Common DomainModel elements. + Standard +       +       +       + + + + + + + + + + Version Identifier. + + + + + Type for identifier of a Version. + + + + + + Type for reference Timetable Version. + + + + + + + + + Type for identifier of a SCHEDULED STOP POINT. + + + + + + Reference to a SCHEDULED STOP POINT. + + + + + + + + Sequence of visit to SCHEDULED STOP POINT.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. + + + + + Elements for a SCHEDULED STOP POINT. + + + + + Reference to a SCHEDULED STOP POINT. + Reference to a STOP POINT. + + + + + Name of SCHEDULED STOP POINT. (Unbounded since SIRI 2.0) + + + + + + + Reference to a SCHEDULED STOP POINT. + Reference to a STOP POINT. + + + + + Name of SCHEDULED STOP POINT. + + + + + Elements identifying an ordered visit to a SCHEDULED STOP POINT within a SERVICE PATTERN. + + + + + + + + Name of SCHEDULED STOP POINT. (Unbounded since SIRI 2.0) + + + + + + + Elements identifying Ordered visit to a stop within calling sequence of a SERVICE PATTERN. + + + + + + + + Name of SCHEDULED STOP POINT. (Unbounded since SIRI 2.0) + + + + + + + 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. + + + + + + + + + Type for identifier of a STOP AREA. + + + + + + Reference to a STOP AREA. + + + + + + + + + Type for identifier of a QUAY (Platform, Bay, etc). + + + + + + Type for reference to a QUAY. + + + + + + + + + Type for identifier of a BOARDING POSITION (location on a QUAY where passengers can actually board/alight). + + + + + + Type for reference to a BOARDING POSITION. + + + + + + + + + Type for identifier of a FLEXIBLE AREA (area that encompasses the stop location of a flexible service). + + + + + + Type for reference to a FLEXIBLE AREA. + + + + + + + + + Identifier of a monitoring point. May correspond to a SCHEDULED STOP POINT or represent a group of Stops other Timing Points (i.e. LOGICAL DISPLAY) + + + + + + Type for reference to a monitoring point (LOGICAL DISPLAY). + + + + + + + + + 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. Default is false (xml default added from SIRI 2.0) + + + + + + Type for identifier of a CONNECTION link + + + + + + Reference to a CONNECTION link + + + + + Type for reference to a CONNECTION link + + + + + + + + + MODEs of transport applicable to timetabled public transport. + + + + + + + + + + + + + + + MODEs of transport applicable to private and non-timetabled transport. + + + + + + + + + + + + + + Union of VEHICLE and continuous MODEs. + + + + + + + + + + + + + + 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 JOURNEY PATTERN Identfiers associated with a journey. + + + + + + + Elements describing the LINE, ROUTE and DIRECTION of a VEHICLE JOURNEYwhich are derived from the JOURNEY PATTERN associated with the 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. + + + + + Name of Joruney Pattern + + + + + A means of transportation such as bus, rail, etc. + + + + + Identifier of ROUTE that journey follows. + + + + + Name or Number by which the LINE is known to the public. (Unbounded since SIRI 2.0) + + + + + Reference to a GROUP OF LINEs to which journey belongs. SIRI 2.0 + + + + + Description of the DIRECTION. May correspond to a DESTINATION DISPLAY. (Unbounded since SIRI 2.0) + + + + + Alternative identifier of LINE that an external system may associate with journey. + + + + + + Reference to a BRANDING. +SIRI v2.1 + + + + + An arbitrary marketing classification. +SIRI v2.1 + + + + + + + + Elements for identifying a LINE and DIRECTION. + + + + + Reference to a LINE. + + + + + Reference to a LINE DIRECTION DIRECTION, typically outward or return. + + + + + + + Type for LINEand DIRECTION. + + + + + + Elements for a LINE and DIRECTION. + + + + + Line Reference. + + + + + Direction Reference. + + + + + + + Type for identifier of a LINE + + + + + + Reference to a LINE. + + + + + Type for reference to a LINE. + + + + + + + + Elements describing the LINEand DESTINATION of a journey. Values for these elements can be specified on an annual schedule and will be inherited, unless overriden, onto the production timetable and then onto the individul dated VEHICLE JOURNEYs of the timetable. Each real-time journey takes its values from the dated VEHICLE JOURNEY that it follows. The absence of a value on an entity at a given level indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity. + + + + + + Description of the destination stop (vehicle signage), if different from the that in timetable - the DESTINATION DISPLAY. Can be overwritten section by section by the entry in an individual CALL. + + + + + + + Name or Number by which the LINEis known to the public. + + + + + Identifier of a GROUP OF LINEs + + + + + + Reference to a GROUP OF LINEs + + + + + + + + + Type for 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. + + + + + + + + Identifier of a ROUTE LINk. + + + + + + Reference to a ROUTE LINk. + + + + + + + + + Type for identifier of a DESTINATION. + + + + + + Reference 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. + + + + + Reference to a TOPOGRAPHIC PLACE. + + + + + Names of place used to help identify the LINE. + + + + + Short name of TOPOGRAPHIC PLACE. Should only be included if the detail level was requested. + + + + + + + + Identifier of a VEHICLE. + + + + + + Reference to a VEHICLE. + + + + + + + + Reference to a VEHICLE. + + + + + Passenger load status of a VEHICLE - GTFS-R / TPEG Pts045 + + + + + TPEG Pts45_0, unknown + + + + + GTFS-R "EMPTY" + The vehicle is considered empty by most measures, and has few or no passengers onboard, but is still accepting passengers. + + + + + GTFS-R "MANY_SEATS_AVAILABLE" / TPEG Pts45_1, many seats available + The vehicle has a large percentage of seats available. What percentage of free seats out of the total seats available is to be considered large enough to fall into this category is determined at the discretion of the producer. + + + + + GTFS-R "FEW_SEATS_AVAILABLE" / TPEG Pts45_2, few seats available + The vehicle has a small percentage of seats available. What percentage of free seats out of the total seats available is to be considered small enough to fall into this category is determined at the discretion of the producer. + + + + + GTFS-R "STANDING_ROOM_ONLY" / TPEG Pts45_4, standing room only (and TPEG Pts45_3, no seats available) + The vehicle can currently accommodate only standing passengers. + + + + + GTFS-R "CRUSHED_STANDING_ROOM_ONLY" + The vehicle can currently accommodate only standing passengers and has limited space for them. + + + + + GTFS-R "FULL" / TPEG Pts45_5, full + + + + + GTFS-R "NOT_ACCEPTING_PASSENGERS" + The vehicle cannot accept passengers. + + + + + TPEG Pts45_255, undefined occupancy + + + + + (SIRI 2.1) deprecated - use a more specific value + + + + + (SIRI 2.1) deprecated - use a more specific value + + + + + + + Identifier of a DRIVER + + + + + + Reference to a DRIVER. + + + + + + + + + DataType for a NOTICe. + + + + + + + + Text annotation that applies to an element. + + + + + + + + Type for identifier of an Info Channel. + + + + + + Type for reference to an Info Channel. + + + + + + + + + Type for identifier of a BRANDING. +SIRI v2.1 + + + + + + Type for reference to a BRANDING. +SIRI v2.1 + + + + + + + + An arbitrary marketing classification. +SIRI v2.1 + + + + + Identity of BRANDING. + + + + + + + + + Identifier of a SITE + + + + + + Reference to a SITE + + + + + + + + Reference to a SITE + + +       diff --git a/xsd/siri_model/siri_situation.xsd b/xsd/siri_model/siri_situation.xsd index 4a50d64b..7a76558f 100644 --- a/xsd/siri_model/siri_situation.xsd +++ b/xsd/siri_model/siri_situation.xsd @@ -1,1535 +1,1535 @@ - - - - - - - - - - - - - - - - - - - - - main schema - e-service developers - Waldemar Isajkin (INIT GmbH) - 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 - - - - 2012-03-23 - - - - 2013-02-11 - - - - 2013-10-01 - - - - 2014-06-20 - - - - 2019-09-01 - - - -

      SIRI-SX 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.siri.org.uk/schema/2.0/xsd/}siri_model/siri_situation.xsd - [ISO 639-2/B] ENG - CEN - - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_stop.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modes.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_monitoredVehicleJourney.xsd - - - Kizoom 2000-2005, CEN 2009-2020 - - -
        -
      • Schema Derived from the Kizoom XTIS schema
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI-SX Xml Schema for PT SITUATIONs. Common element subschema - Standard -       -       - SIRI-SX Situation Model. -       - - - - 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. - - - - - Elements identifying a SITUATION element or an update to a SITUATION. Participant reference 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 describing 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 describing 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. - - - - - 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. - - - - - Datex 2 comments for public use. - - - - - Ccomments not for public use. - - - - - Datex 2 model of where event ois taking place on the road. - - - - - - - Datex2 Tarffic element. - - - - - - - - - - Type for Raod scope for scope of SITUATION or effect. - - - - - AFfected Road as described by a Date2x location. - - - - - Optional spatial projection of road. Can be used to distriute the path of the road to systems that do not already hold it. To pass just a Reference, use Datex2 location. - - - - - - - - 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, i.e. 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. - - - - - Reference to an Agent, i.e. Capture client user who input a 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 a SITUATION can be assigned. - - - - - - - Values for Entry Status. - - - - - - - - - - - - - - Type for Publication status. - - - - - - - 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 using TPEG Pts038 AlertCause. - - - - - - - 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. - - - - - Additional reasons - - - - - - Reason - - - - - - - - - - - - - - - Structured Reason elements. The TpegReason and/or PublicEventReason enumerated values can be used to generate standardized messages describing the SITUATION. If no enumerated values are given, ReasonName is used instead. -Note: this means that ReasonName is NOT a complete message, but only a (few) word(s) to be included in the message! - - - - - Structured classification of nature of SITUATION, from which a standardized message can be generated. - - - - - DEPRECATED (SIRI 2.1) - use only TpegReasonGroup and PublicEventReason. - - - - - Structured classification of Public Event, from which a standardized message can be generated. - - - - - Textual classification of nature of SITUATION, from which a standardized message can be generated. Not normally needed, except when TpegReason and PublicEventReason are absent. (Unbounded since SIRI 2.0) - - - - - - - Values for Sensitivity. - - - - - - - - - - - - Values for Audience. - - - - - - - - - - - - - - - Type for Quality of data indication. - - - - - - - - - - Values for ScopeType - TPEG Pts36, AlertForType with additional values - - - - - TPEG Pts36_0, unknown - - - - - TPEG Pts36_1, stop place - - - - - TPEG Pts36_2, line - - - - - TPEG Pts36_3, route - - - - - TPEG Pts36_4, individual PT service - - - - - TPEG Pts36_5, operator - - - - - TPEG Pts36_6, city - - - - - TPEG Pts36_7, area - - - - - TPEG Pts36_8, stop point - - - - - stop place component - - - - - place - - - - - network - - - - - vehicle journey - - - - - dated vehicle journey - - - - - connection link - - - - - interchange - - - - - TPEG Pts36_0, unknown - - - - - general - - - - - road - - - - - TPEG Pts36_255, undefined - - - - - - - - Type for Location model for scope of SITUATION or effect. - - - - - Affected overall Geographic scope. - - - - - 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. - - - - - - Networks and Route(s) affected by SITUATION. - - - - - - - - - - - - - STOP POINTs affected by SITUATION. - - - - - - STOP POINT affected by SITUATION. - - - - - - - - Places other than STOP POINTs affected by SITUATION. - - - - - - STOP PLACE affected by SITUATION. - - - - - - - - Places other than STOP POINTs affected by SITUATION. - - - - - - Place affected by SITUATION. - - - - - - - - Specific journeys affected by SITUATION. - - - - - - Journeys affected by the SITUATION. - - - - - - - - Specific vehicles affected by SITUATION. (+SIRI v2.0) - - - - - - Vehicles affected by the SITUATION. (+SIRi v2.0) - - - - - - - - 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. (Unbounded since SIRI 2.0) - - - - - Description of SITUATION. Should not repeat any strap line included in Summary. (Unbounded since SIRI 2.0) - - - - - Additional descriptive details about the SITUATION (Unbounded since SIRI 2.0). - - - - - Further advice to passengers. (Unbounded since SIRI 2.0) - - - - - For internal information only, not passenger relevant - - - - - 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. Default is 'true'. - - - - - - - - Values for image content. - - - - - - - - - - - - Type for a general hyperlink. - - - - - URI for link. - - - - - Label for Link. (Unbounded since SIRI 2.0) - - - - - 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. - - - - - Condition(s) of effect of disruptione. - - - - - 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. - - - - - - - - Structured elements of a SITUATION condition. The Condition enumerated value(s) can be used to generate standardized messages describing the SITUATION. If no enumerated values are given, ConditionName is used instead. -Note: this means that ConditionName is NOT a complete message, but only a (few) word(s) to be included in the message! - - - - - Structured classification(s) of effect on service, from which a standardized message can be generated. - - - - - Textual classification of effect on service, from which a standardized message can be generated. Not normally needed, except when Condition is absent. - - - - - - - Type for boarding restrictions. - - - - - Type of boarding and alighting allowed at stop. Default is 'Alighting'. - - - - - Type of alighting allowed at stop. Default is 'Boarding'. - - - - - - - Type for (structured) advice. The AdviceType enumerated value can be used to generate standardized messages describing the SITUATION. If no enumerated value is given, AdviceName is used instead. -Note: this means that AdviceName is NOT a complete message, but only a (few) word(s) to be included in the message! -Alternatively, AdviceRef can be used to reference a (complete) standardised advisory message. - - - - - - Reference to a standard advisory NOTICE to be given to passengers if a particular condition arises. - - - - - Structured classification of advice for passengers in the given SITUATION, from which a standardized message can be generated. - - - - - Textual classification of advice, from which a standardized message can be generated. Not normally needed, except when AdviceType is absent. - - - - - Further textual advice to passengers. (Unbounded since SIRI 2.0) - - - - - - - Values for TPEG Pts039 - AdviceType, with some additional values - - - - - TPEG Pts39_0, unknown - - - - - TPEG Pts39_1, use replacement bus - - - - - TPEG Pts39_2, use replacement train - - - - - TPEG Pts39_3, use the alternative route - - - - - TPEG Pts39_4, go on foot - - - - - TPEG Pts39_5, please leave the station! Danger! - - - - - TPEG Pts39_6, no means of travel - - - - - TPEG Pts39_7, use different stops - - - - - TPEG Pts39_8, use alternative stop - - - - - TPEG Pts39_9, do not leave vehicle! Danger! - - - - - TPEG Pts39_10, take advice from announcements - - - - - TPEG Pts39_11, take advice from personnel - - - - - TPEG Pts39_12, obey advice from police - - - - - use other PT services - - - - - use interchange - - - - - no advice - - - - - TPEG Pts39_255, undefined advice - - - - - - - - Type for blocking. - - - - - Whether information about parts of the network identified by Affects should be blocked from computation made by a Journey Planner that has a real-tiem feed of the SITUATIONs. Default is 'false'; do not suppress. - - - - - Whether information about parts of the network identified by 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. (Unbounded since SIRI 2.0) - - - - - Refernce to a fare exceptions code that is allowed because of the disruption. An easement may relax a fare condition, for exampel "You may use your metro ticket on the bus', or 'You may use your bus ticket in teh metro between these two stops'. - - - - - - - - Type for allowed values of DelayBand. Based on Datex2, with some additional values. - - - - - - - - - - - - - - - - - - - Type for easement info. - - - - - Time band into which delay will fall. - - - - - Category of delay. - - - - - Additional journey time needed to overcome disruption. - - - - - - + + + + + + + + + + + + + + + + + + + + + main schema + e-service developers + Waldemar Isajkin (INIT GmbH) + 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 + + + + 2012-03-23 + + + + 2013-02-11 + + + + 2013-10-01 + + + + 2014-06-20 + + + + 2019-09-01 + + + +

      SIRI-SX 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.siri.org.uk/schema/2.0/xsd/}siri_model/siri_situation.xsd + [ISO 639-2/B] ENG + CEN + + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_stop.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modes.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_monitoredVehicleJourney.xsd + + + Kizoom 2000-2005, CEN 2009-2021 + + +
        +
      • Schema Derived from the Kizoom XTIS schema
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI-SX Xml Schema for PT SITUATIONs. Common element subschema + Standard +       +       + SIRI-SX Situation Model. +       + + + + 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. + + + + + Elements identifying a SITUATION element or an update to a SITUATION. Participant reference 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 describing 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 describing 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. + + + + + 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. + + + + + Datex 2 comments for public use. + + + + + Ccomments not for public use. + + + + + Datex 2 model of where event ois taking place on the road. + + + + + + + Datex2 Tarffic element. + + + + + + + + + + Type for Raod scope for scope of SITUATION or effect. + + + + + AFfected Road as described by a Date2x location. + + + + + Optional spatial projection of road. Can be used to distriute the path of the road to systems that do not already hold it. To pass just a Reference, use Datex2 location. + + + + + + + + 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, i.e. 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. + + + + + Reference to an Agent, i.e. Capture client user who input a 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. Default is reliable + + + + + Whether SITUATION is real or a test. + + + + + Likellihoo of a future sutuation happening. + + + + + Publishing status one of a specified set of substates to which a SITUATION can be assigned. + + + + + + + Values for Entry Status. + + + + + + + + + + + + + + Type for Publication status. + + + + + + + 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 using TPEG Pts038 AlertCause. + + + + + + + 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. + + + + + Additional reasons + + + + + + Reason + + + + + + + + + + + + + + + Structured Reason elements. The TpegReason and/or PublicEventReason enumerated values can be used to generate standardized messages describing the SITUATION. If no enumerated values are given, ReasonName is used instead. +Note: this means that ReasonName is NOT a complete message, but only a (few) word(s) to be included in the message! + + + + + Structured classification of nature of SITUATION, from which a standardized message can be generated. + + + + + DEPRECATED (SIRI 2.1) - use only TpegReasonGroup and PublicEventReason. + + + + + Structured classification of Public Event, from which a standardized message can be generated. + + + + + Textual classification of nature of SITUATION, from which a standardized message can be generated. Not normally needed, except when TpegReason and PublicEventReason are absent. (Unbounded since SIRI 2.0) + + + + + + + Values for Sensitivity. + + + + + + + + + + + + Values for Audience. + + + + + + + + + + + + + + + Type for Quality of data indication. + + + + + + + + + + Values for ScopeType - TPEG Pts36, AlertForType with additional values + + + + + TPEG Pts36_0, unknown + + + + + TPEG Pts36_1, stop place + + + + + TPEG Pts36_2, line + + + + + TPEG Pts36_3, route + + + + + TPEG Pts36_4, individual PT service + + + + + TPEG Pts36_5, operator + + + + + TPEG Pts36_6, city + + + + + TPEG Pts36_7, area + + + + + TPEG Pts36_8, stop point + + + + + stop place component + + + + + place + + + + + network + + + + + vehicle journey + + + + + dated vehicle journey + + + + + connection link + + + + + interchange + + + + + TPEG Pts36_0, unknown + + + + + general + + + + + road + + + + + TPEG Pts36_255, undefined + + + + + + + + Type for Location model for scope of SITUATION or effect. + + + + + Affected overall Geographic scope. + + + + + 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. + + + + + + Networks and Route(s) affected by SITUATION. + + + + + + + + + + + + + STOP POINTs affected by SITUATION. + + + + + + STOP POINT affected by SITUATION. + + + + + + + + Places other than STOP POINTs affected by SITUATION. + + + + + + STOP PLACE affected by SITUATION. + + + + + + + + Places other than STOP POINTs affected by SITUATION. + + + + + + Place affected by SITUATION. + + + + + + + + Specific journeys affected by SITUATION. + + + + + + Journeys affected by the SITUATION. + + + + + + + + Specific vehicles affected by SITUATION. (+SIRI v2.0) + + + + + + Vehicles affected by the SITUATION. (+SIRi v2.0) + + + + + + + + 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. (Unbounded since SIRI 2.0) + + + + + Description of SITUATION. Should not repeat any strap line included in Summary. (Unbounded since SIRI 2.0) + + + + + Additional descriptive details about the SITUATION (Unbounded since SIRI 2.0). + + + + + Further advice to passengers. (Unbounded since SIRI 2.0) + + + + + For internal information only, not passenger relevant + + + + + 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. Default is 'true'. + + + + + + + + Values for image content. + + + + + + + + + + + + Type for a general hyperlink. + + + + + URI for link. + + + + + Label for Link. (Unbounded since SIRI 2.0) + + + + + 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. + + + + + Condition(s) of effect of disruptione. + + + + + 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. + + + + + + + + Structured elements of a SITUATION condition. The Condition enumerated value(s) can be used to generate standardized messages describing the SITUATION. If no enumerated values are given, ConditionName is used instead. +Note: this means that ConditionName is NOT a complete message, but only a (few) word(s) to be included in the message! + + + + + Structured classification(s) of effect on service, from which a standardized message can be generated. + + + + + Textual classification of effect on service, from which a standardized message can be generated. Not normally needed, except when Condition is absent. + + + + + + + Type for boarding restrictions. + + + + + Type of boarding and alighting allowed at stop. Default is 'Alighting'. + + + + + Type of alighting allowed at stop. Default is 'Boarding'. + + + + + + + Type for (structured) advice. The AdviceType enumerated value can be used to generate standardized messages describing the SITUATION. If no enumerated value is given, AdviceName is used instead. +Note: this means that AdviceName is NOT a complete message, but only a (few) word(s) to be included in the message! +Alternatively, AdviceRef can be used to reference a (complete) standardised advisory message. + + + + + + Reference to a standard advisory NOTICE to be given to passengers if a particular condition arises. + + + + + Structured classification of advice for passengers in the given SITUATION, from which a standardized message can be generated. + + + + + Textual classification of advice, from which a standardized message can be generated. Not normally needed, except when AdviceType is absent. + + + + + Further textual advice to passengers. (Unbounded since SIRI 2.0) + + + + + + + Values for TPEG Pts039 - AdviceType, with some additional values + + + + + TPEG Pts39_0, unknown + + + + + TPEG Pts39_1, use replacement bus + + + + + TPEG Pts39_2, use replacement train + + + + + TPEG Pts39_3, use the alternative route + + + + + TPEG Pts39_4, go on foot + + + + + TPEG Pts39_5, please leave the station! Danger! + + + + + TPEG Pts39_6, no means of travel + + + + + TPEG Pts39_7, use different stops + + + + + TPEG Pts39_8, use alternative stop + + + + + TPEG Pts39_9, do not leave vehicle! Danger! + + + + + TPEG Pts39_10, take advice from announcements + + + + + TPEG Pts39_11, take advice from personnel + + + + + TPEG Pts39_12, obey advice from police + + + + + use other PT services + + + + + use interchange + + + + + no advice + + + + + TPEG Pts39_255, undefined advice + + + + + + + + Type for blocking. + + + + + Whether information about parts of the network identified by Affects should be blocked from computation made by a Journey Planner that has a real-tiem feed of the SITUATIONs. Default is 'false'; do not suppress. + + + + + Whether information about parts of the network identified by 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. (Unbounded since SIRI 2.0) + + + + + Refernce to a fare exceptions code that is allowed because of the disruption. An easement may relax a fare condition, for exampel "You may use your metro ticket on the bus', or 'You may use your bus ticket in teh metro between these two stops'. + + + + + + + + Type for allowed values of DelayBand. Based on Datex2, with some additional values. + + + + + + + + + + + + + + + + + + + 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/xsd/siri_model/siri_situationActions.xsd b/xsd/siri_model/siri_situationActions.xsd index 79282131..85e6122e 100644 --- a/xsd/siri_model/siri_situationActions.xsd +++ b/xsd/siri_model/siri_situationActions.xsd @@ -1,750 +1,750 @@ - - - - - - - - - - - - - main schema - e-service developers - Add names - Europe - >Drafted for version 1.0 Kizoom SITUATION Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk - - 2006-09-29 - - - 2007-04-17 - - - 2013-10-01 - - - - 2013-05-01 - - - -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/schema/2.0/xsd/siri_model}/siri_situationActions.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd - - - Kizoom 2000-2007, CEN 2009-2020 - - -
        -
      • Schema derived Derived from the Kizoom XTIS schema
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI-SX XML Schema for PT SITUATIONs. Actions subschema - Standard -       -       - SIRI-SX Situation Actions. -       - - - - - Type for list of actions. - - - - - - Description of the whole action to be published. >SIRI 2.0 - - - - - Extension point. - - - - - - - - Type for list of SITUATIONs. - - - - - Processing Status of action at time of SITUATION publication. - - - - - - - - Type for parameterised, i.e. user definable, actions. - - - - - - - Description of action. - - - - - Data associated with action. - - - - - Defines a number of validity periods. When not sent, then the validity periods of higher level are valid. Can be overwritten by deeper level. - - - - - - - - - Type for publication action. - - - - - - - Whether reminders should be sent. - - - - - - Intervals before validity start date to send reminders. - - - - - - - - Whether a clearing notice should be displayed. - - - - - - - - - Values for Progress Status. - - - - - - - - - - Type for list of SITUATIONs. - - - - - Name of action data Element. - - - - - Data type of action data. - - - - - Value for action. - - - - - Display prompt for presenting action to user. (Unbounded since SIRI 2.0) - - - - - Defines the information area where the action has to be published. - - - - - - - - - - - - - - Allowed actions to perform to distribute SITUATION. - - - - - - - - - - - - - - - - - Action: Publish SITUATION To Web. - - - - - Type for Action Publish SITUATION To Web. - - - - - - - Include in SITUATION lists on web site. Default is 'true'. - - - - - Include on home page on web site. Default is 'false'. - - - - - Include in moving ticker band. Default is 'false'. - - - - - Include in social NETWORK indicated by this name. Possible value could be "twitter.com", "facebook.com", "vk.com" and so on. Parameters may be specifed as Action data. (SIRIv 2.10) - - - - - - - - - Action: Publish SITUATION To WAP and PDA. - - - - - Type for Action Publish SITUATION To Displays. - - - - - - - Include in SITUATION lists on mobile site. Default is 'true'. - - - - - Include in home page on mobile site. Default is 'false'. - - - - - - - - - Action: Publish SITUATION To Displays. - - - - - Type for Action Publish SITUATION To Web. - - - - - - - Include in SITUATION lists on station displays. - - - - - Include onboard displays. - - - - - - - - - Action: Publish SITUATION To Alert Service. - - - - - Type for Action Publish SITUATION To Alert Service. - - - - - - - Send as email alert. - - - - - Send as mobile alert by SMS or WAP push. - - - - - - - - - Action: Publish SITUATION To TvService. - - - - - Type for Notify SITUATION to Tv. - - - - - - - Publish to Ceefax. Default is 'true'. - - - - - Publish to Teletext. Default is 'true'. - - - - - - - - - - Action: Publish SITUATION Manually. i.e. a procedure must be carried out. - - - - - - - - - - Type for Action Publish SITUATION Manual process. - - - - - - - - Action: Publish SITUATION to an individual by SMS. - - - - - Type for Notify user by SMS. - - - - - - - MSISDN of user to which to send messages. - - - - - Whether content is flagged as subject to premium charge. - - - - - - - - - Action: Publish SITUATION to a named workgroup or individual by email. - - - - - Type for Notify user by Email. - - - - - - - Email address to which notice should be sent. - - - - - - - - - Action: Publish SITUATION To pager. - - - - - Type for Notify user by Pager. - - - - - - - Reference to a pager group to be notfied. - - - - - Pager number of pager to be notfied. - - - - - - - - - Action: Publish SITUATION To User. - - - - - Type for Notify user by other means. - - - - - - - Workgroup of user to be notified. - - - - - Name of user to be notified. - - - - - Reference to a user to be notified. - - - - - - - - - - - - Description of SITUATION. Should not repeat any strap line included in Summary. - - - - - Prioritises a description from the information owner's point of view, e.g. usable for sorting or hiding individual descriptions. -1 = highest priority. - - - - - - - - - Further consequence to passengers. - - - - - Prioritises a consequence from the information owner's point of view, e.g. usable for sorting or hiding individual consequences. -1 = highest priority. - - - - - - - - - Further information about the duration to passengers. - - - - - - - - - - - - Reference to the action number within the incident concept. - - - - - The time of the last update - - - - - The monotonically inscresing version of the passenger information instance. If absent, is the same version as the enclosing Situation - - - - - The system which created this passenger information. If absent, is the same version as the enclosing Situation - - - - - The organisation which owns this passenger information. - - - - - Perspective of the passenger, e.g. general, vehicleJourney, stopPoint. - - - - - Prioritises a passenger information action from the information owner's point of view, e.g. suitable for sorting or hiding individual passenger information actions. -1 = highest priority. - - - - - All texts of the passenger information. - - - - - - - - - Type for description of the whole action to be published (extends SIRI-SX v2.0p). - - - - - Defines the information area where the action has to be published. - - - - - - - - - - - Description of the whole passenger information of one action. - - - - - - - - - Reason of passenger information action. - - - - - - - - - Further recommendation to passengers. - - - - - Prioritises a recommendation from the information owner's point of view, e.g. usable for sorting or hiding individual recommendations. -1 = highest priority. - - - - - - - - - Further remark to passengers, e,g, "For more information call xy". - - - - - Prioritises a remark from the information owner's point of view, e.g. usable for sorting or hiding individual remarks. -1 = highest priority. - - - - - - - - - Summary of passenger information action. - - - - - - - - - Class of size, e.g. L (large), M (medium), S (small) - - - - - - Content for summary of a passenger information action - - - - - Content for reason of a passenger information action - - - - - Content for n descriptions of a passenger information action. For hiding / sorting descriptions in end devices, a description priority can be set. - - - - - Content for n consequences of a passenger information action. For hiding / sorting descriptions in end devices, a consequence priority can be set. - - - - - Content for n recommendations of a passenger information action. For hiding / sorting descriptions in end devices, a recommendation priority can be set. - - - - - Content for the duration of a passenger information action. - - - - - Content for n remarks of a passenger information action, e,g, "For more information call xy". For hiding / sorting descriptions in end devices, a remark priority can be set. - - - - - Hyperlinks to other resources associated with SITUATION. - - - - - Any images associated with SITUATION. - - - - - for internal information only, not passenger relevant - - - - - - - Values for perspectives. - - - - - - - + + + + + + + + + + + + + main schema + e-service developers + Add names + Europe + >Drafted for version 1.0 Kizoom SITUATION Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk + + 2006-09-29 + + + 2007-04-17 + + + 2013-10-01 + + + + 2013-05-01 + + + +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/schema/2.0/xsd/siri_model}/siri_situationActions.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd + + + Kizoom 2000-2007, CEN 2009-2021 + + +
        +
      • Schema derived Derived from the Kizoom XTIS schema
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI-SX XML Schema for PT SITUATIONs. Actions subschema + Standard +       +       + SIRI-SX Situation Actions. +       + + + + + Type for list of actions. + + + + + + Description of the whole action to be published. >SIRI 2.0 + + + + + Extension point. + + + + + + + + Type for list of SITUATIONs. + + + + + Processing Status of action at time of SITUATION publication. + + + + + + + + Type for parameterised, i.e. user definable, actions. + + + + + + + Description of action. + + + + + Data associated with action. + + + + + Defines a number of validity periods. When not sent, then the validity periods of higher level are valid. Can be overwritten by deeper level. + + + + + + + + + Type for publication action. + + + + + + + Whether reminders should be sent. + + + + + + Intervals before validity start date to send reminders. + + + + + + + + Whether a clearing notice should be displayed. + + + + + + + + + Values for Progress Status. + + + + + + + + + + Type for list of SITUATIONs. + + + + + Name of action data Element. + + + + + Data type of action data. + + + + + Value for action. + + + + + Display prompt for presenting action to user. (Unbounded since SIRI 2.0) + + + + + Defines the information area where the action has to be published. + + + + + + + + + + + + + + Allowed actions to perform to distribute SITUATION. + + + + + + + + + + + + + + + + + Action: Publish SITUATION To Web. + + + + + Type for Action Publish SITUATION To Web. + + + + + + + Include in SITUATION lists on web site. Default is 'true'. + + + + + Include on home page on web site. Default is 'false'. + + + + + Include in moving ticker band. Default is 'false'. + + + + + Include in social NETWORK indicated by this name. Possible value could be "twitter.com", "facebook.com", "vk.com" and so on. Parameters may be specifed as Action data. (SIRIv 2.10) + + + + + + + + + Action: Publish SITUATION To WAP and PDA. + + + + + Type for Action Publish SITUATION To Displays. + + + + + + + Include in SITUATION lists on mobile site. Default is 'true'. + + + + + Include in home page on mobile site. Default is 'false'. + + + + + + + + + Action: Publish SITUATION To Displays. + + + + + Type for Action Publish SITUATION To Web. + + + + + + + Include in SITUATION lists on station displays. + + + + + Include onboard displays. + + + + + + + + + Action: Publish SITUATION To Alert Service. + + + + + Type for Action Publish SITUATION To Alert Service. + + + + + + + Send as email alert. + + + + + Send as mobile alert by SMS or WAP push. + + + + + + + + + Action: Publish SITUATION To TvService. + + + + + Type for Notify SITUATION to Tv. + + + + + + + Publish to Ceefax. Default is 'true'. + + + + + Publish to Teletext. Default is 'true'. + + + + + + + + + + Action: Publish SITUATION Manually. i.e. a procedure must be carried out. + + + + + + + + + + Type for Action Publish SITUATION Manual process. + + + + + + + + Action: Publish SITUATION to an individual by SMS. + + + + + Type for Notify user by SMS. + + + + + + + MSISDN of user to which to send messages. + + + + + Whether content is flagged as subject to premium charge. + + + + + + + + + Action: Publish SITUATION to a named workgroup or individual by email. + + + + + Type for Notify user by Email. + + + + + + + Email address to which notice should be sent. + + + + + + + + + Action: Publish SITUATION To pager. + + + + + Type for Notify user by Pager. + + + + + + + Reference to a pager group to be notfied. + + + + + Pager number of pager to be notfied. + + + + + + + + + Action: Publish SITUATION To User. + + + + + Type for Notify user by other means. + + + + + + + Workgroup of user to be notified. + + + + + Name of user to be notified. + + + + + Reference to a user to be notified. + + + + + + + + + + + + Description of SITUATION. Should not repeat any strap line included in Summary. + + + + + Prioritises a description from the information owner's point of view, e.g. usable for sorting or hiding individual descriptions. +1 = highest priority. + + + + + + + + + Further consequence to passengers. + + + + + Prioritises a consequence from the information owner's point of view, e.g. usable for sorting or hiding individual consequences. +1 = highest priority. + + + + + + + + + Further information about the duration to passengers. + + + + + + + + + + + + Reference to the action number within the incident concept. + + + + + The time of the last update + + + + + The monotonically inscresing version of the passenger information instance. If absent, is the same version as the enclosing Situation + + + + + The system which created this passenger information. If absent, is the same version as the enclosing Situation + + + + + The organisation which owns this passenger information. + + + + + Perspective of the passenger, e.g. general, vehicleJourney, stopPoint. + + + + + Prioritises a passenger information action from the information owner's point of view, e.g. suitable for sorting or hiding individual passenger information actions. +1 = highest priority. + + + + + All texts of the passenger information. + + + + + + + + + Type for description of the whole action to be published (extends SIRI-SX v2.0p). + + + + + Defines the information area where the action has to be published. + + + + + + + + + + + Description of the whole passenger information of one action. + + + + + + + + + Reason of passenger information action. + + + + + + + + + Further recommendation to passengers. + + + + + Prioritises a recommendation from the information owner's point of view, e.g. usable for sorting or hiding individual recommendations. +1 = highest priority. + + + + + + + + + Further remark to passengers, e,g, "For more information call xy". + + + + + Prioritises a remark from the information owner's point of view, e.g. usable for sorting or hiding individual remarks. +1 = highest priority. + + + + + + + + + Summary of passenger information action. + + + + + + + + + Class of size, e.g. L (large), M (medium), S (small) + + + + + + Content for summary of a passenger information action + + + + + Content for reason of a passenger information action + + + + + Content for n descriptions of a passenger information action. For hiding / sorting descriptions in end devices, a description priority can be set. + + + + + Content for n consequences of a passenger information action. For hiding / sorting descriptions in end devices, a consequence priority can be set. + + + + + Content for n recommendations of a passenger information action. For hiding / sorting descriptions in end devices, a recommendation priority can be set. + + + + + Content for the duration of a passenger information action. + + + + + Content for n remarks of a passenger information action, e,g, "For more information call xy". For hiding / sorting descriptions in end devices, a remark priority can be set. + + + + + Hyperlinks to other resources associated with SITUATION. + + + + + Any images associated with SITUATION. + + + + + for internal information only, not passenger relevant + + + + + + + Values for perspectives. + + + + + + +       \ No newline at end of file diff --git a/xsd/siri_model/siri_situationAffects.xsd b/xsd/siri_model/siri_situationAffects.xsd index bda2af3b..b4f6f5de 100644 --- a/xsd/siri_model/siri_situationAffects.xsd +++ b/xsd/siri_model/siri_situationAffects.xsd @@ -1,1532 +1,1533 @@ - - - - - - - - - - - - - - - - - - - - - main schema - e-service developers - Waldemar Isajkin (INIT GmbH) - 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 - - - - 2013-10-10 - - - 2014-06-20 - - - 2018-06-13 - - - 2018-11-08 - - - 2019-05-07 - - - 2020-01-29 - - - -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/}siri_model/siri_situationAffects.xsd - [ISO 639-2/B] ENG - CEN - - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_situationServiceTypes.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modes.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd - - - Kizoom 2000-2007, CEN 2009-2020 - - -
        -
      • Schema derived Derived from the Kizoom XTIS schema
        • -
      - - Version 2.0 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI-SX Xml Schema for PT Incidents. Common affects element subschema - Standard -       -       - SIRI-SX Situation Scope. -       - - - - Type for an SCHEDULED STOP POINT affected by a SITUATION. - - - - - - Alternative private code of stop. - - - - - Name of SCHEDULED STOP POINT. (Unbounded since SIRI 2.0) - - - - - Type of stop type. Normally implicit in VEHICLE mode. TPEG table pti 17_4 - - - - - Spatial coordinates of STOP POINT. Derivable from StopRef. - - - - - Reference of Stop Place related to this affected StopPoint. - - - - - Name of Stop Place related to this affected StopPoint. (Unbounded to allow a text for every language) - - - - - Modes within station/stop affected by the SITUATION. If not specified, assume all modes of that station. - - - - - Reference to a SITE or TOPOGRAPHIC PLACE affected by the Locality of stop (In UK NPtg Locality Code). Derivable from StopRef. - - - - - Name of locality in which stop is found. Derivable from LocalityRef. (Unbounded since SIRI 2.0) - - - - - Assessment of current ACCESSIBILITY of the STOP POINT as affected by the SITUATION. - - - - - Status of STOP - - - - - CONNECTION links from stop. - - - - - - CONNECTION LINKs from stop that are affected by the SITUATION. - - - - - - - - Used to restrict stop points to some lines - - - - - - - - - - - - - Type for TRANSPORT MODEs affecetd by a SITUATION. - - - - - All known modes for stop. - - - - - Mode affected by SITUATION. - - - - - - - - - - - Type for identifier of a ZONe. - - - - - - Type for a reference to a ZONE or locality. - - - - - - - - - - Type for a reference Information about a CONNECTION link from a given stop that is affected by a SITUATION. - - - - - Reference to a CONNECTION link affected by a SITUATION. - - - - - Name of CONNECTION link affected by a SITUATION. - - - - - - - - - Reference to other connecting STOP POINT of a CONNECTION link. 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 link. Derivable from StopRef. (Unbounded since SIRI 2.0) - - - - - Zone in which connecting stop lies. - - - - - - - Direction of SERVICE JOURNEY INTERCHANGE. Default is 'both'. - - - - - PATH LINKs affected by a SITUATION. - - - - - - - - Values for DIRECTION of CONNECTION link or SERVCIE JOURNEY INTERCHANGE. - - - - - - - - - - - Information about a CONNECTION link from a given stop affected by a SITUATION. - - - - - Identifier of CONNECTION link. - - - - - Description of Link. (Unbounded since SIRI 2.0) - - - - - Nature of CONNECTION link. - - - - - Description of a DIRECTION of CONNECTION link. - - - - - 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 SERVICE JOURNEY INTERCHANGE at CONNECTION link from a given SCHEDULED STOP POINT. - - - - - Reference to a SERVICE JOURNEY INTERCHANGE affected by a SITUATION. - - - - - 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. (Unbounded since SIRI 2.0) - - - - - Reference to connecting VEHICLE JOURNEY affected by a SITUATION. - - - - - - Reference to a CONNECTION Link affected by a SITUATION. - - - - - - - - - Type for identifier of an OPERATOR Code. - - - - - - Type for reference to an OPERATOR. - - - - - - - - Type for identifier of an OPERATOR Code. - - - - - - Type for reference to an Operatorational Unit Code. - - - - - - - - Type for Annotated reference to an OPERATOR affected by a SITUATION. - - - - - Reference to an OPERATOR. - - - - - Public Name of OPERATOR. Can be derived from OperatorRef. (Unbounded since SIRI 2.0) - - - - - Short Name for OPERATOR. Can be derived from OperatorRef. (Unbounded since SIRI 2.0) - - - - - OPERATIONAL UNIT responsible for managing services. - - - - - - - - Type for Annotated reference to a NETWORK affected by a SITUATION. - - - - - Reference to a NETWORK. - - - - - Name of NETWORK. Can be derived from NetworkRef. (Unbounded since SIRI 2.0) - - - - - - - - - Type for ideifier of a Route section. - - - - - - Type for reference to a Section. - - - - - - - - Line to which link connects. - - - - - - - - - - Type for identifier of an advisory NOTICE - - - - - - Type for reference to predefined advisory NOTICE. - - - - - - - - - - - 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 a 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 explicitly overridden, 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. (Unbounded since SIRI 2.0) - - - - - Textual description of overall routes affected. Should correspond to any structured description in the AffectedLines element. (Unbounded since SIRI 2.0) - - - - - - - All LINEs in the network are affected. - - - - - Only some ROUTEs are affected, LINE level information not available. See the RoutesAffected element for textual description. - - - - - Only some COMMON SECTIONs are affected, LINE level information not available. - - - - - - Information about the indvidual LINEs in the network that are affected. If not explicitly overridden, modes and submodes will be defaulted to any values present (i) in the AffectedNetwork (ii) In the general context. - - - - - - - - - - Information about the individual LINEs in the network that are affected by a SITUATION. If not explicitly overridden, modes and submodes will be defaulted to any values present (i) in the AffectedNetwork (ii) in the general context. - - - - - Restricts the affected scope to the specified operators of LINEs that are affected by the situation. Overrides any value specified for (i) Affected Network (ii) General Context. - - - - - - Restricts the affected scope to the specified ORIGINs - - - - - Restricts the affected scope to the specified DESTINATIONs - - - - - DIRECTIONs affected. - - - - - Restricts the affected scope to the specified ROUTEs - - - - - - Route affected by Situation. - - - - - - - - Restricts the affected scope to the specified LINE SECTIONs - - - - - - - - - - Used to restrict lines to some stop points - - - - - - - - - - Used to restrict lines to some stop places - - - - - - - - - - - - - Type for information about the SECTIONs affected by a SITUATION. - - - - - - Reference to a section of ROUTE affected by a SITUATION. - - - - - An indirect reference to a COMMON SECTION by stating the stop point ref of the first and last POINT IN JOURNEY PATTERN of the section in question. Intermediate POINTs should be added if necessary to distinguish different sections having the same start and end point and is a means to exclude sections not containing those stop points. - - - - - - - Used to indicate the SCHEDULED stop point at the start of the SECTION - - - - - Used to indicate that any SCHEDULED stop point with a stop assignment to the indicated StopPlace is to be considered as start of the SECTION - - - - - Used to indicate that any SCHEDULED stop point with a stop assignment to the indicated QUAY is to be considered as start of the SECTION - - - - - - - An intermediate Stop POINT of the SECTION that must be part of SECTION - - - - - Used to indicate that at least one SCHEDULED stop point with a stop assignment to the indicated StopPlace must be part of the SECTION - - - - - Used to indicate that at least one SCHEDULED stop point with a stop assignment to the indicated QUAY must be part of the SECTION - - - - - - - Used to indicate the SCHEDULED stop point at the end of the SECTION - - - - - Used to indicate that any SCHEDULED stop point with a stop assignment to the indicated StopPlace is to be considered as end of the SECTION - - - - - Used to indicate that any SCHEDULED stop point with a stop assignment to the indicated QUAY is to be considered as end of the SECTION - - - - - - - - - - Spatial projection of element that can be used to show affected area on a map. - - - - - - - - - An ordered list of MAPPING POINTs defining one single path through the road (or rail) Network. A ROUTE may pass through the same MAPPING POINT more than once. - - - - - Reference to a ROUTE affected by SITUATION. - - - - - DIRECTIONS affected by SITUATION. - - - - - Sections of ROUTE affected by SITUATION. - - - - - - Sections of ROUTE that is affected by SITUATION. - - - - - - - - Stop Poins of the ROUTE. Can be either all or only affected by SITUATION. - - - - - - Indicates whether the list of STOP POINTS contains all STOP POINTS of ROUTE or only affected by SITUATION. - - - - - - Stop Point of the ROUTE - - - - - GIs projection of Link to the next provided StopPoint. NB Line here means Geometry Polyline, not Transmodel Transport Line. - - - - - - - - - ROUTE LINKs affected by SITUATION. - - - - - - - - - - - - - - Type for information about a VEHICLE JOURNEY affected by a SITUATION. - - - - - Use of simple reference is deprecated - - - - Refercence to a VEHICLE JOURENY framed by the day. SIRI 2.0 - - - - - Reference to a service VEHICLE JOURNEY affected by a SITUATION. - - - - - - Reference to a specific DATED VEHICLE JOURNEY affected by a SITUATION. - - - - - Name of journey affected by a SITUATION. (Unbounded since SIRI 2.0) - - - - - OPERATOR of LINE affected by SITUATION. - - - - - Reference to the LINE of the journey affected by an SITUATION. - - - - - - DIRECTION of LINE in which journey runs. - - - - - BLOCK which journey runs. +SIRI 2.0 - - - - - TRAIN NUMBERs for journey. +SIRI v2.0 - - - - - - TRAIN NUMBER assigned to VEHICLE JOURNEY. +SIRI 2.0 - - - - - - - - JOURNEY PARTs making up JOURNEY +SIRIv2.0 e. - - - - - - Information about Parts of JOURNEY +SIRI v2.0 - - - - - - - - Origin SCHEDULED STOP POINTs from which the LINE runs. [equivalent to pti15 1 start_point route_description_type] - - - - - Restricts the affected scope to the specified DESTINATIONs - - - - - ROUTE affected by the SITUATION. - - - - - Timetabled departure tme of journey from Origin. - - - - - Timetabled arrival time of journey at Destination. - - - - - DESTINATION name shown for journey at the origin. Can be Used to identify joruney for user. (+SIRI 2.0), - - - - - DESTINATION name shown for journey at the origin. Can be Used to identify joruney for user. (+SIRI 2.0) - - - - - Accessibility Disruption status ofto JOURNEY, as affected by Situation. - - - - - enum Status of service for this Vehicle Journey - TPEG value. Multiple Conditions can be valid at the same time. (+SIRI 2.0) - - - - - CALLs making up VEHICLE JOURNEY [equivalent to TPEG pti15 3 stop, 15_5 not-stopping, 15-6 temporary stop route_description_type] - - - - - - - - - - Facilities available for VEHICLE JOURNEY (+SIRI 2.0) - - - - - - Facililitiy available for VEHICLE JOURNEY (+SIRI 2.0) - - - - - - - - - - - Type for information about a VEHICLE affected by an SITUATION. - - - - - Reference to a specific VEHICLE affected by an SITUATION. - - - - - Registration plate of VEHICLE - - - - - (Mobile) phone number on which the vehicle can be called - - - - - Internet protocol address of the VEHICLE in form 000.000.000.000 - - - - - Radio address of the VEHICLE - - - - - Reference to VEHICLE JOURNEY that VEHICLE is making. - - - - - Location where the VEHICLE was when the situation arosse - - - - - Current Location of the VEHICLE - - - - - Current Accessibility assessment of vehicle. - - - - - - If a VEHICLE JOURNEY is a coupled journey, i.e. comprises several coupled BLOCKparts, there will be a separate delivery for each BLOCKp art and this element will indicate the vehicles that the journey part uses. - - - - - - Whether the VEHICLE is in traffic congestion. If not, present, not known. - - - - - Whether the panic alarm on the VEHICLE is activated. Default is 'false'. - - - - - Whether this is a Headway Service, that is shown as operating at a prescribed interval rather than to a fixed timetable. Default is 'false'. - - - - - - - - Type for information about a CALL affected by an SITUATION. - - - - - - - Order of visit to stop within JORUNYE PATTERN of journey. - - - - - Status of CALL TPEG 13_6 - - - - - - - - - - - - - - - - - - - - - Elements describing the arrival of a VEHICLE at a SCHEDULED STOP POINT. - - - - - - - - - - - Elements describing the departure of a VEHICLE from a SCHEDULED STOP POINT. - - - - - - - - - - - - Type for information about a FACILITY affected by an SITUATION. (+SIRI 2.0) - - - - - - Identifier of stop point at which availability first applies. - - - - - Identifier of stop point at which availability last applies. - - - - - Name of FACILITY. - - - - - Status of Facility - - - - - - - - - Type for annotated references to a TOPOGRAPHIC PLACE. - - - - - Reference to a SITE or TOPOGRAPHIC PLACE (Locality). - - - - - Alternative identifier of SITE or TOPOGRAPHIC PLACE - - - - - Name of SITE or TOPOGRAPHIC PLACE (locality) in which stop is found. (Unbounded since SIRI 2.0) - - - - - Spatial coordinates of STOP POINT. Derivable from StopRef. - - - - - Category of TOPGRAPHIC PLACE or SITE. - - - - - Reference to an EQUIPMENT found at location. - - - - - Changes to accessibility for SITE. - - - - - - - - - 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. (Unbounded since SIRI 2.0) - - - - - Type of Stop Place. - - - - - Facilities available for VEHICLE JOURNEY (+SIRI 2.0) - - - - - - Facililitiy available for VEHICLE JOURNEY (+SIRI 2.0) - - - - - - - - Quays affected by SITUATION. - - - - - - Quay affected by SITUATION. - - - - - - - - PathLinks affected by SITUATION. - - - - - - - - - - Used to restrict stop places to some lines - - - - - - - - - - - - - - - Type for information about the quays affected by an SITUATION. - - - - - - - Reference to a Stop Place. - - - - - Name of component. (Unbounded since SIRI 2.0) - - - - - Type of Component. - - - - - - Further qualifcation of affected part of Link projection, - - - - - Type of AccessFeature (+SIRI.20) - - - - - Facilities available for component (+SIRI 2.0) - - - - - - Facility available for VEHICLE JOURNEY (+SIRI 2.0) - - - - - - - - - - - - - Type for Information on casualties. - - - - - Number of fatalities. - - - - - Number of injured presons. - - - - - - - Values for STOP PLACE types - TPEG Pts041 and IFOPT - - - - - TPEG Pts41_0, unknown - - - - - TPEG Pts41_1, railway station - - - - - TPEG Pts41_2, underground station - - - - - IFOPT, TPEG Pts41_3, tram station - - - - - IFOPT, TPEG Pts41_4, bus station - - - - - IFOPT, TPEG Pts41_5, airport - - - - - TPEG Pts41_6, pier - - - - - IFOPT, TPEG Pts41_7, harbour port - - - - - ,IFOPT, TPEG Pts41_8, ferry stop - - - - - TPEG Pts41_9, light railway station - - - - - TPEG Pts41_10, cogwheel station - - - - - TPEG Pts41_11, funicular station - - - - - TPEG Pts41_12, ropeway station - - - - - IFOPT, coach station - - - - - IFOPT, ferry port - - - - - IFOPT, on-street bus stop - - - - - IFOPT, on-street tram stop - - - - - IFOPT, ski lift - - - - - IFOPT, other - - - - - TPEG Pts41_255, undefined stop place type - - - - - IFOPT, deprecated (SIRI 2.1), use railwayStation - - - - - IFOPT, deprecated (SIRI 2.1), use undergroundStation - - - - - - - Values for AccessibilityFeature - TPEG Pts040 and IFOPT - - - - - IFOPT, TPEG Pts40_0, unknown - - - - - TPEG Pts40_1, single step - - - - - IFOPT, TPEG Pts40_2, stairs - - - - - IFOPT, TPEG Pts40_3, escalator - - - - - IFOPT, TPEG Pts40_4, travelator / moving walkway - - - - - IFOPT, TPEG Pts40_5, lift / elevator - - - - - IFOPT, TPEG Pts40_6, ramp - - - - - TPEG Pts40_7, mind the gap - - - - - TPEG Pts40_8, tactile paving - - - - - IFOPT, series of stairs - - - - - IFOPT, shuttle - - - - - IFOPT, barrier - - - - - IFOPT, narrow entrance - - - - - IFOPT, confined space - - - - - IFOPT, queue management - - - - - IFOPT, none - - - - - IFOPT, other - - - - - TPEG Pts40_255, undefined accessibility feature type - - - - - -       + + + + + + + + + + + + + + + + + + + + + main schema + e-service developers + Waldemar Isajkin (INIT GmbH) + 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 + + + + 2013-10-10 + + + 2014-06-20 + + + 2018-06-13 + + + 2018-11-08 + + + 2019-05-07 + + + 2020-01-29 + + + +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}siri_model/siri_situationAffects.xsd + [ISO 639-2/B] ENG + CEN + + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_situationServiceTypes.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modes.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd + + + Kizoom 2000-2007, CEN 2009-2021 + + +
        +
      • Schema derived Derived from the Kizoom XTIS schema
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI-SX Xml Schema for PT Incidents. Common affects element subschema + Standard +       +       + SIRI-SX Situation Scope. +       + + + + Type for an SCHEDULED STOP POINT affected by a SITUATION. + + + + + + Alternative private code of stop. + + + + + Name of SCHEDULED STOP POINT. (Unbounded since SIRI 2.0) + + + + + Type of stop type. Normally implicit in VEHICLE mode. TPEG table pti 17_4 + + + + + Spatial coordinates of STOP POINT. Derivable from StopRef. + + + + + Reference of Stop Place related to this affected StopPoint. + + + + + Name of Stop Place related to this affected StopPoint. (Unbounded to allow a text for every language) + + + + + Modes within station/stop affected by the SITUATION. If not specified, assume all modes of that station. + + + + + Reference to a SITE or TOPOGRAPHIC PLACE affected by the Locality of stop (In UK NPtg Locality Code). Derivable from StopRef. + + + + + Name of locality in which stop is found. Derivable from LocalityRef. (Unbounded since SIRI 2.0) + + + + + Assessment of current ACCESSIBILITY of the STOP POINT as affected by the SITUATION. + + + + + Status of STOP + + + + + CONNECTION links from stop. + + + + + + CONNECTION LINKs from stop that are affected by the SITUATION. + + + + + + + + Used to restrict stop points to some lines + + + + + + + + + + + + + Type for TRANSPORT MODEs affecetd by a SITUATION. + + + + + All known modes for stop. + + + + + Mode affected by SITUATION. + + + + + + + + + + + Type for identifier of a ZONe. + + + + + + Type for a reference to a ZONE or locality. + + + + + + + + + + Type for a reference Information about a CONNECTION link from a given stop that is affected by a SITUATION. + + + + + Reference to a CONNECTION link affected by a SITUATION. + + + + + Name of CONNECTION link affected by a SITUATION. + + + + + + + + + Reference to other connecting STOP POINT of a CONNECTION link. 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 link. Derivable from StopRef. (Unbounded since SIRI 2.0) + + + + + Zone in which connecting stop lies. + + + + + + + Direction of SERVICE JOURNEY INTERCHANGE. Default is 'both'. + + + + + PATH LINKs affected by a SITUATION. + + + + + + + + Values for DIRECTION of CONNECTION link or SERVCIE JOURNEY INTERCHANGE. + + + + + + + + + + + Information about a CONNECTION link from a given stop affected by a SITUATION. + + + + + Identifier of CONNECTION link. + + + + + Description of Link. (Unbounded since SIRI 2.0) + + + + + Nature of CONNECTION link. + + + + + Description of a DIRECTION of CONNECTION link. + + + + + 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 SERVICE JOURNEY INTERCHANGE at CONNECTION link from a given SCHEDULED STOP POINT. + + + + + Reference to a SERVICE JOURNEY INTERCHANGE affected by a SITUATION. + + + + + 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. (Unbounded since SIRI 2.0) + + + + + Reference to connecting VEHICLE JOURNEY affected by a SITUATION. + + + + + + Reference to a CONNECTION Link affected by a SITUATION. + + + + + + + + + Type for identifier of an OPERATOR Code. + + + + + + Type for reference to an OPERATOR. + + + + + + + + Type for identifier of an OPERATOR Code. + + + + + + Type for reference to an Operatorational Unit Code. + + + + + + + + Type for Annotated reference to an OPERATOR affected by a SITUATION. + + + + + Reference to an OPERATOR. + + + + + Public Name of OPERATOR. Can be derived from OperatorRef. (Unbounded since SIRI 2.0) + + + + + Short Name for OPERATOR. Can be derived from OperatorRef. (Unbounded since SIRI 2.0) + + + + + OPERATIONAL UNIT responsible for managing services. + + + + + + + + Type for Annotated reference to a NETWORK affected by a SITUATION. + + + + + Reference to a NETWORK. + + + + + Name of NETWORK. Can be derived from NetworkRef. (Unbounded since SIRI 2.0) + + + + + + + + + Type for ideifier of a Route section. + + + + + + Type for reference to a Section. + + + + + + + + Line to which link connects. + + + + + + + + + + Type for identifier of an advisory NOTICE + + + + + + Type for reference to predefined advisory NOTICE. + + + + + + + + + + + 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 a 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 explicitly overridden, 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. (Unbounded since SIRI 2.0) + + + + + Textual description of overall routes affected. Should correspond to any structured description in the AffectedLines element. (Unbounded since SIRI 2.0) + + + + + + + All LINEs in the network are affected. + + + + + Only some ROUTEs are affected, LINE level information not available. See the RoutesAffected element for textual description. + + + + + Only some COMMON SECTIONs are affected, LINE level information not available. + + + + + + Information about the indvidual LINEs in the network that are affected. If not explicitly overridden, modes and submodes will be defaulted to any values present (i) in the AffectedNetwork (ii) In the general context. + + + + + + + + + + Information about the individual LINEs in the network that are affected by a SITUATION. If not explicitly overridden, modes and submodes will be defaulted to any values present (i) in the AffectedNetwork (ii) in the general context. + + + + + Restricts the affected scope to the specified operators of LINEs that are affected by the situation. Overrides any value specified for (i) Affected Network (ii) General Context. + + + + + + Restricts the affected scope to the specified ORIGINs + + + + + Restricts the affected scope to the specified DESTINATIONs + + + + + DIRECTIONs affected. + + + + + Restricts the affected scope to the specified ROUTEs + + + + + + Route affected by Situation. + + + + + + + + Restricts the affected scope to the specified LINE SECTIONs + + + + + + + + + + Used to restrict lines to some stop points + + + + + + + + + + Used to restrict lines to some stop places + + + + + + + + + + + + + Type for information about the SECTIONs affected by a SITUATION. + + + + + + Reference to a section of ROUTE affected by a SITUATION. + + + + + An indirect reference to a COMMON SECTION by stating the stop point ref of the first and last POINT IN JOURNEY PATTERN of the section in question. Intermediate POINTs should be added if necessary to distinguish different sections having the same start and end point and is a means to exclude sections not containing those stop points. + + + + + + + Used to indicate the SCHEDULED stop point at the start of the SECTION + + + + + Used to indicate that any SCHEDULED stop point with a stop assignment to the indicated StopPlace is to be considered as start of the SECTION + + + + + Used to indicate that any SCHEDULED stop point with a stop assignment to the indicated QUAY is to be considered as start of the SECTION + + + + + + + An intermediate Stop POINT of the SECTION that must be part of SECTION + + + + + Used to indicate that at least one SCHEDULED stop point with a stop assignment to the indicated StopPlace must be part of the SECTION + + + + + Used to indicate that at least one SCHEDULED stop point with a stop assignment to the indicated QUAY must be part of the SECTION + + + + + + + Used to indicate the SCHEDULED stop point at the end of the SECTION + + + + + Used to indicate that any SCHEDULED stop point with a stop assignment to the indicated StopPlace is to be considered as end of the SECTION + + + + + Used to indicate that any SCHEDULED stop point with a stop assignment to the indicated QUAY is to be considered as end of the SECTION + + + + + + + + + + Spatial projection of element that can be used to show affected area on a map. + + + + + + + + + An ordered list of MAPPING POINTs defining one single path through the road (or rail) Network. A ROUTE may pass through the same MAPPING POINT more than once. + + + + + Reference to a ROUTE affected by SITUATION. + + + + + DIRECTIONS affected by SITUATION. + + + + + Sections of ROUTE affected by SITUATION. + + + + + + Sections of ROUTE that is affected by SITUATION. + + + + + + + + Stop Poins of the ROUTE. Can be either all or only affected by SITUATION. + + + + + + Indicates whether the list of STOP POINTS contains all STOP POINTS of ROUTE or only affected by SITUATION. + + + + + + Stop Point of the ROUTE + + + + + GIs projection of Link to the next provided StopPoint. NB Line here means Geometry Polyline, not Transmodel Transport Line. + + + + + + + + + ROUTE LINKs affected by SITUATION. + + + + + + + + + + + + + + Type for information about a VEHICLE JOURNEY affected by a SITUATION. + + + + + Use of simple reference is deprecated + + + + Refercence to a VEHICLE JOURENY framed by the day. SIRI 2.0 + + + + + Reference to a service VEHICLE JOURNEY affected by a SITUATION. + + + + + + Reference to a specific DATED VEHICLE JOURNEY affected by a SITUATION. + + + + + Name of journey affected by a SITUATION. (Unbounded since SIRI 2.0) + + + + + OPERATOR of LINE affected by SITUATION. + + + + + Reference to the LINE of the journey affected by an SITUATION. + + + + + + DIRECTION of LINE in which journey runs. + + + + + BLOCK which journey runs. +SIRI 2.0 + + + + + TRAIN NUMBERs for journey. +SIRI v2.0 + + + + + + TRAIN NUMBER assigned to VEHICLE JOURNEY. +SIRI 2.0 + + + + + + + + JOURNEY PARTs making up JOURNEY +SIRIv2.0 e. + + + + + + Information about Parts of JOURNEY +SIRI v2.0 + + + + + + + + Origin SCHEDULED STOP POINTs from which the LINE runs. [equivalent to pti15 1 start_point route_description_type] + + + + + Restricts the affected scope to the specified DESTINATIONs + + + + + ROUTE affected by the SITUATION. + + + + + Timetabled departure tme of journey from Origin. + + + + + Timetabled arrival time of journey at Destination. + + + + + DESTINATION name shown for journey at the origin. Can be Used to identify joruney for user. (+SIRI 2.0), + + + + + DESTINATION name shown for journey at the origin. Can be Used to identify joruney for user. (+SIRI 2.0) + + + + + Accessibility Disruption status ofto JOURNEY, as affected by Situation. + + + + + enum Status of service for this Vehicle Journey - TPEG value. Multiple Conditions can be valid at the same time. (+SIRI 2.0) + + + + + CALLs making up VEHICLE JOURNEY [equivalent to TPEG pti15 3 stop, 15_5 not-stopping, 15-6 temporary stop route_description_type] + + + + + + + + + + Facilities available for VEHICLE JOURNEY (+SIRI 2.0) + + + + + + Facililitiy available for VEHICLE JOURNEY (+SIRI 2.0) + + + + + + + + + + + Type for information about a VEHICLE affected by an SITUATION. + + + + + Reference to a specific VEHICLE affected by an SITUATION. + + + + + Registration plate of VEHICLE + + + + + (Mobile) phone number on which the vehicle can be called + + + + + Internet protocol address of the VEHICLE in form 000.000.000.000 + + + + + Radio address of the VEHICLE + + + + + Reference to VEHICLE JOURNEY that VEHICLE is making. + + + + + Location where the VEHICLE was when the situation arosse + + + + + Current Location of the VEHICLE + + + + + Current Accessibility assessment of vehicle. + + + + + + If a VEHICLE JOURNEY is a coupled journey, i.e. comprises several coupled BLOCKparts, there will be a separate delivery for each BLOCKp art and this element will indicate the vehicles that the journey part uses. + + + + + + Whether the VEHICLE is in traffic congestion. If not, present, not known. + + + + + Whether the panic alarm on the VEHICLE is activated. Default is 'false'. + + + + + Whether this is a Headway Service, that is shown as operating at a prescribed interval rather than to a fixed timetable. Default is 'false'. + + + + + + + + Type for information about a CALL affected by an SITUATION. + + + + + + + Order of visit to stop within JORUNYE PATTERN of journey. + + + + + Status of CALL TPEG 13_6 + + + + + + + + + + + + + + + + + + + + + Elements describing the arrival of a VEHICLE at a SCHEDULED STOP POINT. + + + + + + + + + + + + Elements describing the departure of a VEHICLE from a SCHEDULED STOP POINT. + + + + + + + + + + + + Type for information about a FACILITY affected by an SITUATION. (+SIRI 2.0) + + + + + + Identifier of stop point at which availability first applies. + + + + + Identifier of stop point at which availability last applies. + + + + + Name of FACILITY. + + + + + Status of Facility + + + + + + + + + Type for annotated references to a TOPOGRAPHIC PLACE. + + + + + Reference to a SITE or TOPOGRAPHIC PLACE (Locality). + + + + + Alternative identifier of SITE or TOPOGRAPHIC PLACE + + + + + Name of SITE or TOPOGRAPHIC PLACE (locality) in which stop is found. (Unbounded since SIRI 2.0) + + + + + Spatial coordinates of STOP POINT. Derivable from StopRef. + + + + + Category of TOPGRAPHIC PLACE or SITE. + + + + + Reference to an EQUIPMENT found at location. + + + + + Changes to accessibility for SITE. + + + + + + + + + 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. (Unbounded since SIRI 2.0) + + + + + Type of Stop Place. + + + + + Facilities available for VEHICLE JOURNEY (+SIRI 2.0) + + + + + + Facililitiy available for VEHICLE JOURNEY (+SIRI 2.0) + + + + + + + + Quays affected by SITUATION. + + + + + + Quay affected by SITUATION. + + + + + + + + PathLinks affected by SITUATION. + + + + + + + + + + Used to restrict stop places to some lines + + + + + + + + + + + + + + + Type for information about the quays affected by an SITUATION. + + + + + + + Reference to a Stop Place. + + + + + Name of component. (Unbounded since SIRI 2.0) + + + + + Type of Component. + + + + + + Further qualifcation of affected part of Link projection, + + + + + Type of AccessFeature (+SIRI.20) + + + + + Facilities available for component (+SIRI 2.0) + + + + + + Facility available for VEHICLE JOURNEY (+SIRI 2.0) + + + + + + + + + + + + + Type for Information on casualties. + + + + + Number of fatalities. + + + + + Number of injured presons. + + + + + + + Values for STOP PLACE types - TPEG Pts041 and IFOPT + + + + + TPEG Pts41_0, unknown + + + + + TPEG Pts41_1, railway station + + + + + TPEG Pts41_2, underground station + + + + + IFOPT, TPEG Pts41_3, tram station + + + + + IFOPT, TPEG Pts41_4, bus station + + + + + IFOPT, TPEG Pts41_5, airport + + + + + TPEG Pts41_6, pier + + + + + IFOPT, TPEG Pts41_7, harbour port + + + + + ,IFOPT, TPEG Pts41_8, ferry stop + + + + + TPEG Pts41_9, light railway station + + + + + TPEG Pts41_10, cogwheel station + + + + + TPEG Pts41_11, funicular station + + + + + TPEG Pts41_12, ropeway station + + + + + IFOPT, coach station + + + + + IFOPT, ferry port + + + + + IFOPT, on-street bus stop + + + + + IFOPT, on-street tram stop + + + + + IFOPT, ski lift + + + + + IFOPT, other + + + + + TPEG Pts41_255, undefined stop place type + + + + + IFOPT, deprecated (SIRI 2.1), use railwayStation + + + + + IFOPT, deprecated (SIRI 2.1), use undergroundStation + + + + + + + Values for AccessibilityFeature - TPEG Pts040 and IFOPT + + + + + IFOPT, TPEG Pts40_0, unknown + + + + + TPEG Pts40_1, single step + + + + + IFOPT, TPEG Pts40_2, stairs + + + + + IFOPT, TPEG Pts40_3, escalator + + + + + IFOPT, TPEG Pts40_4, travelator / moving walkway + + + + + IFOPT, TPEG Pts40_5, lift / elevator + + + + + IFOPT, TPEG Pts40_6, ramp + + + + + TPEG Pts40_7, mind the gap + + + + + TPEG Pts40_8, tactile paving + + + + + IFOPT, series of stairs + + + + + IFOPT, shuttle + + + + + IFOPT, barrier + + + + + IFOPT, narrow entrance + + + + + IFOPT, confined space + + + + + IFOPT, queue management + + + + + IFOPT, none + + + + + IFOPT, other + + + + + TPEG Pts40_255, undefined accessibility feature type + + + + + +       diff --git a/xsd/siri_model/siri_situationClassifiers.xsd b/xsd/siri_model/siri_situationClassifiers.xsd index 5d008ac7..621a7ec0 100644 --- a/xsd/siri_model/siri_situationClassifiers.xsd +++ b/xsd/siri_model/siri_situationClassifiers.xsd @@ -1,430 +1,430 @@ - - - - - - main schema - e-service developers - Add names - Europe - Drafted for version 1.0 Kizoom Incident Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk - - 2008-07-05 - - - 2008-07-05 - - - 2008-10-01 - - - - 2019-09-01 - - - -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}/siri_situationClassifiers.xsd - [ISO 639-2/B] ENG - CEN - - - Kizoom 2000-2007, CEN 2009-2020 - - -
        -
      • Schema derived Derived from the Kizoom XTIS schema
        • -
      • Derived from the TPEG Categories schema
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI-SX Xml Schema for PT Incidents. Classifier subschema - Standard -       -       - SIRI-SX Situation Classifiers. -       - - - - - Severity of Incident - TPEG Pti26. Default is 'normal'. - - - - - Values for TPEG Pti26 - Severity - - - - - TPEG Pti26_0, unknown - - - - - TPEG Pti26_1, very slight - - - - - TPEG Pti26_2, slight - - - - - TPEG Pti26_3, normal - - - - - TPEG Pti26_4, severe - - - - - TPEG Pti26_5, very severe - - - - - TPEG Pti26_6, no impact - - - - - TPEG Pti26_255, undefined - - - - - - - - Classification of effect on service. TPEG PTS043 ServiceStatus - - - - - Values for TPEG Pts43 ServiceStatus, with additional values from Pti013 - - - - - TPEG Pts43_0, unknown - - - - - TPEG Pts43_1, delay - - - - - TPEG Pts43_2, minor delays - - - - - TPEG Pts43_3, major delays - - - - - TPEG Pts43_4, operation time extension - - - - - TPEG Pts43_5, on time - - - - - TPEG Pts43_6, disturbance rectified - - - - - TPEG Pts43_7, change of platform - - - - - TPEG Pts43_8, line cancellation - - - - - TPEG Pts43_9, trip cancellation - - - - - TPEG Pts43_10, boarding - - - - - TPEG Pts43_11, go to gate - - - - - TPEG Pts43_12, stop cancelled - - - - - TPEG Pts43_13, stop moved - - - - - TPEG Pts43_14, stop on demand - - - - - TPEG Pts43_15, additional stop - - - - - TPEG Pts43_16, substituted stop - - - - - TPEG Pts43_17, diverted - - - - - TPEG Pts43_18, disruption - - - - - TPEG Pts43_19, limited operation - - - - - TPEG Pts43_20, discontinued operation - - - - - TPEG Pts43_21, irregular traffic - - - - - TPEG Pts43_22, wagon order changed - - - - - TPEG Pts43_23, train shortened - - - - - TPEG Pts43_24, additional ride - - - - - TPEG Pts43_25, replacement ride - - - - - TPEG Pts43_26, temporarily non-stopping - - - - - TPEG Pts43_27, temporary stopplace - - - - - TPEG Pts43_255, undefined status - - - - - TPEG Pti13_1, deprecated (SIRI 2.1) - - - - - TPEG Pti13_2, deprecated (SIRI 2.1) - - - - - TPEG Pti13_3, deprecated (SIRI 2.1) - - - - - TPEG Pti13_5, deprecated (SIRI 2.1) - - - - - TPEG Pti13_6, deprecated (SIRI 2.1) - - - - - TPEG Pti13_7, deprecated (SIRI 2.1) - - - - - TPEG Pti13_8, deprecated (SIRI 2.1) - - - - - TPEG Pti13_10, deprecated (SIRI 2.1) - - - - - TPEG Pti13_11, deprecated (SIRI 2.1) - - - - - TPEG Pti13_12, deprecated (SIRI 2.1) - - - - - TPEG Pti13_13, deprecated (SIRI 2.1) - - - - - TPEG Pti13_14, deprecated (SIRI 2.1) - - - - - TPEG Pti13_15, deprecated (SIRI 2.1) - - - - - TPEG Pti13_16, deprecated (SIRI 2.1) - - - - - TPEG Pti13_17, deprecated (SIRI 2.1) - - - - - TPEG Pti13_18, deprecated (SIRI 2.1) - - - - - TPEG Pti13_19, deprecated (SIRI 2.1) - - - - - TPEG Pti13_255, deprecated (SIRI 2.1) - - - - - - - - Classification of verification status - TPEG Pti032 - - - - - - - - Values for TPEG Pti032 - VerificationStatus - - - - - TPEG Pti32_0, unknown - - - - - TPEG Pti32_1, unverified - - - - - TPEG Pti32_?, verified - - - - - TPEG Pti32_?, verifiedAsDuplicate - - - - - TPEG Pti32_255 ? - - - - - - - - Classification of Predictability status. - - - - - - - - Values for Predictability Status. - - - - - - - -       + + + + + + main schema + e-service developers + Add names + Europe + Drafted for version 1.0 Kizoom Incident Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk + + 2008-07-05 + + + 2008-07-05 + + + 2008-10-01 + + + + 2019-09-01 + + + +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}/siri_situationClassifiers.xsd + [ISO 639-2/B] ENG + CEN + + + Kizoom 2000-2007, CEN 2009-2021 + + +
        +
      • Schema derived Derived from the Kizoom XTIS schema
        • +
      • Derived from the TPEG Categories schema
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI-SX Xml Schema for PT Incidents. Classifier subschema + Standard +       +       + SIRI-SX Situation Classifiers. +       + + + + + Severity of Incident - TPEG Pti26. Default is 'normal'. + + + + + Values for TPEG Pti26 - Severity + + + + + TPEG Pti26_0, unknown + + + + + TPEG Pti26_1, very slight + + + + + TPEG Pti26_2, slight + + + + + TPEG Pti26_3, normal + + + + + TPEG Pti26_4, severe + + + + + TPEG Pti26_5, very severe + + + + + TPEG Pti26_6, no impact + + + + + TPEG Pti26_255, undefined + + + + + + + + Classification of effect on service. TPEG PTS043 ServiceStatus + + + + + Values for TPEG Pts43 ServiceStatus, with additional values from Pti013 + + + + + TPEG Pts43_0, unknown + + + + + TPEG Pts43_1, delay + + + + + TPEG Pts43_2, minor delays + + + + + TPEG Pts43_3, major delays + + + + + TPEG Pts43_4, operation time extension + + + + + TPEG Pts43_5, on time + + + + + TPEG Pts43_6, disturbance rectified + + + + + TPEG Pts43_7, change of platform + + + + + TPEG Pts43_8, line cancellation + + + + + TPEG Pts43_9, trip cancellation + + + + + TPEG Pts43_10, boarding + + + + + TPEG Pts43_11, go to gate + + + + + TPEG Pts43_12, stop cancelled + + + + + TPEG Pts43_13, stop moved + + + + + TPEG Pts43_14, stop on demand + + + + + TPEG Pts43_15, additional stop + + + + + TPEG Pts43_16, substituted stop + + + + + TPEG Pts43_17, diverted + + + + + TPEG Pts43_18, disruption + + + + + TPEG Pts43_19, limited operation + + + + + TPEG Pts43_20, discontinued operation + + + + + TPEG Pts43_21, irregular traffic + + + + + TPEG Pts43_22, wagon order changed + + + + + TPEG Pts43_23, train shortened + + + + + TPEG Pts43_24, additional ride + + + + + TPEG Pts43_25, replacement ride + + + + + TPEG Pts43_26, temporarily non-stopping + + + + + TPEG Pts43_27, temporary stopplace + + + + + TPEG Pts43_255, undefined status + + + + + TPEG Pti13_1, deprecated (SIRI 2.1) + + + + + TPEG Pti13_2, deprecated (SIRI 2.1) + + + + + TPEG Pti13_3, deprecated (SIRI 2.1) + + + + + TPEG Pti13_5, deprecated (SIRI 2.1) + + + + + TPEG Pti13_6, deprecated (SIRI 2.1) + + + + + TPEG Pti13_7, deprecated (SIRI 2.1) + + + + + TPEG Pti13_8, deprecated (SIRI 2.1) + + + + + TPEG Pti13_10, deprecated (SIRI 2.1) + + + + + TPEG Pti13_11, deprecated (SIRI 2.1) + + + + + TPEG Pti13_12, deprecated (SIRI 2.1) + + + + + TPEG Pti13_13, deprecated (SIRI 2.1) + + + + + TPEG Pti13_14, deprecated (SIRI 2.1) + + + + + TPEG Pti13_15, deprecated (SIRI 2.1) + + + + + TPEG Pti13_16, deprecated (SIRI 2.1) + + + + + TPEG Pti13_17, deprecated (SIRI 2.1) + + + + + TPEG Pti13_18, deprecated (SIRI 2.1) + + + + + TPEG Pti13_19, deprecated (SIRI 2.1) + + + + + TPEG Pti13_255, deprecated (SIRI 2.1) + + + + + + + + Classification of verification status - TPEG Pti032 + + + + + + + + Values for TPEG Pti032 - VerificationStatus + + + + + TPEG Pti32_0, unknown + + + + + TPEG Pti32_1, unverified + + + + + TPEG Pti32_?, verified + + + + + TPEG Pti32_?, verifiedAsDuplicate + + + + + TPEG Pti32_255 ? + + + + + + + + Classification of Predictability status. + + + + + + + + Values for Predictability Status. + + + + + + + +       diff --git a/xsd/siri_model/siri_situationIdentity.xsd b/xsd/siri_model/siri_situationIdentity.xsd index 2f0335ee..c1eb84e1 100644 --- a/xsd/siri_model/siri_situationIdentity.xsd +++ b/xsd/siri_model/siri_situationIdentity.xsd @@ -1,247 +1,247 @@ - - - - - - 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/schema/2.0/xsd/siri_utility/}siri_situationIdentity.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri_uility/siri_participant.xsd - - - Kizoom CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIG CML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI-SX XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Common SITUATION Identity elements. - Standard -       -       - SIRI-SX Situation IDentifiers. -       - - - - - - - - - References to a SITUATION. - - - - - - - - - Reference to a SITUATION associated with the element. - - - - - Type for reference to a SITUATION. - - - - - - Reference to a SITUATION. Elements of SITUATION identfier are expressed as atomic elements. - - - - - - - - - Reference to a SITUATION associated with the element. - - - - - Type for identifier of a SITUATION. Includes the Participant identifier and version components of the identifier. - - - - - - Type for reference to a SITUATION. Includes the Particpant identifier and version components of the identifier. - - - - - - - - - Identifier of SITUATION within a Participant. Exclude versionr. - - - - - Type for a referenceUnique identifier of a SITUATION within participant. - - - - - - - - Type for SITUATION 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. Elements 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. - - - - - - - - - Elements 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. - - - - -       + + + + + + 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/schema/2.0/xsd/siri_utility/}siri_situationIdentity.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri_uility/siri_participant.xsd + + + Kizoom CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG CML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI-SX XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Common SITUATION Identity elements. + Standard +       +       + SIRI-SX Situation IDentifiers. +       + + + + + + + + + References to a SITUATION. + + + + + + + + + Reference to a SITUATION associated with the element. + + + + + Type for reference to a SITUATION. + + + + + + Reference to a SITUATION. Elements of SITUATION identfier are expressed as atomic elements. + + + + + + + + + Reference to a SITUATION associated with the element. + + + + + Type for identifier of a SITUATION. Includes the Participant identifier and version components of the identifier. + + + + + + Type for reference to a SITUATION. Includes the Particpant identifier and version components of the identifier. + + + + + + + + + Identifier of SITUATION within a Participant. Exclude versionr. + + + + + Type for a referenceUnique identifier of a SITUATION within participant. + + + + + + + + Type for SITUATION 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. Elements 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. + + + + + + + + + Elements 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. + + + + +       diff --git a/xsd/siri_model/siri_situationReasons.xsd b/xsd/siri_model/siri_situationReasons.xsd index cc392108..1c5a6c17 100644 --- a/xsd/siri_model/siri_situationReasons.xsd +++ b/xsd/siri_model/siri_situationReasons.xsd @@ -1,1370 +1,1370 @@ - - - - - - main schema - e-service developers - Add names - Europe - Drafted for version 1.0 Kizoom Incident Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk - - 2004-09-29 - - - 2004-10-01 - - - 2005-02-14 - - - 2007-05-14 - - - 2008-07-05 - - - - 2009-03-31 - - - - 2018-11-13 - - - - 2014-06-23 - - - - 2019-09-01 - - - -

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

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

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

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

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/standards/siri/schema/2.0/xsd/siri_model/}siri_situationServiceTypes.xsd - [ISO 639-2/B] ENG - CEN - - - - Kizoom 2000-2007, CEN 2009-2020 - - -
        -
      • Schema derived Derived from the Kizoom XTIS schema
        • -
      • Derived from the TPEG2 PTS schemas
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - Xml Schema for PT Incidents. Service subschema - Standard -       -       -       - - - - - Scope of incident - TPEG Pti27 ReportType - - - - - Values for TPEG Pti27 - ReportType - - - - - TPEG Pti27_0, unknown - - - - - TPEG Pti27_1, incident - - - - - TPEG Pti27_1_1, general - - - - - TPEG Pti27_1_2, operator - - - - - TPEG Pti27_1_3, network - - - - - TPEG Pti27_2, station terminal - - - - - TPEG Pti27_2_1, stoppoint - - - - - TPEG Pti27_2_2, connection link - - - - - TPEG Pti27_2_3, point - - - - - TPEG Pti27_3, route - - - - - TPEG Pti27_4, individual service - - - - - TPEG Pti27_255, undefined type - - - - - - - - Status of a SERVICE JOURNEY INTERCHANGE - TPEG Pti31 InterchangeStatus - - - - - Values for TPEG Pti31 - InterchangeStatus - - - - - TPEG Pti31_0, unknown - - - - - TPEG Pti31_1, connection - - - - - TPEG Pti31_2, replacement - - - - - TPEG Pti31_3, alternative - - - - - TPEG Pti31_4, connection not held - - - - - TPEG Pti31_5, connection held - - - - - TPEG Pti31_6, status of connection undecided - - - - - TPEG Pti31_255, undefined cross reference information - - - - - Interchange is planned but was updated as a result of changes in the QUAYs or arrival/departure times. Can be used if the status is a combination of the other values. +SIRI v2.1 - - - - - An important function of connection protection is the ability to hold back a distributor VEHICLE (i.e. prolonged waiting) to allow passengers to transfer from delayed feeders. -To achieve this a distributorWaitProlonged status shall be communicated back to the feeder VEHICLEs to inform the passengers about the new departure time of the distributor or even a willWait guarantee. +SIRI v2.1 - - - - - Used to provide the passengers with information about a new departure platform of the distributor VEHICLE if the distributor changes its planned stopping position. +SIRI v2.1 - - - - - Interchange is an addition to the plan. +SIRI v2.1 - - - - - Interchange is a cancellation of an interchange in the plan. +SIRI v2.1 - - - - - Loss of the inbound connection indicates the cancellation of the visit (of the FeederJourney) to the FeederArrivalStop, or a severely delayed arrival. This can lead to the distributor VEHICLE abandoning the connection. -Reasons for the loss of a feeder include (but are not limited to) the cancellation of the feeder VEHICLE, diversion/rerouting of the feeder VEHICLE, disruption of a line section or journey part of the feeder VEHICLE etc. +SIRI v2.1 - - - - - Indicates the loss of an outbound connection, i.e., is used to signal the cancellation of the onward connection to the passengers in the feeder VEHICLEs. +SIRI v2.1 - - - - - deprecated (SIRI 2.1) - use statusOfConnectionUndecided instead - - - - - - - - Ticket restrictions - TPEG Pti025 - - - - - Values for TPEG Pti025 - TicketRestrictionType - - - - - TPEG Pti25_0, unknown - - - - - TPEG Pti25_1, all ticket classes valid - - - - - TPEG Pti25_2, full fare only - - - - - TPEG Pti25_3, certain tickets only - - - - - TPEG Pti25_4, ticket with reservation - - - - - TPEG Pti25_5, special fare - - - - - TPEG Pti25_6, only tickets of specified operator - - - - - TPEG Pti25_7, no restrictions - - - - - TPEG Pti25_8, no off-peak tickets - - - - - TPEG Pti25_9, no weekend return tickets - - - - - TPEG Pti25_10, no reduced fare tickets - - - - - TPEG Pti25_255, unknown ticket restriction - - - - - - - - Booking Status - TPEG Pti024. - - - - - Values for Values for TPEG Pti024 - BookingStatus - - - - - TPEG Pti24_0, unknown - - - - - TPEG Pti24_1, available - - - - - TPEG Pti24_2, limited - - - - - TPEG Pti24_3, very limited - - - - - TPEG Pti24_4, full - - - - - TPEG Pti24_5, waiting list - - - - - TPEG Pti24_6, no booking required - - - - - TPEG Pti24_7, booking is required - - - - - TPEG Pti24_8, booking is optional - - - - - TPEG Pti24_255, undefined booking information - - - - - - - - STOP POINT type - TPEG Pts017, ServiceDeliveryPointType - - - - - Values for TPEG Pts017 - ServiceDeliveryPointType - - - - - TPEG Pts17_0, unknown - - - - - TPEG Pts17_1, platform number - - - - - TPEG Pts17_2, terminal gate - - - - - TPEG Pts17_3, ferry berth - - - - - TPEG Pts17_4, harbour pier - - - - - TPEG Pts17_5, unknown - - - - - TPEG Pts17_6, bus stop - - - - - TPEG Pts17_255, undefined service delivery point type - - - - - deprecated (SIRI 2.1) - use undefinedStopPointType - - - - - - - - Type for ROUTE POINT. - - - - - Values for ROUTE POINT type that correspond to TPEG Pts44: StopPlaceUsage (Pti15: deprecated since SIRI v2.1). - - - - - TPEG Pti15_0, Pts44_0, unknown - - - - - TPEG Pts44_1, origin - - - - - TPEG Pti15_2, Pts44_2, destination - - - - - TPEG Pts44_3, intermediate. - - - - - TPEG Pts44_4, leg board - - - - - TPEG Pts44_5, leg intermediate - - - - - TPEG Pts44_6, leg alight - - - - - TPEG Pts44_7, first route point - - - - - TPEG Pts44_8, last route point - - - - - TPEG Pts44_9, affected stop place - - - - - TPEG Pts44_10, presented stop place - - - - - TPEG Pts44_255, undefined stop place usage - - - - - TPEG Pti15_1, start point, deprecated (SIRI v2.1) and replaced by Pts44_1 value 'origin'. - - - - - TPEG Pti15_3, stop, deprecated (SIRI v2.1) - - - - - TPEG Pti15_4, via, deprecated (SIRI v2.1) - - - - - TPEG Pti15_5, not-stopping, deprecated (SIRI v2.1) - - - - - TPEG Pti15_6, temporary stop, deprecated (SIRI v2.1) - - - - - TPEG Pti15_7, temporarily not-stopping, deprecated (SIRI v2.1) - - - - - TPEG Pti15_8, exceptional stop, deprecated (SIRI v2.1) - - - - - TPEG Pti15_9, additional stop, deprecated (SIRI v2.1) - - - - - TPEG Pti15_10, request stop, deprecated (SIRI v2.1) - - - - - TPEG Pti15_11, front train destination, deprecated (SIRI v2.1) - - - - - TPEG Pti15_12, rear train destination, deprecated (SIRI v2.1) - - - - - TPEG Pti15_13, through service destination, deprecated (SIRI v2.1) - - - - - TPEG Pti15_14, not via, deprecated (SIRI v2.1) - - - - - TPEG Pti15_15, altered start point, deprecated (SIRI v2.1) - - - - - TPEG Pti15_16, altered destination, deprecated (SIRI v2.1) - - - - - TPEG Pti15_255, undefined route point, deprecated (SIRI v2.1) - - - - - - - - Timetable type - TPEG Pti033. - - - - - Values for TPEG Pti033 - TimetableType - - - - - TPEG Pti33_0, unknown - - - - - TPEG Pti33_1, winter - - - - - TPEG Pti33_2, spring - - - - - TPEG Pti33_3, summer - - - - - TPEG Pti33_4, autumn - - - - - TPEG Pti33_5, special - - - - - TPEG Pti33_6, emergency - - - - - TPEG Pti33_255, undefined timetable type - - - - -       + + + + + + main schema + e-service developers + Add names + Europe + Drafted for version 1.0 Kizoom Incident Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk + + 2004-09-29 + + + 2004-10-01 + + + 2007-05-14 + + + 2007-05-14 + + + + 2020-01-10 + + + +

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

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

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

      -

      This sub-schema describes the TargetedVehicleJourney used in the Stop Timetable Service.

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_targetedVehicleJourney.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI XML schema. Service Interface for Real-time Information. Subschema for Stop Timetable Service. - Standard -       -       - SIRI-ST TargetedVehicleJourney for Stop Timetable Service. -       - - - - - - Timetabled VEHICLE JOURNEY. - - - - - Type for a targeted VEHICLE JOURNEY. - - - - - - - - - - - - Elements for a targeted call. - - - - - Reference to a SCHEDULED 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. - - - - - -       + + + + + + 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 + + + + 2012-03-23 + + + +

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

      +

      This sub-schema describes the TargetedVehicleJourney used in the Stop Timetable Service.

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_targetedVehicleJourney.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG XML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI XML schema. Service Interface for Real-time Information. Subschema for Stop Timetable Service. + Standard +       +       + SIRI-ST TargetedVehicleJourney for Stop Timetable Service. +       + + + + + + Timetabled VEHICLE JOURNEY. + + + + + Type for a targeted VEHICLE JOURNEY. + + + + + + + + + + + + Elements for a targeted call. + + + + + Reference to a SCHEDULED 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. + + + + + +       diff --git a/xsd/siri_model/siri_time.xsd b/xsd/siri_model/siri_time.xsd index a79d427c..339f1c6f 100644 --- a/xsd/siri_model/siri_time.xsd +++ b/xsd/siri_model/siri_time.xsd @@ -1,356 +1,356 @@ - - - - - - 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 - - - - 2014-06-20 - - - - 2020-01-24 - - - -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_time.xsd - [ISO 639-2/B] ENG - CEN - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIG CML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of time types. - Standard -       -       -       - - - - - 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. - - - - - - - Type for a range of times. Both start and end time are required. - - - - - The (inclusive) start time. - - - - - The (inclusive) end time. - - - - - Precision with which to interpret the inclusive end time. Default is to the second. - - - - - - - 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 range of date times. Start time must be specified, end time is optional. - - - - - The (inclusive) start time stamp. - - - - - The (inclusive) end time stamp. - - - - - Precision with which to interpret the inclusive end time. Default is to the second. (Siri 2.0++) - - - - - - - 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 defined by end time status. - - - - - If end time not provided, whethhr to interpret range as long, term, short term or unknown length of situation. Default is unknown. (Siri 2.0++) - - - - - - - Allowed values for EndTime Precision - - - - - - - - - - - Allowed values for EndTime Status. - - - - - - - - - - - Day on which a SITUATION may apply - TPEG Pti34 DayType - - - - - Values for TPEG Pti34 - DayType - - - - - TPEG Pti34_0, unknown - - - - - TPEG Pti34_1, Monday - - - - - TPEG Pti34_2, Tuesday - - - - - TPEG Pti34_3, Wednesday - - - - - TPEG Pti34_4, Thursday - - - - - TPEG Pti34_5, Friday - - - - - TPEG Pti34_6, Saturday - - - - - TPEG Pti34_7, Sunday - - - - - TPEG Pti34_8, weekdays - - - - - TPEG Pti34_9, weekends - - - - - TPEG Pti34_10, holiday - - - - - TPEG Pti34_11, public holiday - - - - - TPEG Pti34_12, religious holiday - - - - - TPEG Pti34_13, federal holiday - - - - - TPEG Pti34_14, regional holiday - - - - - TPEG Pti34_15, national holiday - - - - - TPEG Pti34_16, Monday to Friday - - - - - TPEG Pti34_17, Monday to Saturday - - - - - TPEG Pti34_18, Sundays and public holidays - - - - - TPEG Pti34_19, school days - - - - - TPEG Pti34_20, every day - - - - - TPEG Pti34_255, undefined day type - - - - - - - Subset of TPEG Pti34 - DayType - - - - - - - - - - - - - - - - - - - Subset of TPEG Pti34 - DayType - - - - - - - - - - - - - - -       + + + + + + 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 + + + + 2014-06-20 + + + + 2020-01-24 + + + +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_time.xsd + [ISO 639-2/B] ENG + CEN + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG CML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of time types. + Standard +       +       +       + + + + + 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. + + + + + + + Type for a range of times. Both start and end time are required. + + + + + The (inclusive) start time. + + + + + The (inclusive) end time. + + + + + Precision with which to interpret the inclusive end time. Default is to the second. + + + + + + + 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 range of date times. Start time must be specified, end time is optional. + + + + + The (inclusive) start time stamp. + + + + + The (inclusive) end time stamp. + + + + + Precision with which to interpret the inclusive end time. Default is to the second. (Siri 2.0++) + + + + + + + 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 defined by end time status. + + + + + If end time not provided, whethhr to interpret range as long, term, short term or unknown length of situation. Default is unknown. (Siri 2.0++) + + + + + + + Allowed values for EndTime Precision + + + + + + + + + + + Allowed values for EndTime Status. + + + + + + + + + + + Day on which a SITUATION may apply - TPEG Pti34 DayType + + + + + Values for TPEG Pti34 - DayType + + + + + TPEG Pti34_0, unknown + + + + + TPEG Pti34_1, Monday + + + + + TPEG Pti34_2, Tuesday + + + + + TPEG Pti34_3, Wednesday + + + + + TPEG Pti34_4, Thursday + + + + + TPEG Pti34_5, Friday + + + + + TPEG Pti34_6, Saturday + + + + + TPEG Pti34_7, Sunday + + + + + TPEG Pti34_8, weekdays + + + + + TPEG Pti34_9, weekends + + + + + TPEG Pti34_10, holiday + + + + + TPEG Pti34_11, public holiday + + + + + TPEG Pti34_12, religious holiday + + + + + TPEG Pti34_13, federal holiday + + + + + TPEG Pti34_14, regional holiday + + + + + TPEG Pti34_15, national holiday + + + + + TPEG Pti34_16, Monday to Friday + + + + + TPEG Pti34_17, Monday to Saturday + + + + + TPEG Pti34_18, Sundays and public holidays + + + + + TPEG Pti34_19, school days + + + + + TPEG Pti34_20, every day + + + + + TPEG Pti34_255, undefined day type + + + + + + + Subset of TPEG Pti34 - DayType + + + + + + + + + + + + + + + + + + + Subset of TPEG Pti34 - DayType + + + + + + + + + + + + + + +       diff --git a/xsd/siri_model_discovery/siri_connectionLink.xsd b/xsd/siri_model_discovery/siri_connectionLink.xsd index 849a23e9..74e01670 100644 --- a/xsd/siri_model_discovery/siri_connectionLink.xsd +++ b/xsd/siri_model_discovery/siri_connectionLink.xsd @@ -1,115 +1,115 @@ - - - - - - main schema - e-service developers - CEN TC278 WG3 SG7 Team - Europe - Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2013-03-07 - - -

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

      -

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

      • Service Feature discovery
      • TYPE OF PRODUCT CATEGORY Discovery
      -

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/}siri_discovery.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference.xsd - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Discovery services Derived from the NaPTAN standard .
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI_DS XML schema. Service Interface for Real-time Information. Discovery subschema. - Standard -       -       - SIRI subschema with view of SCHEDULED CONNECTION LINKS for use in Connection Link Discovery service -       - - - - - - - SCHEDULED CONNECTION LINK definition. - - - - - View of a SCHEDULED CONNECTION LINK description. - - - - - Identifer of the connection link. DetailLevel=minimum - - - - - Identifer of the feeder's stop. DetailLevel=normal - - - - - Identifer of the distributor's stop. DetailLevel=normal - - - - - Whether real-time data is available for the connection link. Default is 'true'. DetailLevel=minimum - - - - - Name of SCHEDULED CONNECTION LINK. DetailLevel=minimum - - - - - Name of the feeder's stop. DetailLevel=full - - - - - Name of the distributor's stop. DetailLevel=full - - - - - Web page associated with connection link. DetailLevel=full - - - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2013-03-07 + + +

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

      +

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

      • Service Feature discovery
      • TYPE OF PRODUCT CATEGORY Discovery
      +

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}siri_discovery.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Discovery services Derived from the NaPTAN standard .
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI_DS XML schema. Service Interface for Real-time Information. Discovery subschema. + Standard +       +       + SIRI subschema with view of SCHEDULED CONNECTION LINKS for use in Connection Link Discovery service +       + + + + + + + SCHEDULED CONNECTION LINK definition. + + + + + View of a SCHEDULED CONNECTION LINK description. + + + + + Identifer of the connection link. DetailLevel=minimum + + + + + Identifer of the feeder's stop. DetailLevel=normal + + + + + Identifer of the distributor's stop. DetailLevel=normal + + + + + Whether real-time data is available for the connection link. Default is 'true'. DetailLevel=minimum + + + + + Name of SCHEDULED CONNECTION LINK. DetailLevel=minimum + + + + + Name of the feeder's stop. DetailLevel=full + + + + + Name of the distributor's stop. DetailLevel=full + + + + + Web page associated with connection link. DetailLevel=full + + + + + +       diff --git a/xsd/siri_model_discovery/siri_feature.xsd b/xsd/siri_model_discovery/siri_feature.xsd index 6ca94648..c3c22b71 100644 --- a/xsd/siri_model_discovery/siri_feature.xsd +++ b/xsd/siri_model_discovery/siri_feature.xsd @@ -1,158 +1,158 @@ - - - - - - main schema - e-service developers - CEN TC278 WG3 SG7 Team - Europe - Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2012-03-23 - - - 2008-11-17 - - - - 2012-03-23 - - - -

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

      -

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

      • SERVICE FEATURE discovery
      • TYPE OF PRODUCT CATEGORY Discovery
      -

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/}siri_discovery.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference.xsd - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Discovery services Derived from the NaPTAN standard .
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI_DS XML schema. Service Interface for Real-time Information. Discovery subschema. - Standard -       -       - SIRI subschema with view of classifiers for use in Discovery service -       - - - - - - - - - Category for classification of a journey as a Product - - - - - Type for TYPE OF PRODUCT CATEGORY description. - - - - - Identifier of TYPE OF PRODUCT CATEGORY classification. SIRI provides a recommended set of values covering most usages, intended to be TPEG compatible. See the SIRI facilities packaged. - - - - - Name of classification (Unbounded since SIRI 2.0) - - - - - Icon used to represent TYPE OF PRODUCT CATEGORY. - - - - - - - - Service Feature description. - - - - - Type for Service Feature description. - - - - - Identifier of classification. SIRI provides a recommended set of values covering most usages, intended to be TPEG compatible. See the SIRI facilities packaged. - - - - - Name of classification. (Unbounded since SIRI 2.0) - - - - - Icon associated with feature. - - - - - - - - Vehicle Feature description. - - - - - Type for description of feature of VEHICLE. - - - - - Identifier of feature of VEHICLE. SIRI provides a recommended set of values covering most usages, intended to be TPEG compatible. See the SIRI facilities packaged. - - - - - Name of feature of VEHICLE. (Unbounded since SIRI 2.0) - - - - - Icon used to represent feature of VEHICLE. - - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2012-03-23 + + + 2008-11-17 + + + + 2012-03-23 + + + +

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

      +

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

      • SERVICE FEATURE discovery
      • TYPE OF PRODUCT CATEGORY Discovery
      +

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}siri_discovery.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Discovery services Derived from the NaPTAN standard .
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI_DS XML schema. Service Interface for Real-time Information. Discovery subschema. + Standard +       +       + SIRI subschema with view of classifiers for use in Discovery service +       + + + + + + + + + Category for classification of a journey as a Product + + + + + Type for TYPE OF PRODUCT CATEGORY description. + + + + + Identifier of TYPE OF PRODUCT CATEGORY classification. SIRI provides a recommended set of values covering most usages, intended to be TPEG compatible. See the SIRI facilities packaged. + + + + + Name of classification (Unbounded since SIRI 2.0) + + + + + Icon used to represent TYPE OF PRODUCT CATEGORY. + + + + + + + + Service Feature description. + + + + + Type for Service Feature description. + + + + + Identifier of classification. SIRI provides a recommended set of values covering most usages, intended to be TPEG compatible. See the SIRI facilities packaged. + + + + + Name of classification. (Unbounded since SIRI 2.0) + + + + + Icon associated with feature. + + + + + + + + Vehicle Feature description. + + + + + Type for description of feature of VEHICLE. + + + + + Identifier of feature of VEHICLE. SIRI provides a recommended set of values covering most usages, intended to be TPEG compatible. See the SIRI facilities packaged. + + + + + Name of feature of VEHICLE. (Unbounded since SIRI 2.0) + + + + + Icon used to represent feature of VEHICLE. + + + + +       diff --git a/xsd/siri_model_discovery/siri_infoChannel.xsd b/xsd/siri_model_discovery/siri_infoChannel.xsd index 7795d140..99c69b0e 100644 --- a/xsd/siri_model_discovery/siri_infoChannel.xsd +++ b/xsd/siri_model_discovery/siri_infoChannel.xsd @@ -1,99 +1,99 @@ - - - - - - main schema - e-service developers - CEN TC278 WG3 SG7 Team - Europe - Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2012-03-23 - - - 2008-11-17 - - - - 2012-03-23 - - - -

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

      -

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

      • Service Feature discovery
      • TYPE OF PRODUCT CATEGORY Discovery
      -

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/}siri_discovery.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference.xsd - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Discovery services Derived from the NaPTAN standard .
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI_DS XML schema. Service Interface for Real-time Information. Discovery subschema. - Standard -       -       - SIRI subschema with view of Info channel for use in Discovery service -       - - - - - - Info Channel supported by Producer service. - - - - - Type for Info Channels description. - - - - - Identifier of classification. - - - - - Name of Info Channel. - - - - - Icon associated with Info Channel. - - - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2012-03-23 + + + 2008-11-17 + + + + 2012-03-23 + + + +

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

      +

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

      • Service Feature discovery
      • TYPE OF PRODUCT CATEGORY Discovery
      +

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}siri_discovery.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Discovery services Derived from the NaPTAN standard .
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI_DS XML schema. Service Interface for Real-time Information. Discovery subschema. + Standard +       +       + SIRI subschema with view of Info channel for use in Discovery service +       + + + + + + Info Channel supported by Producer service. + + + + + Type for Info Channels description. + + + + + Identifier of classification. + + + + + Name of Info Channel. + + + + + Icon associated with Info Channel. + + + + + +       diff --git a/xsd/siri_model_discovery/siri_line.xsd b/xsd/siri_model_discovery/siri_line.xsd index 2d6a7417..54c132f7 100644 --- a/xsd/siri_model_discovery/siri_line.xsd +++ b/xsd/siri_model_discovery/siri_line.xsd @@ -1,241 +1,241 @@ - - - - - - main schema - e-service developers - CEN TC278 WG3 SG7 Team - Europe - Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2012-03-23 - - - 2008-11-17 - - - - 2012-03-23 - - - - 2012-05-10 - - - - 2012-06-12 - - - -

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

      -

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

      • Service Feature discovery
      • TYPE OF PRODUCT CATEGORY Discovery
      -

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/}siri_discovery.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference.xsd - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Discovery services Derived from the NaPTAN standard .
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI_DS XML schema. Service Interface for Real-time Information. Stop Discovery subschema. - Standard -       -       - SIRI subschema with view of LINE for use in Discovery service -       - - - - - - - - - - Information about LINEs covered by server. - - - - - Summary information about a LINE type. - - - - - Identifier of LINE. - - - - - Name of LINE. (Unbounded since SIRI 2.0) - - - - - Whether the LINE has real-time info. Default is 'true'. - - - - - DESTINATIONs to which the LINE runs. Detail level is 'normal' - - - - - - - - - - DIRECTIONs and Stops for the LINE. 'normal' - - - - - - Directions of Route - - - - - - - - - - - - Summary information about a Direction of a Line - - - - - - - JourneyPatterns in Direction of route (+SIRI 2.0) - - - - - - JourneyPattern. (+SIRI 2.0) - - - - - - - Name Of Journety Pattern (SIRI 2.0) - - - - - Ordered collection of STOP POINTs the LINE and direction . Detail level is 'stops'. +SIRI v2.0 - - - - - - Stop within Route of LINE. Detail level is 'stop' +SIRI v2.0 - - - - - - - - - - - - - - - - - - - Summary information about a stop within line - - - - - - - Order of STOP POINT in route +SIRI v2.0 - - - - - Plot of points from this stop to next Stop. Detail level is 'full'. +SIRI v2.0 - - - - - GIs projection of Link to the next provided StopPoint. NB Line here means Geometry Polyline, not Transmodel Transport Line. - - - - - - - - - - - Description of a DESTINATION. - - - - - Type for DESTINATION and place name. - - - - - - Name of destination TOPOGRAPHIC PLACE. (Unbounded since SIRI 2.0) - - - - - Direction in which destination lies. relatoive to currernt stop SIRI 2.0 - - - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2012-03-23 + + + 2008-11-17 + + + + 2012-03-23 + + + + 2012-05-10 + + + + 2012-06-12 + + + +

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

      +

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

      • Service Feature discovery
      • TYPE OF PRODUCT CATEGORY Discovery
      +

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

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

      -

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

      • Service Feature discovery
      • TYPE OF PRODUCT CATEGORY Discovery
      -

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/}siri_discovery.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference.xsd - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Discovery services Derived from the NaPTAN standard .
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI_DS XML schema. Service Interface for Real-time Information. Discovery subschema. - Standard -       -       - SIRI subschema with view of SCHEDUELD STOP POINT for use in Stop Discovery service -       - - - - - - - - SCHEDULED STOP POINT definition. - - - - - View of a SCHEDULED STOP POINT description. - - - - - Identifer of the stop. - - - - - - Whether real-time data is available for the stop. Default is 'true'. Detail level is 'normal'. - - - - - Name of SCHEDULED STOP POINT. Detail level is 'normal'. (Unbounded since SIRI 2.0) - - - - - Identifer of the sSTOP AREA to which SCHEDULED STOP POINT belongs. +SIRI.v2.0 - - - - - Service features of stop. Detail level is 'full' - - - - - - Description of Service features of stop. - - - - - - - - - LINEs that use stop. Detail level is 'full' - - - - - - Reference to a LINE that calls at stop. - - - - - Reference to a LINE that calls at stop. and its direction +SIRI V2.0 - - - - - - - - Coordinates to use to show stop as a poitn on map. Detail level is 'normal'.+SIRI.v2.0 - - - - - Web page associated with Stop. Detail level is 'full'+SIRI.v2.0 - - - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2012-03-23 + + + 2008-11-17 + + + + 2012-03-23 + + + + 2012-06-12 + + + +

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

      +

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

      • Service Feature discovery
      • TYPE OF PRODUCT CATEGORY Discovery
      +

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}siri_discovery.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Discovery services Derived from the NaPTAN standard .
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI_DS XML schema. Service Interface for Real-time Information. Discovery subschema. + Standard +       +       + SIRI subschema with view of SCHEDUELD STOP POINT for use in Stop Discovery service +       + + + + + + + + SCHEDULED STOP POINT definition. + + + + + View of a SCHEDULED STOP POINT description. + + + + + Identifer of the stop. + + + + + + Whether real-time data is available for the stop. Default is 'true'. Detail level is 'normal'. + + + + + Name of SCHEDULED STOP POINT. Detail level is 'normal'. (Unbounded since SIRI 2.0) + + + + + Identifer of the sSTOP AREA to which SCHEDULED STOP POINT belongs. +SIRI.v2.0 + + + + + Service features of stop. Detail level is 'full' + + + + + + Description of Service features of stop. + + + + + + + + + LINEs that use stop. Detail level is 'full' + + + + + + Reference to a LINE that calls at stop. + + + + + Reference to a LINE that calls at stop. and its direction +SIRI V2.0 + + + + + + + + Coordinates to use to show stop as a poitn on map. Detail level is 'normal'.+SIRI.v2.0 + + + + + Web page associated with Stop. Detail level is 'full'+SIRI.v2.0 + + + + + +       diff --git a/xsd/siri_productionTimetable_service.xsd b/xsd/siri_productionTimetable_service.xsd index 73f1652a..5fa32773 100644 --- a/xsd/siri_productionTimetable_service.xsd +++ b/xsd/siri_productionTimetable_service.xsd @@ -1,514 +1,514 @@ - - - - - - main schema - e-service developers - CEN TC278 WG3 SG7 Team - Werner Kohl MDV - Europe - Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2003-02-10 - - - 2004-10-31 - - - 2005-02-14 - - - 2005-02-20 - - - 2005-05-11 - - - 2007-04-17 - - - - 2008-03-26 - - - - 2008-11-17 - - - - 2011-04-18 - - - - 2011-01-19 - - - - 2012-03-23 - - - -

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

      -

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

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

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

      +

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

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

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

      -

      This sub-schema describes the Situation Exchange Service.

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/}siri_SituationExchange_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_situation.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions.xsd - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      • categories from TPEG
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI-SX XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Situation Exchange Service Subschema - Standard -       -       - SIRI-SX Situation Exchange Service. -       - - - - - - - - - - - - - - - - - Convenience artifact to pick out main elements of the Situation Exchange Service. - - - - - - - - - - - - - - - - Request for information about Facilities status. - - - - - Type for Functional Service Request for Situation Exchange Service. - - - - - - - - - - - Version number of request. Fixed - - - - - - - - - Parameters that specify the content to be returned. Logically ANDed with other values. - - - - - Parameters to control time for which subscription applies. - - - - - Parameters to filter Situation Exchange Service requests, based on the time. Logically ANDed with other values. - - - - - - - - - - - - Parameters to filter Situation Exchange Service requests, based on the SITUATION Road. Logically ANDed with other values. - - - - - - - - - - Parameters to filter Situation Exchange Service requests, based on specific needs . - - - - - - - Parameters to filter Situation Exchange Service requests, based on the SITUATION Status. Logically ANDed with other values. - - - - - Forward duration for which SITUATIONs should be included, that is, only SITUATIONs that start before the end of this window time will be included. - - - - - Start time for selecting SITUATIONs to be sent. Only SITUATIONs or updates created after this time will be sent. This enables a restart without resending everything. - - - - - - - Parameters to filter Situation Exchange Service requests, based on the SITUATION Status. Logically ANDed with other values. - - - - - Temporal scope of Situations be included in response. The Situations must be valid within the specified period of time. (+SIRI 2.0) - - - - - Only incidents that are currently within their publication window shouldbe included. Otherwose all incidents will be included. Default is false - - - - - - - Parameters to filter Situation Exchange Service requests, based on the SITUATION Status. Logically ANDed with other values. - - - - - Whether incident has been verified or not If not specified return all. - - - - - Workflow Progress Status. One of a specified set of overall processing states assigned to SITUATION. For example, 'Draft' for not yet published; 'Published' for live SITUATIONs; 'Closed' indicates a completed SITUATION. If not specified return open, published closing and closed. l. - - - - - Whether SITUATION is real or a test. If not specified return all. - - - - - - - Parameters to filter Situation Exchange Service requests, based on the SITUATION Network. Logically ANDed with other values. - - - - - Referance to an OPERATOR. If unspecified, all OPERATOR.s. - - - - - OPERATIONAL UNIT responsible for managing services. - - - - - Reference to a NETWORK. - - - - - - Filter the results to include only the given line. - - - - - Filter the results to include only situations along the given LINEs. - - - - - - Filter the results to include only the given line. and direction - - - - - - - - - - - - - - Parameters to filter Situation Exchange Service requests, based on the STOP PLACEs affected SITUATIONs. Logically ANDed with other values. - - - - - Reference to a STOP PLACE. - - - - - Reference to part of a STOP PLACE. (+SIRI 2.0) - - - - - - - Parameters to filter Situation Exchange Service requests, based on the VEHICLE JOURNEYs affected by the SITUATION. Logically ANDed with other values. - - - - - Use of simple reference is deprecated - - - - Refercence to a VEHICLE JOURNEY framed by the day. SIRI 2.0 - - - - - - - - - - - Parameters to filter Situation Exchange Service requests, based on the SITUATION Classifiers. Logically ANDed with other values. - - - - - Severity filter value to apply: only SITUATIONs with a severity greater than or equal to the specified value will be returned. See TPEG severities. Default is '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 Service requests, based on the SITUATION Place. Logically ANDed with other values. - - - - - Reference to a COUNTRY where incident takes place If specified only incidents that affect this place country will be returned. - - - - - Reference to a TOPOGRAPHIC PLACE. Only incidents which are deemed to affect this place will be returned. - - - - - Bounding box of an arbitrary area. Only incidents geocoded as falling within area will be included. - - - - - - - Type for Parameters to filter Situation Exchange Service requests, based on the SITUATION Road, Logically ANDed with other values. - - - - - Identifier or number of the road on which the reference POINT is located. - - - - - The DIRECTION at the reference point in terms of general destination DIRECTION. If absent both. - - - - - Road reference POINT identifier, unique on the specified road. - - - - - - - Parameters that affect the request processing. - - - - - Preferred languages in which to return text values. - - - - - - The maximum number of SITUATION elements to return in a given delivery. The most recent n Events within the look ahead window are included. - - - - - - - - Request for a subscription to the Situation Exchange Service. - - - - - Parameters that affect the subscription publishing and notification processing. - - - - - Whether the producer will return the complete set of current data, or only provide updates to this data, i.e. additions, modifications and deletions. -If false or omitted, each subscription response will contain the full information as specified in this request. - - - - - - - Type for Subscription Request for Situation Exchange Service. - - - - - - - - - - - - - - - - Delivery for Situation Exchange Service. - - - - - Delivery of Situation Exchange Service included as supplement to main functional service delivery. - - - - - Payload part of Situation Exchange Service delivery. - - - - - Default context for common properties of SITUATIONs, Values specified apply to all SITUATIONs unless overridden. Can be used optionally to reduce file bulk. - - - - - SITUATIONs in Delivery. - - - - - - Description of a SITUATION. - - - - - - - - - - - Type for Delivery for Situation Exchange Service. Provides information about one or more vehicles; each has its own VEHICLE activity element. - - - - - - - Payload part of Situation Exchange Service delivery. - - - - - - - Version number of response. Fixed - - - - - - - - - - Common parameters for all SITUATIONs. - - - - - Reference to a Country of a Participant who published SITUATION. - - - - - Reference to a system publishing SITUATIONs. If SITUATIONs from other participants are included in delivery, then ParticipantRef of immediate publisher must be given here. - - - - - Refrence to a TOPOGRAPHIC PLACE (locality). Also Derivable from an individual StopRef. - - - - - Name of locality in which SITUATIONs apply. Derivable from LocalityRef. (Unbounded since SIRI 2.0) - - - - - Default language of text. - - - - - Default context for common properties of Public Transport SITUATIONs. - - - - - Actions that apply to all SITUATIONs unless overridden. - - - - - - - - Type for shared context. - - - - - Default OPERATOR for SITUATIONs. - - - - - Default Network of affected LINEs. These values apply to all SITUATIONs unless overridden on individual instances. - - - - - - - - - Type for Deliveries for Situation Exchange Service. Used in WSDL. - - - - - Delivery for Vehicle Activity Service. - - - - - - - - - Request for information about Situation Exchange Service Capabilities. Answered with a VehicleMontoringCapabilitiesResponse. - - - - - - Capabilities for Situation Exchange Service. Answers a VehicleMontoringCapabilitiesRequest. - - - - - Type for Delivery for Situation Exchange Service. - - - - - - - - - - - Version number of response. Fixed - - - - - - - - - Capabilities of Situation Exchange Service. Answers a SituationExchangeCapabilitiesRequest. - - - - - Type for SItuation Exchange Service Capabilities. - - - - - - - Filtering Capabilities. - - - - - - Default preview interval. Default is 60 minutes. - - - - - - Whether results can be filtered by location. Fixed as 'true'. - - - - - - Whether results can be filtered by MODE. Default is true.. (+SIRI v2.0) - - - - - Whether results can be filtered by NETWORKs. Default is 'true'. (+SIRI v2.0) - - - - - - - Whether results can be filtered by STOP PLACE identifvier. Default is 'false'. (+SIRI v2.0) - - - - - - - - Whether results can be filtered by Specific Needs. Default is 'true'. - - - - - Whether results can be filtered by Keywords. Default is 'false' - - - - - - - - Request Policy capabilities. - - - - - - - - - - - - - - Subscription Policy capabilities. - - - - - Optional Access control capabilities. - - - - - - - - - - - - - - - Optional Response capabilities. - - - - - - - - - - - - - Elements for volume control. - - - - - Whether a maximum number ofSITUATIONS to include can be specified. Default is 'false'. - - - - - - - - Participant's permissions to use the service. - - - - - - - - - - - - - - Type for Situation Exchange Service Permissions. - - - - - - - - - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + Drafted for version 1.1 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + + 2008-01-22 + + + 2008-01-22 + + + 2009-04-17 + + + + 2008-01-17 + + + + 2008-07-05 + + + + 2008-10-01 + + + + 2008-11-17 + + + + 2012-03-23 + + + + 2013-10-09 + + + + 2014-06-20 + + + + 2018-11-13 + + + +

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

      +

      This sub-schema describes the Situation Exchange Service.

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

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

      -

      This sub-schema describes the Stop Monitoring Service.

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

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

      +

      This sub-schema describes the Stop Monitoring Service.

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

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

      -

      This sub-schema describes the Stop Timetable Service.

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/}siri_stopTmetable_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions.xsd - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI XML schema. Service Interface for Real-time Information. Subschema for Stop Timetable Service. - Standard -       -       - SIRI-ST Stop Timetable Service. -       - - - - - - - Convenience artifact to pick out main elements of the Stop Timetable Service. - - - - - - - - - - - - - - Request for information about Stop Visits, i.e. arrival and departure at a stop. - - - - - - - Type for Functional Service Request for Stop Timetables. - - - - - - - - - - - Version number of request. Fixed - - - - - - - - - Parameters that specify the content to be returned. - - - - - Earliest and latest departure time. If absent, default to the data horizon of the service. - - - - - The stop monitoring point about which data is requested. May be a STOP POINT, timing point or other display point. - - - - - Filter the results to include only data for journeys for the given LINE. - - - - - Filter the results to include only data for journeys running in a specific relative DIRECTION, for example, "inbound" or "outbound". - - - - - - - Parameters that affect the request processing. Mostly act to reduce the number of stops returned. - - - - - Preferred languages in which to return text values. - - - - - - - - - Request for a subscription to Stop TimetablesService. - - - - - Parameters that affect the subscription publishing and notification processing. - - - - - Whether the producer should return the complete set of current data, or only provide updates to the last data returned, i.e. additions, modifications and deletions. -If false each subscription response will contain the full information as specified in this request. - - - - - The amount of change to the arrival or departure time that can happen before an update is sent (i.e. if ChangeBeforeUpdate is set to 2 minutes, the subscriber will not be told that a bus is 30 seconds delayed - an update will only be sent when the bus is at least 2 minutes delayed). Default is zero - all changes will be sent regardless. - - - - - - - Subscription Request for Stop Timetables. - - - - - - - - - - - - - - - - Delivery for Stop Timetable Service. - - - - - Data type Delivery for Stop Timetable Service. - - - - - - - - - - Version number of response. Fixed - - - - - - - - - Payload part of Stop Timetable delivery. - - - - - A visit to a stop by a VEHICLE as an arrival and /or departure, as timetabled in the production timetable. - - - - - A cancellation of a previously issued TimetabledStopVisit. - - - - - - - - Type for Timetabled Visit of a VEHICLE to a stop. May provide information about the arrival, the departure or both. - - - - - - - Reference to a stop monitoring point / LOGICAL DISPLAY to which Stop Visit applies. - - - - - - - - - - - Type for Cancellation of Timetabled Visit of a VEHICLE to a stop. May provide information about the arrival, the departure or both. - - - - - - - Reference to a stop monitoring point to which Stop Visit applies. - - - - - - - - Reason for cancellation. (Unbounded since SIRI 2.0) - - - - - - - - - - - - Type for stop timetable deliveries. Used in WSDL. - - - - - - - - - - - Request for information about Stop Timetable Service Capabilities Answered with a StopTimetableCapabilitiesResponse. - - - - - - Delivery for Stop Timetable Service. Answers a StopTimetableCapabilitiesRequest. - - - - - Type for Delivery for Stop Timetable Service. - - - - - - - - - - - Version number of response. Fixed - - - - - - - - - Capabilities of Stop Timetable Service. - - - - - Type for Capabilities of Stop Timetable Service. - - - - - - - Available Filtering Capabilities. - - - - - - - - - - - - Available request policy options. - - - - - Access control that can be used. - - - - - - - - - - - - - - - - - - - - - Type for Monitoring Service Capability Request Policy. - - - - - - - Whether results can return references for stops. Default is 'true'. - - - - - Whether results can return names for stop. - - - - - - - - - Participant's permissions to use the service. - - - - - - - - Permission for a single participant or all participants to use an aspect of the service. - - - - - - - - - - - - Type for Monitoring Service Permission. - - - - - - - - - The monitoring points that the participant may access. - - - - - - - Participant's permission for this Monitoring Point (LOGICAL DISPLAY) - - - - - - - - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2004-09-29 + + + 2004-10-01 + + + 2005-02-14 + + + 2005-02-20 + + + 2005-05-11 + + 2005-12-12 + 2005 12 07 Correct Spelling of StopMonitorPermissionTag + + 2007-04-17 + Name Space changes + + 2007-03-26 + Drop separate flatten structure on response for stopVisit + + 2008-11-17 + Revise to support substitution groups + + 2012-03-23 + +SIRI v2.0 + Improve modualirisatuioin + Factor out permissions to commomn files + factor out targeted journey, + create separate structure for StopTimetablePermissionStructure + create separate structure for StopTimetableCapabilityRequestPolicyStructure + + +

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

      +

      This sub-schema describes the Stop Timetable Service.

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}siri_stopTmetable_service.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG XML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI XML schema. Service Interface for Real-time Information. Subschema for Stop Timetable Service. + Standard +       +       + SIRI-ST Stop Timetable Service. +       + + + + + + + Convenience artifact to pick out main elements of the Stop Timetable Service. + + + + + + + + + + + + + + Request for information about Stop Visits, i.e. arrival and departure at a stop. + + + + + + + Type for Functional Service Request for Stop Timetables. + + + + + + + + + + + Version number of request. Fixed + + + + + + + + + Parameters that specify the content to be returned. + + + + + Earliest and latest departure time. If absent, default to the data horizon of the service. + + + + + The stop monitoring point about which data is requested. May be a STOP POINT, timing point or other display point. + + + + + Filter the results to include only data for journeys for the given LINE. + + + + + Filter the results to include only data for journeys running in a specific relative DIRECTION, for example, "inbound" or "outbound". + + + + + + + Parameters that affect the request processing. Mostly act to reduce the number of stops returned. + + + + + Preferred languages in which to return text values. + + + + + + + + + Request for a subscription to Stop TimetablesService. + + + + + Parameters that affect the subscription publishing and notification processing. + + + + + Whether the producer should return the complete set of current data, or only provide updates to the last data returned, i.e. additions, modifications and deletions. +If false each subscription response will contain the full information as specified in this request. + + + + + The amount of change to the arrival or departure time that can happen before an update is sent (i.e. if ChangeBeforeUpdate is set to 2 minutes, the subscriber will not be told that a bus is 30 seconds delayed - an update will only be sent when the bus is at least 2 minutes delayed). Default is zero - all changes will be sent regardless. + + + + + + + Subscription Request for Stop Timetables. + + + + + + + + + + + + + + + + Delivery for Stop Timetable Service. + + + + + Data type Delivery for Stop Timetable Service. + + + + + + + + + + Version number of response. Fixed + + + + + + + + + Payload part of Stop Timetable delivery. + + + + + A visit to a stop by a VEHICLE as an arrival and /or departure, as timetabled in the production timetable. + + + + + A cancellation of a previously issued TimetabledStopVisit. + + + + + + + + Type for Timetabled Visit of a VEHICLE to a stop. May provide information about the arrival, the departure or both. + + + + + + + Reference to a stop monitoring point / LOGICAL DISPLAY to which Stop Visit applies. + + + + + + + + + + + Type for Cancellation of Timetabled Visit of a VEHICLE to a stop. May provide information about the arrival, the departure or both. + + + + + + + Reference to a stop monitoring point to which Stop Visit applies. + + + + + + + + Reason for cancellation. (Unbounded since SIRI 2.0) + + + + + + + + + + + + Type for stop timetable deliveries. Used in WSDL. + + + + + + + + + + + Request for information about Stop Timetable Service Capabilities Answered with a StopTimetableCapabilitiesResponse. + + + + + + Delivery for Stop Timetable Service. Answers a StopTimetableCapabilitiesRequest. + + + + + Type for Delivery for Stop Timetable Service. + + + + + + + + + + + Version number of response. Fixed + + + + + + + + + Capabilities of Stop Timetable Service. + + + + + Type for Capabilities of Stop Timetable Service. + + + + + + + Available Filtering Capabilities. + + + + + + + + + + + + Available request policy options. + + + + + Access control that can be used. + + + + + + + + + + + + + + + + + + + + + Type for Monitoring Service Capability Request Policy. + + + + + + + Whether results can return references for stops. Default is 'true'. + + + + + Whether results can return names for stop. + + + + + + + + + Participant's permissions to use the service. + + + + + + + + Permission for a single participant or all participants to use an aspect of the service. + + + + + + + + + + + + Type for Monitoring Service Permission. + + + + + + + + + The monitoring points that the participant may access. + + + + + + + Participant's permission for this Monitoring Point (LOGICAL DISPLAY) + + + + + + + + + + +       diff --git a/xsd/siri_utility/siri_all_utility.xsd b/xsd/siri_utility/siri_all_utility.xsd index 6160a385..82a84bd0 100644 --- a/xsd/siri_utility/siri_all_utility.xsd +++ b/xsd/siri_utility/siri_all_utility.xsd @@ -1,14 +1,14 @@ - - - - - - - - - - - + + + + + + + + + + + diff --git a/xsd/siri_utility/siri_location.xsd b/xsd/siri_utility/siri_location.xsd index d4251a7f..bc7d6a2f 100644 --- a/xsd/siri_utility/siri_location.xsd +++ b/xsd/siri_utility/siri_location.xsd @@ -1,270 +1,270 @@ - - - - - - main schema - e-service developers - CEN TC278 WG3 SG9 Team. - Europe - First drafted for version 1.0 CEN TC278 WG3 SG9 Editor Nicholas Knowles. mailto:schemer@siri.org.uk - - 2004-09-29 - - - 2004-10-01 - - - 2005-02-14 - - - 2005-05-11 - - - 2005-05-04 - - - 2007-03-29 - - - 2012-03-23 - - - - 2012-05-10 - - - -

      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/schema/2.0/xsd/siri_utility/}siri_location.xsd - [ISO 639-2/B] ENG - CEN - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG9. - - SIRI XML schema. Geo spatial location subschema - Standard -       -       - SIRI Framewrok Location Types. -       - - - - - - - - Longitude from Greenwich. - - - - - - - - - Latitude from equator. - - - - - - - - - Altitude metres from sea level. - - - - - - - - - WGS84 Coordinates. - - - - - Longitude from Greenwich Meridian. -180 (West) to +180 (East). Decimal degrees, e.g. 2.356 - - - - - Latitude from equator. -90 (South) to +90 (North). Decimal degrees, e.g. 56.356 - - - - - Altitude metres from sea level. - - - - - - - Type for GM Coordinates. - - - - - - - - Type for coordinate reference system. - - - - - - GML Spatial coordinate reference system. - - - - - - Type for geospatial Position of a point. May be expressed in concrete WGS 84 Coordinates or any gml compatible point coordinates format. - - - - - - - - - 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. - - - - - - Defines a bounding box using two corner points. GML terminology. +SIRI v2.0 - - - - - Upper Left corner as a geospatial point. - - - - - Lower right corner as a geospatial point. - - - - - - - Defines a line shape +SIRI v2.0 - - - - - A geospatial point. +SIRI v2.0 - - - - - - - Type for a circular area centered around a point that may be expressed in concrete WGS 84 Coordinates or any gml compatible point coordinates format. +SIRI v2.1 - - - - - - - Radius around the center point in meters. - - - - - - - - - Bounding box, circular area or gml:polyon of the area where stops of a flexible service are called. +SIRI v2.1 -A flexible area is used in cases where a pre-booked service allows pick-up/drop-off anywhere in a designated area and provides a possible interchange to a higher-frequency service. - - - - - Flexible area specified as a rectangular bounding box. - - - - - Flexible area specified as a circular area (center coordinates and radius). - - - - - Flexible area specified as a gml:Polygon that consists of an interior and exterior linear ring. - - - - - - - - Distance (metres) as defined by http://www.ordnancesurvey.co.uk/xml/resource/units.xml#metres. ALternative units may be specifed by context. - - - - - - Distance (metres per second) ALternative unist may be specifed by context. - - - - - - Type for absolute bearing. - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG9 Team. + Europe + First drafted for version 1.0 CEN TC278 WG3 SG9 Editor Nicholas Knowles. mailto:schemer@siri.org.uk + + 2004-09-29 + + + 2004-10-01 + + + 2005-02-14 + + + 2005-05-11 + + + 2005-05-04 + + + 2007-03-29 + + + 2012-03-23 + + + + 2012-05-10 + + + +

      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/schema/2.0/xsd/siri_utility/}siri_location.xsd + [ISO 639-2/B] ENG + CEN + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG XML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG9. + + SIRI XML schema. Geo spatial location subschema + Standard +       +       + SIRI Framewrok Location Types. +       + + + + + + + + Longitude from Greenwich. + + + + + + + + + Latitude from equator. + + + + + + + + + Altitude metres from sea level. + + + + + + + + + WGS84 Coordinates. + + + + + Longitude from Greenwich Meridian. -180 (West) to +180 (East). Decimal degrees, e.g. 2.356 + + + + + Latitude from equator. -90 (South) to +90 (North). Decimal degrees, e.g. 56.356 + + + + + Altitude metres from sea level. + + + + + + + Type for GM Coordinates. + + + + + + + + Type for coordinate reference system. + + + + + + GML Spatial coordinate reference system. + + + + + + Type for geospatial Position of a point. May be expressed in concrete WGS 84 Coordinates or any gml compatible point coordinates format. + + + + + + + + + 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. + + + + + + Defines a bounding box using two corner points. GML terminology. +SIRI v2.0 + + + + + Upper Left corner as a geospatial point. + + + + + Lower right corner as a geospatial point. + + + + + + + Defines a line shape +SIRI v2.0 + + + + + A geospatial point. +SIRI v2.0 + + + + + + + Type for a circular area centered around a point that may be expressed in concrete WGS 84 Coordinates or any gml compatible point coordinates format. +SIRI v2.1 + + + + + + + Radius around the center point in meters. + + + + + + + + + Bounding box, circular area or gml:polyon of the area where stops of a flexible service are called. +SIRI v2.1 +A flexible area is used in cases where a pre-booked service allows pick-up/drop-off anywhere in a designated area and provides a possible interchange to a higher-frequency service. + + + + + Flexible area specified as a rectangular bounding box. + + + + + Flexible area specified as a circular area (center coordinates and radius). + + + + + Flexible area specified as a gml:Polygon that consists of an interior and exterior linear ring. + + + + + + + + Distance (metres) as defined by http://www.ordnancesurvey.co.uk/xml/resource/units.xml#metres. ALternative units may be specifed by context. + + + + + + Distance (metres per second) ALternative unist may be specifed by context. + + + + + + Type for absolute bearing. + + + +       diff --git a/xsd/siri_utility/siri_participant.xsd b/xsd/siri_utility/siri_participant.xsd index 19db825e..73187ac5 100644 --- a/xsd/siri_utility/siri_participant.xsd +++ b/xsd/siri_utility/siri_participant.xsd @@ -1,79 +1,79 @@ - - - - - - - main schema - e-service developers - CEN TC278 WG3 SG9 Team. - Europe - First drafted for version 1.0 CEN TC278 WG3 SG9 Editor Nicholas Knowles. mailto:schemer@siri.org.uk - - 2004-09-29 - - - 2007-05-15 - - - 2008-07-015 - - - - 2012-03-22 - - - -

      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/schema/2.0/xsd/siri_utility/}siri_participant.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIGXML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG9. - - SIRI XML schema. Participant type elements. - Standard -       -       - SIRI Framework Participant Types. -       - - - - Type for Unique identifier of participant. - - - - - - Reference to Unique identifier of participant. - - - - - -       + + + + + + + main schema + e-service developers + CEN TC278 WG3 SG9 Team. + Europe + First drafted for version 1.0 CEN TC278 WG3 SG9 Editor Nicholas Knowles. mailto:schemer@siri.org.uk + + 2004-09-29 + + + 2007-05-15 + + + 2008-07-015 + + + + 2012-03-22 + + + +

      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/schema/2.0/xsd/siri_utility/}siri_participant.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIGXML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG9. + + SIRI XML schema. Participant type elements. + Standard +       +       + SIRI Framework Participant Types. +       + + + + Type for Unique identifier of participant. + + + + + + Reference to Unique identifier of participant. + + + + + +       diff --git a/xsd/siri_utility/siri_permissions.xsd b/xsd/siri_utility/siri_permissions.xsd index 42d3683e..6fd10786 100644 --- a/xsd/siri_utility/siri_permissions.xsd +++ b/xsd/siri_utility/siri_permissions.xsd @@ -1,135 +1,135 @@ - - - - - - main schema - e-service developers - CEN TC278 WG3 SG9 Team. - Europe - First drafted for version 2.0 CEN TC278 WG3 SG9 Editor Nicholas Knowles. mailto:schemer@siri.org.uk - - 2012-03-24 - - - 2012-03-23 - - - -

      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/schema/2.0/xsd/siri_utility/}siri_permissions.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_utility.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_uility/siri_participant.xsd - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIGXML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG9. - - SIRI XML schema. Common Permission model subschema. - Standard -       -       - SIRI Framework Permission Types. -       - - - - - - - - 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 Common Access control capabilities. - - - - - Whether access control of requests is supported. Default is 'false'. - - - - - - - - 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. - - - - - - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG9 Team. + Europe + First drafted for version 2.0 CEN TC278 WG3 SG9 Editor Nicholas Knowles. mailto:schemer@siri.org.uk + + 2012-03-24 + + + 2012-03-23 + + + +

      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/schema/2.0/xsd/siri_utility/}siri_permissions.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_utility.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_uility/siri_participant.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIGXML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG9. + + SIRI XML schema. Common Permission model subschema. + Standard +       +       + SIRI Framework Permission Types. +       + + + + + + + + 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 Common Access control capabilities. + + + + + Whether access control of requests is supported. Default is 'false'. + + + + + + + + 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. + + + + + + + + +       diff --git a/xsd/siri_utility/siri_types.xsd b/xsd/siri_utility/siri_types.xsd index 37418a50..a1cd32c6 100644 --- a/xsd/siri_utility/siri_types.xsd +++ b/xsd/siri_utility/siri_types.xsd @@ -1,166 +1,166 @@ - - - - - - - main schema - e-service developers - Europe - First drafted for version 1.0 CEN TC278 WG3 SG9 Editor Nicholas Knowles. mailto:schemer@siri.org.uk - - 2005-10-03 - - - 2005-10-04 - - - 2005-05-11 - - - 2007-04-17 - - - 2012-03-23 - - - -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri_utility/}siri_types.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIG CML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, - Air transport, Airports, - Ports and maritime transport, Ferries (marine), - Public transport, Bus services, Coach services, Bus stops and stations, - Rail transport, Railway stations and track, Train services, Underground trains, - Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, - Rail transport, Roads and road transport - - CEN TC278 WG3 SG9. - - SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of time types. - Standard -       -       - SIRI Framework Base Types. -       - - - - A string indicating the versioin of a SIRI data structure. - - - - - - 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. - - - - - - 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. - - - - - - Length type for short distances. System for Units can be specified on frame. Normally (metres) as defined by http://www.ordnancesurvey.co.uk/xml/resource/units.xml#metres. - - - - - - Weight type for mass. System for Units can be specified on Frame. Normal default is (kilos) as defined by http://www.ordnancesurvey.co.uk/xml/resource/units.xml#metres. - - - - - - Number of passengers - capacity. - - - - - - Specifies a percentage from 0 to 100. -The value range is normally 0-100, but could in some circumstances go beyond 100%, e.g. when representing the OccupancyPercentage of an over-crowded vehicle or in similar cases. - - - - - -       + + + + + + + main schema + e-service developers + Europe + First drafted for version 1.0 CEN TC278 WG3 SG9 Editor Nicholas Knowles. mailto:schemer@siri.org.uk + + 2005-10-03 + + + 2005-10-04 + + + 2005-05-11 + + + 2007-04-17 + + + 2012-03-23 + + + +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/siri_utility/}siri_types.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG CML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, + Air transport, Airports, + Ports and maritime transport, Ferries (marine), + Public transport, Bus services, Coach services, Bus stops and stations, + Rail transport, Railway stations and track, Train services, Underground trains, + Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, + Rail transport, Roads and road transport + + CEN TC278 WG3 SG9. + + SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of time types. + Standard +       +       + SIRI Framework Base Types. +       + + + + A string indicating the versioin of a SIRI data structure. + + + + + + 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. + + + + + + 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. + + + + + + Length type for short distances. System for Units can be specified on frame. Normally (metres) as defined by http://www.ordnancesurvey.co.uk/xml/resource/units.xml#metres. + + + + + + Weight type for mass. System for Units can be specified on Frame. Normal default is (kilos) as defined by http://www.ordnancesurvey.co.uk/xml/resource/units.xml#metres. + + + + + + Number of passengers - capacity. + + + + + + Specifies a percentage from 0 to 100. +The value range is normally 0-100, but could in some circumstances go beyond 100%, e.g. when representing the OccupancyPercentage of an over-crowded vehicle or in similar cases. + + + + + +       diff --git a/xsd/siri_utility/siri_utility.xsd b/xsd/siri_utility/siri_utility.xsd index ef2f767a..db5cfaee 100644 --- a/xsd/siri_utility/siri_utility.xsd +++ b/xsd/siri_utility/siri_utility.xsd @@ -1,301 +1,301 @@ - - - - - - - main schema - e-service developers - CEN TC278 WG3 SG9 Team. - Europe - First drafted for version 1.0 CEN TC278 WG3 SG9 Editor Nicholas Knowles. mailto:schemer@siri.org.uk - - 2008-09-307 - - - - 2007-04-17 - - -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri_utiliyty/}siri_utility.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIGXML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG9. - - SIRI XML schema. Shared utility types - Standard -       -       - SIRI Framework Utility Types. -       - - - - - - A type with no allowed content, used when simply the presence of an element is significant. - - - - - - - - - Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). - - - - - Type for Extensions to schema. Wraps an 'any' tag to ensure decidability. - - - - - Placeholder for user extensions. - - - - - - - - A list of alternative Key values for an element. +SIRI v2.1 - - - - Every Key Value Pair must be unique. - - - - - - - - - Type for a Key List. +SIRI v2.1 - - - - - Key value pair for Entity. - - - - - - - Type for a Key List. +SIRI v2.1 - - - - - Identifier of value e.g. System. - - - - - Value for alternative key. - - - - - Identifier of type of key. - - - - - - - - VALUE SETs and TYPE OF VALUEs as part of the SIRI extension model. -TYPES OF VALUE can be used to exchange metadata for validation or collection of data, -such as the description and allowed values for codes. +SIRI v2.1 - - - - VALUE SETs must be unique. - - - - - - - - Type for containment of VALUE SETs and/or TYPE OF VALUEs. +SIRI v2.1 - - - - - - - - - A code value from an extensible set which may be added to by user applications, and is used to classify other SIRI entities. +SIRI v2.1 - - - - - Type for a TYPE OF VALUE. Used to define open classifications of value types. +SIRI v2.1 - - - - - Identifier of a TYPE OF VALUE. - - - - - Name of class of which TypeOfValue is an instance. - - - - - - - - Elements for TYPE OF VALUE. +SIRI v2.1 - - - - - Name of TYPE OF VALUE. - - - - - Short Name for TYPE OF VALUE. - - - - - Description of TYPE OF VALUE. - - - - - Default image for TYPE OF VALUE. - - - - - Default URL for TYPE OF VALUE. - - - - - Arbitrary code (usually the technical part of the identifier). - - - - - - - An extensible set of code values which may be added to by user applications and is used to validate the properties of entities. -Contains TYPE OF VALUEs that are an instance of the same class. +SIRI v2.1 - - - - TYPE OF VALUEs of the set must be unique. - - - - - - - - Type for a VALUE SET. Used to define open classifications of value types. +SIRI v2.1 - - - - - Identifier of VALUE SET. - - - - - Name of Class of values in set. - - - - - - - - Elements for VALUE SET. +SIRI v2.1 - - - - - Name of set. - - - - - Values in set. - - - - - - - Type for a list of TYPE OF VALUEs. +SIRI v2.1 - - - - - - - - - Type for identifier of a TYPE OF VALUE. +SIRI v2.1 - - - - - - Type for reference to a TYPE OF VALUE. +SIRI v2.1 - - - - - - - - Type for identifier of a VALUE SET. +SIRI v2.1 - - - - - - Name of class of which TypeOfValue is an instance. Used for reflection. +SIRI v2.1 - - - - -       + + + + + + + main schema + e-service developers + CEN TC278 WG3 SG9 Team. + Europe + First drafted for version 1.0 CEN TC278 WG3 SG9 Editor Nicholas Knowles. mailto:schemer@siri.org.uk + + 2008-09-307 + + + + 2007-04-17 + + +

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

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

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

      -

      This sub-schema describes the Vehicle Monitoring Service.

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/}siri_vehicleMonitoring_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_reference.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions.xsd - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.0 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI-VM XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Vehicle Monitoring Subschema - Standard -       -       - SIRI-VM Vehicle Monitoring Service. -       - - - - - - - - Convenience artifact to pick out main elements of the Vehicle Monitoring Service. - - - - - - - - - - - - - - - - Request for information about Vehicle Movements. - - - - - Type for Functional Service Request for Vehicle Monitoring Service. - - - - - - - - - - - Version number of request. Fixed - - - - - - - - - Detail Levels for Request. - - - - - Return only the minimum amount of optional data for each stop event to provide a display, A time, line name and destination name. - - - - - Return minimum and other available basic details for each stop event. Do not include data on time at next stop or destination. - - - - - Return all basic data, and also arrival times at DESTINATION. - - - - - Return all available data for each stop event, including previous and onward CALLs with passing times for JOURNEY PATTERN. - - - - - - - Parameters that specify the content to be returned. - - - - - A predefined scope for making VEHICLE requests. - - - - - - Reference to a specific VEHICLE about which data is requested. - - - - - Filter the results to include only vehicles for the specific LINE. - - - - - - Filter the results to include only VEHICLEs going to this DIRECTION. - - - - - - - Parameters that affect the request processing. - - - - - Preferred languages in which to return text values. - - - - - - The maximum number of MONITORED VEHICLE JOURNEYs to include in a given delivery. The most recent n Events within the look ahead window are included. - - - - - Level of detail to include in response. - - - - - If calls are to be returned, maximum number of calls to include in response. If absent, exclude all calls. +SIRI v2.0. - - - - - - Maximum number of previous calls to include. Only applies if VehicleMonitoringDetailLevel of Calls specified. Zero for none. If VehicleMonitoringDetailLevel of Calls specified but MaximumNumberOfCalls.Previous absent, include all previous calls. +SIRI v2.0. - - - - - Maximum number of onwards calls to include. Zero for none. Only applies if VehicleMonitoringDetailLevel of 'calls' specified. Zero for none. If VehicleMonitoringDetailLevel calls specified but MaximumNumberOfCalls.Onwards absent, include all onwards calls. +SIRI v2.0. - - - - - - - - Whether any related Situations should be included in the ServiceDelivery. Default is 'false'. +SIRI v2.0 - - - - - - - - Request for a subscription to the Vehicle Monitoring Service. - - - - - Parameters that affect the subscription publishing and notification processing. - - - - - Whether the producer will return the complete set of current data, or only provide updates to this data, i.e. additions, modifications and deletions. -If false or omitted, each subscription response will contain the full information as specified in this request. - - - - - - The amount of change to the VEHICLE expected arrival time at next stop that can happen before an update is sent (i.e. if ChangeBeforeUpdate is set to 2 minutes, the subscriber will not be told that a bus is 30 seconds delayed - an update will only be sent when the bus is at least 2 minutes delayed). - - - - - Time interval in seconds in which new data is to be transmitted. If unspecified, default to system configuration. - - - - - - - - Type for Subscription Request for Vehicle Monitoring Service. - - - - - - - - - - - - - - - - Delivery for Vehicle Monitoring Service. - - - - - Payload part of Vehicle Monitoring delivery. - - - - - Describes the progress of a VEHICLE along its route. - - - - - Reference to an previously communicated VEHICLE activity which should now be removed from the system. - - - - - Annotation to accompany of Vehicle Activities. - - - - - - - Type for Delivery for Vehicle Monitoring Service. Provides information about one or more vehicles; each has its own VEHICLE activity element. - - - - - - - - - - Version number of response. Fixed - - - - - - - - - - Type for a Vehicle Activity. - - - - - - - Time until when data is valid. - - - - - Reference to monitored VEHICLE or GROUP OF VEHICLEs. - - - - - Name associated with Monitoring Reference. Supports SIRI LITE servcies (+SIRI v2.0). - - - - - Provides information about the progress of the VEHICLE along its current link, that is link from previous visited top to current position. - - - - - Monitored VEHICLE JOURNEY that VEHICLE is following. - - - - - - - - - - Text associated with Delivery. - - - - - - - - - - Identifier of a Vehicle Monitoring scope. - - - - - - Type for reference to a Vehicle Monitoring scope - - - - - - - - - Type for cancellation of an earlier Vehicle Activity. - - - - - - - - - Reason for cancellation. (Unbounded since SIRI 2.0) - - - - - - - - - - Identifiers of Vehicle Activity. - - - - - - Reference to VEHICLE JOURNEY that VEHICLE is making. - - - - - - - - - Type for Deliveries for VEHICLE monitoring services Used in WSDL. - - - - - Delivery for Vehicle Moniroting Service. - - - - - - - - Request for information about Vehicle Monitoring Service Capabilities. Answered with a VehicleMontoringCapabilitiesResponse. - - - - - Type for capability request policy. - - - - - - - Whether results should return references. - - - - - Whether results should return references. - - - - - - - - - Capabilities of Vehicle Monitoring Service. - - - - - - Capabilities for Vehicle Monitoring Service. Answers a VehicleMontoringCapabilitiesRequest. - - - - - Type for Delivery for Vehicle Monitoring Service. - - - - - - - - - - - Version number of response. Fixed - - - - - - - - - Type for Vehicle Monitoring Capabilities. - - - - - - - Topic Filtering Capabilities. - - - - - - Default preview interval. Default is 60 minutes. - - - - - Whether results can be filtered by Vehicle Monitoring Fixed as 'true'. - - - - - - - - - - - Request Policy capabilities. - - - - - - - - - - - - - - Subscription Policy capabilities. - - - - - Optional Access control capabilities. - - - - - - - - - - If access control is supported, whether access control by monitoring point is supported. Default is 'true'. - - - - - - - - - - Optional Response capabilities. - - - - - - Whether result has location. Default is 'true'. - - - - - Whether result supports SITUATION REFERENCESs. Default is 'false'. +SIRI v2.0 - - - - - - - - - - - - - Elements for volume control. - - - - - Whether Detail level filtering is supported. Default is ' false'. - - - - - Detail level. Default Normal. - - - - - Whether results can be limited to a maximum number. Default is 'true'. - - - - - If system can return detailed calling pattern, whether a number of calls to include can be specified. Default is 'false'. +SIRI 2.0 - - - - - If system can return detailed calling pattern, whether a number of onwards calls to include can be specified. Default is 'false'. +SIRI 2.0 - - - - - If system can return detailed calling pattern, whether a number of previous calls to include can be specified. Default is 'false'. +SIRI 2.0 - - - - - - - Participant's permissions to use the service. - - - - - - - - Permissions for use of VEHICLE MONITORING. Can be used to specify which Consumers can see which vehicles - - - - - - - - - - - Type for Monitoring Service Permissions. - - - - - - - - - The Vehicle Monitors (DIUSPLAY ASSIGNMENTs) that the participant may access. - - - - - - - Participant's permission for this Vehicle Monitor (DISPLAY SSIGNMENT). - - - - - - - - - - - - - Type for MonitoringPoint Permission. - - - - - - - Vehicle Monitoring reference for which permission is made. - - - - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2004-09-29 + + + 2004-10-01 + + + 2005-02-14 + + + 2005-02-20 + + + 2005-05-11 + + + 2007-04-17 + + + + 2007-03-26 + + + + 2008-11-17 + + + + 2012-03-23 + + + + 2012-04-29 + + + + 2013-02-11 + + + +

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

      +

      This sub-schema describes the Vehicle Monitoring Service.

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

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

      -

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

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

      -

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

      -

      SIRI includes common mechanisms and messages for system status management.

      -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0}siri.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/siri_wsCOnsumer-Document.wsdl - - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, -Rail transport, Roads and road transport. - - CEN TC278 WG3 SG7 - - XSD elements for WSDL Consumer (Document Wrapped style) interface for SIRI XML schema. Service Interface for Real Time Information relating to Public Transport Operations. - Standard -       -       -       - - - - Type for Heartbeat Notifcation - - - - - - - - - - - - Type for Data Ready Notication - - - - - - - - - - - Type for TerminateSubscription Notication - - - - - - -       + + + + + + + main schema + e-service developers + Christophe Duquesne, Aurige, Guyancourt FRANCE + Michel Etienne, Cityway, Paris FRANCE + Robin Vettier, RATP, Paris FRANCE + Nicholas Knowles, KIZOOM LTD., London EC4A 1LT + Europe + >Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Christophe Duquesne, Aurige + + 2012-05-29 + + +

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

      +

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

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

      +

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

      +

      SIRI includes common mechanisms and messages for system status management.

      +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0}siri.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/siri_wsCOnsumer-Document.wsdl + + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG XML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, +Rail transport, Roads and road transport. + + CEN TC278 WG3 SG7 + + XSD elements for WSDL Consumer (Document Wrapped style) interface for SIRI XML schema. Service Interface for Real Time Information relating to Public Transport Operations. + Standard +       +       +       + + + + Type for Heartbeat Notifcation + + + + + + + + + + + + Type for Data Ready Notication + + + + + + + + + + + Type for TerminateSubscription Notication + + + + + + +       diff --git a/xsd/wsdl_model/siri_wsConsumer-Services.xsd b/xsd/wsdl_model/siri_wsConsumer-Services.xsd index 9a3f04a9..4e9cd132 100644 --- a/xsd/wsdl_model/siri_wsConsumer-Services.xsd +++ b/xsd/wsdl_model/siri_wsConsumer-Services.xsd @@ -1,155 +1,155 @@ - - - - - - - main schema - e-service developers - Christophe Duquesne, Aurige, Guyancourt FRANCE - Michel Etienne, Cityway, Paris FRANCE - Robin Vettier, RATP, Paris FRANCE - Nicholas Knowles, KIZOOM LTD., London EC4A 1LT - Europe - >Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Christophe Duquesne, Aurige - - 2012-05-29 - - -

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

      -

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

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

      -

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

      -

      SIRI includes common mechanisms and messages for system status management.

      -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0}siri.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/siri_wsCOnsumer-Document.wsdl - - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, -Rail transport, Roads and road transport. - - CEN TC278 WG3 SG7 - - XSD elements for WSDL Consumer (Document Wrapped style) interface for SIRI XML schema. Service Interface for Real Time Information relating to Public Transport Operations. - Standard -       -       -       - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -       + + + + + + + main schema + e-service developers + Christophe Duquesne, Aurige, Guyancourt FRANCE + Michel Etienne, Cityway, Paris FRANCE + Robin Vettier, RATP, Paris FRANCE + Nicholas Knowles, KIZOOM LTD., London EC4A 1LT + Europe + >Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Christophe Duquesne, Aurige + + 2012-05-29 + + +

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

      +

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

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

      +

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

      +

      SIRI includes common mechanisms and messages for system status management.

      +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0}siri.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/siri_wsCOnsumer-Document.wsdl + + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG XML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, +Rail transport, Roads and road transport. + + CEN TC278 WG3 SG7 + + XSD elements for WSDL Consumer (Document Wrapped style) interface for SIRI XML schema. Service Interface for Real Time Information relating to Public Transport Operations. + Standard +       +       +       + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +       diff --git a/xsd/wsdl_model/siri_wsProducer-DiscoveryCapability.xsd b/xsd/wsdl_model/siri_wsProducer-DiscoveryCapability.xsd index 05d41b08..e49acf1f 100644 --- a/xsd/wsdl_model/siri_wsProducer-DiscoveryCapability.xsd +++ b/xsd/wsdl_model/siri_wsProducer-DiscoveryCapability.xsd @@ -1,123 +1,123 @@ - - - - - - - main schema - e-service developers - Christophe Duquesne, Aurige, Guyancourt FRANCE - Michel Etienne, Cityway, Paris FRANCE - Robin Vettier, RATP, Paris FRANCE - Nicholas Knowles, KIZOOM LTD., London EC4A 1LT - Europe - >Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Christophe Duquesne, Aurige - - 2012-05-29 - - -

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

      -

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

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

      -

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

      -

      SIRI includes common mechanisms and messages for system status management.

      -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0}siri.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/siri_wsCOnsumer-Document.wsdl - - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, -Rail transport, Roads and road transport. - - CEN TC278 WG3 SG7 - - XSD elements for WSDL Consumer (Document Wrapped style) interface for SIRI XML schema. Service Interface for Real Time Information relating to Public Transport Operations. - Standard -       -       -       - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -       + + + + + + + main schema + e-service developers + Christophe Duquesne, Aurige, Guyancourt FRANCE + Michel Etienne, Cityway, Paris FRANCE + Robin Vettier, RATP, Paris FRANCE + Nicholas Knowles, KIZOOM LTD., London EC4A 1LT + Europe + >Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Christophe Duquesne, Aurige + + 2012-05-29 + + +

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

      +

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

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

      +

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

      +

      SIRI includes common mechanisms and messages for system status management.

      +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0}siri.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/siri_wsCOnsumer-Document.wsdl + + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG XML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, +Rail transport, Roads and road transport. + + CEN TC278 WG3 SG7 + + XSD elements for WSDL Consumer (Document Wrapped style) interface for SIRI XML schema. Service Interface for Real Time Information relating to Public Transport Operations. + Standard +       +       +       + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +       diff --git a/xsd/wsdl_model/siri_wsProducer-Framework.xsd b/xsd/wsdl_model/siri_wsProducer-Framework.xsd index c92ced92..d9b7dc1d 100644 --- a/xsd/wsdl_model/siri_wsProducer-Framework.xsd +++ b/xsd/wsdl_model/siri_wsProducer-Framework.xsd @@ -1,138 +1,138 @@ - - - - - - - main schema - e-service developers - Christophe Duquesne, Aurige, Guyancourt FRANCE - Michel Etienne, Cityway, Paris FRANCE - Robin Vettier, RATP, Paris FRANCE - Nicholas Knowles, KIZOOM LTD., London EC4A 1LT - Europe - >Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Christophe Duquesne, Aurige - - 2012-05-29 - - -

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

      -

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

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

      -

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

      -

      SIRI includes common mechanisms and messages for system status management.

      -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0}siri.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/siri_wsCOnsumer-Document.wsdl - - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, -Rail transport, Roads and road transport. - - CEN TC278 WG3 SG7 - - XSD elements for WSDL Consumer (Document Wrapped style) interface for SIRI XML schema. Service Interface for Real Time Information relating to Public Transport Operations. - Standard -       -       -       - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -       + + + + + + + main schema + e-service developers + Christophe Duquesne, Aurige, Guyancourt FRANCE + Michel Etienne, Cityway, Paris FRANCE + Robin Vettier, RATP, Paris FRANCE + Nicholas Knowles, KIZOOM LTD., London EC4A 1LT + Europe + >Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Christophe Duquesne, Aurige + + 2012-05-29 + + +

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

      +

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

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

      +

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

      +

      SIRI includes common mechanisms and messages for system status management.

      +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0}siri.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/siri_wsCOnsumer-Document.wsdl + + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG XML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, +Rail transport, Roads and road transport. + + CEN TC278 WG3 SG7 + + XSD elements for WSDL Consumer (Document Wrapped style) interface for SIRI XML schema. Service Interface for Real Time Information relating to Public Transport Operations. + Standard +       +       +       + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +       diff --git a/xsd/wsdl_model/siri_wsProducer-Services.xsd b/xsd/wsdl_model/siri_wsProducer-Services.xsd index 375d769f..67c9fbf1 100644 --- a/xsd/wsdl_model/siri_wsProducer-Services.xsd +++ b/xsd/wsdl_model/siri_wsProducer-Services.xsd @@ -1,263 +1,263 @@ - - - - - - - main schema - e-service developers - Christophe Duquesne, Aurige, Guyancourt FRANCE - Michel Etienne, Cityway, Paris FRANCE - Robin Vettier, RATP, Paris FRANCE - Nicholas Knowles, KIZOOM LTD., London EC4A 1LT - Europe - >Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Christophe Duquesne, Aurige - - 2012-05-29 - - -

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

      -

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

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

      -

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

      -

      SIRI includes common mechanisms and messages for system status management.

      -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0}siri.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/siri_wsCOnsumer-Document.wsdl - - - - CEN, VDV, RTIG 2004-2020 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, -Rail transport, Roads and road transport. - - CEN TC278 WG3 SG7 - - XSD elements for WSDL Consumer (Document Wrapped style) interface for SIRI XML schema. Service Interface for Real Time Information relating to Public Transport Operations. - Standard -       -       -       - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -       + + + + + + + main schema + e-service developers + Christophe Duquesne, Aurige, Guyancourt FRANCE + Michel Etienne, Cityway, Paris FRANCE + Robin Vettier, RATP, Paris FRANCE + Nicholas Knowles, KIZOOM LTD., London EC4A 1LT + Europe + >Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Christophe Duquesne, Aurige + + 2012-05-29 + + +

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

      +

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

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

      +

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

      +

      SIRI includes common mechanisms and messages for system status management.

      +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0}siri.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/siri_wsCOnsumer-Document.wsdl + + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG XML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, +Rail transport, Roads and road transport. + + CEN TC278 WG3 SG7 + + XSD elements for WSDL Consumer (Document Wrapped style) interface for SIRI XML schema. Service Interface for Real Time Information relating to Public Transport Operations. + Standard +       +       +       + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +       diff --git a/xsd/xml/2008/09/xsd.xsl b/xsd/xml/2008/09/xsd.xsl index cacffdb9..6c3b7fcd 100644 --- a/xsd/xml/2008/09/xsd.xsl +++ b/xsd/xml/2008/09/xsd.xsl @@ -1,997 +1,997 @@ - - - - - - - - - - - - - - - ]> - - - - - - - - - - - - - - - - - - - - - Schema document for - - - namespace - - - - unspecified namespace - - - - - - - - - - - - - - text/css - .bodytext .bodytext { - margin-left: 0; - margin-right: 0; - } - .bodytext { - margin-left: 15%; - margin-right: 2%; - } - .annotation { - - - } - .same-ns { - color: Green; - } - .diff-ns { - color: maroon; - } - .warning { - color: red; - } - p.note { - font-style: italic; - } - p.dt { - font-weight: bold; - } - span.rfc { - font-variant: small-caps; - } - - - - - - - - * * - - - - - - - - - - - bodytext - - - - - - - - - - - - - - - - - - - - - - annotation - - - - - - Annotation - - - - - - - - bodytext - - - - - - - - - - - - - - ! Unrecognized children in xs:documentation element - - - - - - - - - - - - - - - - - - - - - - -   - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - bodytext - - - - - Notes - - - - - External documentation at - - - - - - - - - - - - - - - Formal declaration in XSD source form - - - - - - - - - - - - - - - - - - - - - - - - - - - - - < - - - - - break - nobreak - - - - - - - - - - - > - - </ - - > - - /> - - - - - - - - - nobreak - - - - - - - - - - - - - - - - - - - - - - - =" - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - " - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Warning: not matched. - - warning - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - external-link same-ns - - - - - - external-link diff-ns - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - attnames - - - - - - attvals - - - - - - - - - - - - - - - - - - unknown - - - - - - - - 0 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + ]> + + + + + + + + + + + + + + + + + + + + + Schema document for + + + namespace + + + + unspecified namespace + + + + + + + + + + + + + + text/css + .bodytext .bodytext { + margin-left: 0; + margin-right: 0; + } + .bodytext { + margin-left: 15%; + margin-right: 2%; + } + .annotation { + + + } + .same-ns { + color: Green; + } + .diff-ns { + color: maroon; + } + .warning { + color: red; + } + p.note { + font-style: italic; + } + p.dt { + font-weight: bold; + } + span.rfc { + font-variant: small-caps; + } + + + + + + + + * * + + + + + + + + + + + bodytext + + + + + + + + + + + + + + + + + + + + + + annotation + + + + + + Annotation + + + + + + + + bodytext + + + + + + + + + + + + + + ! Unrecognized children in xs:documentation element + + + + + + + + + + + + + + + + + + + + + + +   + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + bodytext + + + + + Notes + + + + + External documentation at + + + + + + + + + + + + + + + Formal declaration in XSD source form + + + + + + + + + + + + + + + + + + + + + + + + + + + + + < + + + + + break + nobreak + + + + + + + + + + + > + + </ + + > + + /> + + + + + + + + + nobreak + + + + + + + + + + + + + + + + + + + + + + + =" + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + " + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Warning: not matched. + + warning + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + external-link same-ns + + + + + + external-link diff-ns + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + attnames + + + + + + attvals + + + + + + + + + + + + + + + + + + unknown + + + + + + + + 0 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/xsd/xml/2009/01/XMLSchema.xsd b/xsd/xml/2009/01/XMLSchema.xsd index b5baeb33..27c60c08 100644 --- a/xsd/xml/2009/01/XMLSchema.xsd +++ b/xsd/xml/2009/01/XMLSchema.xsd @@ -1,286 +1,286 @@ - - - - - - -
      -

      About the XML namespace

      - -
      -

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

      -

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

      -

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

      -

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

      -
      -
      -       -       - - - - -
      - -

      lang (as an attribute name)

      -

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

      - -
      -
      -

      Notes

      -

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

      -

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

      -

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

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

      space (as an attribute name)

      -

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

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

      base (as an attribute name)

      -

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

      - -

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

      -
      -       -       -       - - - - -
      - -

      id (as an attribute name)

      -

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

      - -

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

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

      Father (in any context at all)

      - -
      -

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

      -
      -

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

      -
      -
      -
      -       -       - - - -
      -

      About this schema document

      - -
      -

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

      -

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

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

      - or -

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

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

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

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

      -
      -
      -       -       - - - -
      -

      Versioning policy for this schema document

      -
      -

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

      -

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

      -

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

      -

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

      - -
      -
      -       -       - -       + + + + + + +
      +

      About the XML namespace

      + +
      +

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

      +

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

      +

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

      +

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

      +
      +
      +       +       + + + + +
      + +

      lang (as an attribute name)

      +

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

      + +
      +
      +

      Notes

      +

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

      +

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

      +

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

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

      space (as an attribute name)

      +

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

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

      base (as an attribute name)

      +

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

      + +

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

      +
      +       +       +       + + + + +
      + +

      id (as an attribute name)

      +

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

      + +

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

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

      Father (in any context at all)

      + +
      +

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

      +
      +

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

      +
      +
      +
      +       +       + + + +
      +

      About this schema document

      + +
      +

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

      +

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

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

      + or +

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

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

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

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

      +
      +
      +       +       + + + +
      +

      Versioning policy for this schema document

      +
      +

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

      +

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

      +

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

      +

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

      + +
      +
      +       +       + +       From 85660d2f61efc36d03c38a94d502c07a8ccdcec9 Mon Sep 17 00:00:00 2001 From: u215619 Date: Thu, 8 Apr 2021 13:22:58 +0200 Subject: [PATCH 264/290] undo line separator change --- .travis.yml | 20 +- .travis/travis-ci_git-commit.sh | 126 +- .travis/xmllint-check.sh | 6 +- Siri.spp | 474 +- Siri.xpr | 454 +- examples/index.htm | 666 +- .../exa_checkStatus_request.xml | 18 +- .../exa_checkStatus_response.xml | 22 +- .../exa_dataReady_request.xml | 16 +- .../exa_dataReady_response.xml | 18 +- .../exa_dataReceived_response.xml | 20 +- .../exa_dataSupply_request.xml | 20 +- .../exa_heartbeat_request.xml | 24 +- .../exa_requestSubscription_response.xml | 46 +- ...xa_subscriptionTerminated_notification.xml | 28 +- .../exa_terminateSubscription_request.xml | 18 +- .../exa_terminateSubscription_response.xml | 28 +- ...exa_terminateSubscription_response_err.xml | 30 +- ...nnectionMonitoringDistributor_response.xml | 166 +- ...xc_connectionMonitoringFeeder_response.xml | 132 +- ...nectionMonitoring_capabilitiesResponse.xml | 142 +- .../exc_connectionMonitoring_request.xml | 60 +- ...nnectionMonitoring_subscriptionRequest.xml | 44 +- ...nnectionTimetable_capabilitiesResponse.xml | 138 +- .../exc_connectionTimetable_request.xml | 38 +- .../exc_connectionTimetable_response.xml | 126 +- ...onnectionTimetable_subscriptionRequest.xml | 52 +- ...stimatedTimetable_capabilitiesResponse.xml | 136 +- .../ext_estimatedTimetable_request.xml | 44 +- .../ext_estimatedTimetable_response.xml | 182 +- ...estimatedTimetable_subscriptionRequest.xml | 56 +- ...acilityMonitoring_capabilitiesResponse.xml | 132 +- .../exf_facilityMonitoring_request.xml | 50 +- .../exf_facilityMonitoring_response.xml | 190 +- ...facilityMonitoring_subscriptionRequest.xml | 76 +- .../exm_generalMessage_capabilityResponse.xml | 134 +- .../exm_generalMessage_request.xml | 48 +- .../exm_generalMessage_response.xml | 60 +- .../exm_generalMessage_response_embed.xml | 130 +- ...exm_generalMessage_subscriptionRequest.xml | 38 +- ...oductionTimetable_capabilitiesResponse.xml | 140 +- .../ext_productionTimetable_request.xml | 48 +- .../ext_productionTimetable_response.xml | 226 +- ...roductionTimetable_subscriptionRequest.xml | 60 +- .../exp_stopMonitoring_permissions.xml | 152 +- ...xs_stopMonitoring_capabilitiesResponse.xml | 218 +- .../exs_stopMonitoring_request.xml | 90 +- .../exs_stopMonitoring_request_simple.xml | 34 +- .../exs_stopMonitoring_response.xml | 562 +- .../exs_stopMonitoring_response_complex.xml | 682 +- .../exs_stopMonitoring_response_simple.xml | 114 +- ...exs_stopMonitoring_subscriptionRequest.xml | 130 +- ...pMonitoring_subscriptionRequest_simple.xml | 52 +- ...exs_stopTimetable_capabilitiesResponse.xml | 166 +- .../siri_exm_ST/exs_stopTimetable_request.xml | 46 +- .../exs_stopTimetable_response.xml | 94 +- .../exs_stopTimetable_subscriptionRequest.xml | 52 +- .../VDV736_exm/SX_1010_first_message.xml | 508 +- .../VDV736_exm/SX_1022_main_message.xml | 4622 ++-- .../SX_1135_main_message_update.xml | 4412 +-- .../VDV736_exm/SX_1247_end_message.xml | 794 +- .../exx_situationExchangeResponse.xml | 560 +- .../exx_situationExchange_ATOC.xml | 202 +- .../siri_exm_SX/exx_situationExchange_Pt.xml | 202 +- ...x_situationExchange_capabilityResponse.xml | 138 +- .../exx_situationExchange_request.xml | 64 +- .../exx_situationExchange_request_simple.xml | 42 +- .../exx_situationExchange_response.xml | 556 +- .../exx_situationExchange_road.xml | 408 +- ..._situationExchange_subscriptionRequest.xml | 40 +- ...vehicleMonitoring_capabilitiesResponse.xml | 160 +- .../exv_vehicleMonitoring_request.xml | 68 +- .../exv_vehicleMonitoring_request_simple.xml | 44 +- .../exv_vehicleMonitoring_response.xml | 318 +- .../exv_vehicleMonitoring_response_simple.xml | 124 +- ...exv_vehicleMonitoring_responsex_simple.xml | 124 +- ..._vehicleMonitoring_subscriptionRequest.xml | 68 +- .../exd_allServices_capabilitiesRequest.xml | 76 +- .../exd_allServices_capabilitiesResponse.xml | 988 +- .../exd_lines_discoveryRequest.xml | 20 +- .../exd_lines_discoveryResponse.xml | 154 +- ...exd_productCategories_discoveryRequest.xml | 16 +- ...xd_productCategories_discoveryResponse.xml | 26 +- .../exd_serviceFeatures_discoveryRequest.xml | 16 +- .../exd_serviceFeatures_discoveryResponse.xml | 36 +- .../exd_stopPoints_discoveryRequest.xml | 48 +- .../exd_stopPoints_discoveryResponse.xml | 94 +- .../exd_vehicleFeatures_discoveryRequest.xml | 16 +- .../exd_vehicleFeatures_discoveryResponse.xml | 34 +- release-notes/ReadMe.txt | 908 +- release-notes/SIRI_XML-2.0q_changes.txt | 112 +- xsd/acsb/acsb_accessibility.xsd | 276 +- xsd/acsb/acsb_all.xsd | 22 +- xsd/acsb/acsb_limitations.xsd | 282 +- xsd/acsb/acsb_passengerMobility.xsd | 424 +- xsd/datex2/DATEXIISchema.xsd | 7420 ++--- xsd/datex2/DATEXIISchemaWithDefinitions.xsd | 23046 ++++++++-------- xsd/gml/basicTypes.xsd | 534 +- xsd/gml/geometryBasic0d1d-extract.xsd | 542 +- xsd/gml/gmlBase-extract.xsd | 336 +- xsd/gml/gmlBasic2d-extract.xsd | 240 +- xsd/gml/gml_extract_all_objects.xsd | 24 +- xsd/ifopt/ifopt_administration.xsd | 508 +- xsd/ifopt/ifopt_allStopPlace.xsd | 66 +- xsd/ifopt/ifopt_checkpoint.xsd | 444 +- xsd/ifopt/ifopt_countries.xsd | 2640 +- xsd/ifopt/ifopt_equipment.xsd | 414 +- xsd/ifopt/ifopt_location.xsd | 562 +- xsd/ifopt/ifopt_modes.xsd | 168 +- xsd/ifopt/ifopt_modification.xsd | 346 +- xsd/ifopt/ifopt_path.xsd | 328 +- xsd/ifopt/ifopt_stop.xsd | 786 +- xsd/ifopt/ifopt_time.xsd | 262 +- xsd/ifopt/ifopt_types.xsd | 192 +- xsd/siri.xsd | 1062 +- xsd/siri/siri_all_framework.xsd | 24 +- xsd/siri/siri_base.xsd | 630 +- xsd/siri/siri_common_services.xsd | 1800 +- xsd/siri/siri_request_errorConditions.xsd | 1180 +- xsd/siri/siri_request_support.xsd | 420 +- xsd/siri/siri_requests.xsd | 2144 +- xsd/siriSg.xsd | 298 +- xsd/siri_all_functionalServices.xsd | 190 +- xsd/siri_connectionMonitoring_service.xsd | 1462 +- xsd/siri_connectionTimetable_service.xsd | 970 +- xsd/siri_discovery.xsd | 1796 +- xsd/siri_estimatedTimetable_service.xsd | 980 +- xsd/siri_facilityMonitoring_service.xsd | 986 +- xsd/siri_generalMessage_service.xsd | 966 +- xsd/siri_model/siri_all.xsd | 26 +- xsd/siri_model/siri_all_journeyModel.xsd | 42 +- xsd/siri_model/siri_all_model.xsd | 26 +- xsd/siri_model/siri_all_situation.xsd | 34 +- xsd/siri_model/siri_datedVehicleJourney.xsd | 1404 +- .../siri_estimatedVehicleJourney.xsd | 944 +- xsd/siri_model/siri_facilities.xsd | 1034 +- xsd/siri_model/siri_facility.xsd | 1520 +- xsd/siri_model/siri_feature_support.xsd | 290 +- xsd/siri_model/siri_interchangeJourney.xsd | 176 +- xsd/siri_model/siri_journey.xsd | 3806 +-- xsd/siri_model/siri_journey_support.xsd | 2044 +- xsd/siri_model/siri_modelPermissions.xsd | 676 +- xsd/siri_model/siri_modes.xsd | 1372 +- .../siri_monitoredVehicleJourney.xsd | 1276 +- xsd/siri_model/siri_operator_support.xsd | 174 +- xsd/siri_model/siri_reference.xsd | 1688 +- xsd/siri_model/siri_situation.xsd | 3068 +- xsd/siri_model/siri_situationActions.xsd | 1498 +- xsd/siri_model/siri_situationAffects.xsd | 3066 +- xsd/siri_model/siri_situationClassifiers.xsd | 860 +- xsd/siri_model/siri_situationIdentity.xsd | 494 +- xsd/siri_model/siri_situationReasons.xsd | 2738 +- xsd/siri_model/siri_situationServiceTypes.xsd | 1278 +- .../siri_targetedVehicleJourney.xsd | 272 +- xsd/siri_model/siri_time.xsd | 712 +- .../siri_connectionLink.xsd | 230 +- xsd/siri_model_discovery/siri_feature.xsd | 316 +- xsd/siri_model_discovery/siri_infoChannel.xsd | 198 +- xsd/siri_model_discovery/siri_line.xsd | 482 +- xsd/siri_model_discovery/siri_stopPoint.xsd | 316 +- xsd/siri_productionTimetable_service.xsd | 1028 +- xsd/siri_situationExchange_service.xsd | 1570 +- xsd/siri_stopMonitoring_service.xsd | 2104 +- xsd/siri_stopTimetable_service.xsd | 926 +- xsd/siri_utility/siri_all_utility.xsd | 28 +- xsd/siri_utility/siri_location.xsd | 540 +- xsd/siri_utility/siri_participant.xsd | 158 +- xsd/siri_utility/siri_permissions.xsd | 270 +- xsd/siri_utility/siri_types.xsd | 332 +- xsd/siri_utility/siri_utility.xsd | 602 +- xsd/siri_vehicleMonitoring_service.xsd | 1404 +- xsd/siri_wsConsumer-Document.wsdl | 354 +- xsd/siri_wsConsumer-WSDL2.wsdl | 192 +- xsd/siri_wsConsumer.wsdl | 400 +- xsd/siri_wsProducer-Document.wsdl | 1116 +- xsd/siri_wsProducer-WSDL2.wsdl | 458 +- xsd/siri_wsProducer.wsdl | 1258 +- xsd/wsdl_model/siri_wsConsumer-Framework.xsd | 196 +- xsd/wsdl_model/siri_wsConsumer-Services.xsd | 310 +- .../siri_wsProducer-DiscoveryCapability.xsd | 246 +- xsd/wsdl_model/siri_wsProducer-Framework.xsd | 276 +- xsd/wsdl_model/siri_wsProducer-Services.xsd | 526 +- xsd/xml/2008/09/xsd.xsl | 1994 +- xsd/xml/2009/01/XMLSchema.xsd | 572 +- 184 files changed, 63381 insertions(+), 63381 deletions(-) diff --git a/.travis.yml b/.travis.yml index 95d74298..7db6ea77 100644 --- a/.travis.yml +++ b/.travis.yml @@ -1,10 +1,10 @@ -language: minimal - -before_script: - - sudo apt-get install -qq libxml2-utils - -script: - - bash .travis/xmllint-check.sh - -after_script: - - bash .travis/travis-ci_git-commit.sh +language: minimal + +before_script: + - sudo apt-get install -qq libxml2-utils + +script: + - bash .travis/xmllint-check.sh + +after_script: + - bash .travis/travis-ci_git-commit.sh diff --git a/.travis/travis-ci_git-commit.sh b/.travis/travis-ci_git-commit.sh index a245fa0f..896660f6 100644 --- a/.travis/travis-ci_git-commit.sh +++ b/.travis/travis-ci_git-commit.sh @@ -1,64 +1,64 @@ -#!/bin/bash -# function to make a commit on a branch in a Travis CI build -# be sure to avoid creating a Travis CI fork bomb -# see https://gist.github.com/mitchellkrogza/a296ab5102d7e7142cc3599fca634203 and https://github.com/travis-ci/travis-ci/issues/1701 -function travis-branch-commit() { - local head_ref branch_ref - head_ref=$(git rev-parse HEAD) - if [[ $? -ne 0 || ! $head_ref ]]; then - err "Failed to get HEAD reference" - return 1 - fi - branch_ref=$(git rev-parse "$TRAVIS_BRANCH") - if [[ $? -ne 0 || ! $branch_ref ]]; then - err "Failed to get $TRAVIS_BRANCH reference" - return 1 - fi - if [[ $head_ref != $branch_ref ]]; then - msg "HEAD ref ($head_ref) does not match $TRAVIS_BRANCH ref ($branch_ref)" - msg "Someone may have pushed new commits before this build cloned the repo" - return 1 - fi - if ! git checkout "$TRAVIS_BRANCH"; then - err "Failed to checkout $TRAVIS_BRANCH" - return 1 - fi - - if ! git add --all .; then - err "Failed to add modified files to git index" - return 1 - fi - # make Travis CI skip this build - if ! git commit -m "Travis CI update [skip ci]"; then - err "Failed to commit updates" - return 1 - fi - # add to your .travis.yml: `branches\n except:\n - "/travis_build-\\d+/"\n` - local git_tag=travis_build-$TRAVIS_BUILD_NUMBER - if ! git tag "$git_tag" -m "Generated tag from Travis CI build $TRAVIS_BUILD_NUMBER"; then - err "Failed to create git tag: $git_tag" - return 1 - fi - local remote=origin - if [[ $GH_TOKEN ]]; then - remote=https://$GH_TOKEN@github.com/$GH_REPO - fi - if [[ $TRAVIS_BRANCH == master ]]; then - msg "Not pushing updates to branch $TRAVIS_BRANCH" - return 0 - fi - if ! git push --quiet --follow-tags "$remote" "$TRAVIS_BRANCH" > /dev/null 2>&1; then - err "Failed to push git changes" - return 1 - fi -} - -function msg() { - echo "travis-commit: $*" -} - -function err() { - msg "$*" 1>&2 -} - +#!/bin/bash +# function to make a commit on a branch in a Travis CI build +# be sure to avoid creating a Travis CI fork bomb +# see https://gist.github.com/mitchellkrogza/a296ab5102d7e7142cc3599fca634203 and https://github.com/travis-ci/travis-ci/issues/1701 +function travis-branch-commit() { + local head_ref branch_ref + head_ref=$(git rev-parse HEAD) + if [[ $? -ne 0 || ! $head_ref ]]; then + err "Failed to get HEAD reference" + return 1 + fi + branch_ref=$(git rev-parse "$TRAVIS_BRANCH") + if [[ $? -ne 0 || ! $branch_ref ]]; then + err "Failed to get $TRAVIS_BRANCH reference" + return 1 + fi + if [[ $head_ref != $branch_ref ]]; then + msg "HEAD ref ($head_ref) does not match $TRAVIS_BRANCH ref ($branch_ref)" + msg "Someone may have pushed new commits before this build cloned the repo" + return 1 + fi + if ! git checkout "$TRAVIS_BRANCH"; then + err "Failed to checkout $TRAVIS_BRANCH" + return 1 + fi + + if ! git add --all .; then + err "Failed to add modified files to git index" + return 1 + fi + # make Travis CI skip this build + if ! git commit -m "Travis CI update [skip ci]"; then + err "Failed to commit updates" + return 1 + fi + # add to your .travis.yml: `branches\n except:\n - "/travis_build-\\d+/"\n` + local git_tag=travis_build-$TRAVIS_BUILD_NUMBER + if ! git tag "$git_tag" -m "Generated tag from Travis CI build $TRAVIS_BUILD_NUMBER"; then + err "Failed to create git tag: $git_tag" + return 1 + fi + local remote=origin + if [[ $GH_TOKEN ]]; then + remote=https://$GH_TOKEN@github.com/$GH_REPO + fi + if [[ $TRAVIS_BRANCH == master ]]; then + msg "Not pushing updates to branch $TRAVIS_BRANCH" + return 0 + fi + if ! git push --quiet --follow-tags "$remote" "$TRAVIS_BRANCH" > /dev/null 2>&1; then + err "Failed to push git changes" + return 1 + fi +} + +function msg() { + echo "travis-commit: $*" +} + +function err() { + msg "$*" 1>&2 +} + travis-branch-commit \ No newline at end of file diff --git a/.travis/xmllint-check.sh b/.travis/xmllint-check.sh index d2e0c442..ac2f81b1 100644 --- a/.travis/xmllint-check.sh +++ b/.travis/xmllint-check.sh @@ -1,4 +1,4 @@ -#!/bin/bash -/usr/bin/find . -name "*.xsd" -type f | while read i; do XMLLINT_INDENT=" " xmllint --pretty 1 "$i" > "$i.pretty"; mv "$i.pretty" "$i"; done; /usr/bin/find . -name "*.xml" -type f | while read i; do XMLLINT_INDENT=" " xmllint --pretty 1 "$i" > "$i.pretty"; mv "$i.pretty" "$i"; done; /usr/bin/find . -name "*.wsdl" -type f | while read i; do XMLLINT_INDENT=" " xmllint --pretty 1 "$i" > "$i.pretty"; mv "$i.pretty" "$i"; done; -echo "finished formatting" +#!/bin/bash +/usr/bin/find . -name "*.xsd" -type f | while read i; do XMLLINT_INDENT=" " xmllint --pretty 1 "$i" > "$i.pretty"; mv "$i.pretty" "$i"; done; /usr/bin/find . -name "*.xml" -type f | while read i; do XMLLINT_INDENT=" " xmllint --pretty 1 "$i" > "$i.pretty"; mv "$i.pretty" "$i"; done; /usr/bin/find . -name "*.wsdl" -type f | while read i; do XMLLINT_INDENT=" " xmllint --pretty 1 "$i" > "$i.pretty"; mv "$i.pretty" "$i"; done; +echo "finished formatting" find examples/ -iname "*.xml" | xargs xmllint --noout --schema xsd/siri.xsd \ No newline at end of file diff --git a/Siri.spp b/Siri.spp index 2b2a14f1..b92ab041 100644 --- a/Siri.spp +++ b/Siri.spp @@ -1,237 +1,237 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/Siri.xpr b/Siri.xpr index 96d29275..37df7dd1 100644 --- a/Siri.xpr +++ b/Siri.xpr @@ -1,228 +1,228 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/examples/index.htm b/examples/index.htm index 5c3bbc4a..7666a52f 100644 --- a/examples/index.htm +++ b/examples/index.htm @@ -1,334 +1,334 @@ - - - - - - - - - - - - - - - - - - - - - - - - - -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

       
      - - + + + + + + + + + + + + + + + + + + + + + + + + + +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/examples/siri_exa_framework/exa_checkStatus_request.xml b/examples/siri_exa_framework/exa_checkStatus_request.xml index 68843213..40ae1202 100644 --- a/examples/siri_exa_framework/exa_checkStatus_request.xml +++ b/examples/siri_exa_framework/exa_checkStatus_request.xml @@ -1,9 +1,9 @@ - - - - - - 2004-12-17T09:30:47-05:00 - EREWHON - - + + + + + + 2004-12-17T09:30:47-05:00 + EREWHON + + diff --git a/examples/siri_exa_framework/exa_checkStatus_response.xml b/examples/siri_exa_framework/exa_checkStatus_response.xml index 0dd01d2e..c9b81709 100644 --- a/examples/siri_exa_framework/exa_checkStatus_response.xml +++ b/examples/siri_exa_framework/exa_checkStatus_response.xml @@ -1,11 +1,11 @@ - - - - - 2001-12-17T09:30:47-05:00 - true - 2004-12-17T19:30:47-05:00 - PT2M - 2004-12-17T09:30:47-05:00 - - + + + + + 2001-12-17T09:30:47-05:00 + true + 2004-12-17T19:30:47-05:00 + PT2M + 2004-12-17T09:30:47-05:00 + + diff --git a/examples/siri_exa_framework/exa_dataReady_request.xml b/examples/siri_exa_framework/exa_dataReady_request.xml index 12486175..c3d16e45 100644 --- a/examples/siri_exa_framework/exa_dataReady_request.xml +++ b/examples/siri_exa_framework/exa_dataReady_request.xml @@ -1,8 +1,8 @@ - - - - - 2004-12-17T09:30:47-05:00 - KUBRICK - - + + + + + 2004-12-17T09:30:47-05:00 + KUBRICK + + diff --git a/examples/siri_exa_framework/exa_dataReady_response.xml b/examples/siri_exa_framework/exa_dataReady_response.xml index fcf8a014..146e6c4c 100644 --- a/examples/siri_exa_framework/exa_dataReady_response.xml +++ b/examples/siri_exa_framework/exa_dataReady_response.xml @@ -1,9 +1,9 @@ - - - - - 2004-12-17T09:30:47-05:00 - NADER - true - - + + + + + 2004-12-17T09:30:47-05:00 + NADER + true + + diff --git a/examples/siri_exa_framework/exa_dataReceived_response.xml b/examples/siri_exa_framework/exa_dataReceived_response.xml index be5f8425..604cf8fb 100644 --- a/examples/siri_exa_framework/exa_dataReceived_response.xml +++ b/examples/siri_exa_framework/exa_dataReceived_response.xml @@ -1,10 +1,10 @@ - - - - - 2001-12-17T09:30:47-05:00 - NADER - 012225678 - true - - + + + + + 2001-12-17T09:30:47-05:00 + NADER + 012225678 + true + + diff --git a/examples/siri_exa_framework/exa_dataSupply_request.xml b/examples/siri_exa_framework/exa_dataSupply_request.xml index 562de3ee..2eb98a43 100644 --- a/examples/siri_exa_framework/exa_dataSupply_request.xml +++ b/examples/siri_exa_framework/exa_dataSupply_request.xml @@ -1,10 +1,10 @@ - - - - - 2004-12-17T09:30:47-05:00 - NADER - ABCDE0 - false - - + + + + + 2004-12-17T09:30:47-05:00 + NADER + ABCDE0 + false + + diff --git a/examples/siri_exa_framework/exa_heartbeat_request.xml b/examples/siri_exa_framework/exa_heartbeat_request.xml index 7becdc00..7336f549 100644 --- a/examples/siri_exa_framework/exa_heartbeat_request.xml +++ b/examples/siri_exa_framework/exa_heartbeat_request.xml @@ -1,12 +1,12 @@ - - - - - 2004-12-17T09:30:47-05:00 - KUBRICK - true - 2004-12-17T09:30:47-05:00 - P1Y2M3DT10H30M - 2004-12-17T09:30:47-05:00 - - + + + + + 2004-12-17T09:30:47-05:00 + KUBRICK + true + 2004-12-17T09:30:47-05:00 + P1Y2M3DT10H30M + 2004-12-17T09:30:47-05:00 + + diff --git a/examples/siri_exa_framework/exa_requestSubscription_response.xml b/examples/siri_exa_framework/exa_requestSubscription_response.xml index e4b0bf85..75770eff 100644 --- a/examples/siri_exa_framework/exa_requestSubscription_response.xml +++ b/examples/siri_exa_framework/exa_requestSubscription_response.xml @@ -1,23 +1,23 @@ - - - - - 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 - - - - - - + + + + + 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 + + + + + + diff --git a/examples/siri_exa_framework/exa_subscriptionTerminated_notification.xml b/examples/siri_exa_framework/exa_subscriptionTerminated_notification.xml index 23e3f43e..7091b843 100644 --- a/examples/siri_exa_framework/exa_subscriptionTerminated_notification.xml +++ b/examples/siri_exa_framework/exa_subscriptionTerminated_notification.xml @@ -1,14 +1,14 @@ - - - - - 2004-12-17T09:30:47-05:00 - KUBRICK - NADER - 987653 - - - Weekly restart - - - + + + + + 2004-12-17T09:30:47-05:00 + KUBRICK + NADER + 987653 + + + Weekly restart + + + diff --git a/examples/siri_exa_framework/exa_terminateSubscription_request.xml b/examples/siri_exa_framework/exa_terminateSubscription_request.xml index 5d2cf9b8..4bd376d5 100644 --- a/examples/siri_exa_framework/exa_terminateSubscription_request.xml +++ b/examples/siri_exa_framework/exa_terminateSubscription_request.xml @@ -1,9 +1,9 @@ - - - - - 2004-12-17T09:30:47-05:00 - NADER - - - + + + + + 2004-12-17T09:30:47-05:00 + NADER + + + diff --git a/examples/siri_exa_framework/exa_terminateSubscription_response.xml b/examples/siri_exa_framework/exa_terminateSubscription_response.xml index 6393d0e6..adff2aa2 100644 --- a/examples/siri_exa_framework/exa_terminateSubscription_response.xml +++ b/examples/siri_exa_framework/exa_terminateSubscription_response.xml @@ -1,14 +1,14 @@ - - - - - 2004-12-17T09:30:47-05:00 - KUBRICK - - 2004-12-17T09:30:47-05:00 - NADER - 0000456 - true - - - + + + + + 2004-12-17T09:30:47-05:00 + KUBRICK + + 2004-12-17T09:30:47-05:00 + NADER + 0000456 + true + + + diff --git a/examples/siri_exa_framework/exa_terminateSubscription_response_err.xml b/examples/siri_exa_framework/exa_terminateSubscription_response_err.xml index aac2b3fe..664f61a5 100644 --- a/examples/siri_exa_framework/exa_terminateSubscription_response_err.xml +++ b/examples/siri_exa_framework/exa_terminateSubscription_response_err.xml @@ -1,15 +1,15 @@ - - - - - 2004-12-17T09:30:47-05:00 - KUBRICK - - 987653 - false - - - - - - + + + + + 2004-12-17T09:30:47-05:00 + KUBRICK + + 987653 + false + + + + + + diff --git a/examples/siri_exm_CM/exc_connectionMonitoringDistributor_response.xml b/examples/siri_exm_CM/exc_connectionMonitoringDistributor_response.xml index 23c28e78..eb686154 100644 --- a/examples/siri_exm_CM/exc_connectionMonitoringDistributor_response.xml +++ b/examples/siri_exm_CM/exc_connectionMonitoringDistributor_response.xml @@ -1,83 +1,83 @@ - - - - - - 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 - - - - + + + + + + 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/examples/siri_exm_CM/exc_connectionMonitoringFeeder_response.xml b/examples/siri_exm_CM/exc_connectionMonitoringFeeder_response.xml index 8e2679a8..7e186f37 100644 --- a/examples/siri_exm_CM/exc_connectionMonitoringFeeder_response.xml +++ b/examples/siri_exm_CM/exc_connectionMonitoringFeeder_response.xml @@ -1,66 +1,66 @@ - - - - - - 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 - 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 - - - - + + + + + + 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 + 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/examples/siri_exm_CM/exc_connectionMonitoring_capabilitiesResponse.xml b/examples/siri_exm_CM/exc_connectionMonitoring_capabilitiesResponse.xml index 5a0264ee..88fcd3ed 100644 --- a/examples/siri_exm_CM/exc_connectionMonitoring_capabilitiesResponse.xml +++ b/examples/siri_exm_CM/exc_connectionMonitoring_capabilitiesResponse.xml @@ -1,71 +1,71 @@ - - - - 2001-12-17T09:30:47.0Z - http://www.mytransportco.eu - true - - - - cpidId001 - - String - - - - - true - true - - - true - true - - true - true - true - true - - - PT60M - true - true - true - - - en - - - - true - true - - - true - true - true - true - - - - - - - - true - true - - - true - - - true - - - true - - - - - - + + + + 2001-12-17T09:30:47.0Z + http://www.mytransportco.eu + true + + + + cpidId001 + + String + + + + + true + true + + + true + true + + true + true + true + true + + + PT60M + true + true + true + + + en + + + + true + true + + + true + true + true + true + + + + + + + + true + true + + + true + + + true + + + true + + + + + + diff --git a/examples/siri_exm_CM/exc_connectionMonitoring_request.xml b/examples/siri_exm_CM/exc_connectionMonitoring_request.xml index 86cb7ac4..d94783c2 100644 --- a/examples/siri_exm_CM/exc_connectionMonitoring_request.xml +++ b/examples/siri_exm_CM/exc_connectionMonitoring_request.xml @@ -1,30 +1,30 @@ - - - - - - 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 - - - - + + + + + + 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 + + + + diff --git a/examples/siri_exm_CM/exc_connectionMonitoring_subscriptionRequest.xml b/examples/siri_exm_CM/exc_connectionMonitoring_subscriptionRequest.xml index 7d827630..36ea5958 100644 --- a/examples/siri_exm_CM/exc_connectionMonitoring_subscriptionRequest.xml +++ b/examples/siri_exm_CM/exc_connectionMonitoring_subscriptionRequest.xml @@ -1,22 +1,22 @@ - - - - - 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 - - - - - + + + + + 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 + + + + + diff --git a/examples/siri_exm_CT/exc_connectionTimetable_capabilitiesResponse.xml b/examples/siri_exm_CT/exc_connectionTimetable_capabilitiesResponse.xml index 89effee7..f5d0d55f 100644 --- a/examples/siri_exm_CT/exc_connectionTimetable_capabilitiesResponse.xml +++ b/examples/siri_exm_CT/exc_connectionTimetable_capabilitiesResponse.xml @@ -1,69 +1,69 @@ - - - - 2001-12-17T09:30:47.0Z - http://www.mytransportco.eu - true - - - cpidId001 - - String - - - - - true - true - - - true - true - - true - true - true - true - - - true - true - - - en - - - - true - true - - - true - true - true - true - - - - - 0001 - - - - true - true - - - true - - - true - - - true - - - - - - + + + + 2001-12-17T09:30:47.0Z + http://www.mytransportco.eu + true + + + cpidId001 + + String + + + + + true + true + + + true + true + + true + true + true + true + + + true + true + + + en + + + + true + true + + + true + true + true + true + + + + + 0001 + + + + true + true + + + true + + + true + + + true + + + + + + diff --git a/examples/siri_exm_CT/exc_connectionTimetable_request.xml b/examples/siri_exm_CT/exc_connectionTimetable_request.xml index df11fec8..f4dbadeb 100644 --- a/examples/siri_exm_CT/exc_connectionTimetable_request.xml +++ b/examples/siri_exm_CT/exc_connectionTimetable_request.xml @@ -1,19 +1,19 @@ - - - - - - 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 - - - + + + + + + 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 + + + diff --git a/examples/siri_exm_CT/exc_connectionTimetable_response.xml b/examples/siri_exm_CT/exc_connectionTimetable_response.xml index 69025549..725cda7d 100644 --- a/examples/siri_exm_CT/exc_connectionTimetable_response.xml +++ b/examples/siri_exm_CT/exc_connectionTimetable_response.xml @@ -1,63 +1,63 @@ - - - - - - 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 - - - - + + + + + + 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/examples/siri_exm_CT/exc_connectionTimetable_subscriptionRequest.xml b/examples/siri_exm_CT/exc_connectionTimetable_subscriptionRequest.xml index 813db8d1..7c0d7c2c 100644 --- a/examples/siri_exm_CT/exc_connectionTimetable_subscriptionRequest.xml +++ b/examples/siri_exm_CT/exc_connectionTimetable_subscriptionRequest.xml @@ -1,26 +1,26 @@ - - - - - 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 - - - - + + + + + 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 + + + + diff --git a/examples/siri_exm_ET/ext_estimatedTimetable_capabilitiesResponse.xml b/examples/siri_exm_ET/ext_estimatedTimetable_capabilitiesResponse.xml index 2ffca2bd..e1420e1b 100644 --- a/examples/siri_exm_ET/ext_estimatedTimetable_capabilitiesResponse.xml +++ b/examples/siri_exm_ET/ext_estimatedTimetable_capabilitiesResponse.xml @@ -1,68 +1,68 @@ - - - - 2001-12-17T09:30:47.0Z - http://www.mytransportco.eu - true - - - cpidId001 - - String - - - - - true - true - - - true - true - - true - true - true - true - - - true - true - - - en-uk - - - - true - - - true - true - true - true - - - - - 001 - - - - true - true - - - true - - - true - - - true - - - - - - + + + + 2001-12-17T09:30:47.0Z + http://www.mytransportco.eu + true + + + cpidId001 + + 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/examples/siri_exm_ET/ext_estimatedTimetable_request.xml b/examples/siri_exm_ET/ext_estimatedTimetable_request.xml index 172fc6f6..24faf55d 100644 --- a/examples/siri_exm_ET/ext_estimatedTimetable_request.xml +++ b/examples/siri_exm_ET/ext_estimatedTimetable_request.xml @@ -1,22 +1,22 @@ - - - - - - 2004-12-17T09:30:47-05:00 - NADER - - - 2001-12-17T09:30:47-05:00 - P1Y2M3DT10H30M - 0008 - SMOOTH - - - 123 - INBOUND - - - - - + + + + + + 2004-12-17T09:30:47-05:00 + NADER + + + 2001-12-17T09:30:47-05:00 + P1Y2M3DT10H30M + 0008 + SMOOTH + + + 123 + INBOUND + + + + + diff --git a/examples/siri_exm_ET/ext_estimatedTimetable_response.xml b/examples/siri_exm_ET/ext_estimatedTimetable_response.xml index b3e061d3..a1e4d6b2 100644 --- a/examples/siri_exm_ET/ext_estimatedTimetable_response.xml +++ b/examples/siri_exm_ET/ext_estimatedTimetable_response.xml @@ -1,91 +1,91 @@ - - - - - - 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 - Cat274 - 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 - - - - - + + + + + + 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 + Cat274 + 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/examples/siri_exm_ET/ext_estimatedTimetable_subscriptionRequest.xml b/examples/siri_exm_ET/ext_estimatedTimetable_subscriptionRequest.xml index 5e1b4f3b..2311bc09 100644 --- a/examples/siri_exm_ET/ext_estimatedTimetable_subscriptionRequest.xml +++ b/examples/siri_exm_ET/ext_estimatedTimetable_subscriptionRequest.xml @@ -1,28 +1,28 @@ - - - - - - 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 - - - + + + + + + 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/examples/siri_exm_FM/exf_facilityMonitoring_capabilitiesResponse.xml b/examples/siri_exm_FM/exf_facilityMonitoring_capabilitiesResponse.xml index b79580e3..5c9cc831 100644 --- a/examples/siri_exm_FM/exf_facilityMonitoring_capabilitiesResponse.xml +++ b/examples/siri_exm_FM/exf_facilityMonitoring_capabilitiesResponse.xml @@ -1,66 +1,66 @@ - - - - 2001-12-17T09:30:47.0Z - http://www.mytransportco.eu - true - - - cpidId001 - - String - - - - - true - true - - - true - true - - true - true - true - true - - - PT60M - true - true - true - - - en-uk - - - - true - - - true - true - true - - - - - VR23 - - - - true - true - - - true - - - true - - - - - - + + + + 2001-12-17T09:30:47.0Z + http://www.mytransportco.eu + true + + + cpidId001 + + String + + + + + true + true + + + true + true + + true + true + true + true + + + PT60M + true + true + true + + + en-uk + + + + true + + + true + true + true + + + + + VR23 + + + + true + true + + + true + + + true + + + + + + diff --git a/examples/siri_exm_FM/exf_facilityMonitoring_request.xml b/examples/siri_exm_FM/exf_facilityMonitoring_request.xml index 8377dd08..e1d0cb4e 100644 --- a/examples/siri_exm_FM/exf_facilityMonitoring_request.xml +++ b/examples/siri_exm_FM/exf_facilityMonitoring_request.xml @@ -1,25 +1,25 @@ - - - - - - - en - P1Y2M3DT10H30M - P1Y2M3DT10H30M - direct - true - false - - - 2004-12-17T09:30:47-05:00 - NADER - - 2004-12-17T09:30:47-05:00 - - P10M - PLACE98765 - 20 - - - + + + + + + + en + P1Y2M3DT10H30M + P1Y2M3DT10H30M + direct + true + false + + + 2004-12-17T09:30:47-05:00 + NADER + + 2004-12-17T09:30:47-05:00 + + P10M + PLACE98765 + 20 + + + diff --git a/examples/siri_exm_FM/exf_facilityMonitoring_response.xml b/examples/siri_exm_FM/exf_facilityMonitoring_response.xml index 5d440298..c6433f64 100644 --- a/examples/siri_exm_FM/exf_facilityMonitoring_response.xml +++ b/examples/siri_exm_FM/exf_facilityMonitoring_response.xml @@ -1,95 +1,95 @@ - - - - - - 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 - - - - - + + + + + + 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/examples/siri_exm_FM/exf_facilityMonitoring_subscriptionRequest.xml b/examples/siri_exm_FM/exf_facilityMonitoring_subscriptionRequest.xml index 6395c0a4..7f073bab 100644 --- a/examples/siri_exm_FM/exf_facilityMonitoring_subscriptionRequest.xml +++ b/examples/siri_exm_FM/exf_facilityMonitoring_subscriptionRequest.xml @@ -1,38 +1,38 @@ - - - - - 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 - - - + + + + + 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 + + + diff --git a/examples/siri_exm_GM/exm_generalMessage_capabilityResponse.xml b/examples/siri_exm_GM/exm_generalMessage_capabilityResponse.xml index b6160d2b..be81c2da 100644 --- a/examples/siri_exm_GM/exm_generalMessage_capabilityResponse.xml +++ b/examples/siri_exm_GM/exm_generalMessage_capabilityResponse.xml @@ -1,67 +1,67 @@ - - - - 2001-12-17T09:30:47-05:00 - http://www.mytransportco.eu - true - - - cpidId001 - - String - - - - - true - true - - - true - false - - true - true - false - false - - - PT60M - true - - - en-uk - - - - false - true - - - - - - - - true - true - - - true - - - - - - NADER - - - false - EMERGENCY - - - - - - - + + + + 2001-12-17T09:30:47-05:00 + http://www.mytransportco.eu + true + + + cpidId001 + + String + + + + + true + true + + + true + false + + true + true + false + false + + + PT60M + true + + + en-uk + + + + false + true + + + + + + + + true + true + + + true + + + + + + NADER + + + false + EMERGENCY + + + + + + + diff --git a/examples/siri_exm_GM/exm_generalMessage_request.xml b/examples/siri_exm_GM/exm_generalMessage_request.xml index 74bd4ce5..ae11f8e6 100644 --- a/examples/siri_exm_GM/exm_generalMessage_request.xml +++ b/examples/siri_exm_GM/exm_generalMessage_request.xml @@ -1,24 +1,24 @@ - - - - - - - en - P1Y2M3DT10H30M - P1Y2M3DT10H30M - direct - true - false - - - 2004-12-17T09:30:47-05:00 - NADER - - 2004-12-17T09:30:47-05:00 - - WARNING - - - - + + + + + + + en + P1Y2M3DT10H30M + P1Y2M3DT10H30M + direct + true + false + + + 2004-12-17T09:30:47-05:00 + NADER + + 2004-12-17T09:30:47-05:00 + + WARNING + + + + diff --git a/examples/siri_exm_GM/exm_generalMessage_response.xml b/examples/siri_exm_GM/exm_generalMessage_response.xml index c29fbe23..8d31814f 100644 --- a/examples/siri_exm_GM/exm_generalMessage_response.xml +++ b/examples/siri_exm_GM/exm_generalMessage_response.xml @@ -1,30 +1,30 @@ - - - - - - 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 - - - - + + + + + + 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/examples/siri_exm_GM/exm_generalMessage_response_embed.xml b/examples/siri_exm_GM/exm_generalMessage_response_embed.xml index 5a8f1ed6..6b5b61f2 100644 --- a/examples/siri_exm_GM/exm_generalMessage_response_embed.xml +++ b/examples/siri_exm_GM/exm_generalMessage_response_embed.xml @@ -1,65 +1,65 @@ - - - - - - 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 - - - - - - - - - - - + + + + + + 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/examples/siri_exm_GM/exm_generalMessage_subscriptionRequest.xml b/examples/siri_exm_GM/exm_generalMessage_subscriptionRequest.xml index 4abf3776..1cacc293 100644 --- a/examples/siri_exm_GM/exm_generalMessage_subscriptionRequest.xml +++ b/examples/siri_exm_GM/exm_generalMessage_subscriptionRequest.xml @@ -1,19 +1,19 @@ - - - - - 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 - - - - + + + + + 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 + + + + diff --git a/examples/siri_exm_PT/ext_productionTimetable_capabilitiesResponse.xml b/examples/siri_exm_PT/ext_productionTimetable_capabilitiesResponse.xml index e30dc4aa..409aa54c 100644 --- a/examples/siri_exm_PT/ext_productionTimetable_capabilitiesResponse.xml +++ b/examples/siri_exm_PT/ext_productionTimetable_capabilitiesResponse.xml @@ -1,70 +1,70 @@ - - - - 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 - - - - - - + + + + 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/examples/siri_exm_PT/ext_productionTimetable_request.xml b/examples/siri_exm_PT/ext_productionTimetable_request.xml index 061c28b8..bc863c82 100644 --- a/examples/siri_exm_PT/ext_productionTimetable_request.xml +++ b/examples/siri_exm_PT/ext_productionTimetable_request.xml @@ -1,24 +1,24 @@ - - - - - - 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 - - - - - + + + + + + 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/examples/siri_exm_PT/ext_productionTimetable_response.xml b/examples/siri_exm_PT/ext_productionTimetable_response.xml index 9b12116b..31373fe1 100644 --- a/examples/siri_exm_PT/ext_productionTimetable_response.xml +++ b/examples/siri_exm_PT/ext_productionTimetable_response.xml @@ -1,113 +1,113 @@ - - - - - - 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 - - - - - - - - + + + + + + 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/examples/siri_exm_PT/ext_productionTimetable_subscriptionRequest.xml b/examples/siri_exm_PT/ext_productionTimetable_subscriptionRequest.xml index ddab7cb7..14a4951c 100644 --- a/examples/siri_exm_PT/ext_productionTimetable_subscriptionRequest.xml +++ b/examples/siri_exm_PT/ext_productionTimetable_subscriptionRequest.xml @@ -1,30 +1,30 @@ - - - - - - 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 - - - - - - + + + + + + 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/examples/siri_exm_SM/exp_stopMonitoring_permissions.xml b/examples/siri_exm_SM/exp_stopMonitoring_permissions.xml index 0bc6d396..46250ea3 100644 --- a/examples/siri_exm_SM/exp_stopMonitoring_permissions.xml +++ b/examples/siri_exm_SM/exp_stopMonitoring_permissions.xml @@ -1,76 +1,76 @@ - - - - - - - - true - false - - - true - - - - - false - A1 - - - - - false - Bar - - - - - - NADER - - true - true - - - true - - - - true - A1 - Foo - - - - - false - Bar - - - - - - Va - - true - true - - - true - - - true - - - - false - Bar - - - - + + + + + + + + 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/examples/siri_exm_SM/exs_stopMonitoring_capabilitiesResponse.xml b/examples/siri_exm_SM/exs_stopMonitoring_capabilitiesResponse.xml index 23e0d5ec..ac5d8c08 100644 --- a/examples/siri_exm_SM/exs_stopMonitoring_capabilitiesResponse.xml +++ b/examples/siri_exm_SM/exs_stopMonitoring_capabilitiesResponse.xml @@ -1,109 +1,109 @@ - - - - 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 - - - - + + + + 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 + + + + diff --git a/examples/siri_exm_SM/exs_stopMonitoring_request.xml b/examples/siri_exm_SM/exs_stopMonitoring_request.xml index 5635dbb1..b7d9c79f 100644 --- a/examples/siri_exm_SM/exs_stopMonitoring_request.xml +++ b/examples/siri_exm_SM/exs_stopMonitoring_request.xml @@ -1,45 +1,45 @@ - - - - - - - en - P1Y2M3DT10H30M - P1Y2M3DT10H30M - direct - true - false - - - 2004-12-17T09:30:47-05:00 - MONTECHRISTO - 2B|~2B - NADER - - 2004-12-17T09:30:47-05:00 - - - P10M - EH00001 - OPERATOR22 - LINE77 - OUTBOUND - PLACE98765 - all - - true - 7 - 2 - 20 - calls - true - - - + + + + + + + en + P1Y2M3DT10H30M + P1Y2M3DT10H30M + direct + true + false + + + 2004-12-17T09:30:47-05:00 + MONTECHRISTO + 2B|~2B + NADER + + 2004-12-17T09:30:47-05:00 + + + P10M + EH00001 + OPERATOR22 + LINE77 + OUTBOUND + PLACE98765 + all + + true + 7 + 2 + 20 + calls + true + + + diff --git a/examples/siri_exm_SM/exs_stopMonitoring_request_simple.xml b/examples/siri_exm_SM/exs_stopMonitoring_request_simple.xml index 3177540a..163d8b59 100644 --- a/examples/siri_exm_SM/exs_stopMonitoring_request_simple.xml +++ b/examples/siri_exm_SM/exs_stopMonitoring_request_simple.xml @@ -1,17 +1,17 @@ - - - - - 2004-12-17T09:30:47-05:00 - NADER - - 2004-12-17T09:30:47-05:00 - - EH00001 - - - + + + + + 2004-12-17T09:30:47-05:00 + NADER + + 2004-12-17T09:30:47-05:00 + + EH00001 + + + diff --git a/examples/siri_exm_SM/exs_stopMonitoring_response.xml b/examples/siri_exm_SM/exs_stopMonitoring_response.xml index 4dc65be6..92b3eb54 100644 --- a/examples/siri_exm_SM/exs_stopMonitoring_response.xml +++ b/examples/siri_exm_SM/exs_stopMonitoring_response.xml @@ -1,281 +1,281 @@ - - - - - - 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 - HLTST011 - British Museum Stop A - - - 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 - Boris Special - - Kensall Green - - true - false - false - false - reliable - - 180 - 90 - - 23 - 22 - seatsAvailable - 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 - - - true - - 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 - HLTST011 - 123 - Out - What, will the line stretch out to the crack of doom? - - - - 2004-12-17T09:30:47-05:00 - SED9843214675429 - HLTST011 - 123 - Out - - Hello Stop - - - + + + + + + 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 + HLTST011 + British Museum Stop A + + + 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 + Boris Special + + Kensall Green + + true + false + false + false + reliable + + 180 + 90 + + 23 + 22 + seatsAvailable + 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 + + + true + + 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 + HLTST011 + 123 + Out + What, will the line stretch out to the crack of doom? + + + + 2004-12-17T09:30:47-05:00 + SED9843214675429 + HLTST011 + 123 + Out + + Hello Stop + + + diff --git a/examples/siri_exm_SM/exs_stopMonitoring_response_complex.xml b/examples/siri_exm_SM/exs_stopMonitoring_response_complex.xml index 8fe9e6dc..94fac0ef 100644 --- a/examples/siri_exm_SM/exs_stopMonitoring_response_complex.xml +++ b/examples/siri_exm_SM/exs_stopMonitoring_response_complex.xml @@ -1,341 +1,341 @@ - - - - - - 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 - HLTST011 - British Museum Stop A - Musee Britannique Halte A - - - 2004-12-17T09:25:46-05:00 - - SED9843214675432 - 2004-12-17T10:25:46-05:00 - HLTST011 - CLR7654 - - - Line123 - Out - - 2004-12-17 - Oubound - - - 123 - - OP22 - PDCATEXPRESS - SERVCCAT551 - - PLACE21 - Highbury - - Kensall Green - - - Roman Road - - PLACE45 - Paradise Park - Parc du Paradis - Boris Special - - Kensall Green - - true - false - false - false - reliable - - 180 - 90 - - 23 - 22 - seatsAvailable - PT2M - Service running on time - inProgress - - - 1 - 3456 - 1 - - BLOCK765 - RUN765 - VEH987654 - DRV654 - N.I.Blick - - - - HLT0010 - 2 - Town Hall - Hotel de Ville - false - 2004-12-17T09:32:43-05:00 - 2004-12-17T09:32:43-05:00 - - - - 0014 - - true - - 180 - 90 - - - 2004-12-17T09:40:46-05:00 - 2004-12-17T09:40:46-05:00 - arrived - 2004-12-17T09:42:47-05:00 - 2004-12-17T09:40:47-05:00 - - arrived - Bay 5 - - - - - HLTST012 - 4 - Church - Eglise - 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 - - - true - - Hello bus for line 123 ! - Shelter - - - - 2004-12-17T09:25:46-06:00 - - SED9843214675434 - - - - Line128 - Inbound - - 2004-12-17 - ABC576 - - Rt24 - - 24 - To Library - Line128 - - OP22 - PDCATEXPRESS - SERVCCAT551 - 444 - 446 - - PLACE4675 - Chancery Lane - - Picadilly Green - - PLACE1245 - Paradise Park - - Accessiblity help available from driver - - 02134567 - - - true - 2004-12-17T09:30:42-00:00 - 2004-12-17T10:12:47-05:00 - otherService - - - - Low - Low Floo vehicler - notAvailable - - - false - palletAccess_lowFloor - - - - true - false - false - true - abcd - reliable - - 53 - 0.1 - - -PT2M - Running Early - - BLOCK6765 - RUN7865 - VEH9876555 - - - - HLT0107 - 002 - Library - false - 2004-12-17T09:30:42-00:00 - 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 - 2004-12-17T09:55:47-05:00 - - reliable - 0.9 - 2004-12-17T09:55:47-05:00 - 2004-12-17T09:58:47-05:00 - - 2004-12-17T09:55:47-05:00 - onTime - Approaching stop - 2 - PT10M - PT11M - 750 - 1 - - - HLTST113 - 0013 - Starbucks - false - 2004-12-17T10:07:47-05:00 - 2004-12-17T10:09:47-05:00 - 2000 - 2 - - - HLTST114 - 0014 - Station - false - 2004-12-17T10:12:47-05:00 - onTime - 2 - 4000 - 3 - - - - 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 - HLTST011 - 123 - Out - What, will the line stretch out to the crack of doom? - - - - 2004-12-17T09:30:47-05:00 - SED9843214675429 - HLTST011 - 123 - Out - - Hello Stop - - - + + + + + + 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 + HLTST011 + British Museum Stop A + Musee Britannique Halte A + + + 2004-12-17T09:25:46-05:00 + + SED9843214675432 + 2004-12-17T10:25:46-05:00 + HLTST011 + CLR7654 + + + Line123 + Out + + 2004-12-17 + Oubound + + + 123 + + OP22 + PDCATEXPRESS + SERVCCAT551 + + PLACE21 + Highbury + + Kensall Green + + + Roman Road + + PLACE45 + Paradise Park + Parc du Paradis + Boris Special + + Kensall Green + + true + false + false + false + reliable + + 180 + 90 + + 23 + 22 + seatsAvailable + PT2M + Service running on time + inProgress + + + 1 + 3456 + 1 + + BLOCK765 + RUN765 + VEH987654 + DRV654 + N.I.Blick + + + + HLT0010 + 2 + Town Hall + Hotel de Ville + false + 2004-12-17T09:32:43-05:00 + 2004-12-17T09:32:43-05:00 + + + + 0014 + + true + + 180 + 90 + + + 2004-12-17T09:40:46-05:00 + 2004-12-17T09:40:46-05:00 + arrived + 2004-12-17T09:42:47-05:00 + 2004-12-17T09:40:47-05:00 + + arrived + Bay 5 + + + + + HLTST012 + 4 + Church + Eglise + 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 + + + true + + Hello bus for line 123 ! + Shelter + + + + 2004-12-17T09:25:46-06:00 + + SED9843214675434 + + + + Line128 + Inbound + + 2004-12-17 + ABC576 + + Rt24 + + 24 + To Library + Line128 + + OP22 + PDCATEXPRESS + SERVCCAT551 + 444 + 446 + + PLACE4675 + Chancery Lane + + Picadilly Green + + PLACE1245 + Paradise Park + + Accessiblity help available from driver + + 02134567 + + + true + 2004-12-17T09:30:42-00:00 + 2004-12-17T10:12:47-05:00 + otherService + + + + Low + Low Floo vehicler + notAvailable + + + false + palletAccess_lowFloor + + + + true + false + false + true + abcd + reliable + + 53 + 0.1 + + -PT2M + Running Early + + BLOCK6765 + RUN7865 + VEH9876555 + + + + HLT0107 + 002 + Library + false + 2004-12-17T09:30:42-00:00 + 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 + 2004-12-17T09:55:47-05:00 + + reliable + 0.9 + 2004-12-17T09:55:47-05:00 + 2004-12-17T09:58:47-05:00 + + 2004-12-17T09:55:47-05:00 + onTime + Approaching stop + 2 + PT10M + PT11M + 750 + 1 + + + HLTST113 + 0013 + Starbucks + false + 2004-12-17T10:07:47-05:00 + 2004-12-17T10:09:47-05:00 + 2000 + 2 + + + HLTST114 + 0014 + Station + false + 2004-12-17T10:12:47-05:00 + onTime + 2 + 4000 + 3 + + + + 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 + HLTST011 + 123 + Out + What, will the line stretch out to the crack of doom? + + + + 2004-12-17T09:30:47-05:00 + SED9843214675429 + HLTST011 + 123 + Out + + Hello Stop + + + diff --git a/examples/siri_exm_SM/exs_stopMonitoring_response_simple.xml b/examples/siri_exm_SM/exs_stopMonitoring_response_simple.xml index a2b72ff4..27bc59b9 100644 --- a/examples/siri_exm_SM/exs_stopMonitoring_response_simple.xml +++ b/examples/siri_exm_SM/exs_stopMonitoring_response_simple.xml @@ -1,57 +1,57 @@ - - - - - - 2004-12-17T09:30:46-05:00 - KUBRICK - true - - - 2004-12-17T09:30:47-05:00 - NADER - 2004-12-17T09:30:47-05:00 - HLTST011 - - - 2004-12-17T09:25:46-05:00 - HLTST011 - - 123 - OP22 - Paradise Park - Service running on time - - 2004-12-17T09:42:47-05:00 - 2004-12-17T09:40:47-05:00 - - - - - 2004-12-17T09:25:46-06:00 - HLTST011 - - 128 - Running Early - - true - 2004-12-17T09:42:41-05:00 - 2004-12-17T09:40:41-05:00 - onTime - - - - - 2004-12-17T09:30:47-05:00 - HLTST011 - 123 - Out - Happy Easter to all our customers!? - - - - + + + + + + 2004-12-17T09:30:46-05:00 + KUBRICK + true + + + 2004-12-17T09:30:47-05:00 + NADER + 2004-12-17T09:30:47-05:00 + HLTST011 + + + 2004-12-17T09:25:46-05:00 + HLTST011 + + 123 + OP22 + Paradise Park + Service running on time + + 2004-12-17T09:42:47-05:00 + 2004-12-17T09:40:47-05:00 + + + + + 2004-12-17T09:25:46-06:00 + HLTST011 + + 128 + Running Early + + true + 2004-12-17T09:42:41-05:00 + 2004-12-17T09:40:41-05:00 + onTime + + + + + 2004-12-17T09:30:47-05:00 + HLTST011 + 123 + Out + Happy Easter to all our customers!? + + + + diff --git a/examples/siri_exm_SM/exs_stopMonitoring_subscriptionRequest.xml b/examples/siri_exm_SM/exs_stopMonitoring_subscriptionRequest.xml index b74658e9..8dc3e7c3 100644 --- a/examples/siri_exm_SM/exs_stopMonitoring_subscriptionRequest.xml +++ b/examples/siri_exm_SM/exs_stopMonitoring_subscriptionRequest.xml @@ -1,65 +1,65 @@ - - - - - 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 - - - + + + + + 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 + + + diff --git a/examples/siri_exm_SM/exs_stopMonitoring_subscriptionRequest_simple.xml b/examples/siri_exm_SM/exs_stopMonitoring_subscriptionRequest_simple.xml index 31fea846..b5896366 100644 --- a/examples/siri_exm_SM/exs_stopMonitoring_subscriptionRequest_simple.xml +++ b/examples/siri_exm_SM/exs_stopMonitoring_subscriptionRequest_simple.xml @@ -1,26 +1,26 @@ - - - - - 2004-12-17T09:30:47-05:00 - NADER - - NADER - 000234 - 2004-12-17T09:30:47-05:00 - - 2004-12-17T15:30:47-05:00 - POIT5678 - normal - - false - PT2M - - - + + + + + 2004-12-17T09:30:47-05:00 + NADER + + NADER + 000234 + 2004-12-17T09:30:47-05:00 + + 2004-12-17T15:30:47-05:00 + POIT5678 + normal + + false + PT2M + + + diff --git a/examples/siri_exm_ST/exs_stopTimetable_capabilitiesResponse.xml b/examples/siri_exm_ST/exs_stopTimetable_capabilitiesResponse.xml index da1fe67a..78963a49 100644 --- a/examples/siri_exm_ST/exs_stopTimetable_capabilitiesResponse.xml +++ b/examples/siri_exm_ST/exs_stopTimetable_capabilitiesResponse.xml @@ -1,83 +1,83 @@ - - - - 2001-12-17T09:30:47-05:00 - http://www.mytransportco.eu - true - - - cpidId001 - - Capability supported - - - - - 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 - - - - + + + + 2001-12-17T09:30:47-05:00 + http://www.mytransportco.eu + true + + + cpidId001 + + Capability supported + + + + + 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 + + + + diff --git a/examples/siri_exm_ST/exs_stopTimetable_request.xml b/examples/siri_exm_ST/exs_stopTimetable_request.xml index 2cb11d21..c912fc3c 100644 --- a/examples/siri_exm_ST/exs_stopTimetable_request.xml +++ b/examples/siri_exm_ST/exs_stopTimetable_request.xml @@ -1,23 +1,23 @@ - - - - - - 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 - - - + + + + + + 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 + + + diff --git a/examples/siri_exm_ST/exs_stopTimetable_response.xml b/examples/siri_exm_ST/exs_stopTimetable_response.xml index eb1a8ced..424b47dd 100644 --- a/examples/siri_exm_ST/exs_stopTimetable_response.xml +++ b/examples/siri_exm_ST/exs_stopTimetable_response.xml @@ -1,47 +1,47 @@ - - - - - - 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 - - - - - - - + + + + + + 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 + + + + + + + diff --git a/examples/siri_exm_ST/exs_stopTimetable_subscriptionRequest.xml b/examples/siri_exm_ST/exs_stopTimetable_subscriptionRequest.xml index b178fd04..4e15a7f9 100644 --- a/examples/siri_exm_ST/exs_stopTimetable_subscriptionRequest.xml +++ b/examples/siri_exm_ST/exs_stopTimetable_subscriptionRequest.xml @@ -1,26 +1,26 @@ - - - - - 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 - - - - + + + + + 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 + + + + diff --git a/examples/siri_exm_SX/VDV736_exm/SX_1010_first_message.xml b/examples/siri_exm_SX/VDV736_exm/SX_1010_first_message.xml index 15e3f0de..18dc5f39 100644 --- a/examples/siri_exm_SX/VDV736_exm/SX_1010_first_message.xml +++ b/examples/siri_exm_SX/VDV736_exm/SX_1010_first_message.xml @@ -1,254 +1,254 @@ - - - - 2018-10-04T10:11:00+00:00 - ch:VBL -
      http:/server/siri/20_ums
      - t3xWB5cY3 - true - false - - 2018-10-04T10:11:00+00:00 - ch:VBL - 40599x2dsjmu8yjzy - - - 2017-05-28T10:10:00+02:00 - VBL - 5a7cf4f0-c7a5-11e8-813f-f38697968b53 - 1 - - feed - VBL - - published - - 2017-05-04T10:10:00+02:00 - 2017-05-28T17:10:00+02:00 - - fire - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - 3 - line - false - DE - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - - - ch:vbl:622 - Haldensteig - - - - - - disruption - - - - - ch:vbl:VBL006 - 6 - - - ch:vbl:VBL008 - 8 - - - ch:vbl:VBL024 - 24 - - - - - - - false - - - - - - - line - - - - - ch:vbl:VBL006 - 6 - - - ch:vbl:VBL008 - 8 - - - ch:vbl:VBL024 - 24 - - - ch:pb:PB073 - 73 - - - - - - - open - 0010 - 2017-05-28T10:10:00+02:00 - VBL - VBL - general - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Betroffen sind die Linien 6, 8, 24 und 73 - Affected lines are 6, 8, 24 and 73 - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - Es muss mit Verspätungen, Ausfällen und Umleitungen gerechnet werden. Wir werden sie rasch möglichst detaillierter informieren. - Expect delays, cancellations and diversions. More details to come soon. - - - - - - - line - - - - - ch:vbl:VBL006 - 6 - - - ch:vbl:VBL008 - 8 - - - ch:vbl:VBL024 - 24 - - - ch:pb:PB073 - 73 - - - - - - - open - 0010 - 2017-05-28T10:10:00+02:00 - VBL - VBL - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Betroffen sind die Linien 6, 8, 24 und 73 - Affected lines are 6, 8, 24 and 73 - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - Es muss mit Verspätungen, Ausfällen und Umleitungen gerechnet werden. Wir werden sie rasch möglichst detaillierter informieren. - Expect delays, cancellations and diversions. More details to come soon. - - - - - - - line - - - - - ch:vbl:VBL006 - 6 - - - ch:vbl:VBL008 - 8 - - - ch:vbl:VBL024 - 24 - - - ch:pb:PB073 - 73 - - - - - - - open - 0010 - 2017-05-28T10:10:00+02:00 - VBL - VBL - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Betroffen sind die Linien 6, 8, 24 und 73 - Affected lines are 6, 8, 24 and 73 - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - Es muss mit Verspätungen, Ausfällen und Umleitungen gerechnet werden. Wir werden sie rasch möglichst detaillierter informieren. - Expect delays, cancellations and diversions. More details to come soon. - - - - - - - - -       -       + + + + 2018-10-04T10:11:00+00:00 + ch:VBL +
      http:/server/siri/20_ums
      + t3xWB5cY3 + true + false + + 2018-10-04T10:11:00+00:00 + ch:VBL + 40599x2dsjmu8yjzy + + + 2017-05-28T10:10:00+02:00 + VBL + 5a7cf4f0-c7a5-11e8-813f-f38697968b53 + 1 + + feed + VBL + + published + + 2017-05-04T10:10:00+02:00 + 2017-05-28T17:10:00+02:00 + + fire + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + 3 + line + false + DE + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + + + ch:vbl:622 + Haldensteig + + + + + + disruption + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 24 + + + + + + + false + + + + + + + line + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 24 + + + ch:pb:PB073 + 73 + + + + + + + open + 0010 + 2017-05-28T10:10:00+02:00 + VBL + VBL + general + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Betroffen sind die Linien 6, 8, 24 und 73 + Affected lines are 6, 8, 24 and 73 + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + Es muss mit Verspätungen, Ausfällen und Umleitungen gerechnet werden. Wir werden sie rasch möglichst detaillierter informieren. + Expect delays, cancellations and diversions. More details to come soon. + + + + + + + line + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 24 + + + ch:pb:PB073 + 73 + + + + + + + open + 0010 + 2017-05-28T10:10:00+02:00 + VBL + VBL + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Betroffen sind die Linien 6, 8, 24 und 73 + Affected lines are 6, 8, 24 and 73 + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + Es muss mit Verspätungen, Ausfällen und Umleitungen gerechnet werden. Wir werden sie rasch möglichst detaillierter informieren. + Expect delays, cancellations and diversions. More details to come soon. + + + + + + + line + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 24 + + + ch:pb:PB073 + 73 + + + + + + + open + 0010 + 2017-05-28T10:10:00+02:00 + VBL + VBL + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Betroffen sind die Linien 6, 8, 24 und 73 + Affected lines are 6, 8, 24 and 73 + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + Es muss mit Verspätungen, Ausfällen und Umleitungen gerechnet werden. Wir werden sie rasch möglichst detaillierter informieren. + Expect delays, cancellations and diversions. More details to come soon. + + + + + + + + +       +       diff --git a/examples/siri_exm_SX/VDV736_exm/SX_1022_main_message.xml b/examples/siri_exm_SX/VDV736_exm/SX_1022_main_message.xml index 5c5cd448..fb0f9892 100644 --- a/examples/siri_exm_SX/VDV736_exm/SX_1022_main_message.xml +++ b/examples/siri_exm_SX/VDV736_exm/SX_1022_main_message.xml @@ -1,2311 +1,2311 @@ - - - - 2018-10-16T10:22:30+00:00 - ch:VBL -
      http:/server/siri/20_ums
      - Pgfkw0GAsg - true - false - - 2018-10-16T10:22:30+00:00 - ch:VBL - 40599x2dsjmu8yjzy - - - 2017-05-28T10:22:00+02:00 - VBL - 5a7cf4f0-c7a5-11e8-813f-f38697968b53 - 2 - - feed - VBL - - published - - 2017-05-28T10:10:00+02:00 - 2017-05-28T17:10:00+02:00 - - fire - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - 3 - route - DE - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - http://www.vbl.ch/aktuelles/verkehrsmeldungen/stoerungen/20160603_13? - - - - - - - - ch:vbl:622 - Haldensteig - - - - - - disruption - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:2507::01 - Büttenhalde - - - ch:vbl:VBL006:A - Büttenhalde - - - - ch:vbl:621::01 - Casino-Palace - affectedStopplace - - - ch:vbl:615::01 - Europe - affectedStopplace - - - ch:vbl:616::01 - Dietschiberg - affectedStopplace - - - ch:vbl:617::01 - Verkehrshaus - affectedStopplace - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:601:01 - Matthof - - - ch:vbl:VBL006:B - Matthof - - - - ch:vbl:617::02 - Verkehrshaus - affectedStopplace - - - ch:vbl:616::02 - Dietschiberg - affectedStopplace - - - ch:vbl:615::02 - Europe - affectedStopplace - - - ch:vbl:621::02 - Casino-Palace - affectedStopplace - - - ch:vbl:622::02 - Haldensteig - affectedStopplace - - - - - ch:vbl:VBL008 - 8 - - ch:vbl:620:01 - Würzenbach - - - ch:vbl:VBL008:A - Würzenbach - - - - ch:vbl:621::01 - Casino-Palace - affectedStopplace - - - ch:vbl:615::01 - Europe - affectedStopplace - - - ch:vbl:616::01 - Dietschiberg - affectedStopplace - - - ch:vbl:617::01 - Verkehrshaus - affectedStopplace - - - - - ch:vbl:VBL008 - 8 - - ch:vbl:801:01 - Hirtenhof - - - ch:vbl:VBL008:B - Hirtenhof - - - - ch:vbl:617::02 - Verkehrshaus - affectedStopplace - - - ch:vbl:616::02 - Dietschiberg - affectedStopplace - - - ch:vbl:615::02 - Europe - affectedStopplace - - - ch:vbl:621::02 - Casino-Palace - affectedStopplace - - - ch:vbl:622::02 - Haldensteig - affectedStopplace - - - - - - - - true - true - - - - diverted - - - - - ch:vbl:VBL024 - 24 - - ch:vbl:2433:01 - Tschädigen - - - ch:vbl:VBL024:A - Tschädigen - - - - ch:vbl:121::02 - affectedStopplace - - - ch:vbl:621::01 - Casino-Palace - affectedStopplace - - - ch:vbl:617::01 - Verkehrshaus - affectedStopplace - - - ch:vbl:715::01 - intermediate - - - ch:vbl:716::01 - intermediate - - - ch:vbl:1405::01 - intermediate - - - ch:vbl:1406::01 - intermediate - - - ch:vbl:1407::01 - intermediate - - - ch:vbl:1408::01 - intermediate - - - ch:vbl:1409::01 - intermediate - - - ch:vbl:1410::01 - intermediate - - - ch:vbl:1411::01 - intermediate - - - ch:vbl:1412::01 - intermediate - - - - - ch:vbl:VBL024 - 24 - - ch:vbl:119:13 - Bahnhof - - - ch:vbl:VBL024:B - Bahnhof - - - - ch:vbl:617::02 - Verkehrshaus - affectedStopplace - - - ch:vbl:621::02 - affectedStopplace - - - ch:vbl:622::02 - affectedStopplace - - - ch:vbl:1412::02 - intermediate - - - ch:vbl:1411::02 - intermediate - - - ch:vbl:1410::02 - intermediate - - - ch:vbl:1409::02 - intermediate - - - ch:vbl:1408::02 - intermediate - - - ch:vbl:1407::02 - intermediate - - - ch:vbl:1406::02 - intermediate - - - ch:vbl:1405::02 - intermediate - - - ch:vbl:716::02 - intermediate - - - ch:vbl:715::01 - intermediate - - - - - - - - true - true - - - PT7M - - - - - - - line - - - - - ch:vbl:VBL006 - 6 - - - ch:vbl:VBL008 - 8 - - - ch:vbl:VBL024 - 24 - - - ch:pb:PB073 - 73 - - - - - - - open - 0020 - 2017-05-28T10:22:00+02:00 - 1 - vbl - general - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Betroffen sind die Linien 6,8, 24 und 73 - Affected lines are 6, 8, 24 and 73 - - - Linie 6 und 8 fallen zwischen Luzernerhof und Brüelstrasse aus. - Linie 24 wird zwischen Luzernerhof und Brüelstrasse via St. Anna umgeleitet. Ca. 7 Min. längere Fahrzeit. - Linie 73 wird zwischen Luzernerhof und Brüelstrasse via St. Anna umgeleitet. Ca. 6 Min. längere Fahrzeit. - Line 6 and 8 disrupted Luzernerhof and Brüelstrasse. - Line 24 diverted between Luzernerhof and Brüelstrasse via St. Anna. Approx. 7 min delay. - Line 73 diverted between Luzernerhof and Brüelstrasse via St. Anna. Approx. 6 min delay. - - - Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. - Zwischen Luzern, Bahnhof und Verkehrshaus benutzen sie die S3 oder das Schiff. - Umstiegsempfehlung für die Linien 6 und 8: Bei den Haltestellen Luzernerhof bzw. Brüelstrasse auf die umgeleiteten Linien 24 und 73, die normal verkehrende Linie 14 oder den Entlastungsbus umsteigen. - Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. - Between Luzern, Bahnhof and Verkehrshaus use the S3 or ferry. - Transfer advice for line 6 and 8: At Luzernerhof or Brüelstrasse use diverted line 24, 73, additional buses or the regular line 14 services. - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:A - Büttenenhalde - - - - ch:vbl:601::01 - Matthof - - - ch:vbl:602::01 - Schönbühl - - - ch:vbl:603::03 - Wartegg - - - ch:vbl:604::01 - Eisfeldstrasse - - - ch:vbl:605::01 - Weinbergli - - - ch:vbl:606::01 - Werkhofstrasse - - - ch:vbl:407::02 - Bundesplatz - - - ch:vbl:118::01 - Kantonalbank (C) - - - ch:vbl:119::02 - Bahnhof (B) - - - ch:vbl:120:01 - Schwanenplatz - - - - - - - - - open - 0030 - 2017-05-28T10:22:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Die Linie 6 fällt zwischen Luzernerhof und Brüelstrasse aus. - Line 6 cancelled between Luzernerhof and Brüelstrasse. - - - Reisende nach Brüelstrasse und weiter benützen die umgeleitete Linie 24 und 73 (ohne Halte zwischen Wey und Brühlstrasse) oder die normal verkehrende Linie 14 (mit Halten) und steigen an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. - Travellers to Brüelstrasse or further use the diverted line 24, 73 (direct between Wey and Brühlstrasse) or the regular line 14 services (all stop) and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - - - open - 0040 - 2017-05-28T10:22:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Die Linie 6 fällt zwischen Luzernerhof und Brüelstrasse aus. - Line 6 cancelled between Luzernerhof and Brüelstrasse. - - - Reisende nach Brüelstrasse und weiter benützen die umgeleitete Linie 24 und 73 (ohne Halte zwischen Wey und Brühlstrasse) oder die normal verkehrende Linie 14 (mit Halten) und steigen an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. - Travellers to Brüelstrasse or further use the diverted line 24, 73 (direct between Wey and Brühlstrasse) or the regular line 14 services (all stop) and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - Weitere Informationen erhalten Sie unter www.vbl.ch/stoerung/haldenstrasse - For further information, please visit www.vbl.ch/stoerung/haldenstrasse - - - www.vbl.ch/stoerung/haldenstrasse - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:A - Büttenenhalde - - - - ch:vbl:121::02 - Luzernerhof (D) - - - - - - - - - open - 0050 - 2017-05-28T10:22:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Linie 6 wendet hier - Line 6 turns here - - - Reisende zur Brühlstrasse und weiter benützen die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte zwischen Wey und Brühlstrasse) oder die normale verkehrende Linie 14 (mit Halten) ab Kante F (Wey) und steigen an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. - Travellers to Brüelstrasse or further use the diverted line 24, 73, additonal buses (direct between Wey and Brühlstrasse) or the regular line 14 services (all stop) from platform F (Wey) and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:A - Büttenenhalde - - - - ch:vbl:121::01 - Luzernerhof (C) - - - - - ch:vbl:VBL008 - 8 - - ch:vbl:VBL008:A - Würzenbach - - - - ch:vbl:121::01 - Luzernerhof (C) - - - - - - - - - open - 0060 - 2017-05-28T10:22:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Unterbruch der Linien 6 und 8 - Line 6 and 8 disrupted - - - Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die umgeleiteten Linien 24 und 73, die normal verkehrende Linie 14 oder den Entlastungsbus ab Kante F (Wey) und steigen Sie an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. - Transfer advice line 6 and 8: Use diverted line 24, 73, the regular line 14 services or the additional buses to Brüelstrasse and transfer back to line 6 and 8. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - Weitere Informationen erhalten Sie beim Auskunftspersonal. - For further information, please contact staff. - - - - - - - route - - - - - - ch:vbl:VBL014 - 14 - - ch:vbl:VBL014:A - Brüelstrasse - - - - ch:vbl:715::02 - Wey - - - - - ch:vbl:VBL024 - 24 - - ch:vbl:VBL024:A - Tschädingen - - - - ch:vbl:715::02 - Wey - - - - - ch:vbl:VBL073 - 73 - - - ch:vbl:715::02 - Wey - - - - - - - - - - open - 0070 - 2017-05-28T10:22:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Unterbruch der Linien 6 und 8; Umleitung der Linien 24 und 73 - Line 6 and 8 disrupted; Line 24 and 73 diverted - - - Benutzen Sie die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte bis Brühlstrasse) oder die normal verkehrende Linie 14 (mit Halten) bis Brüelstrasse. - Use the diverted line 24, 73, additional buses (direct to Brühlstrasse) or the regular line 14 services (all stops) to Brüelstrasse. - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:A - Büttenenhalde - - - - ch:vbl:121::02 - Luzernerhof (D) - - - - - ch:vbl:VBL008 - 8 - - ch:vbl:VBL008:A - Würzenbach - - - - ch:vbl:121::02 - Luzernerhof (D) - - - - - - - - - open - 0130 - 2017-05-28T10:22:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Linie 6 und 8 fallen bis Brüelstrasse aus. Linie 24 wird zwischen Luzernerhof und Brüelstrasse via St. Anna umgeleitet. Ca. 7 Min. längere Fahrzeit. Linie 73 wird zwischen Luzernerhof und Brüelstrasse via St. Anna umgeleitet. Ca. 6 Min. längere Fahrzeit. - Line 6 and 8 services cancelled to Brüelstrasse. Line 24 services diverted between Luzernerhof and Brüelstrasse via St. Anna. Approx. 7 min. delay. Line 73 services diverted between Luzernerhof and Brüelstrasse. Approx. 6 min delay. - - - Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte zwischen Wey und Brühlstrasse) oder die normale verkehrende Linie 14 (mit Halten) ab Kante F (Wey) und steigen Sie an der Brüelstrasse um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. - Transfer advice for line 6 and 8: To Brüelstrasse use diverted line 24, 73, additional buses (direct between Wey and Brühlstrasse) or the regular line 14 services (all stops) from platform F (Way) and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:A - Büttenenhalde - - - - ch:vbl:621::01 - Casino-Palace - - - ch:vbl:615::01 - Europe - - - ch:vbl:616::01 - Dietschiberg - - - ch:vbl:617::01 - Verkehrshaus - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:B - Matthof - - - - ch:vbl:617::02 - Verkehrshaus - - - ch:vbl:616::02 - Dietschiberg - - - ch:vbl:615::02 - Europe - - - ch:vbl:621::02 - Casino-Palace - - - ch:vbl:622::01 - Haldensteig - - - - - ch:vbl:VBL008 - 8 - - ch:vbl:VBL008:A - Würzenbach - - - - ch:vbl:621::01 - Casino-Palace - - - ch:vbl:615::01 - Europe - - - ch:vbl:616::01 - Dietschiberg - - - ch:vbl:617::01 - Verkehrshaus - - - - - ch:vbl:VBL008 - 8 - - ch:vbl:VBL008:B - Hirtenhof - - - - ch:vbl:617::02 - Verkehrshaus - - - ch:vbl:616::02 - Dietschiberg - - - ch:vbl:615::02 - Europe - - - ch:vbl:621::02 - Casino-Palace - - - ch:vbl:622::01 - Haldensteig - - - - - ch:vbl:VBL024 - 24 - - ch:vbl:VBL024:A - Tschädingen - - - - ch:vbl:621::01 - Casino-Palace - - - ch:vbl:615::01 - Europe - - - ch:vbl:616::01 - Dietschiberg - - - ch:vbl:617::01 - Verkehrshaus - - - - - ch:vbl:VBL024 - 24 - - ch:vbl:VBL024:B - Bahnhof - - - - ch:vbl:617::02 - Verkehrshaus - - - ch:vbl:616::02 - Dietschiberg - - - ch:vbl:615::02 - Europe - - - ch:vbl:621::02 - Casino-Palace - - - ch:vbl:622::01 - Haldensteig - - - - - ch:pb:PB073 - 73 - - - ch:vbl:621::01 - Casino-Palace - - - ch:vbl:615::01 - Europe - - - ch:vbl:616::01 - Dietschiberg - - - ch:vbl:617::01 - Verkehrshaus - - - ch:vbl:617::02 - Verkehrshaus - - - ch:vbl:616::02 - Dietschiberg - - - ch:vbl:615::02 - Europe - - - ch:vbl:621::02 - Casino-Palace - - - ch:vbl:622::01 - Haldensteig - - - - - - - - - open - 0140 - 2017-05-28T10:22:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Keine Bedienung der Linien 6, 8, 24 und 73 zwischen Luzernerhof und Brüelstrasse - No service for line 6, 8, 24 and 73 between Luzernerhof and Brüelstrasse - - - Reisende zwischen Luzernerhof und Brüelstrasse erreichen ihr Ziel nur zu Fuß. Ab Luzernerhof und Brüelstrasse verkehren die Linie auf den normalen Fahrwegen. - Travellers between Luzernerhof and Brüelstrasse can only reach their destination on foot. From Luzernerhof and Brüelstrasse lines will run on regular routes. - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - Fällt aus - Cancelled - - - - - - - route - - - - - ch:vbl:014 - 14 - - ch:vbl:VBL014:A - Brüelstrasse - - - - ch:vbl:618::01 - Brüelstrasse - destination - - - - - - - - - open - 0080 - 2017-05-28T10:22:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Einstieg der Linien 6 und 8 bei Kante C. Reisende nach Verkehrshaus und Dietschiberg erreichen ihr Ziel nur zu Fuß. - Board line 6 and 8 from platform C. Travellers to Verkehrshaus and Dietschiberg can only reach their destination on foot. - - - - - - - route - - - - - ch:vbl:024 - 24 - - ch:vbl:VBL024:A - Tschädingen - - - - ch:vbl:618::01 - Brüelstrasse - intermediate - - - - - ch:pb:073 - 73 - - ch:pb:PB073:A - Rotkreuz - - - - ch:vbl:618::04 - Brüelstrasse - destination - - - - - - - - - open - 0090 - 2017-05-28T10:22:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Die Umleitung endet hier - Diversion ends here - - - Umstieg auf Linie 6 und 8: Einstieg bei Kante C. Reisende nach Verkehrshaus und Dietschiberg erreichen ihr Ziel nur zu Fuß. - Transfer to line 6 and 8: Board from platform C. Travellers to Verkehrshaus and Dietschiberg can only reach their destination on foot. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:A - Büttenhalde - - - - ch:vbl:618::03 - Brüelstrasse - - - - - ch:vbl:VBL008 - 8 - - ch:vbl:VBL008:A - Würzenbach - - - - ch:vbl:618::03 - Brüelstrasse - - - - - - - - - open - 0100 - 2017-05-28T10:22:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Normale Bedienung der Linien 6 bis Büttenenhalde und 8 bis Würzenbach. - Regular line 6 services to Büttenenhalde and 8 to Würzenbach. - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - Es muss mit Verspätungen gerechnet werden. - Expect delays. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:A - Büttenhalde - - - - - ch:vbl:618::03 - Brüelstrasse(B) - - - ch:vbl:2502::01 - Giseli - intermediate - - - ch:vbl:2503::01 - Oberseeburg - intermediate - - - ch:vbl:2504::01 - Oberseeburghöhe - intermediate - - - ch:vbl:2505::01 - Eggen - intermediate - - - ch:vbl:2506::01 - Büttenen - intermediate - - - ch:vbl:2507::01 - Büttenenhalde - destination - - - - - ch:vbl:VBL008 - 8 - - ch:vbl:VBL008:A - Würzenbach - - - - - ch:vbl:618::03 - Brüelstrasse(B) - - - ch:vbl:619::01 - Würzenbachmatte - intermediate - - - ch:vbl:620::01 - Würzenbach - destination - - - - - - - - - open - 0110 - 2017-05-28T10:22:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - Es muss mit Verspätungen gerechnet werden. - Expect delays. - - - - - - - route - - - - - ch:vbl:Entlastungsbus - Entlastungsbus - - ch:vbl:VBL006:A - Büttenhalde - - - - ch:vbl:618::04 - Brüelstrasse - - - - - - - - - open - 0120 - 2017-05-28T10:22:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Diese Fahrt endet hier - This service terminates here - - - Einstieg der Linien 6 und 8 bei Kante C. Reisende nach Verkehrshaus und Dietschiberg erreichen ihr Ziel nur zu Fuß. - Board line 6 and 8 from platform C. Travellers to Verkehrshaus and Dietschiberg can only reach their destination on foot. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:B - Matthof - - - - ch:vbl:2507::01 - Büttenenhalde - origin - - - ch:vbl:2506::02 - Büttenen - intermediate - - - ch:vbl:2505::02 - Eggen - intermediate - - - ch:vbl:2504::02 - Oberseeburghöhe - intermediate - - - ch:vbl:2503::02 - Oberseeburg - intermediate - - - ch:vbl:2502::02 - Giseli - intermediate - - - - - - - - - open - 0150 - 2017-05-28T10:22:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Die Linie 6 fällt zwischen Brüelstrasse und Luzernerhof aus. - Line 6 cancelled between Brüelstrasse and Luzernerhof. - - - Reisende nach Luzernerhof oder weiter benützen die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte zwischen Brühlstrasse und Luzernerhof) oder die normal verkehrende Linie 14 (mit Halten) bis Luzernerhof und steigen dort wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. - Travellers to Luzernerhof or further use the diverted lines 24, 73 and the additional bus (direct between Brühlstrasse and Luzernerhof) or the regular line 14 services (all stop) to Luzernhof and transfer there. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:B - Matthof - - - - ch:vbl:2507::01 - Büttenenhalde - origin - - - ch:vbl:2506::02 - Büttenen - intermediate - - - ch:vbl:2505::02 - Eggen - intermediate - - - ch:vbl:2504::02 - Oberseeburghöhe - intermediate - - - ch:vbl:2503::02 - Oberseeburg - intermediate - - - ch:vbl:2502::02 - Giseli - intermediate - - - - - - - - - open - 0160 - 2017-05-28T10:22:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Die Linie 6 fällt zwischen Brüelstrasse und Luzernerhof aus. - Line 6 cancelled between Brüelstrasse and Luzernerhof. - - - Reisende nach Luzernerhof oder weiter benützen die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte zwischen Brühlstrasse und Luzernerhof) oder die normal verkehrende Linie 14 (mit Halten) bis Luzernerhof und steigen dort wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. - Travellers to Luzernerhof or further use the diverted lines 24, 73 and the additional bus (direct between Brühlstrasse and Luzernerhof) or the regular line 14 services (all stop) to Luzernhof and transfer there. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:B - Matthof - - - - ch:vbl:618::02 - Brüelstrasse - destination - - - - - - - - - open - 0170 - 2017-05-28T10:22:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Linie 6 wendet hier - Line 6 turns here - - - Reisende zum Luzernerhof oder weiter benützen die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte bis Luzernerhof) oder die normal verkehrende Linie 14 (mit Halten) ab Kante D und steigen beim Luzernerhof wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. - Travellers to Luzernerhof or further use the diverted lines 24, 73, addintionl buses (direct to Luzernerhof) or the regular line 14 services (all stops) from platform D and transfer back to line 6 and 8 at Luzernerhof. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:B - Matthof - - - - ch:vbl:618::02 - Brüelstrasse - destination - - - - - ch:vbl:VBL008 - 8 - - ch:vbl:VBL008:B - Hirtenhof - - - - ch:vbl:618::02 - Brüelstrasse - destination - - - - - - - - - open - 0180 - 2017-05-28T10:22:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Unterbruch der Linien 6 und 8 - Line 6 and 8 disrupted - - - Reisende zum Luzernerhof oder weiter benützen die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte bis Luzernerhof) oder die normal verkehrende Linie 14 (mit Halten) ab Kante D und steigen beim Luzernerhof wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. - Travellers to Luzernerhof or further use the diverted lines 24, 73, addintionl buses (direct to Luzernerhof) or the regular line 14 services (all stops) from platform D and transfer back to line 6 and 8 at Luzernerhof. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. - - - - - - - route - - - - - ch:vbl:VBL014 - 14 - - ch:vbl:VBL014:A - Brühlstrasse - - - - ch:vbl:618::04 - Brühlstrasse - destination - - - - - - - ch:vbl:VBL024 - 24 - - ch:vbl:VBL024:B - Bahnhof - - - - ch:vbl:618::04 - Brühlstrasse - destination - - - - - - - - - open - 0190 - 2017-05-28T10:22:00+02:00 - 1 - vbl - stopPoint - - L - - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Unterbruch der Linien 6 und 8; Umleitung der Linien 24 und 73. - Line 6 and 8 disrupted; Line 24 and 73 diverted. - - - Benutzen Sie die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte bis Luzernerhof) oder die normal verkehrende Linie 14 (mit Halten) bis Luzernerhof. - Use diverted line 24, 73, additional buses (direct ot Luzernhof) or the regular line 14 services (all stops) to Luzernhof. - - - - - - - route - - - - - - ch:vbl:VBLEBUS - EBUS - - ch:vbl:VBLEBUS:B - Luzernerhof - - - - ch:vbl:121::xx - Luzernerhof - destination - - - - - - - - - open - 0200 - 2017-05-28T10:22:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Die Umleitung endet hier - Diversion ends here - - - Einstieg der Linien 6 und 8 bei Kante A. Reisende nach Haldensteig, Casino-Palace und Europe erreichen ihr Ziel nur zu Fuß. - Board line 6 and 8 from platform A. Travellers to Haldensteig, Casino-Palace and Europe can only reach their destination on foot. - - - - - - - route - - - - - ch:vbl:VBL014 - 14 - - ch:vbl:VBL014:B - Horw Zentrum - - - - ch:vbl:121::03 - Luzernerhof - intermediate - - - - - - - - - open - 0210 - 2017-05-28T10:22:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Einstieg der Linien 6 und 8 bei Kante A. Reisende nach Haldensteig, Casino-Palace und Europe erreichen ihr Ziel nur zu Fuß. - Board line 6 and 8 from platform A. Travellers to Haldensteig, Casino-Palace and Europe can only reach their destination on foot. - - - - - - - route - - - - - ch:vbl:VBL024 - 24 - - ch:vbl:VBL024:B - Bahnhof - - - - ch:vbl:121::3 - Luzernerhof - origin - - - - - ch:vbl:VBL073 - 73 - - ch:vbl:VBL073:B - Bahnhof - - - - ch:vbl:121::3 - Luzernerhof - origin - - - - - - - - - open - 0215 - 2017-05-28T10:22:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Die Umleitung endet hier - Diversion ends here - - - Einstieg der Linien 6 und 8 bei Kante A. Reisende nach Haldensteig, Casino-Palace und Europe erreichen ihr Ziel nur zu Fuß. - Board line 6 and 8 from platform A. Travellers to Haldensteig, Casino-Palace and Europe can only reach their destination on foot. - - - - - - - route - - - - - ch:vbl:VBL024 - 24 - - ch:vbl:VBL024:B - Bahnhof - - - - ch:vbl:121::3 - Luzernerhof - origin - - - - - - - - - open - 0220 - 2017-05-28T10:22:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Die Umleitung endet hier - Diversion ends here - - - Umstieg auf die Linien 6 und 8: Einstieg bei Kante A. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. - Transfer to line 6 and 8: Board from platform A. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:B - Matthof - - - - ch:vbl:121::04 - Luzernerhof - origin - - - - - ch:vbl:VBL008 - 8 - - ch:vbl:VBL008:B - Hirtenhof - - - - ch:vbl:121::04 - Luzernerhof - origin - - - - - - - - - open - 0230 - 2017-05-28T10:22:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Normale Bedienung der Linien 6 bis Matthof und 8 bis Hirtenhof. - Regular service on line 6 to Matthof and line 8 to Hirtenhof. - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - Es muss mit Verspätungen gerechnet werden. - Expect delays. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:B - Matthof - - - - ch:vbl:120::02 - Schwanenplatz - intermediate - - - ch:vbl:119::01 - Bahnhof - intermediate - - - ch:vbl:118::02 - Kantonalbank - intermediate - - - ch:vbl:407::03 - Bundesplatz - intermediate - - - ch:vbl:606::02 - Werkhofstrasse - intermediate - - - ch:vbl:605::02 - Weinbergli - intermediate - - - ch:vbl:604::02 - Eisfeldstrasse - intermediate - - - ch:vbl:603::02 - Wartegg - intermediate - - - ch:vbl:602::02 - Schönbühl - intermediate - - - ch:vbl:601::01 - Matthof - destination - - - - - - - - - open - 0240 - 2017-05-28T10:22:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Es muss mit Verspätungen gerechnet werden. - Expect delays. - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - - - - - route - - - - - ch:vbl:VBL02A - 2 - - - ch:vbl:119::06 - Luzern Bahnhof - - - - - - - - - open - 0245 - 2017-05-28T10:22:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Unterbruch der Linien 6 und 8 - Line 6 and 8 disrupted - - - Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die umgeleitete Linie 73 oder die normal verkehrende Linie 14 und steigen Sie an der Brüelstrasse wieder um. Reisende nach dem Verkehrshaus benutzen die S3 oder das Schiff. - Transfer advice for line 6 and 8: Use diverted line 73 or the regular line 14 services to Brüelstrasse and transfer back to line 6 and 8. Travellers to Verkehrshaus use the S3 or ferry. - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - - - - - route - - - - - ch:vbl:VBL014A - 14 - - ch:vbl:VBL014:A - Brüelstrasse - - - - ch:vbl:119::08 - Luzern Bahnhof - - - - - - - - - open - 0246 - 2017-05-28T10:22:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Unterbruch der Linien 6 und 8 - Line 6 and 8 disrupted - - - Empfehlung für Linien 6 und 8: Für Fahrten zur Brüelstrasse und weiter bleiben Sie in der Linie 14 und steigen Sie an der Brüelstrasse um. Reisende nach dem Verkehrshaus benutzen ab dem Bahnhof die S3 oder das Schiff. - Advice for line 6 and 8: For services to Brüelstrasse and further, stay on line 14 and transfer at Brüelstrasse. Travellers after Verkehrshaus use the S3 or ferry from main station. - - - Die Dauer der Störung ist noch unbekannt. - Disruption duration until further notice. - - - - - - - - -       -       + + + + 2018-10-16T10:22:30+00:00 + ch:VBL +
      http:/server/siri/20_ums
      + Pgfkw0GAsg + true + false + + 2018-10-16T10:22:30+00:00 + ch:VBL + 40599x2dsjmu8yjzy + + + 2017-05-28T10:22:00+02:00 + VBL + 5a7cf4f0-c7a5-11e8-813f-f38697968b53 + 2 + + feed + VBL + + published + + 2017-05-28T10:10:00+02:00 + 2017-05-28T17:10:00+02:00 + + fire + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + 3 + route + DE + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + http://www.vbl.ch/aktuelles/verkehrsmeldungen/stoerungen/20160603_13? + + + + + + + + ch:vbl:622 + Haldensteig + + + + + + disruption + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:2507::01 + Büttenhalde + + + ch:vbl:VBL006:A + Büttenhalde + + + + ch:vbl:621::01 + Casino-Palace + affectedStopplace + + + ch:vbl:615::01 + Europe + affectedStopplace + + + ch:vbl:616::01 + Dietschiberg + affectedStopplace + + + ch:vbl:617::01 + Verkehrshaus + affectedStopplace + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:601:01 + Matthof + + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:617::02 + Verkehrshaus + affectedStopplace + + + ch:vbl:616::02 + Dietschiberg + affectedStopplace + + + ch:vbl:615::02 + Europe + affectedStopplace + + + ch:vbl:621::02 + Casino-Palace + affectedStopplace + + + ch:vbl:622::02 + Haldensteig + affectedStopplace + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:620:01 + Würzenbach + + + ch:vbl:VBL008:A + Würzenbach + + + + ch:vbl:621::01 + Casino-Palace + affectedStopplace + + + ch:vbl:615::01 + Europe + affectedStopplace + + + ch:vbl:616::01 + Dietschiberg + affectedStopplace + + + ch:vbl:617::01 + Verkehrshaus + affectedStopplace + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:801:01 + Hirtenhof + + + ch:vbl:VBL008:B + Hirtenhof + + + + ch:vbl:617::02 + Verkehrshaus + affectedStopplace + + + ch:vbl:616::02 + Dietschiberg + affectedStopplace + + + ch:vbl:615::02 + Europe + affectedStopplace + + + ch:vbl:621::02 + Casino-Palace + affectedStopplace + + + ch:vbl:622::02 + Haldensteig + affectedStopplace + + + + + + + + true + true + + + + diverted + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:2433:01 + Tschädigen + + + ch:vbl:VBL024:A + Tschädigen + + + + ch:vbl:121::02 + affectedStopplace + + + ch:vbl:621::01 + Casino-Palace + affectedStopplace + + + ch:vbl:617::01 + Verkehrshaus + affectedStopplace + + + ch:vbl:715::01 + intermediate + + + ch:vbl:716::01 + intermediate + + + ch:vbl:1405::01 + intermediate + + + ch:vbl:1406::01 + intermediate + + + ch:vbl:1407::01 + intermediate + + + ch:vbl:1408::01 + intermediate + + + ch:vbl:1409::01 + intermediate + + + ch:vbl:1410::01 + intermediate + + + ch:vbl:1411::01 + intermediate + + + ch:vbl:1412::01 + intermediate + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:119:13 + Bahnhof + + + ch:vbl:VBL024:B + Bahnhof + + + + ch:vbl:617::02 + Verkehrshaus + affectedStopplace + + + ch:vbl:621::02 + affectedStopplace + + + ch:vbl:622::02 + affectedStopplace + + + ch:vbl:1412::02 + intermediate + + + ch:vbl:1411::02 + intermediate + + + ch:vbl:1410::02 + intermediate + + + ch:vbl:1409::02 + intermediate + + + ch:vbl:1408::02 + intermediate + + + ch:vbl:1407::02 + intermediate + + + ch:vbl:1406::02 + intermediate + + + ch:vbl:1405::02 + intermediate + + + ch:vbl:716::02 + intermediate + + + ch:vbl:715::01 + intermediate + + + + + + + + true + true + + + PT7M + + + + + + + line + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 24 + + + ch:pb:PB073 + 73 + + + + + + + open + 0020 + 2017-05-28T10:22:00+02:00 + 1 + vbl + general + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Betroffen sind die Linien 6,8, 24 und 73 + Affected lines are 6, 8, 24 and 73 + + + Linie 6 und 8 fallen zwischen Luzernerhof und Brüelstrasse aus. + Linie 24 wird zwischen Luzernerhof und Brüelstrasse via St. Anna umgeleitet. Ca. 7 Min. längere Fahrzeit. + Linie 73 wird zwischen Luzernerhof und Brüelstrasse via St. Anna umgeleitet. Ca. 6 Min. längere Fahrzeit. + Line 6 and 8 disrupted Luzernerhof and Brüelstrasse. + Line 24 diverted between Luzernerhof and Brüelstrasse via St. Anna. Approx. 7 min delay. + Line 73 diverted between Luzernerhof and Brüelstrasse via St. Anna. Approx. 6 min delay. + + + Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Zwischen Luzern, Bahnhof und Verkehrshaus benutzen sie die S3 oder das Schiff. + Umstiegsempfehlung für die Linien 6 und 8: Bei den Haltestellen Luzernerhof bzw. Brüelstrasse auf die umgeleiteten Linien 24 und 73, die normal verkehrende Linie 14 oder den Entlastungsbus umsteigen. + Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + Between Luzern, Bahnhof and Verkehrshaus use the S3 or ferry. + Transfer advice for line 6 and 8: At Luzernerhof or Brüelstrasse use diverted line 24, 73, additional buses or the regular line 14 services. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:A + Büttenenhalde + + + + ch:vbl:601::01 + Matthof + + + ch:vbl:602::01 + Schönbühl + + + ch:vbl:603::03 + Wartegg + + + ch:vbl:604::01 + Eisfeldstrasse + + + ch:vbl:605::01 + Weinbergli + + + ch:vbl:606::01 + Werkhofstrasse + + + ch:vbl:407::02 + Bundesplatz + + + ch:vbl:118::01 + Kantonalbank (C) + + + ch:vbl:119::02 + Bahnhof (B) + + + ch:vbl:120:01 + Schwanenplatz + + + + + + + + + open + 0030 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Linie 6 fällt zwischen Luzernerhof und Brüelstrasse aus. + Line 6 cancelled between Luzernerhof and Brüelstrasse. + + + Reisende nach Brüelstrasse und weiter benützen die umgeleitete Linie 24 und 73 (ohne Halte zwischen Wey und Brühlstrasse) oder die normal verkehrende Linie 14 (mit Halten) und steigen an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Travellers to Brüelstrasse or further use the diverted line 24, 73 (direct between Wey and Brühlstrasse) or the regular line 14 services (all stop) and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + + + open + 0040 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Linie 6 fällt zwischen Luzernerhof und Brüelstrasse aus. + Line 6 cancelled between Luzernerhof and Brüelstrasse. + + + Reisende nach Brüelstrasse und weiter benützen die umgeleitete Linie 24 und 73 (ohne Halte zwischen Wey und Brühlstrasse) oder die normal verkehrende Linie 14 (mit Halten) und steigen an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Travellers to Brüelstrasse or further use the diverted line 24, 73 (direct between Wey and Brühlstrasse) or the regular line 14 services (all stop) and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + Weitere Informationen erhalten Sie unter www.vbl.ch/stoerung/haldenstrasse + For further information, please visit www.vbl.ch/stoerung/haldenstrasse + + + www.vbl.ch/stoerung/haldenstrasse + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:A + Büttenenhalde + + + + ch:vbl:121::02 + Luzernerhof (D) + + + + + + + + + open + 0050 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Linie 6 wendet hier + Line 6 turns here + + + Reisende zur Brühlstrasse und weiter benützen die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte zwischen Wey und Brühlstrasse) oder die normale verkehrende Linie 14 (mit Halten) ab Kante F (Wey) und steigen an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Travellers to Brüelstrasse or further use the diverted line 24, 73, additonal buses (direct between Wey and Brühlstrasse) or the regular line 14 services (all stop) from platform F (Wey) and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:A + Büttenenhalde + + + + ch:vbl:121::01 + Luzernerhof (C) + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:A + Würzenbach + + + + ch:vbl:121::01 + Luzernerhof (C) + + + + + + + + + open + 0060 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8 + Line 6 and 8 disrupted + + + Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die umgeleiteten Linien 24 und 73, die normal verkehrende Linie 14 oder den Entlastungsbus ab Kante F (Wey) und steigen Sie an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Transfer advice line 6 and 8: Use diverted line 24, 73, the regular line 14 services or the additional buses to Brüelstrasse and transfer back to line 6 and 8. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + Weitere Informationen erhalten Sie beim Auskunftspersonal. + For further information, please contact staff. + + + + + + + route + + + + + + ch:vbl:VBL014 + 14 + + ch:vbl:VBL014:A + Brüelstrasse + + + + ch:vbl:715::02 + Wey + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:VBL024:A + Tschädingen + + + + ch:vbl:715::02 + Wey + + + + + ch:vbl:VBL073 + 73 + + + ch:vbl:715::02 + Wey + + + + + + + + + + open + 0070 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8; Umleitung der Linien 24 und 73 + Line 6 and 8 disrupted; Line 24 and 73 diverted + + + Benutzen Sie die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte bis Brühlstrasse) oder die normal verkehrende Linie 14 (mit Halten) bis Brüelstrasse. + Use the diverted line 24, 73, additional buses (direct to Brühlstrasse) or the regular line 14 services (all stops) to Brüelstrasse. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:A + Büttenenhalde + + + + ch:vbl:121::02 + Luzernerhof (D) + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:A + Würzenbach + + + + ch:vbl:121::02 + Luzernerhof (D) + + + + + + + + + open + 0130 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Linie 6 und 8 fallen bis Brüelstrasse aus. Linie 24 wird zwischen Luzernerhof und Brüelstrasse via St. Anna umgeleitet. Ca. 7 Min. längere Fahrzeit. Linie 73 wird zwischen Luzernerhof und Brüelstrasse via St. Anna umgeleitet. Ca. 6 Min. längere Fahrzeit. + Line 6 and 8 services cancelled to Brüelstrasse. Line 24 services diverted between Luzernerhof and Brüelstrasse via St. Anna. Approx. 7 min. delay. Line 73 services diverted between Luzernerhof and Brüelstrasse. Approx. 6 min delay. + + + Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte zwischen Wey und Brühlstrasse) oder die normale verkehrende Linie 14 (mit Halten) ab Kante F (Wey) und steigen Sie an der Brüelstrasse um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Transfer advice for line 6 and 8: To Brüelstrasse use diverted line 24, 73, additional buses (direct between Wey and Brühlstrasse) or the regular line 14 services (all stops) from platform F (Way) and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:A + Büttenenhalde + + + + ch:vbl:621::01 + Casino-Palace + + + ch:vbl:615::01 + Europe + + + ch:vbl:616::01 + Dietschiberg + + + ch:vbl:617::01 + Verkehrshaus + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:617::02 + Verkehrshaus + + + ch:vbl:616::02 + Dietschiberg + + + ch:vbl:615::02 + Europe + + + ch:vbl:621::02 + Casino-Palace + + + ch:vbl:622::01 + Haldensteig + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:A + Würzenbach + + + + ch:vbl:621::01 + Casino-Palace + + + ch:vbl:615::01 + Europe + + + ch:vbl:616::01 + Dietschiberg + + + ch:vbl:617::01 + Verkehrshaus + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:B + Hirtenhof + + + + ch:vbl:617::02 + Verkehrshaus + + + ch:vbl:616::02 + Dietschiberg + + + ch:vbl:615::02 + Europe + + + ch:vbl:621::02 + Casino-Palace + + + ch:vbl:622::01 + Haldensteig + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:VBL024:A + Tschädingen + + + + ch:vbl:621::01 + Casino-Palace + + + ch:vbl:615::01 + Europe + + + ch:vbl:616::01 + Dietschiberg + + + ch:vbl:617::01 + Verkehrshaus + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:VBL024:B + Bahnhof + + + + ch:vbl:617::02 + Verkehrshaus + + + ch:vbl:616::02 + Dietschiberg + + + ch:vbl:615::02 + Europe + + + ch:vbl:621::02 + Casino-Palace + + + ch:vbl:622::01 + Haldensteig + + + + + ch:pb:PB073 + 73 + + + ch:vbl:621::01 + Casino-Palace + + + ch:vbl:615::01 + Europe + + + ch:vbl:616::01 + Dietschiberg + + + ch:vbl:617::01 + Verkehrshaus + + + ch:vbl:617::02 + Verkehrshaus + + + ch:vbl:616::02 + Dietschiberg + + + ch:vbl:615::02 + Europe + + + ch:vbl:621::02 + Casino-Palace + + + ch:vbl:622::01 + Haldensteig + + + + + + + + + open + 0140 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Keine Bedienung der Linien 6, 8, 24 und 73 zwischen Luzernerhof und Brüelstrasse + No service for line 6, 8, 24 and 73 between Luzernerhof and Brüelstrasse + + + Reisende zwischen Luzernerhof und Brüelstrasse erreichen ihr Ziel nur zu Fuß. Ab Luzernerhof und Brüelstrasse verkehren die Linie auf den normalen Fahrwegen. + Travellers between Luzernerhof and Brüelstrasse can only reach their destination on foot. From Luzernerhof and Brüelstrasse lines will run on regular routes. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + Fällt aus + Cancelled + + + + + + + route + + + + + ch:vbl:014 + 14 + + ch:vbl:VBL014:A + Brüelstrasse + + + + ch:vbl:618::01 + Brüelstrasse + destination + + + + + + + + + open + 0080 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Einstieg der Linien 6 und 8 bei Kante C. Reisende nach Verkehrshaus und Dietschiberg erreichen ihr Ziel nur zu Fuß. + Board line 6 and 8 from platform C. Travellers to Verkehrshaus and Dietschiberg can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:024 + 24 + + ch:vbl:VBL024:A + Tschädingen + + + + ch:vbl:618::01 + Brüelstrasse + intermediate + + + + + ch:pb:073 + 73 + + ch:pb:PB073:A + Rotkreuz + + + + ch:vbl:618::04 + Brüelstrasse + destination + + + + + + + + + open + 0090 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Umleitung endet hier + Diversion ends here + + + Umstieg auf Linie 6 und 8: Einstieg bei Kante C. Reisende nach Verkehrshaus und Dietschiberg erreichen ihr Ziel nur zu Fuß. + Transfer to line 6 and 8: Board from platform C. Travellers to Verkehrshaus and Dietschiberg can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:A + Büttenhalde + + + + ch:vbl:618::03 + Brüelstrasse + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:A + Würzenbach + + + + ch:vbl:618::03 + Brüelstrasse + + + + + + + + + open + 0100 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Normale Bedienung der Linien 6 bis Büttenenhalde und 8 bis Würzenbach. + Regular line 6 services to Büttenenhalde and 8 to Würzenbach. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + Es muss mit Verspätungen gerechnet werden. + Expect delays. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:A + Büttenhalde + + + + + ch:vbl:618::03 + Brüelstrasse(B) + + + ch:vbl:2502::01 + Giseli + intermediate + + + ch:vbl:2503::01 + Oberseeburg + intermediate + + + ch:vbl:2504::01 + Oberseeburghöhe + intermediate + + + ch:vbl:2505::01 + Eggen + intermediate + + + ch:vbl:2506::01 + Büttenen + intermediate + + + ch:vbl:2507::01 + Büttenenhalde + destination + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:A + Würzenbach + + + + + ch:vbl:618::03 + Brüelstrasse(B) + + + ch:vbl:619::01 + Würzenbachmatte + intermediate + + + ch:vbl:620::01 + Würzenbach + destination + + + + + + + + + open + 0110 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + Es muss mit Verspätungen gerechnet werden. + Expect delays. + + + + + + + route + + + + + ch:vbl:Entlastungsbus + Entlastungsbus + + ch:vbl:VBL006:A + Büttenhalde + + + + ch:vbl:618::04 + Brüelstrasse + + + + + + + + + open + 0120 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Diese Fahrt endet hier + This service terminates here + + + Einstieg der Linien 6 und 8 bei Kante C. Reisende nach Verkehrshaus und Dietschiberg erreichen ihr Ziel nur zu Fuß. + Board line 6 and 8 from platform C. Travellers to Verkehrshaus and Dietschiberg can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:2507::01 + Büttenenhalde + origin + + + ch:vbl:2506::02 + Büttenen + intermediate + + + ch:vbl:2505::02 + Eggen + intermediate + + + ch:vbl:2504::02 + Oberseeburghöhe + intermediate + + + ch:vbl:2503::02 + Oberseeburg + intermediate + + + ch:vbl:2502::02 + Giseli + intermediate + + + + + + + + + open + 0150 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Linie 6 fällt zwischen Brüelstrasse und Luzernerhof aus. + Line 6 cancelled between Brüelstrasse and Luzernerhof. + + + Reisende nach Luzernerhof oder weiter benützen die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte zwischen Brühlstrasse und Luzernerhof) oder die normal verkehrende Linie 14 (mit Halten) bis Luzernerhof und steigen dort wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. + Travellers to Luzernerhof or further use the diverted lines 24, 73 and the additional bus (direct between Brühlstrasse and Luzernerhof) or the regular line 14 services (all stop) to Luzernhof and transfer there. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:2507::01 + Büttenenhalde + origin + + + ch:vbl:2506::02 + Büttenen + intermediate + + + ch:vbl:2505::02 + Eggen + intermediate + + + ch:vbl:2504::02 + Oberseeburghöhe + intermediate + + + ch:vbl:2503::02 + Oberseeburg + intermediate + + + ch:vbl:2502::02 + Giseli + intermediate + + + + + + + + + open + 0160 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Linie 6 fällt zwischen Brüelstrasse und Luzernerhof aus. + Line 6 cancelled between Brüelstrasse and Luzernerhof. + + + Reisende nach Luzernerhof oder weiter benützen die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte zwischen Brühlstrasse und Luzernerhof) oder die normal verkehrende Linie 14 (mit Halten) bis Luzernerhof und steigen dort wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. + Travellers to Luzernerhof or further use the diverted lines 24, 73 and the additional bus (direct between Brühlstrasse and Luzernerhof) or the regular line 14 services (all stop) to Luzernhof and transfer there. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:618::02 + Brüelstrasse + destination + + + + + + + + + open + 0170 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Linie 6 wendet hier + Line 6 turns here + + + Reisende zum Luzernerhof oder weiter benützen die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte bis Luzernerhof) oder die normal verkehrende Linie 14 (mit Halten) ab Kante D und steigen beim Luzernerhof wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. + Travellers to Luzernerhof or further use the diverted lines 24, 73, addintionl buses (direct to Luzernerhof) or the regular line 14 services (all stops) from platform D and transfer back to line 6 and 8 at Luzernerhof. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:618::02 + Brüelstrasse + destination + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:B + Hirtenhof + + + + ch:vbl:618::02 + Brüelstrasse + destination + + + + + + + + + open + 0180 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8 + Line 6 and 8 disrupted + + + Reisende zum Luzernerhof oder weiter benützen die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte bis Luzernerhof) oder die normal verkehrende Linie 14 (mit Halten) ab Kante D und steigen beim Luzernerhof wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. + Travellers to Luzernerhof or further use the diverted lines 24, 73, addintionl buses (direct to Luzernerhof) or the regular line 14 services (all stops) from platform D and transfer back to line 6 and 8 at Luzernerhof. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL014 + 14 + + ch:vbl:VBL014:A + Brühlstrasse + + + + ch:vbl:618::04 + Brühlstrasse + destination + + + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:VBL024:B + Bahnhof + + + + ch:vbl:618::04 + Brühlstrasse + destination + + + + + + + + + open + 0190 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8; Umleitung der Linien 24 und 73. + Line 6 and 8 disrupted; Line 24 and 73 diverted. + + + Benutzen Sie die umgeleiteten Linien 24, 73 und den Entlastungsbus (ohne Halte bis Luzernerhof) oder die normal verkehrende Linie 14 (mit Halten) bis Luzernerhof. + Use diverted line 24, 73, additional buses (direct ot Luzernhof) or the regular line 14 services (all stops) to Luzernhof. + + + + + + + route + + + + + + ch:vbl:VBLEBUS + EBUS + + ch:vbl:VBLEBUS:B + Luzernerhof + + + + ch:vbl:121::xx + Luzernerhof + destination + + + + + + + + + open + 0200 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Umleitung endet hier + Diversion ends here + + + Einstieg der Linien 6 und 8 bei Kante A. Reisende nach Haldensteig, Casino-Palace und Europe erreichen ihr Ziel nur zu Fuß. + Board line 6 and 8 from platform A. Travellers to Haldensteig, Casino-Palace and Europe can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL014 + 14 + + ch:vbl:VBL014:B + Horw Zentrum + + + + ch:vbl:121::03 + Luzernerhof + intermediate + + + + + + + + + open + 0210 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Einstieg der Linien 6 und 8 bei Kante A. Reisende nach Haldensteig, Casino-Palace und Europe erreichen ihr Ziel nur zu Fuß. + Board line 6 and 8 from platform A. Travellers to Haldensteig, Casino-Palace and Europe can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:VBL024:B + Bahnhof + + + + ch:vbl:121::3 + Luzernerhof + origin + + + + + ch:vbl:VBL073 + 73 + + ch:vbl:VBL073:B + Bahnhof + + + + ch:vbl:121::3 + Luzernerhof + origin + + + + + + + + + open + 0215 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Umleitung endet hier + Diversion ends here + + + Einstieg der Linien 6 und 8 bei Kante A. Reisende nach Haldensteig, Casino-Palace und Europe erreichen ihr Ziel nur zu Fuß. + Board line 6 and 8 from platform A. Travellers to Haldensteig, Casino-Palace and Europe can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:VBL024:B + Bahnhof + + + + ch:vbl:121::3 + Luzernerhof + origin + + + + + + + + + open + 0220 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Umleitung endet hier + Diversion ends here + + + Umstieg auf die Linien 6 und 8: Einstieg bei Kante A. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Transfer to line 6 and 8: Board from platform A. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:121::04 + Luzernerhof + origin + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:B + Hirtenhof + + + + ch:vbl:121::04 + Luzernerhof + origin + + + + + + + + + open + 0230 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Normale Bedienung der Linien 6 bis Matthof und 8 bis Hirtenhof. + Regular service on line 6 to Matthof and line 8 to Hirtenhof. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + Es muss mit Verspätungen gerechnet werden. + Expect delays. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:120::02 + Schwanenplatz + intermediate + + + ch:vbl:119::01 + Bahnhof + intermediate + + + ch:vbl:118::02 + Kantonalbank + intermediate + + + ch:vbl:407::03 + Bundesplatz + intermediate + + + ch:vbl:606::02 + Werkhofstrasse + intermediate + + + ch:vbl:605::02 + Weinbergli + intermediate + + + ch:vbl:604::02 + Eisfeldstrasse + intermediate + + + ch:vbl:603::02 + Wartegg + intermediate + + + ch:vbl:602::02 + Schönbühl + intermediate + + + ch:vbl:601::01 + Matthof + destination + + + + + + + + + open + 0240 + 2017-05-28T10:22:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Es muss mit Verspätungen gerechnet werden. + Expect delays. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + + + + + route + + + + + ch:vbl:VBL02A + 2 + + + ch:vbl:119::06 + Luzern Bahnhof + + + + + + + + + open + 0245 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8 + Line 6 and 8 disrupted + + + Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die umgeleitete Linie 73 oder die normal verkehrende Linie 14 und steigen Sie an der Brüelstrasse wieder um. Reisende nach dem Verkehrshaus benutzen die S3 oder das Schiff. + Transfer advice for line 6 and 8: Use diverted line 73 or the regular line 14 services to Brüelstrasse and transfer back to line 6 and 8. Travellers to Verkehrshaus use the S3 or ferry. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + + + + + route + + + + + ch:vbl:VBL014A + 14 + + ch:vbl:VBL014:A + Brüelstrasse + + + + ch:vbl:119::08 + Luzern Bahnhof + + + + + + + + + open + 0246 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8 + Line 6 and 8 disrupted + + + Empfehlung für Linien 6 und 8: Für Fahrten zur Brüelstrasse und weiter bleiben Sie in der Linie 14 und steigen Sie an der Brüelstrasse um. Reisende nach dem Verkehrshaus benutzen ab dem Bahnhof die S3 oder das Schiff. + Advice for line 6 and 8: For services to Brüelstrasse and further, stay on line 14 and transfer at Brüelstrasse. Travellers after Verkehrshaus use the S3 or ferry from main station. + + + Die Dauer der Störung ist noch unbekannt. + Disruption duration until further notice. + + + + + + + + +       +       diff --git a/examples/siri_exm_SX/VDV736_exm/SX_1135_main_message_update.xml b/examples/siri_exm_SX/VDV736_exm/SX_1135_main_message_update.xml index d3327f51..b80ee76c 100644 --- a/examples/siri_exm_SX/VDV736_exm/SX_1135_main_message_update.xml +++ b/examples/siri_exm_SX/VDV736_exm/SX_1135_main_message_update.xml @@ -1,2206 +1,2206 @@ - - - - 2018-10-16T10:22:30+00:00 - ch:VBL -
      http:/server/siri/20_ums
      - Pgfkw0GAsg - true - false - - 2018-10-16T10:22:30+00:00 - ch:VBL - 40599x2dsjmu8yjzy - - - 2017-05-28T09:42:00+02:00 - VBL - 5a7cf4f0-c7a5-11e8-813f-f38697968b53 - 2 - - feed - VBL - - published - - 2017-05-28T09:42:00+02:00 - 2017-05-28T17:10:00+02:00 - - fire - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - 3 - route - DE - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - http://www.vbl.ch/aktuelles/verkehrsmeldungen/stoerungen/20160603_13? - - - - - - - - ch:vbl:622 - Haldensteig - - - - - - disruption - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:2507::01 - Büttenhalde - - - ch:vbl:VBL006:A - Büttenhalde - - - - ch:vbl:621::01 - Casino-Palace - affectedStopplace - - - ch:vbl:615::01 - Europe - affectedStopplace - - - ch:vbl:616::01 - Dietschiberg - affectedStopplace - - - ch:vbl:617::01 - Verkehrshaus - affectedStopplace - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:601:01 - Matthof - - - ch:vbl:VBL006:B - Matthof - - - - ch:vbl:617::02 - Verkehrshaus - affectedStopplace - - - ch:vbl:616::02 - Dietschiberg - affectedStopplace - - - ch:vbl:615::02 - Europe - affectedStopplace - - - ch:vbl:621::02 - Casino-Palace - affectedStopplace - - - ch:vbl:622::02 - Haldensteig - affectedStopplace - - - - - ch:vbl:VBL008 - 8 - - ch:vbl:620:01 - Würzenbach - - - ch:vbl:VBL008:A - Würzenbach - - - - ch:vbl:621::01 - Casino-Palace - affectedStopplace - - - ch:vbl:615::01 - Europe - affectedStopplace - - - ch:vbl:616::01 - Dietschiberg - affectedStopplace - - - ch:vbl:617::01 - Verkehrshaus - affectedStopplace - - - - - ch:vbl:VBL008 - 8 - - ch:vbl:801:01 - Hirtenhof - - - ch:vbl:VBL008:B - Hirtenhof - - - - ch:vbl:617::02 - Verkehrshaus - affectedStopplace - - - ch:vbl:616::02 - Dietschiberg - affectedStopplace - - - ch:vbl:615::02 - Europe - affectedStopplace - - - ch:vbl:621::02 - Casino-Palace - affectedStopplace - - - ch:vbl:622::02 - Haldensteig - affectedStopplace - - - - - - - - true - true - - - - diverted - - - - - ch:vbl:VBL024 - 24 - - ch:vbl:2433:01 - Tschädigen - - - ch:vbl:VBL024:A - Tschädigen - - - - ch:vbl:121::02 - affectedStopplace - - - ch:vbl:621::01 - Casino-Palace - affectedStopplace - - - ch:vbl:617::01 - Verkehrshaus - affectedStopplace - - - ch:vbl:715::01 - intermediate - - - ch:vbl:716::01 - intermediate - - - ch:vbl:1405::01 - intermediate - - - ch:vbl:1406::01 - intermediate - - - ch:vbl:1407::01 - intermediate - - - ch:vbl:1408::01 - intermediate - - - ch:vbl:1409::01 - intermediate - - - ch:vbl:1410::01 - intermediate - - - ch:vbl:1411::01 - intermediate - - - ch:vbl:1412::01 - intermediate - - - - - ch:vbl:VBL024 - 24 - - ch:vbl:119:13 - Bahnhof - - - ch:vbl:VBL024:B - Bahnhof - - - - ch:vbl:617::02 - Verkehrshaus - affectedStopplace - - - ch:vbl:621::02 - affectedStopplace - - - ch:vbl:622::02 - affectedStopplace - - - ch:vbl:1412::02 - intermediate - - - ch:vbl:1411::02 - intermediate - - - ch:vbl:1410::02 - intermediate - - - ch:vbl:1409::02 - intermediate - - - ch:vbl:1408::02 - intermediate - - - ch:vbl:1407::02 - intermediate - - - ch:vbl:1406::02 - intermediate - - - ch:vbl:1405::02 - intermediate - - - ch:vbl:716::02 - intermediate - - - ch:vbl:715::01 - Wey Auch? - intermediate - - - - - - - - true - true - - - PT7M - - - - - - - line - - - - - ch:vbl:VBL006 - 6 - - - ch:vbl:VBL008 - 8 - - - ch:vbl:VBL024 - 24 - - - - - - - open - 0250 - 2017-05-28T09:42:00+02:00 - 1 - vbl - general - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Betroffen sind die Linien 6, 8 und 24 - Affected lines are 6, 8 and 24 - - - Linie 6 und 8 fallen zwischen Luzernerhof und Brüelstrasse aus. - Linie 24 wird zwischen Luzernerhof und Brüelstrasse via St. Anna umgeleitet. Ca. 7 Min. längere Fahrzeit. - Line 6 and 8 services cancelled between Luzernerhof and Brüelstrasse. - Line 24 divirted between Luzernerhof and Brüelstrasse via St. Anna. Approx. 7 min delay. - - - Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. - Zwischen Luzern, Bahnhof und Verkehrshaus benutzen sie die S3 oder das Schiff. - Umstiegsempfehlung für die Linien 6 und 8: Bei den Haltestellen Luzernerhof bzw. Brüelstrasse auf die umgeleitete Linie 24, die normal verkehrenden Linien 14 und 73 oder den Entlastungsbus umsteigen. - Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. - Between Luzern, Bahnhof and Verkehrshaus use the S3 or ferry. - Transfer advice for line 6 and 8: At Luzernerhof or Brüelstrasse use diverted line 24, 73, additional buses or the regular line 14 services. - - - Die Störung dauert bis ca.12:30 Uhr. - Disruption duration until 12:30pm. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:A - Büttenenhalde - - - - ch:vbl:601::01 - Matthof - - - ch:vbl:602::01 - Schönbühl - - - ch:vbl:603::03 - Wartegg - - - ch:vbl:604::01 - Eisfeldstrasse - - - ch:vbl:605::01 - Weinbergli - - - ch:vbl:606::01 - Werkhofstrasse - - - ch:vbl:407::02 - Bundesplatz - - - ch:vbl:118::01 - Kantonalbank (C) - - - ch:vbl:119::02 - Bahnhof (B) - - - ch:vbl:120::01 - Schwanenplatz - - - - - - - - - open - 0260 - 2017-05-28T09:42:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Die Linie 6 fällt zwischen Luzernerhof und Brüelstrasse aus. - Line 6 cancelled between Luzernerhof and Brüelstrasse. - - - Reisende nach Brüelstrasse und weiter benützen die umgeleitete Linie 24 (ohne Halte zwischen Wey und Brüelstrasse) oder die normal verkehrenden Linien 14 und 73 und steigen an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. - Travellers to Brüelstrasse or further use the diverted line 24 (direct between Wey and Brühlstrasse) or the regular line 14 or 73 services and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. - - - Die Störung dauert bis ca.12:30 Uhr. - Disruption duration until 12:30pm. - - - - - open - 0270 - 2017-05-28T09:42:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Die Linie 6 fällt zwischen Luzernerhof und Brüelstrasse aus. - Line 6 cancelled between Luzernerhof and Brüelstrasse. - - - Reisende nach Brüelstrasse und weiter benützen die umgeleitete Linie 24 (ohne Halte zwischen Wey und Brüelstrasse) oder die normal verkehrenden Linien 14 und 73 und steigen an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. - Travellers to Brüelstrasse or further use the diverted line 24 (direct between Wey and Brühlstrasse) or the regular services of line 14 or 73 and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. - - - Die Störung dauert bis ca.12:30 Uhr. - Disruption duration until 12:30pm. - - - Weitere Informationen erhalten Sie unter www.vbl.ch/stoerung/haldenstrasse - For further information, please visit www.vbl.ch/stoerung/haldenstrasse - - - www.vbl.ch/stoerung/haldenstrasse - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - - ch:vbl:121::02 - Luzernerhof (B) - - - - - - - - - open - 0280 - 2017-05-28T09:42:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Linie 6 wendet hier - Line 6 turns here - - - Reisende zur Brüelstrasse und weiter benützen die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte zwischen Wey und Brüelstrasse) oder die normale verkehrende Linie 14 (mit Halten) ab Kante F (Wey) oder die Linie 73 ab Kante D und steigen an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. - Travellers to Brüelstrasse or further use the diverted line 24, additonal buses (direct between Wey and Brüelstrasse), the regular services of line 14 (all stops) from platform F (Way) or line 73 from platform D and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - - ch:vbl:121::01 - Luzernerhof (C) - - - ch:vbl:121::02 - Luzernerhof (D) - - - - - ch:vbl:VBL008 - 8 - - - ch:vbl:121::01 - Luzernerhof (C) - - - ch:vbl:121::02 - Luzernerhof (D) - - - - - - - - - open - 0290 - 2017-05-28T09:42:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Unterbruch der Linien 6 und 8 - Line 6 and 8 disrupted - - - Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die umgeleitete Linie 24, die normal verkehrende Linie 14 und den Entlastungsbus ab Kante F (Wey) oder die Linie 73 ab Kante D und steigen Sie an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. - Transfer advice line 6 and 8: To Brüelstrasse use diverted line 24, the regular line 14 services or the additional buses from platform F (Wey) or line 73 from platform D and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. - - - Die Störung dauert bis ca.12:30 Uhr. - Disruption duration until 12:30pm. - - - Weitere Informationen erhalten Sie beim Auskunftspersonal. - For further information, please contact staff. - - - - - - - route - - - - - ch:vbl:Entlastungsbusse - - - ch:vbl:715::01 - Wey - - - - - ch:vbl:VBL014 - 14 - - - ch:vbl:715::01 - Wey - - - - - ch:vbl:VBL24 - 24 - - - ch:vbl:715::01 - Wey - - - - - - - - - open - 0300 - 2017-05-28T09:42:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Unterbruch der Linien 6 und 8; Umleitung der Linien 24. - Line 6 and 8 disrupted; Line 24 diverted. - - - Benutzen Sie die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte bis Brüelstrasse) oder die normal verkehrenden Linie 14 (mit Halten) und 73 bis Brüelstrasse. - Use diverted line 24, additional buses (direct to Brüelstrasse), regular services of line 14 (all stops) or 73 to Brüelstrasse. - - - Die Störung dauert bis ca.12:30 Uhr. - Disruption duration until 12:30pm. - - - - - - - route - - - - - ch:vbl:VBL006 - 06 - - ch:vbl:VBL006:A - Büttenenhalde - - - - ch:vbl:121::02 - Luzernerhof (D) - - - - - ch:vbl:VBL008 - 08 - - ch:vbl:VBL008:A - Würzenbach - - - - ch:vbl:121::02 - Luzernerhof (D) - - - - - - - - - open - 0370 - 2017-05-28T09:42:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Linie 6 und 8 fallen bis Brüelstrasse aus. Linie 24 wird zwischen Luzernerhof und Brüel via St. Anna umgeleitet. Ca. 7 Min. längere Fahrzeit. Linie 73 verkehrt wieder normal. - Line 6 and 8 cancelled services to Brüelstrasse. Line 24 services diverted between Luzernerhof and Brüel via St. Anna. Approx. 7 min delay. Line 73 back to regular service. - - - Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte zwischen Wey und Brüelstrasse) oder die normale verkehrende Linie 14 (mit Halten) ab Kante F (Wey) oder die Linie 73 ab Kante D und steigen Sie an der Brüelstrasse um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. - Transfer advice for line 6 and 8: Use diverted line 73, additonal buses (direct between Wey and Brüelstrasse), the regular line 14 services (all stops) from platform F (Wey) or line 73 from platform D and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. - - - Die Störung dauert bis ca.12:30 Uhr. - Disruption duration until 12:30pm. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:A - Büttenenhalde - - - - ch:vbl:621::01 - Casino-Palace - - - ch:vbl:615::01 - Europe - - - ch:vbl:616::01 - Dietschiberg - - - ch:vbl:617::01 - Verkehrshaus - - - - - ch:vbl:VBL008 - 8 - - ch:vbl:VBL008:A - Würzenbach - - - - ch:vbl:621::01 - Casino-Palace - - - ch:vbl:615::01 - Europe - - - ch:vbl:616::01 - Dietschiberg - - - ch:vbl:617::01 - Verkehrshaus - - - - - ch:vbl:VBL024 - 24 - - ch:vbl:VBL024:A - Tschädingen - - - - ch:vbl:621::01 - Casino-Palace - - - ch:vbl:615::01 - Europe - - - ch:vbl:616::01 - Dietschiberg - - - ch:vbl:617::01 - Verkehrshaus - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:B - Matthof - - - - ch:vbl:617::02 - Verkehrshaus - - - ch:vbl:616::02 - Dietschiberg - - - ch:vbl:615::02 - Europe - - - ch:vbl:621::02 - Casino-Palace - - - ch:vbl:622::01 - Haldensteig - - - - - ch:vbl:VBL008 - 8 - - ch:vbl:VBL008:B - Hirtenhof - - - - ch:vbl:617::02 - Verkehrshaus - - - ch:vbl:616::02 - Dietschiberg - - - ch:vbl:615::02 - Europe - - - ch:vbl:621::02 - Casino-Palace - - - ch:vbl:622::01 - Haldensteig - - - - - ch:vbl:VBL024 - 24 - - ch:vbl:VBL024:B - Bahnhof - - - - ch:vbl:617::02 - Verkehrshaus - - - ch:vbl:616::02 - Dietschiberg - - - ch:vbl:615::02 - Europe - - - ch:vbl:621::02 - Casino-Palace - - - ch:vbl:622::01 - Haldensteig - - - - - - - - - open - 0380 - 2017-05-28T09:42:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Keine Bedienung der Linien 6, 8 und 24 zwischen Luzernerhof und Brüelstrasse - Line 6, 8 and 24 no service between Luzernerhof and Brüelstrasse - - - Reisende zwischen Luzernerhof und Brüelstrasse erreichen ihr Ziel nur zu Fuß. Ab Luzernerhof und Brüelstrasse verkehren die Linie auf den normalen Fahrwegen. - Travellers between Luzernerhof and Brüelstrasse can only reach their destination on foot. From Luzernerhof and Brüelstrasse lines will run on regular routes. - - - Die Störung dauert bis ca.12:30 Uhr. - Disruption duration until 12:30pm. - - - Fällt aus - Cancelled - - - - - - - route - - - - - ch:vbl:014 - 14 - - ch:vbl:VBL014:A - Brüelstrasse - - - - ch:vbl:618::01 - Brüelstrasse - destination - - - - - - - - - open - 0310 - 2017-05-28T09:42:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Die Fahrt endet hier - Service terminates here - - - Einstieg der Linien 6 und 8 bei Kante C. Reisende nach Verkehrshaus und Dietschiberg erreichen ihr Ziel nur zu Fuß. - Board line 6 and 8 from platform C. Travellers to Verkehrshaus and Dietschiberg can only reach their destination on foot. - - - - - - - route - - - - - ch:vbl:024 - 24 - - ch:vbl:VBL014:A - Brüelstrasse - - - - ch:vbl:618::04 - Brüelstrasse - destination - - - - - - - - - open - 0320 - 2017-05-28T09:42:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Die Umleitung endet hier - Diversion ends here - - - Umstieg auf Linie 6 und 8: Einstieg bei Kante C. Reisende nach Verkehrshaus und Dietschiberg erreichen ihr Ziel nur zu Fuß. - Transfer to line 6 and 8: Board from platform C. Travellers to Verkehrshaus and Dietschiberg can only reach their destination on foot. - - - - - - - route - - - - - ch:vbl:VBL006 - 06 - - ch:vbl:VBL006:A - Büttenenhalde - - - - ch:vbl:618::03 - Brüelstrasse - - - - - ch:vbl:VBL008 - 08 - - ch:vbl:VBL008:A - Würzenbach - - - - ch:vbl:618::03 - Brüelstrasse - - - - - - - - - open - 0330 - 2017-05-28T09:42:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Normale Bedienung der Linien 6 bis Büttenenhalde und 8 bis Würzenbach. Es muss mit Verspätungen gerechnet werden. - Regular service on line 6 to Büttenenhalde and 8 to Würzenbach. Expect delays. - - - Die Störung dauert bis ca.12:30 Uhr. - Disruption duration until 12:30pm. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:A - Büttenhalde - - - - ch:vbl:2502::01 - Giseli - - - ch:vbl:2503::01 - Oberseeburg - intermediate - - - ch:vbl:2504::01 - Oberseeburghöhe - intermediate - - - ch:vbl:2505::01 - Eggen - intermediate - - - ch:vbl:2506::01 - Büttenen - intermediate - - - ch:vbl:2507::01 - Büttenenhalde - destination - - - - - ch:vbl:VBL008 - 8 - - ch:vbl:VBL008:A - Würzenbach - - - - ch:vbl:619::01 - Würzenbachmatte - intermediate - - - ch:vbl:620::01 - Würzenbach - destination - - - - - - - - - open - 0340 - 2017-05-28T09:42:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Es muss mit Verspätungen gerechnet werden. - Expect delays. - - - Die Störung dauert bis ca. 12:30 Uhr. - Disruption duration until 12:30pm. - - - - - - - route - - - - - ch:vbl:Entlastungsbus - Entlastungsbus - - ch:vbl:VBL006:A - Büttenhalde - - - - ch:vbl:618::04 - Brüelstrasse - - - - - - - - - open - 0350 - 2017-05-28T10:22:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Diese Fahrt endet hier - This service terminates here - - - Einstieg der Linien 6 und 8 bei Kante C. Reisende nach Verkehrshaus und Dietschiberg erreichen ihr Ziel nur zu Fuß. - Board line 6 and 8 from platform C. Travellers to Verkehrshaus and Dietschiberg can only reach their destination on foot. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:B - Matthof - - - - ch:vbl:2507::01 - Büttenenhalde - origin - - - ch:vbl:2506::02 - Büttenen - intermediate - - - ch:vbl:2505::02 - Eggen - intermediate - - - ch:vbl:2504::02 - Oberseeburghöhe - intermediate - - - ch:vbl:2503::02 - Oberseeburg - intermediate - - - ch:vbl:2502::02 - Giseli - intermediate - - - - - - - - - open - 0390 - 2017-05-28T09:42:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Die Linie 6 fällt zwischen Brüelstrasse und Luzernerhof aus. - Line 6 cancelled between Brüelstrasse and Luzernerhof. - - - Reisende nach Luzernerhof oder weiter benützen die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte zwischen Brüelstrasse und Luzernerhof) oder die normal verkehrenden Linien 14 (mit Halten) und 73 bis Luzernerhof und steigen dort wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. - Travellers to Luzernerhof or further use the diverted line 24, additional buses (direct between Brühlstrasse and Luzernerhof), the regular line 14 services (all stop) or line 73 to Luzernhof and transfer there. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. - - - Die Störung dauert bis ca. 12:30 Uhr. - Disruption duration until 12:30pm. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:B - Matthof - - - - ch:vbl:2507::01 - Büttenenhalde - origin - - - ch:vbl:2506::02 - Büttenen - intermediate - - - ch:vbl:2505::02 - Eggen - intermediate - - - ch:vbl:2504::02 - Oberseeburghöhe - intermediate - - - ch:vbl:2503::02 - Oberseeburg - intermediate - - - ch:vbl:2502::02 - Giseli - intermediate - - - - - - - - - open - 0400 - 2017-05-28T09:42:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Die Linie 6 fällt zwischen Brüelstrasse und Luzernerhof aus. - Line 6 cancelled between Brüelstrasse and Luzernerhof. - - - Reisende nach Luzernerhof oder weiter benützen die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte zwischen Brüelstrasse und Luzernerhof) oder die normal verkehrenden Linien 14 (mit Halten) und 73 bis Luzernerhof und steigen dort wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. - Travellers to Luzernerhof or further use the diverted line 24, the additional buses (direct between Brühlstrasse and Luzernerhof), the regular line 14 services (all stop) or line 73 to Luzernhof and transfer there. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. - - - Die Störung dauert bis ca. 12:30 Uhr. - Disruption duration until 12:30pm. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:B - Matthof - - - - ch:vbl:618::02 - Brüelstrasse - - - - - - - - - open - 0410 - 2017-05-28T09:42:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Linie 6 wendet hier - Line 6 turns here - - - Reisende zum Luzernerhof oder weiter benützen die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte bis Luzernerhof) oder die normal verkehrende Linie 14 (mit Halten) oder 73 ab Kante D und steigen beim Luzernerhof wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. - Travellers to Luzernerhof or further use the diverted line 24, addintional buses (direct to Luzernerhof), the regular line 14 services (all stops) or line 73 from platform D and transfer back to Luzernerhof. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:B - Matthof - - - - ch:vbl:618::02 - Brüelstrasse - - - - - - - - - open - 0420 - 2017-05-28T09:42:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Unterbruch der Linien 6 und 8 - Line 6 and 8 disrupted - - - Reisende zum Luzernerhof oder weiter benützen die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte bis Luzernerhof) ab Kante D oder die normal verkehrenden Linien 14 (mit Halten) ab Kante D und 73 ab Kante C und steigen beim Luzernerhof wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. - Travellers to Luzernerhof or further use the diverted line 24, addintional buses (direct to Luzernerhof) from platform D, the regular line 14 services (all stops) from platform D or line 73 from platform C and transfer back to Luzernerhof. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. - - - Die Störung dauert bis ca. 12:30 Uhr. - Disruption duration until 12:30pm. - - - - - - - route - - - - - ch:vbl:Entlastungsbus - Entlastungsbus - - ch:vbl:VBL006:A - Büttenhalde - - - - ch:vbl:VBL014 - 14 - - ch:vbl:VBL014:A - Brühlstrasse - - - - ch:vbl:618::01 - Brühlstrasse - destination - - - - - - - ch:vbl:VBL024 - 24 - - ch:vbl:VBL024:B - Bahnhof - - - - ch:vbl:618::01 - Brühlstrasse - destination - - - - - - - - - open - 0430 - 2017-05-28T09:42:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Unterbruch der Linien 6 und 8; Umleitung der Linien 24. - Line 6 and 8 disrupted; Line 24 diverted. - - - Benutzen Sie die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte bis Luzernerhof) oder die normal verkehrenden Linien 14 (mit Halten) und 73 bis Luzernerhof. - Use diverted line 24 and additional buses (direct to Luzernerhof) or the regular line 14 (all stops) and line 73 to Luzernerhof. - - - Die Störung dauert bis ca. 12:30 Uhr. - Disruption duration until 12:30pm. - - - - - - - route - - - - - ch:vbl:Entlastungsbus - Entlastungsbus - - ch:vbl:VBL006:A - Büttenhalde - - - - ch:vbl:121::03 - Luzernerhof - - - - - - - - - open - 0440 - 2017-05-28T09:42:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Diese Fahrt endet hier - This service terminates here - - - Einstieg der Linien 6 und 8 bei Kante A. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. - Board line 6 and 8 from platform A. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. - - - Die Störung dauert bis ca. 12:30 Uhr. - Disruption duration until 12:30pm. - - - - - - - route - - - - - ch:vbl:VBL024 - 24 - - ch:vbl:VBL024:B - Bahnhof - - - - ch:vbl:121::04 - Luzernerhof - origin - - - - - - - - - open - 0450 - 2017-05-28T09:42:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Die Umleitung endet hier - Diversion ends here - - - Umstieg auf Linie 6 und 8: Einstieg bei Kante A. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. - Transfer to line 6 and 8: Board from platform A. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. - - - - - - - route - - - - - ch:vbl:VBL014 - 14 - - ch:vbl:VBL014:B - Horw Zentrum - - - - ch:vbl:121::03 - Luzernerhof - intermediate - - - - - - - - - open - 0455 - 2017-05-28T09:42:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - - - Umstieg auf Linie 6 und 8: Einstieg bei Kante A. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. - - - - - - - route - - - - - ch:vbl:VBL024 - 24 - - ch:vbl:VBL024:B - Bahnhof - - - - ch:vbl:121::03 - Luzernerhof - origin - - - - - - - - - open - 0460 - 2017-05-28T09:42:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Die Umleitung endet hier - Diversion ends here - - - Umstieg auf die Linien 6 und 8: Einstieg bei Kante A. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. - Transfer to line 6 and 8: Board from platform A. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:B - Matthof - - - - ch:vbl:121::04 - Luzernerhof - origin - - - - - ch:vbl:VBL008 - 8 - - ch:vbl:VBL008:B - Hiertenhof - - - - ch:vbl:121::04 - Luzernerhof - origin - - - - - - - - - open - 0470 - 2017-05-28T09:42:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Normale Bedienung der Linien 6 bis Matthof und 8 bis Hirtenhof. Es muss mit Verspätungen gerechnet werden. - Regular service on line 6 to Matthof and line 8 to Hirtenhof. Expect delays. - - - Die Störung dauert bis ca. 12:30 Uhr. - Disruption duration until 12:30pm. - - - - - - - route - - - - - ch:vbl:VBL006 - 6 - - ch:vbl:VBL006:B - Matthof - - - - ch:vbl:120::02 - Schwanenplatz - intermediate - - - ch:vbl:119::01 - Bahnhof - intermediate - - - ch:vbl:118::02 - Kantonalbank - intermediate - - - ch:vbl:407::03 - Bundesplatz - intermediate - - - ch:vbl:606::02 - Werkhofstrasse - intermediate - - - ch:vbl:605::02 - Weinbergli - intermediate - - - ch:vbl:604::02 - Eisfeldstrasse - intermediate - - - ch:vbl:603::02 - Wartegg - intermediate - - - ch:vbl:602::02 - Schönbühl - intermediate - - - ch:vbl:601::01 - Matthof - destination - - - - - - - - - open - 0480 - 2017-05-28T09:42:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Es muss mit Verspätungen gerechnet werden. - Expect delays. - - - Die Störung dauert bis ca. 12:30 Uhr. - Disruption duration until 12:30pm. - - - - - - - line - - - - - ch:vbl:VBL002 - 2 - - - ch:vbl:VBL002:A - Bahnhof - - - - ch:vbl:119::06 - Bahnhof - destination - - - - - - - - - open - 0481 - 2017-05-28T09:42:00+02:00 - 1 - vbl - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Unterbruch der Linien 6 und 8 - Line 6 and 8 disrupted - - - Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die Linien 14 oder 73 und steigen Sie an der Brüelstrasse wieder um. Reisende nach dem Verkehrshaus benutzen die S3 oder das Schiff. - Transfer advice line 6 and 8: Use line 14 or 73 to Brüelstrasse and transfer back to line 6 and 8. Travellers to Verkehrshaus use the S3 or ferry. - - - Die Störung dauert bis ca. 12:30 Uhr. - Disruption duration until 12:30pm. - - - - - - - route - - - - - ch:vbl:VBL014 - 14 - - ch:vbl:VBL014:A - Brüelstrasse - - - - ch:vbl:119::08 - Bahnhof - intermediate - - - - - - - - - open - 0482 - 2017-05-28T09:42:00+02:00 - 1 - vbl - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line disruption between Luzernerhof and Verkehrshaus - - - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - - - Unterbruch der Linien 6 und 8 - Line 6 and 8 disrupted - - - Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die Linien 14 oder 73 und steigen Sie an der Brüelstrasse wieder um. Reisende nach dem Verkehrshaus benutzen die S3 oder das Schiff. - Transfer advice line 6 and 8: Use line 14 or 73 to Brüelstrasse and transfer back to line 6 and 8. Travellers to Verkehrshaus use the S3 or ferry. - - - Die Störung dauert bis ca. 12:30 Uhr. - Disruption duration until 12:30pm. - - - - - - - - -       -       + + + + 2018-10-16T10:22:30+00:00 + ch:VBL +
      http:/server/siri/20_ums
      + Pgfkw0GAsg + true + false + + 2018-10-16T10:22:30+00:00 + ch:VBL + 40599x2dsjmu8yjzy + + + 2017-05-28T09:42:00+02:00 + VBL + 5a7cf4f0-c7a5-11e8-813f-f38697968b53 + 2 + + feed + VBL + + published + + 2017-05-28T09:42:00+02:00 + 2017-05-28T17:10:00+02:00 + + fire + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + 3 + route + DE + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + http://www.vbl.ch/aktuelles/verkehrsmeldungen/stoerungen/20160603_13? + + + + + + + + ch:vbl:622 + Haldensteig + + + + + + disruption + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:2507::01 + Büttenhalde + + + ch:vbl:VBL006:A + Büttenhalde + + + + ch:vbl:621::01 + Casino-Palace + affectedStopplace + + + ch:vbl:615::01 + Europe + affectedStopplace + + + ch:vbl:616::01 + Dietschiberg + affectedStopplace + + + ch:vbl:617::01 + Verkehrshaus + affectedStopplace + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:601:01 + Matthof + + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:617::02 + Verkehrshaus + affectedStopplace + + + ch:vbl:616::02 + Dietschiberg + affectedStopplace + + + ch:vbl:615::02 + Europe + affectedStopplace + + + ch:vbl:621::02 + Casino-Palace + affectedStopplace + + + ch:vbl:622::02 + Haldensteig + affectedStopplace + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:620:01 + Würzenbach + + + ch:vbl:VBL008:A + Würzenbach + + + + ch:vbl:621::01 + Casino-Palace + affectedStopplace + + + ch:vbl:615::01 + Europe + affectedStopplace + + + ch:vbl:616::01 + Dietschiberg + affectedStopplace + + + ch:vbl:617::01 + Verkehrshaus + affectedStopplace + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:801:01 + Hirtenhof + + + ch:vbl:VBL008:B + Hirtenhof + + + + ch:vbl:617::02 + Verkehrshaus + affectedStopplace + + + ch:vbl:616::02 + Dietschiberg + affectedStopplace + + + ch:vbl:615::02 + Europe + affectedStopplace + + + ch:vbl:621::02 + Casino-Palace + affectedStopplace + + + ch:vbl:622::02 + Haldensteig + affectedStopplace + + + + + + + + true + true + + + + diverted + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:2433:01 + Tschädigen + + + ch:vbl:VBL024:A + Tschädigen + + + + ch:vbl:121::02 + affectedStopplace + + + ch:vbl:621::01 + Casino-Palace + affectedStopplace + + + ch:vbl:617::01 + Verkehrshaus + affectedStopplace + + + ch:vbl:715::01 + intermediate + + + ch:vbl:716::01 + intermediate + + + ch:vbl:1405::01 + intermediate + + + ch:vbl:1406::01 + intermediate + + + ch:vbl:1407::01 + intermediate + + + ch:vbl:1408::01 + intermediate + + + ch:vbl:1409::01 + intermediate + + + ch:vbl:1410::01 + intermediate + + + ch:vbl:1411::01 + intermediate + + + ch:vbl:1412::01 + intermediate + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:119:13 + Bahnhof + + + ch:vbl:VBL024:B + Bahnhof + + + + ch:vbl:617::02 + Verkehrshaus + affectedStopplace + + + ch:vbl:621::02 + affectedStopplace + + + ch:vbl:622::02 + affectedStopplace + + + ch:vbl:1412::02 + intermediate + + + ch:vbl:1411::02 + intermediate + + + ch:vbl:1410::02 + intermediate + + + ch:vbl:1409::02 + intermediate + + + ch:vbl:1408::02 + intermediate + + + ch:vbl:1407::02 + intermediate + + + ch:vbl:1406::02 + intermediate + + + ch:vbl:1405::02 + intermediate + + + ch:vbl:716::02 + intermediate + + + ch:vbl:715::01 + Wey Auch? + intermediate + + + + + + + + true + true + + + PT7M + + + + + + + line + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 24 + + + + + + + open + 0250 + 2017-05-28T09:42:00+02:00 + 1 + vbl + general + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Betroffen sind die Linien 6, 8 und 24 + Affected lines are 6, 8 and 24 + + + Linie 6 und 8 fallen zwischen Luzernerhof und Brüelstrasse aus. + Linie 24 wird zwischen Luzernerhof und Brüelstrasse via St. Anna umgeleitet. Ca. 7 Min. längere Fahrzeit. + Line 6 and 8 services cancelled between Luzernerhof and Brüelstrasse. + Line 24 divirted between Luzernerhof and Brüelstrasse via St. Anna. Approx. 7 min delay. + + + Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Zwischen Luzern, Bahnhof und Verkehrshaus benutzen sie die S3 oder das Schiff. + Umstiegsempfehlung für die Linien 6 und 8: Bei den Haltestellen Luzernerhof bzw. Brüelstrasse auf die umgeleitete Linie 24, die normal verkehrenden Linien 14 und 73 oder den Entlastungsbus umsteigen. + Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + Between Luzern, Bahnhof and Verkehrshaus use the S3 or ferry. + Transfer advice for line 6 and 8: At Luzernerhof or Brüelstrasse use diverted line 24, 73, additional buses or the regular line 14 services. + + + Die Störung dauert bis ca.12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:A + Büttenenhalde + + + + ch:vbl:601::01 + Matthof + + + ch:vbl:602::01 + Schönbühl + + + ch:vbl:603::03 + Wartegg + + + ch:vbl:604::01 + Eisfeldstrasse + + + ch:vbl:605::01 + Weinbergli + + + ch:vbl:606::01 + Werkhofstrasse + + + ch:vbl:407::02 + Bundesplatz + + + ch:vbl:118::01 + Kantonalbank (C) + + + ch:vbl:119::02 + Bahnhof (B) + + + ch:vbl:120::01 + Schwanenplatz + + + + + + + + + open + 0260 + 2017-05-28T09:42:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Linie 6 fällt zwischen Luzernerhof und Brüelstrasse aus. + Line 6 cancelled between Luzernerhof and Brüelstrasse. + + + Reisende nach Brüelstrasse und weiter benützen die umgeleitete Linie 24 (ohne Halte zwischen Wey und Brüelstrasse) oder die normal verkehrenden Linien 14 und 73 und steigen an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Travellers to Brüelstrasse or further use the diverted line 24 (direct between Wey and Brühlstrasse) or the regular line 14 or 73 services and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + Die Störung dauert bis ca.12:30 Uhr. + Disruption duration until 12:30pm. + + + + + open + 0270 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Linie 6 fällt zwischen Luzernerhof und Brüelstrasse aus. + Line 6 cancelled between Luzernerhof and Brüelstrasse. + + + Reisende nach Brüelstrasse und weiter benützen die umgeleitete Linie 24 (ohne Halte zwischen Wey und Brüelstrasse) oder die normal verkehrenden Linien 14 und 73 und steigen an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Travellers to Brüelstrasse or further use the diverted line 24 (direct between Wey and Brühlstrasse) or the regular services of line 14 or 73 and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + Die Störung dauert bis ca.12:30 Uhr. + Disruption duration until 12:30pm. + + + Weitere Informationen erhalten Sie unter www.vbl.ch/stoerung/haldenstrasse + For further information, please visit www.vbl.ch/stoerung/haldenstrasse + + + www.vbl.ch/stoerung/haldenstrasse + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:121::02 + Luzernerhof (B) + + + + + + + + + open + 0280 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Linie 6 wendet hier + Line 6 turns here + + + Reisende zur Brüelstrasse und weiter benützen die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte zwischen Wey und Brüelstrasse) oder die normale verkehrende Linie 14 (mit Halten) ab Kante F (Wey) oder die Linie 73 ab Kante D und steigen an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Travellers to Brüelstrasse or further use the diverted line 24, additonal buses (direct between Wey and Brüelstrasse), the regular services of line 14 (all stops) from platform F (Way) or line 73 from platform D and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:121::01 + Luzernerhof (C) + + + ch:vbl:121::02 + Luzernerhof (D) + + + + + ch:vbl:VBL008 + 8 + + + ch:vbl:121::01 + Luzernerhof (C) + + + ch:vbl:121::02 + Luzernerhof (D) + + + + + + + + + open + 0290 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8 + Line 6 and 8 disrupted + + + Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die umgeleitete Linie 24, die normal verkehrende Linie 14 und den Entlastungsbus ab Kante F (Wey) oder die Linie 73 ab Kante D und steigen Sie an der Brüelstrasse wieder um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Transfer advice line 6 and 8: To Brüelstrasse use diverted line 24, the regular line 14 services or the additional buses from platform F (Wey) or line 73 from platform D and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + Die Störung dauert bis ca.12:30 Uhr. + Disruption duration until 12:30pm. + + + Weitere Informationen erhalten Sie beim Auskunftspersonal. + For further information, please contact staff. + + + + + + + route + + + + + ch:vbl:Entlastungsbusse + + + ch:vbl:715::01 + Wey + + + + + ch:vbl:VBL014 + 14 + + + ch:vbl:715::01 + Wey + + + + + ch:vbl:VBL24 + 24 + + + ch:vbl:715::01 + Wey + + + + + + + + + open + 0300 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8; Umleitung der Linien 24. + Line 6 and 8 disrupted; Line 24 diverted. + + + Benutzen Sie die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte bis Brüelstrasse) oder die normal verkehrenden Linie 14 (mit Halten) und 73 bis Brüelstrasse. + Use diverted line 24, additional buses (direct to Brüelstrasse), regular services of line 14 (all stops) or 73 to Brüelstrasse. + + + Die Störung dauert bis ca.12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:VBL006 + 06 + + ch:vbl:VBL006:A + Büttenenhalde + + + + ch:vbl:121::02 + Luzernerhof (D) + + + + + ch:vbl:VBL008 + 08 + + ch:vbl:VBL008:A + Würzenbach + + + + ch:vbl:121::02 + Luzernerhof (D) + + + + + + + + + open + 0370 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Linie 6 und 8 fallen bis Brüelstrasse aus. Linie 24 wird zwischen Luzernerhof und Brüel via St. Anna umgeleitet. Ca. 7 Min. längere Fahrzeit. Linie 73 verkehrt wieder normal. + Line 6 and 8 cancelled services to Brüelstrasse. Line 24 services diverted between Luzernerhof and Brüel via St. Anna. Approx. 7 min delay. Line 73 back to regular service. + + + Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte zwischen Wey und Brüelstrasse) oder die normale verkehrende Linie 14 (mit Halten) ab Kante F (Wey) oder die Linie 73 ab Kante D und steigen Sie an der Brüelstrasse um. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Transfer advice for line 6 and 8: Use diverted line 73, additonal buses (direct between Wey and Brüelstrasse), the regular line 14 services (all stops) from platform F (Wey) or line 73 from platform D and transfer back at Brüelstrasse. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + Die Störung dauert bis ca.12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:A + Büttenenhalde + + + + ch:vbl:621::01 + Casino-Palace + + + ch:vbl:615::01 + Europe + + + ch:vbl:616::01 + Dietschiberg + + + ch:vbl:617::01 + Verkehrshaus + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:A + Würzenbach + + + + ch:vbl:621::01 + Casino-Palace + + + ch:vbl:615::01 + Europe + + + ch:vbl:616::01 + Dietschiberg + + + ch:vbl:617::01 + Verkehrshaus + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:VBL024:A + Tschädingen + + + + ch:vbl:621::01 + Casino-Palace + + + ch:vbl:615::01 + Europe + + + ch:vbl:616::01 + Dietschiberg + + + ch:vbl:617::01 + Verkehrshaus + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:617::02 + Verkehrshaus + + + ch:vbl:616::02 + Dietschiberg + + + ch:vbl:615::02 + Europe + + + ch:vbl:621::02 + Casino-Palace + + + ch:vbl:622::01 + Haldensteig + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:B + Hirtenhof + + + + ch:vbl:617::02 + Verkehrshaus + + + ch:vbl:616::02 + Dietschiberg + + + ch:vbl:615::02 + Europe + + + ch:vbl:621::02 + Casino-Palace + + + ch:vbl:622::01 + Haldensteig + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:VBL024:B + Bahnhof + + + + ch:vbl:617::02 + Verkehrshaus + + + ch:vbl:616::02 + Dietschiberg + + + ch:vbl:615::02 + Europe + + + ch:vbl:621::02 + Casino-Palace + + + ch:vbl:622::01 + Haldensteig + + + + + + + + + open + 0380 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Keine Bedienung der Linien 6, 8 und 24 zwischen Luzernerhof und Brüelstrasse + Line 6, 8 and 24 no service between Luzernerhof and Brüelstrasse + + + Reisende zwischen Luzernerhof und Brüelstrasse erreichen ihr Ziel nur zu Fuß. Ab Luzernerhof und Brüelstrasse verkehren die Linie auf den normalen Fahrwegen. + Travellers between Luzernerhof and Brüelstrasse can only reach their destination on foot. From Luzernerhof and Brüelstrasse lines will run on regular routes. + + + Die Störung dauert bis ca.12:30 Uhr. + Disruption duration until 12:30pm. + + + Fällt aus + Cancelled + + + + + + + route + + + + + ch:vbl:014 + 14 + + ch:vbl:VBL014:A + Brüelstrasse + + + + ch:vbl:618::01 + Brüelstrasse + destination + + + + + + + + + open + 0310 + 2017-05-28T09:42:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Fahrt endet hier + Service terminates here + + + Einstieg der Linien 6 und 8 bei Kante C. Reisende nach Verkehrshaus und Dietschiberg erreichen ihr Ziel nur zu Fuß. + Board line 6 and 8 from platform C. Travellers to Verkehrshaus and Dietschiberg can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:024 + 24 + + ch:vbl:VBL014:A + Brüelstrasse + + + + ch:vbl:618::04 + Brüelstrasse + destination + + + + + + + + + open + 0320 + 2017-05-28T09:42:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Umleitung endet hier + Diversion ends here + + + Umstieg auf Linie 6 und 8: Einstieg bei Kante C. Reisende nach Verkehrshaus und Dietschiberg erreichen ihr Ziel nur zu Fuß. + Transfer to line 6 and 8: Board from platform C. Travellers to Verkehrshaus and Dietschiberg can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL006 + 06 + + ch:vbl:VBL006:A + Büttenenhalde + + + + ch:vbl:618::03 + Brüelstrasse + + + + + ch:vbl:VBL008 + 08 + + ch:vbl:VBL008:A + Würzenbach + + + + ch:vbl:618::03 + Brüelstrasse + + + + + + + + + open + 0330 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Normale Bedienung der Linien 6 bis Büttenenhalde und 8 bis Würzenbach. Es muss mit Verspätungen gerechnet werden. + Regular service on line 6 to Büttenenhalde and 8 to Würzenbach. Expect delays. + + + Die Störung dauert bis ca.12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:A + Büttenhalde + + + + ch:vbl:2502::01 + Giseli + + + ch:vbl:2503::01 + Oberseeburg + intermediate + + + ch:vbl:2504::01 + Oberseeburghöhe + intermediate + + + ch:vbl:2505::01 + Eggen + intermediate + + + ch:vbl:2506::01 + Büttenen + intermediate + + + ch:vbl:2507::01 + Büttenenhalde + destination + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:A + Würzenbach + + + + ch:vbl:619::01 + Würzenbachmatte + intermediate + + + ch:vbl:620::01 + Würzenbach + destination + + + + + + + + + open + 0340 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Es muss mit Verspätungen gerechnet werden. + Expect delays. + + + Die Störung dauert bis ca. 12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:Entlastungsbus + Entlastungsbus + + ch:vbl:VBL006:A + Büttenhalde + + + + ch:vbl:618::04 + Brüelstrasse + + + + + + + + + open + 0350 + 2017-05-28T10:22:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Diese Fahrt endet hier + This service terminates here + + + Einstieg der Linien 6 und 8 bei Kante C. Reisende nach Verkehrshaus und Dietschiberg erreichen ihr Ziel nur zu Fuß. + Board line 6 and 8 from platform C. Travellers to Verkehrshaus and Dietschiberg can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:2507::01 + Büttenenhalde + origin + + + ch:vbl:2506::02 + Büttenen + intermediate + + + ch:vbl:2505::02 + Eggen + intermediate + + + ch:vbl:2504::02 + Oberseeburghöhe + intermediate + + + ch:vbl:2503::02 + Oberseeburg + intermediate + + + ch:vbl:2502::02 + Giseli + intermediate + + + + + + + + + open + 0390 + 2017-05-28T09:42:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Linie 6 fällt zwischen Brüelstrasse und Luzernerhof aus. + Line 6 cancelled between Brüelstrasse and Luzernerhof. + + + Reisende nach Luzernerhof oder weiter benützen die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte zwischen Brüelstrasse und Luzernerhof) oder die normal verkehrenden Linien 14 (mit Halten) und 73 bis Luzernerhof und steigen dort wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. + Travellers to Luzernerhof or further use the diverted line 24, additional buses (direct between Brühlstrasse and Luzernerhof), the regular line 14 services (all stop) or line 73 to Luzernhof and transfer there. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. + + + Die Störung dauert bis ca. 12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:2507::01 + Büttenenhalde + origin + + + ch:vbl:2506::02 + Büttenen + intermediate + + + ch:vbl:2505::02 + Eggen + intermediate + + + ch:vbl:2504::02 + Oberseeburghöhe + intermediate + + + ch:vbl:2503::02 + Oberseeburg + intermediate + + + ch:vbl:2502::02 + Giseli + intermediate + + + + + + + + + open + 0400 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Linie 6 fällt zwischen Brüelstrasse und Luzernerhof aus. + Line 6 cancelled between Brüelstrasse and Luzernerhof. + + + Reisende nach Luzernerhof oder weiter benützen die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte zwischen Brüelstrasse und Luzernerhof) oder die normal verkehrenden Linien 14 (mit Halten) und 73 bis Luzernerhof und steigen dort wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. + Travellers to Luzernerhof or further use the diverted line 24, the additional buses (direct between Brühlstrasse and Luzernerhof), the regular line 14 services (all stop) or line 73 to Luzernhof and transfer there. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. + + + Die Störung dauert bis ca. 12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:618::02 + Brüelstrasse + + + + + + + + + open + 0410 + 2017-05-28T09:42:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Linie 6 wendet hier + Line 6 turns here + + + Reisende zum Luzernerhof oder weiter benützen die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte bis Luzernerhof) oder die normal verkehrende Linie 14 (mit Halten) oder 73 ab Kante D und steigen beim Luzernerhof wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. + Travellers to Luzernerhof or further use the diverted line 24, addintional buses (direct to Luzernerhof), the regular line 14 services (all stops) or line 73 from platform D and transfer back to Luzernerhof. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:618::02 + Brüelstrasse + + + + + + + + + open + 0420 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8 + Line 6 and 8 disrupted + + + Reisende zum Luzernerhof oder weiter benützen die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte bis Luzernerhof) ab Kante D oder die normal verkehrenden Linien 14 (mit Halten) ab Kante D und 73 ab Kante C und steigen beim Luzernerhof wieder um. Reisende nach Verkehrshaus, Dietschiberg, Europe, Casino-Palace und Haldensteig erreichen ihr Ziel nur zu Fuß. + Travellers to Luzernerhof or further use the diverted line 24, addintional buses (direct to Luzernerhof) from platform D, the regular line 14 services (all stops) from platform D or line 73 from platform C and transfer back to Luzernerhof. Travellers to Verkehrshaus, Dietschiberg, Europe, Casino-Palace and Haldensteig can only reach their destination on foot. + + + Die Störung dauert bis ca. 12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:Entlastungsbus + Entlastungsbus + + ch:vbl:VBL006:A + Büttenhalde + + + + ch:vbl:VBL014 + 14 + + ch:vbl:VBL014:A + Brühlstrasse + + + + ch:vbl:618::01 + Brühlstrasse + destination + + + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:VBL024:B + Bahnhof + + + + ch:vbl:618::01 + Brühlstrasse + destination + + + + + + + + + open + 0430 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8; Umleitung der Linien 24. + Line 6 and 8 disrupted; Line 24 diverted. + + + Benutzen Sie die umgeleitete Linie 24 und den Entlastungsbus (ohne Halte bis Luzernerhof) oder die normal verkehrenden Linien 14 (mit Halten) und 73 bis Luzernerhof. + Use diverted line 24 and additional buses (direct to Luzernerhof) or the regular line 14 (all stops) and line 73 to Luzernerhof. + + + Die Störung dauert bis ca. 12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:Entlastungsbus + Entlastungsbus + + ch:vbl:VBL006:A + Büttenhalde + + + + ch:vbl:121::03 + Luzernerhof + + + + + + + + + open + 0440 + 2017-05-28T09:42:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Diese Fahrt endet hier + This service terminates here + + + Einstieg der Linien 6 und 8 bei Kante A. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Board line 6 and 8 from platform A. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + Die Störung dauert bis ca. 12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:VBL024:B + Bahnhof + + + + ch:vbl:121::04 + Luzernerhof + origin + + + + + + + + + open + 0450 + 2017-05-28T09:42:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Umleitung endet hier + Diversion ends here + + + Umstieg auf Linie 6 und 8: Einstieg bei Kante A. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Transfer to line 6 and 8: Board from platform A. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL014 + 14 + + ch:vbl:VBL014:B + Horw Zentrum + + + + ch:vbl:121::03 + Luzernerhof + intermediate + + + + + + + + + open + 0455 + 2017-05-28T09:42:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + + + Umstieg auf Linie 6 und 8: Einstieg bei Kante A. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + + + + + + + route + + + + + ch:vbl:VBL024 + 24 + + ch:vbl:VBL024:B + Bahnhof + + + + ch:vbl:121::03 + Luzernerhof + origin + + + + + + + + + open + 0460 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Die Umleitung endet hier + Diversion ends here + + + Umstieg auf die Linien 6 und 8: Einstieg bei Kante A. Reisende nach Haldensteig, Casino-Palace, Europe, Dietschiberg und Verkehrshaus erreichen ihr Ziel nur zu Fuß. + Transfer to line 6 and 8: Board from platform A. Travellers to Haldensteig, Casino-Palace, Europe, Dietschiberg and Verkehrshaus can only reach their destination on foot. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:121::04 + Luzernerhof + origin + + + + + ch:vbl:VBL008 + 8 + + ch:vbl:VBL008:B + Hiertenhof + + + + ch:vbl:121::04 + Luzernerhof + origin + + + + + + + + + open + 0470 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Normale Bedienung der Linien 6 bis Matthof und 8 bis Hirtenhof. Es muss mit Verspätungen gerechnet werden. + Regular service on line 6 to Matthof and line 8 to Hirtenhof. Expect delays. + + + Die Störung dauert bis ca. 12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:VBL006 + 6 + + ch:vbl:VBL006:B + Matthof + + + + ch:vbl:120::02 + Schwanenplatz + intermediate + + + ch:vbl:119::01 + Bahnhof + intermediate + + + ch:vbl:118::02 + Kantonalbank + intermediate + + + ch:vbl:407::03 + Bundesplatz + intermediate + + + ch:vbl:606::02 + Werkhofstrasse + intermediate + + + ch:vbl:605::02 + Weinbergli + intermediate + + + ch:vbl:604::02 + Eisfeldstrasse + intermediate + + + ch:vbl:603::02 + Wartegg + intermediate + + + ch:vbl:602::02 + Schönbühl + intermediate + + + ch:vbl:601::01 + Matthof + destination + + + + + + + + + open + 0480 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Es muss mit Verspätungen gerechnet werden. + Expect delays. + + + Die Störung dauert bis ca. 12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + line + + + + + ch:vbl:VBL002 + 2 + + + ch:vbl:VBL002:A + Bahnhof + + + + ch:vbl:119::06 + Bahnhof + destination + + + + + + + + + open + 0481 + 2017-05-28T09:42:00+02:00 + 1 + vbl + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8 + Line 6 and 8 disrupted + + + Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die Linien 14 oder 73 und steigen Sie an der Brüelstrasse wieder um. Reisende nach dem Verkehrshaus benutzen die S3 oder das Schiff. + Transfer advice line 6 and 8: Use line 14 or 73 to Brüelstrasse and transfer back to line 6 and 8. Travellers to Verkehrshaus use the S3 or ferry. + + + Die Störung dauert bis ca. 12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + route + + + + + ch:vbl:VBL014 + 14 + + ch:vbl:VBL014:A + Brüelstrasse + + + + ch:vbl:119::08 + Bahnhof + intermediate + + + + + + + + + open + 0482 + 2017-05-28T09:42:00+02:00 + 1 + vbl + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line disruption between Luzernerhof and Verkehrshaus + + + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + + + Unterbruch der Linien 6 und 8 + Line 6 and 8 disrupted + + + Umstiegsempfehlung für Linien 6 und 8: Benutzen Sie bis Brüelstrasse die Linien 14 oder 73 und steigen Sie an der Brüelstrasse wieder um. Reisende nach dem Verkehrshaus benutzen die S3 oder das Schiff. + Transfer advice line 6 and 8: Use line 14 or 73 to Brüelstrasse and transfer back to line 6 and 8. Travellers to Verkehrshaus use the S3 or ferry. + + + Die Störung dauert bis ca. 12:30 Uhr. + Disruption duration until 12:30pm. + + + + + + + + +       +       diff --git a/examples/siri_exm_SX/VDV736_exm/SX_1247_end_message.xml b/examples/siri_exm_SX/VDV736_exm/SX_1247_end_message.xml index ec713b1a..ba27997c 100644 --- a/examples/siri_exm_SX/VDV736_exm/SX_1247_end_message.xml +++ b/examples/siri_exm_SX/VDV736_exm/SX_1247_end_message.xml @@ -1,397 +1,397 @@ - - - - 2018-10-04T12:22:00+00:00 - ch:VBL -
      http:/server/siri/20_ums
      - JFI2d2mWP - true - false - - 2018-10-04T12:22:00+00:00 - ch:VBL - 40599x2dsjmu8yjzy - - - 2017-05-28T12:22:00+02:00 - VBL - 1 - 5 - - feed - VBL - - closing - - - 2017-05-28T12:22:00+02:00 - 2017-05-28T17:10:00+02:00 - - fire - Feuerwehreinsatz in der Haldenstrasse - Fire brigade action at Haldenstrasse - 3 - line - false - DE - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line interruption between Luzernerhof and Verkehrshaus - - - - ch:vbl:622 - Haldensteig - - - - - - disturbanceRectified - - - - - ch:vbl:VBL006 - 6 - - - ch:vbl:VBL008 - 8 - - - ch:vbl:VBL024 - 24 - - - - - - false - - - - - - - line - - - - - ch:vbl:VBL006 - 6 - - - ch:vbl:VBL008 - 8 - - - ch:vbl:VBL024 - 14 - - - ch:vbl:VBL024 - 24 - - - ch:vbl:VBL024 - 73 - - - - - - - open - 0510 - 2017-05-28T12:22:00+02:00 - 1 - vbl - VBL - general - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line interruption between Luzernerhof and Verkehrshaus - - - Der Streckenunterbruch zwischen Luzernerhof und Brüelstrasse ist behoben. - The route disruption between Luzernerhof and Brüelstrasse is resolved. - - - Die Linien 6, 8, 24 und 73 verkehren wieder gemäß Fahrplan. - Line 6, 8, 24 and 73 are back to regular service. - - - - - - - line - - - - - ch:vbl:VBL006 - 6 - - - ch:vbl:VBL008 - 8 - - - ch:vbl:VBL024 - 14 - - - ch:vbl:VBL024 - 24 - - - ch:vbl:VBL024 - 73 - - - - - - - open - 0510 - 2017-05-28T12:22:00+02:00 - 1 - vbl - VBL - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line interruption between Luzernerhof and Verkehrshaus - - - Der Streckenunterbruch zwischen Luzernerhof und Brüelstrasse ist behoben. - The route disruption between Luzernerhof and Brüelstrasse is resolved. - - - Die Linien 6, 8, 24 und 73 verkehren wieder gemäß Fahrplan. - Line 6, 8, 24 and 73 are back to regular service. - - - - - - - line - - - - - ch:vbl:VBL006 - 6 - - - ch:vbl:VBL008 - 8 - - - ch:vbl:VBL024 - 14 - - - ch:vbl:VBL024 - 24 - - - ch:vbl:VBL024 - 73 - - - - - - - open - 0510 - 2017-05-28T12:22:00+02:00 - 1 - vbl - VBL - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line interruption between Luzernerhof and Verkehrshaus - - - Der Streckenunterbruch zwischen Luzernerhof und Brüelstrasse ist behoben. - The route disruption between Luzernerhof and Brüelstrasse is resolved. - - - Die Linien 6, 8, 24 und 73 verkehren wieder gemäß Fahrplan. - Line 6, 8, 24 and 73 are back to regular service. - - - - - - - line - - - - - ch:vbl:VBL006 - 6 - - - ch:vbl:VBL008 - 8 - - - ch:vbl:VBL024 - 24 - - - - - - - open - - 2017-05-28T12:47:00+02:00 - 2017-05-28T13:15:00+02:00 - - 0510 - 2017-05-28T12:47:00+02:00 - 1 - vbl - VBL - general - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line interruption between Luzernerhof and Verkehrshaus - - - Der Streckenunterbruch zwischen Luzernerhof und Brüelstrasse ist behoben. - The route disruption between Luzernerhof and Brüelstrasse is resolved. - - - Die Linien 6, 8, 24 und 73 verkehren wieder gemäß Fahrplan. - Line 6, 8, 24 and 73 are back to regular service. - - - - - - - line - - - - - ch:vbl:VBL006 - 6 - - - ch:vbl:VBL008 - 8 - - - ch:vbl:VBL024 - 24 - - - - - - - open - - 2017-05-28T12:47:00+02:00 - 2017-05-28T13:15:00+02:00 - - 0510 - 2017-05-28T12:47:00+02:00 - 1 - vbl - VBL - vehicleJourney - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line interruption between Luzernerhof and Verkehrshaus - - - Der Streckenunterbruch zwischen Luzernerhof und Brüelstrasse ist behoben. - The route disruption between Luzernerhof and Brüelstrasse is resolved. - - - Die Linien 6, 8, 24 und 73 verkehren wieder gemäß Fahrplan. - Line 6, 8, 24 and 73 are back to regular service. - - - - - - - line - - - - - ch:vbl:VBL006 - 6 - - - ch:vbl:VBL008 - 8 - - - ch:vbl:VBL024 - 24 - - - - - - - open - - 2017-05-28T12:47:00+02:00 - 2017-05-28T13:15:00+02:00 - - 0510 - 2017-05-28T12:47:00+02:00 - 1 - vbl - VBL - stopPoint - - L - - Unterbruch zwischen Luzernerhof und Verkehrshaus - Line interruption between Luzernerhof and Verkehrshaus - - - Der Streckenunterbruch zwischen Luzernerhof und Brüelstrasse ist behoben. - The route disruption between Luzernerhof and Brüelstrasse is resolved. - - - Die Linien 6, 8, 24 und 73 verkehren wieder gemäß Fahrplan. - Line 6, 8, 24 and 73 are back to regular service. - - - - - - - - -       -       + + + + 2018-10-04T12:22:00+00:00 + ch:VBL +
      http:/server/siri/20_ums
      + JFI2d2mWP + true + false + + 2018-10-04T12:22:00+00:00 + ch:VBL + 40599x2dsjmu8yjzy + + + 2017-05-28T12:22:00+02:00 + VBL + 1 + 5 + + feed + VBL + + closing + + + 2017-05-28T12:22:00+02:00 + 2017-05-28T17:10:00+02:00 + + fire + Feuerwehreinsatz in der Haldenstrasse + Fire brigade action at Haldenstrasse + 3 + line + false + DE + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line interruption between Luzernerhof and Verkehrshaus + + + + ch:vbl:622 + Haldensteig + + + + + + disturbanceRectified + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 24 + + + + + + false + + + + + + + line + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 14 + + + ch:vbl:VBL024 + 24 + + + ch:vbl:VBL024 + 73 + + + + + + + open + 0510 + 2017-05-28T12:22:00+02:00 + 1 + vbl + VBL + general + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line interruption between Luzernerhof and Verkehrshaus + + + Der Streckenunterbruch zwischen Luzernerhof und Brüelstrasse ist behoben. + The route disruption between Luzernerhof and Brüelstrasse is resolved. + + + Die Linien 6, 8, 24 und 73 verkehren wieder gemäß Fahrplan. + Line 6, 8, 24 and 73 are back to regular service. + + + + + + + line + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 14 + + + ch:vbl:VBL024 + 24 + + + ch:vbl:VBL024 + 73 + + + + + + + open + 0510 + 2017-05-28T12:22:00+02:00 + 1 + vbl + VBL + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line interruption between Luzernerhof and Verkehrshaus + + + Der Streckenunterbruch zwischen Luzernerhof und Brüelstrasse ist behoben. + The route disruption between Luzernerhof and Brüelstrasse is resolved. + + + Die Linien 6, 8, 24 und 73 verkehren wieder gemäß Fahrplan. + Line 6, 8, 24 and 73 are back to regular service. + + + + + + + line + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 14 + + + ch:vbl:VBL024 + 24 + + + ch:vbl:VBL024 + 73 + + + + + + + open + 0510 + 2017-05-28T12:22:00+02:00 + 1 + vbl + VBL + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line interruption between Luzernerhof and Verkehrshaus + + + Der Streckenunterbruch zwischen Luzernerhof und Brüelstrasse ist behoben. + The route disruption between Luzernerhof and Brüelstrasse is resolved. + + + Die Linien 6, 8, 24 und 73 verkehren wieder gemäß Fahrplan. + Line 6, 8, 24 and 73 are back to regular service. + + + + + + + line + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 24 + + + + + + + open + + 2017-05-28T12:47:00+02:00 + 2017-05-28T13:15:00+02:00 + + 0510 + 2017-05-28T12:47:00+02:00 + 1 + vbl + VBL + general + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line interruption between Luzernerhof and Verkehrshaus + + + Der Streckenunterbruch zwischen Luzernerhof und Brüelstrasse ist behoben. + The route disruption between Luzernerhof and Brüelstrasse is resolved. + + + Die Linien 6, 8, 24 und 73 verkehren wieder gemäß Fahrplan. + Line 6, 8, 24 and 73 are back to regular service. + + + + + + + line + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 24 + + + + + + + open + + 2017-05-28T12:47:00+02:00 + 2017-05-28T13:15:00+02:00 + + 0510 + 2017-05-28T12:47:00+02:00 + 1 + vbl + VBL + vehicleJourney + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line interruption between Luzernerhof and Verkehrshaus + + + Der Streckenunterbruch zwischen Luzernerhof und Brüelstrasse ist behoben. + The route disruption between Luzernerhof and Brüelstrasse is resolved. + + + Die Linien 6, 8, 24 und 73 verkehren wieder gemäß Fahrplan. + Line 6, 8, 24 and 73 are back to regular service. + + + + + + + line + + + + + ch:vbl:VBL006 + 6 + + + ch:vbl:VBL008 + 8 + + + ch:vbl:VBL024 + 24 + + + + + + + open + + 2017-05-28T12:47:00+02:00 + 2017-05-28T13:15:00+02:00 + + 0510 + 2017-05-28T12:47:00+02:00 + 1 + vbl + VBL + stopPoint + + L + + Unterbruch zwischen Luzernerhof und Verkehrshaus + Line interruption between Luzernerhof and Verkehrshaus + + + Der Streckenunterbruch zwischen Luzernerhof und Brüelstrasse ist behoben. + The route disruption between Luzernerhof and Brüelstrasse is resolved. + + + Die Linien 6, 8, 24 und 73 verkehren wieder gemäß Fahrplan. + Line 6, 8, 24 and 73 are back to regular service. + + + + + + + + +       +       diff --git a/examples/siri_exm_SX/exx_situationExchangeResponse.xml b/examples/siri_exm_SX/exx_situationExchangeResponse.xml index d43b823a..3df28732 100644 --- a/examples/siri_exm_SX/exx_situationExchangeResponse.xml +++ b/examples/siri_exm_SX/exx_situationExchangeResponse.xml @@ -1,280 +1,280 @@ - - - - - - 2004-12-17T09:30:46-05:00 - KUBRICK - true - false - - - 2004-12-17T09:30:46-05:00 - - - 2001-12-17T09:30:47.0Z - de - RAILCO01 - 000354 - 0 - - - 2001-12-17T09:30:47.0Z - de - RAILCO01 - 000354 - 0 - - - - de - phone - 01223333337654 - 03274 - 2001-12-17T09:30:47.0Z - - verified - open - certain - - 2001-12-17T09:30:47.0Z - 2001-12-17T10:30:47.0Z - - bombExplosion - severe - 3 - public - point - Bomb at Barchester station - Building evacuated. Avoid station until further notice - - - - - - - BAAR0003 - Barchester Station - unknown - - -180 - -90 - 1 - - - - - - BArF001 - - - BAR00021 - Platfrom 3 - - - - - - - - - 2001-12-17T09:30:47.0Z - 2001-12-17T10:30:47.0Z - - unknown - unknown - - true - true - - - noAlighting - noBoarding - - - - - - true - true - false - - - true - false - - - true - true - true - - - - - - 2001-12-17T09:30:47.0Z - de - RAILCO01 - 000354 - 0 - - - 2001-12-17T09:30:47.0Z - de - RAILCO01 - 000354 - 0 - - - - de - phone - 01223333337654 - 03274 - 2001-12-17T09:30:47.0Z - - verified - open - certain - - 2001-12-17T09:30:47.0Z - 2001-12-17T10:30:47.0Z - - bombExplosion - severe - 3 - public - point - Jam on the access road to Barchester Station - Grislock and panic - - - - - - - BAAR0003 - Barchester Station - unknown - - -180 - -90 - 1 - - - - - - BArF001 - - - BAR00021 - Platfrom 3 - - - - - - - - - 2001-12-17T09:30:47.0Z - 2001-12-17T10:30:47.0Z - - delay - severe - - - - - true - true - false - - - true - false - - - true - true - true - - - - - - - - - + + + + + + 2004-12-17T09:30:46-05:00 + KUBRICK + true + false + + + 2004-12-17T09:30:46-05:00 + + + 2001-12-17T09:30:47.0Z + de + RAILCO01 + 000354 + 0 + + + 2001-12-17T09:30:47.0Z + de + RAILCO01 + 000354 + 0 + + + + de + phone + 01223333337654 + 03274 + 2001-12-17T09:30:47.0Z + + verified + open + certain + + 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z + + bombExplosion + severe + 3 + public + point + Bomb at Barchester station + Building evacuated. Avoid station until further notice + + + + + + + BAAR0003 + Barchester Station + unknown + + -180 + -90 + 1 + + + + + + BArF001 + + + BAR00021 + Platfrom 3 + + + + + + + + + 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z + + unknown + unknown + + true + true + + + noAlighting + noBoarding + + + + + + true + true + false + + + true + false + + + true + true + true + + + + + + 2001-12-17T09:30:47.0Z + de + RAILCO01 + 000354 + 0 + + + 2001-12-17T09:30:47.0Z + de + RAILCO01 + 000354 + 0 + + + + de + phone + 01223333337654 + 03274 + 2001-12-17T09:30:47.0Z + + verified + open + certain + + 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z + + bombExplosion + severe + 3 + public + point + Jam on the access road to Barchester Station + Grislock and panic + + + + + + + BAAR0003 + Barchester Station + unknown + + -180 + -90 + 1 + + + + + + BArF001 + + + BAR00021 + Platfrom 3 + + + + + + + + + 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z + + delay + severe + + + + + true + true + false + + + true + false + + + true + true + true + + + + + + + + + diff --git a/examples/siri_exm_SX/exx_situationExchange_ATOC.xml b/examples/siri_exm_SX/exx_situationExchange_ATOC.xml index 8318ce35..31355973 100644 --- a/examples/siri_exm_SX/exx_situationExchange_ATOC.xml +++ b/examples/siri_exm_SX/exx_situationExchange_ATOC.xml @@ -1,101 +1,101 @@ - - - - 2001-12-17T09:30:47.0Z - de - RAILCO01 - 000354 - 0 - - - 2001-12-17T09:30:47.0Z - de - RAILCO01 - 000354 - 0 - - - - de - phone - 01223333337654 - 03274 - 2001-12-17T09:30:47.0Z - - verified - open - certain - - 2001-12-17T09:30:47.0Z - 2001-12-17T10:30:47.0Z - - bombExplosion - severe - 3 - public - point - Bomb at Barchester station - Building evacuated. Avoid station until further notice - - - - - - - BAAR0003 - Barchester Station - unknown - - -180 - -90 - 1 - - - - - - BArF001 - - - BAR00021 - Platform 3 - - - - - - - - - 2001-12-17T09:30:47.0Z - 2001-12-17T10:30:47.0Z - - delay - severe - - true - true - - - noAlighting - noBoarding - - - - - - true - true - false - - - true - false - - - true - true - true - - - + + + + 2001-12-17T09:30:47.0Z + de + RAILCO01 + 000354 + 0 + + + 2001-12-17T09:30:47.0Z + de + RAILCO01 + 000354 + 0 + + + + de + phone + 01223333337654 + 03274 + 2001-12-17T09:30:47.0Z + + verified + open + certain + + 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z + + bombExplosion + severe + 3 + public + point + Bomb at Barchester station + Building evacuated. Avoid station until further notice + + + + + + + BAAR0003 + Barchester Station + unknown + + -180 + -90 + 1 + + + + + + BArF001 + + + BAR00021 + Platform 3 + + + + + + + + + 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z + + delay + severe + + true + true + + + noAlighting + noBoarding + + + + + + true + true + false + + + true + false + + + true + true + true + + + diff --git a/examples/siri_exm_SX/exx_situationExchange_Pt.xml b/examples/siri_exm_SX/exx_situationExchange_Pt.xml index 89b9dba4..6300c46d 100644 --- a/examples/siri_exm_SX/exx_situationExchange_Pt.xml +++ b/examples/siri_exm_SX/exx_situationExchange_Pt.xml @@ -1,101 +1,101 @@ - - - - 2001-12-17T09:30:47.0Z - de - RAILCO01 - 000354 - 0 - - - 2001-12-17T09:30:47.0Z - de - RAILCO01 - 000354 - 0 - - - - de - phone - 01223333337654 - 03274 - 2001-12-17T09:30:47.0Z - - verified - open - certain - - 2001-12-17T09:30:47.0Z - 2001-12-17T10:30:47.0Z - - bombExplosion - severe - 3 - public - point - Bomb at Barchester station - Building evacuated. Avoid station until further notice - - - - - - - BAAR0003 - Barchester Station - unknown - - -180 - -90 - 1 - - - - - - BArF001 - - - BAR00021 - Platfrom 3 - - - - - - - - - 2001-12-17T09:30:47.0Z - 2001-12-17T10:30:47.0Z - - delay - severe - - true - true - - - noAlighting - noBoarding - - - - - - true - true - false - - - true - false - - - true - true - true - - - + + + + 2001-12-17T09:30:47.0Z + de + RAILCO01 + 000354 + 0 + + + 2001-12-17T09:30:47.0Z + de + RAILCO01 + 000354 + 0 + + + + de + phone + 01223333337654 + 03274 + 2001-12-17T09:30:47.0Z + + verified + open + certain + + 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z + + bombExplosion + severe + 3 + public + point + Bomb at Barchester station + Building evacuated. Avoid station until further notice + + + + + + + BAAR0003 + Barchester Station + unknown + + -180 + -90 + 1 + + + + + + BArF001 + + + BAR00021 + Platfrom 3 + + + + + + + + + 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z + + delay + severe + + true + true + + + noAlighting + noBoarding + + + + + + true + true + false + + + true + false + + + true + true + true + + + diff --git a/examples/siri_exm_SX/exx_situationExchange_capabilityResponse.xml b/examples/siri_exm_SX/exx_situationExchange_capabilityResponse.xml index f54f6856..02ca5f45 100644 --- a/examples/siri_exm_SX/exx_situationExchange_capabilityResponse.xml +++ b/examples/siri_exm_SX/exx_situationExchange_capabilityResponse.xml @@ -1,69 +1,69 @@ - - - - 2001-12-17T09:30:47-05:00 - http://www.mytransportco.eu - true - - - cpidId001 - - String - - - - - true - true - - - true - false - - true - true - false - false - - - PT60M - false - true - true - - - en-uk - - - - false - - - - - - - - true - true - - - true - - - true - - - - - NADER - - true - - - true - - - - - + + + + 2001-12-17T09:30:47-05:00 + http://www.mytransportco.eu + true + + + cpidId001 + + String + + + + + true + true + + + true + false + + true + true + false + false + + + PT60M + false + true + true + + + en-uk + + + + false + + + + + + + + true + true + + + true + + + true + + + + + NADER + + true + + + true + + + + + diff --git a/examples/siri_exm_SX/exx_situationExchange_request.xml b/examples/siri_exm_SX/exx_situationExchange_request.xml index 4749cd84..72cbbec1 100644 --- a/examples/siri_exm_SX/exx_situationExchange_request.xml +++ b/examples/siri_exm_SX/exx_situationExchange_request.xml @@ -1,32 +1,32 @@ - - - - - - - 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 - - - - + + + + + + + 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 + + + + diff --git a/examples/siri_exm_SX/exx_situationExchange_request_simple.xml b/examples/siri_exm_SX/exx_situationExchange_request_simple.xml index 5ed7ee31..6c25828d 100644 --- a/examples/siri_exm_SX/exx_situationExchange_request_simple.xml +++ b/examples/siri_exm_SX/exx_situationExchange_request_simple.xml @@ -1,21 +1,21 @@ - - - - - 2004-12-17T09:30:47-05:00 - NADER - - 2004-12-17T09:30:47-05:00 - - line - 52 - - - - + + + + + 2004-12-17T09:30:47-05:00 + NADER + + 2004-12-17T09:30:47-05:00 + + line + 52 + + + + diff --git a/examples/siri_exm_SX/exx_situationExchange_response.xml b/examples/siri_exm_SX/exx_situationExchange_response.xml index bb15c8a8..559f2edc 100644 --- a/examples/siri_exm_SX/exx_situationExchange_response.xml +++ b/examples/siri_exm_SX/exx_situationExchange_response.xml @@ -1,278 +1,278 @@ - - - - - - 2004-12-17T09:30:46-05:00 - KUBRICK - true - false - - - 2004-12-17T09:30:46-05:00 - - - 2001-12-17T09:30:47.0Z - de - RAILCO01 - 000354 - 0 - - - 2001-12-17T09:30:47.0Z - de - RAILCO01 - 000354 - 0 - - - - de - phone - 01223333337654 - 03274 - 2001-12-17T09:30:47.0Z - - verified - open - certain - - 2001-12-17T09:30:47.0Z - 2001-12-17T10:30:47.0Z - - bombExplosion - severe - 3 - public - point - Bomb at Barchester station - Building evacuated. Avoid station until further notice - - - - - - - BAAR0003 - Barchester Station - unknown - - -180 - -90 - 1 - - - - - - BArF001 - - - BAR00021 - Platfrom 3 - - - - - - - - - 2001-12-17T09:30:47.0Z - 2001-12-17T10:30:47.0Z - - unknown - unknown - - true - true - - - noAlighting - noBoarding - - - - - - true - true - false - - - true - false - - - true - true - true - - - - - - 2001-12-17T09:30:47.0Z - de - RAILCO01 - 000354 - 0 - - - 2001-12-17T09:30:47.0Z - de - RAILCO01 - 000354 - 0 - - - - de - phone - 01223333337654 - 03274 - 2001-12-17T09:30:47.0Z - - verified - open - certain - - 2001-12-17T09:30:47.0Z - 2001-12-17T10:30:47.0Z - - bombExplosion - severe - 3 - public - point - Jam on the access road to Barchester Station - Grislock and panic - - - - - - - BAAR0003 - Barchester Station - unknown - - -180 - -90 - 1 - - - - - - BArF001 - - - BAR00021 - Platfrom 3 - - - - - - - - - 2001-12-17T09:30:47.0Z - 2001-12-17T10:30:47.0Z - - delay - severe - - - - - true - true - false - - - true - false - - - true - true - true - - - - - - - - - + + + + + + 2004-12-17T09:30:46-05:00 + KUBRICK + true + false + + + 2004-12-17T09:30:46-05:00 + + + 2001-12-17T09:30:47.0Z + de + RAILCO01 + 000354 + 0 + + + 2001-12-17T09:30:47.0Z + de + RAILCO01 + 000354 + 0 + + + + de + phone + 01223333337654 + 03274 + 2001-12-17T09:30:47.0Z + + verified + open + certain + + 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z + + bombExplosion + severe + 3 + public + point + Bomb at Barchester station + Building evacuated. Avoid station until further notice + + + + + + + BAAR0003 + Barchester Station + unknown + + -180 + -90 + 1 + + + + + + BArF001 + + + BAR00021 + Platfrom 3 + + + + + + + + + 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z + + unknown + unknown + + true + true + + + noAlighting + noBoarding + + + + + + true + true + false + + + true + false + + + true + true + true + + + + + + 2001-12-17T09:30:47.0Z + de + RAILCO01 + 000354 + 0 + + + 2001-12-17T09:30:47.0Z + de + RAILCO01 + 000354 + 0 + + + + de + phone + 01223333337654 + 03274 + 2001-12-17T09:30:47.0Z + + verified + open + certain + + 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z + + bombExplosion + severe + 3 + public + point + Jam on the access road to Barchester Station + Grislock and panic + + + + + + + BAAR0003 + Barchester Station + unknown + + -180 + -90 + 1 + + + + + + BArF001 + + + BAR00021 + Platfrom 3 + + + + + + + + + 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z + + delay + severe + + + + + true + true + false + + + true + false + + + true + true + true + + + + + + + + + diff --git a/examples/siri_exm_SX/exx_situationExchange_road.xml b/examples/siri_exm_SX/exx_situationExchange_road.xml index 6560d66c..8abeeff7 100644 --- a/examples/siri_exm_SX/exx_situationExchange_road.xml +++ b/examples/siri_exm_SX/exx_situationExchange_road.xml @@ -1,204 +1,204 @@ - - - - 2001-12-17T09:30:47.0Z - de - RAILCO01 - 000354 - 0 - - - 2001-12-17T09:30:47.0Z - de - RAILCO01 - 000354 - 0 - - - - de - phone - 01223333337654 - 03274 - 2001-12-17T09:30:47.0Z - - verified - open - certain - - 2001-12-17T09:30:47.0Z - 2001-12-17T10:30:47.0Z - - bombExplosion - severe - 3 - public - point - Jam on the access road to Barchester Station - Grislock and panic - - - - - - - BAAR0003 - Barchester Station - unknown - - -180 - -90 - 1 - - - - - - BArF001 - - - BAR00021 - Platfrom 3 - - - - - - - - - 2001-12-17T09:30:47.0Z - 2001-12-17T10:30:47.0Z - - delay - severe - - - - - true - true - false - - - true - false - - - true - true - true - - - - + + + + 2001-12-17T09:30:47.0Z + de + RAILCO01 + 000354 + 0 + + + 2001-12-17T09:30:47.0Z + de + RAILCO01 + 000354 + 0 + + + + de + phone + 01223333337654 + 03274 + 2001-12-17T09:30:47.0Z + + verified + open + certain + + 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z + + bombExplosion + severe + 3 + public + point + Jam on the access road to Barchester Station + Grislock and panic + + + + + + + BAAR0003 + Barchester Station + unknown + + -180 + -90 + 1 + + + + + + BArF001 + + + BAR00021 + Platfrom 3 + + + + + + + + + 2001-12-17T09:30:47.0Z + 2001-12-17T10:30:47.0Z + + delay + severe + + + + + true + true + false + + + true + false + + + true + true + true + + + + diff --git a/examples/siri_exm_SX/exx_situationExchange_subscriptionRequest.xml b/examples/siri_exm_SX/exx_situationExchange_subscriptionRequest.xml index 7670c3cf..07d33360 100644 --- a/examples/siri_exm_SX/exx_situationExchange_subscriptionRequest.xml +++ b/examples/siri_exm_SX/exx_situationExchange_subscriptionRequest.xml @@ -1,20 +1,20 @@ - - - - - 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 - - - - + + + + + 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 + + + + diff --git a/examples/siri_exm_VM/exv_vehicleMonitoring_capabilitiesResponse.xml b/examples/siri_exm_VM/exv_vehicleMonitoring_capabilitiesResponse.xml index 1d45773f..47c915df 100644 --- a/examples/siri_exm_VM/exv_vehicleMonitoring_capabilitiesResponse.xml +++ b/examples/siri_exm_VM/exv_vehicleMonitoring_capabilitiesResponse.xml @@ -1,80 +1,80 @@ - - - - 2001-12-17T09:30:47.0Z - http://www.mytransportco.eu - true - - - cpidId001 - - 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 - - - - - - + + + + 2001-12-17T09:30:47.0Z + http://www.mytransportco.eu + true + + + cpidId001 + + 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/examples/siri_exm_VM/exv_vehicleMonitoring_request.xml b/examples/siri_exm_VM/exv_vehicleMonitoring_request.xml index 5461b910..1e562ad0 100644 --- a/examples/siri_exm_VM/exv_vehicleMonitoring_request.xml +++ b/examples/siri_exm_VM/exv_vehicleMonitoring_request.xml @@ -1,34 +1,34 @@ - - - - - - - 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 - true - - - + + + + + + + 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 + true + + + diff --git a/examples/siri_exm_VM/exv_vehicleMonitoring_request_simple.xml b/examples/siri_exm_VM/exv_vehicleMonitoring_request_simple.xml index 0d67ca33..8320e4e9 100644 --- a/examples/siri_exm_VM/exv_vehicleMonitoring_request_simple.xml +++ b/examples/siri_exm_VM/exv_vehicleMonitoring_request_simple.xml @@ -1,22 +1,22 @@ - - - - - - 2004-12-17T09:30:47-05:00 - NADER - - 2004-12-17T09:30:47-05:00 - - VEHPT55 - - basic - - - + + + + + + 2004-12-17T09:30:47-05:00 + NADER + + 2004-12-17T09:30:47-05:00 + + VEHPT55 + + basic + + + diff --git a/examples/siri_exm_VM/exv_vehicleMonitoring_response.xml b/examples/siri_exm_VM/exv_vehicleMonitoring_response.xml index b9a14d7e..211f5dba 100644 --- a/examples/siri_exm_VM/exv_vehicleMonitoring_response.xml +++ b/examples/siri_exm_VM/exv_vehicleMonitoring_response.xml @@ -1,159 +1,159 @@ - - - - - - 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 - VEH987659 - - - - HLTST012 - Church - - - - - - - 2004-12-17T09:30:47-05:00 - 9876542 - - 2001-12-17 - 09867 - - Line123 - Out - Gone home - - hello delivery - - - + + + + + + 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 + VEH987659 + + + + HLTST012 + Church + + + + + + + 2004-12-17T09:30:47-05:00 + 9876542 + + 2001-12-17 + 09867 + + Line123 + Out + Gone home + + hello delivery + + + diff --git a/examples/siri_exm_VM/exv_vehicleMonitoring_response_simple.xml b/examples/siri_exm_VM/exv_vehicleMonitoring_response_simple.xml index acec57c4..f4c4c3b5 100644 --- a/examples/siri_exm_VM/exv_vehicleMonitoring_response_simple.xml +++ b/examples/siri_exm_VM/exv_vehicleMonitoring_response_simple.xml @@ -1,62 +1,62 @@ - - - - - - 2004-12-17T09:30:47-05:00 - NADER - - - 2004-12-17T09:30:47-05:00 - NADER - 00047 - - 2004-12-17T09:30:47-05:00 - 2004-12-17T09:30:47-05:00 - ACT019456 - - - Line123 - - 2004-12-17 - 987675 - - 123 - - 0.1 - 53.55 - - 123 - VEH987654 - - - - - 2004-12-17T09:30:47-05:00 - 2004-12-17T09:30:47-05:00 - MYACACT - - - - Line123 - - 2004-12-17 - Outbound - - - 0 - 53.5 - - 70 - VEH987659 - - - - - + + + + + + 2004-12-17T09:30:47-05:00 + NADER + + + 2004-12-17T09:30:47-05:00 + NADER + 00047 + + 2004-12-17T09:30:47-05:00 + 2004-12-17T09:30:47-05:00 + ACT019456 + + + Line123 + + 2004-12-17 + 987675 + + 123 + + 0.1 + 53.55 + + 123 + VEH987654 + + + + + 2004-12-17T09:30:47-05:00 + 2004-12-17T09:30:47-05:00 + MYACACT + + + + Line123 + + 2004-12-17 + Outbound + + + 0 + 53.5 + + 70 + VEH987659 + + + + + diff --git a/examples/siri_exm_VM/exv_vehicleMonitoring_responsex_simple.xml b/examples/siri_exm_VM/exv_vehicleMonitoring_responsex_simple.xml index acec57c4..f4c4c3b5 100644 --- a/examples/siri_exm_VM/exv_vehicleMonitoring_responsex_simple.xml +++ b/examples/siri_exm_VM/exv_vehicleMonitoring_responsex_simple.xml @@ -1,62 +1,62 @@ - - - - - - 2004-12-17T09:30:47-05:00 - NADER - - - 2004-12-17T09:30:47-05:00 - NADER - 00047 - - 2004-12-17T09:30:47-05:00 - 2004-12-17T09:30:47-05:00 - ACT019456 - - - Line123 - - 2004-12-17 - 987675 - - 123 - - 0.1 - 53.55 - - 123 - VEH987654 - - - - - 2004-12-17T09:30:47-05:00 - 2004-12-17T09:30:47-05:00 - MYACACT - - - - Line123 - - 2004-12-17 - Outbound - - - 0 - 53.5 - - 70 - VEH987659 - - - - - + + + + + + 2004-12-17T09:30:47-05:00 + NADER + + + 2004-12-17T09:30:47-05:00 + NADER + 00047 + + 2004-12-17T09:30:47-05:00 + 2004-12-17T09:30:47-05:00 + ACT019456 + + + Line123 + + 2004-12-17 + 987675 + + 123 + + 0.1 + 53.55 + + 123 + VEH987654 + + + + + 2004-12-17T09:30:47-05:00 + 2004-12-17T09:30:47-05:00 + MYACACT + + + + Line123 + + 2004-12-17 + Outbound + + + 0 + 53.5 + + 70 + VEH987659 + + + + + diff --git a/examples/siri_exm_VM/exv_vehicleMonitoring_subscriptionRequest.xml b/examples/siri_exm_VM/exv_vehicleMonitoring_subscriptionRequest.xml index 76bbfaba..e28fad6e 100644 --- a/examples/siri_exm_VM/exv_vehicleMonitoring_subscriptionRequest.xml +++ b/examples/siri_exm_VM/exv_vehicleMonitoring_subscriptionRequest.xml @@ -1,34 +1,34 @@ - - - - - - 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 - - - + + + + + + 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 + + + diff --git a/examples/siri_exu_capability/exd_allServices_capabilitiesRequest.xml b/examples/siri_exu_capability/exd_allServices_capabilitiesRequest.xml index 5db39348..16484fe1 100644 --- a/examples/siri_exu_capability/exd_allServices_capabilitiesRequest.xml +++ b/examples/siri_exu_capability/exd_allServices_capabilitiesRequest.xml @@ -1,38 +1,38 @@ - - - - - 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 - - - + + + + + 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/examples/siri_exu_capability/exd_allServices_capabilitiesResponse.xml b/examples/siri_exu_capability/exd_allServices_capabilitiesResponse.xml index 17ef992e..f65d2e7e 100644 --- a/examples/siri_exu_capability/exd_allServices_capabilitiesResponse.xml +++ b/examples/siri_exu_capability/exd_allServices_capabilitiesResponse.xml @@ -1,494 +1,494 @@ - - - - - 2004-12-17T09:30:47-05:00 - KUBRICK - - 2004-12-17T09:30:47-05:00 - true - - - - true - false - - - true - false - - false - true - false - true - false - - - httpPost - none - - - true - true - true - true - - - en - wgs84 - - - true - - - false - false - false - false - - - - - 2004-12-17T09:30:47-05:00 - true - - - - true - false - - - true - false - - false - true - false - true - false - - - httpPost - none - - - true - true - - - en - WGS84 - - - true - true - - - false - false - false - false - - - - - - 2004-12-17T09:30:47-05:00 - my123 - true - - - - true - false - - - true - false - - false - true - false - true - false - - - httpPost - none - - - true - true - true - - - en - WGS84 - true - true - - - false - false - false - false - - - - - 2004-12-17T09:30:47-05:00 - my123 - true - - - - true - false - - - true - false - - false - true - false - true - false - - - httpPost - none - - - PT60M - true - true - true - true - false - false - - - en - WGS84 - true - true - true - calls - true - true - true - true - true - - - true - true - - - false - false - false - false - - - true - - - - - 2004-12-17T09:30:47-05:00 - abcde - true - - - - true - false - - - true - false - - false - true - false - true - false - - - httpPost - none - - - PT60M - true - true - true - true - - - en - WGS84 - true - normal - true - true - true - true - - - false - true - - - false - false - false - false - - - false - false - - - - - 2004-12-17T09:30:47-05:00 - abcde - true - - - - true - false - - - true - false - - false - true - false - true - false - - - httpPost - none - - - true - true - - - en - WGS84 - false - - - false - false - - - false - false - false - false - - - - - 2004-12-17T09:30:47-05:00 - abcde - true - - - - true - false - - - true - false - - false - true - false - true - false - - - httpPost - none - - - true - true - - - en - WGS84 - false - - - false - false - - - false - false - false - false - - - - - 2004-12-17T09:30:47-05:00 - abcde - true - - - - true - false - - - true - false - - false - true - false - true - false - - - httpPost - none - - - PT10M - true - - - en - WGS84 - - - false - false - - - - - 2004-12-17T09:30:47-05:00 - abcde - true - - - - true - false - - - true - false - - false - true - false - true - false - - - httpPost - none - - - PT60M - true - true - true - true - true - true - false - false - true - - - en - WHS84 - true - - - false - false - - - false - false - false - - - true - true - - - - - 2004-12-17T09:30:47-05:00 - abcde - true - - - - true - false - - - true - false - - false - true - false - true - false - - - httpPost - none - - - - true - true - true - - - true - true - true - true - - - en - WGS84 - true - - - true - true - - - false - false - false - - - - - - + + + + + 2004-12-17T09:30:47-05:00 + KUBRICK + + 2004-12-17T09:30:47-05:00 + true + + + + true + false + + + true + false + + false + true + false + true + false + + + httpPost + none + + + true + true + true + true + + + en + wgs84 + + + true + + + false + false + false + false + + + + + 2004-12-17T09:30:47-05:00 + true + + + + true + false + + + true + false + + false + true + false + true + false + + + httpPost + none + + + true + true + + + en + WGS84 + + + true + true + + + false + false + false + false + + + + + + 2004-12-17T09:30:47-05:00 + my123 + true + + + + true + false + + + true + false + + false + true + false + true + false + + + httpPost + none + + + true + true + true + + + en + WGS84 + true + true + + + false + false + false + false + + + + + 2004-12-17T09:30:47-05:00 + my123 + true + + + + true + false + + + true + false + + false + true + false + true + false + + + httpPost + none + + + PT60M + true + true + true + true + false + false + + + en + WGS84 + true + true + true + calls + true + true + true + true + true + + + true + true + + + false + false + false + false + + + true + + + + + 2004-12-17T09:30:47-05:00 + abcde + true + + + + true + false + + + true + false + + false + true + false + true + false + + + httpPost + none + + + PT60M + true + true + true + true + + + en + WGS84 + true + normal + true + true + true + true + + + false + true + + + false + false + false + false + + + false + false + + + + + 2004-12-17T09:30:47-05:00 + abcde + true + + + + true + false + + + true + false + + false + true + false + true + false + + + httpPost + none + + + true + true + + + en + WGS84 + false + + + false + false + + + false + false + false + false + + + + + 2004-12-17T09:30:47-05:00 + abcde + true + + + + true + false + + + true + false + + false + true + false + true + false + + + httpPost + none + + + true + true + + + en + WGS84 + false + + + false + false + + + false + false + false + false + + + + + 2004-12-17T09:30:47-05:00 + abcde + true + + + + true + false + + + true + false + + false + true + false + true + false + + + httpPost + none + + + PT10M + true + + + en + WGS84 + + + false + false + + + + + 2004-12-17T09:30:47-05:00 + abcde + true + + + + true + false + + + true + false + + false + true + false + true + false + + + httpPost + none + + + PT60M + true + true + true + true + true + true + false + false + true + + + en + WHS84 + true + + + false + false + + + false + false + false + + + true + true + + + + + 2004-12-17T09:30:47-05:00 + abcde + true + + + + true + false + + + true + false + + false + true + false + true + false + + + httpPost + none + + + + true + true + true + + + true + true + true + true + + + en + WGS84 + true + + + true + true + + + false + false + false + + + + + + diff --git a/examples/siri_exu_discovery/exd_lines_discoveryRequest.xml b/examples/siri_exu_discovery/exd_lines_discoveryRequest.xml index 5212c22f..dfb70907 100644 --- a/examples/siri_exu_discovery/exd_lines_discoveryRequest.xml +++ b/examples/siri_exu_discovery/exd_lines_discoveryRequest.xml @@ -1,10 +1,10 @@ - - - - - 2004-12-17T09:30:47-05:00 - NADER - MYAGENCY - full - - + + + + + 2004-12-17T09:30:47-05:00 + NADER + MYAGENCY + full + + diff --git a/examples/siri_exu_discovery/exd_lines_discoveryResponse.xml b/examples/siri_exu_discovery/exd_lines_discoveryResponse.xml index f3eaa311..7e593de1 100644 --- a/examples/siri_exu_discovery/exd_lines_discoveryResponse.xml +++ b/examples/siri_exu_discovery/exd_lines_discoveryResponse.xml @@ -1,77 +1,77 @@ - - - - - 2004-12-17T09:30:47-05:00 - true - - Line564 - 564 - true - - - PLace45 - Paradise - - - - - DIR01 - Outbound - - - - - ST001 - Alpha Road - - Line564 - 22 - - - 0.11 - 53.01 - - 1 - - - ST002 - Beta Street - - Line564 - - - 0.12 - 53.02 - - 2 - - - ST003 - Charley Square - SA2001 - - - Line564 - NORTH - - 44 - - - 0.13 - 53.03 - - 3 - - - - - - - DIR02 - Inbound - - - - - + + + + + 2004-12-17T09:30:47-05:00 + true + + Line564 + 564 + true + + + PLace45 + Paradise + + + + + DIR01 + Outbound + + + + + ST001 + Alpha Road + + Line564 + 22 + + + 0.11 + 53.01 + + 1 + + + ST002 + Beta Street + + Line564 + + + 0.12 + 53.02 + + 2 + + + ST003 + Charley Square + SA2001 + + + Line564 + NORTH + + 44 + + + 0.13 + 53.03 + + 3 + + + + + + + DIR02 + Inbound + + + + + diff --git a/examples/siri_exu_discovery/exd_productCategories_discoveryRequest.xml b/examples/siri_exu_discovery/exd_productCategories_discoveryRequest.xml index dd3a984a..b43b6308 100644 --- a/examples/siri_exu_discovery/exd_productCategories_discoveryRequest.xml +++ b/examples/siri_exu_discovery/exd_productCategories_discoveryRequest.xml @@ -1,8 +1,8 @@ - - - - - 2004-12-17T09:30:47-05:00 - NADER - - + + + + + 2004-12-17T09:30:47-05:00 + NADER + + diff --git a/examples/siri_exu_discovery/exd_productCategories_discoveryResponse.xml b/examples/siri_exu_discovery/exd_productCategories_discoveryResponse.xml index dc643c66..9ba6abc6 100644 --- a/examples/siri_exu_discovery/exd_productCategories_discoveryResponse.xml +++ b/examples/siri_exu_discovery/exd_productCategories_discoveryResponse.xml @@ -1,13 +1,13 @@ - - - - - 2004-12-17T09:30:47-05:00 - true - - CAT1 - Express - http://www.speedy.com - - - + + + + + 2004-12-17T09:30:47-05:00 + true + + CAT1 + Express + http://www.speedy.com + + + diff --git a/examples/siri_exu_discovery/exd_serviceFeatures_discoveryRequest.xml b/examples/siri_exu_discovery/exd_serviceFeatures_discoveryRequest.xml index 6c9980b4..123c7e2e 100644 --- a/examples/siri_exu_discovery/exd_serviceFeatures_discoveryRequest.xml +++ b/examples/siri_exu_discovery/exd_serviceFeatures_discoveryRequest.xml @@ -1,8 +1,8 @@ - - - - - 2004-12-17T09:30:47-05:00 - NADER - - + + + + + 2004-12-17T09:30:47-05:00 + NADER + + diff --git a/examples/siri_exu_discovery/exd_serviceFeatures_discoveryResponse.xml b/examples/siri_exu_discovery/exd_serviceFeatures_discoveryResponse.xml index 8a1a6a26..a60e8270 100644 --- a/examples/siri_exu_discovery/exd_serviceFeatures_discoveryResponse.xml +++ b/examples/siri_exu_discovery/exd_serviceFeatures_discoveryResponse.xml @@ -1,18 +1,18 @@ - - - - - 2004-12-17T09:30:47-05:00 - true - - CAT01 - Express - express.gif - - - CAT021 - School - school.gif - - - + + + + + 2004-12-17T09:30:47-05:00 + true + + CAT01 + Express + express.gif + + + CAT021 + School + school.gif + + + diff --git a/examples/siri_exu_discovery/exd_stopPoints_discoveryRequest.xml b/examples/siri_exu_discovery/exd_stopPoints_discoveryRequest.xml index b447e1cd..70e377e3 100644 --- a/examples/siri_exu_discovery/exd_stopPoints_discoveryRequest.xml +++ b/examples/siri_exu_discovery/exd_stopPoints_discoveryRequest.xml @@ -1,24 +1,24 @@ - - - - - 2004-12-17T09:30:47-05:00 - NADER - - - - 0.1 - 53.1 - - - 0.2 - 53.2 - - - - + + + + + 2004-12-17T09:30:47-05:00 + NADER + + + + 0.1 + 53.1 + + + 0.2 + 53.2 + + + + diff --git a/examples/siri_exu_discovery/exd_stopPoints_discoveryResponse.xml b/examples/siri_exu_discovery/exd_stopPoints_discoveryResponse.xml index a31cd8e2..e385eb56 100644 --- a/examples/siri_exu_discovery/exd_stopPoints_discoveryResponse.xml +++ b/examples/siri_exu_discovery/exd_stopPoints_discoveryResponse.xml @@ -1,47 +1,47 @@ - - - - - 2004-12-17T09:30:47-05:00 - true - - HLTS0001 - true - Stop 101 - - - S123 - Shelter - http://www.mybus.org/shelter.jpg - - - - A23 - - - 0.1 - 53 - - - - HLTS0002 - true - Stop 102 - - - S123 - Shelter - http://www.mybus.org/shelter.jpg - - - - A23 - A24 - - - 0.12 - 53.1 - - - - + + + + + 2004-12-17T09:30:47-05:00 + true + + HLTS0001 + true + Stop 101 + + + S123 + Shelter + http://www.mybus.org/shelter.jpg + + + + A23 + + + 0.1 + 53 + + + + HLTS0002 + true + Stop 102 + + + S123 + Shelter + http://www.mybus.org/shelter.jpg + + + + A23 + A24 + + + 0.12 + 53.1 + + + + diff --git a/examples/siri_exu_discovery/exd_vehicleFeatures_discoveryRequest.xml b/examples/siri_exu_discovery/exd_vehicleFeatures_discoveryRequest.xml index 5d2cd9d8..74a921dd 100644 --- a/examples/siri_exu_discovery/exd_vehicleFeatures_discoveryRequest.xml +++ b/examples/siri_exu_discovery/exd_vehicleFeatures_discoveryRequest.xml @@ -1,8 +1,8 @@ - - - - - 2004-12-17T09:30:47-05:00 - NADER - - + + + + + 2004-12-17T09:30:47-05:00 + NADER + + diff --git a/examples/siri_exu_discovery/exd_vehicleFeatures_discoveryResponse.xml b/examples/siri_exu_discovery/exd_vehicleFeatures_discoveryResponse.xml index 348c9e71..0fc767a5 100644 --- a/examples/siri_exu_discovery/exd_vehicleFeatures_discoveryResponse.xml +++ b/examples/siri_exu_discovery/exd_vehicleFeatures_discoveryResponse.xml @@ -1,17 +1,17 @@ - - - - - 2004-12-17T09:30:47-05:00 - - VF01 - Low doors - lowdoors.gif - - - VF02 - Wheelkchair - spastic.gif - - - + + + + + 2004-12-17T09:30:47-05:00 + + VF01 + Low doors + lowdoors.gif + + + VF02 + Wheelkchair + spastic.gif + + + diff --git a/release-notes/ReadMe.txt b/release-notes/ReadMe.txt index a2201ff4..0c64160f 100644 --- a/release-notes/ReadMe.txt +++ b/release-notes/ReadMe.txt @@ -1,454 +1,454 @@ -Server Interface for Real-time Information -============================================ - -v2.0 As CEN draft European Standard - prCEN/EN EN 00278181 - prCEN/EN EN 15531 - -v1.0 As CEN Technical Standard - CEN/TS 00278181 - CEN/TS 15531 - -(C) Copyright CEN SIRI 2004-2013 - -=========================================== -This ReadMe describes Changes to the SIRI schema up to v2.0 version 2.0 since v1.3 (2012/03/30) - - -======================== - Future: handbook UML DIagrams -======================== -Changes to SIRI schema v2.0 since v1.4 - - 2015.05.13 Bug fix (from french feedback) SIRI 2.0p - * replacement of "NotifyExtension" (appearing 10 times) with "SiriExtension" in siri_wsConsumer.wsdl in order to ensure compatibility with the Document version - - 2015.05.13 Bug fix (from SG7 feedback) SIRI 2.0o - * update annotation in siri.xsd and and siri_all_functionalService.xsd (to add siri__facilityMonitoring_service.xsd ...) - * siri.xsd: move of a SituationExchangeDelivery, renamed IncludedSituationExchangeDelivery, before other complemented service deliveries. - * siri_situationExchange_service.xsd: addition of IncludedSituationExchangeDelivery element - - 2015.05.11 Bug fix (from SG7 skype meeting on May 11th 2015) SIRI 2.0o - * Allow multiple tags within an extension (reapply lost chnage from 2012.06.18 SIRI 2.0d) - siri_utility.xsd - * siri_estimatedVehicleJourney.xsd : in EstimatedTimetableAlterationGroup, addition of FramedVehicleJourneyRef as an alternative to DatedVehicleJourneyRef (choice) and deprecation of DatedVehicleJourneyRef and EstimatedVehicleJourneyCode - * siri_datedVehicleJourney.xsd : DatedVehicleJourneyCode is now optional - * siri.xsd: SituationExchangeDelivery now can be provided as a complement to any other Service delivery (and can still be provided standalone)... note that the SituationExchangeDelivery must be after the other Delivery to get a validating, non-ambiguous XSD. - * siri_estimatedVehicleJourney.xsd : EstimatedVehicleJourneyStructure brought back to SIRI 2.0k situation - * Replacement of EstimatedJourneyInfoGroup by JourneyEndTimesGroup - * Replacement of inclusion of siri_journey.xsd by siri_monitoredVehicleJourney.xsd - * Replacement of EstimatedRealtimeInfoGroup by journeyProgressGroup - * Replacement of OperationalInfoGroup by TrainOperationalInfoGroup - - - 2015.02.10 Bug fix (from french feedback) - * [fr] siri_wsProducer-Framework.xsd: use of siri:CheckStatusRequestStructure instead of siri:RequestStructure for checkStatus (one addition non mandatory version attribute) - * [fr] siri_wsProducer.wsdl: use of siri:CheckStatusRequestStructure instead of siri:RequestStructure for checkStatus (one addition non mandatory version attribute) - * [fr] siri_wsConsumer-Framework.xsd: update type of NotifySubscriptionTerminated to siri:SubscriptionTerminatedNotificationStructure (instead of TerminateSubbscriptionREquest !) - - 2014.11.17 Correction (from french feedback) - * [fr] fix RPC-Document compatibility issue for GetSiri in Document WSDL (siri_wsProducer-Services.xsd): addition of Request/Answer wrapper - * [fr] fix WSDL Document issue: GetCapability was using Answer instead of Request (siri_wsProducer-DiscoveryCapability.xsd) - * [fr] fix RPC-Document compatibility issue for LinesDiscovery,ConnectionLinksDiscovery,StopPointsDiscovery in Document WSDL (siri_wsProducer-DiscoveryCapability.xsd): deletion of useless «xxxAnswerInfo» wrapper - - 2014.06.20 Correction and revisions from Stenungsund - [Part2] - * [fx] Document SubscriptionTerminatedNotification and add error code. (siri-requests.xsd) - * [fx] StopDiscovery response. Add RouteDirection. Rename JourneyPattern/Stops to JourneyPattern/StopsInPattern SubscriptionTerminatedNotification and add error code. (siri-requests.xsd) - * [de] Add Extensions to discovery requests. (siri_discovery.xsd) - - [Part3] - * [ch] Add origin display whereever destination display as per Cologne meeting (siri-Journey.xsd, siri-DatedVehicleJourney.xsd, - * [xh[ Add OriginAtDestination wherever destination display as per Cologne meeting (siri-Journey.xsd) - * [fx] Set default on new DetailLevels on ConnectionMonitoring and EstimatedJourney for backwards compatability. (siri_connectionMonitoring_ervice.xsd siri_EstimatedTimetable_service.xsd - * [ch] Add recordedCall to Estimated jouernesy to allow times for passed stops to be included. iri_EstimatedVehicleJourney.xsd - [Part5 SituationExchange] - * [de] Add missing AffectedFacility that was in document but missing from schema. VehicleJourney, STop & StopComponent siri_situationAffects.xsd. -emporal filter siri_situationExchaneg_service.xsd. - * [de] Add temporal filter to request with ValidityPeriod in siri_situationExchange_service.xsd. - * [se] Add end time precision to halfopen time rangefor input a siri_time.xsd. - * [se] Add end time status to halfopen time range output siri_time.xsd. - * [fr] Add additional small delay bands siri_situation.xsd - * [de] Add IncludeOnly-IfInPublicationWindow to situation request temporal filter siri_situationExchange_service.xsd. - * [fx] StopPlaceFilterGroup: add missing component ref and facility that was in doc but missing from schema siri_situationExchange_service.xsd. - * [fx] Add missing AccessFeature type to AFfectedStopPlaceComponent siri_situationAffects.xsd. - * [fx] Correct cardinality on FacilitRef on request to match doc siri_situationExchaneg_service.xsd. - * [fx] Correct spec to include projection attributes for AFfectedStopPlaceComponent doc. - * [doc] Document FacilityRef as part of request doc - * [doc] Document Access Mode as part of request doc - * [doc] Document Scope as part of request doc - * [doc] Document RoadFilter and Accessibility need filter as part of request doc - * [doc] Correct Documentation of AfFfectedRoads as part of Delivery doc - * [doc/fx] Correct Documentation of capability Matrix and update in schemas well siri_situationExchange_service.xsd. - * [doc/fx] Correct Documentation of Reason codes and correct in schema siri_reasons.xsd - * [doc] Add Annex D to Doc on GTFS real-time mapping - - 2014.05.26 Changes to answer comment from the EU ballot - * [fr] Addition of SubscriptionTerminatedNotification (XSD and WSDL SOAP Web Services(RPC/Document & WSDL2)) - - File siri_common_services.xsd: Addition of SubscriptionTerminatedNotification (SubscriptionTerminatedNotification element + SubscriptionTerminatedNotificationStructure ) - - File siri.xsd: addition of SubscriptionTerminatedNotification in servicesResponseGroup - - Update of siri_wsConsumer-Document.wsdl, siri_wsConsumer.wsdl, siri_wsConsumer-WSDL2.wsdl to add a NotifyTerminateSubscription - - File siri_wsConsumer-Framework.xsd: Addition of WsSubscriptionTerminatedNotificationStructure and NotifySubscriptionTerminated - * [fr] Added ParameterName [0..*] to ParametersIgnoredErrorStructure (siri_request_errorConditions.xsd) - * [fr] Added ExtensionName [0..*] to UnknownExtensionsErrorStructure (siri_request_errorConditions.xsd) - * [fr] Added InvalidRef [0..*] to InvalidDataReferencesErrorStructure (siri_request_errorConditions.xsd) - * [fr] Added Vesion attribute (non mandatory) to CheckStatus request (siri_common_services.xsd) - * [fr] ChangeBeforeUpdates not anymore mandatory in EstimatedTimetableSubscriptionPolicyGroup - * [fr] added optional RecordedAtTime to EstimatedVehicleJourney - * [fr] added ConnectionLinksDiscovery service to WSDL (RPC/Document & WSDL2) (and siri_wsProducerDicoveryCapability.xsd) - - - 2013.06.26 French comments (compatibility issue) - * [fr] Change SOAP Web Service namesapce to http://wsdl.siri.org.uk (previously http://wsdl.siri.org.uk/siri) - - * [fr] update EstimatedVehicleJourney in order to have it consistent with MonitoredVehicleJourney and Siri 2.0 - - use JourneyEndTimesGroup in place of EstimatedJourneyInfoGroup - - use JourneyProgressGroup in place of EstimatedRealtimeInfoGroup - - use TrainOperationalInfoGroup in place of OperationalInfoGroup - - addCallRailGroup (containing PlateformTraversal ) and CallRealTime to EstimatedCall - 2013.02.20 WG3 SG meeting Munich - * [se] Add JourneyEndNamesInfoGroup to EstimatedDirectionAtStop to DestinationDisplayAtStop - This makes destination name available on EstimatedJourney. - * [us] Rename ProgrssStatusEnumeration to CallStatusENumeration to avoid confusion. - * [fr} Add FramedVehicleJourney references as alternative wherever a simple VehicleJourneyRef exists and deprecate use of simple reference. - - DatedVehicleJourney - identifier group. - - FacilityMonitoring - FacilityLocation. - - SituationExchangeService - SituationFilterGroup. - - SituationExchangeService - AffectedVehicleJourneyRef. - * [ch] StopTimeTableCancellation - Add Reason code to be consistet with St opMonitoring. - * [de] ArrivalTimesDepartureGroup - add ExpectedArrivalPredictionQuality element. - * [fr] MonitoredStopVisit Cancellation make VisitNo LineRef DirectionRef optional. - * [fr] EstimatedTimetable, COnnectionMonitoring add detailed level to reqyest - - * [fr] Make AdditionalVersionRefS to OperationalInfoGroup. - * [fr] Add JourneyPatternName The JourneyPatternInfoGroup. - - 2013.02.11 - * [SE] Align documentation and XSD. See comments in individual xsd-files. - * [SE] Add StopNotice and StopNoticeCancellation to StopMonitoringDelivery. - * [SE] Revise ProductionTimetableDelviery to correct ServcieJourneyInterchange to include visit numbers. - * [FR] Updated with latest WDSL from CD. - - - 2012.08.01 - SIRI 2.0e.1. - * [DE] Align documentation and XSD using GT's amendments. - * [FR] Update WDSL and add WSDL2.. Add WSDl chapter by CD to gudie.. - * [DE] Add Delegation elements to more mesages. - * [US] Revise Siri Lite chapter. - *[DE] Revise commends on Prediction quality based on CB's comments - - 2012.06.18 - SIRI 2.0d.2. - * [CH] Allow multiple tags within an extension - * [CH] Make most NL String elements unbounded to allow for NL translations. x dx - Add IncludeTranslations to RequestPolicy. - Add Translations to Cpabilities - * [DE] Add PredictionQuality elements to MonitoredVehicleJourney Onward Call. & EstimatedVehcielJourney - * [FR] Add GroupOfLinesRef to JourneyPattenrInforGroup on MonitoredVehcile Joruney and elsewhere - * [FR] Add Extensions tag to EstimatedTimetableSubscriptionRequest x tx - * [FR] Add Extensions tag to FacilityMonitoringSubscriptionRequest x - * [FR] Add Extensions tag to SituationExchangeSubscriptionRequest x - * [FR] Add Extensions tag to ConnectionMonitoringSubscriptionRequest x tx - * [FR] Add Extensions tag to Connection|TimetableSubscriptionRequest x tx - * [FR] Add Extensions tag to VehicleMonitoringSubscriptionRequest x tx - * [FR] Add Extensions tag to Terminate SubscriptionRequest x tx - * [DE] Correct EstimatedTimetable EstimatedServiceJourneyInterchange x tx - *[US] Add SIRILite chapter to manual. - * [DE] Add DelegatorAddress and DelegatorRef to servicerequest and service response. x tx - * [SE] Correct latestExopectedArrivalTime - * [SE] Add Vehicle Status add additional arrival and departure states - - - 2012.05.31 - SIRI 2.0d.1. - * [MTA] Discovery Revise StopLine discovery to include line direction x - * [MTA] Discovery Revise Line discovery to include Direction/Line x - * [MTA] Correcct typo in name of RouteDirection x - * [Init] Add DriverRef to vehiclejourney x tx - - SIRI 2.0c.1. - 2012.06.11 - SIRI 2.0c - Relax typing on NotifcationRef to be normalized string x - Add wsdl subdirectory for wsd .xsds x - - 2012.06.08 - WSDL [FR] x - In siri-wsProducer-Document.xsd rename StopMonitoringType and StopMonitoringMultipleType to StopMonitoringRequestType to StopMonitoringMultipleRequestType (for more consistent naming) - Add comment to point out that usage of SOAP Fault are now deprecated - Add comment to point out that usage of MultipleStopMonitoring is now deprecated (utilise GetSiriService) - Addition of a Document Wrapped encoding style fully compatible with the RPC Style (Producer and Consumer) - Add GetSiriService in RPC and Document Wrapped mode - Addition of StopDiscovery and LineDiscovery - Cleaning of xmlns:xxx in siri_wsProducer-Document - Suppression of comments on and (for http://www.validwsdl.com/ compliance) .. in poducer and producer-Document WSDL - Rename of Port/Binding/Service in order to clearly diffirentiate them - Change to + - - 2012.05.17 - SIRI 2.0b.3 - [MTA] Add filtering to StopPoints and Lines Discovery requests by point + radius x - [MTA] Add filtering to Lines Discovery request by LineRef and Direction x - [MTA] Add stops in pattern to Lines Discovery, with OnwardLinkShap and LineDetailParameter x - [NeTEx] Add StopAreaRef & url to annotated stop on StopDiscovery x - [General] Correct capability definition - - 2012.04.18 - SIRI 2.0b.2 - [VDV] Add ValidUntil to individual SIRI-CM MonitoredFeederArrival x e - [VDV] Add ValidUntil to individual SIRI-SM MonitoredStopVisit x e - - - [MTA] Add DistanceFromStop and NumberOfStopsAway to to MonitoredCall & OnwardsCall x tx - - 2012.03.23 - SIRI 2.0b.1 - [MTA] Add filtering to StopPoints request by point + radius - - 2012.03.23 - WDSL - Add explicit namespace to body x - Use a SIRI namespace http://wsdl.siri.org.uk/siri x - Correct GetStopTimentable to have soapAction x - Turn annotations into comments x - Use FaultLiteral x - - SIRI 2.0a - Changes to framework - [VDV] Add DataReady to CheckStatus response x. tx. - - JourneyInfo group SIRI-ST SIRI-SM SIRI-VM SIRI-PT SIRI-ET MonitoredJourney, etc - [VDV] Add PublicContact & Operations contact to JourneyInfo group in x tx - [VDV] Add ViaPriority to ViaNames using a new ViaNameStructure x tx - [VDV] at DirectionAtOrigin name to JourneyInfo SIRI-PT, SIRI-ET, SIRI-SM. SIRI-VM - - [VDV] Add EstimatedServiceInterchange to EstimatedTimetableDelivery x tx. - [VDV] Add ServiceJourneyInterchange to ProductionTimetableDelivery SIRI PT x tx - - Changes to MonitoredVehicleJourney SIRI-SM SIRI-VM - [VDV, SE] Add EarliestExpectedArrivalTimeForVehicle to Arrival Times Group x tx - [VDV] Add ProvisionalExpectedDepartureTime to Departure Times Group x tx - [VDV, SE] Add latesExpectedArrivalTimeForVehicle to Departure Times Group x tx - [SE] Add Aimed and expected Platform assignments to CALLs including a reference code. - - [FR] Add FirstOrLastJourney to JourneyTimesGroup x.tx. - [FR] add ArrivalOperatorRefs and DepartureOperatorRefs to Call arrival and Departure - [VDV] Add Velocity to MonitoredVehicleJourney JoueyProgerssGroup SIRI-SM and SIRI-VM - - [FR] Add AimedLatestPassengerAccessTime to MonitoredCall & OnwardsCall x tx - [MTA,FR,UK] Add ArrivalProximityText & DepartureProximityText to MonitoredCall & OnwardsCall x tx - [FR, MTA] Add Velocity to Journey & VelocityType x tx - - StopMonitoringRequest SIRI-SM - [VDV] Add Minimum-StopVisits¬PerVia to STopMonitoringRequestPolicy x tx - [VDV] Add HasMinimum-StopVisits¬Via to STopMonitoringCapabilities x tx - - StopMonitoringDelivery SIRI-SM - [FR] Add Service Exception element - [VDV] Add delivery variant to LineNote - [MTA] Add MaximumNumberOfCalls to VehiclelMonitoring request - - StopMonitoringDelivery SIRI-SX - Upgrade to DatexII - - ConnectionMonitoringDelivery SIRI-CM - [VDV] Add SuggestedWaitDecisionTime to MonitoredFeederArrival SIRI-CM x tx - - Enabling SIRI Lite - [MTA, UK] Add optional authenitication Key to Servce Request TODO - [MTA, UK] Add optional name to StopMonitoring response x tx - [MTA, UK] Add optional name to VehicleMonitoring response x tx - - Discovery services - [Fr] Add location to stop discovery x. - - General Framework - [VDV] Add ErrorNumber to Error Structure SIRI - All - - [VDV] Add new error conditions - - UnknownParticipant Recipient for a message to be distributed is unknown. +SIRI v2.0 - UnknownEndpoint Endpoint to which a message is to be distributed is unknown. +SIRI v2.0 - EndpointDeniedAccess Distribution message could not be delivered because not authorised.. +SIRI v2.0 - EndpointNotAvailable Recipient of a message to be distributed is not available. +SIRI v2.0 - UnapprovedKey User authorisation Key is not enabled. +SIRI v2.0 - - InvalidDataReferences Request contains references to identifiers that are not known. +SIRI v2.0 - ParametersIgnored Request contained parameters that were not supported by the producer. A response has been provided but some parameters have been ignored. +SIRI v2.0 - UnknownExtensions Request contained extensions that were not supported bu the producer. A response has been provided but some or all extensions have been ignored.. +SIRI v2.0 - - [FR] Add DistanceUnits & Velocity Units to ServiceRequestContext x tx - - General improvements to internal structure maintainability - Tidy up comments. x tx. - Improve modularisation (eg permissions/model permissions) to avoid circuloar refs x - Separate subdirectories for common request, model and core elements x - Separate out some model elements into separate packages x - Separate out model journeys from SIRI service packagaes x - Separate out discovery models from discovery services x - - Start of v2,0 ==> - -Changes to SIRI schema v1.4a since v1.3 -============================ - -2011-04-18 Corrections - New cumulative fix version 1.4a - Minor corrections 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 x - (ii) and siri_generalMessage_service.xsd subscription structure x - (iii) Missing type: Assign a type of normalizedString to formatRef x dx - - (b) siri_requests.xsd (line 814) ErrorConditionStructure should not be abstract . Fix from RV ixxi.biz- - made abstract x - - (c) siri_journey.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 x ?? - - (d) siri_productionTimetable_service.xsd Type on request ValidityPeriod start and end should be datetime not time - - Change to ClosedTimestampRange instead of ClosedDateeRange x tx. - - Fix Subscription request to be an element and to have IncrementalUpdate parameter Extensions x - - (e) siri_situation.xsd AffectedVehicleJourney should allow multiple journeys. Brian Ferris onebusaway.org>, x - - (f) ifopt_location.xsd Correct siri: namespace x - - (g) Fix up examples - (i) correct estimated timetable request, production timetable request, stop monitoring request, stop monitoring eprmissions. drop flat examples tx. - (ii) Add examples for facility monitorign and situation exchange ex - - (h) Drop vestigial As Flatgroup alternative coding tx - siri_connectionTimetable_service.xsd InterchangeHourneys x tx - siri_estimatedTimetable_service.xsd EstimatedCalls --> x tx - siri_productionTimetable_service.xsd DatedCalls --> x tx - - (i) Add missing type - siri_requests.xsd formatRef x - DATEXIISchema_1_0_1_0.xsd modelBaseversion - - (j)siri_facility.xsd TidyUp empty ValidityConditionGroup x - - (g) Add xmlSPy project spp. x - -====================== -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 x - (b) siriSg.xsd Remove unnecessary groups for decoupled version x tx. - -2009-03-31 Corrections - (a) StopMonitoring - Change the element type of MaximumNumberOfCalls.Previous, MaximumNumberOfCalls.Onwards from xsd:positiveInteger to xsd:nonNegativeInteger x tx. - - and clarify handling of - - MaximumNumberOfCalls : If calls are to be returned, maximum number of calls to include in response. If absent, exclude all calls. tx. - - Previous : Maximum number of previous calls to include. Zero for none. Only applies if MaximumNumberOfCalls specified. Zero for none. If MaximumNumber of Calls specified but MaximumNumberOfCalls.previous absent, include all previous calls. tx. - - Onwards : Maximum number of onwards calls to include. Zero for none. Only applies if MaximumNumberOfCalls specified. Zero for none. If MaximumNumber of Calls specified but MaximumNumberOfCalls.Onwards absent, include all onwards calls. tx. - -___________________________________________________________________________ - - (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 x - (b) siriSg.xsd Correct cardinality on servcierequest & subscription request to be many x - -2009-09-18 Siricommon - allow empty Terminate subscription response x - (a) Relax mandatory on in siri_common x - -2008-11-18 Revise FM servics - (a) Revise daytypes in siri_time.xsd x - -2008-11-17 Revise to support substitution groups - (a) Make all requests subtypes of abstract request. Add Subst elements x - - (b) Introduce AbstractFunctionalServiceRequest, AbstractCapabilityServiceRequest, AbstractDiscoveryRequest - as common supertypes. revised versiosn of siri_requests.xsd, siri_journey.xsd and siri_permissions.xsd, siri-All and siribase - - (c) add SiriSg and Siri_base.xsd packages -2008-11-12 Corrections to the Caridnailities on the siri_discovery services x - - (a) Change min maxes on >LineRef, StopPoints, Features etc etc x - -2008-10-08 Corrections to the SIRI service - (a) Add SubscriberRef to TerminateSubscriptionRequest x tx. - -2008-10-06 Corrections to the SIRI service - (a) Correct StopTimetable SubscriptionRequest to use group x - (b) Correct cardinality on AnnotatedStopPointRef in StopPointDelivery x - -2008-10-01 Corrections to the SIRI-SX service - (a) Add StatusFilterGroup to SIRI-SX request with Verification, Progress and Reality - (b) add 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 - (c) Allow a link projection & Offset on connection Link via AffectedPathLink - (d) Add an AfFfectedRoad 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 Corrections 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--> x - (c) Allow zero PT or Road Situation elements in a delivery x - (d) Affects Line group corrected to ref a lineref and not a route ref x - (e) Add missing scopeType to Situation classifier group x - (f) Add other subreasons x - (g) add secondary reasons x - -2008 05 08 StopMonitoring service - (a) Correct type on FeatureRef in Stop monitoring x - (b) Add StopMonitoringMultipleRequest x tx - (c) Add optional MonitoringRef to StopMonitoringDelivery so that can return id even if no data x tx. - -2008 03 27 - Fix up ifopt & ACSB version numbers to match ifopt 0.4 x - - -2008-03-26 EstimatedTimetable Production Timetable Service Service - Add wrapper tag for Line + Direction to help binding to Axisx x tx. - Wraps multiple instances x - ** Note this will break strict Compaptibility with 1.0 - -2008 03 12 - Add comments for elements and arrtributes that lacked them x - Correct wdsl errors x - Strip out degree character x - BeyondHorizon type corrected x - -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. x tx - Added a siri_all.xsd, ifopt_allStopPlace.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 x - Change name space : http://www.siri.org.uk/ to www.siri.org.uk/siri x.tx. - - harmonise Facility Monitoring - Revise SpecialNeeds to use acsb package x. - Use Ifopt facility etc x. - Factor out Extensions to utility file x. - -2007 04 V1.2 -======================================= +Server Interface for Real-time Information +============================================ + +v2.0 As CEN draft European Standard + prCEN/EN EN 00278181 + prCEN/EN EN 15531 + +v1.0 As CEN Technical Standard + CEN/TS 00278181 + CEN/TS 15531 + +(C) Copyright CEN SIRI 2004-2013 + +=========================================== +This ReadMe describes Changes to the SIRI schema up to v2.0 version 2.0 since v1.3 (2012/03/30) + + +======================== + Future: handbook UML DIagrams +======================== +Changes to SIRI schema v2.0 since v1.4 + + 2015.05.13 Bug fix (from french feedback) SIRI 2.0p + * replacement of "NotifyExtension" (appearing 10 times) with "SiriExtension" in siri_wsConsumer.wsdl in order to ensure compatibility with the Document version + + 2015.05.13 Bug fix (from SG7 feedback) SIRI 2.0o + * update annotation in siri.xsd and and siri_all_functionalService.xsd (to add siri__facilityMonitoring_service.xsd ...) + * siri.xsd: move of a SituationExchangeDelivery, renamed IncludedSituationExchangeDelivery, before other complemented service deliveries. + * siri_situationExchange_service.xsd: addition of IncludedSituationExchangeDelivery element + + 2015.05.11 Bug fix (from SG7 skype meeting on May 11th 2015) SIRI 2.0o + * Allow multiple tags within an extension (reapply lost chnage from 2012.06.18 SIRI 2.0d) - siri_utility.xsd + * siri_estimatedVehicleJourney.xsd : in EstimatedTimetableAlterationGroup, addition of FramedVehicleJourneyRef as an alternative to DatedVehicleJourneyRef (choice) and deprecation of DatedVehicleJourneyRef and EstimatedVehicleJourneyCode + * siri_datedVehicleJourney.xsd : DatedVehicleJourneyCode is now optional + * siri.xsd: SituationExchangeDelivery now can be provided as a complement to any other Service delivery (and can still be provided standalone)... note that the SituationExchangeDelivery must be after the other Delivery to get a validating, non-ambiguous XSD. + * siri_estimatedVehicleJourney.xsd : EstimatedVehicleJourneyStructure brought back to SIRI 2.0k situation + * Replacement of EstimatedJourneyInfoGroup by JourneyEndTimesGroup + * Replacement of inclusion of siri_journey.xsd by siri_monitoredVehicleJourney.xsd + * Replacement of EstimatedRealtimeInfoGroup by journeyProgressGroup + * Replacement of OperationalInfoGroup by TrainOperationalInfoGroup + + + 2015.02.10 Bug fix (from french feedback) + * [fr] siri_wsProducer-Framework.xsd: use of siri:CheckStatusRequestStructure instead of siri:RequestStructure for checkStatus (one addition non mandatory version attribute) + * [fr] siri_wsProducer.wsdl: use of siri:CheckStatusRequestStructure instead of siri:RequestStructure for checkStatus (one addition non mandatory version attribute) + * [fr] siri_wsConsumer-Framework.xsd: update type of NotifySubscriptionTerminated to siri:SubscriptionTerminatedNotificationStructure (instead of TerminateSubbscriptionREquest !) + + 2014.11.17 Correction (from french feedback) + * [fr] fix RPC-Document compatibility issue for GetSiri in Document WSDL (siri_wsProducer-Services.xsd): addition of Request/Answer wrapper + * [fr] fix WSDL Document issue: GetCapability was using Answer instead of Request (siri_wsProducer-DiscoveryCapability.xsd) + * [fr] fix RPC-Document compatibility issue for LinesDiscovery,ConnectionLinksDiscovery,StopPointsDiscovery in Document WSDL (siri_wsProducer-DiscoveryCapability.xsd): deletion of useless «xxxAnswerInfo» wrapper + + 2014.06.20 Correction and revisions from Stenungsund + [Part2] + * [fx] Document SubscriptionTerminatedNotification and add error code. (siri-requests.xsd) + * [fx] StopDiscovery response. Add RouteDirection. Rename JourneyPattern/Stops to JourneyPattern/StopsInPattern SubscriptionTerminatedNotification and add error code. (siri-requests.xsd) + * [de] Add Extensions to discovery requests. (siri_discovery.xsd) + + [Part3] + * [ch] Add origin display whereever destination display as per Cologne meeting (siri-Journey.xsd, siri-DatedVehicleJourney.xsd, + * [xh[ Add OriginAtDestination wherever destination display as per Cologne meeting (siri-Journey.xsd) + * [fx] Set default on new DetailLevels on ConnectionMonitoring and EstimatedJourney for backwards compatability. (siri_connectionMonitoring_ervice.xsd siri_EstimatedTimetable_service.xsd + * [ch] Add recordedCall to Estimated jouernesy to allow times for passed stops to be included. iri_EstimatedVehicleJourney.xsd + [Part5 SituationExchange] + * [de] Add missing AffectedFacility that was in document but missing from schema. VehicleJourney, STop & StopComponent siri_situationAffects.xsd. +emporal filter siri_situationExchaneg_service.xsd. + * [de] Add temporal filter to request with ValidityPeriod in siri_situationExchange_service.xsd. + * [se] Add end time precision to halfopen time rangefor input a siri_time.xsd. + * [se] Add end time status to halfopen time range output siri_time.xsd. + * [fr] Add additional small delay bands siri_situation.xsd + * [de] Add IncludeOnly-IfInPublicationWindow to situation request temporal filter siri_situationExchange_service.xsd. + * [fx] StopPlaceFilterGroup: add missing component ref and facility that was in doc but missing from schema siri_situationExchange_service.xsd. + * [fx] Add missing AccessFeature type to AFfectedStopPlaceComponent siri_situationAffects.xsd. + * [fx] Correct cardinality on FacilitRef on request to match doc siri_situationExchaneg_service.xsd. + * [fx] Correct spec to include projection attributes for AFfectedStopPlaceComponent doc. + * [doc] Document FacilityRef as part of request doc + * [doc] Document Access Mode as part of request doc + * [doc] Document Scope as part of request doc + * [doc] Document RoadFilter and Accessibility need filter as part of request doc + * [doc] Correct Documentation of AfFfectedRoads as part of Delivery doc + * [doc/fx] Correct Documentation of capability Matrix and update in schemas well siri_situationExchange_service.xsd. + * [doc/fx] Correct Documentation of Reason codes and correct in schema siri_reasons.xsd + * [doc] Add Annex D to Doc on GTFS real-time mapping + + 2014.05.26 Changes to answer comment from the EU ballot + * [fr] Addition of SubscriptionTerminatedNotification (XSD and WSDL SOAP Web Services(RPC/Document & WSDL2)) + - File siri_common_services.xsd: Addition of SubscriptionTerminatedNotification (SubscriptionTerminatedNotification element + SubscriptionTerminatedNotificationStructure ) + - File siri.xsd: addition of SubscriptionTerminatedNotification in servicesResponseGroup + - Update of siri_wsConsumer-Document.wsdl, siri_wsConsumer.wsdl, siri_wsConsumer-WSDL2.wsdl to add a NotifyTerminateSubscription + - File siri_wsConsumer-Framework.xsd: Addition of WsSubscriptionTerminatedNotificationStructure and NotifySubscriptionTerminated + * [fr] Added ParameterName [0..*] to ParametersIgnoredErrorStructure (siri_request_errorConditions.xsd) + * [fr] Added ExtensionName [0..*] to UnknownExtensionsErrorStructure (siri_request_errorConditions.xsd) + * [fr] Added InvalidRef [0..*] to InvalidDataReferencesErrorStructure (siri_request_errorConditions.xsd) + * [fr] Added Vesion attribute (non mandatory) to CheckStatus request (siri_common_services.xsd) + * [fr] ChangeBeforeUpdates not anymore mandatory in EstimatedTimetableSubscriptionPolicyGroup + * [fr] added optional RecordedAtTime to EstimatedVehicleJourney + * [fr] added ConnectionLinksDiscovery service to WSDL (RPC/Document & WSDL2) (and siri_wsProducerDicoveryCapability.xsd) + + + 2013.06.26 French comments (compatibility issue) + * [fr] Change SOAP Web Service namesapce to http://wsdl.siri.org.uk (previously http://wsdl.siri.org.uk/siri) + + * [fr] update EstimatedVehicleJourney in order to have it consistent with MonitoredVehicleJourney and Siri 2.0 + - use JourneyEndTimesGroup in place of EstimatedJourneyInfoGroup + - use JourneyProgressGroup in place of EstimatedRealtimeInfoGroup + - use TrainOperationalInfoGroup in place of OperationalInfoGroup + - addCallRailGroup (containing PlateformTraversal ) and CallRealTime to EstimatedCall + 2013.02.20 WG3 SG meeting Munich + * [se] Add JourneyEndNamesInfoGroup to EstimatedDirectionAtStop to DestinationDisplayAtStop + This makes destination name available on EstimatedJourney. + * [us] Rename ProgrssStatusEnumeration to CallStatusENumeration to avoid confusion. + * [fr} Add FramedVehicleJourney references as alternative wherever a simple VehicleJourneyRef exists and deprecate use of simple reference. + - DatedVehicleJourney - identifier group. + - FacilityMonitoring - FacilityLocation. + - SituationExchangeService - SituationFilterGroup. + - SituationExchangeService - AffectedVehicleJourneyRef. + * [ch] StopTimeTableCancellation - Add Reason code to be consistet with St opMonitoring. + * [de] ArrivalTimesDepartureGroup - add ExpectedArrivalPredictionQuality element. + * [fr] MonitoredStopVisit Cancellation make VisitNo LineRef DirectionRef optional. + * [fr] EstimatedTimetable, COnnectionMonitoring add detailed level to reqyest + + * [fr] Make AdditionalVersionRefS to OperationalInfoGroup. + * [fr] Add JourneyPatternName The JourneyPatternInfoGroup. + + 2013.02.11 + * [SE] Align documentation and XSD. See comments in individual xsd-files. + * [SE] Add StopNotice and StopNoticeCancellation to StopMonitoringDelivery. + * [SE] Revise ProductionTimetableDelviery to correct ServcieJourneyInterchange to include visit numbers. + * [FR] Updated with latest WDSL from CD. + + + 2012.08.01 + SIRI 2.0e.1. + * [DE] Align documentation and XSD using GT's amendments. + * [FR] Update WDSL and add WSDL2.. Add WSDl chapter by CD to gudie.. + * [DE] Add Delegation elements to more mesages. + * [US] Revise Siri Lite chapter. + *[DE] Revise commends on Prediction quality based on CB's comments + + 2012.06.18 + SIRI 2.0d.2. + * [CH] Allow multiple tags within an extension + * [CH] Make most NL String elements unbounded to allow for NL translations. x dx + Add IncludeTranslations to RequestPolicy. + Add Translations to Cpabilities + * [DE] Add PredictionQuality elements to MonitoredVehicleJourney Onward Call. & EstimatedVehcielJourney + * [FR] Add GroupOfLinesRef to JourneyPattenrInforGroup on MonitoredVehcile Joruney and elsewhere + * [FR] Add Extensions tag to EstimatedTimetableSubscriptionRequest x tx + * [FR] Add Extensions tag to FacilityMonitoringSubscriptionRequest x + * [FR] Add Extensions tag to SituationExchangeSubscriptionRequest x + * [FR] Add Extensions tag to ConnectionMonitoringSubscriptionRequest x tx + * [FR] Add Extensions tag to Connection|TimetableSubscriptionRequest x tx + * [FR] Add Extensions tag to VehicleMonitoringSubscriptionRequest x tx + * [FR] Add Extensions tag to Terminate SubscriptionRequest x tx + * [DE] Correct EstimatedTimetable EstimatedServiceJourneyInterchange x tx + *[US] Add SIRILite chapter to manual. + * [DE] Add DelegatorAddress and DelegatorRef to servicerequest and service response. x tx + * [SE] Correct latestExopectedArrivalTime + * [SE] Add Vehicle Status add additional arrival and departure states + + + 2012.05.31 + SIRI 2.0d.1. + * [MTA] Discovery Revise StopLine discovery to include line direction x + * [MTA] Discovery Revise Line discovery to include Direction/Line x + * [MTA] Correcct typo in name of RouteDirection x + * [Init] Add DriverRef to vehiclejourney x tx + + SIRI 2.0c.1. + 2012.06.11 + SIRI 2.0c + Relax typing on NotifcationRef to be normalized string x + Add wsdl subdirectory for wsd .xsds x + + 2012.06.08 + WSDL [FR] x + In siri-wsProducer-Document.xsd rename StopMonitoringType and StopMonitoringMultipleType to StopMonitoringRequestType to StopMonitoringMultipleRequestType (for more consistent naming) + Add comment to point out that usage of SOAP Fault are now deprecated + Add comment to point out that usage of MultipleStopMonitoring is now deprecated (utilise GetSiriService) + Addition of a Document Wrapped encoding style fully compatible with the RPC Style (Producer and Consumer) + Add GetSiriService in RPC and Document Wrapped mode + Addition of StopDiscovery and LineDiscovery + Cleaning of xmlns:xxx in siri_wsProducer-Document + Suppression of comments on and (for http://www.validwsdl.com/ compliance) .. in poducer and producer-Document WSDL + Rename of Port/Binding/Service in order to clearly diffirentiate them + Change to + + + 2012.05.17 + SIRI 2.0b.3 + [MTA] Add filtering to StopPoints and Lines Discovery requests by point + radius x + [MTA] Add filtering to Lines Discovery request by LineRef and Direction x + [MTA] Add stops in pattern to Lines Discovery, with OnwardLinkShap and LineDetailParameter x + [NeTEx] Add StopAreaRef & url to annotated stop on StopDiscovery x + [General] Correct capability definition + + 2012.04.18 + SIRI 2.0b.2 + [VDV] Add ValidUntil to individual SIRI-CM MonitoredFeederArrival x e + [VDV] Add ValidUntil to individual SIRI-SM MonitoredStopVisit x e + + + [MTA] Add DistanceFromStop and NumberOfStopsAway to to MonitoredCall & OnwardsCall x tx + + 2012.03.23 + SIRI 2.0b.1 + [MTA] Add filtering to StopPoints request by point + radius + + 2012.03.23 + WDSL + Add explicit namespace to body x + Use a SIRI namespace http://wsdl.siri.org.uk/siri x + Correct GetStopTimentable to have soapAction x + Turn annotations into comments x + Use FaultLiteral x + + SIRI 2.0a + Changes to framework + [VDV] Add DataReady to CheckStatus response x. tx. + + JourneyInfo group SIRI-ST SIRI-SM SIRI-VM SIRI-PT SIRI-ET MonitoredJourney, etc + [VDV] Add PublicContact & Operations contact to JourneyInfo group in x tx + [VDV] Add ViaPriority to ViaNames using a new ViaNameStructure x tx + [VDV] at DirectionAtOrigin name to JourneyInfo SIRI-PT, SIRI-ET, SIRI-SM. SIRI-VM + + [VDV] Add EstimatedServiceInterchange to EstimatedTimetableDelivery x tx. + [VDV] Add ServiceJourneyInterchange to ProductionTimetableDelivery SIRI PT x tx + + Changes to MonitoredVehicleJourney SIRI-SM SIRI-VM + [VDV, SE] Add EarliestExpectedArrivalTimeForVehicle to Arrival Times Group x tx + [VDV] Add ProvisionalExpectedDepartureTime to Departure Times Group x tx + [VDV, SE] Add latesExpectedArrivalTimeForVehicle to Departure Times Group x tx + [SE] Add Aimed and expected Platform assignments to CALLs including a reference code. + + [FR] Add FirstOrLastJourney to JourneyTimesGroup x.tx. + [FR] add ArrivalOperatorRefs and DepartureOperatorRefs to Call arrival and Departure + [VDV] Add Velocity to MonitoredVehicleJourney JoueyProgerssGroup SIRI-SM and SIRI-VM + + [FR] Add AimedLatestPassengerAccessTime to MonitoredCall & OnwardsCall x tx + [MTA,FR,UK] Add ArrivalProximityText & DepartureProximityText to MonitoredCall & OnwardsCall x tx + [FR, MTA] Add Velocity to Journey & VelocityType x tx + + StopMonitoringRequest SIRI-SM + [VDV] Add Minimum-StopVisits¬PerVia to STopMonitoringRequestPolicy x tx + [VDV] Add HasMinimum-StopVisits¬Via to STopMonitoringCapabilities x tx + + StopMonitoringDelivery SIRI-SM + [FR] Add Service Exception element + [VDV] Add delivery variant to LineNote + [MTA] Add MaximumNumberOfCalls to VehiclelMonitoring request + + StopMonitoringDelivery SIRI-SX + Upgrade to DatexII + + ConnectionMonitoringDelivery SIRI-CM + [VDV] Add SuggestedWaitDecisionTime to MonitoredFeederArrival SIRI-CM x tx + + Enabling SIRI Lite + [MTA, UK] Add optional authenitication Key to Servce Request TODO + [MTA, UK] Add optional name to StopMonitoring response x tx + [MTA, UK] Add optional name to VehicleMonitoring response x tx + + Discovery services + [Fr] Add location to stop discovery x. + + General Framework + [VDV] Add ErrorNumber to Error Structure SIRI - All + + [VDV] Add new error conditions + + UnknownParticipant Recipient for a message to be distributed is unknown. +SIRI v2.0 + UnknownEndpoint Endpoint to which a message is to be distributed is unknown. +SIRI v2.0 + EndpointDeniedAccess Distribution message could not be delivered because not authorised.. +SIRI v2.0 + EndpointNotAvailable Recipient of a message to be distributed is not available. +SIRI v2.0 + UnapprovedKey User authorisation Key is not enabled. +SIRI v2.0 + + InvalidDataReferences Request contains references to identifiers that are not known. +SIRI v2.0 + ParametersIgnored Request contained parameters that were not supported by the producer. A response has been provided but some parameters have been ignored. +SIRI v2.0 + UnknownExtensions Request contained extensions that were not supported bu the producer. A response has been provided but some or all extensions have been ignored.. +SIRI v2.0 + + [FR] Add DistanceUnits & Velocity Units to ServiceRequestContext x tx + + General improvements to internal structure maintainability + Tidy up comments. x tx. + Improve modularisation (eg permissions/model permissions) to avoid circuloar refs x + Separate subdirectories for common request, model and core elements x + Separate out some model elements into separate packages x + Separate out model journeys from SIRI service packagaes x + Separate out discovery models from discovery services x + + Start of v2,0 ==> + +Changes to SIRI schema v1.4a since v1.3 +============================ + +2011-04-18 Corrections - New cumulative fix version 1.4a + Minor corrections 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 x + (ii) and siri_generalMessage_service.xsd subscription structure x + (iii) Missing type: Assign a type of normalizedString to formatRef x dx + + (b) siri_requests.xsd (line 814) ErrorConditionStructure should not be abstract . Fix from RV ixxi.biz- + made abstract x + + (c) siri_journey.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 x ?? + + (d) siri_productionTimetable_service.xsd Type on request ValidityPeriod start and end should be datetime not time + - Change to ClosedTimestampRange instead of ClosedDateeRange x tx. + - Fix Subscription request to be an element and to have IncrementalUpdate parameter Extensions x + + (e) siri_situation.xsd AffectedVehicleJourney should allow multiple journeys. Brian Ferris onebusaway.org>, x + + (f) ifopt_location.xsd Correct siri: namespace x + + (g) Fix up examples + (i) correct estimated timetable request, production timetable request, stop monitoring request, stop monitoring eprmissions. drop flat examples tx. + (ii) Add examples for facility monitorign and situation exchange ex + + (h) Drop vestigial As Flatgroup alternative coding tx + siri_connectionTimetable_service.xsd InterchangeHourneys x tx + siri_estimatedTimetable_service.xsd EstimatedCalls --> x tx + siri_productionTimetable_service.xsd DatedCalls --> x tx + + (i) Add missing type + siri_requests.xsd formatRef x + DATEXIISchema_1_0_1_0.xsd modelBaseversion + + (j)siri_facility.xsd TidyUp empty ValidityConditionGroup x + + (g) Add xmlSPy project spp. x + +====================== +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 x + (b) siriSg.xsd Remove unnecessary groups for decoupled version x tx. + +2009-03-31 Corrections + (a) StopMonitoring + Change the element type of MaximumNumberOfCalls.Previous, MaximumNumberOfCalls.Onwards from xsd:positiveInteger to xsd:nonNegativeInteger x tx. + + and clarify handling of + + MaximumNumberOfCalls : If calls are to be returned, maximum number of calls to include in response. If absent, exclude all calls. tx. + + Previous : Maximum number of previous calls to include. Zero for none. Only applies if MaximumNumberOfCalls specified. Zero for none. If MaximumNumber of Calls specified but MaximumNumberOfCalls.previous absent, include all previous calls. tx. + + Onwards : Maximum number of onwards calls to include. Zero for none. Only applies if MaximumNumberOfCalls specified. Zero for none. If MaximumNumber of Calls specified but MaximumNumberOfCalls.Onwards absent, include all onwards calls. tx. + +___________________________________________________________________________ + + (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 x + (b) siriSg.xsd Correct cardinality on servcierequest & subscription request to be many x + +2009-09-18 Siricommon - allow empty Terminate subscription response x + (a) Relax mandatory on in siri_common x + +2008-11-18 Revise FM servics + (a) Revise daytypes in siri_time.xsd x + +2008-11-17 Revise to support substitution groups + (a) Make all requests subtypes of abstract request. Add Subst elements x + + (b) Introduce AbstractFunctionalServiceRequest, AbstractCapabilityServiceRequest, AbstractDiscoveryRequest + as common supertypes. revised versiosn of siri_requests.xsd, siri_journey.xsd and siri_permissions.xsd, siri-All and siribase + + (c) add SiriSg and Siri_base.xsd packages +2008-11-12 Corrections to the Caridnailities on the siri_discovery services x + + (a) Change min maxes on >LineRef, StopPoints, Features etc etc x + +2008-10-08 Corrections to the SIRI service + (a) Add SubscriberRef to TerminateSubscriptionRequest x tx. + +2008-10-06 Corrections to the SIRI service + (a) Correct StopTimetable SubscriptionRequest to use group x + (b) Correct cardinality on AnnotatedStopPointRef in StopPointDelivery x + +2008-10-01 Corrections to the SIRI-SX service + (a) Add StatusFilterGroup to SIRI-SX request with Verification, Progress and Reality + (b) add 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 + (c) Allow a link projection & Offset on connection Link via AffectedPathLink + (d) Add an AfFfectedRoad 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 Corrections 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--> x + (c) Allow zero PT or Road Situation elements in a delivery x + (d) Affects Line group corrected to ref a lineref and not a route ref x + (e) Add missing scopeType to Situation classifier group x + (f) Add other subreasons x + (g) add secondary reasons x + +2008 05 08 StopMonitoring service + (a) Correct type on FeatureRef in Stop monitoring x + (b) Add StopMonitoringMultipleRequest x tx + (c) Add optional MonitoringRef to StopMonitoringDelivery so that can return id even if no data x tx. + +2008 03 27 + Fix up ifopt & ACSB version numbers to match ifopt 0.4 x + + +2008-03-26 EstimatedTimetable Production Timetable Service Service + Add wrapper tag for Line + Direction to help binding to Axisx x tx. + Wraps multiple instances x + ** Note this will break strict Compaptibility with 1.0 + +2008 03 12 + Add comments for elements and arrtributes that lacked them x + Correct wdsl errors x + Strip out degree character x + BeyondHorizon type corrected x + +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. x tx + Added a siri_all.xsd, ifopt_allStopPlace.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 x + Change name space : http://www.siri.org.uk/ to www.siri.org.uk/siri x.tx. + + harmonise Facility Monitoring + Revise SpecialNeeds to use acsb package x. + Use Ifopt facility etc x. + Factor out Extensions to utility file x. + +2007 04 V1.2 +======================================= diff --git a/release-notes/SIRI_XML-2.0q_changes.txt b/release-notes/SIRI_XML-2.0q_changes.txt index 6630a699..e77e475d 100644 --- a/release-notes/SIRI_XML-2.0q_changes.txt +++ b/release-notes/SIRI_XML-2.0q_changes.txt @@ -1,57 +1,57 @@ -Changes made against SIRI 2.0p for SIRI 2.0q by VDV-Ums -2018-11-13 - D. Rubli, K. Grimme - -ifopt\ifopt_stop-v0.3.xsd -- Enum "ferrytPort" in StopPlaceTypeEnumeration changed to "ferryPort" - -siri_model\siri_reference-v2.0.xsd -- "PublishedLineName" inside "PublishedLineGroup" changed to "unbounded" to allow multiple definitions for different languages due to the xml:lang-Attribute -- "DestinationName" inside "PublishedLineGroup" changed to "unbounded" to allow multiple definitions for different languages due to the xml:lang-Attribute - -siri_model\siri_situationActions-v2.0.xsd: -- ActionsStructure.ActionsGroup.PublishToTvAction changed to unbounded -- ActionsStructure.ActionsGroup.NotifyBySmsAction changed to unbounded -- PublishToDisplayAction added to ActionsGroup -- ActionsStructure.ActionsGroup.PublishToTvAction.Ceefax and Teletext: annotation switched - -siri_model\siri_situationAffects-v2.0.xsd -- Wrapped "AffectedInterchanges" node around AffectedInterchange in AffectedCallStructure -- "PublishedLineName" inside "LineGroup" and "AffectedVehicleJourneyStructure" changed to "unbounded" to allow multiple definitions for different languages due to the xml:lang-Attribute -- "Route" inside "AffectedVehicleJourneyStructure" is now optional since all of its content are optional - -siri_model\siri_situationReasons-v2.0.xsd: -- MiscellaneousReasonEnumeration TPEC-code of "altercation" changed from pti19_1_Alias_6 to pti19_1_Alias_7 because TPEC-code pti19_1_Alias_6 was wrongly doubled in use for "emergencyServicesCall" and "altercation" -- MiscellaneousReasonEnumeration TPEC-code of "illVehicleOccupants" changed from pti19_1_Alias_7 to pti19_1_Alias_8 -- MiscellaneousReasonEnumeration TPEC-code of "undefinedProblem" changed from pti19_27 to pti19_255 -- MiscellaneousSubReasonEnumeration TPEC-code value "assault" added according to recommendation document and Datex2 -- EquipmentReasonEnumeration TPEC-code pti21_6_Alias_2 "defectiveTrain" added according to recommendation document -- EquipmentReasonEnumeration TPEC-code pti21_8_Alias_10 "leveCrossingFailure" changed to "levelCrossingFailure" according to recommendation document -- EquipmentReasonEnumeration TPEC-code pti21_8_Alias_11 "trafficManagementSystemFailure" added according to recommendation document -- EquipmentReasonEnumeration TPEC-code pti21_12_Alias_1 value changed from "oveheadWireFailure" to "overheadWireFailure" according to recommendation document -- EquipmentSubReasonEnumeration TPEC-code value "defectiveTrain" added according to recommendation document -- EquipmentSubReasonEnumeration TPEC-code value "leveCrossingFailure" changed to "levelCrossingFailure" according to recommendation document -- EquipmentSubReasonEnumeration TPEC-code value "trafficManagementSystemFailure" added according to recommendation document -- EquipmentSubReasonEnumeration TPEC-code value "oveheadWireFailure" changed to "overheadWireFailure" according to recommendation document -- EnvironmentReasonEnumeration TPEC-code pti22_13_Alias_1 "flashFloods" added according to recommendation document -- EnvironmentReasonEnumeration TPEC-code pti22_19_Alias_1 "mudslide" added according to recommendation document -- EnvironmentReasonEnumeration TPEC-code pti22_19_Alias_2 "rockfalls" added according to recommendation document -- EnvironmentReasonEnumeration TPEC-code pti22_19_Alias_3 "subsidence" added according to recommendation document -- EnvironmentReasonEnumeration TPEC-code pti22_19_Alias_4 "earthquakeDamage" added according to recommendation document -- EnvironmentReasonEnumeration TPEC-code pti22_3_Alias_3 "avalanches" added according to TPEG document -- EnvironmentReasonEnumeration TPEC-code pti22_13_Alias_1 "flashFloods" added according to recommendation document -- EnvironmentSubReasonEnumeration TPEC-code value "lighteningStrike" changed to "lightningStrike" according to recommendation document -- EnvironmentSubReasonEnumeration TPEC-code value "mudslip" changed to "mudslide" according to recommendation document and Datex2 - -siri_model\siri_situationServiceTypes-v1.0.xsd: -- ReportTypeEnumeration TPEC-code "2_27_1_Alias_2" changed to "27_1_Alias_2" according to recommendation document -- ReportTypeEnumeration TPEC-code "2_27_1_Alias_3" changed to "27_1_Alias_3" according to recommendation document - -siri_model\siri_situation-v2.0.xsd: -- RelatedToEnumeration Enum value "correctionTo" added according to recommendation document -- WorkflowStatusEnumeration Enum value "pendingApproval" added according to recommendation document -- AudienceEnumeration Enum value "authorities" added according to recommendation document -- AudienceEnumeration Enum value "transportOperators" added according to recommendation document -- Severity changed from mandatory to optional as mentioned in XSD annotation and recommendation - -xsd\siri_situationExchange_service.xsd: +Changes made against SIRI 2.0p for SIRI 2.0q by VDV-Ums +2018-11-13 - D. Rubli, K. Grimme + +ifopt\ifopt_stop-v0.3.xsd +- Enum "ferrytPort" in StopPlaceTypeEnumeration changed to "ferryPort" + +siri_model\siri_reference-v2.0.xsd +- "PublishedLineName" inside "PublishedLineGroup" changed to "unbounded" to allow multiple definitions for different languages due to the xml:lang-Attribute +- "DestinationName" inside "PublishedLineGroup" changed to "unbounded" to allow multiple definitions for different languages due to the xml:lang-Attribute + +siri_model\siri_situationActions-v2.0.xsd: +- ActionsStructure.ActionsGroup.PublishToTvAction changed to unbounded +- ActionsStructure.ActionsGroup.NotifyBySmsAction changed to unbounded +- PublishToDisplayAction added to ActionsGroup +- ActionsStructure.ActionsGroup.PublishToTvAction.Ceefax and Teletext: annotation switched + +siri_model\siri_situationAffects-v2.0.xsd +- Wrapped "AffectedInterchanges" node around AffectedInterchange in AffectedCallStructure +- "PublishedLineName" inside "LineGroup" and "AffectedVehicleJourneyStructure" changed to "unbounded" to allow multiple definitions for different languages due to the xml:lang-Attribute +- "Route" inside "AffectedVehicleJourneyStructure" is now optional since all of its content are optional + +siri_model\siri_situationReasons-v2.0.xsd: +- MiscellaneousReasonEnumeration TPEC-code of "altercation" changed from pti19_1_Alias_6 to pti19_1_Alias_7 because TPEC-code pti19_1_Alias_6 was wrongly doubled in use for "emergencyServicesCall" and "altercation" +- MiscellaneousReasonEnumeration TPEC-code of "illVehicleOccupants" changed from pti19_1_Alias_7 to pti19_1_Alias_8 +- MiscellaneousReasonEnumeration TPEC-code of "undefinedProblem" changed from pti19_27 to pti19_255 +- MiscellaneousSubReasonEnumeration TPEC-code value "assault" added according to recommendation document and Datex2 +- EquipmentReasonEnumeration TPEC-code pti21_6_Alias_2 "defectiveTrain" added according to recommendation document +- EquipmentReasonEnumeration TPEC-code pti21_8_Alias_10 "leveCrossingFailure" changed to "levelCrossingFailure" according to recommendation document +- EquipmentReasonEnumeration TPEC-code pti21_8_Alias_11 "trafficManagementSystemFailure" added according to recommendation document +- EquipmentReasonEnumeration TPEC-code pti21_12_Alias_1 value changed from "oveheadWireFailure" to "overheadWireFailure" according to recommendation document +- EquipmentSubReasonEnumeration TPEC-code value "defectiveTrain" added according to recommendation document +- EquipmentSubReasonEnumeration TPEC-code value "leveCrossingFailure" changed to "levelCrossingFailure" according to recommendation document +- EquipmentSubReasonEnumeration TPEC-code value "trafficManagementSystemFailure" added according to recommendation document +- EquipmentSubReasonEnumeration TPEC-code value "oveheadWireFailure" changed to "overheadWireFailure" according to recommendation document +- EnvironmentReasonEnumeration TPEC-code pti22_13_Alias_1 "flashFloods" added according to recommendation document +- EnvironmentReasonEnumeration TPEC-code pti22_19_Alias_1 "mudslide" added according to recommendation document +- EnvironmentReasonEnumeration TPEC-code pti22_19_Alias_2 "rockfalls" added according to recommendation document +- EnvironmentReasonEnumeration TPEC-code pti22_19_Alias_3 "subsidence" added according to recommendation document +- EnvironmentReasonEnumeration TPEC-code pti22_19_Alias_4 "earthquakeDamage" added according to recommendation document +- EnvironmentReasonEnumeration TPEC-code pti22_3_Alias_3 "avalanches" added according to TPEG document +- EnvironmentReasonEnumeration TPEC-code pti22_13_Alias_1 "flashFloods" added according to recommendation document +- EnvironmentSubReasonEnumeration TPEC-code value "lighteningStrike" changed to "lightningStrike" according to recommendation document +- EnvironmentSubReasonEnumeration TPEC-code value "mudslip" changed to "mudslide" according to recommendation document and Datex2 + +siri_model\siri_situationServiceTypes-v1.0.xsd: +- ReportTypeEnumeration TPEC-code "2_27_1_Alias_2" changed to "27_1_Alias_2" according to recommendation document +- ReportTypeEnumeration TPEC-code "2_27_1_Alias_3" changed to "27_1_Alias_3" according to recommendation document + +siri_model\siri_situation-v2.0.xsd: +- RelatedToEnumeration Enum value "correctionTo" added according to recommendation document +- WorkflowStatusEnumeration Enum value "pendingApproval" added according to recommendation document +- AudienceEnumeration Enum value "authorities" added according to recommendation document +- AudienceEnumeration Enum value "transportOperators" added according to recommendation document +- Severity changed from mandatory to optional as mentioned in XSD annotation and recommendation + +xsd\siri_situationExchange_service.xsd: - SituationExchangeServiceCapabilitiesStructure.TopicFiltering "FilterByKeword" changed to "FilterByKeyword" according to recommendation document \ No newline at end of file diff --git a/xsd/acsb/acsb_accessibility.xsd b/xsd/acsb/acsb_accessibility.xsd index fcaf5102..79bb5ede 100644 --- a/xsd/acsb/acsb_accessibility.xsd +++ b/xsd/acsb/acsb_accessibility.xsd @@ -1,138 +1,138 @@ - - - - - - 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.siri.org.uk/schema/2.0/ifopt}ifopt_accessibility.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, Crown Copyright 2006-2021 - - -
        -
      • Derived from the SIRI standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 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. - - - - - Identifier of LIMITATION. - - - - - Validty condition governing applicability of LIMITATION. - - - - - - - - - - - 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. - - - - - - - - - -       + + + + + + 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.siri.org.uk/schema/2.0/ifopt}ifopt_accessibility.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + CEN, Crown Copyright 2006-2021 + + +
        +
      • Derived from the SIRI standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 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. + + + + + Identifier of LIMITATION. + + + + + Validty condition governing applicability of LIMITATION. + + + + + + + + + + + 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. + + + + + + + + + +       diff --git a/xsd/acsb/acsb_all.xsd b/xsd/acsb/acsb_all.xsd index 3b33ce70..358a9a71 100644 --- a/xsd/acsb/acsb_all.xsd +++ b/xsd/acsb/acsb_all.xsd @@ -1,11 +1,11 @@ - - - - - - - - + + + + + + + + diff --git a/xsd/acsb/acsb_limitations.xsd b/xsd/acsb/acsb_limitations.xsd index 7da189ad..5869e977 100644 --- a/xsd/acsb/acsb_limitations.xsd +++ b/xsd/acsb/acsb_limitations.xsd @@ -1,141 +1,141 @@ - - - - - - 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.siri.org.uk/schema/2.0/ifopt}ifopt_accessibility.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, Crown Copyright 2006-2021 - - -
        -
      • Derived from the SIRI standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG6 - - IFOPT Fixed Objects in Public Transport - accessibility Types. - Standard -       -       - Fixed Objects accessibility limitation types for IFOPT Fixed Objects in Public Transport. -       - - - - - Group of mobility LIMITATIONs. - - - - - - - - - - - Enumeration of values for an accessibility value. - - - - - - - - - - Group of sensory LIMITATIONs. - - - - - Whether a PLACE / SITE ELEMENT has Audible signals for the viusally impaired. - - - - - Whether a PLACE / SITE ELEMENT has Visual signals for the hearing impaired. - - - - - - - - Type for accessibility. - - - - - - - - Whether a PLACE / SITE ELEMENT is wheelchair accessible. - - - - - Whether a PLACE / SITE ELEMENT has step free access. - - - - - Whether a PLACE / SITE ELEMENT has escalator free access. - - - - - Whether a PLACE / SITE ELEMENT has lift free access. - - - - - Whether a PLACE / SITE ELEMENT is wheelchair accessible. - - - - - Whether a PLACE / SITE ELEMENT has Visual signals availble for the free access. - - - - - Whether a PLACE / SITE ELEMENT allows guide dog access. - - - -       + + + + + + 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.siri.org.uk/schema/2.0/ifopt}ifopt_accessibility.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + CEN, Crown Copyright 2006-2021 + + +
        +
      • Derived from the SIRI standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG6 + + IFOPT Fixed Objects in Public Transport - accessibility Types. + Standard +       +       + Fixed Objects accessibility limitation types for IFOPT Fixed Objects in Public Transport. +       + + + + + Group of mobility LIMITATIONs. + + + + + + + + + + + Enumeration of values for an accessibility value. + + + + + + + + + + Group of sensory LIMITATIONs. + + + + + Whether a PLACE / SITE ELEMENT has Audible signals for the viusally impaired. + + + + + Whether a PLACE / SITE ELEMENT has Visual signals for the hearing impaired. + + + + + + + + Type for accessibility. + + + + + + + + Whether a PLACE / SITE ELEMENT is wheelchair accessible. + + + + + Whether a PLACE / SITE ELEMENT has step free access. + + + + + Whether a PLACE / SITE ELEMENT has escalator free access. + + + + + Whether a PLACE / SITE ELEMENT has lift free access. + + + + + Whether a PLACE / SITE ELEMENT is wheelchair accessible. + + + + + Whether a PLACE / SITE ELEMENT has Visual signals availble for the free access. + + + + + Whether a PLACE / SITE ELEMENT allows guide dog access. + + + +       diff --git a/xsd/acsb/acsb_passengerMobility.xsd b/xsd/acsb/acsb_passengerMobility.xsd index 304546d5..cac29142 100644 --- a/xsd/acsb/acsb_passengerMobility.xsd +++ b/xsd/acsb/acsb_passengerMobility.xsd @@ -1,212 +1,212 @@ - - - - - - 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.siri.org.uk/schema/2.0/ifopt}ifopt_accessibility.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, Crown Copyright 2006-2021 - - -
        -
      • Derived from the SIRI standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 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 choice 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. Default is 'included'. - - - - - Relative ranking of USER NEED on a sclae 1-5 - - - - - Extensions to USETR NEED. - - - - - - - - - Passenger mobility USER NEED for which SUITABILITY is specified. - - - - - Passenger mobility USER NEED for which SUITABILITY is specified. - - - - - Passenger medical USER NEED for which SUITABILITY is specified. - - - - - - - - Passenger enceumbrance USER NEED for which SUITABILITY is specified. - - - - - - - - Identification of mobility USER NEEDs. - - - - - - - - - - - - - - Enumeration of specific psychosensory USER NEEDs. - - - - - - - - - - - - - - - - Enumeration of specific Medical USER NEEDs. - - - - - - - - - - - Enumeration of specific encumbrances USER NEEDs. - - - - - - - - - - - - - - - Type for of a specific SUITABILITY. - - - - - Whether the Facility is suitable. - - - - - USER NEED for which SUITABILITY is specified. - - - - - - - Identification of specific SUITABILITY. - - - - - - - -       + + + + + + 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.siri.org.uk/schema/2.0/ifopt}ifopt_accessibility.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + CEN, Crown Copyright 2006-2021 + + +
        +
      • Derived from the SIRI standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 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 choice 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. Default is 'included'. + + + + + Relative ranking of USER NEED on a sclae 1-5 + + + + + Extensions to USETR NEED. + + + + + + + + + Passenger mobility USER NEED for which SUITABILITY is specified. + + + + + Passenger mobility USER NEED for which SUITABILITY is specified. + + + + + Passenger medical USER NEED for which SUITABILITY is specified. + + + + + + + + Passenger enceumbrance USER NEED for which SUITABILITY is specified. + + + + + + + + Identification of mobility USER NEEDs. + + + + + + + + + + + + + + Enumeration of specific psychosensory USER NEEDs. + + + + + + + + + + + + + + + + Enumeration of specific Medical USER NEEDs. + + + + + + + + + + + Enumeration of specific encumbrances USER NEEDs. + + + + + + + + + + + + + + + Type for of a specific SUITABILITY. + + + + + Whether the Facility is suitable. + + + + + USER NEED for which SUITABILITY is specified. + + + + + + + Identification of specific SUITABILITY. + + + + + + + +       diff --git a/xsd/datex2/DATEXIISchema.xsd b/xsd/datex2/DATEXIISchema.xsd index 9064f4d8..86819714 100644 --- a/xsd/datex2/DATEXIISchema.xsd +++ b/xsd/datex2/DATEXIISchema.xsd @@ -1,3710 +1,3710 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/xsd/datex2/DATEXIISchemaWithDefinitions.xsd b/xsd/datex2/DATEXIISchemaWithDefinitions.xsd index 368a1e05..7149d081 100644 --- a/xsd/datex2/DATEXIISchemaWithDefinitions.xsd +++ b/xsd/datex2/DATEXIISchemaWithDefinitions.xsd @@ -1,11523 +1,11523 @@ - - - - - A traffic condition which is not normal. - - - - - - - A characterization 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. - - - - - Assessment of the traffic flow conditions relative to normally expected conditions at this date/time. - - - - - A characterization of the traffic flow. - - - - - A characterization 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 stationary, or very near stationary, at the specified location (i.e. average speed is less than 10% of its free-flow level). - - - - - Traffic is queuing at the specified location, although there is still some traffic movement (i.e. average speed is between 10% and 25% of its free-flow level). - - - - - Traffic is slow moving at the specified location, but not yet forming queues (i.e. average speed is between 25% and 75% of its free-flow level). - - - - - Traffic is heavy at the specified location (i.e. average speed is between 75% and 90% of its free-flow level). - - - - - There are abnormal traffic conditions of an unspecified nature at the specified location. - - - - - Other than as defined in this enumeration. - - - - - - - Accidents are events where one or more vehicles are involved in collisions or in leaving the roadway. These include collisions between vehicles or with other road users or obstacles. - - - - - - - A descriptor indicating the most significant factor causing an accident. - - - - - A characterization of the nature of the accident. - - - - - The total number of people that are involved. - - - - - The total number of vehicles that are involved. - - - - - The vehicle involved in the 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 impaired visibility. - - - - - Not keeping a safe distance from the vehicle in front. - - - - - 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. - - - - - 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 mass transit vehicle. - - - - - Includes all accidents involving at least one moped. - - - - - Includes all accidents involving at least one motorcycle. - - - - - Accident involving radioactive material. - - - - - 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 action external to the traffic stream or roadway which could disrupt traffic. - - - - - - - Mobility of the activity. - - - - - - - - - - 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. EN ISO 14819-3 for the allocation of a location table number. - - - - - Version number associated with an ALERT-C table reference. - - - - - Area location defined by a specific Alert-C location. - - - - - - - - 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 (i.e. valid only for ring roads) the sense in which navigation should be made from the primary location to the secondary location, to avoid ambiguity. TRUE indicates positive RDS direction, i.e. direction of coding of 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. EN ISO 14819-3 for the allocation of a location table number. - - - - - Version number associated with 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. - - - - - - - - Linear location defined by a specific Alert-C location. - - - - - - - - - - Identification of a specific point, linear or area location in an ALERT-C location table. - - - - - Name of ALERT-C location. - - - - - Unique code within the ALERT-C location table which identifies the specific point, linear or area location. - - - - - - - - A positive integer number (between 1 and 63,487) which uniquely identifies a pre-defined Alert C location defined within an Alert-C table. - - - - - - 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. EN ISO 14819-3 for the allocation of a location table number. - - - - - Version number associated with an ALERT-C table reference. - - - - - - - - An integer number representing an angle in whole degrees between 0 and 359. - - - - - - 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 discrimination (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. - - - - - - - Authority initiated operation or activity that could disrupt traffic. - - - - - - - Type of authority initiated operation or activity that could disrupt traffic. - - - - - - - - - - Types of authority operations. - - - - - An operation involving authorised investigation work connected to an earlier reported accident. - - - - - An operation where a bomb squad is in action to deal with suspected or actual explosive or incendiary devices which 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 permanent or temporary operation established by customs and excise authorities on or adjacent to the carriageway. - - - - - An operation involving the juridical reconstruction of events for the purposes of judicial or legal proceedings. - - - - - 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 use by the road operator, such as for survey or inspection purposes, but not for traffic management purposes. - - - - - A permanent or temporary operation established by authorities on or adjacent to the carriageway for the purpose of gathering statistics or other traffic related information. - - - - - An operation to transport one or more VIPs. - - - - - An authority activity of undefined type. - - - - - A permanent or temporary operation established on or adjacent to the carriageway for inspection of vehicles by authorities (e.g. vehicle safety checks and tachograph checks). - - - - - A permanent or temporary operation established on or adjacent to the carriageway for weighing of vehicles by authorities. - - - - - A permanent or temporary facility established by authorities on the carriageway for weighing vehicles while in motion. - - - - - 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 the interval between the axles of the individual vehicle from front to back (e.g. 1, 2, 3...). This cannot exceed (numberOfAxles -1) if the numberOfAxles is also given as part of the VehicleCharacteristics. - - - - - - - - Vehicle axles per hour. - - - - - - The weight details of a specific axle on the vehicle. - - - - - Indicates the position of the axle on the vehicle numbered from front to back (i.e. 1, 2, 3...). This cannot exceed the numberOfAxles if provided as part of VehicleCharacteristics. - - - - - The weight of the specific axle, indicated by the axleSequenceIdentifier, on the vehicle numbered from front to back of the vehicle. - - - - - The maximum permitted weight of this specific axle on the vehicle. - - - - - - - - Generic data value(s) of either measured or elaborated data. Where values of different type are given in a single instance the metadata contained in the BasicDataValue must be applicable to all, otherwise separate instances must be given. - - - - - The extent to which the 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. 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. - - - - - The location (e.g. the stretch of road or area) to which the data value is pertinent/relevant. This may be different from the location of the measurement equipment (i.e. the measurement site location). - - - - - - - - Boolean has the value space required to support the mathematical concept of binary-valued logic: {true, false}. - - - - - - 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 (duration) 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, i.e. the section of road passing over another. - - - - - On the left hand feeder road. - - - - - On the left hand parallel 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, i.e. the section of road passing under another. - - - - - - - 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. - - - - - An earlier accident. - - - - - An earlier event. - - - - - An earlier incident. - - - - - Failure of roadside equipment. - - - - - Excessive heat. - - - - - Frost. - - - - - Holiday traffic. - - - - - Failure of road infrastructure. - - - - - Large numbers of visitors. - - - - - Obstruction (of unspecified type) on the roadway. - - - - - An alert relating to dangerous levels of pollution. - - - - - 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. - - - - - Radioactive leak alert. - - - - - A roadside event (of unspecified nature) whether planned or not. - - - - - Drivers being distracted and turning to look at an accident or other roadside event. - - - - - A security incident. - - - - - Shear weight of traffic. - - - - - Technical problems. - - - - - A terrorist incident. - - - - - An alert relating to the release of toxic gases and/or particulates. - - - - - A vandalism incident. - - - - - Other than as defined in this enumeration. - - - - - - - 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 un-coded observations/information. - - - - - A free text comment that can be used by the operator to convey un-coded 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 "greater than or equal to". - - - - - Logical comparison operator of "less than". - - - - - Logical comparison operator of "less than or equal to". - - - - - - - Types of compliance. - - - - - Advisory compliance . - - - - - Mandatory compliance. - - - - - - - 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. - - - - - - - Concentration defined in grams per cubic centimetre. - - - - - - A measure of concentration defined in µg/m3 (microgrammes/cubic metre). - - - - - - A measure of traffic density defined in number of vehicles per kilometre of road. - - - - - - 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). - - - - - Restricted for use only by authorities, traffic operators, publishers (service providers) and variable message signs. - - - - - - - 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. - - - - - Road widening work at the specified location - - - - - - - List of countries. - - - - - Austria - - - - - Belgium - - - - - Bulgaria - - - - - Switzerland - - - - - Serbia and Montenegro - - - - - Cyprus - - - - - Czech Republic - - - - - Germany - - - - - Denmark - - - - - Estonia - - - - - Spain - - - - - Finland - - - - - Faroe Islands - - - - - France - - - - - Great Britain - - - - - Guernsey - - - - - Gibraltar - - - - - 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. - - - - - - - A volumetric measure defined in cubic metres. - - - - - - - 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. - - - - - - - A combination of integer-valued year, month, day, hour, minute properties, a decimal-valued second property and a timezone property from which it is possible to determine the local time, the equivalent UTC time and the timezone offset from UTC. - - - - - - 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. - - - - - - - Specification of periods defined by the intersection of days, weeks and months. - - - - - Applicable day of the week. "All days of the week" is expressed by non-inclusion of this attribute. - - - - - Applicable week of the month (1 to 5). "All weeks of the month" is expressed by non-inclusion of this attribute. - - - - - Applicable month of the year. "All months of the year" is expressed by non-inclusion of this attribute. - - - - - - - - Classifications of a delay banded by length (i.e. the additional travel time). - - - - - Negligible delay. - - - - - Delay up to ten minutes. - - - - - Delay between ten minutes and thirty minutes. - - - - - Delay between thirty minutes and one hour. - - - - - Delay between one hour and three hours. - - - - - Delay between three hours and six hours. - - - - - Delay longer than six hours. - - - - - - - The details of the delays being caused by the situation element defined in the situation record. It is recommended to only use one of the optional attributes to avoid confusion. - - - - - The time band within which the additional travel time due to adverse travel conditions of any kind falls, when compared to "normal conditions". - - - - - Coarse 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. - - - - - Anticlockwise direction of travel on a ring road. - - - - - Clockwise direction of travel on a ring road. - - - - - North bound direction of travel. - - - - - North east bound direction of travel. - - - - - East bound direction of travel. - - - - - South east bound direction of travel. - - - - - South bound direction of travel. - - - - - South west bound direction of travel. - - - - - West bound direction of travel. - - - - - North west bound direction of travel. - - - - - Heading towards town centre direction of travel. - - - - - Heading out of or away from the town centre direction of travel. - - - - - - - Deliberate human action of either a public disorder nature or of a situation alert type which could disrupt traffic. - - - - - - - Includes all situations of a public disorder type or of an alert type, with potential to disrupt traffic. - - - - - - - - - - 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 an attack on a vehicle or its occupants has taken place. - - - - - A manned blockade or barrier across a road stopping vehicles passing. - - - - - An alert to a situation where suspected or actual explosive or incendiary devices may cause disruption to traffic. - - - - - 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 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. - - - - - A situation of public disorder, with potential to disrupt traffic. - - - - - An alert to a radioactive leak which may endanger the public and hence may cause traffic disruption. - - - - - A situation of public disorder involving violent behaviour and/or destruction of property with the potential to disrupt traffic. - - - - - A situation resulting from any act of sabotage. - - - - - An official alert 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 stolen. - - - - - An alert to a toxic release of gases and/or particulates into the environment which may endanger the public and hence may cause traffic disruption. - - - - - An alert to a perceived or actual threat of an unspecified nature, which could disrupt traffic. - - - - - 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. - - - - - - - An 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 snow slides. - - - - - 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. - - - - - Falling ice off trees, power lines or structures which may cause traffic disruption. - - - - - Falling light ice or snow off trees, power lines or structures which may cause traffic disruption. - - - - - 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 forest fire adjacent to the roadway. - - - - - 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 is obstructed or partially obstructed by overflows from one or more sewers. - - - - - 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. - - - - - Smoke or fumes which may hinder driving conditions or distract drivers. - - - - - 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. - - - - - - - Equipment or system which is faulty, malfunctioning or not in a fully operational state that may be of interest or concern to road operators and road users. - - - - - - - Failure, malfunction or non operational condition of equipment or system. - - - - - The type of equipment or system which is faulty, malfunctioning or not in a fully operational state. - - - - - - - - - - Types of fault, malfunctioning or non operational conditions of equipment or systems. - - - - - Not working or functioning. - - - - - Out of service (usually for operational reasons). - - - - - Working incorrectly. - - - - - Working intermittently. - - - - - - - Types of equipment and systems used to support the operation of the road network. - - - - - Automated toll system. - - - - - Emergency roadside telephones. - - - - - Gallery lights. - - - - - Signs used to control lane usage (e.g. in tidal flow systems or hard shoulder running). - - - - - Level crossing (barriers and signals). - - - - - Matrix signs. These normally comprise a symbol display area surrounded by four lights (usually amber) which flash when a symbol is displayed. - - - - - Ramp control equipment. - - - - - Roadside communications system which is used by one or more roadside equipments or systems. - - - - - Roadside power system which is used by one or more roadside equipments or systems. - - - - - Signs used to control traffic speed. - - - - - Street or road lighting. - - - - - Temporary traffic lights. - - - - - Toll gates. - - - - - Sets of traffic lights. - - - - - Traffic signals. - - - - - Tunnel lights. - - - - - Tunnel ventilation system. - - - - - Variable message signs. - - - - - Other than as defined in this enumeration. - - - - - - - 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. - - - - - For "Client Pull" exchange mode (operating mode 3 - snapshot) it defines the date/time at which the snapshot was produced. - - - - - For "Client Pull" exchange mode (operating mode 3 - snapshot) it defines the date/time after which the snapshot is no longer considered valid. - - - - - Indicator that this exchange is due to "keep alive" functionality. - - - - - The type 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. - - - - - - - - - - - - - - - - - - A location defined by reference to an external/other referencing system. - - - - - A code in the external referencing system which defines the location. - - - - - Identification of the external/other location referencing system. - - - - - - - - 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. - - - - - - - - A floating point number whose value space consists of the values m × 2^e, where m is an integer whose absolute value is less than 2^24, and e is an integer between -149 and 104, inclusive. - - - - - - Type of fuel used by a vehicle. - - - - - Battery. - - - - - Biodiesel. - - - - - Diesel. - - - - - Diesel and battery hybrid. - - - - - Ethanol. - - - - - Hydrogen. - - - - - Liquid gas of any type including LPG. - - - - - Liquid petroleum gas. - - - - - Methane gas. - - - - - Petrol. - - - - - Petrol and battery hybrid. - - - - - - - General instruction that is issued by the network/road operator which is applicable to drivers and sometimes passengers. - - - - - - - General instruction that is issued by the network/road operator which is applicable to drivers and sometimes passengers. - - - - - - - - - - General instructions that may be issued to road users (specifically drivers and sometimes passengers) by an operator or operational system in support of network management activities. - - - - - Allow emergency vehicles to pass. - - - - - Approach with care. - - - - - Drivers are to avoid the area. - - - - - Close all windows and turn off heater and vents. - - - - - Cross junction with care. - - - - - Do not allow unnecessary gaps. - - - - - Do not leave your vehicle. - - - - - Do not throw out any burning objects. - - - - - Do not use navigation systems to determine routing. - - - - - Drive carefully. - - - - - Drive with extreme caution. - - - - - Flash your lights to warn oncoming traffic of hazard ahead. - - - - - Follow the vehicle in front, smoothly. - - - - - Increase normal following distance. - - - - - In emergency, wait for patrol service (either road operator or police patrol service). - - - - - Keep your distance. - - - - - Leave your vehicle and proceed to next safe place. - - - - - No naked flames. - - - - - No overtaking on the specified section of road. - - - - - No smoking. - - - - - No stopping. - - - - - No U-turns. - - - - - Observe signals. - - - - - Observe signs. - - - - - Only travel if absolutely necessary. - - - - - Overtake with care. - - - - - 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 bus service. - - - - - Use fog lights. - - - - - Use hazard warning lights. - - - - - Use headlights. - - - - - Use rail service. - - - - - Use tram service. - - - - - Use underground service. - - - - - Wait for escort vehicle. - - - - - Other than as defined in this enumeration. - - - - - - - Network management action that is instigated either manually or automatically by the network/road operator. Compliance with any resulting control may be advisory or mandatory. - - - - - - - The type of traffic management action instigated by the network/road operator. - - - - - Type of person that is manually directing traffic (applicable if generalNetworkManagementType is set to "trafficBeingManuallyDirected"). - - - - - - - - - - Types of network management actions. - - - - - The bridge at the specified location has swung or lifted and is therefore temporarily closed to traffic. - - - - - A convoy service is in operation. - - - - - Signs are being put out before or around an obstacle to protect drivers. - - - - - Ramp metering is now active at the specified location. - - - - - Traffic is being controlled by temporary traffic lights (red-yellow-green or red-green). - - - - - Toll gates are open with no fee collection at the specified location. - - - - - Traffic is being manually directed. - - - - - Traffic in the specified direction is temporarily held up due to an unplanned event (e.g. for clearance of wreckage following an accident). - - - - - Other than as defined in this enumeration. - - - - - - - Any stationary or moving obstacle of a physical nature, other than of an animal, vehicle, environmental, or damaged equipment nature. - - - - - - - Characterization of the type of general obstruction. - - - - - - - - - - - A publication used to make level B extensions at the publication level. - - - - - - - The name of the generic publication. - - - - - - - - - - A generic SituationRecord for use when adding level B extensions at the SituationRecord level. - - - - - - - The name of the GenericSituationRecord. - - - - - - - - - - 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. - - - - - - - - - - A group of one or more physically separate locations which have no specific order. - - - - - - - Location contained in a non ordered group of locations. - - - - - - - - - - Group of people involved in the event having common characteristics and/or status. - - - - - The number of people of this group that are involved. - - - - - The injury status of the people involved. - - - - - The involvement role of the people. - - - - - The category of persons involved. - - - - - - - - Group of the vehicles involved having common characteristics and/or status. - - - - - The number of vehicles of this group that are involved. - - - - - Vehicle status. - - - - - - - - - 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 of the geographic area 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 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. - - - - - - - - Details of atmospheric humidity. - - - - - The amount of water vapour in the air, as a percentage of the amount of water vapour in saturated air at the same temperature and at atmospheric pressure. The measurement is taken between 1.5 and 2 m above the ground and behind a meteo screen. - - - - - - - - Measurements of atmospheric humidity. - - - - - - - - - - - - - An assessment of the impact that an event or operator action defined by the situation record has on the driving conditions. - - - - - The ratio of current capacity to the normal (free flow) 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 usable lanes on the carriageway which are now restricted either fully or partially (this may include the hard shoulder if it is normally available for operational use, e.g. in hard shoulder running schemes). - - - - - The number of usable lanes in the specified direction which remain fully operational (this may include the hard shoulder if it is being used as an operational lane). - - - - - The normal number of usable lanes in the specified direction that the carriageway has before reduction due to roadworks or traffic events. - - - - - The total width of the combined operational lanes in the specified direction. - - - - - The type of constriction to which traffic is subjected as a result of an event or operator action. - - - - - - - - - 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. - - - - - - - An obstruction on the road resulting from the failure or damage of infrastructure on, under, above or close to the road. - - - - - - - Characterization of an obstruction on the road resulting from the failure or damage of infrastructure on, under, above or close to the road. - - - - - - - - - - Types of infrastructure 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 surface has sunken or collapsed in places due to sewer failure. - - - - - Damage to a bridge that may cause traffic disruption. - - - - - Damage to a crash barrier that may cause traffic disruption. - - - - - Damage to an elevated section of the carriageway over another carriageway that may cause traffic disruption. - - - - - Damage to a gallery that may cause traffic disruption. - - - - - Damage to a gantry above the roadway that may cause traffic disruption. - - - - - Damage to the road surface that may cause traffic disruption. - - - - - Damage to a tunnel that may cause traffic disruption. - - - - - Damage to a viaduct that may cause traffic disruption. - - - - - 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. - - - - - Weak bridge capable of carrying a reduced load, typically with a reduced weight limit restriction imposed. - - - - - Other than as defined in this enumeration. - - - - - - - Types of injury status of people. - - - - - Dead. - - - - - Injured requiring medical treatment. - - - - - Seriously injured requiring urgent hospital treatment. - - - - - Slightly injured requiring medical treatment. - - - - - Uninjured. - - - - - Injury status unknown. - - - - - - - A measure of the quantity of application of a substance to an area defined in kilogrammes per square metre. - - - - - - A measure of precipitation intensity defined in millimetres per hour. - - - - - - 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. - - - - - - - A group of one or more physically separate locations arranged as an ordered set that defines an itinerary or route. The index indicates the order. - - - - - - - Location contained in an itinerary (i.e. an ordered set of locations defining a route or itinerary). - - - - - - - - - - - - Destination of a route or final location in an itinerary. - - - - - - - - - - A measure of speed defined in kilometres per hour. - - - - - - 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 carriageways 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. - - - - - - - A language datatype, identifies a specified language. - - - - - - 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 (true) or not (false). If finished (i.e. end is true) then the overallEndTime in the OverallPeriod class associated with the SituationRecord must be populated. - - - - - - - - A linear section along a single road with optional directionality defined between two points on the same 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. - - - - - No load. - - - - - 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. - - - - - Any goods of a commercial nature. - - - - - Materials classed as being of a hazardous nature. - - - - - Liquid of an unspecified 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. - - - - - Materials classed as being dangerous when exposed to water (e.g. materials which may react exothermically with water). - - - - - 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 or petroleum. - - - - - 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 which may be used by clients for visual display on user interfaces. - - - - - - - - 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. - - - - - On the carriageway or lane which is inbound towards the centre of the town or city. - - - - - In gallery. - - - - - 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 elevated section of road. - - - - - On flyover, i.e. on section of road over another road. - - - - - 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. - - - - - On underground section of road. - - - - - On underpass, i.e. section of road which passes under another road. - - - - - On the carriageway or lane which is outbound from the centre of the town or city. - - - - - Over the crest of a hill. - - - - - On the main carriageway within a junction between exit slip road and entry slip road. - - - - - - - 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. - - - - - - - Details of the maintenance vehicles involved in the roadworks activity. - - - - - 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. - - - - - - - - Roadworks involving the maintenance or installation of infrastructure. - - - - - - - The type of road maintenance or installation work at the specified location. - - - - - - - - - - A cause of this situation record which is managed by the publication creator, i.e. one which is represented by another situation record produced by the same publication creator. - - - - - - - A reference to another situation record produced by the same publication creator which defines a cause of the event defined here. - - - - - - - - - - Information relating to the management of the situation record. - - - - - - - - - - Types of matrix sign faults. - - - - - Comunications failure affecting matrix sign. - - - - - Incorrect aspect (face) is being displayed. - - - - - Not currently in service (e.g. intentionally disconnected or switched off during roadworks). - - - - - 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 individual vehicle measurements. - - - - - 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 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. - - - - - Measured or derived visibility information. - - - - - Measured or derived wind information. - - - - - - - Contains optional characteristics for the specific measured value (indexed to correspond with the defined characteristics of the measurement at the referenced measurement site) which override the static characteristics defined in the MeasurementSiteTable. - - - - - 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. - - - - - The version of the measurement site record, managed by systems external to DATEX II. - - - - - The date/time that this version of the measurement site record was defined. This is managed by systems external to DATEX II. - - - - - 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. - - - - - Composition to the indexed measurement specific characteristics associated with the measurement site. The index uniquely associates the measurement characteristics with the corresponding indexed measurement values for the measurement site. - - - - - - - - - - - - - - - - - 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 identification 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 value 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 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. 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. - - - - - - - - - A measure of distance defined in metres in a floating point format. - - - - - - A measure of distance defined in metres in a non negative integer format. - - - - - - An indication of whether the associated instance of a SituationRecord is mobile (e.g. a march or parade moving along a road) or stationary. - - - - - An indication of whether the associated instance of a SituationRecord is mobile (e.g. a march or parade moving along a road) or stationary. - - - - - - - - Types of mobility relating to a situation element defined by a SituationReord. - - - - - The described element of a situation is moving. - - - - - The described element of a situation is stationary. - - - - - The mobility of the described element of a situation 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). - - - - - - - - - - - - - - Network management action which is applicable to the road network and its users. - - - - - - - Defines whether the network management instruction or the control resulting from a network management action is advisory or mandatory. - - - - - The ultimate traffic direction to which the network management is applicable. - - - - - The type of traffic to which the network management is applicable. - - - - - Places, in generic terms, at which the network management applies. - - - - - Defines whether the network management is initiated by an automatic system. - - - - - The characteristics of those vehicles for which the network management is applicable. - - - - - - - - - - A cause of this situation record which is not managed by the publication creator, i.e. one which is not represented by another situation record produced by the same publication creator. - - - - - - - Description of a cause which is not managed by the publication creator (e.g. an off network cause). - - - - - Indicates an external influence that may be the causation of components of a situation. - - - - - - - - - - An integer number whose value space is the set {0, 1, 2, ..., 2147483645, 2147483646, 2147483647}. - - - - - - 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 diesel on the road. - - - - - 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 petrol on road. - - - - - The road surface is damaged, severely rutted or potholed (i.e. it is in a poor state of repair). - - - - - The road surface is slippery due to an unspecified cause. - - - - - Other than as defined in this enumeration. - - - - - - - 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. - - - - - The mobility of the obstruction. - - - - - - - - - - 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. - - - - - Scattered fragments of wreckage or other material on the road. - - - - - 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. - - - - - Unspecified hazard(s) on the road 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. - - - - - Industrial accident near the roadway 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 hazard 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. - - - - - "Subscription Management Mechanism" - a specialized operating mode to handle subscriptions. - - - - - "Publisher Push on Occurrence" operating mode. - - - - - "Publisher Push Periodic" operating mode. - - - - - "Client Pull" operating mode. - - - - - - - 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. - - - - - - - - - - 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. - - - - - A request, either internal or external, has been received to implement an action. It has neither been approved nor has any activity yet been undertaken to implement the action. - - - - - The action has been approved by the recipient of the request but activity to implement the action has not yet commenced. - - - - - The action is in the process of being implemented. - - - - - The action is fully implemented. - - - - - The action has been rejected by the recipient of the request and hence is not implemented. - - - - - A request, either internal or external, has been received to terminate the action, but activity to terminate the action has not yet commenced. - - - - - The action is in the process of being terminated either because the action has reached the end of its validity period or because new circumstances have arisen and its termination has been requested, e.g. because of a traffic jam on the alternative route. - - - - - - - A continuous or discontinuous 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 single time period, a recurring time period or a set of different recurring time periods during which validity is true. - - - - - A single time period, a recurring time period or a set of different recurring time periods during which validity is false. - - - - - - - - Levels of severity of a situation as whole assessed by the impact that the situation 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 medium level. - - - - - Perceived by supplier as being of a low level. - - - - - Perceived by supplier as being of the lowest discernible level. - - - - - Perceived by supplier as having a severity rating of none. - - - - - Perceived by supplier as being of an unknown level. - - - - - - - Passenger car units per hour. - - - - - - 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 description of the information which is to be found in the publications originating from the particular feed (URL). - - - - - 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. - - - - - - - - The default language used throughout the payload publications, specified by an ISO 639-2 3-alpha code. - - - - - - A measure of percentage. - - - - - - 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. - - - - - A recurring period of a day. - - - - - A recurring period defined in terms of days of the week, weeks of the month and months of the year. - - - - - - - - Categories of person. - - - - - Adult. - - - - - Child (age 4 to 17). - - - - - A member of the emergency services, other than the police. - - - - - A member of the fire service. - - - - - Infant (age 0 to 3). - - - - - A member of the medical service. - - - - - A member of the general public. - - - - - 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 member of the local traffic warden service. - - - - - A very important person. - - - - - - - List of types of places. - - - - - Around bends in the road. - - - - - At customs posts. - - - - - At high altitudes. - - - - - At toll plazas. - - - - - In galleries. - - - - - In low lying areas. - - - - - In roadworks areas. - - - - - In shaded areas. - - - - - In the city centre. - - - - - In the inner city areas. - - - - - In tunnels. - - - - - On bridges. - - - - - On elevated sections of the road. - - - - - On entering or leaving tunnels. - - - - - On entry into the country. - - - - - On flyover sections of the road, i.e. sections of the road which pass over another road. - - - - - On leaving the country. - - - - - On motorways. - - - - - On non motorways. - - - - - On roundabouts. - - - - - On slip roads. - - - - - On underground sections of the road. - - - - - On underpasses, i.e. sections of the road which pass under another road. - - - - - Over the crest of hills. - - - - - 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). - - - - - Polycyclic aromatic hydrocarbons. - - - - - 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. - - - - - 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. - - - - - Pollution of an unspecified nature. - - - - - 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. - - - - - - - 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. - - - - - - - Indication of whether precipitation is present or not. True indicates there is no precipitation. - - - - - - - - - - - Types of precipitation. - - - - - Light, fine rain. - - - - - Freezing 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 assigned to the 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 the set of predefined locations. - - - - - The version of the predefined location set. - - - - - - - - - - A publication containing one or more sets of predefined locations. - - - - - - - - - - - - - - Levels of confidence that the sender has in the information, ordered {certain, probable, risk of}. - - - - - The source is completely 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. - - - - - - - Organised public event which could disrupt traffic. - - - - - - - Type of public event which could disrupt traffic. - - - - - - - - - - Type of public event (Datex2 PublicEventTypeEnum and PublicEventType2Enum combined) - - - - - Unknown - - - - - Agricultural show or event which could disrupt traffic. - - - - - Air show or other aeronautical event which could disrupt traffic. - - - - - Art event that could disrupt traffic. - - - - - Athletics event that could disrupt traffic. - - - - - Beer festival 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. - - - - - Boat show which 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. - - - - - Commercial event which could disrupt traffic. - - - - - Concert event that could disrupt traffic. - - - - - Cricket match that could disrupt traffic. - - - - - Cultural event which 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 festival that could disrupt traffic. - - - - - Film or TV making event which could disrupt traffic. - - - - - Fireworks display that could disrupt traffic. - - - - - Flower event that could disrupt traffic. - - - - - Food festival that could disrupt traffic. - - - - - Football match that could disrupt traffic. - - - - - Periodic (e.g. annual), often traditional, gathering for entertainment, which could disrupt traffic. - - - - - Gardening and/or flower show or event 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 show which could disrupt traffic. - - - - - Motor sport race meeting that could disrupt traffic. - - - - - Open air concert that could disrupt traffic. - - - - - Formal display or organised procession which could disrupt traffic. - - - - - An 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. - - - - - Sound and light show 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. - - - - - Street festival that could disrupt traffic. - - - - - Tennis tournament that could disrupt traffic. - - - - - Theatrical event that could disrupt traffic. - - - - - Sporting event or series of events of unspecified type lasting more than one day which could disrupt traffic. - - - - - A periodic (e.g. annual), often traditional, gathering for trade promotion, which could disrupt traffic. - - - - - Water sports meeting that could disrupt traffic. - - - - - Wine festival that could disrupt traffic. - - - - - Winter sports meeting or event (e.g. skiing, ski jumping, skating) that could disrupt traffic. - - - - - Other than as defined in this enumeration. - - - - - - - A reference to an identifiable object instance (e.g. a GUID reference). - - - - - - Directions of traffic flow relative to sequential numbering scheme of reference points. 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. - - - - - - - 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 assessment 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 flow is normal at the specified location at this date/time. - - - - - Traffic is lighter than normally expected at the specified location at this date/time. - - - - - Traffic is very much 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. - - - - - A request for the supplier's catalogue. - - - - - A request for the client's filter as currently stored by the supplier. - - - - - A request for current data. - - - - - A request for historical data, i.e. data which was valid within an historical time window. - - - - - A request for a client's subscription as currently held by a supplier. - - - - - - - Rerouting management action that is issued by the network/road operator. - - - - - - - Type of rerouting management action instigated by operator. - - - - - A description of the rerouting itinerary. - - - - - Indication of whether the rerouting is signed. - - - - - The specified entry on to another road at which the alternative route commences. - - - - - The specified exit from the normal route/road at which the alternative route commences. - - - - - The intersecting road or the junction at which the alternative route commences. - - - - - The definition of the alternative route (rerouting) specified as an ordered set of locations (itinerary) which may be specific to one or more defined destinations. - - - - - - - - - - Management actions relating to rerouting. - - - - - Do not follow diversion signs. - - - - - Rerouted traffic is not to use the specified entry onto the identified road to commence the alternative route. - - - - - Rerouted traffic is not to use the specified exit from the identified road to commence the alternative route. - - - - - Rerouted traffic is not to use the specified intersection or junction. - - - - - Rerouted traffic is to follow the diversion signs. - - - - - Rerouted traffic is to follow local diversion. - - - - - Rerouted traffic is to follow the special diversion markers. - - - - - 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. - - - - - An acknowledgement that the supplier has received and complied with the client's request. - - - - - A notification that the supplier has denied the client's request for a catalogue. - - - - - A notification that the supplier has denied the client's request for a filter. - - - - - A notification that the supplier has denied the client's request for a data. - - - - - A notification that the supplier has denied the client's request for a subscription. - - - - - - - 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 an unspecified nature. - - - - - Controlled avalanche work. - - - - - Installation of new equipments or systems on or along-side the roadway. - - - - - Grass cutting work. - - - - - Maintenance of road, associated infrastructure or equipments. - - - - - Works which are overhead of the carriageway. - - - - - 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. - - - - - Spreading of salt and / or grit on the road surface to prevent or melt snow or ice. - - - - - Snowploughs or other similar mechanical devices in use to clear snow from the road. - - - - - Tree and vegetation cutting work adjacent to the roadway. - - - - - Other than as defined in this enumeration. - - - - - - - Details of disruption to normal road operator services - - - - - - - The type of road operator service which is disrupted. - - - - - - - - - - Types of disruption to road operator services relevant to road users. - - - - - Emergency telephone number for use by public to report incidents is out of service. - - - - - Road information service telephone number is out of service. - - - - - No traffic officer patrol service is operating. - - - - - - - Road, carriageway or lane management action that is instigated by the network/road operator. - - - - - - - Type of road, carriageway or lane management action instigated by operator. - - - - - The minimum number of persons required in a vehicle in order for it to be allowed to transit the specified road section. - - - - - The carriageway which is the subject of the management action. - - - - - The lane which is the subject of the management action. - - - - - - - - - - Management actions relating to road, carriageway or lane usage. - - - - - Dedicated car pool lane(s) are in operation for vehicles carrying at least the specified number of occupants. - - - - - Carriageway closures are in operation at the specified location. - - - - - Clear a lane for emergency vehicles. - - - - - Clear a lane for snow ploughs and gritting vehicles. - - - - - 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. - - - - - Do not use the specified lane(s) or carriageway(s). - - - - - The hard shoulder is open as an operational lane. - - - - - Road closures occur intermittently on the specified road in the specified direction for short durations. - - - - - Keep to the left. - - - - - Keep to the right. - - - - - Lane closures are in operation at the specified location for vehicles with the specified characteristics or all, if none defined, in the specified direction. - - - - - Lane deviations are in operation at the specified location. - - - - - Normal lane widths are temporarily reduced. - - - - - A new layout of lanes/carriageway has been implemented associated with roadworks. - - - - - 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. - - - - - The road has been cleared of earlier reported problems. - - - - - The road is closed to vehicles with the specified characteristics or all, if none defined, in the specified direction. - - - - - Traffic officers or police are driving slowly in front of a queue of traffic to create a gap in the traffic to allow for clearance activities to take place in safety on the road ahead. - - - - - 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. - - - - - Dedicated tidal flow lane(s) are in operation in the specified direction. - - - - - Traffic is being directed back down the opposite carriageway, possibly requiring the temporary removal of the central crash barrier. - - - - - The specified lane(s) or carriageway(s) may be used. The normal lane(s) or carriageway(s) restrictions are not currently in force. - - - - - Use the specified lane(s) or carriageway(s). - - - - - Vehicles are being stored on the roadway and/or at a rest area or service area at the specified location. - - - - - Other than as defined in this enumeration. - - - - - - - Details of road side assistance required or being given. - - - - - - - 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. - - - - - - - One of a sequence of roadside reference points along a road, normally spaced at regular intervals along each carriageway with a sequence of identification from a known starting point. - - - - - Roadside reference point identifier, unique on the specified road. - - - - - Identification of the road administration area which contains the reference point. - - - - - Name of a road. - - - - - 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 roadside reference point. - - - - - The distance of the roadside reference point from the starting point of the sequence on the road. - - - - - - - - A linear section along a single road defined between two points on the same road identified by roadside reference points. - - - - - - - - - - The point (called Primary point) which is at the downstream end of a linear road section. The point is identified by a roadside reference point. - - - - - - - - - The point (called Secondary point) which is at the upstream end of a linear road section. The point is identified by a roadside reference point. - - - - - - - - - Details of disruption to normal roadside services (e.g. specific services at a service areas). - - - - - - - The type of roadside service which is disrupted. - - - - - - - - - - Types of disruption to roadside 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. - - - - - - - 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. - - - - - - - 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 under traffic or not under traffic. 'True' indicates the road is under traffic. - - - - - 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. - - - - - - - Seconds. - - - - - - 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. - - - - - Composition to the indexed measured value associated with the measurement site. The index uniquely associates the measurement value with the corresponding indexed measurement characteristics defined for the measurement site. - - - - - - - - - - - - - - - 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. - - - - - Each situation may iterate through a series of versions during its life time. The situation version uniquely identifies the version of the situation. It is generated and used by systems external to DATEX II. - - - - - The date/time that this current version of the Situation was written into the database of the supplier which is involved in the data exchange. - - - - - - - - - - - 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 II. - - - - - 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. - - - - - The extent to which the related information may be circulated, according to the recipient type. Recipients must comply with this confidentiality statement. This overrides any confidentiality defined for the situation as a whole in the header information. - - - - - An assessment of the degree of likelihood that the reported event will occur. - - - - - - - - - A comment which may be freely distributed to the general public - - - - - A comment which should not be distributed to the general public. - - - - - - - - - - - - Details of the source from which the information was obtained. - - - - - ISO 3166-1 two character country code of the source of the information. - - - - - Identifier 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. - - - - - - - Speed management action that is instigated by the network/road operator. - - - - - - - Type of speed management action instigated by operator. - - - - - Temporary limit defining the maximum advisory or mandatory speed of vehicles. - - - - - - - - - - Management actions relating to speed. - - - - - Automatic speed control measures are in place at the specified location, whereby speed limits are set by an automatic system which is triggered by traffic sensing equipment. - - - - - Do not slow down unnecessarily. - - - - - Observe speed limit. - - - - - Police speed checks are in operation. - - - - - Reduce your speed. - - - - - Other than as defined in this enumeration. - - - - - - - Details of percentage (from an observation set) of vehicles whose speeds fall below a stated value. - - - - - The percentage of vehicles from the observation set whose speeds fall below the stated speed (speedPercentile). - - - - - The speed below which the associated percentage of vehicles in the measurement set are travelling at. - - - - - - - - A character string whose value space is the set of finite-length sequences of characters. Every character has a corresponding Universal Character Set code point (as defined in ISO/IEC 10646), which is an integer. - - - - - - - - The subjects with which the roadworks are associated. - - - - - The subject type 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. - - - - - Crash barrier. - - - - - Gallery. - - - - - Gantry over or above the roadway. - - - - - Gas mains. - - - - - Motorway or major road interchange. - - - - - Motorway or major road junction. - - - - - Level-crossing or associated equipment. - - - - - Road lighting system. - - - - - Equipment used for determining traffic measurements. - - - - - Installations along the roadway designed to reduce road noise in the surrounding environment. - - - - - Road. - - - - - Roadside drains. - - - - - Roadside embankment. - - - - - Roadside equipment. - - - - - Road signs. - - - - - Roundabout. - - - - - Toll gate. - - - - - 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. - - - - - The client's subscription as registered with a supplier is currently active. - - - - - The client's subscription as registered with a supplier is currently suspended. - - - - - - - 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. - - - - - Indicates that the location is given with a precision which is better than the stated value in metres. - - - - - The sequential number of an exit/entrance ramp from a given location in a given direction (normally used to indicate a specific exit/entrance in a complex junction/intersection). - - - - - - - - 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. - - - - - - - - A measure of temperature defined in degrees Celsius. - - - - - - Measurements of atmospheric temperature. - - - - - - - - - - - - - An instant of time that recurs every day. The value space of time is the space of time of day values as defined in § 5.3 of [ISO 8601]. Specifically, it is a set of zero-duration daily time instances. - - - - - - 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. - - - - - - - - A measure of weight defined in metric tonnes. - - - - - - A descriptor for describing an area location. - - - - - - - The nature of the descriptor used to define the location 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 discrimination. - - - - - The type of TPEG location. - - - - - - - - - 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. - - - - - - - - A point on the road network which is framed between two other points on the same road. - - - - - - - The type of TPEG location. - - - - - A single non junction point on the road network which is framed between two other specified points on the road network. - - - - - The location at the down stream end of the section of road which frames the TPEGFramedPoint. - - - - - The location at the up stream end of the section of road which frames the TPEGFramedPoint. - - - - - - - - - - A geometric area defined by a centre point and a radius. - - - - - - - The radius of the geometric area identified. - - - - - Centre point of a circular geometric area. - - - - - Name of area. - - - - - - - - - - Height information which provides additional discrimination 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 location under consideration (derived from the TPEG Loc table 03). - - - - - - - - - - A point on the road network which is a road junction point. - - - - - - - - A name which identifies a junction point on the road network - - - - - A descriptor for describing a junction by identifying the intersecting roads at a road junction. - - - - - A descriptive name which helps to identify the junction point. - - - - - - - - - - A descriptor for describing a point at a junction on a road network. - - - - - - - The nature of the descriptor used to define the location under consideration (derived from the TPEG Loc table 03). - - - - - - - - - - A linear section along a single road defined between two points on the same road by a TPEG-Loc structure. - - - - - The direction of traffic flow. - - - - - The type of TPEG location. - - - - - The location at the down stream end of the linear section of road. - - - - - The location at the up stream end of the linear section of road. - - - - - - - - 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 an area. - - - - - Name of a county (administrative sub-division). - - - - - Name of a lake. - - - - - Name of a 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 administrative area. - - - - - Reference name by which an administrative area is known. - - - - - Name of an airport. - - - - - Name of an area. - - - - - 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 county (administrative sub-division). - - - - - 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 nation (e.g. Wales) which is a sub-division of a ISO recognised country. - - - - - 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 a general point of interest. - - - - - Name of a railway station. - - - - - Name of a geographic region. - - - - - 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. - - - - - - - Name of area. - - - - - - - - - - A point on the road network which is not a road junction point. - - - - - - - - A descriptive name which helps to identify the non junction point. At least one descriptor must identify the road on which the point is located, i.e. must be of type 'linkName' or 'localLinkName'. - - - - - - - - - - General descriptor for describing a point. - - - - - - - The nature of the descriptor used to define the location under consideration (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. - - - - - - - - A point on the road network which is not bounded by any other points on the road network. - - - - - - - The type of TPEG location. - - - - - A single point defined by a coordinate set and TPEG decriptors. - - - - - - - - - - Averaged measurements of traffic concentration. - - - - - - - An averaged measurement of the concentration of vehicles at the specified measurement site. - - - - - An averaged measurement of the percentage of time that a section of road at the specified measurement site is occuppied by vehicles. - - - - - - - - - - Types of constriction 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. - - - - - 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. - - - - - - - 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 site. - - - - - An averaged measurement of flow rate defined in terms of the number of passenger car units passing the specified measurement site. - - - - - An averaged measurement of the percentage of long vehicles contained in the traffic flow at the specified measurement site. - - - - - An averaged measurement of flow rate defined in terms of the number of vehicles passing the specified measurement site. - - - - - - - - - - A collection of terms for describing the characteristics of traffic flow. - - - - - Traffic flow is of an irregular nature, subject to sudden changes in rates. - - - - - Traffic flow is smooth. - - - - - Traffic flow is of a stop and go nature with queues forming and ending continuously on the specified section of road. - - - - - Traffic is blocked at the specified location and in the specified direction due to an unplanned event. - - - - - - - Averaged measurements of traffic headway, i.e. the distance or time interval 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 site. - - - - - 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 site. - - - - - - - - - - Averaged measurements of traffic speed. - - - - - - - An averaged measurement of the speed of vehicles at the specified measurement site. - - - - - - - - - - - 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 characterization 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. - - - - - - - Types of traffic, mostly classified by its destination type. - - - - - Traffic destined for local access only. - - - - - Traffic destined for the airport. - - - - - Traffic destined for airport arrivals. - - - - - Traffic destined for airport departures. - - - - - Traffic destined for the ferry service. - - - - - Traffic destined for the rail service. - - - - - Traffic heading towards holiday destinations. - - - - - Traffic heading towards local destinations. - - - - - Traffic heading towards destinations which are a long distance away. - - - - - Traffic heading towards local regional destinations. - - - - - Local residents only traffic. - - - - - Traffic which is not for local access, i.e. traffic not destined for local town, city or built up area but for transit though the area. - - - - - Traffic heading towards local visitor attraction. - - - - - - - Measured or derived values relating to traffic or individual vehicle movements on a specific section or at a specific point on the road network. - - - - - - - Used to define the vehicle characteristics to which the TrafficValue is applicable primarily in Elaborated Data Publications, but may also be used in Measured Data Publications to override vehicle characteristics defined for the measurement site. - - - - - - - - - - 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 which shall comprise at most one instance of each of the following: OperatorAction, TrafficElement, ElaboratedData and CCTVImages. - - - - - 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 flotsam. - - - - - The departure of the specified service is on schedule. - - - - - The ferry service has been replaced by an ice road. - - - - - A shuttle service is operating at no charge between specified locations until the specified time. - - - - - The information service relating to the specified transport system is not currently available. - - - - - The specified service is subject to irregular delays. - - - - - The load capacity for the specified service has been changed. - - - - - 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 until the specified time. - - - - - 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. - - - - - Vehicle type. - - - - - - - - - - The types of updates of situations that may be requested by a client. - - - - - The client has currently requested that all situation elements are sent when one or more component elements are updated. - - - - - The client has currently requested that only the individual elements of a situation that have changed are sent when updated. - - - - - The client has requested that all situations and their elements which are valid at the time of request be sent together, i.e. a snapshot in time of all valid situations. - - - - - - - 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. - - - - - - - A Uniform Resource Locator (URL) address comprising a compact string of characters for a resource available on the Internet. - - - - - - Details of a Uniform Resource Locator (URL) address pointing to a resource available on the Internet from where further relevant information may be obtained. - - - - - A Uniform Resource Locator (URL) address pointing to a resource available on the Internet from where further relevant information may be obtained. - - - - - Description of the relevant information available on the Internet from the URL link. - - - - - Details of the type of relevant information available on the Internet from the URL link. - - - - - - - - Types of URL links. - - - - - URL link to a pdf document. - - - - - URL link to an html page. - - - - - URL link to an image. - - - - - URL link to an RSS feed. - - - - - URL link to a video stream. - - - - - URL link to a voice stream. - - - - - Other than as defined in this enumeration. - - - - - - - Specification of validity, either explicitly or by a validity time period specification which may be discontinuous. - - - - - Specification of validity, either explicitly overriding the validity time specification or confirming it. - - - - - The activity or action described by the SituationRecord is still in progress, overrunning its planned duration as indicated in a previous version of this record. - - - - - A specification of periods of validity defined by overall bounding start and end times and the possible intersection of valid periods with exception periods (exception periods overriding valid periods). - - - - - - - - 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. - - - - - - - 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. - - - - - - - - - - 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 which is updated by the ISO 3166 Maintenance Agency. - - - - - A vehicle identification number (VIN) comprising 17 characters that is based on either ISO 3779 or ISO 3780 and uniquely identifies the individual vehicle. This is normally securely attached to the vehicle chassis. - - - - - Indicates the stated manufacturer of the vehicle i.e. Ford. - - - - - Indicates the model (or range name) of the vehicle i.e. Ford Mondeo. - - - - - An identifier or code displayed on a vehicle registration plate attached to the vehicle used for official identification purposes. The registration identifier is numeric or alphanumeric and is unique within the issuing authority's region. - - - - - Vehicle status. - - - - - - The spacing between axles on the vehicles. - - - - - The weight details relating to a specific axle on the vehicle. - - - - - Details of hazardous goods carried by the vehicle. - - - - - - - - The characteristics 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. - - - - - Vehicle type. - - - - - 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 site. - - - - - 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 distance 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 site. - - - - - The measured distance between the front (respectively back) of this vehicle and the front (respectively back) of the preceding vehicle at the specified measurement site. - - - - - - - - An obstruction on the road caused by one or more vehicles. - - - - - - - Characterization of an obstruction on the road caused by one or more vehicles. - - - - - The obstructing vehicle. - - - - - - - - - - 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 experiencing difficulties (e.g. manoeuvring or propulsion difficulties) which may cause traffic disruption. - - - - - A vehicle is travelling the wrong way along a divided highway (i.e. on the wrong side). - - - - - 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 over-height 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. - - - - - - - Measurement of individual vehicle speed. - - - - - The measured speed of the individual vehicle at the specified measurement site. - - - - - - - - Vehicles per hour. - - - - - - 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. - - - - - Bicycle. - - - - - Bus. - - - - - Car. - - - - - Caravan. - - - - - Car or light vehicle. - - - - - Car towing a caravan. - - - - - Car towing a trailer. - - - - - Four wheel drive vehicle. - - - - - High sided vehicle. - - - - - Lorry of any type. - - - - - Moped (a two wheeled motor vehicle characterized by a small engine typically less than 50cc and by normally having pedals). - - - - - Motorcycle. - - - - - Three wheeled vehicle comprising a motorcycle with an attached side car. - - - - - Motor scooter (a two wheeled motor vehicle characterized by a step-through frame and small diameter wheels). - - - - - Vehicle with large tank for carrying bulk liquids. - - - - - Three wheeled vehicle of unspecified type. - - - - - Trailer. - - - - - Tram. - - - - - 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 usage of a vehicle. - - - - - Vehicle used for agricultural purposes. - - - - - Vehicle which is limited to non-private usage or public transport usage. - - - - - 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. road operator or automobile association patrol vehicle. - - - - - 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. - - - - - - - Details of atmospheric visibility. - - - - - The minimum 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. - - - - - Not currently in service (e.g. intentionally disconnected or switched off during roadworks). - - - - - 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. - - - - - - - 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 that is related to the weather 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). - - - - - 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 (with little or no traffic yet) 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. - - - - - The road surface is slippery due to bad weather conditions. - - - - - 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. - - - - - Water is resting on the roadway which provides an increased hazard to vehicles. - - - - - 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. - - - - - 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). - - - - - - - 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. - - - - - - - - - - - - - Winter driving management action that is instigated by the network/road operator. - - - - - - - Type of winter equipment management action instigated by operator. - - - - - - - - - - Instructions relating to the use of winter equipment. - - - - - Do not use stud tyres. - - - - - Use snow chains. - - - - - Use snow chains or snow tyres. - - - - - Use snow tyres. - - - - - The carrying of winter equipment (snow chains and/or snow tyres) is required. - - - - - Other than as defined in this enumeration. - - - - - + + + + + A traffic condition which is not normal. + + + + + + + A characterization 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. + + + + + Assessment of the traffic flow conditions relative to normally expected conditions at this date/time. + + + + + A characterization of the traffic flow. + + + + + A characterization 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 stationary, or very near stationary, at the specified location (i.e. average speed is less than 10% of its free-flow level). + + + + + Traffic is queuing at the specified location, although there is still some traffic movement (i.e. average speed is between 10% and 25% of its free-flow level). + + + + + Traffic is slow moving at the specified location, but not yet forming queues (i.e. average speed is between 25% and 75% of its free-flow level). + + + + + Traffic is heavy at the specified location (i.e. average speed is between 75% and 90% of its free-flow level). + + + + + There are abnormal traffic conditions of an unspecified nature at the specified location. + + + + + Other than as defined in this enumeration. + + + + + + + Accidents are events where one or more vehicles are involved in collisions or in leaving the roadway. These include collisions between vehicles or with other road users or obstacles. + + + + + + + A descriptor indicating the most significant factor causing an accident. + + + + + A characterization of the nature of the accident. + + + + + The total number of people that are involved. + + + + + The total number of vehicles that are involved. + + + + + The vehicle involved in the 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 impaired visibility. + + + + + Not keeping a safe distance from the vehicle in front. + + + + + 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. + + + + + 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 mass transit vehicle. + + + + + Includes all accidents involving at least one moped. + + + + + Includes all accidents involving at least one motorcycle. + + + + + Accident involving radioactive material. + + + + + 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 action external to the traffic stream or roadway which could disrupt traffic. + + + + + + + Mobility of the activity. + + + + + + + + + + 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. EN ISO 14819-3 for the allocation of a location table number. + + + + + Version number associated with an ALERT-C table reference. + + + + + Area location defined by a specific Alert-C location. + + + + + + + + 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 (i.e. valid only for ring roads) the sense in which navigation should be made from the primary location to the secondary location, to avoid ambiguity. TRUE indicates positive RDS direction, i.e. direction of coding of 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. EN ISO 14819-3 for the allocation of a location table number. + + + + + Version number associated with 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. + + + + + + + + Linear location defined by a specific Alert-C location. + + + + + + + + + + Identification of a specific point, linear or area location in an ALERT-C location table. + + + + + Name of ALERT-C location. + + + + + Unique code within the ALERT-C location table which identifies the specific point, linear or area location. + + + + + + + + A positive integer number (between 1 and 63,487) which uniquely identifies a pre-defined Alert C location defined within an Alert-C table. + + + + + + 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. EN ISO 14819-3 for the allocation of a location table number. + + + + + Version number associated with an ALERT-C table reference. + + + + + + + + An integer number representing an angle in whole degrees between 0 and 359. + + + + + + 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 discrimination (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. + + + + + + + Authority initiated operation or activity that could disrupt traffic. + + + + + + + Type of authority initiated operation or activity that could disrupt traffic. + + + + + + + + + + Types of authority operations. + + + + + An operation involving authorised investigation work connected to an earlier reported accident. + + + + + An operation where a bomb squad is in action to deal with suspected or actual explosive or incendiary devices which 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 permanent or temporary operation established by customs and excise authorities on or adjacent to the carriageway. + + + + + An operation involving the juridical reconstruction of events for the purposes of judicial or legal proceedings. + + + + + 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 use by the road operator, such as for survey or inspection purposes, but not for traffic management purposes. + + + + + A permanent or temporary operation established by authorities on or adjacent to the carriageway for the purpose of gathering statistics or other traffic related information. + + + + + An operation to transport one or more VIPs. + + + + + An authority activity of undefined type. + + + + + A permanent or temporary operation established on or adjacent to the carriageway for inspection of vehicles by authorities (e.g. vehicle safety checks and tachograph checks). + + + + + A permanent or temporary operation established on or adjacent to the carriageway for weighing of vehicles by authorities. + + + + + A permanent or temporary facility established by authorities on the carriageway for weighing vehicles while in motion. + + + + + 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 the interval between the axles of the individual vehicle from front to back (e.g. 1, 2, 3...). This cannot exceed (numberOfAxles -1) if the numberOfAxles is also given as part of the VehicleCharacteristics. + + + + + + + + Vehicle axles per hour. + + + + + + The weight details of a specific axle on the vehicle. + + + + + Indicates the position of the axle on the vehicle numbered from front to back (i.e. 1, 2, 3...). This cannot exceed the numberOfAxles if provided as part of VehicleCharacteristics. + + + + + The weight of the specific axle, indicated by the axleSequenceIdentifier, on the vehicle numbered from front to back of the vehicle. + + + + + The maximum permitted weight of this specific axle on the vehicle. + + + + + + + + Generic data value(s) of either measured or elaborated data. Where values of different type are given in a single instance the metadata contained in the BasicDataValue must be applicable to all, otherwise separate instances must be given. + + + + + The extent to which the 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. 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. + + + + + The location (e.g. the stretch of road or area) to which the data value is pertinent/relevant. This may be different from the location of the measurement equipment (i.e. the measurement site location). + + + + + + + + Boolean has the value space required to support the mathematical concept of binary-valued logic: {true, false}. + + + + + + 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 (duration) 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, i.e. the section of road passing over another. + + + + + On the left hand feeder road. + + + + + On the left hand parallel 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, i.e. the section of road passing under another. + + + + + + + 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. + + + + + An earlier accident. + + + + + An earlier event. + + + + + An earlier incident. + + + + + Failure of roadside equipment. + + + + + Excessive heat. + + + + + Frost. + + + + + Holiday traffic. + + + + + Failure of road infrastructure. + + + + + Large numbers of visitors. + + + + + Obstruction (of unspecified type) on the roadway. + + + + + An alert relating to dangerous levels of pollution. + + + + + 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. + + + + + Radioactive leak alert. + + + + + A roadside event (of unspecified nature) whether planned or not. + + + + + Drivers being distracted and turning to look at an accident or other roadside event. + + + + + A security incident. + + + + + Shear weight of traffic. + + + + + Technical problems. + + + + + A terrorist incident. + + + + + An alert relating to the release of toxic gases and/or particulates. + + + + + A vandalism incident. + + + + + Other than as defined in this enumeration. + + + + + + + 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 un-coded observations/information. + + + + + A free text comment that can be used by the operator to convey un-coded 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 "greater than or equal to". + + + + + Logical comparison operator of "less than". + + + + + Logical comparison operator of "less than or equal to". + + + + + + + Types of compliance. + + + + + Advisory compliance . + + + + + Mandatory compliance. + + + + + + + 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. + + + + + + + Concentration defined in grams per cubic centimetre. + + + + + + A measure of concentration defined in µg/m3 (microgrammes/cubic metre). + + + + + + A measure of traffic density defined in number of vehicles per kilometre of road. + + + + + + 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). + + + + + Restricted for use only by authorities, traffic operators, publishers (service providers) and variable message signs. + + + + + + + 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. + + + + + Road widening work at the specified location + + + + + + + List of countries. + + + + + Austria + + + + + Belgium + + + + + Bulgaria + + + + + Switzerland + + + + + Serbia and Montenegro + + + + + Cyprus + + + + + Czech Republic + + + + + Germany + + + + + Denmark + + + + + Estonia + + + + + Spain + + + + + Finland + + + + + Faroe Islands + + + + + France + + + + + Great Britain + + + + + Guernsey + + + + + Gibraltar + + + + + 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. + + + + + + + A volumetric measure defined in cubic metres. + + + + + + + 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. + + + + + + + A combination of integer-valued year, month, day, hour, minute properties, a decimal-valued second property and a timezone property from which it is possible to determine the local time, the equivalent UTC time and the timezone offset from UTC. + + + + + + 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. + + + + + + + Specification of periods defined by the intersection of days, weeks and months. + + + + + Applicable day of the week. "All days of the week" is expressed by non-inclusion of this attribute. + + + + + Applicable week of the month (1 to 5). "All weeks of the month" is expressed by non-inclusion of this attribute. + + + + + Applicable month of the year. "All months of the year" is expressed by non-inclusion of this attribute. + + + + + + + + Classifications of a delay banded by length (i.e. the additional travel time). + + + + + Negligible delay. + + + + + Delay up to ten minutes. + + + + + Delay between ten minutes and thirty minutes. + + + + + Delay between thirty minutes and one hour. + + + + + Delay between one hour and three hours. + + + + + Delay between three hours and six hours. + + + + + Delay longer than six hours. + + + + + + + The details of the delays being caused by the situation element defined in the situation record. It is recommended to only use one of the optional attributes to avoid confusion. + + + + + The time band within which the additional travel time due to adverse travel conditions of any kind falls, when compared to "normal conditions". + + + + + Coarse 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. + + + + + Anticlockwise direction of travel on a ring road. + + + + + Clockwise direction of travel on a ring road. + + + + + North bound direction of travel. + + + + + North east bound direction of travel. + + + + + East bound direction of travel. + + + + + South east bound direction of travel. + + + + + South bound direction of travel. + + + + + South west bound direction of travel. + + + + + West bound direction of travel. + + + + + North west bound direction of travel. + + + + + Heading towards town centre direction of travel. + + + + + Heading out of or away from the town centre direction of travel. + + + + + + + Deliberate human action of either a public disorder nature or of a situation alert type which could disrupt traffic. + + + + + + + Includes all situations of a public disorder type or of an alert type, with potential to disrupt traffic. + + + + + + + + + + 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 an attack on a vehicle or its occupants has taken place. + + + + + A manned blockade or barrier across a road stopping vehicles passing. + + + + + An alert to a situation where suspected or actual explosive or incendiary devices may cause disruption to traffic. + + + + + 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 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. + + + + + A situation of public disorder, with potential to disrupt traffic. + + + + + An alert to a radioactive leak which may endanger the public and hence may cause traffic disruption. + + + + + A situation of public disorder involving violent behaviour and/or destruction of property with the potential to disrupt traffic. + + + + + A situation resulting from any act of sabotage. + + + + + An official alert 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 stolen. + + + + + An alert to a toxic release of gases and/or particulates into the environment which may endanger the public and hence may cause traffic disruption. + + + + + An alert to a perceived or actual threat of an unspecified nature, which could disrupt traffic. + + + + + 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. + + + + + + + An 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 snow slides. + + + + + 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. + + + + + Falling ice off trees, power lines or structures which may cause traffic disruption. + + + + + Falling light ice or snow off trees, power lines or structures which may cause traffic disruption. + + + + + 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 forest fire adjacent to the roadway. + + + + + 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 is obstructed or partially obstructed by overflows from one or more sewers. + + + + + 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. + + + + + Smoke or fumes which may hinder driving conditions or distract drivers. + + + + + 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. + + + + + + + Equipment or system which is faulty, malfunctioning or not in a fully operational state that may be of interest or concern to road operators and road users. + + + + + + + Failure, malfunction or non operational condition of equipment or system. + + + + + The type of equipment or system which is faulty, malfunctioning or not in a fully operational state. + + + + + + + + + + Types of fault, malfunctioning or non operational conditions of equipment or systems. + + + + + Not working or functioning. + + + + + Out of service (usually for operational reasons). + + + + + Working incorrectly. + + + + + Working intermittently. + + + + + + + Types of equipment and systems used to support the operation of the road network. + + + + + Automated toll system. + + + + + Emergency roadside telephones. + + + + + Gallery lights. + + + + + Signs used to control lane usage (e.g. in tidal flow systems or hard shoulder running). + + + + + Level crossing (barriers and signals). + + + + + Matrix signs. These normally comprise a symbol display area surrounded by four lights (usually amber) which flash when a symbol is displayed. + + + + + Ramp control equipment. + + + + + Roadside communications system which is used by one or more roadside equipments or systems. + + + + + Roadside power system which is used by one or more roadside equipments or systems. + + + + + Signs used to control traffic speed. + + + + + Street or road lighting. + + + + + Temporary traffic lights. + + + + + Toll gates. + + + + + Sets of traffic lights. + + + + + Traffic signals. + + + + + Tunnel lights. + + + + + Tunnel ventilation system. + + + + + Variable message signs. + + + + + Other than as defined in this enumeration. + + + + + + + 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. + + + + + For "Client Pull" exchange mode (operating mode 3 - snapshot) it defines the date/time at which the snapshot was produced. + + + + + For "Client Pull" exchange mode (operating mode 3 - snapshot) it defines the date/time after which the snapshot is no longer considered valid. + + + + + Indicator that this exchange is due to "keep alive" functionality. + + + + + The type 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. + + + + + + + + + + + + + + + + + + A location defined by reference to an external/other referencing system. + + + + + A code in the external referencing system which defines the location. + + + + + Identification of the external/other location referencing system. + + + + + + + + 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. + + + + + + + + A floating point number whose value space consists of the values m × 2^e, where m is an integer whose absolute value is less than 2^24, and e is an integer between -149 and 104, inclusive. + + + + + + Type of fuel used by a vehicle. + + + + + Battery. + + + + + Biodiesel. + + + + + Diesel. + + + + + Diesel and battery hybrid. + + + + + Ethanol. + + + + + Hydrogen. + + + + + Liquid gas of any type including LPG. + + + + + Liquid petroleum gas. + + + + + Methane gas. + + + + + Petrol. + + + + + Petrol and battery hybrid. + + + + + + + General instruction that is issued by the network/road operator which is applicable to drivers and sometimes passengers. + + + + + + + General instruction that is issued by the network/road operator which is applicable to drivers and sometimes passengers. + + + + + + + + + + General instructions that may be issued to road users (specifically drivers and sometimes passengers) by an operator or operational system in support of network management activities. + + + + + Allow emergency vehicles to pass. + + + + + Approach with care. + + + + + Drivers are to avoid the area. + + + + + Close all windows and turn off heater and vents. + + + + + Cross junction with care. + + + + + Do not allow unnecessary gaps. + + + + + Do not leave your vehicle. + + + + + Do not throw out any burning objects. + + + + + Do not use navigation systems to determine routing. + + + + + Drive carefully. + + + + + Drive with extreme caution. + + + + + Flash your lights to warn oncoming traffic of hazard ahead. + + + + + Follow the vehicle in front, smoothly. + + + + + Increase normal following distance. + + + + + In emergency, wait for patrol service (either road operator or police patrol service). + + + + + Keep your distance. + + + + + Leave your vehicle and proceed to next safe place. + + + + + No naked flames. + + + + + No overtaking on the specified section of road. + + + + + No smoking. + + + + + No stopping. + + + + + No U-turns. + + + + + Observe signals. + + + + + Observe signs. + + + + + Only travel if absolutely necessary. + + + + + Overtake with care. + + + + + 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 bus service. + + + + + Use fog lights. + + + + + Use hazard warning lights. + + + + + Use headlights. + + + + + Use rail service. + + + + + Use tram service. + + + + + Use underground service. + + + + + Wait for escort vehicle. + + + + + Other than as defined in this enumeration. + + + + + + + Network management action that is instigated either manually or automatically by the network/road operator. Compliance with any resulting control may be advisory or mandatory. + + + + + + + The type of traffic management action instigated by the network/road operator. + + + + + Type of person that is manually directing traffic (applicable if generalNetworkManagementType is set to "trafficBeingManuallyDirected"). + + + + + + + + + + Types of network management actions. + + + + + The bridge at the specified location has swung or lifted and is therefore temporarily closed to traffic. + + + + + A convoy service is in operation. + + + + + Signs are being put out before or around an obstacle to protect drivers. + + + + + Ramp metering is now active at the specified location. + + + + + Traffic is being controlled by temporary traffic lights (red-yellow-green or red-green). + + + + + Toll gates are open with no fee collection at the specified location. + + + + + Traffic is being manually directed. + + + + + Traffic in the specified direction is temporarily held up due to an unplanned event (e.g. for clearance of wreckage following an accident). + + + + + Other than as defined in this enumeration. + + + + + + + Any stationary or moving obstacle of a physical nature, other than of an animal, vehicle, environmental, or damaged equipment nature. + + + + + + + Characterization of the type of general obstruction. + + + + + + + + + + + A publication used to make level B extensions at the publication level. + + + + + + + The name of the generic publication. + + + + + + + + + + A generic SituationRecord for use when adding level B extensions at the SituationRecord level. + + + + + + + The name of the GenericSituationRecord. + + + + + + + + + + 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. + + + + + + + + + + A group of one or more physically separate locations which have no specific order. + + + + + + + Location contained in a non ordered group of locations. + + + + + + + + + + Group of people involved in the event having common characteristics and/or status. + + + + + The number of people of this group that are involved. + + + + + The injury status of the people involved. + + + + + The involvement role of the people. + + + + + The category of persons involved. + + + + + + + + Group of the vehicles involved having common characteristics and/or status. + + + + + The number of vehicles of this group that are involved. + + + + + Vehicle status. + + + + + + + + + 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 of the geographic area 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 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. + + + + + + + + Details of atmospheric humidity. + + + + + The amount of water vapour in the air, as a percentage of the amount of water vapour in saturated air at the same temperature and at atmospheric pressure. The measurement is taken between 1.5 and 2 m above the ground and behind a meteo screen. + + + + + + + + Measurements of atmospheric humidity. + + + + + + + + + + + + + An assessment of the impact that an event or operator action defined by the situation record has on the driving conditions. + + + + + The ratio of current capacity to the normal (free flow) 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 usable lanes on the carriageway which are now restricted either fully or partially (this may include the hard shoulder if it is normally available for operational use, e.g. in hard shoulder running schemes). + + + + + The number of usable lanes in the specified direction which remain fully operational (this may include the hard shoulder if it is being used as an operational lane). + + + + + The normal number of usable lanes in the specified direction that the carriageway has before reduction due to roadworks or traffic events. + + + + + The total width of the combined operational lanes in the specified direction. + + + + + The type of constriction to which traffic is subjected as a result of an event or operator action. + + + + + + + + + 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. + + + + + + + An obstruction on the road resulting from the failure or damage of infrastructure on, under, above or close to the road. + + + + + + + Characterization of an obstruction on the road resulting from the failure or damage of infrastructure on, under, above or close to the road. + + + + + + + + + + Types of infrastructure 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 surface has sunken or collapsed in places due to sewer failure. + + + + + Damage to a bridge that may cause traffic disruption. + + + + + Damage to a crash barrier that may cause traffic disruption. + + + + + Damage to an elevated section of the carriageway over another carriageway that may cause traffic disruption. + + + + + Damage to a gallery that may cause traffic disruption. + + + + + Damage to a gantry above the roadway that may cause traffic disruption. + + + + + Damage to the road surface that may cause traffic disruption. + + + + + Damage to a tunnel that may cause traffic disruption. + + + + + Damage to a viaduct that may cause traffic disruption. + + + + + 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. + + + + + Weak bridge capable of carrying a reduced load, typically with a reduced weight limit restriction imposed. + + + + + Other than as defined in this enumeration. + + + + + + + Types of injury status of people. + + + + + Dead. + + + + + Injured requiring medical treatment. + + + + + Seriously injured requiring urgent hospital treatment. + + + + + Slightly injured requiring medical treatment. + + + + + Uninjured. + + + + + Injury status unknown. + + + + + + + A measure of the quantity of application of a substance to an area defined in kilogrammes per square metre. + + + + + + A measure of precipitation intensity defined in millimetres per hour. + + + + + + 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. + + + + + + + A group of one or more physically separate locations arranged as an ordered set that defines an itinerary or route. The index indicates the order. + + + + + + + Location contained in an itinerary (i.e. an ordered set of locations defining a route or itinerary). + + + + + + + + + + + + Destination of a route or final location in an itinerary. + + + + + + + + + + A measure of speed defined in kilometres per hour. + + + + + + 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 carriageways 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. + + + + + + + A language datatype, identifies a specified language. + + + + + + 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 (true) or not (false). If finished (i.e. end is true) then the overallEndTime in the OverallPeriod class associated with the SituationRecord must be populated. + + + + + + + + A linear section along a single road with optional directionality defined between two points on the same 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. + + + + + No load. + + + + + 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. + + + + + Any goods of a commercial nature. + + + + + Materials classed as being of a hazardous nature. + + + + + Liquid of an unspecified 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. + + + + + Materials classed as being dangerous when exposed to water (e.g. materials which may react exothermically with water). + + + + + 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 or petroleum. + + + + + 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 which may be used by clients for visual display on user interfaces. + + + + + + + + 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. + + + + + On the carriageway or lane which is inbound towards the centre of the town or city. + + + + + In gallery. + + + + + 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 elevated section of road. + + + + + On flyover, i.e. on section of road over another road. + + + + + 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. + + + + + On underground section of road. + + + + + On underpass, i.e. section of road which passes under another road. + + + + + On the carriageway or lane which is outbound from the centre of the town or city. + + + + + Over the crest of a hill. + + + + + On the main carriageway within a junction between exit slip road and entry slip road. + + + + + + + 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. + + + + + + + Details of the maintenance vehicles involved in the roadworks activity. + + + + + 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. + + + + + + + + Roadworks involving the maintenance or installation of infrastructure. + + + + + + + The type of road maintenance or installation work at the specified location. + + + + + + + + + + A cause of this situation record which is managed by the publication creator, i.e. one which is represented by another situation record produced by the same publication creator. + + + + + + + A reference to another situation record produced by the same publication creator which defines a cause of the event defined here. + + + + + + + + + + Information relating to the management of the situation record. + + + + + + + + + + Types of matrix sign faults. + + + + + Comunications failure affecting matrix sign. + + + + + Incorrect aspect (face) is being displayed. + + + + + Not currently in service (e.g. intentionally disconnected or switched off during roadworks). + + + + + 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 individual vehicle measurements. + + + + + 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 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. + + + + + Measured or derived visibility information. + + + + + Measured or derived wind information. + + + + + + + Contains optional characteristics for the specific measured value (indexed to correspond with the defined characteristics of the measurement at the referenced measurement site) which override the static characteristics defined in the MeasurementSiteTable. + + + + + 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. + + + + + The version of the measurement site record, managed by systems external to DATEX II. + + + + + The date/time that this version of the measurement site record was defined. This is managed by systems external to DATEX II. + + + + + 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. + + + + + Composition to the indexed measurement specific characteristics associated with the measurement site. The index uniquely associates the measurement characteristics with the corresponding indexed measurement values for the measurement site. + + + + + + + + + + + + + + + + + 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 identification 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 value 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 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. 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. + + + + + + + + + A measure of distance defined in metres in a floating point format. + + + + + + A measure of distance defined in metres in a non negative integer format. + + + + + + An indication of whether the associated instance of a SituationRecord is mobile (e.g. a march or parade moving along a road) or stationary. + + + + + An indication of whether the associated instance of a SituationRecord is mobile (e.g. a march or parade moving along a road) or stationary. + + + + + + + + Types of mobility relating to a situation element defined by a SituationReord. + + + + + The described element of a situation is moving. + + + + + The described element of a situation is stationary. + + + + + The mobility of the described element of a situation 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). + + + + + + + + + + + + + + Network management action which is applicable to the road network and its users. + + + + + + + Defines whether the network management instruction or the control resulting from a network management action is advisory or mandatory. + + + + + The ultimate traffic direction to which the network management is applicable. + + + + + The type of traffic to which the network management is applicable. + + + + + Places, in generic terms, at which the network management applies. + + + + + Defines whether the network management is initiated by an automatic system. + + + + + The characteristics of those vehicles for which the network management is applicable. + + + + + + + + + + A cause of this situation record which is not managed by the publication creator, i.e. one which is not represented by another situation record produced by the same publication creator. + + + + + + + Description of a cause which is not managed by the publication creator (e.g. an off network cause). + + + + + Indicates an external influence that may be the causation of components of a situation. + + + + + + + + + + An integer number whose value space is the set {0, 1, 2, ..., 2147483645, 2147483646, 2147483647}. + + + + + + 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 diesel on the road. + + + + + 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 petrol on road. + + + + + The road surface is damaged, severely rutted or potholed (i.e. it is in a poor state of repair). + + + + + The road surface is slippery due to an unspecified cause. + + + + + Other than as defined in this enumeration. + + + + + + + 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. + + + + + The mobility of the obstruction. + + + + + + + + + + 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. + + + + + Scattered fragments of wreckage or other material on the road. + + + + + 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. + + + + + Unspecified hazard(s) on the road 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. + + + + + Industrial accident near the roadway 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 hazard 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. + + + + + "Subscription Management Mechanism" - a specialized operating mode to handle subscriptions. + + + + + "Publisher Push on Occurrence" operating mode. + + + + + "Publisher Push Periodic" operating mode. + + + + + "Client Pull" operating mode. + + + + + + + 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. + + + + + + + + + + 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. + + + + + A request, either internal or external, has been received to implement an action. It has neither been approved nor has any activity yet been undertaken to implement the action. + + + + + The action has been approved by the recipient of the request but activity to implement the action has not yet commenced. + + + + + The action is in the process of being implemented. + + + + + The action is fully implemented. + + + + + The action has been rejected by the recipient of the request and hence is not implemented. + + + + + A request, either internal or external, has been received to terminate the action, but activity to terminate the action has not yet commenced. + + + + + The action is in the process of being terminated either because the action has reached the end of its validity period or because new circumstances have arisen and its termination has been requested, e.g. because of a traffic jam on the alternative route. + + + + + + + A continuous or discontinuous 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 single time period, a recurring time period or a set of different recurring time periods during which validity is true. + + + + + A single time period, a recurring time period or a set of different recurring time periods during which validity is false. + + + + + + + + Levels of severity of a situation as whole assessed by the impact that the situation 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 medium level. + + + + + Perceived by supplier as being of a low level. + + + + + Perceived by supplier as being of the lowest discernible level. + + + + + Perceived by supplier as having a severity rating of none. + + + + + Perceived by supplier as being of an unknown level. + + + + + + + Passenger car units per hour. + + + + + + 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 description of the information which is to be found in the publications originating from the particular feed (URL). + + + + + 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. + + + + + + + + The default language used throughout the payload publications, specified by an ISO 639-2 3-alpha code. + + + + + + A measure of percentage. + + + + + + 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. + + + + + A recurring period of a day. + + + + + A recurring period defined in terms of days of the week, weeks of the month and months of the year. + + + + + + + + Categories of person. + + + + + Adult. + + + + + Child (age 4 to 17). + + + + + A member of the emergency services, other than the police. + + + + + A member of the fire service. + + + + + Infant (age 0 to 3). + + + + + A member of the medical service. + + + + + A member of the general public. + + + + + 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 member of the local traffic warden service. + + + + + A very important person. + + + + + + + List of types of places. + + + + + Around bends in the road. + + + + + At customs posts. + + + + + At high altitudes. + + + + + At toll plazas. + + + + + In galleries. + + + + + In low lying areas. + + + + + In roadworks areas. + + + + + In shaded areas. + + + + + In the city centre. + + + + + In the inner city areas. + + + + + In tunnels. + + + + + On bridges. + + + + + On elevated sections of the road. + + + + + On entering or leaving tunnels. + + + + + On entry into the country. + + + + + On flyover sections of the road, i.e. sections of the road which pass over another road. + + + + + On leaving the country. + + + + + On motorways. + + + + + On non motorways. + + + + + On roundabouts. + + + + + On slip roads. + + + + + On underground sections of the road. + + + + + On underpasses, i.e. sections of the road which pass under another road. + + + + + Over the crest of hills. + + + + + 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). + + + + + Polycyclic aromatic hydrocarbons. + + + + + 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. + + + + + 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. + + + + + Pollution of an unspecified nature. + + + + + 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. + + + + + + + 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. + + + + + + + Indication of whether precipitation is present or not. True indicates there is no precipitation. + + + + + + + + + + + Types of precipitation. + + + + + Light, fine rain. + + + + + Freezing 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 assigned to the 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 the set of predefined locations. + + + + + The version of the predefined location set. + + + + + + + + + + A publication containing one or more sets of predefined locations. + + + + + + + + + + + + + + Levels of confidence that the sender has in the information, ordered {certain, probable, risk of}. + + + + + The source is completely 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. + + + + + + + Organised public event which could disrupt traffic. + + + + + + + Type of public event which could disrupt traffic. + + + + + + + + + + Type of public event (Datex2 PublicEventTypeEnum and PublicEventType2Enum combined) + + + + + Unknown + + + + + Agricultural show or event which could disrupt traffic. + + + + + Air show or other aeronautical event which could disrupt traffic. + + + + + Art event that could disrupt traffic. + + + + + Athletics event that could disrupt traffic. + + + + + Beer festival 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. + + + + + Boat show which 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. + + + + + Commercial event which could disrupt traffic. + + + + + Concert event that could disrupt traffic. + + + + + Cricket match that could disrupt traffic. + + + + + Cultural event which 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 festival that could disrupt traffic. + + + + + Film or TV making event which could disrupt traffic. + + + + + Fireworks display that could disrupt traffic. + + + + + Flower event that could disrupt traffic. + + + + + Food festival that could disrupt traffic. + + + + + Football match that could disrupt traffic. + + + + + Periodic (e.g. annual), often traditional, gathering for entertainment, which could disrupt traffic. + + + + + Gardening and/or flower show or event 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 show which could disrupt traffic. + + + + + Motor sport race meeting that could disrupt traffic. + + + + + Open air concert that could disrupt traffic. + + + + + Formal display or organised procession which could disrupt traffic. + + + + + An 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. + + + + + Sound and light show 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. + + + + + Street festival that could disrupt traffic. + + + + + Tennis tournament that could disrupt traffic. + + + + + Theatrical event that could disrupt traffic. + + + + + Sporting event or series of events of unspecified type lasting more than one day which could disrupt traffic. + + + + + A periodic (e.g. annual), often traditional, gathering for trade promotion, which could disrupt traffic. + + + + + Water sports meeting that could disrupt traffic. + + + + + Wine festival that could disrupt traffic. + + + + + Winter sports meeting or event (e.g. skiing, ski jumping, skating) that could disrupt traffic. + + + + + Other than as defined in this enumeration. + + + + + + + A reference to an identifiable object instance (e.g. a GUID reference). + + + + + + Directions of traffic flow relative to sequential numbering scheme of reference points. 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. + + + + + + + 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 assessment 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 flow is normal at the specified location at this date/time. + + + + + Traffic is lighter than normally expected at the specified location at this date/time. + + + + + Traffic is very much 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. + + + + + A request for the supplier's catalogue. + + + + + A request for the client's filter as currently stored by the supplier. + + + + + A request for current data. + + + + + A request for historical data, i.e. data which was valid within an historical time window. + + + + + A request for a client's subscription as currently held by a supplier. + + + + + + + Rerouting management action that is issued by the network/road operator. + + + + + + + Type of rerouting management action instigated by operator. + + + + + A description of the rerouting itinerary. + + + + + Indication of whether the rerouting is signed. + + + + + The specified entry on to another road at which the alternative route commences. + + + + + The specified exit from the normal route/road at which the alternative route commences. + + + + + The intersecting road or the junction at which the alternative route commences. + + + + + The definition of the alternative route (rerouting) specified as an ordered set of locations (itinerary) which may be specific to one or more defined destinations. + + + + + + + + + + Management actions relating to rerouting. + + + + + Do not follow diversion signs. + + + + + Rerouted traffic is not to use the specified entry onto the identified road to commence the alternative route. + + + + + Rerouted traffic is not to use the specified exit from the identified road to commence the alternative route. + + + + + Rerouted traffic is not to use the specified intersection or junction. + + + + + Rerouted traffic is to follow the diversion signs. + + + + + Rerouted traffic is to follow local diversion. + + + + + Rerouted traffic is to follow the special diversion markers. + + + + + 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. + + + + + An acknowledgement that the supplier has received and complied with the client's request. + + + + + A notification that the supplier has denied the client's request for a catalogue. + + + + + A notification that the supplier has denied the client's request for a filter. + + + + + A notification that the supplier has denied the client's request for a data. + + + + + A notification that the supplier has denied the client's request for a subscription. + + + + + + + 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 an unspecified nature. + + + + + Controlled avalanche work. + + + + + Installation of new equipments or systems on or along-side the roadway. + + + + + Grass cutting work. + + + + + Maintenance of road, associated infrastructure or equipments. + + + + + Works which are overhead of the carriageway. + + + + + 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. + + + + + Spreading of salt and / or grit on the road surface to prevent or melt snow or ice. + + + + + Snowploughs or other similar mechanical devices in use to clear snow from the road. + + + + + Tree and vegetation cutting work adjacent to the roadway. + + + + + Other than as defined in this enumeration. + + + + + + + Details of disruption to normal road operator services + + + + + + + The type of road operator service which is disrupted. + + + + + + + + + + Types of disruption to road operator services relevant to road users. + + + + + Emergency telephone number for use by public to report incidents is out of service. + + + + + Road information service telephone number is out of service. + + + + + No traffic officer patrol service is operating. + + + + + + + Road, carriageway or lane management action that is instigated by the network/road operator. + + + + + + + Type of road, carriageway or lane management action instigated by operator. + + + + + The minimum number of persons required in a vehicle in order for it to be allowed to transit the specified road section. + + + + + The carriageway which is the subject of the management action. + + + + + The lane which is the subject of the management action. + + + + + + + + + + Management actions relating to road, carriageway or lane usage. + + + + + Dedicated car pool lane(s) are in operation for vehicles carrying at least the specified number of occupants. + + + + + Carriageway closures are in operation at the specified location. + + + + + Clear a lane for emergency vehicles. + + + + + Clear a lane for snow ploughs and gritting vehicles. + + + + + 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. + + + + + Do not use the specified lane(s) or carriageway(s). + + + + + The hard shoulder is open as an operational lane. + + + + + Road closures occur intermittently on the specified road in the specified direction for short durations. + + + + + Keep to the left. + + + + + Keep to the right. + + + + + Lane closures are in operation at the specified location for vehicles with the specified characteristics or all, if none defined, in the specified direction. + + + + + Lane deviations are in operation at the specified location. + + + + + Normal lane widths are temporarily reduced. + + + + + A new layout of lanes/carriageway has been implemented associated with roadworks. + + + + + 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. + + + + + The road has been cleared of earlier reported problems. + + + + + The road is closed to vehicles with the specified characteristics or all, if none defined, in the specified direction. + + + + + Traffic officers or police are driving slowly in front of a queue of traffic to create a gap in the traffic to allow for clearance activities to take place in safety on the road ahead. + + + + + 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. + + + + + Dedicated tidal flow lane(s) are in operation in the specified direction. + + + + + Traffic is being directed back down the opposite carriageway, possibly requiring the temporary removal of the central crash barrier. + + + + + The specified lane(s) or carriageway(s) may be used. The normal lane(s) or carriageway(s) restrictions are not currently in force. + + + + + Use the specified lane(s) or carriageway(s). + + + + + Vehicles are being stored on the roadway and/or at a rest area or service area at the specified location. + + + + + Other than as defined in this enumeration. + + + + + + + Details of road side assistance required or being given. + + + + + + + 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. + + + + + + + One of a sequence of roadside reference points along a road, normally spaced at regular intervals along each carriageway with a sequence of identification from a known starting point. + + + + + Roadside reference point identifier, unique on the specified road. + + + + + Identification of the road administration area which contains the reference point. + + + + + Name of a road. + + + + + 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 roadside reference point. + + + + + The distance of the roadside reference point from the starting point of the sequence on the road. + + + + + + + + A linear section along a single road defined between two points on the same road identified by roadside reference points. + + + + + + + + + + The point (called Primary point) which is at the downstream end of a linear road section. The point is identified by a roadside reference point. + + + + + + + + + The point (called Secondary point) which is at the upstream end of a linear road section. The point is identified by a roadside reference point. + + + + + + + + + Details of disruption to normal roadside services (e.g. specific services at a service areas). + + + + + + + The type of roadside service which is disrupted. + + + + + + + + + + Types of disruption to roadside 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. + + + + + + + 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. + + + + + + + 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 under traffic or not under traffic. 'True' indicates the road is under traffic. + + + + + 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. + + + + + + + Seconds. + + + + + + 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. + + + + + Composition to the indexed measured value associated with the measurement site. The index uniquely associates the measurement value with the corresponding indexed measurement characteristics defined for the measurement site. + + + + + + + + + + + + + + + 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. + + + + + Each situation may iterate through a series of versions during its life time. The situation version uniquely identifies the version of the situation. It is generated and used by systems external to DATEX II. + + + + + The date/time that this current version of the Situation was written into the database of the supplier which is involved in the data exchange. + + + + + + + + + + + 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 II. + + + + + 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. + + + + + The extent to which the related information may be circulated, according to the recipient type. Recipients must comply with this confidentiality statement. This overrides any confidentiality defined for the situation as a whole in the header information. + + + + + An assessment of the degree of likelihood that the reported event will occur. + + + + + + + + + A comment which may be freely distributed to the general public + + + + + A comment which should not be distributed to the general public. + + + + + + + + + + + + Details of the source from which the information was obtained. + + + + + ISO 3166-1 two character country code of the source of the information. + + + + + Identifier 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. + + + + + + + Speed management action that is instigated by the network/road operator. + + + + + + + Type of speed management action instigated by operator. + + + + + Temporary limit defining the maximum advisory or mandatory speed of vehicles. + + + + + + + + + + Management actions relating to speed. + + + + + Automatic speed control measures are in place at the specified location, whereby speed limits are set by an automatic system which is triggered by traffic sensing equipment. + + + + + Do not slow down unnecessarily. + + + + + Observe speed limit. + + + + + Police speed checks are in operation. + + + + + Reduce your speed. + + + + + Other than as defined in this enumeration. + + + + + + + Details of percentage (from an observation set) of vehicles whose speeds fall below a stated value. + + + + + The percentage of vehicles from the observation set whose speeds fall below the stated speed (speedPercentile). + + + + + The speed below which the associated percentage of vehicles in the measurement set are travelling at. + + + + + + + + A character string whose value space is the set of finite-length sequences of characters. Every character has a corresponding Universal Character Set code point (as defined in ISO/IEC 10646), which is an integer. + + + + + + + + The subjects with which the roadworks are associated. + + + + + The subject type 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. + + + + + Crash barrier. + + + + + Gallery. + + + + + Gantry over or above the roadway. + + + + + Gas mains. + + + + + Motorway or major road interchange. + + + + + Motorway or major road junction. + + + + + Level-crossing or associated equipment. + + + + + Road lighting system. + + + + + Equipment used for determining traffic measurements. + + + + + Installations along the roadway designed to reduce road noise in the surrounding environment. + + + + + Road. + + + + + Roadside drains. + + + + + Roadside embankment. + + + + + Roadside equipment. + + + + + Road signs. + + + + + Roundabout. + + + + + Toll gate. + + + + + 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. + + + + + The client's subscription as registered with a supplier is currently active. + + + + + The client's subscription as registered with a supplier is currently suspended. + + + + + + + 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. + + + + + Indicates that the location is given with a precision which is better than the stated value in metres. + + + + + The sequential number of an exit/entrance ramp from a given location in a given direction (normally used to indicate a specific exit/entrance in a complex junction/intersection). + + + + + + + + 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. + + + + + + + + A measure of temperature defined in degrees Celsius. + + + + + + Measurements of atmospheric temperature. + + + + + + + + + + + + + An instant of time that recurs every day. The value space of time is the space of time of day values as defined in § 5.3 of [ISO 8601]. Specifically, it is a set of zero-duration daily time instances. + + + + + + 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. + + + + + + + + A measure of weight defined in metric tonnes. + + + + + + A descriptor for describing an area location. + + + + + + + The nature of the descriptor used to define the location 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 discrimination. + + + + + The type of TPEG location. + + + + + + + + + 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. + + + + + + + + A point on the road network which is framed between two other points on the same road. + + + + + + + The type of TPEG location. + + + + + A single non junction point on the road network which is framed between two other specified points on the road network. + + + + + The location at the down stream end of the section of road which frames the TPEGFramedPoint. + + + + + The location at the up stream end of the section of road which frames the TPEGFramedPoint. + + + + + + + + + + A geometric area defined by a centre point and a radius. + + + + + + + The radius of the geometric area identified. + + + + + Centre point of a circular geometric area. + + + + + Name of area. + + + + + + + + + + Height information which provides additional discrimination 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 location under consideration (derived from the TPEG Loc table 03). + + + + + + + + + + A point on the road network which is a road junction point. + + + + + + + + A name which identifies a junction point on the road network + + + + + A descriptor for describing a junction by identifying the intersecting roads at a road junction. + + + + + A descriptive name which helps to identify the junction point. + + + + + + + + + + A descriptor for describing a point at a junction on a road network. + + + + + + + The nature of the descriptor used to define the location under consideration (derived from the TPEG Loc table 03). + + + + + + + + + + A linear section along a single road defined between two points on the same road by a TPEG-Loc structure. + + + + + The direction of traffic flow. + + + + + The type of TPEG location. + + + + + The location at the down stream end of the linear section of road. + + + + + The location at the up stream end of the linear section of road. + + + + + + + + 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 an area. + + + + + Name of a county (administrative sub-division). + + + + + Name of a lake. + + + + + Name of a 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 administrative area. + + + + + Reference name by which an administrative area is known. + + + + + Name of an airport. + + + + + Name of an area. + + + + + 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 county (administrative sub-division). + + + + + 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 nation (e.g. Wales) which is a sub-division of a ISO recognised country. + + + + + 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 a general point of interest. + + + + + Name of a railway station. + + + + + Name of a geographic region. + + + + + 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. + + + + + + + Name of area. + + + + + + + + + + A point on the road network which is not a road junction point. + + + + + + + + A descriptive name which helps to identify the non junction point. At least one descriptor must identify the road on which the point is located, i.e. must be of type 'linkName' or 'localLinkName'. + + + + + + + + + + General descriptor for describing a point. + + + + + + + The nature of the descriptor used to define the location under consideration (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. + + + + + + + + A point on the road network which is not bounded by any other points on the road network. + + + + + + + The type of TPEG location. + + + + + A single point defined by a coordinate set and TPEG decriptors. + + + + + + + + + + Averaged measurements of traffic concentration. + + + + + + + An averaged measurement of the concentration of vehicles at the specified measurement site. + + + + + An averaged measurement of the percentage of time that a section of road at the specified measurement site is occuppied by vehicles. + + + + + + + + + + Types of constriction 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. + + + + + 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. + + + + + + + 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 site. + + + + + An averaged measurement of flow rate defined in terms of the number of passenger car units passing the specified measurement site. + + + + + An averaged measurement of the percentage of long vehicles contained in the traffic flow at the specified measurement site. + + + + + An averaged measurement of flow rate defined in terms of the number of vehicles passing the specified measurement site. + + + + + + + + + + A collection of terms for describing the characteristics of traffic flow. + + + + + Traffic flow is of an irregular nature, subject to sudden changes in rates. + + + + + Traffic flow is smooth. + + + + + Traffic flow is of a stop and go nature with queues forming and ending continuously on the specified section of road. + + + + + Traffic is blocked at the specified location and in the specified direction due to an unplanned event. + + + + + + + Averaged measurements of traffic headway, i.e. the distance or time interval 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 site. + + + + + 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 site. + + + + + + + + + + Averaged measurements of traffic speed. + + + + + + + An averaged measurement of the speed of vehicles at the specified measurement site. + + + + + + + + + + + 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 characterization 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. + + + + + + + Types of traffic, mostly classified by its destination type. + + + + + Traffic destined for local access only. + + + + + Traffic destined for the airport. + + + + + Traffic destined for airport arrivals. + + + + + Traffic destined for airport departures. + + + + + Traffic destined for the ferry service. + + + + + Traffic destined for the rail service. + + + + + Traffic heading towards holiday destinations. + + + + + Traffic heading towards local destinations. + + + + + Traffic heading towards destinations which are a long distance away. + + + + + Traffic heading towards local regional destinations. + + + + + Local residents only traffic. + + + + + Traffic which is not for local access, i.e. traffic not destined for local town, city or built up area but for transit though the area. + + + + + Traffic heading towards local visitor attraction. + + + + + + + Measured or derived values relating to traffic or individual vehicle movements on a specific section or at a specific point on the road network. + + + + + + + Used to define the vehicle characteristics to which the TrafficValue is applicable primarily in Elaborated Data Publications, but may also be used in Measured Data Publications to override vehicle characteristics defined for the measurement site. + + + + + + + + + + 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 which shall comprise at most one instance of each of the following: OperatorAction, TrafficElement, ElaboratedData and CCTVImages. + + + + + 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 flotsam. + + + + + The departure of the specified service is on schedule. + + + + + The ferry service has been replaced by an ice road. + + + + + A shuttle service is operating at no charge between specified locations until the specified time. + + + + + The information service relating to the specified transport system is not currently available. + + + + + The specified service is subject to irregular delays. + + + + + The load capacity for the specified service has been changed. + + + + + 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 until the specified time. + + + + + 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. + + + + + Vehicle type. + + + + + + + + + + The types of updates of situations that may be requested by a client. + + + + + The client has currently requested that all situation elements are sent when one or more component elements are updated. + + + + + The client has currently requested that only the individual elements of a situation that have changed are sent when updated. + + + + + The client has requested that all situations and their elements which are valid at the time of request be sent together, i.e. a snapshot in time of all valid situations. + + + + + + + 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. + + + + + + + A Uniform Resource Locator (URL) address comprising a compact string of characters for a resource available on the Internet. + + + + + + Details of a Uniform Resource Locator (URL) address pointing to a resource available on the Internet from where further relevant information may be obtained. + + + + + A Uniform Resource Locator (URL) address pointing to a resource available on the Internet from where further relevant information may be obtained. + + + + + Description of the relevant information available on the Internet from the URL link. + + + + + Details of the type of relevant information available on the Internet from the URL link. + + + + + + + + Types of URL links. + + + + + URL link to a pdf document. + + + + + URL link to an html page. + + + + + URL link to an image. + + + + + URL link to an RSS feed. + + + + + URL link to a video stream. + + + + + URL link to a voice stream. + + + + + Other than as defined in this enumeration. + + + + + + + Specification of validity, either explicitly or by a validity time period specification which may be discontinuous. + + + + + Specification of validity, either explicitly overriding the validity time specification or confirming it. + + + + + The activity or action described by the SituationRecord is still in progress, overrunning its planned duration as indicated in a previous version of this record. + + + + + A specification of periods of validity defined by overall bounding start and end times and the possible intersection of valid periods with exception periods (exception periods overriding valid periods). + + + + + + + + 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. + + + + + + + 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. + + + + + + + + + + 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 which is updated by the ISO 3166 Maintenance Agency. + + + + + A vehicle identification number (VIN) comprising 17 characters that is based on either ISO 3779 or ISO 3780 and uniquely identifies the individual vehicle. This is normally securely attached to the vehicle chassis. + + + + + Indicates the stated manufacturer of the vehicle i.e. Ford. + + + + + Indicates the model (or range name) of the vehicle i.e. Ford Mondeo. + + + + + An identifier or code displayed on a vehicle registration plate attached to the vehicle used for official identification purposes. The registration identifier is numeric or alphanumeric and is unique within the issuing authority's region. + + + + + Vehicle status. + + + + + + The spacing between axles on the vehicles. + + + + + The weight details relating to a specific axle on the vehicle. + + + + + Details of hazardous goods carried by the vehicle. + + + + + + + + The characteristics 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. + + + + + Vehicle type. + + + + + 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 site. + + + + + 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 distance 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 site. + + + + + The measured distance between the front (respectively back) of this vehicle and the front (respectively back) of the preceding vehicle at the specified measurement site. + + + + + + + + An obstruction on the road caused by one or more vehicles. + + + + + + + Characterization of an obstruction on the road caused by one or more vehicles. + + + + + The obstructing vehicle. + + + + + + + + + + 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 experiencing difficulties (e.g. manoeuvring or propulsion difficulties) which may cause traffic disruption. + + + + + A vehicle is travelling the wrong way along a divided highway (i.e. on the wrong side). + + + + + 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 over-height 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. + + + + + + + Measurement of individual vehicle speed. + + + + + The measured speed of the individual vehicle at the specified measurement site. + + + + + + + + Vehicles per hour. + + + + + + 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. + + + + + Bicycle. + + + + + Bus. + + + + + Car. + + + + + Caravan. + + + + + Car or light vehicle. + + + + + Car towing a caravan. + + + + + Car towing a trailer. + + + + + Four wheel drive vehicle. + + + + + High sided vehicle. + + + + + Lorry of any type. + + + + + Moped (a two wheeled motor vehicle characterized by a small engine typically less than 50cc and by normally having pedals). + + + + + Motorcycle. + + + + + Three wheeled vehicle comprising a motorcycle with an attached side car. + + + + + Motor scooter (a two wheeled motor vehicle characterized by a step-through frame and small diameter wheels). + + + + + Vehicle with large tank for carrying bulk liquids. + + + + + Three wheeled vehicle of unspecified type. + + + + + Trailer. + + + + + Tram. + + + + + 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 usage of a vehicle. + + + + + Vehicle used for agricultural purposes. + + + + + Vehicle which is limited to non-private usage or public transport usage. + + + + + 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. road operator or automobile association patrol vehicle. + + + + + 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. + + + + + + + Details of atmospheric visibility. + + + + + The minimum 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. + + + + + Not currently in service (e.g. intentionally disconnected or switched off during roadworks). + + + + + 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. + + + + + + + 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 that is related to the weather 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). + + + + + 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 (with little or no traffic yet) 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. + + + + + The road surface is slippery due to bad weather conditions. + + + + + 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. + + + + + Water is resting on the roadway which provides an increased hazard to vehicles. + + + + + 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. + + + + + 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). + + + + + + + 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. + + + + + + + + + + + + + Winter driving management action that is instigated by the network/road operator. + + + + + + + Type of winter equipment management action instigated by operator. + + + + + + + + + + Instructions relating to the use of winter equipment. + + + + + Do not use stud tyres. + + + + + Use snow chains. + + + + + Use snow chains or snow tyres. + + + + + Use snow tyres. + + + + + The carrying of winter equipment (snow chains and/or snow tyres) is required. + + + + + Other than as defined in this enumeration. + + + + + diff --git a/xsd/gml/basicTypes.xsd b/xsd/gml/basicTypes.xsd index 4ad5c991..463203ca 100644 --- a/xsd/gml/basicTypes.xsd +++ b/xsd/gml/basicTypes.xsd @@ -1,267 +1,267 @@ - - - - basicTypes.xsd - See ISO/DIS 19136 8.2. -W3C XML Schema provides a set of built-in "simple" types which define methods for representing values as literals without internal markup. These are described in W3C XML Schema Part 2:2001. Because GML is an XML encoding in which instances are described using XML Schema, these simple types shall be used as far as possible and practical for the representation of data types. W3C XML Schema also provides methods for defining -- new simple types by restriction and combination of the built-in types, and -- complex types, with simple content, but which also have XML attributes. -In many places where a suitable built-in simple type is not available, simple content types derived using the XML Schema mechanisms are used for the representation of data types in GML. -A set of these simple content types that are required by several GML components are defined in the basicTypes schema, as well as some elements based on them. These are primarily based around components needed to record amounts, counts, flags and terms, together with support for exceptions or null values. - -GML is an OGC Standard. -Copyright (c) 2007,2010 Open Geospatial Consortium, Inc. All Rights Reserved. -To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . - - - - - gml:NilReasonType defines a content model that allows recording of an explanation for a void value or other exception. -gml:NilReasonType is a union of the following enumerated values: -- inapplicable there is no value -- missing the correct value is not readily available to the sender of this data. Furthermore, a correct value may not exist -- template the value will be available later -- unknown the correct value is not known to, and not computable by, the sender of this data. However, a correct value probably exists -- withheld the value is not divulged -- other:text other brief explanation, where text is a string of two or more characters with no included spaces -and -- anyURI which should refer to a resource which describes the reason for the exception -A particular community may choose to assign more detailed semantics to the standard values provided. Alternatively, the URI method enables a specific or more complete explanation for the absence of a value to be provided elsewhere and indicated by-reference in an instance document. -gml:NilReasonType is used as a member of a union in a number of simple content types where it is necessary to permit a value from the NilReasonType union as an alternative to the primary type. - - - - - - - - - - - - - - - - - - - - - - - - gml:SignType is a convenience type with values "+" (plus) and "-" (minus). - - - - - - - - - Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. - - - - - - Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. - - - - - - Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. - - - - - - Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. - - - - - - Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. - - - - - - gml:CodeType is a generalized type to be used for a term, keyword or name. -It adds a XML attribute codeSpace to a term, where the value of the codeSpace attribute (if present) shall indicate a dictionary, thesaurus, classification scheme, authority, or pattern for the term. - - - - - - - - - - gml:CodeWithAuthorityType requires that the codeSpace attribute is provided in an instance. - - - - - - - - - - gml:MeasureType supports recording an amount encoded as a value of XML Schema double, together with a units of measure indicated by an attribute uom, short for "units of measure". The value of the uom attribute identifies a reference system for the amount, usually a ratio or interval scale. - - - - - - - - - - The simple type gml:Uomidentifier defines the syntax and value space of the unit of measure identifier. - - - - - - This type specifies a character string of length at least one, and restricted such that it must not contain any of the following characters: ":" (colon), " " (space), (newline), (carriage return), (tab). This allows values corresponding to familiar abbreviations, such as "kg", "m/s", etc. -It is recommended that the symbol be an identifier for a unit of measure as specified in the "Unified Code of Units of Measure" (UCUM) (http://aurora.regenstrief.org/UCUM). This provides a set of symbols and a grammar for constructing identifiers for units of measure that are unique, and may be easily entered with a keyboard supporting the limited character set known as 7-bit ASCII. ISO 2955 formerly provided a specification with this scope, but was withdrawn in 2001. UCUM largely follows ISO 2955 with modifications to remove ambiguities and other problems. - - - - - - - - This type specifies a URI, restricted such that it must start with one of the following sequences: "#", "./", "../", or a string of characters followed by a ":". These patterns ensure that the most common URI forms are supported, including absolute and relative URIs and URIs that are simple fragment identifiers, but prohibits certain forms of relative URI that could be mistaken for unit of measure symbol . -NOTE It is possible to re-write such a relative URI to conform to the restriction (e.g. "./m/s"). -In an instance document, on elements of type gml:MeasureType the mandatory uom attribute shall carry a value corresponding to either -- a conventional unit of measure symbol, -- a link to a definition of a unit of measure that does not have a conventional symbol, or when it is desired to indicate a precise or variant definition. - - - - - - - - This type is deprecated for tuples with ordinate values that are numbers. -CoordinatesType is a text string, intended to be used to record an array of tuples or coordinates. -While it is not possible to enforce the internal structure of the string through schema validation, some optional attributes have been provided in previous versions of GML to support a description of the internal structure. These attributes are deprecated. The attributes were intended to be used as follows: -Decimal symbol used for a decimal point (default="." a stop or period) -cs symbol used to separate components within a tuple or coordinate string (default="," a comma) -ts symbol used to separate tuples or coordinate strings (default=" " a space) -Since it is based on the XML Schema string type, CoordinatesType may be used in the construction of tables of tuples or arrays of tuples, including ones that contain mixed text and numeric values. - - - - - - - - - - - - A type for a list of values of the respective simple type. - - - - - - A type for a list of values of the respective simple type. - - - - - - A type for a list of values of the respective simple type. - - - - - - A type for a list of values of the respective simple type. - - - - - - A type for a list of values of the respective simple type. - - - - - - A type for a list of values of the respective simple type. - - - - - - A type for a list of values of the respective simple type. - - - - - - A type for a list of values of the respective simple type. - - - - - - A type for a list of values of the respective simple type. - - - - - - A type for a list of values of the respective simple type. - - - - - - gml:CodeListType provides for lists of terms. The values in an instance element shall all be valid according to the rules of the dictionary, classification scheme, or authority identified by the value of its codeSpace attribute. - - - - - - - - - - gml:CodeOrNilReasonListType provides for lists of terms. The values in an instance element shall all be valid according to the rules of the dictionary, classification scheme, or authority identified by the value of its codeSpace attribute. An instance element may also include embedded values from NilReasonType. It is intended to be used in situations where a term or classification is expected, but the value may be absent for some reason. - - - - - - - - - - gml:MeasureListType provides for a list of quantities. - - - - - - - - - - gml:MeasureOrNilReasonListType provides for a list of quantities. An instance element may also include embedded values from NilReasonType. It is intended to be used in situations where a value is expected, but the value may be absent for some reason. - - - - - - - - + + + + basicTypes.xsd + See ISO/DIS 19136 8.2. +W3C XML Schema provides a set of built-in "simple" types which define methods for representing values as literals without internal markup. These are described in W3C XML Schema Part 2:2001. Because GML is an XML encoding in which instances are described using XML Schema, these simple types shall be used as far as possible and practical for the representation of data types. W3C XML Schema also provides methods for defining +- new simple types by restriction and combination of the built-in types, and +- complex types, with simple content, but which also have XML attributes. +In many places where a suitable built-in simple type is not available, simple content types derived using the XML Schema mechanisms are used for the representation of data types in GML. +A set of these simple content types that are required by several GML components are defined in the basicTypes schema, as well as some elements based on them. These are primarily based around components needed to record amounts, counts, flags and terms, together with support for exceptions or null values. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium, Inc. All Rights Reserved. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + gml:NilReasonType defines a content model that allows recording of an explanation for a void value or other exception. +gml:NilReasonType is a union of the following enumerated values: +- inapplicable there is no value +- missing the correct value is not readily available to the sender of this data. Furthermore, a correct value may not exist +- template the value will be available later +- unknown the correct value is not known to, and not computable by, the sender of this data. However, a correct value probably exists +- withheld the value is not divulged +- other:text other brief explanation, where text is a string of two or more characters with no included spaces +and +- anyURI which should refer to a resource which describes the reason for the exception +A particular community may choose to assign more detailed semantics to the standard values provided. Alternatively, the URI method enables a specific or more complete explanation for the absence of a value to be provided elsewhere and indicated by-reference in an instance document. +gml:NilReasonType is used as a member of a union in a number of simple content types where it is necessary to permit a value from the NilReasonType union as an alternative to the primary type. + + + + + + + + + + + + + + + + + + + + + + + + gml:SignType is a convenience type with values "+" (plus) and "-" (minus). + + + + + + + + + Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. + + + + + + Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. + + + + + + Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. + + + + + + Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. + + + + + + Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. + + + + + + gml:CodeType is a generalized type to be used for a term, keyword or name. +It adds a XML attribute codeSpace to a term, where the value of the codeSpace attribute (if present) shall indicate a dictionary, thesaurus, classification scheme, authority, or pattern for the term. + + + + + + + + + + gml:CodeWithAuthorityType requires that the codeSpace attribute is provided in an instance. + + + + + + + + + + gml:MeasureType supports recording an amount encoded as a value of XML Schema double, together with a units of measure indicated by an attribute uom, short for "units of measure". The value of the uom attribute identifies a reference system for the amount, usually a ratio or interval scale. + + + + + + + + + + The simple type gml:Uomidentifier defines the syntax and value space of the unit of measure identifier. + + + + + + This type specifies a character string of length at least one, and restricted such that it must not contain any of the following characters: ":" (colon), " " (space), (newline), (carriage return), (tab). This allows values corresponding to familiar abbreviations, such as "kg", "m/s", etc. +It is recommended that the symbol be an identifier for a unit of measure as specified in the "Unified Code of Units of Measure" (UCUM) (http://aurora.regenstrief.org/UCUM). This provides a set of symbols and a grammar for constructing identifiers for units of measure that are unique, and may be easily entered with a keyboard supporting the limited character set known as 7-bit ASCII. ISO 2955 formerly provided a specification with this scope, but was withdrawn in 2001. UCUM largely follows ISO 2955 with modifications to remove ambiguities and other problems. + + + + + + + + This type specifies a URI, restricted such that it must start with one of the following sequences: "#", "./", "../", or a string of characters followed by a ":". These patterns ensure that the most common URI forms are supported, including absolute and relative URIs and URIs that are simple fragment identifiers, but prohibits certain forms of relative URI that could be mistaken for unit of measure symbol . +NOTE It is possible to re-write such a relative URI to conform to the restriction (e.g. "./m/s"). +In an instance document, on elements of type gml:MeasureType the mandatory uom attribute shall carry a value corresponding to either +- a conventional unit of measure symbol, +- a link to a definition of a unit of measure that does not have a conventional symbol, or when it is desired to indicate a precise or variant definition. + + + + + + + + This type is deprecated for tuples with ordinate values that are numbers. +CoordinatesType is a text string, intended to be used to record an array of tuples or coordinates. +While it is not possible to enforce the internal structure of the string through schema validation, some optional attributes have been provided in previous versions of GML to support a description of the internal structure. These attributes are deprecated. The attributes were intended to be used as follows: +Decimal symbol used for a decimal point (default="." a stop or period) +cs symbol used to separate components within a tuple or coordinate string (default="," a comma) +ts symbol used to separate tuples or coordinate strings (default=" " a space) +Since it is based on the XML Schema string type, CoordinatesType may be used in the construction of tables of tuples or arrays of tuples, including ones that contain mixed text and numeric values. + + + + + + + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + gml:CodeListType provides for lists of terms. The values in an instance element shall all be valid according to the rules of the dictionary, classification scheme, or authority identified by the value of its codeSpace attribute. + + + + + + + + + + gml:CodeOrNilReasonListType provides for lists of terms. The values in an instance element shall all be valid according to the rules of the dictionary, classification scheme, or authority identified by the value of its codeSpace attribute. An instance element may also include embedded values from NilReasonType. It is intended to be used in situations where a term or classification is expected, but the value may be absent for some reason. + + + + + + + + + + gml:MeasureListType provides for a list of quantities. + + + + + + + + + + gml:MeasureOrNilReasonListType provides for a list of quantities. An instance element may also include embedded values from NilReasonType. It is intended to be used in situations where a value is expected, but the value may be absent for some reason. + + + + + + + + diff --git a/xsd/gml/geometryBasic0d1d-extract.xsd b/xsd/gml/geometryBasic0d1d-extract.xsd index d66cf9d5..fec149d6 100644 --- a/xsd/gml/geometryBasic0d1d-extract.xsd +++ b/xsd/gml/geometryBasic0d1d-extract.xsd @@ -1,271 +1,271 @@ - - - - - geometryBasic0d1d.xsd - See ISO/DIS 19136 Clause 10. -Any geometry element that inherits the semantics of AbstractGeometryType may be viewed as a set of direct positions. -All of the classes derived from AbstractGeometryType inherit an optional association to a coordinate reference system. All direct positions shall directly or indirectly be associated with a coordinate reference system. When geometry elements are aggregated in another geometry element (such as a MultiGeometry or GeometricComplex), which already has a coordinate reference system specified, then these elements are assumed to be in that same coordinate reference system unless otherwise specified. -The geometry model distinguishes geometric primitives, aggregates and complexes. -Geometric primitives, i.e. instances of a subtype of AbstractGeometricPrimitiveType, will be open, that is, they will not contain their boundary points; curves will not contain their end points, surfaces will not contain their boundary curves, and solids will not contain their bounding surfaces. - -GML is an OGC Standard. -Copyright (c) 2007,2010 Open Geospatial Consortium, Inc. All Rights Reserved. -To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . - - - - - - All geometry elements are derived directly or indirectly from this abstract supertype. A geometry element may have an identifying attribute (gml:id), one or more names (elements identifier and name) and a description (elements description and descriptionReference) . It may be associated with a spatial reference system (attribute group gml:SRSReferenceGroup). -The following rules shall be adhered to: -- Every geometry type shall derive from this abstract type. -- Every geometry element (i.e. an element of a geometry type) shall be directly or indirectly in the substitution group of AbstractGeometry. - - - - - - - - - - The attribute group SRSReferenceGroup is an optional reference to the CRS used by this geometry, with optional additional information to simplify the processing of the coordinates when a more complete definition of the CRS is not needed. -In general the attribute srsName points to a CRS instance of gml:AbstractCoordinateReferenceSystem. For well-known references it is not required that the CRS description exists at the location the URI points to. -If no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of. - - - - - - - - The attributes uomLabels and axisLabels, defined in the SRSInformationGroup attribute group, are optional additional and redundant information for a CRS to simplify the processing of the coordinate values when a more complete definition of the CRS is not needed. This information shall be the same as included in the complete definition of the CRS, referenced by the srsName attribute. When the srsName attribute is included, either both or neither of the axisLabels and uomLabels attributes shall be included. When the srsName attribute is omitted, both of these attributes shall be omitted. -The attribute axisLabels is an ordered list of labels for all the axes of this CRS. The gml:axisAbbrev value should be used for these axis labels, after spaces and forbidden characters are removed. When the srsName attribute is included, this attribute is optional. When the srsName attribute is omitted, this attribute shall also be omitted. -The attribute uomLabels is an ordered list of unit of measure (uom) labels for all the axes of this CRS. The value of the string in the gml:catalogSymbol should be used for this uom labels, after spaces and forbidden characters are removed. When the axisLabels attribute is included, this attribute shall also be included. When the axisLabels attribute is omitted, this attribute shall also be omitted. - - - - - The AbstractGeometry element is the abstract head of the substitution group for all geometry elements of GML. This includes pre-defined and user-defined geometry elements. Any geometry element shall be a direct or indirect extension/restriction of AbstractGeometryType and shall be directly or indirectly in the substitution group of AbstractGeometry. - - - - - A geometric property may either be any geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same or another document). Note that either the reference or the contained element shall be given, but not both or none. -If a feature has a property that takes a geometry element as its value, this is called a geometry property. A generic type for such a geometry property is GeometryPropertyType. - - - - - - - - - - If a feature has a property which takes an array of geometry elements as its value, this is called a geometry array property. A generic type for such a geometry property is GeometryArrayPropertyType. -The elements are always contained inline in the array property, referencing geometry elements or arrays of geometry elements via XLinks is not supported. - - - - - - - - - Direct position instances hold the coordinates for a position within some coordinate reference system (CRS). Since direct positions, as data types, will often be included in larger objects (such as geometry elements) that have references to CRS, the srsName attribute will in general be missing, if this particular direct position is included in a larger element with such a reference to a CRS. In this case, the CRS is implicitly assumed to take on the value of the containing object's CRS. -if no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of, typically a geometric object like a point, curve, etc. - - - - - - - - - - - posList instances (and other instances with the content model specified by DirectPositionListType) hold the coordinates for a sequence of direct positions within the same coordinate reference system (CRS). -if no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of, typically a geometric object like a point, curve, etc. -The optional attribute count specifies the number of direct positions in the list. If the attribute count is present then the attribute srsDimension shall be present, too. -The number of entries in the list is equal to the product of the dimensionality of the coordinate reference system (i.e. it is a derived value of the coordinate reference system definition) and the number of direct positions. - - - - - - - - - - - - GML supports two different ways to specify a geometric position: either by a direct position (a data type) or a point (a geometric object). -pos elements are positions that are "owned" by the geometric primitive encapsulating this geometric position. -pointProperty elements contain a point that may be referenced from other geometry elements or reference another point defined elsewhere (reuse of existing points). - - - - - - - - - GML supports two different ways to specify a list of geometric positions: either by a sequence of geometric positions (by reusing the group definition) or a sequence of direct positions (element posList). -The posList element allows for a compact way to specify the coordinates of the positions, if all positions are represented in the same coordinate reference system. - - - - - - - - - For some applications the components of the position may be adjusted to yield a unit vector. - - - - - - - - - - - - - - - deprecated - - - - - - - - Envelope defines an extent using a pair of positions defining opposite corners in arbitrary dimensions. The first direct position is the "lower corner" (a coordinate position consisting of all the minimal ordinates for each dimension for all points within the envelope), the second one the "upper corner" (a coordinate position consisting of all the maximal ordinates for each dimension for all points within the envelope). -The use of the properties "coordinates" and "pos" has been deprecated. The explicitly named properties "lowerCorner" and "upperCorner" shall be used instead. - - - - - gml:AbstractGeometricPrimitiveType is the abstract root type of the geometric primitives. A geometric primitive is a geometric object that is not decomposed further into other primitives in the system. All primitives are oriented in the direction implied by the sequence of their coordinate tuples. - - - - - - - - The AbstractGeometricPrimitive element is the abstract head of the substitution group for all (pre- and user-defined) geometric primitives. - - - - - A property that has a geometric primitive as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. - - - - - - - - - - - - - - - - - - - - - A Point is defined by a single coordinate tuple. The direct position of a point is specified by the pos element which is of type DirectPositionType. - - - - - A property that has a point as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. - - - - - - - - - - This property element either references a point via the XLink-attributes or contains the point element. pointProperty is the predefined property which may be used by GML Application Schemas whenever a GML feature has a property with a value that is substitutable for Point. - - - - - gml:PointArrayPropertyType is a container for an array of points. The elements are always contained inline in the array property, referencing geometry elements or arrays of geometry elements via XLinks is not supported. - - - - - - - - - gml:AbstractCurveType is an abstraction of a curve to support the different levels of complexity. The curve may always be viewed as a geometric primitive, i.e. is continuous. - - - - - - - - The AbstractCurve element is the abstract head of the substitution group for all (continuous) curve elements. - - - - - A property that has a curve as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. - - - - - - - - - - This property element either references a curve via the XLink-attributes or contains the curve element. curveProperty is the predefined property which may be used by GML Application Schemas whenever a GML feature has a property with a value that is substitutable for AbstractCurve. - - - - - A container for an array of curves. The elements are always contained in the array property, referencing geometry elements or arrays of geometry elements via XLinks is not supported. - - - - - - - - - - - - - - - - - - - - - - - - A LineString is a special curve that consists of a single segment with linear interpolation. It is defined by two or more coordinate tuples, with linear interpolation between them. The number of direct positions in the list shall be at least two. - - - + + + + + geometryBasic0d1d.xsd + See ISO/DIS 19136 Clause 10. +Any geometry element that inherits the semantics of AbstractGeometryType may be viewed as a set of direct positions. +All of the classes derived from AbstractGeometryType inherit an optional association to a coordinate reference system. All direct positions shall directly or indirectly be associated with a coordinate reference system. When geometry elements are aggregated in another geometry element (such as a MultiGeometry or GeometricComplex), which already has a coordinate reference system specified, then these elements are assumed to be in that same coordinate reference system unless otherwise specified. +The geometry model distinguishes geometric primitives, aggregates and complexes. +Geometric primitives, i.e. instances of a subtype of AbstractGeometricPrimitiveType, will be open, that is, they will not contain their boundary points; curves will not contain their end points, surfaces will not contain their boundary curves, and solids will not contain their bounding surfaces. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium, Inc. All Rights Reserved. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + All geometry elements are derived directly or indirectly from this abstract supertype. A geometry element may have an identifying attribute (gml:id), one or more names (elements identifier and name) and a description (elements description and descriptionReference) . It may be associated with a spatial reference system (attribute group gml:SRSReferenceGroup). +The following rules shall be adhered to: +- Every geometry type shall derive from this abstract type. +- Every geometry element (i.e. an element of a geometry type) shall be directly or indirectly in the substitution group of AbstractGeometry. + + + + + + + + + + The attribute group SRSReferenceGroup is an optional reference to the CRS used by this geometry, with optional additional information to simplify the processing of the coordinates when a more complete definition of the CRS is not needed. +In general the attribute srsName points to a CRS instance of gml:AbstractCoordinateReferenceSystem. For well-known references it is not required that the CRS description exists at the location the URI points to. +If no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of. + + + + + + + + The attributes uomLabels and axisLabels, defined in the SRSInformationGroup attribute group, are optional additional and redundant information for a CRS to simplify the processing of the coordinate values when a more complete definition of the CRS is not needed. This information shall be the same as included in the complete definition of the CRS, referenced by the srsName attribute. When the srsName attribute is included, either both or neither of the axisLabels and uomLabels attributes shall be included. When the srsName attribute is omitted, both of these attributes shall be omitted. +The attribute axisLabels is an ordered list of labels for all the axes of this CRS. The gml:axisAbbrev value should be used for these axis labels, after spaces and forbidden characters are removed. When the srsName attribute is included, this attribute is optional. When the srsName attribute is omitted, this attribute shall also be omitted. +The attribute uomLabels is an ordered list of unit of measure (uom) labels for all the axes of this CRS. The value of the string in the gml:catalogSymbol should be used for this uom labels, after spaces and forbidden characters are removed. When the axisLabels attribute is included, this attribute shall also be included. When the axisLabels attribute is omitted, this attribute shall also be omitted. + + + + + The AbstractGeometry element is the abstract head of the substitution group for all geometry elements of GML. This includes pre-defined and user-defined geometry elements. Any geometry element shall be a direct or indirect extension/restriction of AbstractGeometryType and shall be directly or indirectly in the substitution group of AbstractGeometry. + + + + + A geometric property may either be any geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same or another document). Note that either the reference or the contained element shall be given, but not both or none. +If a feature has a property that takes a geometry element as its value, this is called a geometry property. A generic type for such a geometry property is GeometryPropertyType. + + + + + + + + + + If a feature has a property which takes an array of geometry elements as its value, this is called a geometry array property. A generic type for such a geometry property is GeometryArrayPropertyType. +The elements are always contained inline in the array property, referencing geometry elements or arrays of geometry elements via XLinks is not supported. + + + + + + + + + Direct position instances hold the coordinates for a position within some coordinate reference system (CRS). Since direct positions, as data types, will often be included in larger objects (such as geometry elements) that have references to CRS, the srsName attribute will in general be missing, if this particular direct position is included in a larger element with such a reference to a CRS. In this case, the CRS is implicitly assumed to take on the value of the containing object's CRS. +if no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of, typically a geometric object like a point, curve, etc. + + + + + + + + + + + posList instances (and other instances with the content model specified by DirectPositionListType) hold the coordinates for a sequence of direct positions within the same coordinate reference system (CRS). +if no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of, typically a geometric object like a point, curve, etc. +The optional attribute count specifies the number of direct positions in the list. If the attribute count is present then the attribute srsDimension shall be present, too. +The number of entries in the list is equal to the product of the dimensionality of the coordinate reference system (i.e. it is a derived value of the coordinate reference system definition) and the number of direct positions. + + + + + + + + + + + + GML supports two different ways to specify a geometric position: either by a direct position (a data type) or a point (a geometric object). +pos elements are positions that are "owned" by the geometric primitive encapsulating this geometric position. +pointProperty elements contain a point that may be referenced from other geometry elements or reference another point defined elsewhere (reuse of existing points). + + + + + + + + + GML supports two different ways to specify a list of geometric positions: either by a sequence of geometric positions (by reusing the group definition) or a sequence of direct positions (element posList). +The posList element allows for a compact way to specify the coordinates of the positions, if all positions are represented in the same coordinate reference system. + + + + + + + + + For some applications the components of the position may be adjusted to yield a unit vector. + + + + + + + + + + + + + + + deprecated + + + + + + + + Envelope defines an extent using a pair of positions defining opposite corners in arbitrary dimensions. The first direct position is the "lower corner" (a coordinate position consisting of all the minimal ordinates for each dimension for all points within the envelope), the second one the "upper corner" (a coordinate position consisting of all the maximal ordinates for each dimension for all points within the envelope). +The use of the properties "coordinates" and "pos" has been deprecated. The explicitly named properties "lowerCorner" and "upperCorner" shall be used instead. + + + + + gml:AbstractGeometricPrimitiveType is the abstract root type of the geometric primitives. A geometric primitive is a geometric object that is not decomposed further into other primitives in the system. All primitives are oriented in the direction implied by the sequence of their coordinate tuples. + + + + + + + + The AbstractGeometricPrimitive element is the abstract head of the substitution group for all (pre- and user-defined) geometric primitives. + + + + + A property that has a geometric primitive as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + + + + + + + + + + + + A Point is defined by a single coordinate tuple. The direct position of a point is specified by the pos element which is of type DirectPositionType. + + + + + A property that has a point as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + This property element either references a point via the XLink-attributes or contains the point element. pointProperty is the predefined property which may be used by GML Application Schemas whenever a GML feature has a property with a value that is substitutable for Point. + + + + + gml:PointArrayPropertyType is a container for an array of points. The elements are always contained inline in the array property, referencing geometry elements or arrays of geometry elements via XLinks is not supported. + + + + + + + + + gml:AbstractCurveType is an abstraction of a curve to support the different levels of complexity. The curve may always be viewed as a geometric primitive, i.e. is continuous. + + + + + + + + The AbstractCurve element is the abstract head of the substitution group for all (continuous) curve elements. + + + + + A property that has a curve as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + This property element either references a curve via the XLink-attributes or contains the curve element. curveProperty is the predefined property which may be used by GML Application Schemas whenever a GML feature has a property with a value that is substitutable for AbstractCurve. + + + + + A container for an array of curves. The elements are always contained in the array property, referencing geometry elements or arrays of geometry elements via XLinks is not supported. + + + + + + + + + + + + + + + + + + + + + + + + A LineString is a special curve that consists of a single segment with linear interpolation. It is defined by two or more coordinate tuples, with linear interpolation between them. The number of direct positions in the list shall be at least two. + + + diff --git a/xsd/gml/gmlBase-extract.xsd b/xsd/gml/gmlBase-extract.xsd index bc2308e9..a870b6d7 100644 --- a/xsd/gml/gmlBase-extract.xsd +++ b/xsd/gml/gmlBase-extract.xsd @@ -1,168 +1,168 @@ - - - - gmlBase.xsd - See ISO/DIS 19136 7.2. -The gmlBase schema components establish the GML model and syntax, in particular -- a root XML type from which XML types for all GML objects should be derived, -- a pattern and components for GML properties, -- patterns for collections and arrays, and components for generic collections and arrays, -- components for associating metadata with GML objects, -- components for constructing definitions and dictionaries. - -GML is an OGC Standard. -Copyright (c) 2007,2010 Open Geospatial Consortium, Inc. All Rights Reserved. -To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . - - - - - - - This element has no type defined, and is therefore implicitly (according to the rules of W3C XML Schema) an XML Schema anyType. It is used as the head of an XML Schema substitution group which unifies complex content and certain simple content elements used for datatypes in GML, including the gml:AbstractGML substitution group. - - - - - The abstract element gml:AbstractGML is "any GML object having identity". It acts as the head of an XML Schema substitution group, which may include any element which is a GML feature, or other object, with identity. This is used as a variable in content models in GML core and application schemas. It is effectively an abstract superclass for all GML objects. - - - - - - - - - - - - - - - - - - XLink components are the standard method to support hypertext referencing in XML. An XML Schema attribute group, gml:AssociationAttributeGroup, is provided to support the use of Xlinks as the method for indicating the value of a property by reference in a uniform manner in GML. - - - - - - Applying this pattern shall restrict the multiplicity of objects in a property element using this content model to exactly one. An instance of this type shall contain an element representing an object, or serve as a pointer to a remote object. -Applying the pattern to define an application schema specific property type allows to restrict -- the inline object to specified object types, -- the encoding to "by-reference only" (see 7.2.3.7), -- the encoding to "inline only" (see 7.2.3.8). - - - - - - - - - - - - Encoding a GML property inline vs. by-reference shall not imply anything about the "ownership" of the contained or referenced GML Object, i.e. the encoding style shall not imply any "deep-copy" or "deep-delete" semantics. To express ownership over the contained or referenced GML Object, the gml:OwnershipAttributeGroup attribute group may be added to object-valued property elements. If the attribute group is not part of the content model of such a property element, then the value may not be "owned". -When the value of the owns attribute is "true", the existence of inline or referenced object(s) depends upon the existence of the parent object. - - - - - - This element shows how an element - declaration may include a Schematron constraint to limit the property to act - in either inline or by-reference mode, but not both. - - - - - gml:abstractReference may be used as the head of a subtitution group of more specific elements providing a value by-reference. - - - - - gml:ReferenceType is intended to be used in application schemas directly, if a property element shall use a "by-reference only" encoding. - - - - - - - gml:abstractInlineProperty may be used as the head of a subtitution group of more specific elements providing a value inline. - - - - - - - - - - - If the value of an object property is another object and that object contains also a property for the association between the two objects, then this name of the reverse property may be encoded in a gml:reversePropertyName element in an appinfo annotation of the property element to document the constraint between the two properties. The value of the element shall contain the qualified name of the property element. - - - - - The value of this property is a remote text description of the object. The xlink:href attribute of the gml:descriptionReference property references the external description. - - - - - The gml:name property provides a label or identifier for the object, commonly a descriptive name. An object may have several names, typically assigned by different authorities. gml:name uses the gml:CodeType content model. The authority for a name is indicated by the value of its (optional) codeSpace attribute. The name may or may not be unique, as determined by the rules of the organization responsible for the codeSpace. In common usage there will be one name per authority, so a processing application may select the name from its preferred codeSpace. - - - - - Often, a special identifier is assigned to an object by the maintaining authority with the intention that it is used in references to the object For such cases, the codeSpace shall be provided. That identifier is usually unique either globally or within an application domain. gml:identifier is a pre-defined property for such identifiers. - - - - - The attribute gml:id supports provision of a handle for the XML element representing a GML Object. Its use is mandatory for all GML objects. It is of XML type ID, so is constrained to be unique in the XML document within which it occurs. - - - - - To create a collection of GML Objects that are not all features, a property type shall be derived by extension from gml:AbstractMemberType. -This abstract property type is intended to be used only in object types where software shall be able to identify that an instance of such an object type is to be interpreted as a collection of objects. -By default, this abstract property type does not imply any ownership of the objects in the collection. The owns attribute of gml:OwnershipAttributeGroup may be used on a property element instance to assert ownership of an object in the collection. A collection shall not own an object already owned by another object. - - - - - - - A GML Object Collection is any GML Object with a property element in its content model whose content model is derived by extension from gml:AbstractMemberType. -In addition, the complex type describing the content model of the GML Object Collection may also include a reference to the attribute group gml:AggregationAttributeGroup to provide additional information about the semantics of the object collection. This information may be used by applications to group GML objects, and optionally to order and index them. -The allowed values for the aggregationType attribute are defined by gml:AggregationType. See 8.4 of ISO/IEC 11404:1996 for the meaning of the values in the enumeration. - - - - - - - - - - - - - - - - To associate metadata described by any XML Schema with a GML object, a property element shall be defined whose content model is derived by extension from gml:AbstractMetadataPropertyType. -The value of such a property shall be metadata. The content model of such a property type, i.e. the metadata application schema shall be specified by the GML Application Schema. -By default, this abstract property type does not imply any ownership of the metadata. The owns attribute of gml:OwnershipAttributeGroup may be used on a metadata property element instance to assert ownership of the metadata. -If metadata following the conceptual model of ISO 19115 is to be encoded in a GML document, the corresponding Implementation Specification specified in ISO/TS 19139 shall be used to encode the metadata information. - - - - - - - - - + + + + gmlBase.xsd + See ISO/DIS 19136 7.2. +The gmlBase schema components establish the GML model and syntax, in particular +- a root XML type from which XML types for all GML objects should be derived, +- a pattern and components for GML properties, +- patterns for collections and arrays, and components for generic collections and arrays, +- components for associating metadata with GML objects, +- components for constructing definitions and dictionaries. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium, Inc. All Rights Reserved. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + + This element has no type defined, and is therefore implicitly (according to the rules of W3C XML Schema) an XML Schema anyType. It is used as the head of an XML Schema substitution group which unifies complex content and certain simple content elements used for datatypes in GML, including the gml:AbstractGML substitution group. + + + + + The abstract element gml:AbstractGML is "any GML object having identity". It acts as the head of an XML Schema substitution group, which may include any element which is a GML feature, or other object, with identity. This is used as a variable in content models in GML core and application schemas. It is effectively an abstract superclass for all GML objects. + + + + + + + + + + + + + + + + + + XLink components are the standard method to support hypertext referencing in XML. An XML Schema attribute group, gml:AssociationAttributeGroup, is provided to support the use of Xlinks as the method for indicating the value of a property by reference in a uniform manner in GML. + + + + + + Applying this pattern shall restrict the multiplicity of objects in a property element using this content model to exactly one. An instance of this type shall contain an element representing an object, or serve as a pointer to a remote object. +Applying the pattern to define an application schema specific property type allows to restrict +- the inline object to specified object types, +- the encoding to "by-reference only" (see 7.2.3.7), +- the encoding to "inline only" (see 7.2.3.8). + + + + + + + + + + + + Encoding a GML property inline vs. by-reference shall not imply anything about the "ownership" of the contained or referenced GML Object, i.e. the encoding style shall not imply any "deep-copy" or "deep-delete" semantics. To express ownership over the contained or referenced GML Object, the gml:OwnershipAttributeGroup attribute group may be added to object-valued property elements. If the attribute group is not part of the content model of such a property element, then the value may not be "owned". +When the value of the owns attribute is "true", the existence of inline or referenced object(s) depends upon the existence of the parent object. + + + + + + This element shows how an element + declaration may include a Schematron constraint to limit the property to act + in either inline or by-reference mode, but not both. + + + + + gml:abstractReference may be used as the head of a subtitution group of more specific elements providing a value by-reference. + + + + + gml:ReferenceType is intended to be used in application schemas directly, if a property element shall use a "by-reference only" encoding. + + + + + + + gml:abstractInlineProperty may be used as the head of a subtitution group of more specific elements providing a value inline. + + + + + + + + + + + If the value of an object property is another object and that object contains also a property for the association between the two objects, then this name of the reverse property may be encoded in a gml:reversePropertyName element in an appinfo annotation of the property element to document the constraint between the two properties. The value of the element shall contain the qualified name of the property element. + + + + + The value of this property is a remote text description of the object. The xlink:href attribute of the gml:descriptionReference property references the external description. + + + + + The gml:name property provides a label or identifier for the object, commonly a descriptive name. An object may have several names, typically assigned by different authorities. gml:name uses the gml:CodeType content model. The authority for a name is indicated by the value of its (optional) codeSpace attribute. The name may or may not be unique, as determined by the rules of the organization responsible for the codeSpace. In common usage there will be one name per authority, so a processing application may select the name from its preferred codeSpace. + + + + + Often, a special identifier is assigned to an object by the maintaining authority with the intention that it is used in references to the object For such cases, the codeSpace shall be provided. That identifier is usually unique either globally or within an application domain. gml:identifier is a pre-defined property for such identifiers. + + + + + The attribute gml:id supports provision of a handle for the XML element representing a GML Object. Its use is mandatory for all GML objects. It is of XML type ID, so is constrained to be unique in the XML document within which it occurs. + + + + + To create a collection of GML Objects that are not all features, a property type shall be derived by extension from gml:AbstractMemberType. +This abstract property type is intended to be used only in object types where software shall be able to identify that an instance of such an object type is to be interpreted as a collection of objects. +By default, this abstract property type does not imply any ownership of the objects in the collection. The owns attribute of gml:OwnershipAttributeGroup may be used on a property element instance to assert ownership of an object in the collection. A collection shall not own an object already owned by another object. + + + + + + + A GML Object Collection is any GML Object with a property element in its content model whose content model is derived by extension from gml:AbstractMemberType. +In addition, the complex type describing the content model of the GML Object Collection may also include a reference to the attribute group gml:AggregationAttributeGroup to provide additional information about the semantics of the object collection. This information may be used by applications to group GML objects, and optionally to order and index them. +The allowed values for the aggregationType attribute are defined by gml:AggregationType. See 8.4 of ISO/IEC 11404:1996 for the meaning of the values in the enumeration. + + + + + + + + + + + + + + + + To associate metadata described by any XML Schema with a GML object, a property element shall be defined whose content model is derived by extension from gml:AbstractMetadataPropertyType. +The value of such a property shall be metadata. The content model of such a property type, i.e. the metadata application schema shall be specified by the GML Application Schema. +By default, this abstract property type does not imply any ownership of the metadata. The owns attribute of gml:OwnershipAttributeGroup may be used on a metadata property element instance to assert ownership of the metadata. +If metadata following the conceptual model of ISO 19115 is to be encoded in a GML document, the corresponding Implementation Specification specified in ISO/TS 19139 shall be used to encode the metadata information. + + + + + + + + + diff --git a/xsd/gml/gmlBasic2d-extract.xsd b/xsd/gml/gmlBasic2d-extract.xsd index 386b5b4b..a7e51919 100644 --- a/xsd/gml/gmlBasic2d-extract.xsd +++ b/xsd/gml/gmlBasic2d-extract.xsd @@ -1,120 +1,120 @@ - - - - geometryBasic2d.xsd - See ISO/DIS 19136 Clause 10. - - GML is an OGC Standard. - Copyright (c) 2007,2010 Open Geospatial Consortium, Inc. All Rights Reserved. - To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . - - - - - - gml:AbstractSurfaceType is an abstraction of a surface to support the different levels of complexity. A surface is always a continuous region of a plane. - - - - - - - - The AbstractSurface element is the abstract head of the substitution group for all (continuous) surface elements. - - - - - A property that has a surface as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. - - - - - - - - - - This property element either references a surface via the XLink-attributes or contains the surface element. surfaceProperty is the predefined property which may be used by GML Application Schemas whenever a GML feature has a property with a value that is substitutable for AbstractSurface. - - - - - gml:SurfaceArrayPropertyType is a container for an array of surfaces. The elements are always contained in the array property, referencing geometry elements or arrays of geometry elements via XLinks is not supported. - - - - - - - - - - - - - - - - - - - A Polygon is a special surface that is defined by a single surface patch (see D.3.6). The boundary of this patch is coplanar and the polygon uses planar interpolation in its interior. -The elements exterior and interior describe the surface boundary of the polygon. - - - - - A boundary of a surface consists of a number of rings. In the normal 2D case, one of these rings is distinguished as being the exterior boundary. In a general manifold this is not always possible, in which case all boundaries shall be listed as interior boundaries, and the exterior will be empty. - - - - - A boundary of a surface consists of a number of rings. The "interior" rings separate the surface / surface patch from the area enclosed by the rings. - - - - - - - An abstraction of a ring to support surface boundaries of different complexity. -The AbstractRing element is the abstract head of the substitution group for all closed boundaries of a surface patch. - - - - - A property with the content model of gml:AbstractRingPropertyType encapsulates a ring to represent the surface boundary property of a surface. - - - - - - - - - - - - - - - - - - - - - - - A LinearRing is defined by four or more coordinate tuples, with linear interpolation between them; the first and last coordinates shall be coincident. The number of direct positions in the list shall be at least four. - - - - - A property with the content model of gml:LinearRingPropertyType encapsulates a linear ring to represent a component of a surface boundary. - - - - - - + + + + geometryBasic2d.xsd + See ISO/DIS 19136 Clause 10. + + GML is an OGC Standard. + Copyright (c) 2007,2010 Open Geospatial Consortium, Inc. All Rights Reserved. + To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + gml:AbstractSurfaceType is an abstraction of a surface to support the different levels of complexity. A surface is always a continuous region of a plane. + + + + + + + + The AbstractSurface element is the abstract head of the substitution group for all (continuous) surface elements. + + + + + A property that has a surface as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + This property element either references a surface via the XLink-attributes or contains the surface element. surfaceProperty is the predefined property which may be used by GML Application Schemas whenever a GML feature has a property with a value that is substitutable for AbstractSurface. + + + + + gml:SurfaceArrayPropertyType is a container for an array of surfaces. The elements are always contained in the array property, referencing geometry elements or arrays of geometry elements via XLinks is not supported. + + + + + + + + + + + + + + + + + + + A Polygon is a special surface that is defined by a single surface patch (see D.3.6). The boundary of this patch is coplanar and the polygon uses planar interpolation in its interior. +The elements exterior and interior describe the surface boundary of the polygon. + + + + + A boundary of a surface consists of a number of rings. In the normal 2D case, one of these rings is distinguished as being the exterior boundary. In a general manifold this is not always possible, in which case all boundaries shall be listed as interior boundaries, and the exterior will be empty. + + + + + A boundary of a surface consists of a number of rings. The "interior" rings separate the surface / surface patch from the area enclosed by the rings. + + + + + + + An abstraction of a ring to support surface boundaries of different complexity. +The AbstractRing element is the abstract head of the substitution group for all closed boundaries of a surface patch. + + + + + A property with the content model of gml:AbstractRingPropertyType encapsulates a ring to represent the surface boundary property of a surface. + + + + + + + + + + + + + + + + + + + + + + + A LinearRing is defined by four or more coordinate tuples, with linear interpolation between them; the first and last coordinates shall be coincident. The number of direct positions in the list shall be at least four. + + + + + A property with the content model of gml:LinearRingPropertyType encapsulates a linear ring to represent a component of a surface boundary. + + + + + + diff --git a/xsd/gml/gml_extract_all_objects.xsd b/xsd/gml/gml_extract_all_objects.xsd index cd6227d3..1771bb9f 100644 --- a/xsd/gml/gml_extract_all_objects.xsd +++ b/xsd/gml/gml_extract_all_objects.xsd @@ -1,12 +1,12 @@ - - - - - - - - - - - - + + + + + + + + + + + + diff --git a/xsd/ifopt/ifopt_administration.xsd b/xsd/ifopt/ifopt_administration.xsd index bb098f19..d09d011b 100644 --- a/xsd/ifopt/ifopt_administration.xsd +++ b/xsd/ifopt/ifopt_administration.xsd @@ -1,254 +1,254 @@ - - - - - - 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.siri.org.uk/schema/2.0/ifopt}ifopt_administration.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, Crown Copyright 2006-2021 - - -
        -
      • Derived from the SIRI standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG6 - - IFOPT Fixed Objects in Public Transport - Base Types. - Standard -       -       - Data administration types for IFOPT Fixed Objects in Public Transport. -       - - - - - - - Type for identifier of an ORGANISATION with administrative responsibility. - - - - - - Type for a reference to an ORGANISATION with administrative responsibility. - - - - - - - - Type for a versioned reference to an ORGANISATION with administrative responsibility. - - - - - - - - - - - Type for identifier of ADMINISTRATIVE ZONE. - - - - - - - - Type for a reference to an ADMINISTRATIVE ZONE. - - - - - - - - Type for a versioned reference to anADMINISTRATIVE ZONE. - - - - - - - - - - Type for a collection of one or more references to ADMINISTRATIVE ZONEs. - - - - - Reference to the identifier of an ADMINISTRATIVE ZONE. - - - - - - - - Enumeration of allowed values for RESPONSIBILITY ROLEs. - - - - - - - - - - - - - - Type for identifier of type of Namespace. - - - - - - Type for a reference to an Namespace. - - - - - - - - The type for identifier of Namespace. - - - - - - Type for a value of a namespace. - - - - - - - Type for a Identifier of Region. - - - - - - Type for a Reference to identifier of Region. - - - - - - - - - Type for identifier of AUTHORITY. - - - - - - - - Type for a reference to an AUTHORITY. - - - - - - - - - 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 DATA MANAGED OBJECT, that is an object that may be assigned a RESPONSIBILITY SET dictating a responsible ORGANISATION and/or ADMINISTRATIVE ZONE. - - - - - - - - - - - - Elements for a DATA MANAGED OBJECT. - - - - - ADMINISTRATIVE ZONEthat manages object. If absent then manager same as for containing parent of object. - - - - - Collection of URL's associated with object. - - - - -       + + + + + + 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.siri.org.uk/schema/2.0/ifopt}ifopt_administration.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + CEN, Crown Copyright 2006-2021 + + +
        +
      • Derived from the SIRI standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG6 + + IFOPT Fixed Objects in Public Transport - Base Types. + Standard +       +       + Data administration types for IFOPT Fixed Objects in Public Transport. +       + + + + + + + Type for identifier of an ORGANISATION with administrative responsibility. + + + + + + Type for a reference to an ORGANISATION with administrative responsibility. + + + + + + + + Type for a versioned reference to an ORGANISATION with administrative responsibility. + + + + + + + + + + + Type for identifier of ADMINISTRATIVE ZONE. + + + + + + + + Type for a reference to an ADMINISTRATIVE ZONE. + + + + + + + + Type for a versioned reference to anADMINISTRATIVE ZONE. + + + + + + + + + + Type for a collection of one or more references to ADMINISTRATIVE ZONEs. + + + + + Reference to the identifier of an ADMINISTRATIVE ZONE. + + + + + + + + Enumeration of allowed values for RESPONSIBILITY ROLEs. + + + + + + + + + + + + + + Type for identifier of type of Namespace. + + + + + + Type for a reference to an Namespace. + + + + + + + + The type for identifier of Namespace. + + + + + + Type for a value of a namespace. + + + + + + + Type for a Identifier of Region. + + + + + + Type for a Reference to identifier of Region. + + + + + + + + + Type for identifier of AUTHORITY. + + + + + + + + Type for a reference to an AUTHORITY. + + + + + + + + + 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 DATA MANAGED OBJECT, that is an object that may be assigned a RESPONSIBILITY SET dictating a responsible ORGANISATION and/or ADMINISTRATIVE ZONE. + + + + + + + + + + + + Elements for a DATA MANAGED OBJECT. + + + + + ADMINISTRATIVE ZONEthat manages object. If absent then manager same as for containing parent of object. + + + + + Collection of URL's associated with object. + + + + +       diff --git a/xsd/ifopt/ifopt_allStopPlace.xsd b/xsd/ifopt/ifopt_allStopPlace.xsd index b164f96e..bd231b33 100644 --- a/xsd/ifopt/ifopt_allStopPlace.xsd +++ b/xsd/ifopt/ifopt_allStopPlace.xsd @@ -1,33 +1,33 @@ - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + diff --git a/xsd/ifopt/ifopt_checkpoint.xsd b/xsd/ifopt/ifopt_checkpoint.xsd index e56f494a..c5201fec 100644 --- a/xsd/ifopt/ifopt_checkpoint.xsd +++ b/xsd/ifopt/ifopt_checkpoint.xsd @@ -1,222 +1,222 @@ - - - - - - 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 CHECK CONSTRAINT types.

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_accessibility.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, Crown Copyright 2006-2021 - - -
        -
      • Derived from the IFOPT standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG6 - - IFOPT Fixed Objects in Public Transport - CHECK CONSTRAINT Types. - Standard -       -       - Fixed Objects CHECK CONSTRAINT types for IFOPT Fixed Objects in Public Transport. -       - - - - - - Type for identifier of a CHECK CONSTRAINT.within a STOP PLACE. - - - - - - Type for reference to am identifier of a hazard within a STOP PLACE. - - - - - - - - - Type for a CHECK CONSTRAINT Hazard that can be associated with. - - - - - Identifier of CHECK CONSTRAINt. - - - - - - - - - - - Validty condition governing applicability of CHECK CONSTRAINT. - - - - - Type of process that may occur at CHECK CONSTRAINt. - - - - - Type of process that may occur at CHECK CONSTRAINt. - - - - - Type of physical featrue that may slow use of CHECK CONSTRAINt. - - - - - Type of crowding that may slow use of CHECK CONSTRAINt. - - - - - Classification of feature of CHECK CONSTRAINT. - - - - - - - Allowed values for a CHECK CONSTRAINT. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Allowed values for a CHECK CONSTRAINT. - - - - - - - - - - Allowed values for a CHECK CONSTRAINT. - - - - - - - - - - - - - - - - - - - - - Allowed values for a CHECK CONSTRAINT. - - - - - - - - - - - Group of delays found at a stop group. Duratiosn relate to given validity condition. - - - - - Minimum duration needed to pass through CHECK CONSTRAINT. - - - - - Average duration expected to pass through CHECK CONSTRAINT. - - - - - Maximum duration expected to pass through CHECK CONSTRAINT. - - - - - -       + + + + + + 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 CHECK CONSTRAINT types.

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_accessibility.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + CEN, Crown Copyright 2006-2021 + + +
        +
      • Derived from the IFOPT standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG6 + + IFOPT Fixed Objects in Public Transport - CHECK CONSTRAINT Types. + Standard +       +       + Fixed Objects CHECK CONSTRAINT types for IFOPT Fixed Objects in Public Transport. +       + + + + + + Type for identifier of a CHECK CONSTRAINT.within a STOP PLACE. + + + + + + Type for reference to am identifier of a hazard within a STOP PLACE. + + + + + + + + + Type for a CHECK CONSTRAINT Hazard that can be associated with. + + + + + Identifier of CHECK CONSTRAINt. + + + + + + + + + + + Validty condition governing applicability of CHECK CONSTRAINT. + + + + + Type of process that may occur at CHECK CONSTRAINt. + + + + + Type of process that may occur at CHECK CONSTRAINt. + + + + + Type of physical featrue that may slow use of CHECK CONSTRAINt. + + + + + Type of crowding that may slow use of CHECK CONSTRAINt. + + + + + Classification of feature of CHECK CONSTRAINT. + + + + + + + Allowed values for a CHECK CONSTRAINT. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Allowed values for a CHECK CONSTRAINT. + + + + + + + + + + Allowed values for a CHECK CONSTRAINT. + + + + + + + + + + + + + + + + + + + + + Allowed values for a CHECK CONSTRAINT. + + + + + + + + + + + Group of delays found at a stop group. Duratiosn relate to given validity condition. + + + + + Minimum duration needed to pass through CHECK CONSTRAINT. + + + + + Average duration expected to pass through CHECK CONSTRAINT. + + + + + Maximum duration expected to pass through CHECK CONSTRAINT. + + + + + +       diff --git a/xsd/ifopt/ifopt_countries.xsd b/xsd/ifopt/ifopt_countries.xsd index a52b6449..9dfdadbf 100644 --- a/xsd/ifopt/ifopt_countries.xsd +++ b/xsd/ifopt/ifopt_countries.xsd @@ -1,1320 +1,1320 @@ - - - - - - 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.siri.org.uk/schema/2.0/ifopt}ifopt_countries.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, Crown Copyright 2006-2021 - - -
        -
      • Derived from the SIRI standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 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. - - - - - -       + + + + + + 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.siri.org.uk/schema/2.0/ifopt}ifopt_countries.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + CEN, Crown Copyright 2006-2021 + + +
        +
      • Derived from the SIRI standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 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/xsd/ifopt/ifopt_equipment.xsd b/xsd/ifopt/ifopt_equipment.xsd index e8d1319c..e18088f0 100644 --- a/xsd/ifopt/ifopt_equipment.xsd +++ b/xsd/ifopt/ifopt_equipment.xsd @@ -1,207 +1,207 @@ - - - - - - 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.siri.org.uk/schema/2.0/ifopt}ifopt_equipment.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, Crown Copyright 2006-2021 - - -
        -
      • Derived from the TransModel standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG6 - - IFOPT Fixed Objects in Public Transport - Equipment Base Types. - Standard -       -       - Equipment types for IFOPT Fixed Objects in Public Transport. -       - - - - - - - - Type for identifier of EQUIPMENT. - - - - - - Type for reference to a EQUIPMENT. - - - - - - - - - Type for a identifier of EQUIPMENT. - - - - - - Type for TYPE OF EQUIPMENT. - - - - - - - - - Availabilityload status of a EQUIPMENT. - - - - - - - - - - - Coomon Elements for EQUIPMENt. - - - - - Identifer of EQUIPMENT. - - - - - Name of EQUIPMENT. - - - - - Type for reference to TYPE OF EQUIPMENT. - - - - - - - Type for abstract EQUIPMENT. - - - - - - - - - - - - Type for INSTALLED EQUIPMENT. - - - - - - - - - Type for SITE EQUIPMENT. - - - - - - - - - - - - EQUIPMENT. that may be in a fixed within a SITe. - - - - - - LOCAL SERVICe. - - - - - Element for LOCAL SERVICe. - - - - - Conditison governing availability of serevice. - - - - - Classification of features. - - - - - - Features of LOCAL SERVICe. - - - - - - - - - - Type for LOCAL SERVICE. - - - - - - - - - - -       + + + + + + 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.siri.org.uk/schema/2.0/ifopt}ifopt_equipment.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + CEN, Crown Copyright 2006-2021 + + +
        +
      • Derived from the TransModel standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG6 + + IFOPT Fixed Objects in Public Transport - Equipment Base Types. + Standard +       +       + Equipment types for IFOPT Fixed Objects in Public Transport. +       + + + + + + + + Type for identifier of EQUIPMENT. + + + + + + Type for reference to a EQUIPMENT. + + + + + + + + + Type for a identifier of EQUIPMENT. + + + + + + Type for TYPE OF EQUIPMENT. + + + + + + + + + Availabilityload status of a EQUIPMENT. + + + + + + + + + + + Coomon Elements for EQUIPMENt. + + + + + Identifer of EQUIPMENT. + + + + + Name of EQUIPMENT. + + + + + Type for reference to TYPE OF EQUIPMENT. + + + + + + + Type for abstract EQUIPMENT. + + + + + + + + + + + + Type for INSTALLED EQUIPMENT. + + + + + + + + + Type for SITE EQUIPMENT. + + + + + + + + + + + + EQUIPMENT. that may be in a fixed within a SITe. + + + + + + LOCAL SERVICe. + + + + + Element for LOCAL SERVICe. + + + + + Conditison governing availability of serevice. + + + + + Classification of features. + + + + + + Features of LOCAL SERVICe. + + + + + + + + + + Type for LOCAL SERVICE. + + + + + + + + + + +       diff --git a/xsd/ifopt/ifopt_location.xsd b/xsd/ifopt/ifopt_location.xsd index 0f53d84d..9081a640 100644 --- a/xsd/ifopt/ifopt_location.xsd +++ b/xsd/ifopt/ifopt_location.xsd @@ -1,281 +1,281 @@ - - - - - - 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 03 23 Revise projections - - - 2007-06-12 - - 2011-04-19 - Correct siri: namespace - - -

      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.siri.org.uk/schema/2.0/ifopt}ifopt_location.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, Crown Copyright 2006-2021 - - -
        -
      • Derived from the SIRI standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 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 FEATURE in a GIS data system. - - - - - - - - - - Type for reference to a FEATURE. - - - - - Unique identfiier of referenced element, eg TOId. - - - - - Type for identifier of FEATURE. - - - - - - - Type for identifier of a GIS FEATURe. - - - - - - Type for reference to a GIS FEATURe. - - - - - - - - - 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 Coordinates. - - - - - 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 onto 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. - - - - - - - - - - - - - -       + + + + + + 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 03 23 Revise projections + + + 2007-06-12 + + 2011-04-19 + Correct siri: namespace + + +

      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.siri.org.uk/schema/2.0/ifopt}ifopt_location.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + CEN, Crown Copyright 2006-2021 + + +
        +
      • Derived from the SIRI standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 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 FEATURE in a GIS data system. + + + + + + + + + + Type for reference to a FEATURE. + + + + + Unique identfiier of referenced element, eg TOId. + + + + + Type for identifier of FEATURE. + + + + + + + Type for identifier of a GIS FEATURe. + + + + + + Type for reference to a GIS FEATURe. + + + + + + + + + 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 Coordinates. + + + + + 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 onto 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. + + + + + + + + + + + + + +       diff --git a/xsd/ifopt/ifopt_modes.xsd b/xsd/ifopt/ifopt_modes.xsd index 15c88525..aef9d00b 100644 --- a/xsd/ifopt/ifopt_modes.xsd +++ b/xsd/ifopt/ifopt_modes.xsd @@ -1,84 +1,84 @@ - - - - - - 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.siri.org.uk/schema/2.0/ifopt}ifopt_modes.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, Crown Copyright 2006-2021 - - -
        -
      • Derived from the SIRI standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG6 - - IFOPT Fixed Objects in Public Transport - mode Types. - Standard -       -       - Mode types for IFOPT Fixed Objects in Public Transport. -       - - - - - Allowed categories of stop place. - - - - - - - - - - - - - - - - - Allowed categroies of access to stop place. - - - - - - - - - -       + + + + + + 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.siri.org.uk/schema/2.0/ifopt}ifopt_modes.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + CEN, Crown Copyright 2006-2021 + + +
        +
      • Derived from the SIRI standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG6 + + IFOPT Fixed Objects in Public Transport - mode Types. + Standard +       +       + Mode types for IFOPT Fixed Objects in Public Transport. +       + + + + + Allowed categories of stop place. + + + + + + + + + + + + + + + + + Allowed categroies of access to stop place. + + + + + + + + + +       diff --git a/xsd/ifopt/ifopt_modification.xsd b/xsd/ifopt/ifopt_modification.xsd index a4fca7dd..5014a5db 100644 --- a/xsd/ifopt/ifopt_modification.xsd +++ b/xsd/ifopt/ifopt_modification.xsd @@ -1,173 +1,173 @@ - - - - - - - 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.siri.org.uk/schema/2.0/ifopt}ifopt_modification.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, Crown Copyright 2006-2021 - - -
        -
      • Derived from the SIRI standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 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. - - - -       + + + + + + + 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.siri.org.uk/schema/2.0/ifopt}ifopt_modification.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + CEN, Crown Copyright 2006-2021 + + +
        +
      • Derived from the SIRI standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 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/xsd/ifopt/ifopt_path.xsd b/xsd/ifopt/ifopt_path.xsd index 5f1040c5..9119ccb4 100644 --- a/xsd/ifopt/ifopt_path.xsd +++ b/xsd/ifopt/ifopt_path.xsd @@ -1,164 +1,164 @@ - - - - - - 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.siri.org.uk/schema/2.0/ifopt}ifopt_types.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, Crown Copyright 2006-2021 - - -
        -
      • Derived from the SIRI standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG6 - - IFOPT Fixed Objects in Public Transport - Stop place Base Types. - Standard -       -       - Basic link types for IFOPT Fixed Objects in Public Transport. -       - - - - Type for identifier of PATH JUNCTION. - - - - - - Reference to a PATH JUNCTION. - - - - - Type for reference to a PATH JUNCTION. - - - - - - - - - - - Type for identifier of an ACCESS link. - - - - - - Reference to an ACCESS link. - - - - - Type for reference to an ACCESS link. - - - - - - - - - Type for identifier of NAVIGATION PATH. - - - - - - Reference to a NAVIGATION PATH. - - - - - Type for reference to a NAVIGATION PATH. - - - - - - - - - Values for flow DIRECTION along PATH LINk. - - - - - - - - - Values for path heading. - - - - - - - - - - - - - Values for path heading. - - - - - - - - - - - Values for NAVIGATION PATH. type. - - - - - - - - - - - - -       + + + + + + 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.siri.org.uk/schema/2.0/ifopt}ifopt_types.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + CEN, Crown Copyright 2006-2021 + + +
        +
      • Derived from the SIRI standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG6 + + IFOPT Fixed Objects in Public Transport - Stop place Base Types. + Standard +       +       + Basic link types for IFOPT Fixed Objects in Public Transport. +       + + + + Type for identifier of PATH JUNCTION. + + + + + + Reference to a PATH JUNCTION. + + + + + Type for reference to a PATH JUNCTION. + + + + + + + + + + + Type for identifier of an ACCESS link. + + + + + + Reference to an ACCESS link. + + + + + Type for reference to an ACCESS link. + + + + + + + + + Type for identifier of NAVIGATION PATH. + + + + + + Reference to a NAVIGATION PATH. + + + + + Type for reference to a NAVIGATION PATH. + + + + + + + + + Values for flow DIRECTION along PATH LINk. + + + + + + + + + Values for path heading. + + + + + + + + + + + + + Values for path heading. + + + + + + + + + + + Values for NAVIGATION PATH. type. + + + + + + + + + + + + +       diff --git a/xsd/ifopt/ifopt_stop.xsd b/xsd/ifopt/ifopt_stop.xsd index 69295671..87325769 100644 --- a/xsd/ifopt/ifopt_stop.xsd +++ b/xsd/ifopt/ifopt_stop.xsd @@ -1,393 +1,393 @@ - - - - - - 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 - - 2012-03-12 - Change IdentifertYpe to normalizedString - - 2018-11-13 - [vdv] Enum "ferrytPort" in StopPlaceTypeEnumeration changed to "ferryPort" - - -

      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.siri.org.uk/schema/2.0/ifopt}ifopt_types.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, Crown Copyright 2006-2021 - - -
        -
      • Derived from the SIRI standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 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 identifier of STOP PLACE. - - - - - - Reference to a STOP PLACE. - - - - - Type for reference to a STOP PLACE. - - - - - - - - Type for a collection of one or more references to a STOP PLACE. - - - - - - - - - Type for identifier of STOP PLACE. - - - - - - Type for reference to STOP PLACE. - - - - - - - - Type for reference to STOP PLACE Space. - - - - - - - - Type for reference to QUAY. - - - - - - - - Type for reference to ACCESS SPACe. - - - - - - - - Type for reference to BOARDING POSITION. - - - - - - - - Type for reference to STOP PLACE Entrance. - - - - - - - - Type for reference to VEHICLE STOPPING PLACe. - - - - - - - - Type for reference to VEHICLE STOPPING POSITION. - - - - - - - - - Type for identifier of a building LEVEL within a STOP PLACE. - - - - - - Type for reference to identifier of LEVEL. - - - - - - - - - Type for reference to identifier of PATHLINK. - - - - - - - - Type for reference to STOP PLACE Space. - - - - - - - - - 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 identifying the stop by SMS and other self-service channels. - - - - - A private code that 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 SITE COMPONENT Types. - - - - - - - - - - - - Enumeration of QUAY Types. - - - - - - - - - - - - - - - - - - - Enumeration of ACCESS SPACE Types. - - - - - - - - - - - - - - - - - - - - Enumeration of Passage Types. - - - - - - - - - - - - - - Enumeration of BOARDING POSITION Types. - - - - - - - - - - - - - - - - - - - - Enumeration of Relation to VEHICLE of STOPPING POSITION. - - - - - - - - - - - - - Enumeration of Interchange Weighting. - - - - - - - - - -       + + + + + + 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 + + 2012-03-12 + Change IdentifertYpe to normalizedString + + 2018-11-13 + [vdv] Enum "ferrytPort" in StopPlaceTypeEnumeration changed to "ferryPort" + + +

      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.siri.org.uk/schema/2.0/ifopt}ifopt_types.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + CEN, Crown Copyright 2006-2021 + + +
        +
      • Derived from the SIRI standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 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 identifier of STOP PLACE. + + + + + + Reference to a STOP PLACE. + + + + + Type for reference to a STOP PLACE. + + + + + + + + Type for a collection of one or more references to a STOP PLACE. + + + + + + + + + Type for identifier of STOP PLACE. + + + + + + Type for reference to STOP PLACE. + + + + + + + + Type for reference to STOP PLACE Space. + + + + + + + + Type for reference to QUAY. + + + + + + + + Type for reference to ACCESS SPACe. + + + + + + + + Type for reference to BOARDING POSITION. + + + + + + + + Type for reference to STOP PLACE Entrance. + + + + + + + + Type for reference to VEHICLE STOPPING PLACe. + + + + + + + + Type for reference to VEHICLE STOPPING POSITION. + + + + + + + + + Type for identifier of a building LEVEL within a STOP PLACE. + + + + + + Type for reference to identifier of LEVEL. + + + + + + + + + Type for reference to identifier of PATHLINK. + + + + + + + + Type for reference to STOP PLACE Space. + + + + + + + + + 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 identifying the stop by SMS and other self-service channels. + + + + + A private code that 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 SITE COMPONENT Types. + + + + + + + + + + + + Enumeration of QUAY Types. + + + + + + + + + + + + + + + + + + + Enumeration of ACCESS SPACE Types. + + + + + + + + + + + + + + + + + + + + Enumeration of Passage Types. + + + + + + + + + + + + + + Enumeration of BOARDING POSITION Types. + + + + + + + + + + + + + + + + + + + + Enumeration of Relation to VEHICLE of STOPPING POSITION. + + + + + + + + + + + + + Enumeration of Interchange Weighting. + + + + + + + + + +       diff --git a/xsd/ifopt/ifopt_time.xsd b/xsd/ifopt/ifopt_time.xsd index 83b12812..68666289 100644 --- a/xsd/ifopt/ifopt_time.xsd +++ b/xsd/ifopt/ifopt_time.xsd @@ -1,131 +1,131 @@ - - - - - - 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.siri.org.uk/schema/2.0/ifopt}ifopt_types.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, Crown Copyright 2006-2021 - - -
        -
      • Derived from the SIRI standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG6 - - IFOPT Fixed Objects in Public Transport - Time Base Types. - Standard -       -       - Basic Time types for IFOPT Fixed Objects in Public Transport. -       - - - - - - 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 specifed by the EndTimeStatus - - - - - - - - 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. - - - - - -       + + + + + + 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.siri.org.uk/schema/2.0/ifopt}ifopt_types.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + CEN, Crown Copyright 2006-2021 + + +
        +
      • Derived from the SIRI standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG6 + + IFOPT Fixed Objects in Public Transport - Time Base Types. + Standard +       +       + Basic Time types for IFOPT Fixed Objects in Public Transport. +       + + + + + + 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 specifed by the EndTimeStatus + + + + + + + + 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. + + + + + +       diff --git a/xsd/ifopt/ifopt_types.xsd b/xsd/ifopt/ifopt_types.xsd index 8fe51ed1..3f69fb07 100644 --- a/xsd/ifopt/ifopt_types.xsd +++ b/xsd/ifopt/ifopt_types.xsd @@ -1,96 +1,96 @@ - - - - - - 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.siri.org.uk/schema/2.0/ifopt}ifopt_types.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, Crown Copyright 2006-2021 - - -
        -
      • Derived from the SIRI standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 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. - - - -       + + + + + + 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.siri.org.uk/schema/2.0/ifopt}ifopt_types.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + CEN, Crown Copyright 2006-2021 + + +
        +
      • Derived from the SIRI standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 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. + + + +       diff --git a/xsd/siri.xsd b/xsd/siri.xsd index 09aba650..3a41b38c 100644 --- a/xsd/siri.xsd +++ b/xsd/siri.xsd @@ -1,531 +1,531 @@ - - - - - - main schema - e-service developers - - Dipl.-Kfm. Winfried Bruns, Verband Deutscher, Köln, de v1.0 - Mark Cartwright, Centaur Consulting Limited, Guildford, uk v1.0 - Christophe Duquesne, PDG Consultant en systémes, Dryade Guyancourt, fr v1.0 - Stefan Fjällemark, HUR - Hovedstadens, Valby, dk v1.0 - Jonas Jäderberg, Columna, Borlänge, fi v1.0 - Dipl.-Ing. Sven Juergens psitrans juergens@psitrans.de v1.0 - Nicholas Knowles, KIZOOM Limited, London EC4A 1LT, uk v1.0 - Werner Kohl, Mentz Datenverarbeitung GmbH, München,de v1.0 - Peter Miller, ACIS Research and Development, Cambridge CB4 0DL, uk v1.0 - Dr. Martin Siczkowski, West Yorkshire PTE, Leeds, uk v1.0 - Gustav Thiessen BLIC thi@BLIC.DE, de v1.0 - Dr Bartak, bartak@apex-jesenice.cz v1.0 - Dr. Franz-Josef Czuka, Beratungsgesellschaft für, Düsseldorf, de v1.0 - Dr.-Ing. Klaus-Peter Heynert, PSI Transportation GmbH, Berlin, de v1.0 - Jean-Laurant Franchineau, CONNEX-EUROLUM, PARIS, fr v1.0 - Dipl.-Ing. (FH) Rainer Ganninger, init innovation in, Karlsruhe, de v1.0 - Dipl.-Ing. HTL Peter Machalek, Siemens Transit, Neuhausen am Rheinfall, ch v1.0 - El Ing. Ernst Pfister, Siemens Transit, Neuhausen am Rheinfall, ch v1.0 - Dipl.-Ing. Berthold Radermacher, Verband Deutscher, Köln, de v1.0 - Dr. Friedemann Weik, Hamburger Berater Team GmbH, Hamburg, de v1.0 - - Robin Vettier, ixxi.com, fr v1.3 - Ofer Porat, fr v1.3 - Burt Alexander', sigtec.com - Michelle Etienne, Dryade, Paris fr, v1.3 - Brian Ferris onebusaway.org, us, v1.3 - Manuem Mahne Siemens.com - - Ulf Bjersing, Hogia - Stenungsgrund, se v2.0 - Dipl.-Math Christoph Blendinger, DB, Frankfort, de v2.0 - Dipl.-Kfm. Winfried Bruns, Verband Deutscher, Köln, de v2.0 - Christophe Duquesne, PDG Consultant en systémes, Auriga, fr v2.0 - Gerald Dury, Trapeze Neuhausen am Rhein, ch, fr v2.0 - Michelle Etienne, Dryade, Paris fr v2.0 - Michael Frumin, MTA, us, v2.0 - Nicholas Knowles, Trapeze Limited, London, uk v2.0 - Werner Kohl, Mentz Datenverarbeitung GmbH, München, de v2.0 - Davide Lallouche, RATP, Paris, fr v2.0 - Jeff Maki, us, v2.0 - Daniel Rubli, Trapeze Neuhausen am Rhein, ch, fr v2.0 - Gustav Thiessen BLIC thi@BLIC.DE, de 2.0 v1.0 - Europe - >Drafted for version 1.0 & Version 2.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. -mailto:schemer@siri.org.uk - - 2004-09-29 - - - 2004-10-01 - - - 2005-02-14 - - - 2005-02-20 - - - 2005-05-11 - - - 2007-02-02 - - 2007-04-17 - Name Space changes - - 2008-11-17 - Change to use common 1_2. Add in mussing StopMonitoringMultipelRequest - Rename groups to identify common SIRI elements - - 2009-03-03 - Corrrect cardinality on facility and Service Monitoring Delivery request - - 2011-04-18 - Updated journey, request and other subpackages - see readme - - 2012-03-23 - SIRI Version 2.0 - Model subpackages Refactored to improve modularisation. - [SIRI-LITE] Add authentication Key - See Readme.txt for list of changes - - 2012-05-18 - SIRI Version 2.0 - Correct error in SituationExchangeCapabilitiesReponse include - - 2012-08-01 - SIRI Version 2.0 - Correct delegation elements - - 2014-03-31 - +SIRI v2.0 Comments - - Add terminate subscription notification - - -

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

      -

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

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

      -

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

      -

      SIRI includes common mechanisms and messages for system status management.

      -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/}siri.xsd - [ISO 639-2/B] ENG - Kizoom Software Ltd 16 High Holborn, London WC1V 6BX - - http://www.siri.org.uk/schema/2.0/xsd/siri__common_services.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__estimatedTimetable_service.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__productionTimetable_service.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__stopMonitoring_service.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__vehicleMonitoring_service.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__connectionTimetable_service.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__connectionMonitoring_service.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__generalMessage_service.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__discovery.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__situationExchange_service.xsd - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.0 Version with cumulative fixes - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport. - - CEN TC278 WG3 SG7 - - SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. - Standard -       -       - SIRI Service Interface for Real-time Information relating to Public Transport Operations. - XML Schema with explicit functional services -       - - - - - - - SIRI Service Interface for Real-time Operation. - - - - - - - - - - - - - - SIRI All Requests. - - - - - - - - - - - - Request from Consumer to Producer for immediate delivery of data. Answered with a ServiceDelivery (or a DataReadyRequest) - - - - - - - - - - Requests for service provision. - - - - - - - - - - SIRI Service Request. - - - - - - - - - - SIRI Functional Service Concrete Requests. - - - - - - - - - - - - - - - - - - - Request from Subscriber to Producer for a subscription. Answered with a SubscriptionResponse. - - - - - - - - - - - Type for SIRI Subscription Request. - - - - - - - - - - - - Type for SIRI Functional Service Subscription types. Used for WSDL exchanges. - - - - - - - - SIRI Functional Service Subscription types. For a given SubscriptionRequest, must all be of the same service type. - - - - - - - - - - - - - - - - - - SIRI Service Responses. - - - - - - - - - - - Responses to requests other than deliveries and status information. - - - - - - - - - - - Responses that deliver payload content. - - - - - - - - - - - Response from Producer to Consumer to deliver payload data. Either answers a direct ServiceRequest, or asynchronously satisfies a subscription. May be sent directly in one step, or fetched in response to a DataSupply Request. - - - - - - - - - - Type for SIRI Service Delivery. - - - - - - - - - Default gml coordinate format for eny location elements in response; applies if Coordinates element is used to specify points. May be overridden on individual points. - - - - - - - - Type for SIRI Service Delivery Body.. - - - - - - - Default gml coordinate format for eny location elements in response; applies if Coordinates element is used to specify points. May be overridden on individual points. - - - - - - Elements for SIRI Service Delivery. - - - - - - Whether there is a further delivery message with more current updates that follows this one. Default is 'false'. - - - - - - - - Type for a SIRI SIRI Functional Service Delivery types.Used for WSDL. - - - - - - - - SIRI Functional Service Delivery types. - - - - - - - - - - - Delivery for Stop Event service. - - - - - Delivery for Vehicle Activity Service. - - - - - - Delivery for Connection Protection Fetcher Service. - - - - - Delivery for Connection Protection Fetcher Service. - - - - - Delivery for general Message service. - - - - - - - - - - - - Requests for reference data for use in SIRI Functional Service requests. - - - - - - - - - Responses with reference data for use in SIRI Functional Service requests. - - - - - Responses with the capabilities of an implementation. Answers a CapabilityRequest. - - - - - - - - - - Requests a the current capabilities of the server. Answred with a CpabailitiesResponse. - - - - - Type for Requests for capabilities of the current system. - - - - - - - Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. - - - - - - If request has been proxied by an intermediate aggregating system, tracking information relating to the original requestor. This allows the aggregation to be stateless - - - - - - - - - - - Defines the capabilities of an individual SIRI service request functions. - - - - - - - - - - - - - - - - - - Responses with the capabilities of an implementation. - - - - - Type for the capabilities of an implementation. - - - - - - - - - - - - - Defines the capabilities of an individual SIRI service response functions. - - - - - - - - - - - - - - - -       + + + + + + main schema + e-service developers + + Dipl.-Kfm. Winfried Bruns, Verband Deutscher, Köln, de v1.0 + Mark Cartwright, Centaur Consulting Limited, Guildford, uk v1.0 + Christophe Duquesne, PDG Consultant en systémes, Dryade Guyancourt, fr v1.0 + Stefan Fjällemark, HUR - Hovedstadens, Valby, dk v1.0 + Jonas Jäderberg, Columna, Borlänge, fi v1.0 + Dipl.-Ing. Sven Juergens psitrans juergens@psitrans.de v1.0 + Nicholas Knowles, KIZOOM Limited, London EC4A 1LT, uk v1.0 + Werner Kohl, Mentz Datenverarbeitung GmbH, München,de v1.0 + Peter Miller, ACIS Research and Development, Cambridge CB4 0DL, uk v1.0 + Dr. Martin Siczkowski, West Yorkshire PTE, Leeds, uk v1.0 + Gustav Thiessen BLIC thi@BLIC.DE, de v1.0 + Dr Bartak, bartak@apex-jesenice.cz v1.0 + Dr. Franz-Josef Czuka, Beratungsgesellschaft für, Düsseldorf, de v1.0 + Dr.-Ing. Klaus-Peter Heynert, PSI Transportation GmbH, Berlin, de v1.0 + Jean-Laurant Franchineau, CONNEX-EUROLUM, PARIS, fr v1.0 + Dipl.-Ing. (FH) Rainer Ganninger, init innovation in, Karlsruhe, de v1.0 + Dipl.-Ing. HTL Peter Machalek, Siemens Transit, Neuhausen am Rheinfall, ch v1.0 + El Ing. Ernst Pfister, Siemens Transit, Neuhausen am Rheinfall, ch v1.0 + Dipl.-Ing. Berthold Radermacher, Verband Deutscher, Köln, de v1.0 + Dr. Friedemann Weik, Hamburger Berater Team GmbH, Hamburg, de v1.0 + + Robin Vettier, ixxi.com, fr v1.3 + Ofer Porat, fr v1.3 + Burt Alexander', sigtec.com + Michelle Etienne, Dryade, Paris fr, v1.3 + Brian Ferris onebusaway.org, us, v1.3 + Manuem Mahne Siemens.com + + Ulf Bjersing, Hogia - Stenungsgrund, se v2.0 + Dipl.-Math Christoph Blendinger, DB, Frankfort, de v2.0 + Dipl.-Kfm. Winfried Bruns, Verband Deutscher, Köln, de v2.0 + Christophe Duquesne, PDG Consultant en systémes, Auriga, fr v2.0 + Gerald Dury, Trapeze Neuhausen am Rhein, ch, fr v2.0 + Michelle Etienne, Dryade, Paris fr v2.0 + Michael Frumin, MTA, us, v2.0 + Nicholas Knowles, Trapeze Limited, London, uk v2.0 + Werner Kohl, Mentz Datenverarbeitung GmbH, München, de v2.0 + Davide Lallouche, RATP, Paris, fr v2.0 + Jeff Maki, us, v2.0 + Daniel Rubli, Trapeze Neuhausen am Rhein, ch, fr v2.0 + Gustav Thiessen BLIC thi@BLIC.DE, de 2.0 v1.0 + Europe + >Drafted for version 1.0 & Version 2.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. +mailto:schemer@siri.org.uk + + 2004-09-29 + + + 2004-10-01 + + + 2005-02-14 + + + 2005-02-20 + + + 2005-05-11 + + + 2007-02-02 + + 2007-04-17 + Name Space changes + + 2008-11-17 + Change to use common 1_2. Add in mussing StopMonitoringMultipelRequest + Rename groups to identify common SIRI elements + + 2009-03-03 + Corrrect cardinality on facility and Service Monitoring Delivery request + + 2011-04-18 + Updated journey, request and other subpackages - see readme + + 2012-03-23 + SIRI Version 2.0 + Model subpackages Refactored to improve modularisation. + [SIRI-LITE] Add authentication Key + See Readme.txt for list of changes + + 2012-05-18 + SIRI Version 2.0 + Correct error in SituationExchangeCapabilitiesReponse include + + 2012-08-01 + SIRI Version 2.0 + Correct delegation elements + + 2014-03-31 + +SIRI v2.0 Comments + - Add terminate subscription notification + + +

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

      +

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

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

      +

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

      +

      SIRI includes common mechanisms and messages for system status management.

      +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}siri.xsd + [ISO 639-2/B] ENG + Kizoom Software Ltd 16 High Holborn, London WC1V 6BX + + http://www.siri.org.uk/schema/2.0/xsd/siri__common_services.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__estimatedTimetable_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__productionTimetable_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__stopMonitoring_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__vehicleMonitoring_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__connectionTimetable_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__connectionMonitoring_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__generalMessage_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__discovery.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__situationExchange_service.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG XML and Trident standards.
        • +
      + + Version 2.0 Version with cumulative fixes + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport. + + CEN TC278 WG3 SG7 + + SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. + Standard +       +       + SIRI Service Interface for Real-time Information relating to Public Transport Operations. - XML Schema with explicit functional services +       + + + + + + + SIRI Service Interface for Real-time Operation. + + + + + + + + + + + + + + SIRI All Requests. + + + + + + + + + + + + Request from Consumer to Producer for immediate delivery of data. Answered with a ServiceDelivery (or a DataReadyRequest) + + + + + + + + + + Requests for service provision. + + + + + + + + + + SIRI Service Request. + + + + + + + + + + SIRI Functional Service Concrete Requests. + + + + + + + + + + + + + + + + + + + Request from Subscriber to Producer for a subscription. Answered with a SubscriptionResponse. + + + + + + + + + + + Type for SIRI Subscription Request. + + + + + + + + + + + + Type for SIRI Functional Service Subscription types. Used for WSDL exchanges. + + + + + + + + SIRI Functional Service Subscription types. For a given SubscriptionRequest, must all be of the same service type. + + + + + + + + + + + + + + + + + + SIRI Service Responses. + + + + + + + + + + + Responses to requests other than deliveries and status information. + + + + + + + + + + + Responses that deliver payload content. + + + + + + + + + + + Response from Producer to Consumer to deliver payload data. Either answers a direct ServiceRequest, or asynchronously satisfies a subscription. May be sent directly in one step, or fetched in response to a DataSupply Request. + + + + + + + + + + Type for SIRI Service Delivery. + + + + + + + + + Default gml coordinate format for eny location elements in response; applies if Coordinates element is used to specify points. May be overridden on individual points. + + + + + + + + Type for SIRI Service Delivery Body.. + + + + + + + Default gml coordinate format for eny location elements in response; applies if Coordinates element is used to specify points. May be overridden on individual points. + + + + + + Elements for SIRI Service Delivery. + + + + + + Whether there is a further delivery message with more current updates that follows this one. Default is 'false'. + + + + + + + + Type for a SIRI SIRI Functional Service Delivery types.Used for WSDL. + + + + + + + + SIRI Functional Service Delivery types. + + + + + + + + + + + Delivery for Stop Event service. + + + + + Delivery for Vehicle Activity Service. + + + + + + Delivery for Connection Protection Fetcher Service. + + + + + Delivery for Connection Protection Fetcher Service. + + + + + Delivery for general Message service. + + + + + + + + + + + + Requests for reference data for use in SIRI Functional Service requests. + + + + + + + + + Responses with reference data for use in SIRI Functional Service requests. + + + + + Responses with the capabilities of an implementation. Answers a CapabilityRequest. + + + + + + + + + + Requests a the current capabilities of the server. Answred with a CpabailitiesResponse. + + + + + Type for Requests for capabilities of the current system. + + + + + + + Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. + + + + + + If request has been proxied by an intermediate aggregating system, tracking information relating to the original requestor. This allows the aggregation to be stateless + + + + + + + + + + + Defines the capabilities of an individual SIRI service request functions. + + + + + + + + + + + + + + + + + + Responses with the capabilities of an implementation. + + + + + Type for the capabilities of an implementation. + + + + + + + + + + + + + Defines the capabilities of an individual SIRI service response functions. + + + + + + + + + + + + + + + +       diff --git a/xsd/siri/siri_all_framework.xsd b/xsd/siri/siri_all_framework.xsd index dfa55d89..f1b3f959 100644 --- a/xsd/siri/siri_all_framework.xsd +++ b/xsd/siri/siri_all_framework.xsd @@ -1,12 +1,12 @@ - - - - - - - - - + + + + + + + + + diff --git a/xsd/siri/siri_base.xsd b/xsd/siri/siri_base.xsd index 8f002003..823f95fb 100644 --- a/xsd/siri/siri_base.xsd +++ b/xsd/siri/siri_base.xsd @@ -1,315 +1,315 @@ - - - - - - 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 Limited, 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 - - 2012-06-17 - - - - 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 that 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/schema/2.0/xsd/}siri.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri__common_services.xsd - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport. - - CEN TC278 WG3 SG7 - - SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations Generic base schema. - Standard -       -       - SIRI Common Request Fra,mework -       - - - - - - - - - - - - - - - SIRI Requests. - - - - - - - - - - - Requests for service provision. - - - - - - - - - - - Request from Consumer to Producer for immediate delivery of data. Answered with a ServiceDelivery (or a DataReadyRequest) - - - - - - - - - - - - - - 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. - - - - - - - - - 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. - - - - - - Elements 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. - - - - - - - - - - -       + + + + + + 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 Limited, 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 + + 2012-06-17 + + + + 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 that 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/schema/2.0/xsd/}siri.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri__common_services.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG XML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport. + + CEN TC278 WG3 SG7 + + SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations Generic base schema. + Standard +       +       + SIRI Common Request Fra,mework +       + + + + + + + + + + + + + + + SIRI Requests. + + + + + + + + + + + Requests for service provision. + + + + + + + + + + + Request from Consumer to Producer for immediate delivery of data. Answered with a ServiceDelivery (or a DataReadyRequest) + + + + + + + + + + + + + + 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. + + + + + + + + + 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. + + + + + + Elements 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/xsd/siri/siri_common_services.xsd b/xsd/siri/siri_common_services.xsd index e04f0893..254c18cf 100644 --- a/xsd/siri/siri_common_services.xsd +++ b/xsd/siri/siri_common_services.xsd @@ -1,900 +1,900 @@ - - - - - - main schema - e-service developers - CEN TC278 WG3 SG7 Team - Europe - First drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2004-09-29 - - - 2005-02-14 - - - 2005-02-20 - - - 2005-05-11 - - 2007-04-17 - - Name Space changes - - 2008-10-09 - -- Add Subscriber ref to TermninateSubscription Request - - 2008-11-17 - -- Revise for substitution groups and move down to siri subdirectory - - 2012-03-23 - +SIRI v2.0 - - Add DataReady to Check Status - - Add DistanceUnits and VelocityUnits to ServiceRequestContext - - [FR] Add Extensions tag to Terminate SubscriptionRequest - - 2014-03-31 - +SIRI v2.0 Comments - - Add terminate subscription notification - - 2014-06-23 - +SIRI v2.0 Comments - - Revise terminate subscription erroc condition to be consistent with other services - - -

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

      -

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

      -

      It contains the following request

      -
        -
      • GS: Terminate Subscription Resquest
        • -
      • GS: Terminate Subscription Response
        • -
      • GS: Subscription Response
        • -
      • GS: Data Ready Notification
        • -
      • GS: Data Ready Acknowledgement
        • -
      • GS: Data Supply Request
        • -
      • GS: Data Received Response
        • -
      • GS: Check Status Request
        • -
      • GS: Check Status Response
        • -
      • GS: Heartbeat Request
        • -
      -

      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/schema/2.0/xsd/siri/}siri_common_services.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI XML schema. Service Interface for Real-time Information. Common Requests - Standard -       -       - SIRI Framework - Common Requests. -       - - - - - - - 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. - - - - - - - - - - - Address elements 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. - - - - - - - Address elements 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 is ' 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 languages 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. - - - - - - Units for Distance Type. Default is metres. +SIRI v2.0 - - - - - Units for Distance Type. Default is metres per second. +SIRI v2.0 - - - - - - - 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 a subscription or subscriptions. - - - - - - - - If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 - - - - - - - - - - - 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. - - - - - - - - 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. - - - - - - - - - - - - Type for Status of termination response. - - - - - - - - - Description of any error or warning condition. - - - - - - - - - - - - Text description of error. - - - - - - - - - - - Notification from Subscriber to Subscription Manager to terminate a subscription. - - - - - Type for Notification to terminate a subscription or subscriptions. - - - - - - - - Text description providing additional information about the reason for the subscription termination. - - - - - - - - - - - Responses that infrom about the service status. - - - - - - - - Type for Response Status. - - - - - - - - - - Description of any error or warning condition. - - - - - - - - - - Contains infromation about the processing of a an individual service subscription - either success info or an error condition. (VDV Acknowledgement). - - - - - - 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. - - - - - - - - - General requests for fetched data delivery. - - - - - - - - - - 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. - - - - - - - - - - - - - - - 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. - - - - - - - - - - - - Specifies content to be included in data supply. - - - - - Reference to a 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. - - - - - - - - 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. - - - - - - - - - - - - Elements identifying data Consumer, i.e. requestor, if synchronous delivery or subscriber if asynchronous. - - - - - - Reference to an arbitrary unique reference associated with the request which gave rise to this response. - - - - - - - - Request from Consumer to Producer to check whether services is working. Answers a CheckStatusRequest. - - - - - Type for check status request. - - - - - - - - - Version number of request. - - - - - - - - - Data received AcknowledgementService Status Check Request content. - - - - - - Whether data delivery is ready to be fetched SIRI v 2.0 - - - - - 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. - - - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + First drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2004-09-29 + + + 2005-02-14 + + + 2005-02-20 + + + 2005-05-11 + + 2007-04-17 + - Name Space changes + + 2008-10-09 + -- Add Subscriber ref to TermninateSubscription Request + + 2008-11-17 + -- Revise for substitution groups and move down to siri subdirectory + + 2012-03-23 + +SIRI v2.0 + - Add DataReady to Check Status + - Add DistanceUnits and VelocityUnits to ServiceRequestContext + - [FR] Add Extensions tag to Terminate SubscriptionRequest + + 2014-03-31 + +SIRI v2.0 Comments + - Add terminate subscription notification + + 2014-06-23 + +SIRI v2.0 Comments + - Revise terminate subscription erroc condition to be consistent with other services + + +

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

      +

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

      +

      It contains the following request

      +
        +
      • GS: Terminate Subscription Resquest
        • +
      • GS: Terminate Subscription Response
        • +
      • GS: Subscription Response
        • +
      • GS: Data Ready Notification
        • +
      • GS: Data Ready Acknowledgement
        • +
      • GS: Data Supply Request
        • +
      • GS: Data Received Response
        • +
      • GS: Check Status Request
        • +
      • GS: Check Status Response
        • +
      • GS: Heartbeat Request
        • +
      +

      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/schema/2.0/xsd/siri/}siri_common_services.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG XML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI XML schema. Service Interface for Real-time Information. Common Requests + Standard +       +       + SIRI Framework - Common Requests. +       + + + + + + + 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. + + + + + + + + + + + Address elements 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. + + + + + + + Address elements 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 is ' 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 languages 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. + + + + + + Units for Distance Type. Default is metres. +SIRI v2.0 + + + + + Units for Distance Type. Default is metres per second. +SIRI v2.0 + + + + + + + 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 a subscription or subscriptions. + + + + + + + + If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 + + + + + + + + + + + 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. + + + + + + + + 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. + + + + + + + + + + + + Type for Status of termination response. + + + + + + + + + Description of any error or warning condition. + + + + + + + + + + + + Text description of error. + + + + + + + + + + + Notification from Subscriber to Subscription Manager to terminate a subscription. + + + + + Type for Notification to terminate a subscription or subscriptions. + + + + + + + + Text description providing additional information about the reason for the subscription termination. + + + + + + + + + + + Responses that infrom about the service status. + + + + + + + + Type for Response Status. + + + + + + + + + + Description of any error or warning condition. + + + + + + + + + + Contains infromation about the processing of a an individual service subscription - either success info or an error condition. (VDV Acknowledgement). + + + + + + 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. + + + + + + + + + General requests for fetched data delivery. + + + + + + + + + + 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. + + + + + + + + + + + + + + + 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. + + + + + + + + + + + + Specifies content to be included in data supply. + + + + + Reference to a 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. + + + + + + + + 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. + + + + + + + + + + + + Elements identifying data Consumer, i.e. requestor, if synchronous delivery or subscriber if asynchronous. + + + + + + Reference to an arbitrary unique reference associated with the request which gave rise to this response. + + + + + + + + Request from Consumer to Producer to check whether services is working. Answers a CheckStatusRequest. + + + + + Type for check status request. + + + + + + + + + Version number of request. + + + + + + + + + Data received AcknowledgementService Status Check Request content. + + + + + + Whether data delivery is ready to be fetched SIRI v 2.0 + + + + + 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/xsd/siri/siri_request_errorConditions.xsd b/xsd/siri/siri_request_errorConditions.xsd index c1505496..555f32f6 100644 --- a/xsd/siri/siri_request_errorConditions.xsd +++ b/xsd/siri/siri_request_errorConditions.xsd @@ -1,590 +1,590 @@ - - - - - - - - - main schema - e-service developers - CEN TC278 WG3 SG7 Team - Europe - First drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2012-03-24 - - - - 2009-03-31 - - - - 2011-04-18 - - - - 2012-03-23 - - - -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri/}siri_requests_errorConditions.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri_uility/siri_types.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_uility/siri_participant.xsd - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIGXML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI XML schema. Common Request Error Conditions - Standard -       -       - SIRI Framework Error COnditions. -       - - - - Description of error or warning condition associated with response. - - - - - Type for RequestErrorCondition. - - - - - - - - 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. - - - - - - - - Element fror an erroc condition (for use in WSDL.) - - - - - Type for Standard ErrorConditions for Service request. - - - - - - - - - Text description of error. - - - - - - - Type for Description of an error. - - - - - - - - - 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. - - - - - - Error code number associated with 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. - - - - - - - - - - Errors that may arise in the execution of a delegated distribution request. +SIRI v2.0 - - - - - - Error: Recipient for a message to be distributed is unknown. I.e. delegatior is found, but +SIRI v2.0 - - - - - - - - - - - Error:Recipient of a message to be distributed is not available. +SIRI v2.0 - - - - - Type for Error: UnapprovedKey +SIRI v2.0 - - - - - - - User key. - - - - - - - - - - Error: Recipient for a message to be distributed is unknown. +SIRI v2.0 - - - - - Type for Error: Unknown Participant. +SIRI v2.0 - - - - - - - Reference to Participant who is unknown. + SIRI v2.0 - - - - - - - - - - Error: Recipient for a message to be distributed is unknown. +SIRI v2.0 - - - - - Type for Error: Unknown Endpoint +SIRI v2.0 - - - - - - - Endpoint that is noit known. + SIRI v2.0 - - - - - - - - - - Error:Endpoint to which a message is to be distributed did not allow access by the cloient. +SIRI v2.0 - - - - - Type for Error: EndpointDeniedAccess +SIRI v2.0 - - - - - - - Endpoint that was denied access + SIRI v2.0 - - - - - - - - - - Error:Recipient of a message to be distributed is not available. +SIRI v2.0 - - - - - Type for Error: EndpointNotAvailable +SIRI v2.0 - - - - - - - Endpoint that is noit available. + SIRI v2.0 - - - - - - - - - - - Errors that may arise in the execution of a request. - - - - - - - - - Error: Data period or subscription period is outside of period covered by service. +SIRI v2.0. - - - - - - - Error: Request contained extensions that were not supported by the producer. A response has been provided but some or all extensions have been ignored. +SIRI v2.0. - - - - - - - - - - Error: Functional service is not available to use (but it is still capable of giving this response). - - - - - Type for Service Not Available error. - - - - - - - Expected time fro reavailability of servcie. +SIRI v2.0 - - - - - - - - - - Error: Service does not support the 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:Access Not Allowed. - - - - - - - - - Error: Valid request was made but service does not hold any data for the requested topic. expression. - - - - - Type for Error: No Info for Topic - - - - - - - - - Error: Request contains references to identifiers that are not known. +SIRI v2.0. - - - - - Type for InvalidDataReferencesError:. +SIRI v2.0. - - - - - - - Invalid reference values encoountered. - - - - - - - - - - Error: Request contained parameters that were not supported by the producer. A response has been provided but some parameters have been ignored. +SIRI v2.0. - - - - - Type for Parameters Ignored Error:. +SIRI v2.0. - - - - - - - Name of the unsupported parameter. - - - - - - - - - - Error: Request contained extensions that were not supported by the producer. A response has been provided but some or all extensions have been ignored.. +SIRI v2.0. - - - - - Type for Unknown Extensions Error:. +SIRI v2.0. - - - - - - - Name of the unknown encountered extensions. - - - - - - - - - - Error: Valid request was made but request would exceed the permitted resource usage of the client. - - - - - Type for error. AllowedResourceUsageExceeded. - - - - - - - - - - - Error: Subscriber not found. - - - - - Type for Error: Subscriber not found. - - - - - - - Id of capabiliuty that is noit supported. + SIRI v2.0 - - - - - - - - - - - Error: Subscription not found. - - - - - Type for Error: Subscription not found. - - - - - - - Ubscription code that could not be found. + SIRI v2.0 - - - - - - - - - - Error: Error type other than the well defined codes. - - - - - Type for error. - - - - - - -       + + + + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + First drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2012-03-24 + + + + 2009-03-31 + + + + 2011-04-18 + + + + 2012-03-23 + + + +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/siri/}siri_requests_errorConditions.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri_uility/siri_types.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_uility/siri_participant.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIGXML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI XML schema. Common Request Error Conditions + Standard +       +       + SIRI Framework Error COnditions. +       + + + + Description of error or warning condition associated with response. + + + + + Type for RequestErrorCondition. + + + + + + + + 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. + + + + + + + + Element fror an erroc condition (for use in WSDL.) + + + + + Type for Standard ErrorConditions for Service request. + + + + + + + + + Text description of error. + + + + + + + Type for Description of an error. + + + + + + + + + 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. + + + + + + Error code number associated with 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. + + + + + + + + + + Errors that may arise in the execution of a delegated distribution request. +SIRI v2.0 + + + + + + Error: Recipient for a message to be distributed is unknown. I.e. delegatior is found, but +SIRI v2.0 + + + + + + + + + + + Error:Recipient of a message to be distributed is not available. +SIRI v2.0 + + + + + Type for Error: UnapprovedKey +SIRI v2.0 + + + + + + + User key. + + + + + + + + + + Error: Recipient for a message to be distributed is unknown. +SIRI v2.0 + + + + + Type for Error: Unknown Participant. +SIRI v2.0 + + + + + + + Reference to Participant who is unknown. + SIRI v2.0 + + + + + + + + + + Error: Recipient for a message to be distributed is unknown. +SIRI v2.0 + + + + + Type for Error: Unknown Endpoint +SIRI v2.0 + + + + + + + Endpoint that is noit known. + SIRI v2.0 + + + + + + + + + + Error:Endpoint to which a message is to be distributed did not allow access by the cloient. +SIRI v2.0 + + + + + Type for Error: EndpointDeniedAccess +SIRI v2.0 + + + + + + + Endpoint that was denied access + SIRI v2.0 + + + + + + + + + + Error:Recipient of a message to be distributed is not available. +SIRI v2.0 + + + + + Type for Error: EndpointNotAvailable +SIRI v2.0 + + + + + + + Endpoint that is noit available. + SIRI v2.0 + + + + + + + + + + + Errors that may arise in the execution of a request. + + + + + + + + + Error: Data period or subscription period is outside of period covered by service. +SIRI v2.0. + + + + + + + Error: Request contained extensions that were not supported by the producer. A response has been provided but some or all extensions have been ignored. +SIRI v2.0. + + + + + + + + + + Error: Functional service is not available to use (but it is still capable of giving this response). + + + + + Type for Service Not Available error. + + + + + + + Expected time fro reavailability of servcie. +SIRI v2.0 + + + + + + + + + + Error: Service does not support the 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:Access Not Allowed. + + + + + + + + + Error: Valid request was made but service does not hold any data for the requested topic. expression. + + + + + Type for Error: No Info for Topic + + + + + + + + + Error: Request contains references to identifiers that are not known. +SIRI v2.0. + + + + + Type for InvalidDataReferencesError:. +SIRI v2.0. + + + + + + + Invalid reference values encoountered. + + + + + + + + + + Error: Request contained parameters that were not supported by the producer. A response has been provided but some parameters have been ignored. +SIRI v2.0. + + + + + Type for Parameters Ignored Error:. +SIRI v2.0. + + + + + + + Name of the unsupported parameter. + + + + + + + + + + Error: Request contained extensions that were not supported by the producer. A response has been provided but some or all extensions have been ignored.. +SIRI v2.0. + + + + + Type for Unknown Extensions Error:. +SIRI v2.0. + + + + + + + Name of the unknown encountered extensions. + + + + + + + + + + Error: Valid request was made but request would exceed the permitted resource usage of the client. + + + + + Type for error. AllowedResourceUsageExceeded. + + + + + + + + + + + Error: Subscriber not found. + + + + + Type for Error: Subscriber not found. + + + + + + + Id of capabiliuty that is noit supported. + SIRI v2.0 + + + + + + + + + + + Error: Subscription not found. + + + + + Type for Error: Subscription not found. + + + + + + + Ubscription code that could not be found. + SIRI v2.0 + + + + + + + + + + Error: Error type other than the well defined codes. + + + + + Type for error. + + + + + + +       diff --git a/xsd/siri/siri_request_support.xsd b/xsd/siri/siri_request_support.xsd index 53093910..ca07a583 100644 --- a/xsd/siri/siri_request_support.xsd +++ b/xsd/siri/siri_request_support.xsd @@ -1,210 +1,210 @@ - - - - - - - main schema - e-service developers - CEN TC278 WG3 SG7 Team - Europe - First drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2012-03-29 - - - 2012-03-23 - - - -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri/}siri_request_support.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the SIRI 1.0 standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI XML schema. Common Request identifier types - Standard -       -       - SIRI Common Framework basic identifier types. -       - - - - - Unique identifier of a message within SIRI functional service type and participant. - - - - - - - - Type for reference to a message. - - - - - - - - Type for unique identifier of Subscription within Participant. - - - - - - - - Type for reference to a subscription. - - - - - - - - Type for unique identifier of Subscription filter within Participant. - - - - - - - - Type for unique identifier of Subscription filter within Participant. - - - - - - - - - Timestamp on request. - - - - - Reference to a requestor - Participant Code. - - - - - Type for a endpoint. - - - - - - Time individual response element was created. - - - - - - Type for identifier of an Item. A transient reference for efficient handling of events. - - - - - - Type for reference to an Item. - - - - - - - - - Whether additional translations of text names are to be included in elements. If 'false', then only one element should be returned. Default is 'false'. -Where multiple values are returned The first element returned will be used as the default value. - - - - - Whether SERVICE JOURNEY INTERCHANGE data is to be transmitted or not. Default is 'true'. +SIRI v2.1 - - - - - Whether JOURNEY RELATION data is to be transmitted or not. Default is 'true'. +SIRI v2.1 - - - - - Whether TRAIN (ELEMENT), COMPOUND TRAIN and TRAIN STOP ASSIGNMENT data is to be transmitted or not. Default is 'true'. +SIRI v2.1 - - - - - - Type for capability ref. - - - - - - - - Type for capability code. - - - - - - - Enumeration of communications transport method usage. - - - - - - - - - - - - - Enumeration of compression usage. - - - - - - - -       + + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + First drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2012-03-29 + + + 2012-03-23 + + + +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/siri/}siri_request_support.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the SIRI 1.0 standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI XML schema. Common Request identifier types + Standard +       +       + SIRI Common Framework basic identifier types. +       + + + + + Unique identifier of a message within SIRI functional service type and participant. + + + + + + + + Type for reference to a message. + + + + + + + + Type for unique identifier of Subscription within Participant. + + + + + + + + Type for reference to a subscription. + + + + + + + + Type for unique identifier of Subscription filter within Participant. + + + + + + + + Type for unique identifier of Subscription filter within Participant. + + + + + + + + + Timestamp on request. + + + + + Reference to a requestor - Participant Code. + + + + + Type for a endpoint. + + + + + + Time individual response element was created. + + + + + + Type for identifier of an Item. A transient reference for efficient handling of events. + + + + + + Type for reference to an Item. + + + + + + + + + Whether additional translations of text names are to be included in elements. If 'false', then only one element should be returned. Default is 'false'. +Where multiple values are returned The first element returned will be used as the default value. + + + + + Whether SERVICE JOURNEY INTERCHANGE data is to be transmitted or not. Default is 'true'. +SIRI v2.1 + + + + + Whether JOURNEY RELATION data is to be transmitted or not. Default is 'true'. +SIRI v2.1 + + + + + Whether TRAIN (ELEMENT), COMPOUND TRAIN and TRAIN STOP ASSIGNMENT data is to be transmitted or not. Default is 'true'. +SIRI v2.1 + + + + + + Type for capability ref. + + + + + + + + Type for capability code. + + + + + + + Enumeration of communications transport method usage. + + + + + + + + + + + + + Enumeration of compression usage. + + + + + + + +       diff --git a/xsd/siri/siri_requests.xsd b/xsd/siri/siri_requests.xsd index 023ba1f7..3c72224c 100644 --- a/xsd/siri/siri_requests.xsd +++ b/xsd/siri/siri_requests.xsd @@ -1,1072 +1,1072 @@ - - - - - - main schema - e-service developers - CEN TC278 WG3 SG7 Team - Europe - First drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 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 - - - - 2012-03-23 - - - - 2012-06-17 - - - - 2013-02-11 - - - -

      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/schema/2.0/xsd/siri/}siri_requests.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIGXML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry transport, -Roads and road transport - CEN TC278 WG3 SG7 - - SIRI XML schema. Common Request elements. - Standard -       -       - SIRI Common Request Framework. -       - - - - - - - - - Subsititutable type for a timestamped SIRI request. - - - - - Type for General SIRI Request. - - - - - - - - - Subsititutable type for an authenticated request Authenticated. - - - - - Type for Authticated SIRI Request. - - - - - - - - - - Elemenst for authecticiation. +SIRI v2.0 - - - - - Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . +SIRI v2.0 - - - - - Authentication key for request. May be used to authenticate requests from a particular account. +SIRI v2.0 - - - - - - - - Type for General SIRI Request. - - - - - - - - If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 - - - - - - - - - Elements relating to system that sent request. - - - - - 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 in subsequent interactions. - - - - - - - If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. - - - - - Address of original Consumer, i.e. requesting system to which delegating response is to be returned. +SIRI 2.0 - - - - - Identifier of delegating system that originated message. +SIRI 2.0 - - - - - - - - Subsititutable type for a SIRI request with requestor dteials tracked. - - - - - - Substitutable 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. - - - - - By using this element, the subscriber asks the data provider for an extension of the InitialTerminationTime of the subscription. -If SubscriptionRenewal is omitted, this request is to be treated as a re-subscription and therefore all data corresponding to the SubscriptionRequest must be sent in the initial response (or a portion of the data if MoreData is set to 'true'). +SIRI v2.1 - - - - - - - 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. Specific 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. - - - - - - - - If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 - - - - - - - - - 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. - - - - - - - - - - - If request has been proxied by an intermediate aggregating system, tracking information relating to the original requestor. This allows the aggregation to be stateless. - - - - - - - - - - - Common defaults. - - - - - Default language for text elements. - - - - - - - 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. - - - - - Reference to a Subscription 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. - - - - - Reference to a service subscription: unique within Service and Subscriber. - - - - - - - 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. - - - - - - - Whether the request was processed successfully or not. Default is 'true'. - - - - - - 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. - - - - - - - - If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 - - - - - - - - - Unique reference to this 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. - - - - - - - - If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 - - - - - - - - - - - Type for Unique reference to request to the producer. May be used to reference request in subsequent interactions. Used for WSDL. - - - - - - - - If request has been proxied by an intermediate aggregating system, tracking information relating to the original requestor. This allows the aggregation to be stateless. - - - - - - - - - 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 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. - - - - - - - - If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 - - - - - - - - - Unique reference to reponse from producer. May be used to reference request in subsequent interactions. - - - - - Unique identifier of Producer - Participant reference. - - - - - Endpoint Address to which acknowledgements to confirm delivery 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 an Activity. - - - - - Time at which data was recorded. - - - - - - - Type for an Activity that can be referenced. - - - - - - - Identifier of item. - - - - - - - - - Type for an Activity that can be referenced. - - - - - - - Identifier of item. - - - - - - - - - Type for an Activity that references a previous Activity. - - - - - - - Reference to an Activity Element of a delivery. - - - - - - - - - Type for an Activity that references a previous Activity. - - - - - - - Reference to an Activity Element of a delivery. - - - - - - - - - - - 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. - - - - - - - - If request has been proxied by an intermediate aggregating system, tracking information relating to the original requestor. This allows the aggregation to be stateless. - - - - - - - - - - - - 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 service supports Publish Subscribe Interaction. Default is 'true'. - - - - - - - - Delivery capabilities. - - - - - - Whether the service supports Direct delivery. - - - - - Whether the service 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. Default is ' false'. - - - - - Whether the service supports Delivery confirm. - - - - - Whether the 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. - - - - - Whether producer can provide multiple translations of NL text elements +SIRI 2.0 - - - - - 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 is ' true'. - - - - - Whether change threshold can be specified for updates. Default is 'true'. - - - - - - - - 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'. - - - - - - - - Abstract Discovery request. - - - - - Requests for stop reference data for use in service requests. - - - - - - - - - - - - Abstract type for a discovery delivery. - - - - - Abstract supertype fro discovery responses. - - - - - - - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + First drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 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 + + + + 2012-03-23 + + + + 2012-06-17 + + + + 2013-02-11 + + + +

      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/schema/2.0/xsd/siri/}siri_requests.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIGXML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry transport, +Roads and road transport + CEN TC278 WG3 SG7 + + SIRI XML schema. Common Request elements. + Standard +       +       + SIRI Common Request Framework. +       + + + + + + + + + Subsititutable type for a timestamped SIRI request. + + + + + Type for General SIRI Request. + + + + + + + + + Subsititutable type for an authenticated request Authenticated. + + + + + Type for Authticated SIRI Request. + + + + + + + + + + Elemenst for authecticiation. +SIRI v2.0 + + + + + Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . +SIRI v2.0 + + + + + Authentication key for request. May be used to authenticate requests from a particular account. +SIRI v2.0 + + + + + + + + Type for General SIRI Request. + + + + + + + + If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 + + + + + + + + + Elements relating to system that sent request. + + + + + 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 in subsequent interactions. + + + + + + + If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. + + + + + Address of original Consumer, i.e. requesting system to which delegating response is to be returned. +SIRI 2.0 + + + + + Identifier of delegating system that originated message. +SIRI 2.0 + + + + + + + + Subsititutable type for a SIRI request with requestor dteials tracked. + + + + + + Substitutable 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. + + + + + By using this element, the subscriber asks the data provider for an extension of the InitialTerminationTime of the subscription. +If SubscriptionRenewal is omitted, this request is to be treated as a re-subscription and therefore all data corresponding to the SubscriptionRequest must be sent in the initial response (or a portion of the data if MoreData is set to 'true'). +SIRI v2.1 + + + + + + + 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. Specific 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. + + + + + + + + If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 + + + + + + + + + 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. + + + + + + + + + + + If request has been proxied by an intermediate aggregating system, tracking information relating to the original requestor. This allows the aggregation to be stateless. + + + + + + + + + + + Common defaults. + + + + + Default language for text elements. + + + + + + + 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. + + + + + Reference to a Subscription 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. + + + + + Reference to a service subscription: unique within Service and Subscriber. + + + + + + + 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. + + + + + + + Whether the request was processed successfully or not. Default is 'true'. + + + + + + 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. + + + + + + + + If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 + + + + + + + + + Unique reference to this 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. + + + + + + + + If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 + + + + + + + + + + + Type for Unique reference to request to the producer. May be used to reference request in subsequent interactions. Used for WSDL. + + + + + + + + If request has been proxied by an intermediate aggregating system, tracking information relating to the original requestor. This allows the aggregation to be stateless. + + + + + + + + + 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 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. + + + + + + + + If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 + + + + + + + + + Unique reference to reponse from producer. May be used to reference request in subsequent interactions. + + + + + Unique identifier of Producer - Participant reference. + + + + + Endpoint Address to which acknowledgements to confirm delivery 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 an Activity. + + + + + Time at which data was recorded. + + + + + + + Type for an Activity that can be referenced. + + + + + + + Identifier of item. + + + + + + + + + Type for an Activity that can be referenced. + + + + + + + Identifier of item. + + + + + + + + + Type for an Activity that references a previous Activity. + + + + + + + Reference to an Activity Element of a delivery. + + + + + + + + + Type for an Activity that references a previous Activity. + + + + + + + Reference to an Activity Element of a delivery. + + + + + + + + + + + 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. + + + + + + + + If request has been proxied by an intermediate aggregating system, tracking information relating to the original requestor. This allows the aggregation to be stateless. + + + + + + + + + + + + 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 service supports Publish Subscribe Interaction. Default is 'true'. + + + + + + + + Delivery capabilities. + + + + + + Whether the service supports Direct delivery. + + + + + Whether the service 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. Default is ' false'. + + + + + Whether the service supports Delivery confirm. + + + + + Whether the 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. + + + + + Whether producer can provide multiple translations of NL text elements +SIRI 2.0 + + + + + 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 is ' true'. + + + + + Whether change threshold can be specified for updates. Default is 'true'. + + + + + + + + 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'. + + + + + + + + Abstract Discovery request. + + + + + Requests for stop reference data for use in service requests. + + + + + + + + + + + + Abstract type for a discovery delivery. + + + + + Abstract supertype fro discovery responses. + + + + + + + + + +       diff --git a/xsd/siriSg.xsd b/xsd/siriSg.xsd index 3e8933a2..310ef35c 100644 --- a/xsd/siriSg.xsd +++ b/xsd/siriSg.xsd @@ -1,149 +1,149 @@ - - - - - - main schema - e-service developers - - Dipl.-Kfm. Winfried Bruns, Verband Deutscher, Köln, de v1.0 - Mark Cartwright, Centaur Consulting Limited, Guildford, uk v1.0 - Christophe Duquesne, PDG Consultant en systémes, Dryade Guyancourt, fr v1.0 - Stefan Fjällemark, HUR - Hovedstadens, Valby, dk v1.0 - Jonas Jäderberg, Columna, Borlänge, fi v1.0 - Dipl.-Ing. Sven Juergens psitrans juergens@psitrans.de v1.0 - Nicholas Knowles, KIZOOM Limited, London EC4A 1LT, uk v1.0 - Werner Kohl, Mentz Datenverarbeitung GmbH, München,de v1.0 - Peter Miller, ACIS Research and Development, Cambridge CB4 0DL, uk v1.0 - Dr. Martin Siczkowski, West Yorkshire PTE, Leeds, uk v1.0 - Gustav Thiessen BLIC thi@BLIC.DE, de v1.0 - Dr Bartak, bartak@apex-jesenice.cz v1.0 - Dr. Franz-Josef Czuka, Beratungsgesellschaft für, Düsseldorf, de v1.0 - Dr.-Ing. Klaus-Peter Heynert, PSI Transportation GmbH, Berlin, de v1.0 - Jean-Laurant Franchineau, CONNEX-EUROLUM, PARIS, fr v1.0 - Dipl.-Ing. (FH) Rainer Ganninger, init innovation in, Karlsruhe, de v1.0 - Dipl.-Ing. HTL Peter Machalek, Siemens Transit, Neuhausen am Rheinfall, ch v1.0 - El Ing. Ernst Pfister, Siemens Transit, Neuhausen am Rheinfall, ch v1.0 - Dipl.-Ing. Berthold Radermacher, Verband Deutscher, Köln, de v1.0 - Dr. Friedemann Weik, Hamburger Berater Team GmbH, Hamburg, de v1.0 - - Robin Vettier, ixxi.com, fr v1.3 - Ofer Porat, fr v1.3 - Burt Alexander', sigtec.com - Michelle Etienne, Dryade, Paris fr, v1.3 - Brian Ferris onebusaway.org, us, v1.3 - Manuem Mahne Siemens.com - - Ulf Bjersing, Hogia - Stenungsgrund, se v2.0 - Dipl.-Math Christoph Blendinger, DB, Frankfort, de v2.0 - Dipl.-Kfm. Winfried Bruns, Verband Deutscher, Köln, de v2.0 - Christophe Duquesne, PDG Consultant en systémes, Auriga, fr v2.0 - Gerald Dury, Trapeze Neuhausen am Rhein, ch, fr v2.0 - Michelle Etienne, Dryade, Paris fr v2.0 - Michael Frumin, MTA, us, v2.0 - Nicholas Knowles, Trapeze Limited, London, uk v2.0 - Werner Kohl, Mentz Datenverarbeitung GmbH, München, de v2.0 - Davide Lallouche, RATP, Paris, fr v2.0 - Jeff Makkie, us, v2.0 - Daniel Rubli, Trapeze Neuhausen am Rhein, ch, fr v2.0 - Gustav Thiessen BLIC thi@BLIC.DE, de 2.0 v1.0 - Jeff Maki, openplans, us, v2.0 - Europe - >Drafted for version 1.0 & Version 2.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2008-11-17 - - - - 2008-04-18 - - - - 2009-03-30 - - - - 2011-04-18 - - - - 2012-03-23 - - - -

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

      -

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

      -

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

      -

      SIRI includes common mechanisms and messages for system status management.

      -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/}siriSg.xsd - [ISO 639-2/B] ENG - Kizoom Software Ltd 16 High Holborn, London WC1V 6BX - - http://www.siri.org.uk/schema/2.0/xsd/siri__base.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__allFunctionalServices.xsd - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      • Derived from the SIRI Version 1.0
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport. - - CEN TC278 WG3 SG7 - - SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Generic Substitution groups version - Standard -       -       - SIRI Service Interface for Real-time Information relating to Public Transport Operations. XML Schema with loosely coupled functional services, -       - - - - - - - - - - - Service Interface for Real-time Operation. - - - - - - - - - - - -       + + + + + + main schema + e-service developers + + Dipl.-Kfm. Winfried Bruns, Verband Deutscher, Köln, de v1.0 + Mark Cartwright, Centaur Consulting Limited, Guildford, uk v1.0 + Christophe Duquesne, PDG Consultant en systémes, Dryade Guyancourt, fr v1.0 + Stefan Fjällemark, HUR - Hovedstadens, Valby, dk v1.0 + Jonas Jäderberg, Columna, Borlänge, fi v1.0 + Dipl.-Ing. Sven Juergens psitrans juergens@psitrans.de v1.0 + Nicholas Knowles, KIZOOM Limited, London EC4A 1LT, uk v1.0 + Werner Kohl, Mentz Datenverarbeitung GmbH, München,de v1.0 + Peter Miller, ACIS Research and Development, Cambridge CB4 0DL, uk v1.0 + Dr. Martin Siczkowski, West Yorkshire PTE, Leeds, uk v1.0 + Gustav Thiessen BLIC thi@BLIC.DE, de v1.0 + Dr Bartak, bartak@apex-jesenice.cz v1.0 + Dr. Franz-Josef Czuka, Beratungsgesellschaft für, Düsseldorf, de v1.0 + Dr.-Ing. Klaus-Peter Heynert, PSI Transportation GmbH, Berlin, de v1.0 + Jean-Laurant Franchineau, CONNEX-EUROLUM, PARIS, fr v1.0 + Dipl.-Ing. (FH) Rainer Ganninger, init innovation in, Karlsruhe, de v1.0 + Dipl.-Ing. HTL Peter Machalek, Siemens Transit, Neuhausen am Rheinfall, ch v1.0 + El Ing. Ernst Pfister, Siemens Transit, Neuhausen am Rheinfall, ch v1.0 + Dipl.-Ing. Berthold Radermacher, Verband Deutscher, Köln, de v1.0 + Dr. Friedemann Weik, Hamburger Berater Team GmbH, Hamburg, de v1.0 + + Robin Vettier, ixxi.com, fr v1.3 + Ofer Porat, fr v1.3 + Burt Alexander', sigtec.com + Michelle Etienne, Dryade, Paris fr, v1.3 + Brian Ferris onebusaway.org, us, v1.3 + Manuem Mahne Siemens.com + + Ulf Bjersing, Hogia - Stenungsgrund, se v2.0 + Dipl.-Math Christoph Blendinger, DB, Frankfort, de v2.0 + Dipl.-Kfm. Winfried Bruns, Verband Deutscher, Köln, de v2.0 + Christophe Duquesne, PDG Consultant en systémes, Auriga, fr v2.0 + Gerald Dury, Trapeze Neuhausen am Rhein, ch, fr v2.0 + Michelle Etienne, Dryade, Paris fr v2.0 + Michael Frumin, MTA, us, v2.0 + Nicholas Knowles, Trapeze Limited, London, uk v2.0 + Werner Kohl, Mentz Datenverarbeitung GmbH, München, de v2.0 + Davide Lallouche, RATP, Paris, fr v2.0 + Jeff Makkie, us, v2.0 + Daniel Rubli, Trapeze Neuhausen am Rhein, ch, fr v2.0 + Gustav Thiessen BLIC thi@BLIC.DE, de 2.0 v1.0 + Jeff Maki, openplans, us, v2.0 + Europe + >Drafted for version 1.0 & Version 2.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2008-11-17 + + + + 2008-04-18 + + + + 2009-03-30 + + + + 2011-04-18 + + + + 2012-03-23 + + + +

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

      +

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

      +

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

      +

      SIRI includes common mechanisms and messages for system status management.

      +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}siriSg.xsd + [ISO 639-2/B] ENG + Kizoom Software Ltd 16 High Holborn, London WC1V 6BX + + http://www.siri.org.uk/schema/2.0/xsd/siri__base.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__allFunctionalServices.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG XML and Trident standards.
        • +
      • Derived from the SIRI Version 1.0
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport. + + CEN TC278 WG3 SG7 + + SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Generic Substitution groups version + Standard +       +       + SIRI Service Interface for Real-time Information relating to Public Transport Operations. XML Schema with loosely coupled functional services, +       + + + + + + + + + + + Service Interface for Real-time Operation. + + + + + + + + + + + +       diff --git a/xsd/siri_all_functionalServices.xsd b/xsd/siri_all_functionalServices.xsd index 0b49cb7e..52287375 100644 --- a/xsd/siri_all_functionalServices.xsd +++ b/xsd/siri_all_functionalServices.xsd @@ -1,95 +1,95 @@ - - - - - - main schema - e-service developers - Europe - >Drafted for Version 2.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - 2012-03-29 - Facrore dout from Siri.xsd - - 2012-03-29 - SIRI Version 2.0 - Refactored to improve modularisation - - -

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

      -

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

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

      -

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

      -

      SIRI includes common mechanisms and messages for system status management.

      -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/}all_functionalServices.xsd - [ISO 639-2/B] ENG - Kizoom Software Ltd 16 High Holborn, London WC1V 6BX - - http://www.siri.org.uk/schema/2.0/xsd/siri__base.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__estimatedTimetable_service.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__productionTimetable_service.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__stopMonitoring_service.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__vehicleMonitoring_service.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__connectionTimetable_service.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__connectionMonitoring_service.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__generalMessage_service.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__discovery.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__situationExchange_service.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri__facilityMonitoring_service.xsd - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      • Derived from the SIRI Version 1.0.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport. - - CEN TC278 WG3 SG7 - - SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Current SIRI functional servics - Standard -       -       -       - - - - - - - - - - - - - - - - -       + + + + + + main schema + e-service developers + Europe + >Drafted for Version 2.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + 2012-03-29 + Facrore dout from Siri.xsd + + 2012-03-29 + SIRI Version 2.0 + Refactored to improve modularisation + + +

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

      +

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

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

      +

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

      +

      SIRI includes common mechanisms and messages for system status management.

      +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}all_functionalServices.xsd + [ISO 639-2/B] ENG + Kizoom Software Ltd 16 High Holborn, London WC1V 6BX + + http://www.siri.org.uk/schema/2.0/xsd/siri__base.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__estimatedTimetable_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__productionTimetable_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__stopMonitoring_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__vehicleMonitoring_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__connectionTimetable_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__connectionMonitoring_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__generalMessage_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__discovery.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__situationExchange_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__facilityMonitoring_service.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG XML and Trident standards.
        • +
      • Derived from the SIRI Version 1.0.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport. + + CEN TC278 WG3 SG7 + + SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Current SIRI functional servics + Standard +       +       +       + + + + + + + + + + + + + + + + +       diff --git a/xsd/siri_connectionMonitoring_service.xsd b/xsd/siri_connectionMonitoring_service.xsd index 607c12c1..bf9c5122 100644 --- a/xsd/siri_connectionMonitoring_service.xsd +++ b/xsd/siri_connectionMonitoring_service.xsd @@ -1,731 +1,731 @@ - - - - - - main schema - e-service developers - CEN TC278 WG3 SG7 Team - Dipl.-Ing. Sven Juergens psitrans juergens@psitrans.de - Gustav Thiessen BLIC thi@BLIC.DE - Europe - Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2004-09-10 - - - 2004-10-01 - - - 2005-02-14 - - - 2005-02-20 - - - 2005-05-11 - - 2007-04-17 - Name Space changes - - 2008-11-17 - Revise to support substitution groups - - 2012-03-23 - +SIRI v2.0 - Add SuggestedWaitDecisionTime to MonitoredArrival - - 2012-04-18 - +SIRI v2.0 - Add ValidUntil Time to MonitoredFeederArrival - - * [FR] Add Extensions tag to ConnectionMonitoringSubscriptionRequest - [DE] Correct Capabilities matrix - - 2013-01-24 - WB: insert the AimedArrivalTime in MonitoredFeederArrival; insert the ArrivalPlatformName into MonitoredFeederArrival - - -

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

      -

      This sub-schema describes the Connection Monitoring Service.

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

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

      +

      This sub-schema describes the Connection Monitoring Service.

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

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

      -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/siri/2.0/xsd/}siri_connectionTimetable_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - -SIRI-CT schema. Service Interface for Real-time Information. Connection Timetable Service. - Standard -       -       - SIRI-CT Connection Timetable Service. -       - - - - - - - Convenience artifact to pick out main elements of the Connection Timetable Service. - - - - - - - - - - - - - - - - Request for information about timetabled connections at a stop. - - - - - Parameters that specify the content to be returned. - - - - - Earliest and latest time. If absent, default to the data horizon of the service. - - - - - CONNECTION link for which data is to be supplied. - - - - - Feeder LINE for which data is to be supplied. - - - - - Feeder DIRECTION for which data is to be supplied. - - - - - - - Type for Request for Connection Timetable Service. - - - - - - - - - - - Version number of request. Fixed - - - - - - - - - Parameters that affect the request processing. - - - - - Preferred languages in which to return text values. - - - - - - - - - Parameters that affect the subscription processing. - - - - - - Subscription Request for information about Timetabled connections at a stop. - - - - - Type for Subscription Request for Connection Protection. - - - - - - - - - - - - - - - Delivery for Connection Timetable Service. - - - - - Type for Delivery for Connection Protection. - - - - - - - - - - Version number of response. Fixed - - - - - - - - - Feeder delivery payload content. - - - - - - - - - - Fedder/Fetcher SERVICE JOURNEY INTERCHANGE Activity. - - - - - Type for an SERVICE JOURNEY INTERCHANGE feeder Activity. - - - - - - - Time until when data is valid. +SIRI 2.0 - - - - - - - - - - Elements identifying CALL at CONNECTION link of SERVICE JORUNEY INTERCHANGE of Feeder Journey . - - - - - Reference to the the SERVICE JOURNEY INTERCHANGE between two journeys for which data is being returned. - - - - - Reference to the CONNECTION link or ACCESS ZONE for which data is to be returned. i.e. associated with known feeder arrival and distributor departure STOP POINTs. - - - - - - - - - A feeder arrival at the arrival SCHEDUELD STOP POINT of the CONNECTION link . - - - - - Type for incoming visit by feeder journey to SERVICE JOURNEY NTERCHANGE - - - - - - - Information about the feeder journey. - - - - - Planned arrival time at the connection point. - - - - - - - - - - Cancellation of a previously issued Feeder Arrival. - - - - - Type for Timetabled Deletion of a feeder connection. - - - - - - - - Reference to a LINE. - - - - - Reference to a DIRECTION, typically outward or return. - - - - - Reference to a VEHICLE JOURNEY. - - - - - - Reason for deletion. (Unbounded since SIRI 2.0) - - - - - - - - - - - - Type for Deliveries for Connection Timetable Service. Used in WSDl. - - - - - - - - - - Request for information about Connection Timetable Service Capabilities. Answered with a ConnectionTimetableCapabilitiesResponse. - - - - - Capabilities for Connection Timetable Service. Answers a ConnectionTimetableCapabilitiesRequest. - - - - - - Type for Delivery for Connection TimetableService. - - - - - - - - Participant's permissions to use the service, Only returned if requested. - - - - - - - - Permission for a single participant or all participants to use an aspect of the service. - - - - - - - - - - - - -Version number of response. Fixed - - - - - - - - - Type for capability request. - - - - - - - Whether results returns foreign journeys only. - - - - - - - - - Capabilities of Connection Timetable Service. - - - - - Type for Connection Timetable Capabilities. - - - - - - - Filtering Capabilities. - - - - - - - Whether results can be filtered by Connection link. Default is ' true'. - - - - - - - - Request Policy capabilities. - - - - - - - - Whether service returns only foreign journeys. Default is 'false'. - - - - - - - - - - Subscription Policy capabilities. - - - - - Optional Access control capabilities. - - - - - - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Dipl.-Ing. Sven Juergens psitrans juergens@psitrans.de + Gustav Thiessen BLIC thi@BLIC.DE + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2004-09-10 + + + 2004-10-01 + + + 2005-02-14 + + + 2005-02-20 + + + 2005-05-11 + + + 2007-04-17 + + + + 2008-11-17 + + + + 2011-01-19 + + + + 2012-03-23 + + + + 2012-04-18 + + + +

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

      +

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

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

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

      -

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

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/}siri_discovery.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference.xsd - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Discovery services Derived from the NaPTAN standard .
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI_DS XML schema. Service Interface for Real-time Information. Discovery subschema. - Standard -       -       - SIRI DIscovery Services for SCHEDULED STOP POINTs, LINEs,OPERATORs, FACILITies and feature TYPE OF VALUE codes. -       - - - - - - - - - - - - Convenience artifact to pick out main elements of the Estimated Timetable Service. - - - - - - - - - Requests for reference data for use in service requests. - - - - - - - - - - - - - - - - - - Responses with reference data for use in service requests. - - - - - - - - - - - - - - - - - Requests a list of the STOP POINTs and places covered by a Producer. - - - - - - - - - - Requests for stop reference data for use in service requests. - - - - - - - Parameters that specify the content to be returned. (+SIRI v2.0) - - - - - Parameters that affect the request processing. Mostly act to reduce the number of stops returned. (+SIRI v2.0) - - - - - - - Version number of request. Fixed - - - - - - - - - Parameters that specify the STOP POINTs to be returned. +SIRI v2.0 - - - - - - Rectangle containing stops be returned. (+SIRI v2.0) - - - - - Circle containing stops be returned. Point indicates centre, precision indicates radius (+SIRI v2.0) - - - - - Filter the results to include only stops associated with the PLACE . (+SIRI v2.0) - - - - - - Filter the results to include only stops run by the specified OPERATOR. (+SIRI v2.0) - - - - - Filter the results to include only stops for the given LINE. (+SIRI v2.0) - - - - - - - Parameters that affect the request processing. Mostly act to reduce the number of stops returned. +SIRI v2.0 - - - - - Preferred languages in which to return text values. +SIRI v2.0 - - - - - Level of detail to include in response. Default is 'normal'. +SIRI v2.0 - - - - - - - Detail Levels for Stop Points Discovery Request. +SIRI v2.0 - - - - - Return only the name and identifier of the stop. - - - - - Return name, dientifier and coordinates of the stop. - - - - - Return all available data for each stop. - - - - - - - - Returns basic details about the STOP POINTs/places covered by a service. Answers a StopPointsRequest. - - - - - Response with STOP POINTs available to make requests. - - - - - - - - - - Version number of response. Fixed - - - - - - - - - - - Requests a list of the LINEs covered by a Producer. - - - - - Requests for LINE data for use in service requests. - - - - - - - - - - - Version number of request. Fixed - - - - - - - - - Parameters that specify the LINEs to be returned. +SIRI v2.0 - - - - - - - Rectangle containing stops of lines be returned. (+SIRI v2.0) - - - - - Circle containing stops for lines be returned. Point indicates centre, precision indicates radius (+SIRI v2.0) - - - - - Filter the results to include only lines for stops assoicated with the place . (+SIRI v2.0) - - - - - - Reference to line for which details are to be returned (v2.0) - - - - - - Filter the results to include only Stop d run by the specified OPERATOR. (+SIRI v2.0) - - - - - - - Parameters that affect the request processing. Mostly act to reduce the number of Linesreturned. +SIRI v2.0 - - - - - Preferred languages in which to return text values. +SIRI v2.0 - - - - - Level of detail to include in response. Default is 'normal'. +SIRI v2.0 - - - - - - - Detail Levels for Lines Discovery Request. +SIRI v2.0 - - - - - Return only the name and identifier of the stop. - - - - - Return name, dientifier and coordinates of the stop. - - - - - - Return all available data for each stop. - - - - - - - - Returns the LINEs covered by a web service. Answers a LINEsRequest. - - - - - Response with LINEs available to make requests. - - - - - - - - - - Version number of response. Fixed. - - - - - - - - - - Requests a list of the Product Categories covered by a Producer. - - - - - Requests for TYPE OF PRODUCT CATEGORY reference data for use in service requests. - - - - - - - - - - Version number of request. Fixed - - - - - - - - - Parameters that affect the request processing. Mostly act to reduce the number of Facilities returned. +SIRI v2.0 - - - - - Preferred languages in which to return text values. +SIRI v2.0 - - - - - - - - Returns the Product Categories covered by a service. Answers a ProductCategoriesRequest. - - - - - Type for Response with Product Categories available to make requests. - - - - - - - - - - Version number of response. Fixed. - - - - - - - - - - Requests a list of the Vehicle Features covered by a Producer. - - - - - Requests for VEHICLE feature data for use in service requests. - - - - - - - - - - Version number of request. Fixed - - - - - - - - - Parameters that affect the request processing. Mostly act to reduce the number of Facilities returned. +SIRI v2.0 - - - - - Preferred languages in which to return text values. +SIRI v2.0 - - - - - - - - Returns the Vehicle Features covered by a service. Answers a VehicleFeaturesRequest. - - - - - Type for Response with Vehicle Features available to make requests. - - - - - - - - - - Version number of response. Fixed. - - - - - - - - - - Requests a list of the Info Channels covered by a Producer. - - - - - Requests for info channels for use in service requests. - - - - - - - - - Version number of request. Fixed - - - - - - - - - - Returns the Info Channels covered by a service. Answers a InfoChannelRequest. - - - - - Type for Response with Info channels categories available to make requests. - - - - - - - - - - Version number of response. Fixed. - - - - - - - - - - Requests a list of the Facilities covered by a Producer. - - - - - Requests for info channels for use in service requests. - - - - - - - - - - - Version number of request. Fixed - - - - - - - - - Parameters that specify the Facilities to be returned. +SIRI v2.0 - - - - - - Rectangle containing Facilities be returned. (+SIRI v2.0) - - - - - Filter the results to include only Facilities associated with the TOPOGRAPHIC PLACE . (+SIRI v2.0) - - - - - - Filter the results to include only Facilities run by the specified OPERATOR. (+SIRI v2.0) - - - - - Filter the results to include only Facilities for the given LINE. (+SIRI v2.0) - - - - - - - Parameters that affect the request processing. Mostly act to reduce the number of Facilities returned. +SIRI v2.0 - - - - - Preferred languages in which to return text values. +SIRI v2.0 - - - - - Level of detail to include in response. Default is 'normal'. +SIRI v2.0 - - - - - - - Detail Levels for Facility Points Request. +SIRI v2.0 - - - - - Return only the name and identifier of the Facility. - - - - - Return name, identifier and coordinates of the Facility. - - - - - Return all available data for each Facility. - - - - - - - - Returns the Facilities covered by a service. Answers a StopPointsRequest. - - - - - Response with Facilities available to make requests. - - - - - - - Facility Definition. - - - - - - - Version number of response. Fixed. - - - - - - - - - - - Requests a list of the Service Features covered by a Producer. - - - - - - - - - - Type for equests for TYPE OF PRODUCT CATEGORY reference data for use in service requests. - - - - - - - - - Version number of request. Fixed - - - - - - - - - - Returns the SERVICE FEATUREs covered by a service. Answers a ServiceFeaturesRequest. - - - - - Type for Response with SERVICE FEATUREs available to make requests. - - - - - - - - - Version number of response. Fixed. - - - - - - - - - - Requests a list of the CONNECTION LINKs covered by a Producer. +SIRI v2.0 - - - - - Requests for CONNECTION LINK data for use in service requests. +SIRI v2.0 - - - - - - - - - - - Version number of request. Fixed - - - - - - - - Parameters that specify the CONNECTION LINKs to be returned. +SIRI v2.0 - - - - - - - Rectangle containing stops of ConnectionLinks be returned. - - - - - Circle containing stops for ConnectionLinks be returned. Point indicates centre, precision indicates radius - - - - - Filter the results to include only ConnectionLinks for stops assoicated with the place . - - - - - - - Filter the results to include only ConnectionLinks for stops assoicated with the specified line. - - - - - Filter the results to include only Stop d run by the specified OPERATOR. - - - - - - - Parameters that affect the request processing. Mostly act to reduce the number of ConnectionLinks returned. +SIRI v2.0 - - - - - Preferred languages in which to return text values. +SIRI v2.0 - - - - - Level of detail to include in response. Default is 'normal'. +SIRI v2.0 - - - - - - - Detail Levels for CONNECTION LINKs Discovery Request. +SIRI v2.0 - - - - - Return only the name and identifier of the connection link. - - - - - Return name, identifier of the connection link and connected stops's identifiers. - - - - - Return all available data for each connection link. - - - - - - - - Returns the CONNECTION LINKs covered by a web service. Answers a LINEsRequest. +Siri v2.0 - - - - - Response with CONNECTION LINKs available to make requests. +SIR v2.0 - - - - - - - - - - Version number of response. Fixed. - - - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2004-09-29 + + + 2005-02-14 + + + 2005-02-20 + + + 2005-05-04 + + + 2005-11-25 + + + 2007-04-17 + + + + 2008-11-13 + + + + 2008-11-17 + + + + 2012-03-23 + + + + 2012-05-17 + + + + 2013-03-28 + + + +

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

      +

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

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

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

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

      -

      This sub-schema describes the Estimated Timetable Service.

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/}siri_estimatedTimetable_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_estimatedVehicleJourney.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions.xsd - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI-ET XML schema. Service Interface for Real-time Information. Estimated Timetable Service. - Standard -       -       - SIRI-ET Estimated Timetable Service. -       - - - - - - - - Convenience artifact to pick out main elements of the Estimated Timetable Service. - - - - - - - - - - - - - - - - - Request for information about the estimated timetable. - - - - - Type for Type for Functional Service Request for Estimated Timetable. - - - - - - - - - - - Version number of request. Fixed - - - - - - - - - Parameters that specify the content to be returned. - - - - - Forward duration for which journeys should be included. For subscriptions, this duration is a continuously rolling window from the present time. For immediate requests, this duration is measured from the time of the request. - - - - - Communicate only differences to the timetable specified by this version of the timetable. - - - - - Filter the results to include journeys for only the specified OPERATORs. - - - - - Filter the results to include only VEHICLEs along the given LINEs. - - - - - - Include only vehicles along the given LINE. - - - - - - - - Filter the results to include only journeys of the specified VEHICLE MODE. +SIRI v2.1 - - - - - Filter the results to include only journeys of the specified TYPE OF PRODUCT CATEGORY. +SIRI v2.1 - - - - - Filter the results to include only journeys with a CALL at the specified STOP POINT. +SIRI v2.1 - - - - - - - Parameters that affect the request processing. Mostly act to reduce the number of messages exchanged. - - - - - Preferred languages in which to return text values. - - - - - - - - - Level of detail to include in response. Default is 'normal'. (SIRI 2.0) - - - - - - - Detail Levels for Estimated Timetable Request. - - - - - Return only the minimum amount of optional data for each Stop Visit to provide a display, A time at stop, LINE name and destination name. - - - - - Return minimum and other available basic details for each Stop Visit. Do not include data on times at next stop or destination. - - - - - Return all basic data, and also origin VIA points and destination. - - - - - Return in addition to normal data, the estimated call data i . - - - - - Return all available data for each including calls. - - - - - - - - Request for a subscription to the Estimated Timetable Service. - - - - - Parameters that affect the subscription publishing and notification processing. - - - - - Whether the producer should return the complete set of data, or only provide updates to the previously returned data i.e. changes to the expected deviation (delay or early time). Default is 'true'. If true only changes at the first stop will be returned and the client must interpolate the -If false each subscription response will contain the full information as specified in this request (++SIRI 2.0). - - - - - The amount of change to the arrival or departure time that can happen before an update is sent (i.e. if ChangeBeforeUpdate is set to 2 minutes, the subscriber will not be told that a timetable is changed by 30 seconds - an update will only be sent when the timetable is changed by at least least 2 minutes. (OPtional from SIRI 2.0) - - - - - Indicates whether actual arrival-/departure times should be delivered as incremental updates, i.e. whether RECORDED CALL updates are transmitted immediately after an event occurs. +SIRI v2.1 -- 'false': Specifies that the data producer should transmit RECORDED CALL data, in particular actual arrival-/departure information as an incremental update immediately after an event occurs (with hysteresis taken into account) as is generally the case. -The server will automatically proceed with 'false' if capability is not supported. -- 'true': Can be requested if the data traffic is to be reduced and an immediate transmissions is not required in any of the consumer systems. -'true' specifies that the data producer should skip RECORDED CALL updates (if capability is supported after all), i.e., deliver them with the next update instead. -- No specification: Default value 'false' applies (don't skip updates of recorded data). - - - - - Indicates whether ONLY actual arrival-/departure times should be delivered. In other words, whether all updates related to ESTIMATED CALL should be skipped. +SIRI v2.1 -- 'false': Specifies that the data producer should transmit ESTIMATED and RECORDED CALL data as an incremental update immediately after an event occurs (with hysteresis taken into account) as is generally the case. -The server will automatically proceed with 'false' if capability is not supported. -- 'true': Can be requested if a consumer system is only interested in the actual times / recorded events because it only wants to check the performance for example. -'true' specifies that the data producer should only deliver RECORDED CALL udpates and skip ESTIMATED CALL updates (if capability is supported after all), i.e., deliver ESTIMATED CALL updates only with the next RECORDED CALL update. -- No specification: Default value 'false' applies (don't skip updates of estimated data). - - - - - - - Subscription Request for the Estimated Timetable Service. - - - - - - - - - - - - - - - - - - Delivery for Estimated Timetable Service. - - - - - Type for Delivery for Real-time Timetable Service. - - - - - - - - - Version number of response. Fixed - - - - - - - - - Type for version frame structure. - - - - - - - - - Connection parameters for a monitored SERVICE JOURNEY INTERCHANGE between a feeder and distributor journey. SIRI 2.0 - - - - - - - - - Payload part of Estimated Timetable Delivery. - - - - - Estimated Journeys of a common TIMETABLE VERSION FRAME, grouped by timetable version. - - - - - - - - - - Type for Deliveries for Real-time Timetable Service. Used in WSDL. - - - - - - - - - - Request for information about Estimated Timetable Service Capabilities. Answered with a EstimatedTimetableCapabilitiesResponse. - - - - - - Capabilities for Estimated Timetable Service. Answers a EstimatedTimetableCapabilitiesRequest. - - - - - Type for Delivery for Estimated Timetable Capability. - - - - - - - - - - - - - - - Type for Estimated Timetable Capability Request Policy. - - - - - - - Whether results returns foreign journeys only. - - - - - - - - - Capabilities of Estimated TimetableService. - - - - - Type for Estimated Timetable Capabilities. - - - - - - - Filtering Capabilities. - - - - - - Preview interval available for estimations. - - - - - - - - - - Whether results can be filtered by TIMETABLE VERSION Default is 'true'. - - - - - - - - Request Policy capabilities. - - - - - - - - - - Subscription Policy capabilities. - - - - - Optional Access control capabilities. - - - - - - - - - - - Participant's permissions to use the service. - - - - - - - - Permission for a single participant or all participants to use an aspect of the service. - - - - - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Werner Kohl MDV + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2003-02-10 + + + 2004-10-31 + + + 2005-02-14 + + + 2005-02-20 + + + 2005-05-11 + + 2007-04-17 + Name Space changes + + 2008-03-26 + Add wrapper tag for Line DIRECTION to help binding to Axis + + 2008-11-17 + Revise to support substitution groups + + 2011-01-19 + Drop use of As Flat Groups for EstimatedCalls + + 2012-03-23 + +SIRI v2.0 + - Add EstimatedServiceJourneyInterchange (i.e. Estimated Connection of VEHICLE) to EstimatedTimetableDelivery + - [FR] Add Extensions tag to EstimatedTimetableSubscriptionRequest + - [DE] Add ExpectedDeparturePredictionQuality to OnwardVehicleDepartureTimes + [DE] Correct capabilites matrix to matx doc. Add defauklt preview intervakl and versionref + + +

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

      +

      This sub-schema describes the Estimated Timetable Service.

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

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

      -

      This sub-schema describes the Facility Monitoring Service.

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/}sir_facilityMonitoring_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_reference.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions.xsd - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI-FM XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Facility Monitoring Subschema - Standard -       -       - SIRI-FM Facility Monitoring Service. -       - - - - - - - - - - - - - - - - - Convenience artifact to pick out main elements of the Facility Monitoring Service. - - - - - - - - - - - - - - - - Request for information about Facilities status. - - - - - Type for Functional Service Request for Facility Monitoring Service. - - - - - - - - - - - Version number of request. Fixed - - - - - - - - - Parameters that specify the content to be returned. - - - - - Forward duration for which Facilities status change: only status change which will occur within this time span will be returned. - - - - - Start time for PreviewInterval. If absent, then current time is assumed. - - - - - Parameters to filter Facility Monitoring requests, based on the facility location. Parameter value will be logically ANDed together. Multiple values fro the same parameter will be logically ORed. - - - - - Filter only for facility changes that affect the following accessibility needs. - - - - - - - Type for information about Accessibility Facilities status. - - - - - User need to be monitored. - - - - - - - Parameters to filter Facility Monitoring requests, based on the facility location . - - - - - - - - - - Use of simple reference is deprecated - - - - Refercence to a VEHICLE JOURNEY framed by the day. SIRI 2.0 - - - - - - - - - Reference to a stop place. - - - - - Reference to a stop place component. - - - - - Reference to a Site. - - - - - - - Parameters that affect the request processing. - - - - - Preferred languages in which to return text values. - - - - - - The maximum number of facility status in a given delivery. The most recent n Events within the look ahead window are included. - - - - - - - - Request for a subscription to the Vehicle Monitoring Service. - - - - - Parameters that affect the subscription publishing and notification processing. - - - - - Whether the producer will return the complete set of current data, or only provide updates to this data, i.e. additions, modifications and deletions. -If false or omitted, each subscription response will contain the full information as specified in this request. - - - - - - - Type for Subscription Request for Vehicle Monitoring Service. - - - - - - - - - - - - - - - - Delivery for Vehicle Monitoring Service. - - - - - Payload part of Vehicle Monitoring delivery. - - - - - - - - Type for Delivery for Vehicle Monitoring Service. Provides information about one or more vehicles; each has its own VEHICLE activity element. - - - - - - - Payload part of Facility Monitoring delivery. - - - - - - - Version number of response. Fixed - - - - - - - - - Condition of a Facility that is being monitored. - - - - - - - - Type for Deliveries for VEHICLE monitoring services Used in WSDL. - - - - - Delivery for Vehicle Activity Service. - - - - - - - - - Request for information about Vehicle Monitoring Service Capabilities. Answered with a VehicleMontoringCapabilitiesResponse. - - - - - - Capabilities for Vehicle Monitoring Service. Answers a VehicleMontoringCapabilitiesRequest. - - - - - Type for Delivery for Vehicle Monitoring Service. - - - - - - - - - - - Version number of response. Fixed - - - - - - - - - Capabilities of Vehicle Monitoring Service. - - - - - Type for Vehicle Monitoring Capabilities. - - - - - - - Filtering Capabilities. - - - - - - Default preview interval. Default is 60 minutes. - - - - - - Whether results can be filtered by location. Fixed as 'true'. - - - - - - - - - - - Whether results can be filtered by Specific Needs. Default is 'true'. - - - - - - - - Request Policy capabilities. - - - - - - - - - - - - - - Subscription Policy capabilities. - - - - - Optional Access control capabilities. - - - - - - - - - - - - - - - Optional Response capabilities. - - - - - - Whether result supports remedy information. Default is 'false' - - - - - Whether result supports facility location information. Default is 'true'. - - - - - - - - - - - - - Elements for volume control. - - - - - Whether a maximum number of Facility Status to include can be specified. Default is 'false'. - - - - - - - - Participant's permissions to use the service. - - - - - - - - - - - - - - Type for Facility Monitoring Service Permissions. - - - - - - - - - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + Drafted for version 1.1 CEN TC278 WG3 SG7 Editor Christophe Duquesne Dryade mailto:christophe.duquesne@dryade.net + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + + 2007-01-22 + + + 2007-01-22 + + 2007-04-17 + Name Space changes + + 2008-11-17 + Revise to support substitution groups + + 2008-11-18 + Revise in line with FM spec - add filters + + 2012-03-23 + +SIRI v2.0 + Add Extensions tag to FacilityMonitoringSubscriptionRequest + + +

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

      +

      This sub-schema describes the Facility Monitoring Service.

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

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

      -

      This sub-schema describes the General Message Service.

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/}siri_generalMessage_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_reference.xsd - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI-GM XML schema. Service Interface for Real-time Information. SubSchema for General Message Service - Standard -       -       - SIRI-GM General Message Service. -       - - - - - - - Convenience artefact to pick out main elements of the General Message Service. - - - - - - - - - - - - - - - - - Request for information about general information messages affecting stops, vehicles or services. - - - - - Service Request for General Messages. - - - - - - - - - - - Version number of request. Fixed - - - - - - - - - Parameters that affect the request processing. - - - - - Referenceto an Info Channel for which messages are to be returned. - - - - - - - Parameters that affect the request processing. - - - - - Preferred languages in which to return text values. - - - - - - - Request for a subscription to General Message Service. - - - - - Subscription for General Message Service. - - - - - - - - - - - - - - - Delivery for General Message Service. - - - - - General Message payload content. - - - - - - - - - Delivery for General Message. - - - - - - - - - - Version number of response. Fixed - - - - - - - - - - An informative message. - - - - - Type for an Info Message. @formatRef. - - - - - - - - Time until when message is valid. If absent unopen ended. - - - - - - Message Content. Format is specified by Format Ref. - - - - - - - - - Reference to a format of the Content. If absent, free text. - - - - - - - - Extra information provided on general message notifcation that can be used to filter messages. - - - - - Unique identifier of message. - - - - - Optional version number of update to previosu message. - - - - - Info Channel to which message belongs. - - - - - - - A revocation of a previous message. - - - - - Type for Revocation of a previous message. - - - - - - - Identifier of message. Unique within service and Producer participant. - - - - - Info Channel to which message belongs. - - - - - - - - - - - Type for identifier of an Info Message. - - - - - - Type for reference to an Info Message. - - - - - - - - - - Type for Deliveries. Used in WSDL. - - - - - Delivery for general Message service. - - - - - - - - - Request for information about General Message Service Capabilities. Answered with a GeneralMessageCapabilitiesResponse. - - - - - - Capabilities for General Message Service. Answers a GeneralMessageCapabilitiesResponse. - - - - - Type for Delivery for General MessageService. - - - - - - - - - - - -Version number of response. Fixed - - - - - - - - - Capabilities of General Message Service. - - - - - Type for General Message Capabilities. - - - - - - - Filtering Capabilities. - - - - - - Default preview interval. Default is 60 minutes. - - - - - Whether results can be filtered by InfoChannel, departures. Default is 'true'. - - - - - - - - Request Policiy capabilities. - - - - - Optional Access control capabilities. - - - - - - - - - - Participant's permissions to use the service. - - - - - - - - Permission or a single particpant or all participants. - - - - - - - - - - Type for General MessageService Permission. - - - - - - - The monitoring points that the participant may access. - - - - - - - Participant's permission for this InfoChannel. - - - - - - - - - - - - - Type for access control. - - - - - - - If access control is supported, whether access control by LINE is supported. Default is 'true'. - - - - - - - - - Type for Info Channel Permission. - - - - - - - Reference to an Info Channel to which permission applies. - - - - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Gustav Thiessen BLIC thi@BLIC.DE + Europe + >Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2004-09-29 + + + 2004-10-01 + + + 2005-02-14 + + + 2005-02-20 + + + 2005-05-11 + + + 2007-04-17 + + + + 2008-11-17 + + + + 2011-04-18 + + + + 2012-03-23 + + + +

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

      +

      This sub-schema describes the General Message Service.

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}siri_generalMessage_service.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_reference.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG XML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI-GM XML schema. Service Interface for Real-time Information. SubSchema for General Message Service + Standard +       +       + SIRI-GM General Message Service. +       + + + + + + + Convenience artefact to pick out main elements of the General Message Service. + + + + + + + + + + + + + + + + + Request for information about general information messages affecting stops, vehicles or services. + + + + + Service Request for General Messages. + + + + + + + + + + + Version number of request. Fixed + + + + + + + + + Parameters that affect the request processing. + + + + + Referenceto an Info Channel for which messages are to be returned. + + + + + + + Parameters that affect the request processing. + + + + + Preferred languages in which to return text values. + + + + + + + Request for a subscription to General Message Service. + + + + + Subscription for General Message Service. + + + + + + + + + + + + + + + Delivery for General Message Service. + + + + + General Message payload content. + + + + + + + + + Delivery for General Message. + + + + + + + + + + Version number of response. Fixed + + + + + + + + + + An informative message. + + + + + Type for an Info Message. @formatRef. + + + + + + + + Time until when message is valid. If absent unopen ended. + + + + + + Message Content. Format is specified by Format Ref. + + + + + + + + + Reference to a format of the Content. If absent, free text. + + + + + + + + Extra information provided on general message notifcation that can be used to filter messages. + + + + + Unique identifier of message. + + + + + Optional version number of update to previosu message. + + + + + Info Channel to which message belongs. + + + + + + + A revocation of a previous message. + + + + + Type for Revocation of a previous message. + + + + + + + Identifier of message. Unique within service and Producer participant. + + + + + Info Channel to which message belongs. + + + + + + + + + + + Type for identifier of an Info Message. + + + + + + Type for reference to an Info Message. + + + + + + + + + + Type for Deliveries. Used in WSDL. + + + + + Delivery for general Message service. + + + + + + + + + Request for information about General Message Service Capabilities. Answered with a GeneralMessageCapabilitiesResponse. + + + + + + Capabilities for General Message Service. Answers a GeneralMessageCapabilitiesResponse. + + + + + Type for Delivery for General MessageService. + + + + + + + + + + + +Version number of response. Fixed + + + + + + + + + Capabilities of General Message Service. + + + + + Type for General Message Capabilities. + + + + + + + Filtering Capabilities. + + + + + + Default preview interval. Default is 60 minutes. + + + + + Whether results can be filtered by InfoChannel, departures. Default is 'true'. + + + + + + + + Request Policiy capabilities. + + + + + Optional Access control capabilities. + + + + + + + + + + Participant's permissions to use the service. + + + + + + + + Permission or a single particpant or all participants. + + + + + + + + + + Type for General MessageService Permission. + + + + + + + The monitoring points that the participant may access. + + + + + + + Participant's permission for this InfoChannel. + + + + + + + + + + + + + Type for access control. + + + + + + + If access control is supported, whether access control by LINE is supported. Default is 'true'. + + + + + + + + + Type for Info Channel Permission. + + + + + + + Reference to an Info Channel to which permission applies. + + + + + + +       diff --git a/xsd/siri_model/siri_all.xsd b/xsd/siri_model/siri_all.xsd index 62625177..0ab0d00f 100644 --- a/xsd/siri_model/siri_all.xsd +++ b/xsd/siri_model/siri_all.xsd @@ -1,13 +1,13 @@ - - - - - - - - - - + + + + + + + + + + diff --git a/xsd/siri_model/siri_all_journeyModel.xsd b/xsd/siri_model/siri_all_journeyModel.xsd index 25648414..48079667 100644 --- a/xsd/siri_model/siri_all_journeyModel.xsd +++ b/xsd/siri_model/siri_all_journeyModel.xsd @@ -1,21 +1,21 @@ - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + diff --git a/xsd/siri_model/siri_all_model.xsd b/xsd/siri_model/siri_all_model.xsd index 80ada732..984702ec 100644 --- a/xsd/siri_model/siri_all_model.xsd +++ b/xsd/siri_model/siri_all_model.xsd @@ -1,13 +1,13 @@ - - - - - - - - - - + + + + + + + + + + diff --git a/xsd/siri_model/siri_all_situation.xsd b/xsd/siri_model/siri_all_situation.xsd index a2fc4d7f..2c0f6a2c 100644 --- a/xsd/siri_model/siri_all_situation.xsd +++ b/xsd/siri_model/siri_all_situation.xsd @@ -1,17 +1,17 @@ - - - - - - - - - - - - - - + + + + + + + + + + + + + + diff --git a/xsd/siri_model/siri_datedVehicleJourney.xsd b/xsd/siri_model/siri_datedVehicleJourney.xsd index b34038f5..9539794d 100644 --- a/xsd/siri_model/siri_datedVehicleJourney.xsd +++ b/xsd/siri_model/siri_datedVehicleJourney.xsd @@ -1,702 +1,702 @@ - - - - - - main schema - e-service developers - CEN TC278 WG3 SG7 Team - Werner Kohl MDV - Europe - Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2003-02-10 - - - 2004-10-31 - - - 2005-02-14 - - - 2005-02-20 - - - 2005-05-11 - - 2007-04-17 - Name Space changes - - 2008-03-26 - Add wrapper tag for Line DIRECTION to help binding to Axis - - 2008-11-17 - Revise to support substitution groups - - 2011-04-18 - - siri_productionTimetable_service.xsd Type on request ValidiyPeriod start and end should be datetime not time .. - - Change to ClosedTimestampRange instead of ClosedTimeRange. - Fix Subscription request to be an element and have extensions . - - 2011-01-19 - SIRI 1.3 Drop use of As Flat Groups for DatedCalls. - - 2012-03-23 - Factor out fropm ProductionTimetable package - +SIRI v2.0 Add ServiceJourneyInterchange (i.e. Monitored Connection) - [VDV] Add additional times to TargetedServiceInterchange MinimumTransferTime, MaximimTransferTime, StandardTransferTime, MaximumAUtomaticWaitTime, StandardWaitTime. - [VDV] Add Public and Contact Details to JourneyInfo - [VDV] Add AimedLatestPassengerAccessTime to TargetedCall - - - 2013-02-11 - SIRI v2.0 Modified ServiceJourneyInterchange SIRI:PT - - -

      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/schema/2.0/xsd/siri_model/}siri_datedVehicleJourney.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI_PT XML schema. Service Interface for Real-time Information. Production Timetable Service. - Standard -       -       - SIRI-Model Dated Vehicle Joruney. -       - - - - - - A planned VEHICLE JOURNEY taking place on a particular date. - - - - - Type for Planned VEHICLE JOURNEY (Production Timetable Service). - - - - - Identifier for a VEHICLE JOURNEY. - - - - - - - - - - - - - Complete sequence of stops along the route path, in calling order. - - - - - - - - - - Relations of the journey with other journeys, e.g., in case a joining/splitting takes place or the journey substitutes for another one etc. - - - - - - - - Type for previously planned VEHICLE JOURNEY that is removed from the data producer when using incremental updates. +SIRI v2.1 - - - - - A reference to the DATED VEHICLE JOURNEY from a previous PT delivery that is removed by the data producer. - - - - - Optionally identify the VEHICLE JOURNEY indirectly by origin and destination and the scheduled times at these stops. - - - - - TRAIN NUMBERs for journey. - - - - - - TRAIN NUMBER assigned to VEHICLE JOURNEY. - - - - - - - - - - - General info elements that apply to all journeys of timetable version unless overriden. - - - - - Description of the origin stop (vehicle signage) to show on vehicle, Can be overwritten for a journey, and then also section by section by the entry in an Individual Call. (+SIRI 2.0) - - - - - Description of the 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. (Unbounded since SIRI 2.0) - - - - - Additional Text associated with LINE. (Unbounded since SIRI 2.0) - - - - - Whether journey is first or last jouurney of day. +SIRI v2.0 - - - - - - - If the journey is an alteration to a timetable, indicates the original journey, and the nature of the difference. - - - - - Use of simple reference is deprecated - - - - Refecence to a VEHICLE JOURNEY framed by the day. SIRI 2.0 - - - - - - - - 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 cancellation of a journey in the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the journey is not cancelled. - - - - - - - - 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 SERVICE JOURNEY INTERCHANGE between two journeys. +SIRI v2.0 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A planned SERVICE JOURNEY INTERCHANGE from a journey. +SIRI v2.0 - - - - - - - - - - - - - - - - - - - - - - - - - - - A planned SERVICE JOURNEY INTERCHANGE to a journey. +SIRI v2.0 - - - - - - - - - - - - - - - - - - - - - - - - - - - A planned SERVICE JOURNEY INTERCHANGE between two journeys. +SIRI v2.0 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Type for a previously planned SERVICE JOURNEY INTERCHANGE that a data producer wants to silently remove from the plan (because it is erroneous data). Careful: Removal is different from Cancellation. +SIRI v2.1 - - - - - - - - - - - - - - - - - - - - - - - - - - Time Elements for SERVICE JOURNEY INTERCHANGE. - - - - - Elements for INTERCHANGE WAIT TIME. - - - - - - - - Elements for INTERCHANGE TRANSFER duration. - - - - - Standard transfer duration for INTERCHANGE. SIRI v2,0 - - - - - Minimum transfer duration for INTERCHANGE. SIRI v2,0 - - - - - Maximum transfer duration for INTERCHANGE. SIRI v2,0 - - - - - - - Elements for INTERCHANGE WAIT TIME. - - - - - Standard wait time for INTERCHANGE. SIRI v2,0 - - - - - Maximum time that Distributor will wait for Feeder for INTERCHANGE. SIRI v1.0 - - - - - Maximum automatic wait time that Distributor will wait for Feeder for INTERCHANGE. +SIRI v2.0 - - - - - - - - Complete sequence of stops along the route path, in calling order. - - - - - Type for Planned VEHICLE JOURNEY Stop (Production Timetable Service). - - - - - - - Whether this DATED CALL is an addition to the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to false: the journey is not an addition. - - - - - Whether this DATED CALL is a cancellation of a previously announced call (or planned according to the long-term timetable). Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the journey is not cancelled. - - - - - - - Text annotation that applies to this call. - - - - - - - Information on any planned distributor connections (deprecated from SIRI V2.0 ... see 2 next attributes) - - - - - Information on any planned feeder connections. SIRI 2.0 - - - - - Information on any planned distributor connections. SIRI 2.0 - - - - - - - - - Planned Connection between two VEHICLE JOURNEYs. - - - - - - - Reference to a (dated) distributor VEHICLE JOURNEY. - - - - - - Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY 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. - - - - - - - - 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. - - - - - - - - - Connection between two stops within a connection area. Used within the context of one or other end. - - - - - Identifier of CONNECTION LINk. - - - - - - - - - - Times for making SERVICE JOURNEY INTERCHANGE. - - - - - Default time (Duration) needeed to traverse SERVICE JOURNEY INTERCHANGE from feeder to distributor. - - - - - Time needeed by a traveller whis is familiar with SERVICE JOURNEY INTERCHANGE to traverse it. If absent, use DefaultDuration. - - - - - Time needeed by a traveller whis is not familiar with SERVICE JOURNEY INTERCHANGE to traverse it. If absent, use DefaultDuration and a standard weighting. - - - - - Time needeed by a traveller wos is mobility impaired to traverse SERVICE JOURNEY INTERCHANGE. If absent, use DefaultDuration and a standard impaired travel speed. - - - - - - - Properties of SERVICE JOURNEY INTERCHANGE. - - - - - Whether the passenger can remain in VEHICLE (i.e. BLOCKlinking). Default is 'false': the passenger must change vehicles for this connection. - - - - - Whether the SERVICE JOURNEY INTERCHANGE is guaranteed. Default is 'false'; SERVICE JOURNEY INTERCHANGE is not guaranteed. - - - - - Whether the SERVICE JOURNEY 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. - - - - - - - - Identifier of SERVICE JOURNEY INTERCHANGE. +SIRI v2.0 - - - - - Whether this interchange is an addition to the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the interchange is not an addition. +SIRI v2.1 - - - - - Whether this interchange is a cancellation of a previously announced interchange (or planned according to the long-term timetable. -Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the interchange is not cancelled. +SIRI v2.1 - - - - - - The data producer must provide a reason, e.g. type of error and description, in case he wants to silently remove (instead of cancel) a journey or an interchange from the plan. +SIRI v2.1 - - - - - Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 - - - - - SCHEDULED STOP POINT at which feeder journey arrives. +SIRI v2.0 - - - - - Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. - - - - - For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. -ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 - - - - - Planned time at which feeder VEHICLE is scheduled to arrive. SIRI v2.1 - - - - - Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 - - - - - SCHEDULED STOP POINT at which distributor journet departs. +SIRI v2.0 - - - - - Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. - - - - - For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. -ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 - - - - - Planned time at which distributor VEHICLE is scheduled to depart. SIRI v2.1 - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Werner Kohl MDV + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2003-02-10 + + + 2004-10-31 + + + 2005-02-14 + + + 2005-02-20 + + + 2005-05-11 + + 2007-04-17 + Name Space changes + + 2008-03-26 + Add wrapper tag for Line DIRECTION to help binding to Axis + + 2008-11-17 + Revise to support substitution groups + + 2011-04-18 + - siri_productionTimetable_service.xsd Type on request ValidiyPeriod start and end should be datetime not time .. + - Change to ClosedTimestampRange instead of ClosedTimeRange. + Fix Subscription request to be an element and have extensions . + + 2011-01-19 + SIRI 1.3 Drop use of As Flat Groups for DatedCalls. + + 2012-03-23 + Factor out fropm ProductionTimetable package + +SIRI v2.0 Add ServiceJourneyInterchange (i.e. Monitored Connection) + [VDV] Add additional times to TargetedServiceInterchange MinimumTransferTime, MaximimTransferTime, StandardTransferTime, MaximumAUtomaticWaitTime, StandardWaitTime. + [VDV] Add Public and Contact Details to JourneyInfo + [VDV] Add AimedLatestPassengerAccessTime to TargetedCall + + + 2013-02-11 + SIRI v2.0 Modified ServiceJourneyInterchange SIRI:PT + + +

      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/schema/2.0/xsd/siri_model/}siri_datedVehicleJourney.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG XML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI_PT XML schema. Service Interface for Real-time Information. Production Timetable Service. + Standard +       +       + SIRI-Model Dated Vehicle Joruney. +       + + + + + + A planned VEHICLE JOURNEY taking place on a particular date. + + + + + Type for Planned VEHICLE JOURNEY (Production Timetable Service). + + + + + Identifier for a VEHICLE JOURNEY. + + + + + + + + + + + + + Complete sequence of stops along the route path, in calling order. + + + + + + + + + + Relations of the journey with other journeys, e.g., in case a joining/splitting takes place or the journey substitutes for another one etc. + + + + + + + + Type for previously planned VEHICLE JOURNEY that is removed from the data producer when using incremental updates. +SIRI v2.1 + + + + + A reference to the DATED VEHICLE JOURNEY from a previous PT delivery that is removed by the data producer. + + + + + Optionally identify the VEHICLE JOURNEY indirectly by origin and destination and the scheduled times at these stops. + + + + + TRAIN NUMBERs for journey. + + + + + + TRAIN NUMBER assigned to VEHICLE JOURNEY. + + + + + + + + + + + General info elements that apply to all journeys of timetable version unless overriden. + + + + + Description of the origin stop (vehicle signage) to show on vehicle, Can be overwritten for a journey, and then also section by section by the entry in an Individual Call. (+SIRI 2.0) + + + + + Description of the 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. (Unbounded since SIRI 2.0) + + + + + Additional Text associated with LINE. (Unbounded since SIRI 2.0) + + + + + Whether journey is first or last jouurney of day. +SIRI v2.0 + + + + + + + If the journey is an alteration to a timetable, indicates the original journey, and the nature of the difference. + + + + + Use of simple reference is deprecated + + + + Refecence to a VEHICLE JOURNEY framed by the day. SIRI 2.0 + + + + + + + + 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 cancellation of a journey in the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the journey is not cancelled. + + + + + + + + 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 SERVICE JOURNEY INTERCHANGE between two journeys. +SIRI v2.0 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + A planned SERVICE JOURNEY INTERCHANGE from a journey. +SIRI v2.0 + + + + + + + + + + + + + + + + + + + + + + + + + + + A planned SERVICE JOURNEY INTERCHANGE to a journey. +SIRI v2.0 + + + + + + + + + + + + + + + + + + + + + + + + + + + A planned SERVICE JOURNEY INTERCHANGE between two journeys. +SIRI v2.0 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Type for a previously planned SERVICE JOURNEY INTERCHANGE that a data producer wants to silently remove from the plan (because it is erroneous data). Careful: Removal is different from Cancellation. +SIRI v2.1 + + + + + + + + + + + + + + + + + + + + + + + + + + Time Elements for SERVICE JOURNEY INTERCHANGE. + + + + + Elements for INTERCHANGE WAIT TIME. + + + + + + + + Elements for INTERCHANGE TRANSFER duration. + + + + + Standard transfer duration for INTERCHANGE. SIRI v2,0 + + + + + Minimum transfer duration for INTERCHANGE. SIRI v2,0 + + + + + Maximum transfer duration for INTERCHANGE. SIRI v2,0 + + + + + + + Elements for INTERCHANGE WAIT TIME. + + + + + Standard wait time for INTERCHANGE. SIRI v2,0 + + + + + Maximum time that Distributor will wait for Feeder for INTERCHANGE. SIRI v1.0 + + + + + Maximum automatic wait time that Distributor will wait for Feeder for INTERCHANGE. +SIRI v2.0 + + + + + + + + Complete sequence of stops along the route path, in calling order. + + + + + Type for Planned VEHICLE JOURNEY Stop (Production Timetable Service). + + + + + + + Whether this DATED CALL is an addition to the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to false: the journey is not an addition. + + + + + Whether this DATED CALL is a cancellation of a previously announced call (or planned according to the long-term timetable). Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the journey is not cancelled. + + + + + + + Text annotation that applies to this call. + + + + + + + Information on any planned distributor connections (deprecated from SIRI V2.0 ... see 2 next attributes) + + + + + Information on any planned feeder connections. SIRI 2.0 + + + + + Information on any planned distributor connections. SIRI 2.0 + + + + + + + + + Planned Connection between two VEHICLE JOURNEYs. + + + + + + + Reference to a (dated) distributor VEHICLE JOURNEY. + + + + + + Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY 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. + + + + + + + + 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. + + + + + + + + + Connection between two stops within a connection area. Used within the context of one or other end. + + + + + Identifier of CONNECTION LINk. + + + + + + + + + + Times for making SERVICE JOURNEY INTERCHANGE. + + + + + Default time (Duration) needeed to traverse SERVICE JOURNEY INTERCHANGE from feeder to distributor. + + + + + Time needeed by a traveller whis is familiar with SERVICE JOURNEY INTERCHANGE to traverse it. If absent, use DefaultDuration. + + + + + Time needeed by a traveller whis is not familiar with SERVICE JOURNEY INTERCHANGE to traverse it. If absent, use DefaultDuration and a standard weighting. + + + + + Time needeed by a traveller wos is mobility impaired to traverse SERVICE JOURNEY INTERCHANGE. If absent, use DefaultDuration and a standard impaired travel speed. + + + + + + + Properties of SERVICE JOURNEY INTERCHANGE. + + + + + Whether the passenger can remain in VEHICLE (i.e. BLOCKlinking). Default is 'false': the passenger must change vehicles for this connection. + + + + + Whether the SERVICE JOURNEY INTERCHANGE is guaranteed. Default is 'false'; SERVICE JOURNEY INTERCHANGE is not guaranteed. + + + + + Whether the SERVICE JOURNEY 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. + + + + + + + + Identifier of SERVICE JOURNEY INTERCHANGE. +SIRI v2.0 + + + + + Whether this interchange is an addition to the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the interchange is not an addition. +SIRI v2.1 + + + + + Whether this interchange is a cancellation of a previously announced interchange (or planned according to the long-term timetable. +Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the interchange is not cancelled. +SIRI v2.1 + + + + + + The data producer must provide a reason, e.g. type of error and description, in case he wants to silently remove (instead of cancel) a journey or an interchange from the plan. +SIRI v2.1 + + + + + Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 + + + + + SCHEDULED STOP POINT at which feeder journey arrives. +SIRI v2.0 + + + + + Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. + + + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. +ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 + + + + + Planned time at which feeder VEHICLE is scheduled to arrive. SIRI v2.1 + + + + + Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 + + + + + SCHEDULED STOP POINT at which distributor journet departs. +SIRI v2.0 + + + + + Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. + + + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. +ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 + + + + + Planned time at which distributor VEHICLE is scheduled to depart. SIRI v2.1 + + + +       diff --git a/xsd/siri_model/siri_estimatedVehicleJourney.xsd b/xsd/siri_model/siri_estimatedVehicleJourney.xsd index 88933aa7..9cce5107 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney.xsd @@ -1,472 +1,472 @@ - - - - - - main schema - e-service developers - CEN TC278 WG3 SG7 Team - Werner Kohl MDV - Europe - Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2003-02-10 - - - 2004-10-31 - - - 2005-02-14 - - - 2005-02-20 - - - 2005-05-11 - - - 2007-04-17 - - - - 2008-03-26 - - - - 2008-11-17 - - - - 2011-01-19 - - - - 2012-03-23 - - - -

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

      -

      This sub-schema describes the Estimated Timetable Service.

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

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

      +

      This sub-schema describes the Estimated Timetable Service.

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

      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/schema/2.0/xsd/siri_model/}siri_facility.xsd - [ISO 639-2/B] ENG - CEN - - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from TransModel and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Common Facility Elements - Standard -       -       - SIRi Facility model elemenys -       - - - - - - - - - - - - - - - - - Type for identifier of a Faclility. - - - - - - Reference to a Facility. - - - - - Type for reference to a Faclility. - - - - - - - - - - Type for description of the MONITORED FACILITY itself. - - - - - Identfier of Facility. - - - - - Textual description of the facility. (Unbounded since SIRI 2.0) - - - - - 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 the 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 category of a facility. - - - - - - - - - - - - - - - - - - Summary information about Facility. Used in DISCOVERY. - - - - - - Whether real-time data is available for the stop. Default is 'true'. - - - - - Description of the facility (without its status) - - - - - - - - Allowed values for the status of a MONITORED FACILITY. - - - - - - - - - - - - - Allowed values for changes to the status of a facility. - - - - - - - - - - Allowed values for TypeOfCounting. - - - - - - - - - - - - - - - Allowed values for trend of a counting. - - - - - - - - - - - - - - - - Allowed values for units of what is counted - bay: parking bay for cars, bicycle, scooter, etc - otherSpaces: any other kind of spaces: lockers, standing spaces, toilets, etc. - devices: electronic devices (audio guide, headphones, etc.) and physical devices (walking stick, wheelchair, etc.) - vehicles: any type of vehicles (cycle, car, scooter, hoverboard, motorbike, etc.) - kW (kiloWatt) or kWh (kiloWatt-hour): means that an available or consumed power is measured - mAh (milliAmpere per hour): typically used for battery charging level - litres and cubicMeters: means that a volume is measured - squareMeters: means that a surface is measured - meters: means that a distance is measured - kg (kilogram): means that a mass is measured - A (Ampere): means that an electric current is measured - C (degree Celsius): means that a temperature is measured - other: use of "other" requires the additional open ended TypeOfCountedFeature (monitoredCountingStructure) to be filled - - - - - - - - - - - - - - - - - - - - - - - - - Description of the status of a MONITORED FACILITY. - - - - - Status of the facility. - - - - - Description of the facility Status. (Unbounded since SIRI 2.0) - - - - - Accessibility of the facility. - - - - - - - - Location of the MONITORED FACILITY. - - - - - Group of Facility accessibility elements. - - - - - Group of Facility accessibility elements. - - - - - - - - Monitored counted values. - - - - - Nature of what is counted. - - - - - Unit of type for what is being counted - - - - - Open ended type or refined classification of what is counted (complement to the information coming from the facility type itself) - - - - - - Counted value - - - - - Value as a percentage (0.0 to 100.0) of the maximum possible value - - - - - - Trend of the count - - - - - Accuracy of the count, as a percentage (0.0 to 100.0), the percentage being a + or - maximum deviation from the provided value - - - - - Description of what is counted - - - - - List of the IDs of the counted items: usefull mainly for reservation and detailed information purposes - - - - - - IDs of a counted item - - - - - - - - - - - - Description of any change concerning a MONITORED FACILITY New structure defined in SIRI XSD 1.1 for Facilities Management. - - - - - Description of any change concerning a MONITORED FACILITY New structure defined in SIRI XSD 1.1 for Facilities Management. - - - - - - Facility affected by condition. - - - - - - - Status of Facility. - - - - - - - - - - - - New position of the Facility referenced by the FacilityRef or described in the FacilityStructure - - - - - - 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. - - - - - - - - - Allowed values for actions to remedy a facility 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. (Unbounded since SIRI 2.0) - - - - - Validity period for the remedy - - - - - - - - - - Allowed values for the monitoring conditions (frequency of measurement, etc): an automatic monitoring of the status of a lift with pushed alert in case of incident is very different from a daily manual/visual check. - - - - - Mean time interval between two measurements. - - - - - How monitoring is automatic, manual, etc. - - - - - When the monitoring is in effect. If absent always. - - - - - - - - Allowed values for the types of monitoring: automatic or manual - describing the hardware transducer (video, GPS/Radio, in-road sensors, etc.) doesn't seeme useful for SIRI. - - - - - - - - - - Allowed values for the type for Description of the monitoring conditions (frequency of mesurement, etc): an automatic monitoring of the status of a lift with pushed alert in case of incident is very different from a daily manual/visual check. - - - - - Date and tme 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. - - - - - - - - A change to the availaibility of EQUIPMENT. Basic structure defined in the first 1.0 SIRI XSd. - - - - - Type for Availaibility Change of EQUIPMENT. - - - - - Reference to an EQUIPMENT. - - - - - Description of EQUIPMENT. (Unbounded since SIRI 2.0) - - - - - Reference to a TYPE OF EQUIPMENT. - - - - - Period for which change to EQUIPMENT status applies applies. If omitted, indefinite period. - - - - - Availability status of the EQUIPMENT. Default is 'notAvailable'. - - - - - 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. - - - - - - - - - Type for 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 or more MobilityFacility instances to specify which types of mobility access are available (true) or not available (false). For example suitableForWheelChair, or stepFreeAccess. - - - - - Classification of Mobility Facility type - Based on Tpeg pti23. - - - - - - - Elements describing nature of disruption. - - - - - Information about a change of the formation (e.g. TRAIN composition) or changes of vehicles within the formation. +SIRI v2.1 - - - - - Information about a change of Equipment availability at stop or on vehicle that may affect access or use. - - - - - This sequence is here only for compatibility reasons between Siri 1.0 and Siri 1.1 - - - - - - - - - - Classification of vehicle energy type. See Transmodel TypeOfFuel. +SIRI v2.1 - - - - - Values for vehicle fuel type. Use of 'other' requires the additional open ended OtherTypeOfFuel to be filled. - - - - - An arbitrary vehicle fuel classification. - - - - -       + + + + + + 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 + + + + 2012-03-23 + + + +

      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/schema/2.0/xsd/siri_model/}siri_facility.xsd + [ISO 639-2/B] ENG + CEN + + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from TransModel and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Common Facility Elements + Standard +       +       + SIRi Facility model elemenys +       + + + + + + + + + + + + + + + + + Type for identifier of a Faclility. + + + + + + Reference to a Facility. + + + + + Type for reference to a Faclility. + + + + + + + + + + Type for description of the MONITORED FACILITY itself. + + + + + Identfier of Facility. + + + + + Textual description of the facility. (Unbounded since SIRI 2.0) + + + + + 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 the 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 category of a facility. + + + + + + + + + + + + + + + + + + Summary information about Facility. Used in DISCOVERY. + + + + + + Whether real-time data is available for the stop. Default is 'true'. + + + + + Description of the facility (without its status) + + + + + + + + Allowed values for the status of a MONITORED FACILITY. + + + + + + + + + + + + + Allowed values for changes to the status of a facility. + + + + + + + + + + Allowed values for TypeOfCounting. + + + + + + + + + + + + + + + Allowed values for trend of a counting. + + + + + + + + + + + + + + + + Allowed values for units of what is counted + bay: parking bay for cars, bicycle, scooter, etc + otherSpaces: any other kind of spaces: lockers, standing spaces, toilets, etc. + devices: electronic devices (audio guide, headphones, etc.) and physical devices (walking stick, wheelchair, etc.) + vehicles: any type of vehicles (cycle, car, scooter, hoverboard, motorbike, etc.) + kW (kiloWatt) or kWh (kiloWatt-hour): means that an available or consumed power is measured + mAh (milliAmpere per hour): typically used for battery charging level + litres and cubicMeters: means that a volume is measured + squareMeters: means that a surface is measured + meters: means that a distance is measured + kg (kilogram): means that a mass is measured + A (Ampere): means that an electric current is measured + C (degree Celsius): means that a temperature is measured + other: use of "other" requires the additional open ended TypeOfCountedFeature (monitoredCountingStructure) to be filled + + + + + + + + + + + + + + + + + + + + + + + + + Description of the status of a MONITORED FACILITY. + + + + + Status of the facility. + + + + + Description of the facility Status. (Unbounded since SIRI 2.0) + + + + + Accessibility of the facility. + + + + + + + + Location of the MONITORED FACILITY. + + + + + Group of Facility accessibility elements. + + + + + Group of Facility accessibility elements. + + + + + + + + Monitored counted values. + + + + + Nature of what is counted. + + + + + Unit of type for what is being counted + + + + + Open ended type or refined classification of what is counted (complement to the information coming from the facility type itself) + + + + + + Counted value + + + + + Value as a percentage (0.0 to 100.0) of the maximum possible value + + + + + + Trend of the count + + + + + Accuracy of the count, as a percentage (0.0 to 100.0), the percentage being a + or - maximum deviation from the provided value + + + + + Description of what is counted + + + + + List of the IDs of the counted items: usefull mainly for reservation and detailed information purposes + + + + + + IDs of a counted item + + + + + + + + + + + + Description of any change concerning a MONITORED FACILITY New structure defined in SIRI XSD 1.1 for Facilities Management. + + + + + Description of any change concerning a MONITORED FACILITY New structure defined in SIRI XSD 1.1 for Facilities Management. + + + + + + Facility affected by condition. + + + + + + + Status of Facility. + + + + + + + + + + + + New position of the Facility referenced by the FacilityRef or described in the FacilityStructure + + + + + + 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. + + + + + + + + + Allowed values for actions to remedy a facility 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. (Unbounded since SIRI 2.0) + + + + + Validity period for the remedy + + + + + + + + + + Allowed values for the monitoring conditions (frequency of measurement, etc): an automatic monitoring of the status of a lift with pushed alert in case of incident is very different from a daily manual/visual check. + + + + + Mean time interval between two measurements. + + + + + How monitoring is automatic, manual, etc. + + + + + When the monitoring is in effect. If absent always. + + + + + + + + Allowed values for the types of monitoring: automatic or manual - describing the hardware transducer (video, GPS/Radio, in-road sensors, etc.) doesn't seeme useful for SIRI. + + + + + + + + + + Allowed values for the type for Description of the monitoring conditions (frequency of mesurement, etc): an automatic monitoring of the status of a lift with pushed alert in case of incident is very different from a daily manual/visual check. + + + + + Date and tme 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. + + + + + + + + A change to the availaibility of EQUIPMENT. Basic structure defined in the first 1.0 SIRI XSd. + + + + + Type for Availaibility Change of EQUIPMENT. + + + + + Reference to an EQUIPMENT. + + + + + Description of EQUIPMENT. (Unbounded since SIRI 2.0) + + + + + Reference to a TYPE OF EQUIPMENT. + + + + + Period for which change to EQUIPMENT status applies applies. If omitted, indefinite period. + + + + + Availability status of the EQUIPMENT. Default is 'notAvailable'. + + + + + 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. + + + + + + + + + Type for 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 or more MobilityFacility instances to specify which types of mobility access are available (true) or not available (false). For example suitableForWheelChair, or stepFreeAccess. + + + + + Classification of Mobility Facility type - Based on Tpeg pti23. + + + + + + + Elements describing nature of disruption. + + + + + Information about a change of the formation (e.g. TRAIN composition) or changes of vehicles within the formation. +SIRI v2.1 + + + + + Information about a change of Equipment availability at stop or on vehicle that may affect access or use. + + + + + This sequence is here only for compatibility reasons between Siri 1.0 and Siri 1.1 + + + + + + + + + + Classification of vehicle energy type. See Transmodel TypeOfFuel. +SIRI v2.1 + + + + + Values for vehicle fuel type. Use of 'other' requires the additional open ended OtherTypeOfFuel to be filled. + + + + + An arbitrary vehicle fuel classification. + + + + +       diff --git a/xsd/siri_model/siri_feature_support.xsd b/xsd/siri_model/siri_feature_support.xsd index f553ac1d..48ce0738 100644 --- a/xsd/siri_model/siri_feature_support.xsd +++ b/xsd/siri_model/siri_feature_support.xsd @@ -1,145 +1,145 @@ - - - - - - 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 - - - 2012-03-22 - - - -

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

      -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_feature.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIG CML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Common DomainModel elements. - Standard -       -       -       - - - - Type for identifier of a TYPE OF PRODUCT CATEGORY. - - - - - - Type for reference to a TYPE OF PRODUCT CATEGORY. - - - - - - - - - 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. - - - - - Type for reference to a ServiceCategory. - - - - - - - - - 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. - - - - - - 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. - - - - - 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. - - - - - - Type for reference to a Feature Code. - - - - - - -       + + + + + + 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 + + + 2012-03-22 + + + +

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

      +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_feature.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG CML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Common DomainModel elements. + Standard +       +       +       + + + + Type for identifier of a TYPE OF PRODUCT CATEGORY. + + + + + + Type for reference to a TYPE OF PRODUCT CATEGORY. + + + + + + + + + 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. + + + + + Type for reference to a ServiceCategory. + + + + + + + + + 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. + + + + + + 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. + + + + + 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. + + + + + + Type for reference to a Feature Code. + + + + + + +       diff --git a/xsd/siri_model/siri_interchangeJourney.xsd b/xsd/siri_model/siri_interchangeJourney.xsd index 4a092281..1b949ab1 100644 --- a/xsd/siri_model/siri_interchangeJourney.xsd +++ b/xsd/siri_model/siri_interchangeJourney.xsd @@ -1,88 +1,88 @@ - - - - - - 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 - 2012-03-29 - Factored out of conection timnetable servcie - - 2012-03-20 - +SIRI v2.0 - - -

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

      -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/siri/2.0/xsd/}siri_connectionTimetable_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - -SIRI-CT Interchange journey for Service Interface for Real-time Information. Connection Timetable Service. - Standard -       -       - SIRI-CT Interchange journey Connection Timetable Service. -       - - - - - - Type for feeder or Distributor Journey info about a VEHICLE JOURNEY. - - - - - - - - - - Whether there is real-time information available for journey. Default is 'true'. - - - - - On a Distributor journey, a timetabled departure time of the VEHICLE JOURNEY from the CONNECTION LINK for the SERVICE JOURNEY INTERCHANGE. On a Feeder journey a Timetabled arrival time of the VEHICLE JOURNEY at the CONNECTION link for the SERVICE JOURNEY INTERCHANGE. - - - - - - -       + + + + + + 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 + 2012-03-29 + Factored out of conection timnetable servcie + + 2012-03-20 + +SIRI v2.0 + + +

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

      +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/siri/2.0/xsd/}siri_connectionTimetable_service.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG XML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + -SIRI-CT Interchange journey for Service Interface for Real-time Information. Connection Timetable Service. + Standard +       +       + SIRI-CT Interchange journey Connection Timetable Service. +       + + + + + + Type for feeder or Distributor Journey info about a VEHICLE JOURNEY. + + + + + + + + + + Whether there is real-time information available for journey. Default is 'true'. + + + + + On a Distributor journey, a timetabled departure time of the VEHICLE JOURNEY from the CONNECTION LINK for the SERVICE JOURNEY INTERCHANGE. On a Feeder journey a Timetabled arrival time of the VEHICLE JOURNEY at the CONNECTION link for the SERVICE JOURNEY INTERCHANGE. + + + + + + +       diff --git a/xsd/siri_model/siri_journey.xsd b/xsd/siri_model/siri_journey.xsd index 6f240fa8..b4335f26 100644 --- a/xsd/siri_model/siri_journey.xsd +++ b/xsd/siri_model/siri_journey.xsd @@ -1,1903 +1,1903 @@ - - - - - - main schema - e-service developers - Cen TC278 WG3 SG7 Team - Europe - Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2004-03-05 - - - 2004-10-06 - - - 2005-05-11 - - - 2005-11-15 - - - 2007-03-29 - - - 2008-11-13 - - - - 2011-04-18 - - - - 2012-03-22 - - - - 2012-04-27 - - - - 2013-01-25 - - - - 2013-02-11 - - - - 2014-06-20 - - - -

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

      -

      This subschema defines common journey elements.

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri/}siri_journey.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd - - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIG CML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of common Journey elements - Standard -       -       - SIRI Common Journey Model. -       - - - - - - - - - - - - - - - - Elements describing a VEHICLE JOURNEY. Values for these elements can be specified on an annual schedule and will be inherited, unless overriden, onto the production timetable and then onto the individul DATED VEHICLE JOURNEYs of the timetable. Each real-time journey (e.g. ESTIMATED VEHICLE JOURNEY or MONITORED VEHICLE JORUNEY) takes its values from the DATED VEHICLE JOURNEY that it follows. The absence of a value on an entity at a given level indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity. - - - - - For train services with named journeys. Train name, e.g. “West Coast Express”. If omitted: No train name. Inherited property. (Unbounded since SIRI 2.0) - - - - - - Contact details for use by members of public. +SIRI v2.0 - - - - - Contact details for use by operational staff. +SIRI v2.0 - - - - - - - Type for Simple Contact Details. - - - - - Phone number +SIRI v2.0 - - - - - Url for contact +SIRI v2.0 - - - - - - - - Common information about a VEHICLE JOURNEY. (Similar to VDV TripInfo) - - - - - - - - - - - End names for journey. - - - - - - Name of the origin of the journey. (Unbounded since SIRI 2.0) - - - - - Short name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as Origin Name. - - - - - DIRECTION name shown for jurney at the origin. +SIRI v2.0 - - - - - Names of VIA points, used to help identify the LINE, for example, Luton to Luton via Sutton. Currently 3 in VDV. Should only be included if the detail level was requested. - - - - - Reference to a DESTINATION. - - - - - Description of the destination stop (vehicle signage), Can be overwritten for a journey, and then also section by section by the entry in an individual CALl. (Unbounded since SIRI 2.0) - - - - - Short name of the DESTINATION.of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as DestinationName. (Unbounded since SIRI 2.0) - - - - - Origin name shown for jourey at the destination +SIRI v2.0 - - - - - - - Type for VIA NAMes structure. - - - - - - - Relative priority to give to VIA name in displays. 1=high. Default is 2. +SIRI v2.0 - - - - - - - - - - Type for Information about a DESTINATION. - - - - - Identifer of Destinatioin - - - - - Name of Destination - - - - - - - The name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. - - - - - Names of VIA points, used to help identify the LINEfor example, Luton to Luton via Sutton. Currently 3 in VDV. Should only be included if the detail level was requested. - - - - - The name of the DESTINATION of the journey; used to help identify the VEHICLE to the public. Note when used in a CALL, this is the Dynamic Destination Display: since vehicles can change their destination during a journey, the destination included here should be what the VEHICLE will display when it reaches the stop. - - - - - - Call times for journey. - - - - - Whether this is a Headway Service, that is shown as operating at a prescribed interval rather than to a fixed timetable. Default is 'false'. - - - - - Timetabled departure time from Origin. - - - - - Timetabled arrival time at Destination. - - - - - - - - Whether journey is first or last journey of day. +SIRI v2.0 - - - - - Additional descriptive text associated with journey. Inherited property. - - - - - Description of a DIRECTION. - - - - - Type for DIRECTION. - - - - - Identifer of DIRECTION, - - - - - Description of DIRECTION. (Unbounded since SIRI 2.0) - - - - - - - - Operational information about the monitored VEHICLE JOURNEY. - - - - - - - - Refercence to other VEHICLE Journeys (+SIRI v2.0) - - - - - A reference to the DRIVER or Crew currently logged in to operate a monitored VEHICLE. May be omitted if real-time data is not available - i.e. it is timetabled data. +SIRI v2.0 - - - - - The name oo the Driver or Crew +SIRI v2.0 - - - - - - - Operational information about the monitored VEHICLE JOURNEY. - - - - - - - - - Operational information about the monitored VEHICLE JOURNEY. - - - - - BLOCK that VEHICLE is running. - - - - - COURSE OF JOURNEY ('Run') that VEHICLE is running. - - - - - - - Type for Progress between stops. - - - - - The total distance in metres between the previous stop and the next stop. - - - - - Percentage along link that VEHICLE has travelled. - - - - - - - - - Type for Abstract CALL at stop. - - - - - - - - - Elements describing the targeted CALL of a VEHICLE at a stop. - - - - - - - - - - - Elements describing the arrival of a VEHICLE at a stop. - - - - - - - - Assignment of planned arrival at scheduled STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. +SIRI v2.0. - - - - - - - - - Elements describing the departure of a VEHICLE from a stop. - - - - - - - - - - - - - - Type for Abstract CALL at stop. - - - - - - - - Elements describing the arrival status of a VEHICLE at a stop. - - - - - - - - - - Assignment of planned, expected and/or recorded arrival at STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. +SIRI v2.0. - - - - - - - - - - Elements describing the departure status of a VEHICLE from a stop. - - - - - - - - - - - - - - - - - - - Elements describing the CALL Properties Values for these elements can be specified on an production VEHICLE JOURNEY CALL. Each real-time journey CALL takes its values from the corresponding dated VEHICLE JOURNEY CALL. The absence of a value on an real-time CALL l indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity. - - - - - - Whether this is a Hail and Ride Stop. Default is 'false'. - - - - - Whether Vehicle stops only if requested explicitly by passenger. Default is 'false'. - - - - - Origin to show for the VEHICLE at the specific stop (vehicle signage), if different to the Origin Name for the full journey. (+Siri 2.0) - - - - - Destination to show for the VEHICLE at the specific stop (vehicle signage), if different to the Destination Name for the full journey. - - - - - - - Annotations of the CALL. - - - - - Text annotation that applies to this CALL. - - - - - - - - Type for CALLing pattern for JOURNEY PATTERN. - - - - - - - - Type Onwards CALLs at stop. - - - - - - - - - - - - - - - - - Elements describing the CALL. Values for these elements can be specified on an production VEHICLE JOURNEY CALL. Each real-time journey CALL takes its values from the corresponding dated VEHICLE JOURNEY CALL. The absence of a value on an real-time CALL l indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity. - - - - - - - - - - - - - - Elements for Arrival in onward CALl. - - - - - - - - - Latest time at which a VEHICLE will arrive at stop. +SIRI v2.1 - - - - - Prediction quality, either as approximate level, or more quantitative percentile range of predictions that will fall within a given range of times. +SIRI v2.0 - - - - - - If the producer is (temporarily) not able to deliver real-time predictions (e.g. because of a connection loss), he has various options (and combinations of them) to inform the consumer: -(i) set Monitored to 'false' -(ii) transmit ExpectedArrivalTime together with "PredictionInaccurate=true" -(iii) drop/omit ExpectedArrivalTime -(iv) set ArrivalStatus to 'noReport' -However, this might introduce ambiguity: e.g. option (iii) might be interpreted as "on time" by one consumer, but also as "indefinite delay" by another consumer. -To avoid this, the producer should transmit xxxPredictionUnknown instead of any expected times. +SIRI v2.1 - - - - - - - - Elements for departure in ONWARD CALL. - - - - - - - - - Expected departure time of VEHICLE without waiting time due to operational actions. For people at stop this would normally be shown if different from Expected departure time. So if servcie decides not to wait may leave earler than expected departure time +SIRI v2.0. - - - - - Earliest time at which VEHICLE may leave the stop. Used to secure connections. Used for passenger announcements. Passengers must be at boarding point by this time to be sure of catching VEHICLE. i.e. "Vehicle will not leave before this time" - may be revised from original aimed time. +SIRI v2.0 - - - - - Prediction quality, either as approximate level, or more quantitative percentile range of predictions that will fall within a given range of times. +SIRI v2.0 - - - - - - If the producer is (temporarily) not able to deliver real-time predictions (e.g. because of a connection loss), he has various options (and combinations of them) to inform the consumer: -(i) set Monitored to 'false' -(ii) transmit ExpectedDepartureTime together with "PredictionInaccurate=true" -(iii) drop/omit ExpectedDepartureTime -(iv) set DepartureStatus to 'noReport' -However, this might introduce ambiguity: e.g. option (iii) might be interpreted as "on time" by one consumer, but also as "indefinite delay" by another consumer. -To avoid this, the producer should transmit xxxPredictionUnknown instead of any expected times. +SIRI v2.1 - - - - - - - - Elements describing the HEADWAY INTERVALs. - - - - - - - - - Elements describing the distance from the stop of a VEHICLE. +SIRI v2.0. - - - - - Distance of VEHICLE from stop of CALL as measured along ROUTE track. Only shown if detail level is 'calls' or higher. Positive value denotes distance before stop. +SIRI v2.0. - - - - - Count of stops along SERVICE PATTERN between current position of VEHICLE and stop of CALL as measured along ROUTE track. Only shown if detail level is 'calls' or higher. +SIRI v2.0. - - - - - - - Type for Prediction Quality quantifcation. - - - - - An approxiimate characterisation of prediction quality as one of five values. +SIRI v2.0 - - - - - - Percentile associated with range as specified by lower and upper bound. +SIRI v2.0 - - - - - Lower bound on time of prediction for confidence level if different from defaults. +SIRI v2.0 - - - - - Upper bound on time of prediction for confidence level if different from defaults. +SIRI v2.0 - - - - - - - - - Area that encompasses the scheduled flexible stop locations according to the planned timetable. +SIRI v2.1 - - - - - Reference to the scheduled location or flexible area. +SIRI v2.1 - - - - - Name or description (e.g. address) of the scheduled location or flexible area. +SIRI v2.1 - - - - - - Elements for location of flexible stops or service that allows pickup anywhere in a designated area. +SIRI v2.1 - - - - - - - - Area that encompasses the expected flexible stop locations according to the real-time prediction. - - - - - - Name or description (e.g. address) of the expected location or flexible area. - - - - - Area that encompasses the actually recorded flexible stop locations. - - - - - - Name or description (e.g. address) of the actually recorded location or flexible area. - - - - - - - - Elements for assignment of a SCHEDULED STOP POINT to a specific QUAY or platform. +SIRI v2.1 - - - - - Physical QUAY to use according to the planned timetable. +SIRI v2.0 - - - - - Scheduled Platform name. Can be used to indicate platfrom change. +SIRI v2.0 - - - - - Physical QUAY to use according to the real-time prediction. +SIRI v2.0 - - - - - Expected Platform name. Can be used to indicate real-time prediction. +SIRI v2.1 - - - - - Physical QUAY actually used. +SIRI v2.0 - - - - - Actual Platform name. Can be used to indicate recorded platform. +SIRI v2.1 - - - - - - - - - Elements for assignment of a SCHEDULED STOP POINT to a specific BOARDING POSITION or location on a QUAY. +SIRI v2.1 - - - - - Physical BOARDING POSITION to use according to the planned timetable. - - - - - Scheduled BOARDING POSITION name. Can be used to indicate boarding position change. - - - - - Physical BOARDING POSITION to use according to the real-time prediction. - - - - - Expected BOARDING POSITION name. Can be used to indicate real-time prediction. - - - - - Actually recorded BOARDING POSITION. Can be used to indicate the actually used boarding position. - - - - - Recorded BOARDING POSITION name. Can be used to indicate the actually used boarding position. - - - - - - - - Type for assignment of a SCHEDULED STOP POINT to a physical location, in particular to a QUAY or BOARDING POSITION. +SIRI v2.0. - - - - - - - - - - - - - Type for assignment of a SCHEDULED STOP POINT to a physical location, in particular to a QUAY or BOARDING POSITION, according to the planned timetable. +SIRI v2.0. - - - - - - - Physical QUAY to use according to the planned timetable. +SIRI v2.0 - - - - - Scheduled Platform name. +SIRI v2.0 - - - - - - - - Physical BOARDING POSITION to use according to the planned timetable. +SIRI v2.1 - - - - - Scheduled BOARDING POSITION name. +SIRI v2.1 - - - - - - - - - - - - - Indicates the type of a nested QUAY in case of detailed STOP PLACE models. -A QUAY may be part of a group of QUAYs, or may be divided into sectors, i.e., smaller sub-QUAYs. +SIRI v2.1 - - - - - - Whether the prediction for a specific stop or the whole journey is considered to be of a useful accuracy or not. Default is 'false', i.e. prediction is considered to be accurate. -If prediction is degraded, e.g. because of a situation, PredictionInaccurate is used to indicate a lowered quality of data. Inherited property. PredictionInaccurate can be used in combination with InCongestion, but is more general. - - - - - Can be used to inform the passenger about the reason for a change of the prediction (in)accuracy in case PredictionInaccurate is set to 'true'. +SIRI v2.1 - - - - - An approximate figure of how occupied the journey is after departing from a given stop, e.g. 'manySeatsAvailable' or 'standingRoomOnly'. If omitted: Passenger load is unknown. -Occupancies and capacities for individual VEHICLEs, e.g. parts of a COMPOUND TRAIN, can also be specified in more detail for the departure on CALL level. - - - - - - Target arrival time of VEHICLE at stop according to latest working timetable. - - - - - Observed time of arrival of VEHICLE at stop. - - - - - Estimated time of arriival of VEHICLE at stop . - - - - - Classification of the timeliness of the visit according to a fixed list of values. If not specified, same as DepartureStatus. - - - - - Text annotation to be used in cases where ArrivalStatus is set to 'cancelled'. +SIRI v2.1 - - - - - Arbitrary text string to show to indicate the status of the departure of the VEHICLE for example, “Enroute”, “5 Km”, “Approaching”. May depend on the policy of the OPERATOR, for example show “Approaching” if less than 200metres away from stop. +SIRI v2.0 - - - - - Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicle to arrive at. -Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is: -(i) any arrival platform on any related dated timetable element, -(ii) any departure platform name on this estimated element; -(iii) any departure platform name on any related dated timetable CALL. - - - - - Type of boarding and alighting allowed at stop. Default is 'Alighting'. - - - - - Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). If not given, assume same as for departure. +SIRI v2.1 - - - - - Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. +SIRI v2.1 -Examples: -- "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle arriving at sector A first when approaching the QUAY with sectors A-B-C-D. If the arriving vehicle is represented as an arrow, "towards A" would be abstracted as "=> A-B-C-D". -- "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle arriving at this reference point first when approaching the QUAY. If the arriving vehicle is represented as an arrow, "towards 0" would be abstracted as "=> 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). -It is advised to specify a reference point that is meaningful for passengers on location. - - - - - - OPERATORs of of service up until arrival. May change for departure. +SIRI v2.0. - - - - - - Arrival times for CALL. - - - - - - - - - - - - - Target departure time of VEHICLE from stop according to latest working timetable. - - - - - Observed time of departure of VEHICLE from stop. - - - - - Estimated time of departure of VEHICLE from stop, most likely taking into account all control actions such as waiting. - - - - - Latest target time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. +SIRI 2.0 - - - - - Latest expected time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. +SIRI 2.0 - - - - - Classification of the timeliness of the departure part of the CALL, according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are still classified as on-time. Applications may use this to guide their own presentation of times. - - - - - Text annotation to be used in cases where DepartureStatus is set to 'cancelled'. +SIRI v2.1 - - - - - Arbitrary text string to show to indicate the status of the departure of the vehicle, for example, “Boarding”, “GatesClosed”. +SIRI v2.0 - - - - - Departure QUAY (bay or platform) name. Default taken from planned timetable. - - - - - Nature of boarding allowed at stop. Default is 'Boarding'. - - - - - Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). +SIRI v2.1 - - - - - Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. +SIRI v2.1 -Examples: -- "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle departing in the direction of sector A on a QUAY with sectors A-B-C-D. If the departing vehicle is represented as an arrow, "towards A" would be abstracted as "<= A-B-C-D". -- "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle departing in the direction of this reference point. If the departing vehicle is represented as an arrow, "towards 0" would be abstracted as "<= 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). -It is advised to specify a reference point that is meaningful for passengers on location. - - - - - Real-time occupancies of a VEHICLE and reservations after departing from a given stop. +SIRI v2.1 - - - - - Real-time capacities (number of available seats) of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. +SIRI v2.1 - - - - - OPERATORs of service for departure and onwards. May change from that for arrival. +SIRI v2.0. - - - - - Recorded occupancies of a VEHICLE and reserved seats after departing from a given stop. +SIRI v2.1 - - - - - Recorded capacities of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. +SIRI v2.1 - - - - - - Departure times for CALL. - - - - - - - - - - - - Passenger arrival times at STOP PLACE in order to meet VEHICLE departure times for CALL. - - - - - - - - - - For frequency based services, target interval between vehicles at stop. - - - - - For frequency based services, expected interval between vehicles at stop. - - - - - For frequency based services, observed interval between vehicles at stop. - - - - - - Provides information about relations to other journeys. +SIRI v2.1 - - - - - - - - - - Specifies the type of the relation, e.g., joining, splitting, replacement etc. +SIRI v2.1 - - - - - - - - - Specifies which CALL or JOURNEY PART of the JOURNEY has a JOURNEY RELATION. +SIRI v2.1 - - - - - - Information about the stop at which the JOURNEY is related to another JOURNEY. +SIRI v2.1 - - - - - Information about the JOURNEY PARTs for which the JOURNEY has a JOURNEY RELATION. +SIRI v2.1 - - - - - - Information about related parts of JOURNEY. +SIRI v2.1 - - - - - - - - - - - The JOURNEY RELATION refers to this CALL. +SIRI v2.1 - - - - - - - - - - - - - The JOURNEY RELATION refers to this JOURNEY PART. +SIRI v2.1 - - - - - - - - Refers to the JOURNEY to which the current JOURNEY is related. +SIRI v2.1 - - - - - - - - - - - - - - - Groups relevant elements of the formation model that are used on JOURNEY level. -The TRAIN conceptual model represents VEHICLE TYPE properties that are peculiar to TRAINs. A TRAIN may comprise not just a single VEHICLE but a chain of carriages, TRAIN ELEMENTS, assembled as TRAIN COMPONENTs. -Groups of carriages may be managed as sections by composing TRAINs into a COMPOUND TRAIN made up of multiple TRAIN IN COMPOUND TRAIN, for example in a train that joins or splits. +SIRI v2.1 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. +SIRI v2.1 -Examples: -- "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle arriving or departing in the direction of sector A on a QUAY with sectors A-B-C-D. If the arriving vehicle is represented as an arrow, "towards A" would be abstracted as "=> A-B-C-D". If the departing vehicle is represented as an arrow, "towards A" would be abstracted as "<= A-B-C-D". -- "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle arriving or departing in the direction of this reference point. If the arriving vehicle is represented as an arrow, "towards 0" would be abstracted as "=> 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). If the departing vehicle is represented as an arrow, "towards 0" would be abstracted as "<= 0...100". -It is advised to specify a reference point that is meaningful for passengers on location. - - - - - - - - Assignment of the arrival/departure of a VEHICLE within a formation, e.g. carriage in a TRAIN composition, to a physical QUAY or nested QUAY (i.e. platform or sector of a platform). +SIRI v2.1 - - - - - - Information about a change of a VEHICLE within the formation, e.g., whether a VEHICLE is open, booked or has defective doors. - - - - - References to the QUAY on which the particular VEHICLE, i.e., component of the formation, arrives or departs from. -If a QUAY is divided into sub-QUAYs or sectors (with the help of STOP ASSIGNMENTs), and a TRAIN COMPONENT spans over multiple sectors of the QUAY, the FORMATION ASSIGNMENT must reference all of them (in multiple STOP ASSIGNMENTs). - - - - - - - Information about a change of the formation (e.g. TRAIN composition) or changes of vehicles within the formation. +SIRI v2.1 - - - - - Type for FORMATION CONDITION. +SIRI v2.1 - - - - - - - Status of formation, e.g., whether it has changed compared to the plan, certain VEHICLEs or features are missing or extra VEHICLEs are added. - - - - - Status of a VEHICLE within formation, e.g., whether a VEHICLE is open, booked or has defective doors. - - - - - - - Information on recommendations for passengers on how to deal with the formation change. - - - - - - - - Description of the status of a monitored formation. - - - - - Status of the formation. - - - - - - - - Description of the status of a monitored vehicle. - - - - - Status of vehicle. - - - - - - - - Elements for FormationStatus that further describe the status of the formation, e.g. whether the accessibility has changed. +SIRI v2.1 - - - - - Description of the status of a formation or a vehicle within the formation. - - - - - Accessibility of the formation or a vehicle within the formation. - - - - - - - - Description of the recommended action for passengers on how to deal with changes, for example of the TRAIN formation. - - - - - Type of the recommendation, e.g. 'unknown', 'replacement' or 'otherRoute'. - - - - - Description of the recommended action in natural language. - - - - - - - - - Elements for a PASSENGER CAPACITY. Used to indicate the maximum capacities of a TRAIN ELEMENT or the estimated/recorded capacities of a VEHICLE at a given stop, i.e., the number of seats available. +SIRI v2.1 - - - - - The total capacity of the vehicle in number of passengers. - - - - - The seating capacity of the vehicle in number of passengers. - - - - - The standing capacity of the vehicle in number of passengers. - - - - - The number of special places on the vehicle, e.g. seats for the disabled or lounge seats. - - - - - The number of push chair places on the vehicle. - - - - - The number of wheelchair places on the vehicle. - - - - - The number of places on the vehicle that are suitable for prams. - - - - - The number of bicycle racks on the vehicle. - - - - - - - The intersection of supplied elements describes the extent that the Occupancy values applies to. +SIRI v2.1 -Only vehicle-centric filter (measurement in a part or at an entrance of a TRAIN) are available here, but a stop-centric filtering (measurement in a sector or at a position on a QUAY) can be achieved indirectly via Arrival-/DepartureFormationAssignment. - - - - - - Fare class in VEHICLE for which occupancy or capacities are specified. - - - - - Adult, child, wheelchair etc. - - - - - - - Occupancy values applying to indicated scope. +SIRI v2.1 - - - - - An approximate figure of how occupied or full a VEHICLE and its parts are, e.g. 'manySeatsAvailable' or 'standingRoomOnly'. -More accurate data can be provided by the individual occupancies or capacities below. - - - - - Utilised percentage of maximum payload after departing the STOP POINT. - - - - - Total number of alighting passengers for this vehicle journey at this STOP POINT. - - - - - Total number of boarding passengers for this vehicle journey at this STOP POINT. - - - - - Total number of passengers on-board after departing the STOP POINT. - - - - - Total number of special places, e.g. seats for the disabled or lounge seats, that are occupied after departing the STOP POINT. - - - - - Total number of pushchairs on-board after departing the STOP POINT. - - - - - Total number of wheelchairs on-board after departing the STOP POINT. - - - - - Total number of prams on-board after departing the STOP POINT. - - - - - Total number of bicycles on-board, i.e., number of bicycle racks that are occupied after departing the STOP POINT. - - - - - - - Used to specify that a travel group has booked a section of the vehicle for a part of the journey, and if so under what name. +SIRI v2.1 - - - - - Name for which the travel group has made the reservation. - - - - - Number of seats that the group has booked. - - - - - - - Real-time occupancies of a VEHICLE (by fare class). Could be feedback from an automatic passenger counting system (APC) or estimated values from statistics. +SIRI v2.1 - - - - - - - Total number of booked seats from individual and group reservations. - - - - - Reservations of travel groups, i.e., name of group and number of seats booked. - - - - - - - Real-time capacities of a VEHICLE (by fare class), i.e., number of available seats. Alternative way to communicate occupancy measurements. +SIRI v2.1 - - - - - - - - - - An elementary component of a TRAIN, e.g. wagon or locomotive. +SIRI v2.1 - - - - - Type for TRAIN ELEMENT. +SIRI v2.1 - - - - - Identifier for TRAIN ELEMENT. - - - - - - - - - Elements for a TRAIN ELEMENT. +SIRI v2.1 - - - - - Type of TRAIN ELEMENT. - - - - - Denotes the official "registration number" of the vehicle or wagon/coach. In rail transport VEHICLE NUMBER would be equal to the 12-digit UIC wagon/coach number, possibly followed by other combinations of letters, e.g. by the UIC classification of railway coaches. - - - - - - - - - Specifies the order of a certain TRAIN ELEMENT within a TRAIN and how the TRAIN ELEMENT is labeled in that context. +SIRI v2.1 - - - - - Type for TRAIN COMPONENT. +SIRI v2.1 - - - - - Identifier for TRAIN COMPONENT. - - - - - Specifies the order of the TRAIN ELEMENT within the TRAIN. The locomotive would ideally have ORDER '1', the first wagon/coach attached to the locomotive ORDER '2' and so on. - - - - - - - - Elements for a TRAIN COMPONENT. +SIRI v2.1 - - - - - Specifies how the TRAIN ELEMENT is labeled within the context of the TRAIN. This advertised label or number, e.g. "Carriage B" or "23", can be used for seat reservations and passenger orientation. - - - - - Description of TRAIN COMPONENT, e.g. "Front Carriage 1st Class". - - - - - - - - - Whether orientation of TRAIN ELEMENT within TRAIN is reversed or not. Default is 'false', i.e., they have the same orientation (usually forward in the direction of travel). - - - - - - - - A vehicle composed of TRAIN ELEMENTs assembled in a certain order (so called TRAIN COMPONENTs), i.e. wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 - - - - - Type for TRAIN. +SIRI v2.1 - - - - - Identifier for TRAIN. - - - - - - - - - Elements for TRAIN. +SIRI v2.1 - - - - - Number of cars needed in TRAIN. - - - - - Nature of TRAIN size, e.g "short", "long", "normal". Default is "normal". - - - - - Ordered collection of TRAIN COMPONENTs making up the TRAIN. - - - - - - - - - - - - - - Groups of carriages may be managed as sections by composing TRAINs into a COMPOUND TRAIN, for example if a TRAIN joins (or splits from) another TRAIN. +SIRI v2.1 -TRAINs within a COMPOUND TRAIN may have different origins and destinations due to joining/splitting. A COMPOUND TRAIN may be stable for one or multiple JOURNEY PARTs and change at a certain STOP POINT due to planned joining/splitting, despatching alterations or a situation. - - - - - Type for COMPOUND TRAIN. +SIRI v2.1 - - - - - Identifier for COMPOUND TRAIN. - - - - - - Ordered collection of TRAINs making up the COMPOUND TRAIN. - - - - - - - - - - - - - Specifies the order of a certain TRAIN within a COMPOUND TRAIN and how the TRAIN is labeled in that context. +SIRI v2.1 - - - - - Type for a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 - - - - - Identifier for TRAIN IN COMPOUND TRAIN. - - - - - Specifies the order of the TRAIN within the COMPOUND TRAIN. - - - - - - - - Elements for a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 - - - - - Specifies how the TRAIN is labeled within the context of the COMPOUND TRAIN. This advertised label or number, e.g. the individual TRAIN NUMBER, can be used for seat reservations and passenger orientation. - - - - - Description of TRAIN IN COMPOUND TRAIN. - - - - - - - - - - Whether orientation of TRAIN within COMPOUND TRAIN is reversed or not. Default is 'false', i.e., they have the same orientation (usually forward in the direction of travel). - - - - - Specifies whether a passage from/to an adjacent TRAIN is possible for passengers. - - - - - - - - - - - - Indicates whether passengers have access to adjacent TRAINs or TRAIN COMPONENTs within a COMPOUND TRAIN, i.e., whether passage between those wagons/coaches is possible. +SIRI v2.1 - - - - - - - - - - - Elements for a VEHICLE TYPE. +SIRI v2.1 - - - - - Name of VEHICLE TYPE. - - - - - Short Name of VEHICLE TYPE. - - - - - Description of VEHICLE TYPE. - - - - - - - Facilities of VEHICLE TYPE. - - - - - - - - - - - - - - - - Property elements for the abstract VEHICLE TYPE. +SIRI v2.1 - - - - - Whether vehicles of the type have a reversing direction. - - - - - Whether vehicles of the type are self-propelled. - - - - - The type of fuel used by a vehicle of the type. - - - - - Euroclass of the vehicle type. Corresponds to the 12-digit European Identification Number (EIN). - - - - - Break down of capacities by FARE CLASS, i.e., maximum number of passengers that TRAIN ELEMENT can carry. - - - - - - - - - - - - - - Elements specifying Requirement properties of VEHICLE TYPE. Vehicle should satisfy these requirements. +SIRI v2.1 - - - - - Whether Vehicle is low floor to facilitate access by the mobility impaired. - - - - - Whether vehicle has lift or ramp to facilitate wheelchair access. - - - - - Whether vehicle has hoist for wheelchair access. - - - - - - - Dimension elements for a VEHICLE TYPE. +SIRI v2.1 - - - - - The length of a VEHICLE of the type. - - - - - The width of a VEHICLE of the type. - - - - - The length of a VEHICLE of the type. - - - - - The weight of a VEHICLE of the type. - - - - - -       + + + + + + main schema + e-service developers + Cen TC278 WG3 SG7 Team + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2004-03-05 + + + 2004-10-06 + + + 2005-05-11 + + + 2005-11-15 + + + 2007-03-29 + + + 2008-11-13 + + + + 2011-04-18 + + + + 2012-03-22 + + + + 2012-04-27 + + + + 2013-01-25 + + + + 2013-02-11 + + + + 2014-06-20 + + + +

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

      +

      This subschema defines common journey elements.

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/siri/}siri_journey.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd + + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG CML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of common Journey elements + Standard +       +       + SIRI Common Journey Model. +       + + + + + + + + + + + + + + + + Elements describing a VEHICLE JOURNEY. Values for these elements can be specified on an annual schedule and will be inherited, unless overriden, onto the production timetable and then onto the individul DATED VEHICLE JOURNEYs of the timetable. Each real-time journey (e.g. ESTIMATED VEHICLE JOURNEY or MONITORED VEHICLE JORUNEY) takes its values from the DATED VEHICLE JOURNEY that it follows. The absence of a value on an entity at a given level indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity. + + + + + For train services with named journeys. Train name, e.g. “West Coast Express”. If omitted: No train name. Inherited property. (Unbounded since SIRI 2.0) + + + + + + Contact details for use by members of public. +SIRI v2.0 + + + + + Contact details for use by operational staff. +SIRI v2.0 + + + + + + + Type for Simple Contact Details. + + + + + Phone number +SIRI v2.0 + + + + + Url for contact +SIRI v2.0 + + + + + + + + Common information about a VEHICLE JOURNEY. (Similar to VDV TripInfo) + + + + + + + + + + + End names for journey. + + + + + + Name of the origin of the journey. (Unbounded since SIRI 2.0) + + + + + Short name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as Origin Name. + + + + + DIRECTION name shown for jurney at the origin. +SIRI v2.0 + + + + + Names of VIA points, used to help identify the LINE, for example, Luton to Luton via Sutton. Currently 3 in VDV. Should only be included if the detail level was requested. + + + + + Reference to a DESTINATION. + + + + + Description of the destination stop (vehicle signage), Can be overwritten for a journey, and then also section by section by the entry in an individual CALl. (Unbounded since SIRI 2.0) + + + + + Short name of the DESTINATION.of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as DestinationName. (Unbounded since SIRI 2.0) + + + + + Origin name shown for jourey at the destination +SIRI v2.0 + + + + + + + Type for VIA NAMes structure. + + + + + + + Relative priority to give to VIA name in displays. 1=high. Default is 2. +SIRI v2.0 + + + + + + + + + + Type for Information about a DESTINATION. + + + + + Identifer of Destinatioin + + + + + Name of Destination + + + + + + + The name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. + + + + + Names of VIA points, used to help identify the LINEfor example, Luton to Luton via Sutton. Currently 3 in VDV. Should only be included if the detail level was requested. + + + + + The name of the DESTINATION of the journey; used to help identify the VEHICLE to the public. Note when used in a CALL, this is the Dynamic Destination Display: since vehicles can change their destination during a journey, the destination included here should be what the VEHICLE will display when it reaches the stop. + + + + + + Call times for journey. + + + + + Whether this is a Headway Service, that is shown as operating at a prescribed interval rather than to a fixed timetable. Default is 'false'. + + + + + Timetabled departure time from Origin. + + + + + Timetabled arrival time at Destination. + + + + + + + + Whether journey is first or last journey of day. +SIRI v2.0 + + + + + Additional descriptive text associated with journey. Inherited property. + + + + + Description of a DIRECTION. + + + + + Type for DIRECTION. + + + + + Identifer of DIRECTION, + + + + + Description of DIRECTION. (Unbounded since SIRI 2.0) + + + + + + + + Operational information about the monitored VEHICLE JOURNEY. + + + + + + + + Refercence to other VEHICLE Journeys (+SIRI v2.0) + + + + + A reference to the DRIVER or Crew currently logged in to operate a monitored VEHICLE. May be omitted if real-time data is not available - i.e. it is timetabled data. +SIRI v2.0 + + + + + The name oo the Driver or Crew +SIRI v2.0 + + + + + + + Operational information about the monitored VEHICLE JOURNEY. + + + + + + + + + Operational information about the monitored VEHICLE JOURNEY. + + + + + BLOCK that VEHICLE is running. + + + + + COURSE OF JOURNEY ('Run') that VEHICLE is running. + + + + + + + Type for Progress between stops. + + + + + The total distance in metres between the previous stop and the next stop. + + + + + Percentage along link that VEHICLE has travelled. + + + + + + + + + Type for Abstract CALL at stop. + + + + + + + + + Elements describing the targeted CALL of a VEHICLE at a stop. + + + + + + + + + + + Elements describing the arrival of a VEHICLE at a stop. + + + + + + + + Assignment of planned arrival at scheduled STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. +SIRI v2.0. + + + + + + + + + Elements describing the departure of a VEHICLE from a stop. + + + + + + + + + + + + + + Type for Abstract CALL at stop. + + + + + + + + Elements describing the arrival status of a VEHICLE at a stop. + + + + + + + + + + Assignment of planned, expected and/or recorded arrival at STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. +SIRI v2.0. + + + + + + + + + + Elements describing the departure status of a VEHICLE from a stop. + + + + + + + + + + + + + + + + + + + Elements describing the CALL Properties Values for these elements can be specified on an production VEHICLE JOURNEY CALL. Each real-time journey CALL takes its values from the corresponding dated VEHICLE JOURNEY CALL. The absence of a value on an real-time CALL l indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity. + + + + + + Whether this is a Hail and Ride Stop. Default is 'false'. + + + + + Whether Vehicle stops only if requested explicitly by passenger. Default is 'false'. + + + + + Origin to show for the VEHICLE at the specific stop (vehicle signage), if different to the Origin Name for the full journey. (+Siri 2.0) + + + + + Destination to show for the VEHICLE at the specific stop (vehicle signage), if different to the Destination Name for the full journey. + + + + + + + Annotations of the CALL. + + + + + Text annotation that applies to this CALL. + + + + + + + + Type for CALLing pattern for JOURNEY PATTERN. + + + + + + + + Type Onwards CALLs at stop. + + + + + + + + + + + + + + + + + Elements describing the CALL. Values for these elements can be specified on an production VEHICLE JOURNEY CALL. Each real-time journey CALL takes its values from the corresponding dated VEHICLE JOURNEY CALL. The absence of a value on an real-time CALL l indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity. + + + + + + + + + + + + + + Elements for Arrival in onward CALl. + + + + + + + + + Latest time at which a VEHICLE will arrive at stop. +SIRI v2.1 + + + + + Prediction quality, either as approximate level, or more quantitative percentile range of predictions that will fall within a given range of times. +SIRI v2.0 + + + + + + If the producer is (temporarily) not able to deliver real-time predictions (e.g. because of a connection loss), he has various options (and combinations of them) to inform the consumer: +(i) set Monitored to 'false' +(ii) transmit ExpectedArrivalTime together with "PredictionInaccurate=true" +(iii) drop/omit ExpectedArrivalTime +(iv) set ArrivalStatus to 'noReport' +However, this might introduce ambiguity: e.g. option (iii) might be interpreted as "on time" by one consumer, but also as "indefinite delay" by another consumer. +To avoid this, the producer should transmit xxxPredictionUnknown instead of any expected times. +SIRI v2.1 + + + + + + + + Elements for departure in ONWARD CALL. + + + + + + + + + Expected departure time of VEHICLE without waiting time due to operational actions. For people at stop this would normally be shown if different from Expected departure time. So if servcie decides not to wait may leave earler than expected departure time +SIRI v2.0. + + + + + Earliest time at which VEHICLE may leave the stop. Used to secure connections. Used for passenger announcements. Passengers must be at boarding point by this time to be sure of catching VEHICLE. i.e. "Vehicle will not leave before this time" - may be revised from original aimed time. +SIRI v2.0 + + + + + Prediction quality, either as approximate level, or more quantitative percentile range of predictions that will fall within a given range of times. +SIRI v2.0 + + + + + + If the producer is (temporarily) not able to deliver real-time predictions (e.g. because of a connection loss), he has various options (and combinations of them) to inform the consumer: +(i) set Monitored to 'false' +(ii) transmit ExpectedDepartureTime together with "PredictionInaccurate=true" +(iii) drop/omit ExpectedDepartureTime +(iv) set DepartureStatus to 'noReport' +However, this might introduce ambiguity: e.g. option (iii) might be interpreted as "on time" by one consumer, but also as "indefinite delay" by another consumer. +To avoid this, the producer should transmit xxxPredictionUnknown instead of any expected times. +SIRI v2.1 + + + + + + + + Elements describing the HEADWAY INTERVALs. + + + + + + + + + Elements describing the distance from the stop of a VEHICLE. +SIRI v2.0. + + + + + Distance of VEHICLE from stop of CALL as measured along ROUTE track. Only shown if detail level is 'calls' or higher. Positive value denotes distance before stop. +SIRI v2.0. + + + + + Count of stops along SERVICE PATTERN between current position of VEHICLE and stop of CALL as measured along ROUTE track. Only shown if detail level is 'calls' or higher. +SIRI v2.0. + + + + + + + Type for Prediction Quality quantifcation. + + + + + An approxiimate characterisation of prediction quality as one of five values. +SIRI v2.0 + + + + + + Percentile associated with range as specified by lower and upper bound. +SIRI v2.0 + + + + + Lower bound on time of prediction for confidence level if different from defaults. +SIRI v2.0 + + + + + Upper bound on time of prediction for confidence level if different from defaults. +SIRI v2.0 + + + + + + + + + Area that encompasses the scheduled flexible stop locations according to the planned timetable. +SIRI v2.1 + + + + + Reference to the scheduled location or flexible area. +SIRI v2.1 + + + + + Name or description (e.g. address) of the scheduled location or flexible area. +SIRI v2.1 + + + + + + Elements for location of flexible stops or service that allows pickup anywhere in a designated area. +SIRI v2.1 + + + + + + + + Area that encompasses the expected flexible stop locations according to the real-time prediction. + + + + + + Name or description (e.g. address) of the expected location or flexible area. + + + + + Area that encompasses the actually recorded flexible stop locations. + + + + + + Name or description (e.g. address) of the actually recorded location or flexible area. + + + + + + + + Elements for assignment of a SCHEDULED STOP POINT to a specific QUAY or platform. +SIRI v2.1 + + + + + Physical QUAY to use according to the planned timetable. +SIRI v2.0 + + + + + Scheduled Platform name. Can be used to indicate platfrom change. +SIRI v2.0 + + + + + Physical QUAY to use according to the real-time prediction. +SIRI v2.0 + + + + + Expected Platform name. Can be used to indicate real-time prediction. +SIRI v2.1 + + + + + Physical QUAY actually used. +SIRI v2.0 + + + + + Actual Platform name. Can be used to indicate recorded platform. +SIRI v2.1 + + + + + + + + + Elements for assignment of a SCHEDULED STOP POINT to a specific BOARDING POSITION or location on a QUAY. +SIRI v2.1 + + + + + Physical BOARDING POSITION to use according to the planned timetable. + + + + + Scheduled BOARDING POSITION name. Can be used to indicate boarding position change. + + + + + Physical BOARDING POSITION to use according to the real-time prediction. + + + + + Expected BOARDING POSITION name. Can be used to indicate real-time prediction. + + + + + Actually recorded BOARDING POSITION. Can be used to indicate the actually used boarding position. + + + + + Recorded BOARDING POSITION name. Can be used to indicate the actually used boarding position. + + + + + + + + Type for assignment of a SCHEDULED STOP POINT to a physical location, in particular to a QUAY or BOARDING POSITION. +SIRI v2.0. + + + + + + + + + + + + + Type for assignment of a SCHEDULED STOP POINT to a physical location, in particular to a QUAY or BOARDING POSITION, according to the planned timetable. +SIRI v2.0. + + + + + + + Physical QUAY to use according to the planned timetable. +SIRI v2.0 + + + + + Scheduled Platform name. +SIRI v2.0 + + + + + + + + Physical BOARDING POSITION to use according to the planned timetable. +SIRI v2.1 + + + + + Scheduled BOARDING POSITION name. +SIRI v2.1 + + + + + + + + + + + + + Indicates the type of a nested QUAY in case of detailed STOP PLACE models. +A QUAY may be part of a group of QUAYs, or may be divided into sectors, i.e., smaller sub-QUAYs. +SIRI v2.1 + + + + + + Whether the prediction for a specific stop or the whole journey is considered to be of a useful accuracy or not. Default is 'false', i.e. prediction is considered to be accurate. +If prediction is degraded, e.g. because of a situation, PredictionInaccurate is used to indicate a lowered quality of data. Inherited property. PredictionInaccurate can be used in combination with InCongestion, but is more general. + + + + + Can be used to inform the passenger about the reason for a change of the prediction (in)accuracy in case PredictionInaccurate is set to 'true'. +SIRI v2.1 + + + + + An approximate figure of how occupied the journey is after departing from a given stop, e.g. 'manySeatsAvailable' or 'standingRoomOnly'. If omitted: Passenger load is unknown. +Occupancies and capacities for individual VEHICLEs, e.g. parts of a COMPOUND TRAIN, can also be specified in more detail for the departure on CALL level. + + + + + + Target arrival time of VEHICLE at stop according to latest working timetable. + + + + + Observed time of arrival of VEHICLE at stop. + + + + + Estimated time of arriival of VEHICLE at stop . + + + + + Classification of the timeliness of the visit according to a fixed list of values. If not specified, same as DepartureStatus. + + + + + Text annotation to be used in cases where ArrivalStatus is set to 'cancelled'. +SIRI v2.1 + + + + + Arbitrary text string to show to indicate the status of the departure of the VEHICLE for example, “Enroute”, “5 Km”, “Approaching”. May depend on the policy of the OPERATOR, for example show “Approaching” if less than 200metres away from stop. +SIRI v2.0 + + + + + Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicle to arrive at. +Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is: +(i) any arrival platform on any related dated timetable element, +(ii) any departure platform name on this estimated element; +(iii) any departure platform name on any related dated timetable CALL. + + + + + Type of boarding and alighting allowed at stop. Default is 'Alighting'. + + + + + Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). If not given, assume same as for departure. +SIRI v2.1 + + + + + Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. +SIRI v2.1 +Examples: +- "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle arriving at sector A first when approaching the QUAY with sectors A-B-C-D. If the arriving vehicle is represented as an arrow, "towards A" would be abstracted as "=> A-B-C-D". +- "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle arriving at this reference point first when approaching the QUAY. If the arriving vehicle is represented as an arrow, "towards 0" would be abstracted as "=> 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). +It is advised to specify a reference point that is meaningful for passengers on location. + + + + + + OPERATORs of of service up until arrival. May change for departure. +SIRI v2.0. + + + + + + Arrival times for CALL. + + + + + + + + + + + + + Target departure time of VEHICLE from stop according to latest working timetable. + + + + + Observed time of departure of VEHICLE from stop. + + + + + Estimated time of departure of VEHICLE from stop, most likely taking into account all control actions such as waiting. + + + + + Latest target time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. +SIRI 2.0 + + + + + Latest expected time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. +SIRI 2.0 + + + + + Classification of the timeliness of the departure part of the CALL, according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are still classified as on-time. Applications may use this to guide their own presentation of times. + + + + + Text annotation to be used in cases where DepartureStatus is set to 'cancelled'. +SIRI v2.1 + + + + + Arbitrary text string to show to indicate the status of the departure of the vehicle, for example, “Boarding”, “GatesClosed”. +SIRI v2.0 + + + + + Departure QUAY (bay or platform) name. Default taken from planned timetable. + + + + + Nature of boarding allowed at stop. Default is 'Boarding'. + + + + + Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). +SIRI v2.1 + + + + + Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. +SIRI v2.1 +Examples: +- "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle departing in the direction of sector A on a QUAY with sectors A-B-C-D. If the departing vehicle is represented as an arrow, "towards A" would be abstracted as "<= A-B-C-D". +- "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle departing in the direction of this reference point. If the departing vehicle is represented as an arrow, "towards 0" would be abstracted as "<= 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). +It is advised to specify a reference point that is meaningful for passengers on location. + + + + + Real-time occupancies of a VEHICLE and reservations after departing from a given stop. +SIRI v2.1 + + + + + Real-time capacities (number of available seats) of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. +SIRI v2.1 + + + + + OPERATORs of service for departure and onwards. May change from that for arrival. +SIRI v2.0. + + + + + Recorded occupancies of a VEHICLE and reserved seats after departing from a given stop. +SIRI v2.1 + + + + + Recorded capacities of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. +SIRI v2.1 + + + + + + Departure times for CALL. + + + + + + + + + + + + Passenger arrival times at STOP PLACE in order to meet VEHICLE departure times for CALL. + + + + + + + + + + For frequency based services, target interval between vehicles at stop. + + + + + For frequency based services, expected interval between vehicles at stop. + + + + + For frequency based services, observed interval between vehicles at stop. + + + + + + Provides information about relations to other journeys. +SIRI v2.1 + + + + + + + + + + Specifies the type of the relation, e.g., joining, splitting, replacement etc. +SIRI v2.1 + + + + + + + + + Specifies which CALL or JOURNEY PART of the JOURNEY has a JOURNEY RELATION. +SIRI v2.1 + + + + + + Information about the stop at which the JOURNEY is related to another JOURNEY. +SIRI v2.1 + + + + + Information about the JOURNEY PARTs for which the JOURNEY has a JOURNEY RELATION. +SIRI v2.1 + + + + + + Information about related parts of JOURNEY. +SIRI v2.1 + + + + + + + + + + + The JOURNEY RELATION refers to this CALL. +SIRI v2.1 + + + + + + + + + + + + + The JOURNEY RELATION refers to this JOURNEY PART. +SIRI v2.1 + + + + + + + + Refers to the JOURNEY to which the current JOURNEY is related. +SIRI v2.1 + + + + + + + + + + + + + + + Groups relevant elements of the formation model that are used on JOURNEY level. +The TRAIN conceptual model represents VEHICLE TYPE properties that are peculiar to TRAINs. A TRAIN may comprise not just a single VEHICLE but a chain of carriages, TRAIN ELEMENTS, assembled as TRAIN COMPONENTs. +Groups of carriages may be managed as sections by composing TRAINs into a COMPOUND TRAIN made up of multiple TRAIN IN COMPOUND TRAIN, for example in a train that joins or splits. +SIRI v2.1 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. +SIRI v2.1 +Examples: +- "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle arriving or departing in the direction of sector A on a QUAY with sectors A-B-C-D. If the arriving vehicle is represented as an arrow, "towards A" would be abstracted as "=> A-B-C-D". If the departing vehicle is represented as an arrow, "towards A" would be abstracted as "<= A-B-C-D". +- "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle arriving or departing in the direction of this reference point. If the arriving vehicle is represented as an arrow, "towards 0" would be abstracted as "=> 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). If the departing vehicle is represented as an arrow, "towards 0" would be abstracted as "<= 0...100". +It is advised to specify a reference point that is meaningful for passengers on location. + + + + + + + + Assignment of the arrival/departure of a VEHICLE within a formation, e.g. carriage in a TRAIN composition, to a physical QUAY or nested QUAY (i.e. platform or sector of a platform). +SIRI v2.1 + + + + + + Information about a change of a VEHICLE within the formation, e.g., whether a VEHICLE is open, booked or has defective doors. + + + + + References to the QUAY on which the particular VEHICLE, i.e., component of the formation, arrives or departs from. +If a QUAY is divided into sub-QUAYs or sectors (with the help of STOP ASSIGNMENTs), and a TRAIN COMPONENT spans over multiple sectors of the QUAY, the FORMATION ASSIGNMENT must reference all of them (in multiple STOP ASSIGNMENTs). + + + + + + + Information about a change of the formation (e.g. TRAIN composition) or changes of vehicles within the formation. +SIRI v2.1 + + + + + Type for FORMATION CONDITION. +SIRI v2.1 + + + + + + + Status of formation, e.g., whether it has changed compared to the plan, certain VEHICLEs or features are missing or extra VEHICLEs are added. + + + + + Status of a VEHICLE within formation, e.g., whether a VEHICLE is open, booked or has defective doors. + + + + + + + Information on recommendations for passengers on how to deal with the formation change. + + + + + + + + Description of the status of a monitored formation. + + + + + Status of the formation. + + + + + + + + Description of the status of a monitored vehicle. + + + + + Status of vehicle. + + + + + + + + Elements for FormationStatus that further describe the status of the formation, e.g. whether the accessibility has changed. +SIRI v2.1 + + + + + Description of the status of a formation or a vehicle within the formation. + + + + + Accessibility of the formation or a vehicle within the formation. + + + + + + + + Description of the recommended action for passengers on how to deal with changes, for example of the TRAIN formation. + + + + + Type of the recommendation, e.g. 'unknown', 'replacement' or 'otherRoute'. + + + + + Description of the recommended action in natural language. + + + + + + + + + Elements for a PASSENGER CAPACITY. Used to indicate the maximum capacities of a TRAIN ELEMENT or the estimated/recorded capacities of a VEHICLE at a given stop, i.e., the number of seats available. +SIRI v2.1 + + + + + The total capacity of the vehicle in number of passengers. + + + + + The seating capacity of the vehicle in number of passengers. + + + + + The standing capacity of the vehicle in number of passengers. + + + + + The number of special places on the vehicle, e.g. seats for the disabled or lounge seats. + + + + + The number of push chair places on the vehicle. + + + + + The number of wheelchair places on the vehicle. + + + + + The number of places on the vehicle that are suitable for prams. + + + + + The number of bicycle racks on the vehicle. + + + + + + + The intersection of supplied elements describes the extent that the Occupancy values applies to. +SIRI v2.1 +Only vehicle-centric filter (measurement in a part or at an entrance of a TRAIN) are available here, but a stop-centric filtering (measurement in a sector or at a position on a QUAY) can be achieved indirectly via Arrival-/DepartureFormationAssignment. + + + + + + Fare class in VEHICLE for which occupancy or capacities are specified. + + + + + Adult, child, wheelchair etc. + + + + + + + Occupancy values applying to indicated scope. +SIRI v2.1 + + + + + An approximate figure of how occupied or full a VEHICLE and its parts are, e.g. 'manySeatsAvailable' or 'standingRoomOnly'. +More accurate data can be provided by the individual occupancies or capacities below. + + + + + Utilised percentage of maximum payload after departing the STOP POINT. + + + + + Total number of alighting passengers for this vehicle journey at this STOP POINT. + + + + + Total number of boarding passengers for this vehicle journey at this STOP POINT. + + + + + Total number of passengers on-board after departing the STOP POINT. + + + + + Total number of special places, e.g. seats for the disabled or lounge seats, that are occupied after departing the STOP POINT. + + + + + Total number of pushchairs on-board after departing the STOP POINT. + + + + + Total number of wheelchairs on-board after departing the STOP POINT. + + + + + Total number of prams on-board after departing the STOP POINT. + + + + + Total number of bicycles on-board, i.e., number of bicycle racks that are occupied after departing the STOP POINT. + + + + + + + Used to specify that a travel group has booked a section of the vehicle for a part of the journey, and if so under what name. +SIRI v2.1 + + + + + Name for which the travel group has made the reservation. + + + + + Number of seats that the group has booked. + + + + + + + Real-time occupancies of a VEHICLE (by fare class). Could be feedback from an automatic passenger counting system (APC) or estimated values from statistics. +SIRI v2.1 + + + + + + + Total number of booked seats from individual and group reservations. + + + + + Reservations of travel groups, i.e., name of group and number of seats booked. + + + + + + + Real-time capacities of a VEHICLE (by fare class), i.e., number of available seats. Alternative way to communicate occupancy measurements. +SIRI v2.1 + + + + + + + + + + An elementary component of a TRAIN, e.g. wagon or locomotive. +SIRI v2.1 + + + + + Type for TRAIN ELEMENT. +SIRI v2.1 + + + + + Identifier for TRAIN ELEMENT. + + + + + + + + + Elements for a TRAIN ELEMENT. +SIRI v2.1 + + + + + Type of TRAIN ELEMENT. + + + + + Denotes the official "registration number" of the vehicle or wagon/coach. In rail transport VEHICLE NUMBER would be equal to the 12-digit UIC wagon/coach number, possibly followed by other combinations of letters, e.g. by the UIC classification of railway coaches. + + + + + + + + + Specifies the order of a certain TRAIN ELEMENT within a TRAIN and how the TRAIN ELEMENT is labeled in that context. +SIRI v2.1 + + + + + Type for TRAIN COMPONENT. +SIRI v2.1 + + + + + Identifier for TRAIN COMPONENT. + + + + + Specifies the order of the TRAIN ELEMENT within the TRAIN. The locomotive would ideally have ORDER '1', the first wagon/coach attached to the locomotive ORDER '2' and so on. + + + + + + + + Elements for a TRAIN COMPONENT. +SIRI v2.1 + + + + + Specifies how the TRAIN ELEMENT is labeled within the context of the TRAIN. This advertised label or number, e.g. "Carriage B" or "23", can be used for seat reservations and passenger orientation. + + + + + Description of TRAIN COMPONENT, e.g. "Front Carriage 1st Class". + + + + + + + + + Whether orientation of TRAIN ELEMENT within TRAIN is reversed or not. Default is 'false', i.e., they have the same orientation (usually forward in the direction of travel). + + + + + + + + A vehicle composed of TRAIN ELEMENTs assembled in a certain order (so called TRAIN COMPONENTs), i.e. wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 + + + + + Type for TRAIN. +SIRI v2.1 + + + + + Identifier for TRAIN. + + + + + + + + + Elements for TRAIN. +SIRI v2.1 + + + + + Number of cars needed in TRAIN. + + + + + Nature of TRAIN size, e.g "short", "long", "normal". Default is "normal". + + + + + Ordered collection of TRAIN COMPONENTs making up the TRAIN. + + + + + + + + + + + + + + Groups of carriages may be managed as sections by composing TRAINs into a COMPOUND TRAIN, for example if a TRAIN joins (or splits from) another TRAIN. +SIRI v2.1 +TRAINs within a COMPOUND TRAIN may have different origins and destinations due to joining/splitting. A COMPOUND TRAIN may be stable for one or multiple JOURNEY PARTs and change at a certain STOP POINT due to planned joining/splitting, despatching alterations or a situation. + + + + + Type for COMPOUND TRAIN. +SIRI v2.1 + + + + + Identifier for COMPOUND TRAIN. + + + + + + Ordered collection of TRAINs making up the COMPOUND TRAIN. + + + + + + + + + + + + + Specifies the order of a certain TRAIN within a COMPOUND TRAIN and how the TRAIN is labeled in that context. +SIRI v2.1 + + + + + Type for a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 + + + + + Identifier for TRAIN IN COMPOUND TRAIN. + + + + + Specifies the order of the TRAIN within the COMPOUND TRAIN. + + + + + + + + Elements for a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 + + + + + Specifies how the TRAIN is labeled within the context of the COMPOUND TRAIN. This advertised label or number, e.g. the individual TRAIN NUMBER, can be used for seat reservations and passenger orientation. + + + + + Description of TRAIN IN COMPOUND TRAIN. + + + + + + + + + + Whether orientation of TRAIN within COMPOUND TRAIN is reversed or not. Default is 'false', i.e., they have the same orientation (usually forward in the direction of travel). + + + + + Specifies whether a passage from/to an adjacent TRAIN is possible for passengers. + + + + + + + + + + + + Indicates whether passengers have access to adjacent TRAINs or TRAIN COMPONENTs within a COMPOUND TRAIN, i.e., whether passage between those wagons/coaches is possible. +SIRI v2.1 + + + + + + + + + + + Elements for a VEHICLE TYPE. +SIRI v2.1 + + + + + Name of VEHICLE TYPE. + + + + + Short Name of VEHICLE TYPE. + + + + + Description of VEHICLE TYPE. + + + + + + + Facilities of VEHICLE TYPE. + + + + + + + + + + + + + + + + Property elements for the abstract VEHICLE TYPE. +SIRI v2.1 + + + + + Whether vehicles of the type have a reversing direction. + + + + + Whether vehicles of the type are self-propelled. + + + + + The type of fuel used by a vehicle of the type. + + + + + Euroclass of the vehicle type. Corresponds to the 12-digit European Identification Number (EIN). + + + + + Break down of capacities by FARE CLASS, i.e., maximum number of passengers that TRAIN ELEMENT can carry. + + + + + + + + + + + + + + Elements specifying Requirement properties of VEHICLE TYPE. Vehicle should satisfy these requirements. +SIRI v2.1 + + + + + Whether Vehicle is low floor to facilitate access by the mobility impaired. + + + + + Whether vehicle has lift or ramp to facilitate wheelchair access. + + + + + Whether vehicle has hoist for wheelchair access. + + + + + + + Dimension elements for a VEHICLE TYPE. +SIRI v2.1 + + + + + The length of a VEHICLE of the type. + + + + + The width of a VEHICLE of the type. + + + + + The length of a VEHICLE of the type. + + + + + The weight of a VEHICLE of the type. + + + + + +       diff --git a/xsd/siri_model/siri_journey_support.xsd b/xsd/siri_model/siri_journey_support.xsd index c36a2902..02f9f85e 100644 --- a/xsd/siri_model/siri_journey_support.xsd +++ b/xsd/siri_model/siri_journey_support.xsd @@ -1,1022 +1,1022 @@ - - - - - - main schema - e-service developers - Cen TC278 WG3 SG7 Team - Europe - Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2004-03-05 - - - 2004-10-06 - - - 2005-05-11 - - - 2005-11-15 - - - 2007-03-29 - - - 2008-11-13 - - - - 2011-04-18 - - - - 2012-03-22 - - - - 2013-02-11 - - - -

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

      -

      This subschema defines identifer definitions for common journey elements.

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_journey_support.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_types.xsd - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIG CML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of identifers common journey elements - Standard -       -       - SIRI Journey Model Identifiers. -       - - - - - - - Elements identifying VEHICLE JOURNEY. - - - - - Reference to a LINE. - - - - - Reference to a DIRECTION, typically outward or return. - - - - - A reference to the dated VEHICLE JOURNEY that the VEHICLE is making. - - - - - - - Elements identifying a VEHICLE JOURNEY. LINE and DIRECTION will be same as for journey unless overridden. - - - - - Reference to LINE of journey. - - - - - Reference to DIRECTION of journey. - - - - - A reference to the DATED VEHICLE JOURNEY that the VEHICLE is making, unique with the data horizon of the service. - - - - - - - - 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. - - - - - - Type for Origin and Destination stop of a VEHICLE JOURNEY. - - - - - The origin is used to help identify the VEHICLE JOURNEY. - - - - - Departure time from origin SCHEDULED STOP POINT. - - - - - The destination is used to help identify the VEHICLE JOURNEY. - - - - - Arrival time at destination SCHEDULED STOP POINT. - - - - - - - - Type for a reference to a connecting journey. - - - - - A reference to the DATE VEHICLE JOURNEY that the VEHICLE is making, unique with the data horizon of the service. - - - - - Identify a VEHICLE JOURNEY indirectly by origin and destination as well as the scheduled times at these stops. - - - - - Reference to LINE of journey. - - - - - Reference to TRAIN NUMBER of journey. - - - - - Reference to OPERATOR of journey. - - - - - PARTICIPANT reference that identifies data producer of journey. - - - - - - - - Type for identifer of a SERVICE JOURNEY INTERCHANGE. - - - - - - Type for reference to a SERVICE JOURNEY INTERCHANGE. - - - - - - - - Reference to a SERVICE JOURNEY INTERCHANGE. - - - - - - Type for identifer of a VEHICLE JOURNEY within data Horizon of a service. - - - - - identifier of data frame within particpant service. Used to ensure that the Reference to a DATED VEGICLE JOURNEY 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 identifier of a data VERSION FRAME. - - - - - - Type for identifier of a data VERSION FRAME. - - - - - - - - - Type for identifier of Train Part. - - - - - - Type for reference to a Train Part. - - - - - - - - - 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). - - - - - - - - - Type for identifier of an JOURNEY PART - - - - - - Type for reference to a JOURNEY PART - - - - - - - - Type for identifier of an TRAIN NUMBER - - - - - - Type for reference to a TRAIN NUMBER - - - - - - - - Type for identifier of a TRAIN ELEMENT. An elementary component of a TRAIN (e.g. wagon, locomotive etc.). +SIRI v2.1 - - - - - - Type for reference to a TRAIN ELEMENT. +SIRI v2.1 - - - - - - - - Reference to a TRAIN ELEMENT. +SIRI v2.1 - - - - - Type for identifier of a TRAIN COMPONENT. A TRAIN ELEMENT with a specific order within a TRAIN. +SIRI v2.1 - - - - - - Type for reference to a TRAIN COMPONENT. +SIRI v2.1 - - - - - - - - Reference to a TRAIN COMPONENT. +SIRI v2.1 - - - - - Type for identifier of a TRAIN. An ordered sequence of TRAIN ELEMENTs or TRAIN COMPONENTs respectively. +SIRI v2.1 - - - - - - Type for reference to a TRAIN. +SIRI v2.1 - - - - - - - - Reference to a TRAIN. +SIRI v2.1 - - - - - Type for identifier of a COMPOUND TRAIN. An ordered sequence of TRAINs or TRAIN IN COMPOUND TRAINs respectively. +SIRI v2.1 - - - - - - Type for reference to a COMPOUND TRAIN. +SIRI v2.1 - - - - - - - - Reference to a COMPOUND TRAIN. +SIRI v2.1 - - - - - Type for identifier of a TRAIN IN COMPOUND TRAIN. A TRAIN with a specific order within a COMPOUND TRAIN. +SIRI v2.1 - - - - - - Type for reference to a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 - - - - - - - - Reference to a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 - - - - - Type for identifier of an ENTRANCE TO VEHICLE, e.g. a door of a TRAIN ELEMENT. +SIRI v2.1 - - - - - - Type for reference to an ENTRANCE TO VEHICLE. +SIRI v2.1 - - - - - - - - Reference to an ENTRANCE TO VEHICLE. +SIRI v2.1 - - - - - - Groups together the relevant references needed in a formation. +SIRI v2.1 -Has the following uses: -- Either the smallest part of a formation, a TRAIN COMPONENT, is referenced or the TRAIN itself. The former is ideally used in a FORMATION ASSIGNMENT, i.e. QUAY (sector) assignment, to provide the highest level of detail for passenger orientation. -- If the formation consists of multiple coupled TRAINs, a reference to the COMPOUND TRAIN is also possible. This might be used in a FORMATION CONDITION to signal a change of the train composition. -- In case alighting/boarding data from an automatic passenger counting system is available, the respective vehicle entrances may be referenced. - - - - - - - - - - - - - Allowed types activity for Boarding and Alighting. - - - - - - - - - - - Allowed types activity for Alighting. - - - - - - - - - - Allowed types activity for Boarding. - - - - - - - - - - - - Reference to the origin SCHEDULED STOP POINT of the journey. - - - - - Reference to a SCHEDULED STOP POINT that is a VIA point on the journey. - - - - - Reference to the destination SCHEDULED STOP POINT of the journey. - - - - - Type for reference to a DESTINATION. - - - - - - - - - Information that classifies journey. - - - - - OPERATOR of a VEHICLE JOURNEY. Note that the operator may change over the course of a journey. This shoudl show teh operator for the curent point in the journey. Use Journey Parts tp record all the operators in the whole journeyh. - - - - - Product Classification of VEHICLE 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. -Corresponds to NeTEX TYPE OF SERVICe. - - - - - - - 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. - - - - - - - - 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 still 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 cancelled. - - - - - Service has arrived. - - - - - - - There is no information about the service. - - - - - Service is not expected to call this stop. For instance a flexible service that has not yet been preordered. - - - - - - - Classification of the State of the VEHICLE JOURNEY according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are still classified as on-time. Applications may use this to guide their own presentation of times. - - - - - Service is expected to be performed. - - - - - Service is not expected to be run. For instance a flexible service that has not yet been preordered. - - - - - - - - - Service has departed from first stop. - - - - - - - It has been detected that the Service was completed. - - - - - It is assumed that the Service has completed. - - - - - - - - Classification of the quality of the prediction 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). - - - - - - - Allowed types activity for FirstOrLastJourney. - - - - - - - - - - - - Allowed values for PredictionInaccurateReason, i.e., possible reasons for a change in prediction (in)accuracy. - - - - - Prediction is inaccurate because of a traffic jam. - - - - - Prediction is inaccurate because of technical problems. - - - - - Prediction is inaccurate because of a despatching alteration. - - - - - Prediction is inaccurate because communication errors have prevented any updates. - - - - - Prediction is inaccurate but the reason for an inaccurate prediction is unknown. - - - - - - - - Allowed types of relation between JOURNEYs. - - - - - The journey is a continuation of the specified RelatedJourney at the stop point given in CallInfo. -Passengers don't need to change vehicles. The new journey is not communicated as an interchange. - - - - - The journey is continued by the specified RelatedJourney at the stop point given in CallInfo. -Passengers don't need to change vehicles. The new journey is not communicated as an interchange. - - - - - The journey splits into multiple RelatedJourneys at the stop point given in CallInfo. - - - - - The journey is a continuation of a single RelatedJourney splitting into multiple journeys at the stop point given in CallInfo. - - - - - The journey is the continuation of multiple RelatedJourneys joining together at the stop point given in CallInfo. - - - - - The journey is continued by a single RelatedJourney after joining other journeys at the stop point given in CallInfo. - - - - - The journey replaces one or more partially or fully cancelled RelatedJourneys during the JourneyPart defined or referenced in JourneyPartInfo. - - - - - The partially or fully cancelled journey is replaced by one or more RelatedJourneys during the JourneyPart defined or referenced in JourneyPartInfo. - - - - - The journey partially or fully supports one or more RelatedJourneys during the JourneyPart defined or referenced in JourneyPartInfo. - - - - - The journey is partially or fully supported by one or more RelatedJourneys during the JourneyPart defined or referenced in JourneyPartInfo. - - - - - - - - Allowed values for characterisation of nested QUAYs as part of a STOP ASSIGNMENT. +SIRI v2.1 - - - - - A type of QUAY that consists of multiple QUAYs of type 'platform'. Examples of such groups would be the lower and upper level of a station. - - - - - A type of QUAY that consists of at least two child QUAYs of type 'platformEdge'. - - - - - A type of QUAY which allows direct access to a VEHICLE, e.g. an on-street bus stop, or consists of multiple child QUAYs of type 'platformSector'. - - - - - A QUAY of type 'platformEdge' may be divided into multiple sectors, e.g. "A", "B", "C" etc., to help passengers find a specific part of a vehicle. -The first class carriage of a TRAIN might, for example, be assigned to sector "A" of a QUAY. - - - - - - - - Allowed values for TYPE OF TRAIN ELEMENT. +SIRI v2.1 - - - - - - - - - - - - - - - Allowed values for TRAIN SIZE. +SIRI v2.1 - - - - - - - - - - Allowed values for TYPE OF FUEL. +SIRI v2.1 - - - - - - - - - - - - - - - Classification of FARE CLASSes. +SIRI v2.1 - - - - - List of FARE CLASSes. +SIRI v2.1 - - - - - List of values for FARE CLASSes. +SIRI v2.1 - - - - - - Values for Fare Class Facility. +SIRI v2.1 - - - - - pti23_0 - - - - - pti23_6 - - - - - pti23_7 - - - - - pti23_8 - - - - - - pti23_6_1 - - - - - Business Class - pti23_10 - - - - - Standard class Add pti23_7 - - - - - - pti23_9 - - - - - - - - Allowed values for VEHICLE IN FORMATION STATUS CODE. +SIRI v2.1 - - - - - - - - - - - - - - - - - - Allowed values for FORMATION CHANGE CODE. +SIRI v2.1 - - - - - - - - - - - - - - - - -       + + + + + + main schema + e-service developers + Cen TC278 WG3 SG7 Team + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2004-03-05 + + + 2004-10-06 + + + 2005-05-11 + + + 2005-11-15 + + + 2007-03-29 + + + 2008-11-13 + + + + 2011-04-18 + + + + 2012-03-22 + + + + 2013-02-11 + + + +

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

      +

      This subschema defines identifer definitions for common journey elements.

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_journey_support.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_types.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG CML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of identifers common journey elements + Standard +       +       + SIRI Journey Model Identifiers. +       + + + + + + + Elements identifying VEHICLE JOURNEY. + + + + + Reference to a LINE. + + + + + Reference to a DIRECTION, typically outward or return. + + + + + A reference to the dated VEHICLE JOURNEY that the VEHICLE is making. + + + + + + + Elements identifying a VEHICLE JOURNEY. LINE and DIRECTION will be same as for journey unless overridden. + + + + + Reference to LINE of journey. + + + + + Reference to DIRECTION of journey. + + + + + A reference to the DATED VEHICLE JOURNEY that the VEHICLE is making, unique with the data horizon of the service. + + + + + + + + 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. + + + + + + Type for Origin and Destination stop of a VEHICLE JOURNEY. + + + + + The origin is used to help identify the VEHICLE JOURNEY. + + + + + Departure time from origin SCHEDULED STOP POINT. + + + + + The destination is used to help identify the VEHICLE JOURNEY. + + + + + Arrival time at destination SCHEDULED STOP POINT. + + + + + + + + Type for a reference to a connecting journey. + + + + + A reference to the DATE VEHICLE JOURNEY that the VEHICLE is making, unique with the data horizon of the service. + + + + + Identify a VEHICLE JOURNEY indirectly by origin and destination as well as the scheduled times at these stops. + + + + + Reference to LINE of journey. + + + + + Reference to TRAIN NUMBER of journey. + + + + + Reference to OPERATOR of journey. + + + + + PARTICIPANT reference that identifies data producer of journey. + + + + + + + + Type for identifer of a SERVICE JOURNEY INTERCHANGE. + + + + + + Type for reference to a SERVICE JOURNEY INTERCHANGE. + + + + + + + + Reference to a SERVICE JOURNEY INTERCHANGE. + + + + + + Type for identifer of a VEHICLE JOURNEY within data Horizon of a service. + + + + + identifier of data frame within particpant service. Used to ensure that the Reference to a DATED VEGICLE JOURNEY 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 identifier of a data VERSION FRAME. + + + + + + Type for identifier of a data VERSION FRAME. + + + + + + + + + Type for identifier of Train Part. + + + + + + Type for reference to a Train Part. + + + + + + + + + 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). + + + + + + + + + Type for identifier of an JOURNEY PART + + + + + + Type for reference to a JOURNEY PART + + + + + + + + Type for identifier of an TRAIN NUMBER + + + + + + Type for reference to a TRAIN NUMBER + + + + + + + + Type for identifier of a TRAIN ELEMENT. An elementary component of a TRAIN (e.g. wagon, locomotive etc.). +SIRI v2.1 + + + + + + Type for reference to a TRAIN ELEMENT. +SIRI v2.1 + + + + + + + + Reference to a TRAIN ELEMENT. +SIRI v2.1 + + + + + Type for identifier of a TRAIN COMPONENT. A TRAIN ELEMENT with a specific order within a TRAIN. +SIRI v2.1 + + + + + + Type for reference to a TRAIN COMPONENT. +SIRI v2.1 + + + + + + + + Reference to a TRAIN COMPONENT. +SIRI v2.1 + + + + + Type for identifier of a TRAIN. An ordered sequence of TRAIN ELEMENTs or TRAIN COMPONENTs respectively. +SIRI v2.1 + + + + + + Type for reference to a TRAIN. +SIRI v2.1 + + + + + + + + Reference to a TRAIN. +SIRI v2.1 + + + + + Type for identifier of a COMPOUND TRAIN. An ordered sequence of TRAINs or TRAIN IN COMPOUND TRAINs respectively. +SIRI v2.1 + + + + + + Type for reference to a COMPOUND TRAIN. +SIRI v2.1 + + + + + + + + Reference to a COMPOUND TRAIN. +SIRI v2.1 + + + + + Type for identifier of a TRAIN IN COMPOUND TRAIN. A TRAIN with a specific order within a COMPOUND TRAIN. +SIRI v2.1 + + + + + + Type for reference to a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 + + + + + + + + Reference to a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 + + + + + Type for identifier of an ENTRANCE TO VEHICLE, e.g. a door of a TRAIN ELEMENT. +SIRI v2.1 + + + + + + Type for reference to an ENTRANCE TO VEHICLE. +SIRI v2.1 + + + + + + + + Reference to an ENTRANCE TO VEHICLE. +SIRI v2.1 + + + + + + Groups together the relevant references needed in a formation. +SIRI v2.1 +Has the following uses: +- Either the smallest part of a formation, a TRAIN COMPONENT, is referenced or the TRAIN itself. The former is ideally used in a FORMATION ASSIGNMENT, i.e. QUAY (sector) assignment, to provide the highest level of detail for passenger orientation. +- If the formation consists of multiple coupled TRAINs, a reference to the COMPOUND TRAIN is also possible. This might be used in a FORMATION CONDITION to signal a change of the train composition. +- In case alighting/boarding data from an automatic passenger counting system is available, the respective vehicle entrances may be referenced. + + + + + + + + + + + + + Allowed types activity for Boarding and Alighting. + + + + + + + + + + + Allowed types activity for Alighting. + + + + + + + + + + Allowed types activity for Boarding. + + + + + + + + + + + + Reference to the origin SCHEDULED STOP POINT of the journey. + + + + + Reference to a SCHEDULED STOP POINT that is a VIA point on the journey. + + + + + Reference to the destination SCHEDULED STOP POINT of the journey. + + + + + Type for reference to a DESTINATION. + + + + + + + + + Information that classifies journey. + + + + + OPERATOR of a VEHICLE JOURNEY. Note that the operator may change over the course of a journey. This shoudl show teh operator for the curent point in the journey. Use Journey Parts tp record all the operators in the whole journeyh. + + + + + Product Classification of VEHICLE 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. +Corresponds to NeTEX TYPE OF SERVICe. + + + + + + + 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. + + + + + + + + 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 still 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 cancelled. + + + + + Service has arrived. + + + + + + + There is no information about the service. + + + + + Service is not expected to call this stop. For instance a flexible service that has not yet been preordered. + + + + + + + Classification of the State of the VEHICLE JOURNEY according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are still classified as on-time. Applications may use this to guide their own presentation of times. + + + + + Service is expected to be performed. + + + + + Service is not expected to be run. For instance a flexible service that has not yet been preordered. + + + + + + + + + Service has departed from first stop. + + + + + + + It has been detected that the Service was completed. + + + + + It is assumed that the Service has completed. + + + + + + + + Classification of the quality of the prediction 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). + + + + + + + Allowed types activity for FirstOrLastJourney. + + + + + + + + + + + + Allowed values for PredictionInaccurateReason, i.e., possible reasons for a change in prediction (in)accuracy. + + + + + Prediction is inaccurate because of a traffic jam. + + + + + Prediction is inaccurate because of technical problems. + + + + + Prediction is inaccurate because of a despatching alteration. + + + + + Prediction is inaccurate because communication errors have prevented any updates. + + + + + Prediction is inaccurate but the reason for an inaccurate prediction is unknown. + + + + + + + + Allowed types of relation between JOURNEYs. + + + + + The journey is a continuation of the specified RelatedJourney at the stop point given in CallInfo. +Passengers don't need to change vehicles. The new journey is not communicated as an interchange. + + + + + The journey is continued by the specified RelatedJourney at the stop point given in CallInfo. +Passengers don't need to change vehicles. The new journey is not communicated as an interchange. + + + + + The journey splits into multiple RelatedJourneys at the stop point given in CallInfo. + + + + + The journey is a continuation of a single RelatedJourney splitting into multiple journeys at the stop point given in CallInfo. + + + + + The journey is the continuation of multiple RelatedJourneys joining together at the stop point given in CallInfo. + + + + + The journey is continued by a single RelatedJourney after joining other journeys at the stop point given in CallInfo. + + + + + The journey replaces one or more partially or fully cancelled RelatedJourneys during the JourneyPart defined or referenced in JourneyPartInfo. + + + + + The partially or fully cancelled journey is replaced by one or more RelatedJourneys during the JourneyPart defined or referenced in JourneyPartInfo. + + + + + The journey partially or fully supports one or more RelatedJourneys during the JourneyPart defined or referenced in JourneyPartInfo. + + + + + The journey is partially or fully supported by one or more RelatedJourneys during the JourneyPart defined or referenced in JourneyPartInfo. + + + + + + + + Allowed values for characterisation of nested QUAYs as part of a STOP ASSIGNMENT. +SIRI v2.1 + + + + + A type of QUAY that consists of multiple QUAYs of type 'platform'. Examples of such groups would be the lower and upper level of a station. + + + + + A type of QUAY that consists of at least two child QUAYs of type 'platformEdge'. + + + + + A type of QUAY which allows direct access to a VEHICLE, e.g. an on-street bus stop, or consists of multiple child QUAYs of type 'platformSector'. + + + + + A QUAY of type 'platformEdge' may be divided into multiple sectors, e.g. "A", "B", "C" etc., to help passengers find a specific part of a vehicle. +The first class carriage of a TRAIN might, for example, be assigned to sector "A" of a QUAY. + + + + + + + + Allowed values for TYPE OF TRAIN ELEMENT. +SIRI v2.1 + + + + + + + + + + + + + + + Allowed values for TRAIN SIZE. +SIRI v2.1 + + + + + + + + + + Allowed values for TYPE OF FUEL. +SIRI v2.1 + + + + + + + + + + + + + + + Classification of FARE CLASSes. +SIRI v2.1 + + + + + List of FARE CLASSes. +SIRI v2.1 + + + + + List of values for FARE CLASSes. +SIRI v2.1 + + + + + + Values for Fare Class Facility. +SIRI v2.1 + + + + + pti23_0 + + + + + pti23_6 + + + + + pti23_7 + + + + + pti23_8 + + + + + + pti23_6_1 + + + + + Business Class - pti23_10 + + + + + Standard class Add pti23_7 + + + + + + pti23_9 + + + + + + + + Allowed values for VEHICLE IN FORMATION STATUS CODE. +SIRI v2.1 + + + + + + + + + + + + + + + + + + Allowed values for FORMATION CHANGE CODE. +SIRI v2.1 + + + + + + + + + + + + + + + + +       diff --git a/xsd/siri_model/siri_modelPermissions.xsd b/xsd/siri_model/siri_modelPermissions.xsd index 51e9e4bf..09a3a899 100644 --- a/xsd/siri_model/siri_modelPermissions.xsd +++ b/xsd/siri_model/siri_modelPermissions.xsd @@ -1,338 +1,338 @@ - - - - - - - - - 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/schema/2.0/xsd/siri_model}siri_modelPermissions.xsd - [ISO 639-2/B] ENG - CEN - - http://www.siri.org.uk/schema/2.0/xsd/siri_types.xsd - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIGXML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI XML schema. Common Permission elements. - Standard -       -       -       - - - Type for abstract permissions. - - - - - Version of permission set. - - - - - - - - - The LINEs that the participant may access. - - - - - - - Participant's permission for this LINE. - - - - - - - - Type for Line Permission. - - - - - - - Reference to a LINE. whose data participant is allowed to access. - - - - - Reference to a DIRECTION of LINE. that participant is allowed to access. - - - - - - - - - The OPERATOR data that the participant may access. - - - - - - - Participant's permission for this OPERATOR. - - - - - - - - Type for OPERATOR Permission. - - - - - - - Reference to an OPERATOR whose data participant is allowed to access. - - - - - - - - - The CONNECTION links that the participant may access. - - - - - - - Participant's permission for this CONNECTION link. - - - - - - - - Type for CONNECTION link Permission. - - - - - - - Reference to a CONNECTION link for which permission is made. - - - - - - - - - Type for Monitoring Point (LOGICAL DISPLAY) Permission. - - - - - - - Reference to a Stop Monitoring point (LOGICAL DISPLAY) to which permission applies. - - - - - - - - - - Whether results can be filtered by VALIDITY PERIOD. 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 (LOGICAL DISPLAY). 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 SCHEDULED STOP POINT. Default is 'true'. - - - - - Whether results can be filtered by SERVICE JOURNEY INTERCHANGE. Default is 'false'. - - - - - Whether results can be filtered by VEHICLE JOURNEY. Default is 'false'. - - - - - Whether results can be filtered by Facility (EQUIPMENT). Default is 'true'. - - - - - Whether results can be filtered by VEHICLE MODE. Default is 'true'. +SIRI v2.1 - - - - - Whether results can be filtered by PRODUCT CATEGORY. Default is 'true'. +SIRI v2.1 - - - - - - Type for Monitoring Service Capability access control. - - - - - - - - - - - - - - - Permission for a single participant or all participants to use an aspect of the service. - - - - - Type for Monitoring Service Permission. - - - - - - - - - - - - - - - Abstract type for 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 (LOGICAL DISPLAY) is supported. Default is 'true'. - - - - - If access control is supported, whether access control by CONNECTION link is supported. Default is 'true'. - - -       + + + + + + + + + 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/schema/2.0/xsd/siri_model}siri_modelPermissions.xsd + [ISO 639-2/B] ENG + CEN + + http://www.siri.org.uk/schema/2.0/xsd/siri_types.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIGXML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI XML schema. Common Permission elements. + Standard +       +       +       + + + Type for abstract permissions. + + + + + Version of permission set. + + + + + + + + + The LINEs that the participant may access. + + + + + + + Participant's permission for this LINE. + + + + + + + + Type for Line Permission. + + + + + + + Reference to a LINE. whose data participant is allowed to access. + + + + + Reference to a DIRECTION of LINE. that participant is allowed to access. + + + + + + + + + The OPERATOR data that the participant may access. + + + + + + + Participant's permission for this OPERATOR. + + + + + + + + Type for OPERATOR Permission. + + + + + + + Reference to an OPERATOR whose data participant is allowed to access. + + + + + + + + + The CONNECTION links that the participant may access. + + + + + + + Participant's permission for this CONNECTION link. + + + + + + + + Type for CONNECTION link Permission. + + + + + + + Reference to a CONNECTION link for which permission is made. + + + + + + + + + Type for Monitoring Point (LOGICAL DISPLAY) Permission. + + + + + + + Reference to a Stop Monitoring point (LOGICAL DISPLAY) to which permission applies. + + + + + + + + + + Whether results can be filtered by VALIDITY PERIOD. 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 (LOGICAL DISPLAY). 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 SCHEDULED STOP POINT. Default is 'true'. + + + + + Whether results can be filtered by SERVICE JOURNEY INTERCHANGE. Default is 'false'. + + + + + Whether results can be filtered by VEHICLE JOURNEY. Default is 'false'. + + + + + Whether results can be filtered by Facility (EQUIPMENT). Default is 'true'. + + + + + Whether results can be filtered by VEHICLE MODE. Default is 'true'. +SIRI v2.1 + + + + + Whether results can be filtered by PRODUCT CATEGORY. Default is 'true'. +SIRI v2.1 + + + + + + Type for Monitoring Service Capability access control. + + + + + + + + + + + + + + + Permission for a single participant or all participants to use an aspect of the service. + + + + + Type for Monitoring Service Permission. + + + + + + + + + + + + + + + Abstract type for 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 (LOGICAL DISPLAY) is supported. Default is 'true'. + + + + + If access control is supported, whether access control by CONNECTION link is supported. Default is 'true'. + + +       diff --git a/xsd/siri_model/siri_modes.xsd b/xsd/siri_model/siri_modes.xsd index c2a8f264..ca684528 100644 --- a/xsd/siri_model/siri_modes.xsd +++ b/xsd/siri_model/siri_modes.xsd @@ -1,686 +1,686 @@ - - - - - - main schema - e-service developers - Add names - Europe - >Drafted for version 1.0 Kizoom Incident Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk - - 2004-09-29 - - - 2004-10-01 - - - 2005-02-14 - - - 2007-03-29 - - -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_modes.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - - Kizoom 2000-2005, CEN 2009-2021 - - -
        -
      • Schema derived Derived from the Kizoom XTIS schema
        • -
      • Derived from the TPEG Categories schema
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of common Mode elements - Standard -       -       - SIRI TRANSPORT MODEs -       - - - - - Transport Sub Modes. - - - - - - - - - PT Transport Sub Modes. - - - - - - - - - - - - - - - - Non PT Road Submodes. - - - - - - - - - Submode of mode. - - - - - - - - - - - - - - - - Vehicle mode- 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. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - DEPRECATED since SIRI 2.1 - - - - - - - - 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. - - - - - - - - - - - - - - - - - - -       + + + + + + main schema + e-service developers + Add names + Europe + >Drafted for version 1.0 Kizoom Incident Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk + + 2004-09-29 + + + 2004-10-01 + + + 2005-02-14 + + + 2007-03-29 + + +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_modes.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + + Kizoom 2000-2005, CEN 2009-2021 + + +
        +
      • Schema derived Derived from the Kizoom XTIS schema
        • +
      • Derived from the TPEG Categories schema
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of common Mode elements + Standard +       +       + SIRI TRANSPORT MODEs +       + + + + + Transport Sub Modes. + + + + + + + + + PT Transport Sub Modes. + + + + + + + + + + + + + + + + Non PT Road Submodes. + + + + + + + + + Submode of mode. + + + + + + + + + + + + + + + + Vehicle mode- 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. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + DEPRECATED since SIRI 2.1 + + + + + + + + TPEG pti03 Coach submodes. + + + + + Values for Coach ModesOfTransport: TPEG pti_table_03. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + TPEG pti04 Metro submodes. + + + + + Values for Metro ModesOfTransport: TPEG pti_table_04. + + + + + + + + + + + + + + + + + + + + TPEG pti05 Bus submodes. + + + + + Values for Bus ModesOfTransport: TPEG pti_table_05, loc_table_10. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + TPEG pti06 Tram submodes. + + + + + Values for Tram ModesOfTransport: TPEG pti_table_06, loc_table_12. + + + + + + + + + + + + + + + + + + + + + + + + + + + + TPEG pti07 Water submodes. + + + + + Values for Water ModesOfTransport: TPEG pti_table_07. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + TPEG pti08 Air submodes. + + + + + Values for Air ModesOfTransport: TPEG pti_table_08. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + TPEG pti09 Telecabin submodes. + + + + + Values for Telecabin ModesOfTransport: TPEG pti_table_09, loc_table_14. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + TPEG pti10 Funicular submodes. + + + + + Values for Funicular ModesOfTransport: TPEG pti_table_10. + + + + + + + + + + + + + + + + + TPEG pti11 Taxi submodes. + + + + + Values for Taxi ModesOfTransport: TPEG pti_table_11. + + + + + + + + + + + + + + + + + + + + + + + + + + TPEG pti12 SelfDrive submodes. + + + + + Values for SelfDrive ModesOfTransport: TPEG pti_table_12. + + + + + + + + + + + + + + + + + + +       diff --git a/xsd/siri_model/siri_monitoredVehicleJourney.xsd b/xsd/siri_model/siri_monitoredVehicleJourney.xsd index 6b52473c..1bca27b4 100644 --- a/xsd/siri_model/siri_monitoredVehicleJourney.xsd +++ b/xsd/siri_model/siri_monitoredVehicleJourney.xsd @@ -1,638 +1,638 @@ - - - - - - main schema - e-service developers - Cen TC278 WG3 SG7 Team - Europe - Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2004-03-05 - - - 2004-10-06 - - - 2005-05-11 - - - 2005-11-15 - - - 2007-03-29 - - 2008-11-13 - - - 2011-04-18 - - - 2012-03-22 - - - 2012-04-27 - - - 2012-04-27 - - - -

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

      -

      This subschema defines common journey elements.

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_monitoredVehicleJourney.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd - - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIG CML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of common Journey elements - Standard -       -       - SIRI MONITORED VEHICLE JOURNEY Model. -       - - - - - - Type for Monitored VEHICLE JOURNEY. - - - - - - - - - - - - - - Elements describing the real-time progress of a monitored VEHICLE JOURNEY. - - - - - Whether there is real-time information available for journey. Default is 'true'. -It is recommended to specify a MonitoringError if Monitored is set to 'false'. - - - - - If Monitored is 'false', a (list of) reason(s) for non-availability of real-time data. Examples are "GPS", "GPRS", "Radio" etc. -MonitoringError must not be used if Monitored is omitted or set to 'true'. - - - - - - - - - Elements describing the qua;ity of real-time progress data of a journey. - - - - - Whether the VEHICLE iis 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, default is 'false'. - - - - - - - System originating real-time data. Can be used to make judgements of relative quality and accuracy compared to other feeds. - - - - - Confidence QUALITY LEVEL of data. Default is 'reliable'. - - - - - - - Elements describing the real-time progress of a journey. - - - - - Current geospatial location of VEHICLE. Measured to front of vehicle. - - - - - Time at which location was recorded. If not present assume that the recorded at time on the containing delivery. - - - - - Bearing in compass degrees in which VEHICLE is heading. - - - - - Rate of progress of VEHICLE. Default is 'normal' - - - - - Velocity of VEHICLE. EIther actual speed or average speed may be used. +SIRI v2.0 - - - - - Whether the engine of the vehicle is on. Default is 'true' (+SIRI 2.0) - - - - - - Delay of VEHICLE against schedule, to a precision in seconds. Early times are shown as negative values. - - - - - An arbitrary textual status description of the running of this VEHICLE JOURNEY. (Unbounded 0:* since SIRI 2.0) - - - - - An classification of the progress state of running of this VEHICLE JOURNEY. +SIRI 2.0 - - - - - - - Elements describing the main places bewteen which a VEHICLE JOURNEY runs. - - - - - Origin of the VEHICLE JOURNEY. - - - - - - - - - - - VIA points for VEHICLE JOURNEY - - - - - - - - Relative priority for incliding via in displays. 1 Is high 3 is low. +SIRI v2.0 - - - - - - - - Destination of VEHICLE 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. -For SIRI-SM this is the stop for which data is requested. -For SIRI-VM this is the most recent stop visited by the VEHICLE. - - - - - 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. Default is 'false'. - - - - - - - - Type for a reference to JOURNEY PART. +SIRI v2.0 - - - - - Reference to a JOURNEY part. +SIRI v2.0 - - - - - Train Number for JOURNEY PART +SIRI v2.0 - - - - - Operator of JOURNEY PART. +SIRI v2.0 - - - - - Reference to COMPOUND TRAIN that represents the train formation/composition as a whole (for this JOURNEY PART). +SIRI v2.1 -A journey does always have one or more JOURNEY PARTs for which the train formation/composition remains unchanged. - - - - - - - - Type for a reference to JOURNEY PART. +SIRI v2.1 - - - - - Reference to a JOURNEY part. - - - - - Train Number for JOURNEY PART. - - - - - Operator of JOURNEY PART. - - - - - Reference to COMPOUND TRAIN that represents the train formation/composition as a whole (for this JOURNEY PART). +SIRI v2.1 -A journey does always have one or more JOURNEY PARTs for which the train formation/composition remains unchanged. - - - - - - - - - If no JOURNEY PART reference is available (or in addition to the reference), identify it indirectly by From-/ToStopPointRef and Start-/EndTime (i.e. the scheduled times at these stops). +SIRI v2.1 - - - - - Reference to the SCHEDULED STOP POINT at which the related JOURNEY PART begins. - - - - - Reference to the SCHEDULED STOP POINT at which the related JOURNEY PART ends. - - - - - Time at which the related JOURNEY PART begins. - - - - - Time at which the related JOURNEY PART ends. - - - - - - - - Type for BLOCK part elements of VEHICLE JOURNEY. - - - - - Total number of BLOCK parts making up the train of which this is part. - - - - - Reference to a 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 BLOCKparts, there will be a separate delivery for each BLOCKp art and this element will indicate the vehicles that the journey part uses. - - - - - - TRAIN NUMBERs for journey. +SIRI v2.0 - - - - - - TRAIN NUMBER assigned to VEHICLE JOURNEY. +SIRI 2.0 - - - - - - - - JOURNEY PARTs making up JOURNEY +SIRIv2.0 e. - - - - - - Information about Parts of JOURNEY +SIRI v2.0 - - - - - - - - - - - Operational information about the monitored VEHICLE JOURNEY. - - - - - If a VEHICLE JOURNEY is a coupled journey, i.e. comprises several coupled BLOCKparts, there will be a separate delivery for each BLOCKp art and this element will indicate the vehicles that the journey part uses. - - - - - - TRAIN NUMBERs for journey. +SIRI v2.0 - - - - - - TRAIN NUMBER assigned to VEHICLE JOURNEY. +SIRI 2.0 - - - - - - - - JOURNEY PARTs making up JOURNEY +SIRIv2.0 e. - - - - - - Information about Parts of JOURNEY +SIRI v2.0 - - - - - - - - - - - - - Type for Ordered list of CALLs at previous stop. - - - - - - - - Type for CALL at previous stop. - - - - - - - - - - - - - - - - Type for Current CALL at stop. - - - - - - - - - - - - - Elements for a monitored CALL. - - - - - - - - - - - - - - - - Elements describing the Real-time CALL properties. - - - - - - Exact location that VEHICLE will take up / or has taken at STOP POINT. - - - - - - - Elements describing theProperties specific to a 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. - - - - - - - Elements describing the the arrival of a VEHICLE at a stop. - - - - - - - - - Arrival times for CALL. - - - - - - Latest time at which a VEHICLE will arrive at stop. +SIRI v2.0 - - - - - - - Elements describing the the departure of a VEHICLE from a stop. - - - - - - - - - - Departure times for CALL. - - - - - - Expected departure time of VEHICLE without waiting time due to operational actions. For people at stop this would normally be shown if different from Expected Departure time. +SIRI v2.0. - - - - - Earliest time at which VEHICLE may leave the stop. Used to secure connections. Passengers must be at boarding point by this time to be sure of catching VEHICLE. +SIRI v2.0 - - - - - Prediction quality, either as approcimate level, or more quantitatyive percentile range of predictions will fall within a given range of times. +SIRI v2.0 - - - - - -       + + + + + + main schema + e-service developers + Cen TC278 WG3 SG7 Team + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2004-03-05 + + + 2004-10-06 + + + 2005-05-11 + + + 2005-11-15 + + + 2007-03-29 + + 2008-11-13 + + + 2011-04-18 + + + 2012-03-22 + + + 2012-04-27 + + + 2012-04-27 + + + +

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

      +

      This subschema defines common journey elements.

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_monitoredVehicleJourney.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd + + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG CML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of common Journey elements + Standard +       +       + SIRI MONITORED VEHICLE JOURNEY Model. +       + + + + + + Type for Monitored VEHICLE JOURNEY. + + + + + + + + + + + + + + Elements describing the real-time progress of a monitored VEHICLE JOURNEY. + + + + + Whether there is real-time information available for journey. Default is 'true'. +It is recommended to specify a MonitoringError if Monitored is set to 'false'. + + + + + If Monitored is 'false', a (list of) reason(s) for non-availability of real-time data. Examples are "GPS", "GPRS", "Radio" etc. +MonitoringError must not be used if Monitored is omitted or set to 'true'. + + + + + + + + + Elements describing the qua;ity of real-time progress data of a journey. + + + + + Whether the VEHICLE iis 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, default is 'false'. + + + + + + + System originating real-time data. Can be used to make judgements of relative quality and accuracy compared to other feeds. + + + + + Confidence QUALITY LEVEL of data. Default is 'reliable'. + + + + + + + Elements describing the real-time progress of a journey. + + + + + Current geospatial location of VEHICLE. Measured to front of vehicle. + + + + + Time at which location was recorded. If not present assume that the recorded at time on the containing delivery. + + + + + Bearing in compass degrees in which VEHICLE is heading. + + + + + Rate of progress of VEHICLE. Default is 'normal' + + + + + Velocity of VEHICLE. EIther actual speed or average speed may be used. +SIRI v2.0 + + + + + Whether the engine of the vehicle is on. Default is 'true' (+SIRI 2.0) + + + + + + Delay of VEHICLE against schedule, to a precision in seconds. Early times are shown as negative values. + + + + + An arbitrary textual status description of the running of this VEHICLE JOURNEY. (Unbounded 0:* since SIRI 2.0) + + + + + An classification of the progress state of running of this VEHICLE JOURNEY. +SIRI 2.0 + + + + + + + Elements describing the main places bewteen which a VEHICLE JOURNEY runs. + + + + + Origin of the VEHICLE JOURNEY. + + + + + + + + + + + VIA points for VEHICLE JOURNEY + + + + + + + + Relative priority for incliding via in displays. 1 Is high 3 is low. +SIRI v2.0 + + + + + + + + Destination of VEHICLE 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. +For SIRI-SM this is the stop for which data is requested. +For SIRI-VM this is the most recent stop visited by the VEHICLE. + + + + + 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. Default is 'false'. + + + + + + + + Type for a reference to JOURNEY PART. +SIRI v2.0 + + + + + Reference to a JOURNEY part. +SIRI v2.0 + + + + + Train Number for JOURNEY PART +SIRI v2.0 + + + + + Operator of JOURNEY PART. +SIRI v2.0 + + + + + Reference to COMPOUND TRAIN that represents the train formation/composition as a whole (for this JOURNEY PART). +SIRI v2.1 +A journey does always have one or more JOURNEY PARTs for which the train formation/composition remains unchanged. + + + + + + + + Type for a reference to JOURNEY PART. +SIRI v2.1 + + + + + Reference to a JOURNEY part. + + + + + Train Number for JOURNEY PART. + + + + + Operator of JOURNEY PART. + + + + + Reference to COMPOUND TRAIN that represents the train formation/composition as a whole (for this JOURNEY PART). +SIRI v2.1 +A journey does always have one or more JOURNEY PARTs for which the train formation/composition remains unchanged. + + + + + + + + + If no JOURNEY PART reference is available (or in addition to the reference), identify it indirectly by From-/ToStopPointRef and Start-/EndTime (i.e. the scheduled times at these stops). +SIRI v2.1 + + + + + Reference to the SCHEDULED STOP POINT at which the related JOURNEY PART begins. + + + + + Reference to the SCHEDULED STOP POINT at which the related JOURNEY PART ends. + + + + + Time at which the related JOURNEY PART begins. + + + + + Time at which the related JOURNEY PART ends. + + + + + + + + Type for BLOCK part elements of VEHICLE JOURNEY. + + + + + Total number of BLOCK parts making up the train of which this is part. + + + + + Reference to a 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 BLOCKparts, there will be a separate delivery for each BLOCKp art and this element will indicate the vehicles that the journey part uses. + + + + + + TRAIN NUMBERs for journey. +SIRI v2.0 + + + + + + TRAIN NUMBER assigned to VEHICLE JOURNEY. +SIRI 2.0 + + + + + + + + JOURNEY PARTs making up JOURNEY +SIRIv2.0 e. + + + + + + Information about Parts of JOURNEY +SIRI v2.0 + + + + + + + + + + + Operational information about the monitored VEHICLE JOURNEY. + + + + + If a VEHICLE JOURNEY is a coupled journey, i.e. comprises several coupled BLOCKparts, there will be a separate delivery for each BLOCKp art and this element will indicate the vehicles that the journey part uses. + + + + + + TRAIN NUMBERs for journey. +SIRI v2.0 + + + + + + TRAIN NUMBER assigned to VEHICLE JOURNEY. +SIRI 2.0 + + + + + + + + JOURNEY PARTs making up JOURNEY +SIRIv2.0 e. + + + + + + Information about Parts of JOURNEY +SIRI v2.0 + + + + + + + + + + + + + Type for Ordered list of CALLs at previous stop. + + + + + + + + Type for CALL at previous stop. + + + + + + + + + + + + + + + + Type for Current CALL at stop. + + + + + + + + + + + + + Elements for a monitored CALL. + + + + + + + + + + + + + + + + Elements describing the Real-time CALL properties. + + + + + + Exact location that VEHICLE will take up / or has taken at STOP POINT. + + + + + + + Elements describing theProperties specific to a 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. + + + + + + + Elements describing the the arrival of a VEHICLE at a stop. + + + + + + + + + Arrival times for CALL. + + + + + + Latest time at which a VEHICLE will arrive at stop. +SIRI v2.0 + + + + + + + Elements describing the the departure of a VEHICLE from a stop. + + + + + + + + + + Departure times for CALL. + + + + + + Expected departure time of VEHICLE without waiting time due to operational actions. For people at stop this would normally be shown if different from Expected Departure time. +SIRI v2.0. + + + + + Earliest time at which VEHICLE may leave the stop. Used to secure connections. Passengers must be at boarding point by this time to be sure of catching VEHICLE. +SIRI v2.0 + + + + + Prediction quality, either as approcimate level, or more quantitatyive percentile range of predictions will fall within a given range of times. +SIRI v2.0 + + + + + +       diff --git a/xsd/siri_model/siri_operator_support.xsd b/xsd/siri_model/siri_operator_support.xsd index ca28a2d9..8779065a 100644 --- a/xsd/siri_model/siri_operator_support.xsd +++ b/xsd/siri_model/siri_operator_support.xsd @@ -1,87 +1,87 @@ - - - - - - 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 - Add organisation cidoe - - -

      SIRI Real-time server interface. This subschema defines transport OPERATOR base types.

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_operator_support.xsd - [ISO 639-2/B] ENG - CEN - Add POSTAL ADDRESS - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the SIRI standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI Server Interface for Real-tiem Info - OPERATOR Types. - Standard -       -       - OPERATOR types for SIRi. -       - - - - Reference to an OPERATOR. - - - - - - - - Type for identifier of an OPERATOR Code. - - - - - - - Reference to an Organisation. - - - - - - - - Type for identifier of an OrganisationCode. - - - - -       + + + + + + 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 + Add organisation cidoe + + +

      SIRI Real-time server interface. This subschema defines transport OPERATOR base types.

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_operator_support.xsd + [ISO 639-2/B] ENG + CEN - Add POSTAL ADDRESS + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the SIRI standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI Server Interface for Real-tiem Info - OPERATOR Types. + Standard +       +       + OPERATOR types for SIRi. +       + + + + Reference to an OPERATOR. + + + + + + + + Type for identifier of an OPERATOR Code. + + + + + + + Reference to an Organisation. + + + + + + + + Type for identifier of an OrganisationCode. + + + + +       diff --git a/xsd/siri_model/siri_reference.xsd b/xsd/siri_model/siri_reference.xsd index d0b9ab61..e930abea 100644 --- a/xsd/siri_model/siri_reference.xsd +++ b/xsd/siri_model/siri_reference.xsd @@ -1,844 +1,844 @@ - - - - - - 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 - - - 2012-03-22 - - - - 2012-06-22 - - - - 2013-02-11 - - - - 2018-11-08 - - - - 2020-01-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/schema/2.0/xsd/siri/utility/}siri_reference.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIG CML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Common DomainModel elements. - Standard -       -       -       - - - - - - - - - - Version Identifier. - - - - - Type for identifier of a Version. - - - - - - Type for reference Timetable Version. - - - - - - - - - Type for identifier of a SCHEDULED STOP POINT. - - - - - - Reference to a SCHEDULED STOP POINT. - - - - - - - - Sequence of visit to SCHEDULED STOP POINT.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. - - - - - Elements for a SCHEDULED STOP POINT. - - - - - Reference to a SCHEDULED STOP POINT. - Reference to a STOP POINT. - - - - - Name of SCHEDULED STOP POINT. (Unbounded since SIRI 2.0) - - - - - - - Reference to a SCHEDULED STOP POINT. - Reference to a STOP POINT. - - - - - Name of SCHEDULED STOP POINT. - - - - - Elements identifying an ordered visit to a SCHEDULED STOP POINT within a SERVICE PATTERN. - - - - - - - - Name of SCHEDULED STOP POINT. (Unbounded since SIRI 2.0) - - - - - - - Elements identifying Ordered visit to a stop within calling sequence of a SERVICE PATTERN. - - - - - - - - Name of SCHEDULED STOP POINT. (Unbounded since SIRI 2.0) - - - - - - - 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. - - - - - - - - - Type for identifier of a STOP AREA. - - - - - - Reference to a STOP AREA. - - - - - - - - - Type for identifier of a QUAY (Platform, Bay, etc). - - - - - - Type for reference to a QUAY. - - - - - - - - - Type for identifier of a BOARDING POSITION (location on a QUAY where passengers can actually board/alight). - - - - - - Type for reference to a BOARDING POSITION. - - - - - - - - - Type for identifier of a FLEXIBLE AREA (area that encompasses the stop location of a flexible service). - - - - - - Type for reference to a FLEXIBLE AREA. - - - - - - - - - Identifier of a monitoring point. May correspond to a SCHEDULED STOP POINT or represent a group of Stops other Timing Points (i.e. LOGICAL DISPLAY) - - - - - - Type for reference to a monitoring point (LOGICAL DISPLAY). - - - - - - - - - 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. Default is false (xml default added from SIRI 2.0) - - - - - - Type for identifier of a CONNECTION link - - - - - - Reference to a CONNECTION link - - - - - Type for reference to a CONNECTION link - - - - - - - - - MODEs of transport applicable to timetabled public transport. - - - - - - - - - - - - - - - MODEs of transport applicable to private and non-timetabled transport. - - - - - - - - - - - - - - Union of VEHICLE and continuous MODEs. - - - - - - - - - - - - - - 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 JOURNEY PATTERN Identfiers associated with a journey. - - - - - - - Elements describing the LINE, ROUTE and DIRECTION of a VEHICLE JOURNEYwhich are derived from the JOURNEY PATTERN associated with the 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. - - - - - Name of Joruney Pattern - - - - - A means of transportation such as bus, rail, etc. - - - - - Identifier of ROUTE that journey follows. - - - - - Name or Number by which the LINE is known to the public. (Unbounded since SIRI 2.0) - - - - - Reference to a GROUP OF LINEs to which journey belongs. SIRI 2.0 - - - - - Description of the DIRECTION. May correspond to a DESTINATION DISPLAY. (Unbounded since SIRI 2.0) - - - - - Alternative identifier of LINE that an external system may associate with journey. - - - - - - Reference to a BRANDING. +SIRI v2.1 - - - - - An arbitrary marketing classification. +SIRI v2.1 - - - - - - - - Elements for identifying a LINE and DIRECTION. - - - - - Reference to a LINE. - - - - - Reference to a LINE DIRECTION DIRECTION, typically outward or return. - - - - - - - Type for LINEand DIRECTION. - - - - - - Elements for a LINE and DIRECTION. - - - - - Line Reference. - - - - - Direction Reference. - - - - - - - Type for identifier of a LINE - - - - - - Reference to a LINE. - - - - - Type for reference to a LINE. - - - - - - - - Elements describing the LINEand DESTINATION of a journey. Values for these elements can be specified on an annual schedule and will be inherited, unless overriden, onto the production timetable and then onto the individul dated VEHICLE JOURNEYs of the timetable. Each real-time journey takes its values from the dated VEHICLE JOURNEY that it follows. The absence of a value on an entity at a given level indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity. - - - - - - Description of the destination stop (vehicle signage), if different from the that in timetable - the DESTINATION DISPLAY. Can be overwritten section by section by the entry in an individual CALL. - - - - - - - Name or Number by which the LINEis known to the public. - - - - - Identifier of a GROUP OF LINEs - - - - - - Reference to a GROUP OF LINEs - - - - - - - - - Type for 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. - - - - - - - - Identifier of a ROUTE LINk. - - - - - - Reference to a ROUTE LINk. - - - - - - - - - Type for identifier of a DESTINATION. - - - - - - Reference 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. - - - - - Reference to a TOPOGRAPHIC PLACE. - - - - - Names of place used to help identify the LINE. - - - - - Short name of TOPOGRAPHIC PLACE. Should only be included if the detail level was requested. - - - - - - - - Identifier of a VEHICLE. - - - - - - Reference to a VEHICLE. - - - - - - - - Reference to a VEHICLE. - - - - - Passenger load status of a VEHICLE - GTFS-R / TPEG Pts045 - - - - - TPEG Pts45_0, unknown - - - - - GTFS-R "EMPTY" - The vehicle is considered empty by most measures, and has few or no passengers onboard, but is still accepting passengers. - - - - - GTFS-R "MANY_SEATS_AVAILABLE" / TPEG Pts45_1, many seats available - The vehicle has a large percentage of seats available. What percentage of free seats out of the total seats available is to be considered large enough to fall into this category is determined at the discretion of the producer. - - - - - GTFS-R "FEW_SEATS_AVAILABLE" / TPEG Pts45_2, few seats available - The vehicle has a small percentage of seats available. What percentage of free seats out of the total seats available is to be considered small enough to fall into this category is determined at the discretion of the producer. - - - - - GTFS-R "STANDING_ROOM_ONLY" / TPEG Pts45_4, standing room only (and TPEG Pts45_3, no seats available) - The vehicle can currently accommodate only standing passengers. - - - - - GTFS-R "CRUSHED_STANDING_ROOM_ONLY" - The vehicle can currently accommodate only standing passengers and has limited space for them. - - - - - GTFS-R "FULL" / TPEG Pts45_5, full - - - - - GTFS-R "NOT_ACCEPTING_PASSENGERS" - The vehicle cannot accept passengers. - - - - - TPEG Pts45_255, undefined occupancy - - - - - (SIRI 2.1) deprecated - use a more specific value - - - - - (SIRI 2.1) deprecated - use a more specific value - - - - - - - Identifier of a DRIVER - - - - - - Reference to a DRIVER. - - - - - - - - - DataType for a NOTICe. - - - - - - - - Text annotation that applies to an element. - - - - - - - - Type for identifier of an Info Channel. - - - - - - Type for reference to an Info Channel. - - - - - - - - - Type for identifier of a BRANDING. +SIRI v2.1 - - - - - - Type for reference to a BRANDING. +SIRI v2.1 - - - - - - - - An arbitrary marketing classification. +SIRI v2.1 - - - - - Identity of BRANDING. - - - - - - - - - Identifier of a SITE - - - - - - Reference to a SITE - - - - - - - - Reference to a SITE - - -       + + + + + + 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 + + + 2012-03-22 + + + + 2012-06-22 + + + + 2013-02-11 + + + + 2018-11-08 + + + + 2020-01-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/schema/2.0/xsd/siri/utility/}siri_reference.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG CML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Common DomainModel elements. + Standard +       +       +       + + + + + + + + + + Version Identifier. + + + + + Type for identifier of a Version. + + + + + + Type for reference Timetable Version. + + + + + + + + + Type for identifier of a SCHEDULED STOP POINT. + + + + + + Reference to a SCHEDULED STOP POINT. + + + + + + + + Sequence of visit to SCHEDULED STOP POINT.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. + + + + + Elements for a SCHEDULED STOP POINT. + + + + + Reference to a SCHEDULED STOP POINT. + Reference to a STOP POINT. + + + + + Name of SCHEDULED STOP POINT. (Unbounded since SIRI 2.0) + + + + + + + Reference to a SCHEDULED STOP POINT. + Reference to a STOP POINT. + + + + + Name of SCHEDULED STOP POINT. + + + + + Elements identifying an ordered visit to a SCHEDULED STOP POINT within a SERVICE PATTERN. + + + + + + + + Name of SCHEDULED STOP POINT. (Unbounded since SIRI 2.0) + + + + + + + Elements identifying Ordered visit to a stop within calling sequence of a SERVICE PATTERN. + + + + + + + + Name of SCHEDULED STOP POINT. (Unbounded since SIRI 2.0) + + + + + + + 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. + + + + + + + + + Type for identifier of a STOP AREA. + + + + + + Reference to a STOP AREA. + + + + + + + + + Type for identifier of a QUAY (Platform, Bay, etc). + + + + + + Type for reference to a QUAY. + + + + + + + + + Type for identifier of a BOARDING POSITION (location on a QUAY where passengers can actually board/alight). + + + + + + Type for reference to a BOARDING POSITION. + + + + + + + + + Type for identifier of a FLEXIBLE AREA (area that encompasses the stop location of a flexible service). + + + + + + Type for reference to a FLEXIBLE AREA. + + + + + + + + + Identifier of a monitoring point. May correspond to a SCHEDULED STOP POINT or represent a group of Stops other Timing Points (i.e. LOGICAL DISPLAY) + + + + + + Type for reference to a monitoring point (LOGICAL DISPLAY). + + + + + + + + + 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. Default is false (xml default added from SIRI 2.0) + + + + + + Type for identifier of a CONNECTION link + + + + + + Reference to a CONNECTION link + + + + + Type for reference to a CONNECTION link + + + + + + + + + MODEs of transport applicable to timetabled public transport. + + + + + + + + + + + + + + + MODEs of transport applicable to private and non-timetabled transport. + + + + + + + + + + + + + + Union of VEHICLE and continuous MODEs. + + + + + + + + + + + + + + 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 JOURNEY PATTERN Identfiers associated with a journey. + + + + + + + Elements describing the LINE, ROUTE and DIRECTION of a VEHICLE JOURNEYwhich are derived from the JOURNEY PATTERN associated with the 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. + + + + + Name of Joruney Pattern + + + + + A means of transportation such as bus, rail, etc. + + + + + Identifier of ROUTE that journey follows. + + + + + Name or Number by which the LINE is known to the public. (Unbounded since SIRI 2.0) + + + + + Reference to a GROUP OF LINEs to which journey belongs. SIRI 2.0 + + + + + Description of the DIRECTION. May correspond to a DESTINATION DISPLAY. (Unbounded since SIRI 2.0) + + + + + Alternative identifier of LINE that an external system may associate with journey. + + + + + + Reference to a BRANDING. +SIRI v2.1 + + + + + An arbitrary marketing classification. +SIRI v2.1 + + + + + + + + Elements for identifying a LINE and DIRECTION. + + + + + Reference to a LINE. + + + + + Reference to a LINE DIRECTION DIRECTION, typically outward or return. + + + + + + + Type for LINEand DIRECTION. + + + + + + Elements for a LINE and DIRECTION. + + + + + Line Reference. + + + + + Direction Reference. + + + + + + + Type for identifier of a LINE + + + + + + Reference to a LINE. + + + + + Type for reference to a LINE. + + + + + + + + Elements describing the LINEand DESTINATION of a journey. Values for these elements can be specified on an annual schedule and will be inherited, unless overriden, onto the production timetable and then onto the individul dated VEHICLE JOURNEYs of the timetable. Each real-time journey takes its values from the dated VEHICLE JOURNEY that it follows. The absence of a value on an entity at a given level indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity. + + + + + + Description of the destination stop (vehicle signage), if different from the that in timetable - the DESTINATION DISPLAY. Can be overwritten section by section by the entry in an individual CALL. + + + + + + + Name or Number by which the LINEis known to the public. + + + + + Identifier of a GROUP OF LINEs + + + + + + Reference to a GROUP OF LINEs + + + + + + + + + Type for 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. + + + + + + + + Identifier of a ROUTE LINk. + + + + + + Reference to a ROUTE LINk. + + + + + + + + + Type for identifier of a DESTINATION. + + + + + + Reference 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. + + + + + Reference to a TOPOGRAPHIC PLACE. + + + + + Names of place used to help identify the LINE. + + + + + Short name of TOPOGRAPHIC PLACE. Should only be included if the detail level was requested. + + + + + + + + Identifier of a VEHICLE. + + + + + + Reference to a VEHICLE. + + + + + + + + Reference to a VEHICLE. + + + + + Passenger load status of a VEHICLE - GTFS-R / TPEG Pts045 + + + + + TPEG Pts45_0, unknown + + + + + GTFS-R "EMPTY" + The vehicle is considered empty by most measures, and has few or no passengers onboard, but is still accepting passengers. + + + + + GTFS-R "MANY_SEATS_AVAILABLE" / TPEG Pts45_1, many seats available + The vehicle has a large percentage of seats available. What percentage of free seats out of the total seats available is to be considered large enough to fall into this category is determined at the discretion of the producer. + + + + + GTFS-R "FEW_SEATS_AVAILABLE" / TPEG Pts45_2, few seats available + The vehicle has a small percentage of seats available. What percentage of free seats out of the total seats available is to be considered small enough to fall into this category is determined at the discretion of the producer. + + + + + GTFS-R "STANDING_ROOM_ONLY" / TPEG Pts45_4, standing room only (and TPEG Pts45_3, no seats available) + The vehicle can currently accommodate only standing passengers. + + + + + GTFS-R "CRUSHED_STANDING_ROOM_ONLY" + The vehicle can currently accommodate only standing passengers and has limited space for them. + + + + + GTFS-R "FULL" / TPEG Pts45_5, full + + + + + GTFS-R "NOT_ACCEPTING_PASSENGERS" + The vehicle cannot accept passengers. + + + + + TPEG Pts45_255, undefined occupancy + + + + + (SIRI 2.1) deprecated - use a more specific value + + + + + (SIRI 2.1) deprecated - use a more specific value + + + + + + + Identifier of a DRIVER + + + + + + Reference to a DRIVER. + + + + + + + + + DataType for a NOTICe. + + + + + + + + Text annotation that applies to an element. + + + + + + + + Type for identifier of an Info Channel. + + + + + + Type for reference to an Info Channel. + + + + + + + + + Type for identifier of a BRANDING. +SIRI v2.1 + + + + + + Type for reference to a BRANDING. +SIRI v2.1 + + + + + + + + An arbitrary marketing classification. +SIRI v2.1 + + + + + Identity of BRANDING. + + + + + + + + + Identifier of a SITE + + + + + + Reference to a SITE + + + + + + + + Reference to a SITE + + +       diff --git a/xsd/siri_model/siri_situation.xsd b/xsd/siri_model/siri_situation.xsd index 7a76558f..5ac25271 100644 --- a/xsd/siri_model/siri_situation.xsd +++ b/xsd/siri_model/siri_situation.xsd @@ -1,1535 +1,1535 @@ - - - - - - - - - - - - - - - - - - - - - main schema - e-service developers - Waldemar Isajkin (INIT GmbH) - 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 - - - - 2012-03-23 - - - - 2013-02-11 - - - - 2013-10-01 - - - - 2014-06-20 - - - - 2019-09-01 - - - -

      SIRI-SX 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.siri.org.uk/schema/2.0/xsd/}siri_model/siri_situation.xsd - [ISO 639-2/B] ENG - CEN - - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_stop.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modes.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_monitoredVehicleJourney.xsd - - - Kizoom 2000-2005, CEN 2009-2021 - - -
        -
      • Schema Derived from the Kizoom XTIS schema
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI-SX Xml Schema for PT SITUATIONs. Common element subschema - Standard -       -       - SIRI-SX Situation Model. -       - - - - 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. - - - - - Elements identifying a SITUATION element or an update to a SITUATION. Participant reference 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 describing 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 describing 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. - - - - - 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. - - - - - Datex 2 comments for public use. - - - - - Ccomments not for public use. - - - - - Datex 2 model of where event ois taking place on the road. - - - - - - - Datex2 Tarffic element. - - - - - - - - - - Type for Raod scope for scope of SITUATION or effect. - - - - - AFfected Road as described by a Date2x location. - - - - - Optional spatial projection of road. Can be used to distriute the path of the road to systems that do not already hold it. To pass just a Reference, use Datex2 location. - - - - - - - - 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, i.e. 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. - - - - - Reference to an Agent, i.e. Capture client user who input a 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. Default is reliable - - - - - Whether SITUATION is real or a test. - - - - - Likellihoo of a future sutuation happening. - - - - - Publishing status one of a specified set of substates to which a SITUATION can be assigned. - - - - - - - Values for Entry Status. - - - - - - - - - - - - - - Type for Publication status. - - - - - - - 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 using TPEG Pts038 AlertCause. - - - - - - - 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. - - - - - Additional reasons - - - - - - Reason - - - - - - - - - - - - - - - Structured Reason elements. The TpegReason and/or PublicEventReason enumerated values can be used to generate standardized messages describing the SITUATION. If no enumerated values are given, ReasonName is used instead. -Note: this means that ReasonName is NOT a complete message, but only a (few) word(s) to be included in the message! - - - - - Structured classification of nature of SITUATION, from which a standardized message can be generated. - - - - - DEPRECATED (SIRI 2.1) - use only TpegReasonGroup and PublicEventReason. - - - - - Structured classification of Public Event, from which a standardized message can be generated. - - - - - Textual classification of nature of SITUATION, from which a standardized message can be generated. Not normally needed, except when TpegReason and PublicEventReason are absent. (Unbounded since SIRI 2.0) - - - - - - - Values for Sensitivity. - - - - - - - - - - - - Values for Audience. - - - - - - - - - - - - - - - Type for Quality of data indication. - - - - - - - - - - Values for ScopeType - TPEG Pts36, AlertForType with additional values - - - - - TPEG Pts36_0, unknown - - - - - TPEG Pts36_1, stop place - - - - - TPEG Pts36_2, line - - - - - TPEG Pts36_3, route - - - - - TPEG Pts36_4, individual PT service - - - - - TPEG Pts36_5, operator - - - - - TPEG Pts36_6, city - - - - - TPEG Pts36_7, area - - - - - TPEG Pts36_8, stop point - - - - - stop place component - - - - - place - - - - - network - - - - - vehicle journey - - - - - dated vehicle journey - - - - - connection link - - - - - interchange - - - - - TPEG Pts36_0, unknown - - - - - general - - - - - road - - - - - TPEG Pts36_255, undefined - - - - - - - - Type for Location model for scope of SITUATION or effect. - - - - - Affected overall Geographic scope. - - - - - 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. - - - - - - Networks and Route(s) affected by SITUATION. - - - - - - - - - - - - - STOP POINTs affected by SITUATION. - - - - - - STOP POINT affected by SITUATION. - - - - - - - - Places other than STOP POINTs affected by SITUATION. - - - - - - STOP PLACE affected by SITUATION. - - - - - - - - Places other than STOP POINTs affected by SITUATION. - - - - - - Place affected by SITUATION. - - - - - - - - Specific journeys affected by SITUATION. - - - - - - Journeys affected by the SITUATION. - - - - - - - - Specific vehicles affected by SITUATION. (+SIRI v2.0) - - - - - - Vehicles affected by the SITUATION. (+SIRi v2.0) - - - - - - - - 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. (Unbounded since SIRI 2.0) - - - - - Description of SITUATION. Should not repeat any strap line included in Summary. (Unbounded since SIRI 2.0) - - - - - Additional descriptive details about the SITUATION (Unbounded since SIRI 2.0). - - - - - Further advice to passengers. (Unbounded since SIRI 2.0) - - - - - For internal information only, not passenger relevant - - - - - 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. Default is 'true'. - - - - - - - - Values for image content. - - - - - - - - - - - - Type for a general hyperlink. - - - - - URI for link. - - - - - Label for Link. (Unbounded since SIRI 2.0) - - - - - 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. - - - - - Condition(s) of effect of disruptione. - - - - - 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. - - - - - - - - Structured elements of a SITUATION condition. The Condition enumerated value(s) can be used to generate standardized messages describing the SITUATION. If no enumerated values are given, ConditionName is used instead. -Note: this means that ConditionName is NOT a complete message, but only a (few) word(s) to be included in the message! - - - - - Structured classification(s) of effect on service, from which a standardized message can be generated. - - - - - Textual classification of effect on service, from which a standardized message can be generated. Not normally needed, except when Condition is absent. - - - - - - - Type for boarding restrictions. - - - - - Type of boarding and alighting allowed at stop. Default is 'Alighting'. - - - - - Type of alighting allowed at stop. Default is 'Boarding'. - - - - - - - Type for (structured) advice. The AdviceType enumerated value can be used to generate standardized messages describing the SITUATION. If no enumerated value is given, AdviceName is used instead. -Note: this means that AdviceName is NOT a complete message, but only a (few) word(s) to be included in the message! -Alternatively, AdviceRef can be used to reference a (complete) standardised advisory message. - - - - - - Reference to a standard advisory NOTICE to be given to passengers if a particular condition arises. - - - - - Structured classification of advice for passengers in the given SITUATION, from which a standardized message can be generated. - - - - - Textual classification of advice, from which a standardized message can be generated. Not normally needed, except when AdviceType is absent. - - - - - Further textual advice to passengers. (Unbounded since SIRI 2.0) - - - - - - - Values for TPEG Pts039 - AdviceType, with some additional values - - - - - TPEG Pts39_0, unknown - - - - - TPEG Pts39_1, use replacement bus - - - - - TPEG Pts39_2, use replacement train - - - - - TPEG Pts39_3, use the alternative route - - - - - TPEG Pts39_4, go on foot - - - - - TPEG Pts39_5, please leave the station! Danger! - - - - - TPEG Pts39_6, no means of travel - - - - - TPEG Pts39_7, use different stops - - - - - TPEG Pts39_8, use alternative stop - - - - - TPEG Pts39_9, do not leave vehicle! Danger! - - - - - TPEG Pts39_10, take advice from announcements - - - - - TPEG Pts39_11, take advice from personnel - - - - - TPEG Pts39_12, obey advice from police - - - - - use other PT services - - - - - use interchange - - - - - no advice - - - - - TPEG Pts39_255, undefined advice - - - - - - - - Type for blocking. - - - - - Whether information about parts of the network identified by Affects should be blocked from computation made by a Journey Planner that has a real-tiem feed of the SITUATIONs. Default is 'false'; do not suppress. - - - - - Whether information about parts of the network identified by 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. (Unbounded since SIRI 2.0) - - - - - Refernce to a fare exceptions code that is allowed because of the disruption. An easement may relax a fare condition, for exampel "You may use your metro ticket on the bus', or 'You may use your bus ticket in teh metro between these two stops'. - - - - - - - - Type for allowed values of DelayBand. Based on Datex2, with some additional values. - - - - - - - - - - - - - - - - - - - Type for easement info. - - - - - Time band into which delay will fall. - - - - - Category of delay. - - - - - Additional journey time needed to overcome disruption. - - - - - - + + + + + + + + + + + + + + + + + + + + + main schema + e-service developers + Waldemar Isajkin (INIT GmbH) + 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 + + + + 2012-03-23 + + + + 2013-02-11 + + + + 2013-10-01 + + + + 2014-06-20 + + + + 2019-09-01 + + + +

      SIRI-SX 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.siri.org.uk/schema/2.0/xsd/}siri_model/siri_situation.xsd + [ISO 639-2/B] ENG + CEN + + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_stop.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modes.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_monitoredVehicleJourney.xsd + + + Kizoom 2000-2005, CEN 2009-2021 + + +
        +
      • Schema Derived from the Kizoom XTIS schema
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI-SX Xml Schema for PT SITUATIONs. Common element subschema + Standard +       +       + SIRI-SX Situation Model. +       + + + + 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. + + + + + Elements identifying a SITUATION element or an update to a SITUATION. Participant reference 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 describing 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 describing 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. + + + + + 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. + + + + + Datex 2 comments for public use. + + + + + Ccomments not for public use. + + + + + Datex 2 model of where event ois taking place on the road. + + + + + + + Datex2 Tarffic element. + + + + + + + + + + Type for Raod scope for scope of SITUATION or effect. + + + + + AFfected Road as described by a Date2x location. + + + + + Optional spatial projection of road. Can be used to distriute the path of the road to systems that do not already hold it. To pass just a Reference, use Datex2 location. + + + + + + + + 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, i.e. 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. + + + + + Reference to an Agent, i.e. Capture client user who input a 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. Default is reliable + + + + + Whether SITUATION is real or a test. + + + + + Likellihoo of a future sutuation happening. + + + + + Publishing status one of a specified set of substates to which a SITUATION can be assigned. + + + + + + + Values for Entry Status. + + + + + + + + + + + + + + Type for Publication status. + + + + + + + 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 using TPEG Pts038 AlertCause. + + + + + + + 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. + + + + + Additional reasons + + + + + + Reason + + + + + + + + + + + + + + + Structured Reason elements. The TpegReason and/or PublicEventReason enumerated values can be used to generate standardized messages describing the SITUATION. If no enumerated values are given, ReasonName is used instead. +Note: this means that ReasonName is NOT a complete message, but only a (few) word(s) to be included in the message! + + + + + Structured classification of nature of SITUATION, from which a standardized message can be generated. + + + + + DEPRECATED (SIRI 2.1) - use only TpegReasonGroup and PublicEventReason. + + + + + Structured classification of Public Event, from which a standardized message can be generated. + + + + + Textual classification of nature of SITUATION, from which a standardized message can be generated. Not normally needed, except when TpegReason and PublicEventReason are absent. (Unbounded since SIRI 2.0) + + + + + + + Values for Sensitivity. + + + + + + + + + + + + Values for Audience. + + + + + + + + + + + + + + + Type for Quality of data indication. + + + + + + + + + + Values for ScopeType - TPEG Pts36, AlertForType with additional values + + + + + TPEG Pts36_0, unknown + + + + + TPEG Pts36_1, stop place + + + + + TPEG Pts36_2, line + + + + + TPEG Pts36_3, route + + + + + TPEG Pts36_4, individual PT service + + + + + TPEG Pts36_5, operator + + + + + TPEG Pts36_6, city + + + + + TPEG Pts36_7, area + + + + + TPEG Pts36_8, stop point + + + + + stop place component + + + + + place + + + + + network + + + + + vehicle journey + + + + + dated vehicle journey + + + + + connection link + + + + + interchange + + + + + TPEG Pts36_0, unknown + + + + + general + + + + + road + + + + + TPEG Pts36_255, undefined + + + + + + + + Type for Location model for scope of SITUATION or effect. + + + + + Affected overall Geographic scope. + + + + + 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. + + + + + + Networks and Route(s) affected by SITUATION. + + + + + + + + + + + + + STOP POINTs affected by SITUATION. + + + + + + STOP POINT affected by SITUATION. + + + + + + + + Places other than STOP POINTs affected by SITUATION. + + + + + + STOP PLACE affected by SITUATION. + + + + + + + + Places other than STOP POINTs affected by SITUATION. + + + + + + Place affected by SITUATION. + + + + + + + + Specific journeys affected by SITUATION. + + + + + + Journeys affected by the SITUATION. + + + + + + + + Specific vehicles affected by SITUATION. (+SIRI v2.0) + + + + + + Vehicles affected by the SITUATION. (+SIRi v2.0) + + + + + + + + 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. (Unbounded since SIRI 2.0) + + + + + Description of SITUATION. Should not repeat any strap line included in Summary. (Unbounded since SIRI 2.0) + + + + + Additional descriptive details about the SITUATION (Unbounded since SIRI 2.0). + + + + + Further advice to passengers. (Unbounded since SIRI 2.0) + + + + + For internal information only, not passenger relevant + + + + + 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. Default is 'true'. + + + + + + + + Values for image content. + + + + + + + + + + + + Type for a general hyperlink. + + + + + URI for link. + + + + + Label for Link. (Unbounded since SIRI 2.0) + + + + + 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. + + + + + Condition(s) of effect of disruptione. + + + + + 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. + + + + + + + + Structured elements of a SITUATION condition. The Condition enumerated value(s) can be used to generate standardized messages describing the SITUATION. If no enumerated values are given, ConditionName is used instead. +Note: this means that ConditionName is NOT a complete message, but only a (few) word(s) to be included in the message! + + + + + Structured classification(s) of effect on service, from which a standardized message can be generated. + + + + + Textual classification of effect on service, from which a standardized message can be generated. Not normally needed, except when Condition is absent. + + + + + + + Type for boarding restrictions. + + + + + Type of boarding and alighting allowed at stop. Default is 'Alighting'. + + + + + Type of alighting allowed at stop. Default is 'Boarding'. + + + + + + + Type for (structured) advice. The AdviceType enumerated value can be used to generate standardized messages describing the SITUATION. If no enumerated value is given, AdviceName is used instead. +Note: this means that AdviceName is NOT a complete message, but only a (few) word(s) to be included in the message! +Alternatively, AdviceRef can be used to reference a (complete) standardised advisory message. + + + + + + Reference to a standard advisory NOTICE to be given to passengers if a particular condition arises. + + + + + Structured classification of advice for passengers in the given SITUATION, from which a standardized message can be generated. + + + + + Textual classification of advice, from which a standardized message can be generated. Not normally needed, except when AdviceType is absent. + + + + + Further textual advice to passengers. (Unbounded since SIRI 2.0) + + + + + + + Values for TPEG Pts039 - AdviceType, with some additional values + + + + + TPEG Pts39_0, unknown + + + + + TPEG Pts39_1, use replacement bus + + + + + TPEG Pts39_2, use replacement train + + + + + TPEG Pts39_3, use the alternative route + + + + + TPEG Pts39_4, go on foot + + + + + TPEG Pts39_5, please leave the station! Danger! + + + + + TPEG Pts39_6, no means of travel + + + + + TPEG Pts39_7, use different stops + + + + + TPEG Pts39_8, use alternative stop + + + + + TPEG Pts39_9, do not leave vehicle! Danger! + + + + + TPEG Pts39_10, take advice from announcements + + + + + TPEG Pts39_11, take advice from personnel + + + + + TPEG Pts39_12, obey advice from police + + + + + use other PT services + + + + + use interchange + + + + + no advice + + + + + TPEG Pts39_255, undefined advice + + + + + + + + Type for blocking. + + + + + Whether information about parts of the network identified by Affects should be blocked from computation made by a Journey Planner that has a real-tiem feed of the SITUATIONs. Default is 'false'; do not suppress. + + + + + Whether information about parts of the network identified by 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. (Unbounded since SIRI 2.0) + + + + + Refernce to a fare exceptions code that is allowed because of the disruption. An easement may relax a fare condition, for exampel "You may use your metro ticket on the bus', or 'You may use your bus ticket in teh metro between these two stops'. + + + + + + + + Type for allowed values of DelayBand. Based on Datex2, with some additional values. + + + + + + + + + + + + + + + + + + + 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/xsd/siri_model/siri_situationActions.xsd b/xsd/siri_model/siri_situationActions.xsd index 85e6122e..bf3a641a 100644 --- a/xsd/siri_model/siri_situationActions.xsd +++ b/xsd/siri_model/siri_situationActions.xsd @@ -1,750 +1,750 @@ - - - - - - - - - - - - - main schema - e-service developers - Add names - Europe - >Drafted for version 1.0 Kizoom SITUATION Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk - - 2006-09-29 - - - 2007-04-17 - - - 2013-10-01 - - - - 2013-05-01 - - - -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/schema/2.0/xsd/siri_model}/siri_situationActions.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd - - - Kizoom 2000-2007, CEN 2009-2021 - - -
        -
      • Schema derived Derived from the Kizoom XTIS schema
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI-SX XML Schema for PT SITUATIONs. Actions subschema - Standard -       -       - SIRI-SX Situation Actions. -       - - - - - Type for list of actions. - - - - - - Description of the whole action to be published. >SIRI 2.0 - - - - - Extension point. - - - - - - - - Type for list of SITUATIONs. - - - - - Processing Status of action at time of SITUATION publication. - - - - - - - - Type for parameterised, i.e. user definable, actions. - - - - - - - Description of action. - - - - - Data associated with action. - - - - - Defines a number of validity periods. When not sent, then the validity periods of higher level are valid. Can be overwritten by deeper level. - - - - - - - - - Type for publication action. - - - - - - - Whether reminders should be sent. - - - - - - Intervals before validity start date to send reminders. - - - - - - - - Whether a clearing notice should be displayed. - - - - - - - - - Values for Progress Status. - - - - - - - - - - Type for list of SITUATIONs. - - - - - Name of action data Element. - - - - - Data type of action data. - - - - - Value for action. - - - - - Display prompt for presenting action to user. (Unbounded since SIRI 2.0) - - - - - Defines the information area where the action has to be published. - - - - - - - - - - - - - - Allowed actions to perform to distribute SITUATION. - - - - - - - - - - - - - - - - - Action: Publish SITUATION To Web. - - - - - Type for Action Publish SITUATION To Web. - - - - - - - Include in SITUATION lists on web site. Default is 'true'. - - - - - Include on home page on web site. Default is 'false'. - - - - - Include in moving ticker band. Default is 'false'. - - - - - Include in social NETWORK indicated by this name. Possible value could be "twitter.com", "facebook.com", "vk.com" and so on. Parameters may be specifed as Action data. (SIRIv 2.10) - - - - - - - - - Action: Publish SITUATION To WAP and PDA. - - - - - Type for Action Publish SITUATION To Displays. - - - - - - - Include in SITUATION lists on mobile site. Default is 'true'. - - - - - Include in home page on mobile site. Default is 'false'. - - - - - - - - - Action: Publish SITUATION To Displays. - - - - - Type for Action Publish SITUATION To Web. - - - - - - - Include in SITUATION lists on station displays. - - - - - Include onboard displays. - - - - - - - - - Action: Publish SITUATION To Alert Service. - - - - - Type for Action Publish SITUATION To Alert Service. - - - - - - - Send as email alert. - - - - - Send as mobile alert by SMS or WAP push. - - - - - - - - - Action: Publish SITUATION To TvService. - - - - - Type for Notify SITUATION to Tv. - - - - - - - Publish to Ceefax. Default is 'true'. - - - - - Publish to Teletext. Default is 'true'. - - - - - - - - - - Action: Publish SITUATION Manually. i.e. a procedure must be carried out. - - - - - - - - - - Type for Action Publish SITUATION Manual process. - - - - - - - - Action: Publish SITUATION to an individual by SMS. - - - - - Type for Notify user by SMS. - - - - - - - MSISDN of user to which to send messages. - - - - - Whether content is flagged as subject to premium charge. - - - - - - - - - Action: Publish SITUATION to a named workgroup or individual by email. - - - - - Type for Notify user by Email. - - - - - - - Email address to which notice should be sent. - - - - - - - - - Action: Publish SITUATION To pager. - - - - - Type for Notify user by Pager. - - - - - - - Reference to a pager group to be notfied. - - - - - Pager number of pager to be notfied. - - - - - - - - - Action: Publish SITUATION To User. - - - - - Type for Notify user by other means. - - - - - - - Workgroup of user to be notified. - - - - - Name of user to be notified. - - - - - Reference to a user to be notified. - - - - - - - - - - - - Description of SITUATION. Should not repeat any strap line included in Summary. - - - - - Prioritises a description from the information owner's point of view, e.g. usable for sorting or hiding individual descriptions. -1 = highest priority. - - - - - - - - - Further consequence to passengers. - - - - - Prioritises a consequence from the information owner's point of view, e.g. usable for sorting or hiding individual consequences. -1 = highest priority. - - - - - - - - - Further information about the duration to passengers. - - - - - - - - - - - - Reference to the action number within the incident concept. - - - - - The time of the last update - - - - - The monotonically inscresing version of the passenger information instance. If absent, is the same version as the enclosing Situation - - - - - The system which created this passenger information. If absent, is the same version as the enclosing Situation - - - - - The organisation which owns this passenger information. - - - - - Perspective of the passenger, e.g. general, vehicleJourney, stopPoint. - - - - - Prioritises a passenger information action from the information owner's point of view, e.g. suitable for sorting or hiding individual passenger information actions. -1 = highest priority. - - - - - All texts of the passenger information. - - - - - - - - - Type for description of the whole action to be published (extends SIRI-SX v2.0p). - - - - - Defines the information area where the action has to be published. - - - - - - - - - - - Description of the whole passenger information of one action. - - - - - - - - - Reason of passenger information action. - - - - - - - - - Further recommendation to passengers. - - - - - Prioritises a recommendation from the information owner's point of view, e.g. usable for sorting or hiding individual recommendations. -1 = highest priority. - - - - - - - - - Further remark to passengers, e,g, "For more information call xy". - - - - - Prioritises a remark from the information owner's point of view, e.g. usable for sorting or hiding individual remarks. -1 = highest priority. - - - - - - - - - Summary of passenger information action. - - - - - - - - - Class of size, e.g. L (large), M (medium), S (small) - - - - - - Content for summary of a passenger information action - - - - - Content for reason of a passenger information action - - - - - Content for n descriptions of a passenger information action. For hiding / sorting descriptions in end devices, a description priority can be set. - - - - - Content for n consequences of a passenger information action. For hiding / sorting descriptions in end devices, a consequence priority can be set. - - - - - Content for n recommendations of a passenger information action. For hiding / sorting descriptions in end devices, a recommendation priority can be set. - - - - - Content for the duration of a passenger information action. - - - - - Content for n remarks of a passenger information action, e,g, "For more information call xy". For hiding / sorting descriptions in end devices, a remark priority can be set. - - - - - Hyperlinks to other resources associated with SITUATION. - - - - - Any images associated with SITUATION. - - - - - for internal information only, not passenger relevant - - - - - - - Values for perspectives. - - - - - - - + + + + + + + + + + + + + main schema + e-service developers + Add names + Europe + >Drafted for version 1.0 Kizoom SITUATION Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk + + 2006-09-29 + + + 2007-04-17 + + + 2013-10-01 + + + + 2013-05-01 + + + +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/schema/2.0/xsd/siri_model}/siri_situationActions.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd + + + Kizoom 2000-2007, CEN 2009-2021 + + +
        +
      • Schema derived Derived from the Kizoom XTIS schema
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI-SX XML Schema for PT SITUATIONs. Actions subschema + Standard +       +       + SIRI-SX Situation Actions. +       + + + + + Type for list of actions. + + + + + + Description of the whole action to be published. >SIRI 2.0 + + + + + Extension point. + + + + + + + + Type for list of SITUATIONs. + + + + + Processing Status of action at time of SITUATION publication. + + + + + + + + Type for parameterised, i.e. user definable, actions. + + + + + + + Description of action. + + + + + Data associated with action. + + + + + Defines a number of validity periods. When not sent, then the validity periods of higher level are valid. Can be overwritten by deeper level. + + + + + + + + + Type for publication action. + + + + + + + Whether reminders should be sent. + + + + + + Intervals before validity start date to send reminders. + + + + + + + + Whether a clearing notice should be displayed. + + + + + + + + + Values for Progress Status. + + + + + + + + + + Type for list of SITUATIONs. + + + + + Name of action data Element. + + + + + Data type of action data. + + + + + Value for action. + + + + + Display prompt for presenting action to user. (Unbounded since SIRI 2.0) + + + + + Defines the information area where the action has to be published. + + + + + + + + + + + + + + Allowed actions to perform to distribute SITUATION. + + + + + + + + + + + + + + + + + Action: Publish SITUATION To Web. + + + + + Type for Action Publish SITUATION To Web. + + + + + + + Include in SITUATION lists on web site. Default is 'true'. + + + + + Include on home page on web site. Default is 'false'. + + + + + Include in moving ticker band. Default is 'false'. + + + + + Include in social NETWORK indicated by this name. Possible value could be "twitter.com", "facebook.com", "vk.com" and so on. Parameters may be specifed as Action data. (SIRIv 2.10) + + + + + + + + + Action: Publish SITUATION To WAP and PDA. + + + + + Type for Action Publish SITUATION To Displays. + + + + + + + Include in SITUATION lists on mobile site. Default is 'true'. + + + + + Include in home page on mobile site. Default is 'false'. + + + + + + + + + Action: Publish SITUATION To Displays. + + + + + Type for Action Publish SITUATION To Web. + + + + + + + Include in SITUATION lists on station displays. + + + + + Include onboard displays. + + + + + + + + + Action: Publish SITUATION To Alert Service. + + + + + Type for Action Publish SITUATION To Alert Service. + + + + + + + Send as email alert. + + + + + Send as mobile alert by SMS or WAP push. + + + + + + + + + Action: Publish SITUATION To TvService. + + + + + Type for Notify SITUATION to Tv. + + + + + + + Publish to Ceefax. Default is 'true'. + + + + + Publish to Teletext. Default is 'true'. + + + + + + + + + + Action: Publish SITUATION Manually. i.e. a procedure must be carried out. + + + + + + + + + + Type for Action Publish SITUATION Manual process. + + + + + + + + Action: Publish SITUATION to an individual by SMS. + + + + + Type for Notify user by SMS. + + + + + + + MSISDN of user to which to send messages. + + + + + Whether content is flagged as subject to premium charge. + + + + + + + + + Action: Publish SITUATION to a named workgroup or individual by email. + + + + + Type for Notify user by Email. + + + + + + + Email address to which notice should be sent. + + + + + + + + + Action: Publish SITUATION To pager. + + + + + Type for Notify user by Pager. + + + + + + + Reference to a pager group to be notfied. + + + + + Pager number of pager to be notfied. + + + + + + + + + Action: Publish SITUATION To User. + + + + + Type for Notify user by other means. + + + + + + + Workgroup of user to be notified. + + + + + Name of user to be notified. + + + + + Reference to a user to be notified. + + + + + + + + + + + + Description of SITUATION. Should not repeat any strap line included in Summary. + + + + + Prioritises a description from the information owner's point of view, e.g. usable for sorting or hiding individual descriptions. +1 = highest priority. + + + + + + + + + Further consequence to passengers. + + + + + Prioritises a consequence from the information owner's point of view, e.g. usable for sorting or hiding individual consequences. +1 = highest priority. + + + + + + + + + Further information about the duration to passengers. + + + + + + + + + + + + Reference to the action number within the incident concept. + + + + + The time of the last update + + + + + The monotonically inscresing version of the passenger information instance. If absent, is the same version as the enclosing Situation + + + + + The system which created this passenger information. If absent, is the same version as the enclosing Situation + + + + + The organisation which owns this passenger information. + + + + + Perspective of the passenger, e.g. general, vehicleJourney, stopPoint. + + + + + Prioritises a passenger information action from the information owner's point of view, e.g. suitable for sorting or hiding individual passenger information actions. +1 = highest priority. + + + + + All texts of the passenger information. + + + + + + + + + Type for description of the whole action to be published (extends SIRI-SX v2.0p). + + + + + Defines the information area where the action has to be published. + + + + + + + + + + + Description of the whole passenger information of one action. + + + + + + + + + Reason of passenger information action. + + + + + + + + + Further recommendation to passengers. + + + + + Prioritises a recommendation from the information owner's point of view, e.g. usable for sorting or hiding individual recommendations. +1 = highest priority. + + + + + + + + + Further remark to passengers, e,g, "For more information call xy". + + + + + Prioritises a remark from the information owner's point of view, e.g. usable for sorting or hiding individual remarks. +1 = highest priority. + + + + + + + + + Summary of passenger information action. + + + + + + + + + Class of size, e.g. L (large), M (medium), S (small) + + + + + + Content for summary of a passenger information action + + + + + Content for reason of a passenger information action + + + + + Content for n descriptions of a passenger information action. For hiding / sorting descriptions in end devices, a description priority can be set. + + + + + Content for n consequences of a passenger information action. For hiding / sorting descriptions in end devices, a consequence priority can be set. + + + + + Content for n recommendations of a passenger information action. For hiding / sorting descriptions in end devices, a recommendation priority can be set. + + + + + Content for the duration of a passenger information action. + + + + + Content for n remarks of a passenger information action, e,g, "For more information call xy". For hiding / sorting descriptions in end devices, a remark priority can be set. + + + + + Hyperlinks to other resources associated with SITUATION. + + + + + Any images associated with SITUATION. + + + + + for internal information only, not passenger relevant + + + + + + + Values for perspectives. + + + + + + +       \ No newline at end of file diff --git a/xsd/siri_model/siri_situationAffects.xsd b/xsd/siri_model/siri_situationAffects.xsd index b4f6f5de..c6e34943 100644 --- a/xsd/siri_model/siri_situationAffects.xsd +++ b/xsd/siri_model/siri_situationAffects.xsd @@ -1,1533 +1,1533 @@ - - - - - - - - - - - - - - - - - - - - - main schema - e-service developers - Waldemar Isajkin (INIT GmbH) - 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 - - - - 2013-10-10 - - - 2014-06-20 - - - 2018-06-13 - - - 2018-11-08 - - - 2019-05-07 - - - 2020-01-29 - - - -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/}siri_model/siri_situationAffects.xsd - [ISO 639-2/B] ENG - CEN - - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_situationServiceTypes.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modes.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd - - - Kizoom 2000-2007, CEN 2009-2021 - - -
        -
      • Schema derived Derived from the Kizoom XTIS schema
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI-SX Xml Schema for PT Incidents. Common affects element subschema - Standard -       -       - SIRI-SX Situation Scope. -       - - - - Type for an SCHEDULED STOP POINT affected by a SITUATION. - - - - - - Alternative private code of stop. - - - - - Name of SCHEDULED STOP POINT. (Unbounded since SIRI 2.0) - - - - - Type of stop type. Normally implicit in VEHICLE mode. TPEG table pti 17_4 - - - - - Spatial coordinates of STOP POINT. Derivable from StopRef. - - - - - Reference of Stop Place related to this affected StopPoint. - - - - - Name of Stop Place related to this affected StopPoint. (Unbounded to allow a text for every language) - - - - - Modes within station/stop affected by the SITUATION. If not specified, assume all modes of that station. - - - - - Reference to a SITE or TOPOGRAPHIC PLACE affected by the Locality of stop (In UK NPtg Locality Code). Derivable from StopRef. - - - - - Name of locality in which stop is found. Derivable from LocalityRef. (Unbounded since SIRI 2.0) - - - - - Assessment of current ACCESSIBILITY of the STOP POINT as affected by the SITUATION. - - - - - Status of STOP - - - - - CONNECTION links from stop. - - - - - - CONNECTION LINKs from stop that are affected by the SITUATION. - - - - - - - - Used to restrict stop points to some lines - - - - - - - - - - - - - Type for TRANSPORT MODEs affecetd by a SITUATION. - - - - - All known modes for stop. - - - - - Mode affected by SITUATION. - - - - - - - - - - - Type for identifier of a ZONe. - - - - - - Type for a reference to a ZONE or locality. - - - - - - - - - - Type for a reference Information about a CONNECTION link from a given stop that is affected by a SITUATION. - - - - - Reference to a CONNECTION link affected by a SITUATION. - - - - - Name of CONNECTION link affected by a SITUATION. - - - - - - - - - Reference to other connecting STOP POINT of a CONNECTION link. 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 link. Derivable from StopRef. (Unbounded since SIRI 2.0) - - - - - Zone in which connecting stop lies. - - - - - - - Direction of SERVICE JOURNEY INTERCHANGE. Default is 'both'. - - - - - PATH LINKs affected by a SITUATION. - - - - - - - - Values for DIRECTION of CONNECTION link or SERVCIE JOURNEY INTERCHANGE. - - - - - - - - - - - Information about a CONNECTION link from a given stop affected by a SITUATION. - - - - - Identifier of CONNECTION link. - - - - - Description of Link. (Unbounded since SIRI 2.0) - - - - - Nature of CONNECTION link. - - - - - Description of a DIRECTION of CONNECTION link. - - - - - 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 SERVICE JOURNEY INTERCHANGE at CONNECTION link from a given SCHEDULED STOP POINT. - - - - - Reference to a SERVICE JOURNEY INTERCHANGE affected by a SITUATION. - - - - - 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. (Unbounded since SIRI 2.0) - - - - - Reference to connecting VEHICLE JOURNEY affected by a SITUATION. - - - - - - Reference to a CONNECTION Link affected by a SITUATION. - - - - - - - - - Type for identifier of an OPERATOR Code. - - - - - - Type for reference to an OPERATOR. - - - - - - - - Type for identifier of an OPERATOR Code. - - - - - - Type for reference to an Operatorational Unit Code. - - - - - - - - Type for Annotated reference to an OPERATOR affected by a SITUATION. - - - - - Reference to an OPERATOR. - - - - - Public Name of OPERATOR. Can be derived from OperatorRef. (Unbounded since SIRI 2.0) - - - - - Short Name for OPERATOR. Can be derived from OperatorRef. (Unbounded since SIRI 2.0) - - - - - OPERATIONAL UNIT responsible for managing services. - - - - - - - - Type for Annotated reference to a NETWORK affected by a SITUATION. - - - - - Reference to a NETWORK. - - - - - Name of NETWORK. Can be derived from NetworkRef. (Unbounded since SIRI 2.0) - - - - - - - - - Type for ideifier of a Route section. - - - - - - Type for reference to a Section. - - - - - - - - Line to which link connects. - - - - - - - - - - Type for identifier of an advisory NOTICE - - - - - - Type for reference to predefined advisory NOTICE. - - - - - - - - - - - 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 a 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 explicitly overridden, 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. (Unbounded since SIRI 2.0) - - - - - Textual description of overall routes affected. Should correspond to any structured description in the AffectedLines element. (Unbounded since SIRI 2.0) - - - - - - - All LINEs in the network are affected. - - - - - Only some ROUTEs are affected, LINE level information not available. See the RoutesAffected element for textual description. - - - - - Only some COMMON SECTIONs are affected, LINE level information not available. - - - - - - Information about the indvidual LINEs in the network that are affected. If not explicitly overridden, modes and submodes will be defaulted to any values present (i) in the AffectedNetwork (ii) In the general context. - - - - - - - - - - Information about the individual LINEs in the network that are affected by a SITUATION. If not explicitly overridden, modes and submodes will be defaulted to any values present (i) in the AffectedNetwork (ii) in the general context. - - - - - Restricts the affected scope to the specified operators of LINEs that are affected by the situation. Overrides any value specified for (i) Affected Network (ii) General Context. - - - - - - Restricts the affected scope to the specified ORIGINs - - - - - Restricts the affected scope to the specified DESTINATIONs - - - - - DIRECTIONs affected. - - - - - Restricts the affected scope to the specified ROUTEs - - - - - - Route affected by Situation. - - - - - - - - Restricts the affected scope to the specified LINE SECTIONs - - - - - - - - - - Used to restrict lines to some stop points - - - - - - - - - - Used to restrict lines to some stop places - - - - - - - - - - - - - Type for information about the SECTIONs affected by a SITUATION. - - - - - - Reference to a section of ROUTE affected by a SITUATION. - - - - - An indirect reference to a COMMON SECTION by stating the stop point ref of the first and last POINT IN JOURNEY PATTERN of the section in question. Intermediate POINTs should be added if necessary to distinguish different sections having the same start and end point and is a means to exclude sections not containing those stop points. - - - - - - - Used to indicate the SCHEDULED stop point at the start of the SECTION - - - - - Used to indicate that any SCHEDULED stop point with a stop assignment to the indicated StopPlace is to be considered as start of the SECTION - - - - - Used to indicate that any SCHEDULED stop point with a stop assignment to the indicated QUAY is to be considered as start of the SECTION - - - - - - - An intermediate Stop POINT of the SECTION that must be part of SECTION - - - - - Used to indicate that at least one SCHEDULED stop point with a stop assignment to the indicated StopPlace must be part of the SECTION - - - - - Used to indicate that at least one SCHEDULED stop point with a stop assignment to the indicated QUAY must be part of the SECTION - - - - - - - Used to indicate the SCHEDULED stop point at the end of the SECTION - - - - - Used to indicate that any SCHEDULED stop point with a stop assignment to the indicated StopPlace is to be considered as end of the SECTION - - - - - Used to indicate that any SCHEDULED stop point with a stop assignment to the indicated QUAY is to be considered as end of the SECTION - - - - - - - - - - Spatial projection of element that can be used to show affected area on a map. - - - - - - - - - An ordered list of MAPPING POINTs defining one single path through the road (or rail) Network. A ROUTE may pass through the same MAPPING POINT more than once. - - - - - Reference to a ROUTE affected by SITUATION. - - - - - DIRECTIONS affected by SITUATION. - - - - - Sections of ROUTE affected by SITUATION. - - - - - - Sections of ROUTE that is affected by SITUATION. - - - - - - - - Stop Poins of the ROUTE. Can be either all or only affected by SITUATION. - - - - - - Indicates whether the list of STOP POINTS contains all STOP POINTS of ROUTE or only affected by SITUATION. - - - - - - Stop Point of the ROUTE - - - - - GIs projection of Link to the next provided StopPoint. NB Line here means Geometry Polyline, not Transmodel Transport Line. - - - - - - - - - ROUTE LINKs affected by SITUATION. - - - - - - - - - - - - - - Type for information about a VEHICLE JOURNEY affected by a SITUATION. - - - - - Use of simple reference is deprecated - - - - Refercence to a VEHICLE JOURENY framed by the day. SIRI 2.0 - - - - - Reference to a service VEHICLE JOURNEY affected by a SITUATION. - - - - - - Reference to a specific DATED VEHICLE JOURNEY affected by a SITUATION. - - - - - Name of journey affected by a SITUATION. (Unbounded since SIRI 2.0) - - - - - OPERATOR of LINE affected by SITUATION. - - - - - Reference to the LINE of the journey affected by an SITUATION. - - - - - - DIRECTION of LINE in which journey runs. - - - - - BLOCK which journey runs. +SIRI 2.0 - - - - - TRAIN NUMBERs for journey. +SIRI v2.0 - - - - - - TRAIN NUMBER assigned to VEHICLE JOURNEY. +SIRI 2.0 - - - - - - - - JOURNEY PARTs making up JOURNEY +SIRIv2.0 e. - - - - - - Information about Parts of JOURNEY +SIRI v2.0 - - - - - - - - Origin SCHEDULED STOP POINTs from which the LINE runs. [equivalent to pti15 1 start_point route_description_type] - - - - - Restricts the affected scope to the specified DESTINATIONs - - - - - ROUTE affected by the SITUATION. - - - - - Timetabled departure tme of journey from Origin. - - - - - Timetabled arrival time of journey at Destination. - - - - - DESTINATION name shown for journey at the origin. Can be Used to identify joruney for user. (+SIRI 2.0), - - - - - DESTINATION name shown for journey at the origin. Can be Used to identify joruney for user. (+SIRI 2.0) - - - - - Accessibility Disruption status ofto JOURNEY, as affected by Situation. - - - - - enum Status of service for this Vehicle Journey - TPEG value. Multiple Conditions can be valid at the same time. (+SIRI 2.0) - - - - - CALLs making up VEHICLE JOURNEY [equivalent to TPEG pti15 3 stop, 15_5 not-stopping, 15-6 temporary stop route_description_type] - - - - - - - - - - Facilities available for VEHICLE JOURNEY (+SIRI 2.0) - - - - - - Facililitiy available for VEHICLE JOURNEY (+SIRI 2.0) - - - - - - - - - - - Type for information about a VEHICLE affected by an SITUATION. - - - - - Reference to a specific VEHICLE affected by an SITUATION. - - - - - Registration plate of VEHICLE - - - - - (Mobile) phone number on which the vehicle can be called - - - - - Internet protocol address of the VEHICLE in form 000.000.000.000 - - - - - Radio address of the VEHICLE - - - - - Reference to VEHICLE JOURNEY that VEHICLE is making. - - - - - Location where the VEHICLE was when the situation arosse - - - - - Current Location of the VEHICLE - - - - - Current Accessibility assessment of vehicle. - - - - - - If a VEHICLE JOURNEY is a coupled journey, i.e. comprises several coupled BLOCKparts, there will be a separate delivery for each BLOCKp art and this element will indicate the vehicles that the journey part uses. - - - - - - Whether the VEHICLE is in traffic congestion. If not, present, not known. - - - - - Whether the panic alarm on the VEHICLE is activated. Default is 'false'. - - - - - Whether this is a Headway Service, that is shown as operating at a prescribed interval rather than to a fixed timetable. Default is 'false'. - - - - - - - - Type for information about a CALL affected by an SITUATION. - - - - - - - Order of visit to stop within JORUNYE PATTERN of journey. - - - - - Status of CALL TPEG 13_6 - - - - - - - - - - - - - - - - - - - - - Elements describing the arrival of a VEHICLE at a SCHEDULED STOP POINT. - - - - - - - - - - - - Elements describing the departure of a VEHICLE from a SCHEDULED STOP POINT. - - - - - - - - - - - - Type for information about a FACILITY affected by an SITUATION. (+SIRI 2.0) - - - - - - Identifier of stop point at which availability first applies. - - - - - Identifier of stop point at which availability last applies. - - - - - Name of FACILITY. - - - - - Status of Facility - - - - - - - - - Type for annotated references to a TOPOGRAPHIC PLACE. - - - - - Reference to a SITE or TOPOGRAPHIC PLACE (Locality). - - - - - Alternative identifier of SITE or TOPOGRAPHIC PLACE - - - - - Name of SITE or TOPOGRAPHIC PLACE (locality) in which stop is found. (Unbounded since SIRI 2.0) - - - - - Spatial coordinates of STOP POINT. Derivable from StopRef. - - - - - Category of TOPGRAPHIC PLACE or SITE. - - - - - Reference to an EQUIPMENT found at location. - - - - - Changes to accessibility for SITE. - - - - - - - - - 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. (Unbounded since SIRI 2.0) - - - - - Type of Stop Place. - - - - - Facilities available for VEHICLE JOURNEY (+SIRI 2.0) - - - - - - Facililitiy available for VEHICLE JOURNEY (+SIRI 2.0) - - - - - - - - Quays affected by SITUATION. - - - - - - Quay affected by SITUATION. - - - - - - - - PathLinks affected by SITUATION. - - - - - - - - - - Used to restrict stop places to some lines - - - - - - - - - - - - - - - Type for information about the quays affected by an SITUATION. - - - - - - - Reference to a Stop Place. - - - - - Name of component. (Unbounded since SIRI 2.0) - - - - - Type of Component. - - - - - - Further qualifcation of affected part of Link projection, - - - - - Type of AccessFeature (+SIRI.20) - - - - - Facilities available for component (+SIRI 2.0) - - - - - - Facility available for VEHICLE JOURNEY (+SIRI 2.0) - - - - - - - - - - - - - Type for Information on casualties. - - - - - Number of fatalities. - - - - - Number of injured presons. - - - - - - - Values for STOP PLACE types - TPEG Pts041 and IFOPT - - - - - TPEG Pts41_0, unknown - - - - - TPEG Pts41_1, railway station - - - - - TPEG Pts41_2, underground station - - - - - IFOPT, TPEG Pts41_3, tram station - - - - - IFOPT, TPEG Pts41_4, bus station - - - - - IFOPT, TPEG Pts41_5, airport - - - - - TPEG Pts41_6, pier - - - - - IFOPT, TPEG Pts41_7, harbour port - - - - - ,IFOPT, TPEG Pts41_8, ferry stop - - - - - TPEG Pts41_9, light railway station - - - - - TPEG Pts41_10, cogwheel station - - - - - TPEG Pts41_11, funicular station - - - - - TPEG Pts41_12, ropeway station - - - - - IFOPT, coach station - - - - - IFOPT, ferry port - - - - - IFOPT, on-street bus stop - - - - - IFOPT, on-street tram stop - - - - - IFOPT, ski lift - - - - - IFOPT, other - - - - - TPEG Pts41_255, undefined stop place type - - - - - IFOPT, deprecated (SIRI 2.1), use railwayStation - - - - - IFOPT, deprecated (SIRI 2.1), use undergroundStation - - - - - - - Values for AccessibilityFeature - TPEG Pts040 and IFOPT - - - - - IFOPT, TPEG Pts40_0, unknown - - - - - TPEG Pts40_1, single step - - - - - IFOPT, TPEG Pts40_2, stairs - - - - - IFOPT, TPEG Pts40_3, escalator - - - - - IFOPT, TPEG Pts40_4, travelator / moving walkway - - - - - IFOPT, TPEG Pts40_5, lift / elevator - - - - - IFOPT, TPEG Pts40_6, ramp - - - - - TPEG Pts40_7, mind the gap - - - - - TPEG Pts40_8, tactile paving - - - - - IFOPT, series of stairs - - - - - IFOPT, shuttle - - - - - IFOPT, barrier - - - - - IFOPT, narrow entrance - - - - - IFOPT, confined space - - - - - IFOPT, queue management - - - - - IFOPT, none - - - - - IFOPT, other - - - - - TPEG Pts40_255, undefined accessibility feature type - - - - - -       + + + + + + + + + + + + + + + + + + + + + main schema + e-service developers + Waldemar Isajkin (INIT GmbH) + 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 + + + + 2013-10-10 + + + 2014-06-20 + + + 2018-06-13 + + + 2018-11-08 + + + 2019-05-07 + + + 2020-01-29 + + + +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}siri_model/siri_situationAffects.xsd + [ISO 639-2/B] ENG + CEN + + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_situationServiceTypes.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modes.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd + + + Kizoom 2000-2007, CEN 2009-2021 + + +
        +
      • Schema derived Derived from the Kizoom XTIS schema
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI-SX Xml Schema for PT Incidents. Common affects element subschema + Standard +       +       + SIRI-SX Situation Scope. +       + + + + Type for an SCHEDULED STOP POINT affected by a SITUATION. + + + + + + Alternative private code of stop. + + + + + Name of SCHEDULED STOP POINT. (Unbounded since SIRI 2.0) + + + + + Type of stop type. Normally implicit in VEHICLE mode. TPEG table pti 17_4 + + + + + Spatial coordinates of STOP POINT. Derivable from StopRef. + + + + + Reference of Stop Place related to this affected StopPoint. + + + + + Name of Stop Place related to this affected StopPoint. (Unbounded to allow a text for every language) + + + + + Modes within station/stop affected by the SITUATION. If not specified, assume all modes of that station. + + + + + Reference to a SITE or TOPOGRAPHIC PLACE affected by the Locality of stop (In UK NPtg Locality Code). Derivable from StopRef. + + + + + Name of locality in which stop is found. Derivable from LocalityRef. (Unbounded since SIRI 2.0) + + + + + Assessment of current ACCESSIBILITY of the STOP POINT as affected by the SITUATION. + + + + + Status of STOP + + + + + CONNECTION links from stop. + + + + + + CONNECTION LINKs from stop that are affected by the SITUATION. + + + + + + + + Used to restrict stop points to some lines + + + + + + + + + + + + + Type for TRANSPORT MODEs affecetd by a SITUATION. + + + + + All known modes for stop. + + + + + Mode affected by SITUATION. + + + + + + + + + + + Type for identifier of a ZONe. + + + + + + Type for a reference to a ZONE or locality. + + + + + + + + + + Type for a reference Information about a CONNECTION link from a given stop that is affected by a SITUATION. + + + + + Reference to a CONNECTION link affected by a SITUATION. + + + + + Name of CONNECTION link affected by a SITUATION. + + + + + + + + + Reference to other connecting STOP POINT of a CONNECTION link. 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 link. Derivable from StopRef. (Unbounded since SIRI 2.0) + + + + + Zone in which connecting stop lies. + + + + + + + Direction of SERVICE JOURNEY INTERCHANGE. Default is 'both'. + + + + + PATH LINKs affected by a SITUATION. + + + + + + + + Values for DIRECTION of CONNECTION link or SERVCIE JOURNEY INTERCHANGE. + + + + + + + + + + + Information about a CONNECTION link from a given stop affected by a SITUATION. + + + + + Identifier of CONNECTION link. + + + + + Description of Link. (Unbounded since SIRI 2.0) + + + + + Nature of CONNECTION link. + + + + + Description of a DIRECTION of CONNECTION link. + + + + + 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 SERVICE JOURNEY INTERCHANGE at CONNECTION link from a given SCHEDULED STOP POINT. + + + + + Reference to a SERVICE JOURNEY INTERCHANGE affected by a SITUATION. + + + + + 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. (Unbounded since SIRI 2.0) + + + + + Reference to connecting VEHICLE JOURNEY affected by a SITUATION. + + + + + + Reference to a CONNECTION Link affected by a SITUATION. + + + + + + + + + Type for identifier of an OPERATOR Code. + + + + + + Type for reference to an OPERATOR. + + + + + + + + Type for identifier of an OPERATOR Code. + + + + + + Type for reference to an Operatorational Unit Code. + + + + + + + + Type for Annotated reference to an OPERATOR affected by a SITUATION. + + + + + Reference to an OPERATOR. + + + + + Public Name of OPERATOR. Can be derived from OperatorRef. (Unbounded since SIRI 2.0) + + + + + Short Name for OPERATOR. Can be derived from OperatorRef. (Unbounded since SIRI 2.0) + + + + + OPERATIONAL UNIT responsible for managing services. + + + + + + + + Type for Annotated reference to a NETWORK affected by a SITUATION. + + + + + Reference to a NETWORK. + + + + + Name of NETWORK. Can be derived from NetworkRef. (Unbounded since SIRI 2.0) + + + + + + + + + Type for ideifier of a Route section. + + + + + + Type for reference to a Section. + + + + + + + + Line to which link connects. + + + + + + + + + + Type for identifier of an advisory NOTICE + + + + + + Type for reference to predefined advisory NOTICE. + + + + + + + + + + + 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 a 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 explicitly overridden, 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. (Unbounded since SIRI 2.0) + + + + + Textual description of overall routes affected. Should correspond to any structured description in the AffectedLines element. (Unbounded since SIRI 2.0) + + + + + + + All LINEs in the network are affected. + + + + + Only some ROUTEs are affected, LINE level information not available. See the RoutesAffected element for textual description. + + + + + Only some COMMON SECTIONs are affected, LINE level information not available. + + + + + + Information about the indvidual LINEs in the network that are affected. If not explicitly overridden, modes and submodes will be defaulted to any values present (i) in the AffectedNetwork (ii) In the general context. + + + + + + + + + + Information about the individual LINEs in the network that are affected by a SITUATION. If not explicitly overridden, modes and submodes will be defaulted to any values present (i) in the AffectedNetwork (ii) in the general context. + + + + + Restricts the affected scope to the specified operators of LINEs that are affected by the situation. Overrides any value specified for (i) Affected Network (ii) General Context. + + + + + + Restricts the affected scope to the specified ORIGINs + + + + + Restricts the affected scope to the specified DESTINATIONs + + + + + DIRECTIONs affected. + + + + + Restricts the affected scope to the specified ROUTEs + + + + + + Route affected by Situation. + + + + + + + + Restricts the affected scope to the specified LINE SECTIONs + + + + + + + + + + Used to restrict lines to some stop points + + + + + + + + + + Used to restrict lines to some stop places + + + + + + + + + + + + + Type for information about the SECTIONs affected by a SITUATION. + + + + + + Reference to a section of ROUTE affected by a SITUATION. + + + + + An indirect reference to a COMMON SECTION by stating the stop point ref of the first and last POINT IN JOURNEY PATTERN of the section in question. Intermediate POINTs should be added if necessary to distinguish different sections having the same start and end point and is a means to exclude sections not containing those stop points. + + + + + + + Used to indicate the SCHEDULED stop point at the start of the SECTION + + + + + Used to indicate that any SCHEDULED stop point with a stop assignment to the indicated StopPlace is to be considered as start of the SECTION + + + + + Used to indicate that any SCHEDULED stop point with a stop assignment to the indicated QUAY is to be considered as start of the SECTION + + + + + + + An intermediate Stop POINT of the SECTION that must be part of SECTION + + + + + Used to indicate that at least one SCHEDULED stop point with a stop assignment to the indicated StopPlace must be part of the SECTION + + + + + Used to indicate that at least one SCHEDULED stop point with a stop assignment to the indicated QUAY must be part of the SECTION + + + + + + + Used to indicate the SCHEDULED stop point at the end of the SECTION + + + + + Used to indicate that any SCHEDULED stop point with a stop assignment to the indicated StopPlace is to be considered as end of the SECTION + + + + + Used to indicate that any SCHEDULED stop point with a stop assignment to the indicated QUAY is to be considered as end of the SECTION + + + + + + + + + + Spatial projection of element that can be used to show affected area on a map. + + + + + + + + + An ordered list of MAPPING POINTs defining one single path through the road (or rail) Network. A ROUTE may pass through the same MAPPING POINT more than once. + + + + + Reference to a ROUTE affected by SITUATION. + + + + + DIRECTIONS affected by SITUATION. + + + + + Sections of ROUTE affected by SITUATION. + + + + + + Sections of ROUTE that is affected by SITUATION. + + + + + + + + Stop Poins of the ROUTE. Can be either all or only affected by SITUATION. + + + + + + Indicates whether the list of STOP POINTS contains all STOP POINTS of ROUTE or only affected by SITUATION. + + + + + + Stop Point of the ROUTE + + + + + GIs projection of Link to the next provided StopPoint. NB Line here means Geometry Polyline, not Transmodel Transport Line. + + + + + + + + + ROUTE LINKs affected by SITUATION. + + + + + + + + + + + + + + Type for information about a VEHICLE JOURNEY affected by a SITUATION. + + + + + Use of simple reference is deprecated + + + + Refercence to a VEHICLE JOURENY framed by the day. SIRI 2.0 + + + + + Reference to a service VEHICLE JOURNEY affected by a SITUATION. + + + + + + Reference to a specific DATED VEHICLE JOURNEY affected by a SITUATION. + + + + + Name of journey affected by a SITUATION. (Unbounded since SIRI 2.0) + + + + + OPERATOR of LINE affected by SITUATION. + + + + + Reference to the LINE of the journey affected by an SITUATION. + + + + + + DIRECTION of LINE in which journey runs. + + + + + BLOCK which journey runs. +SIRI 2.0 + + + + + TRAIN NUMBERs for journey. +SIRI v2.0 + + + + + + TRAIN NUMBER assigned to VEHICLE JOURNEY. +SIRI 2.0 + + + + + + + + JOURNEY PARTs making up JOURNEY +SIRIv2.0 e. + + + + + + Information about Parts of JOURNEY +SIRI v2.0 + + + + + + + + Origin SCHEDULED STOP POINTs from which the LINE runs. [equivalent to pti15 1 start_point route_description_type] + + + + + Restricts the affected scope to the specified DESTINATIONs + + + + + ROUTE affected by the SITUATION. + + + + + Timetabled departure tme of journey from Origin. + + + + + Timetabled arrival time of journey at Destination. + + + + + DESTINATION name shown for journey at the origin. Can be Used to identify joruney for user. (+SIRI 2.0), + + + + + DESTINATION name shown for journey at the origin. Can be Used to identify joruney for user. (+SIRI 2.0) + + + + + Accessibility Disruption status ofto JOURNEY, as affected by Situation. + + + + + enum Status of service for this Vehicle Journey - TPEG value. Multiple Conditions can be valid at the same time. (+SIRI 2.0) + + + + + CALLs making up VEHICLE JOURNEY [equivalent to TPEG pti15 3 stop, 15_5 not-stopping, 15-6 temporary stop route_description_type] + + + + + + + + + + Facilities available for VEHICLE JOURNEY (+SIRI 2.0) + + + + + + Facililitiy available for VEHICLE JOURNEY (+SIRI 2.0) + + + + + + + + + + + Type for information about a VEHICLE affected by an SITUATION. + + + + + Reference to a specific VEHICLE affected by an SITUATION. + + + + + Registration plate of VEHICLE + + + + + (Mobile) phone number on which the vehicle can be called + + + + + Internet protocol address of the VEHICLE in form 000.000.000.000 + + + + + Radio address of the VEHICLE + + + + + Reference to VEHICLE JOURNEY that VEHICLE is making. + + + + + Location where the VEHICLE was when the situation arosse + + + + + Current Location of the VEHICLE + + + + + Current Accessibility assessment of vehicle. + + + + + + If a VEHICLE JOURNEY is a coupled journey, i.e. comprises several coupled BLOCKparts, there will be a separate delivery for each BLOCKp art and this element will indicate the vehicles that the journey part uses. + + + + + + Whether the VEHICLE is in traffic congestion. If not, present, not known. + + + + + Whether the panic alarm on the VEHICLE is activated. Default is 'false'. + + + + + Whether this is a Headway Service, that is shown as operating at a prescribed interval rather than to a fixed timetable. Default is 'false'. + + + + + + + + Type for information about a CALL affected by an SITUATION. + + + + + + + Order of visit to stop within JORUNYE PATTERN of journey. + + + + + Status of CALL TPEG 13_6 + + + + + + + + + + + + + + + + + + + + + Elements describing the arrival of a VEHICLE at a SCHEDULED STOP POINT. + + + + + + + + + + + + Elements describing the departure of a VEHICLE from a SCHEDULED STOP POINT. + + + + + + + + + + + + Type for information about a FACILITY affected by an SITUATION. (+SIRI 2.0) + + + + + + Identifier of stop point at which availability first applies. + + + + + Identifier of stop point at which availability last applies. + + + + + Name of FACILITY. + + + + + Status of Facility + + + + + + + + + Type for annotated references to a TOPOGRAPHIC PLACE. + + + + + Reference to a SITE or TOPOGRAPHIC PLACE (Locality). + + + + + Alternative identifier of SITE or TOPOGRAPHIC PLACE + + + + + Name of SITE or TOPOGRAPHIC PLACE (locality) in which stop is found. (Unbounded since SIRI 2.0) + + + + + Spatial coordinates of STOP POINT. Derivable from StopRef. + + + + + Category of TOPGRAPHIC PLACE or SITE. + + + + + Reference to an EQUIPMENT found at location. + + + + + Changes to accessibility for SITE. + + + + + + + + + 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. (Unbounded since SIRI 2.0) + + + + + Type of Stop Place. + + + + + Facilities available for VEHICLE JOURNEY (+SIRI 2.0) + + + + + + Facililitiy available for VEHICLE JOURNEY (+SIRI 2.0) + + + + + + + + Quays affected by SITUATION. + + + + + + Quay affected by SITUATION. + + + + + + + + PathLinks affected by SITUATION. + + + + + + + + + + Used to restrict stop places to some lines + + + + + + + + + + + + + + + Type for information about the quays affected by an SITUATION. + + + + + + + Reference to a Stop Place. + + + + + Name of component. (Unbounded since SIRI 2.0) + + + + + Type of Component. + + + + + + Further qualifcation of affected part of Link projection, + + + + + Type of AccessFeature (+SIRI.20) + + + + + Facilities available for component (+SIRI 2.0) + + + + + + Facility available for VEHICLE JOURNEY (+SIRI 2.0) + + + + + + + + + + + + + Type for Information on casualties. + + + + + Number of fatalities. + + + + + Number of injured presons. + + + + + + + Values for STOP PLACE types - TPEG Pts041 and IFOPT + + + + + TPEG Pts41_0, unknown + + + + + TPEG Pts41_1, railway station + + + + + TPEG Pts41_2, underground station + + + + + IFOPT, TPEG Pts41_3, tram station + + + + + IFOPT, TPEG Pts41_4, bus station + + + + + IFOPT, TPEG Pts41_5, airport + + + + + TPEG Pts41_6, pier + + + + + IFOPT, TPEG Pts41_7, harbour port + + + + + ,IFOPT, TPEG Pts41_8, ferry stop + + + + + TPEG Pts41_9, light railway station + + + + + TPEG Pts41_10, cogwheel station + + + + + TPEG Pts41_11, funicular station + + + + + TPEG Pts41_12, ropeway station + + + + + IFOPT, coach station + + + + + IFOPT, ferry port + + + + + IFOPT, on-street bus stop + + + + + IFOPT, on-street tram stop + + + + + IFOPT, ski lift + + + + + IFOPT, other + + + + + TPEG Pts41_255, undefined stop place type + + + + + IFOPT, deprecated (SIRI 2.1), use railwayStation + + + + + IFOPT, deprecated (SIRI 2.1), use undergroundStation + + + + + + + Values for AccessibilityFeature - TPEG Pts040 and IFOPT + + + + + IFOPT, TPEG Pts40_0, unknown + + + + + TPEG Pts40_1, single step + + + + + IFOPT, TPEG Pts40_2, stairs + + + + + IFOPT, TPEG Pts40_3, escalator + + + + + IFOPT, TPEG Pts40_4, travelator / moving walkway + + + + + IFOPT, TPEG Pts40_5, lift / elevator + + + + + IFOPT, TPEG Pts40_6, ramp + + + + + TPEG Pts40_7, mind the gap + + + + + TPEG Pts40_8, tactile paving + + + + + IFOPT, series of stairs + + + + + IFOPT, shuttle + + + + + IFOPT, barrier + + + + + IFOPT, narrow entrance + + + + + IFOPT, confined space + + + + + IFOPT, queue management + + + + + IFOPT, none + + + + + IFOPT, other + + + + + TPEG Pts40_255, undefined accessibility feature type + + + + + +       diff --git a/xsd/siri_model/siri_situationClassifiers.xsd b/xsd/siri_model/siri_situationClassifiers.xsd index 621a7ec0..b96289b4 100644 --- a/xsd/siri_model/siri_situationClassifiers.xsd +++ b/xsd/siri_model/siri_situationClassifiers.xsd @@ -1,430 +1,430 @@ - - - - - - main schema - e-service developers - Add names - Europe - Drafted for version 1.0 Kizoom Incident Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk - - 2008-07-05 - - - 2008-07-05 - - - 2008-10-01 - - - - 2019-09-01 - - - -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}/siri_situationClassifiers.xsd - [ISO 639-2/B] ENG - CEN - - - Kizoom 2000-2007, CEN 2009-2021 - - -
        -
      • Schema derived Derived from the Kizoom XTIS schema
        • -
      • Derived from the TPEG Categories schema
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI-SX Xml Schema for PT Incidents. Classifier subschema - Standard -       -       - SIRI-SX Situation Classifiers. -       - - - - - Severity of Incident - TPEG Pti26. Default is 'normal'. - - - - - Values for TPEG Pti26 - Severity - - - - - TPEG Pti26_0, unknown - - - - - TPEG Pti26_1, very slight - - - - - TPEG Pti26_2, slight - - - - - TPEG Pti26_3, normal - - - - - TPEG Pti26_4, severe - - - - - TPEG Pti26_5, very severe - - - - - TPEG Pti26_6, no impact - - - - - TPEG Pti26_255, undefined - - - - - - - - Classification of effect on service. TPEG PTS043 ServiceStatus - - - - - Values for TPEG Pts43 ServiceStatus, with additional values from Pti013 - - - - - TPEG Pts43_0, unknown - - - - - TPEG Pts43_1, delay - - - - - TPEG Pts43_2, minor delays - - - - - TPEG Pts43_3, major delays - - - - - TPEG Pts43_4, operation time extension - - - - - TPEG Pts43_5, on time - - - - - TPEG Pts43_6, disturbance rectified - - - - - TPEG Pts43_7, change of platform - - - - - TPEG Pts43_8, line cancellation - - - - - TPEG Pts43_9, trip cancellation - - - - - TPEG Pts43_10, boarding - - - - - TPEG Pts43_11, go to gate - - - - - TPEG Pts43_12, stop cancelled - - - - - TPEG Pts43_13, stop moved - - - - - TPEG Pts43_14, stop on demand - - - - - TPEG Pts43_15, additional stop - - - - - TPEG Pts43_16, substituted stop - - - - - TPEG Pts43_17, diverted - - - - - TPEG Pts43_18, disruption - - - - - TPEG Pts43_19, limited operation - - - - - TPEG Pts43_20, discontinued operation - - - - - TPEG Pts43_21, irregular traffic - - - - - TPEG Pts43_22, wagon order changed - - - - - TPEG Pts43_23, train shortened - - - - - TPEG Pts43_24, additional ride - - - - - TPEG Pts43_25, replacement ride - - - - - TPEG Pts43_26, temporarily non-stopping - - - - - TPEG Pts43_27, temporary stopplace - - - - - TPEG Pts43_255, undefined status - - - - - TPEG Pti13_1, deprecated (SIRI 2.1) - - - - - TPEG Pti13_2, deprecated (SIRI 2.1) - - - - - TPEG Pti13_3, deprecated (SIRI 2.1) - - - - - TPEG Pti13_5, deprecated (SIRI 2.1) - - - - - TPEG Pti13_6, deprecated (SIRI 2.1) - - - - - TPEG Pti13_7, deprecated (SIRI 2.1) - - - - - TPEG Pti13_8, deprecated (SIRI 2.1) - - - - - TPEG Pti13_10, deprecated (SIRI 2.1) - - - - - TPEG Pti13_11, deprecated (SIRI 2.1) - - - - - TPEG Pti13_12, deprecated (SIRI 2.1) - - - - - TPEG Pti13_13, deprecated (SIRI 2.1) - - - - - TPEG Pti13_14, deprecated (SIRI 2.1) - - - - - TPEG Pti13_15, deprecated (SIRI 2.1) - - - - - TPEG Pti13_16, deprecated (SIRI 2.1) - - - - - TPEG Pti13_17, deprecated (SIRI 2.1) - - - - - TPEG Pti13_18, deprecated (SIRI 2.1) - - - - - TPEG Pti13_19, deprecated (SIRI 2.1) - - - - - TPEG Pti13_255, deprecated (SIRI 2.1) - - - - - - - - Classification of verification status - TPEG Pti032 - - - - - - - - Values for TPEG Pti032 - VerificationStatus - - - - - TPEG Pti32_0, unknown - - - - - TPEG Pti32_1, unverified - - - - - TPEG Pti32_?, verified - - - - - TPEG Pti32_?, verifiedAsDuplicate - - - - - TPEG Pti32_255 ? - - - - - - - - Classification of Predictability status. - - - - - - - - Values for Predictability Status. - - - - - - - -       + + + + + + main schema + e-service developers + Add names + Europe + Drafted for version 1.0 Kizoom Incident Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk + + 2008-07-05 + + + 2008-07-05 + + + 2008-10-01 + + + + 2019-09-01 + + + +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}/siri_situationClassifiers.xsd + [ISO 639-2/B] ENG + CEN + + + Kizoom 2000-2007, CEN 2009-2021 + + +
        +
      • Schema derived Derived from the Kizoom XTIS schema
        • +
      • Derived from the TPEG Categories schema
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI-SX Xml Schema for PT Incidents. Classifier subschema + Standard +       +       + SIRI-SX Situation Classifiers. +       + + + + + Severity of Incident - TPEG Pti26. Default is 'normal'. + + + + + Values for TPEG Pti26 - Severity + + + + + TPEG Pti26_0, unknown + + + + + TPEG Pti26_1, very slight + + + + + TPEG Pti26_2, slight + + + + + TPEG Pti26_3, normal + + + + + TPEG Pti26_4, severe + + + + + TPEG Pti26_5, very severe + + + + + TPEG Pti26_6, no impact + + + + + TPEG Pti26_255, undefined + + + + + + + + Classification of effect on service. TPEG PTS043 ServiceStatus + + + + + Values for TPEG Pts43 ServiceStatus, with additional values from Pti013 + + + + + TPEG Pts43_0, unknown + + + + + TPEG Pts43_1, delay + + + + + TPEG Pts43_2, minor delays + + + + + TPEG Pts43_3, major delays + + + + + TPEG Pts43_4, operation time extension + + + + + TPEG Pts43_5, on time + + + + + TPEG Pts43_6, disturbance rectified + + + + + TPEG Pts43_7, change of platform + + + + + TPEG Pts43_8, line cancellation + + + + + TPEG Pts43_9, trip cancellation + + + + + TPEG Pts43_10, boarding + + + + + TPEG Pts43_11, go to gate + + + + + TPEG Pts43_12, stop cancelled + + + + + TPEG Pts43_13, stop moved + + + + + TPEG Pts43_14, stop on demand + + + + + TPEG Pts43_15, additional stop + + + + + TPEG Pts43_16, substituted stop + + + + + TPEG Pts43_17, diverted + + + + + TPEG Pts43_18, disruption + + + + + TPEG Pts43_19, limited operation + + + + + TPEG Pts43_20, discontinued operation + + + + + TPEG Pts43_21, irregular traffic + + + + + TPEG Pts43_22, wagon order changed + + + + + TPEG Pts43_23, train shortened + + + + + TPEG Pts43_24, additional ride + + + + + TPEG Pts43_25, replacement ride + + + + + TPEG Pts43_26, temporarily non-stopping + + + + + TPEG Pts43_27, temporary stopplace + + + + + TPEG Pts43_255, undefined status + + + + + TPEG Pti13_1, deprecated (SIRI 2.1) + + + + + TPEG Pti13_2, deprecated (SIRI 2.1) + + + + + TPEG Pti13_3, deprecated (SIRI 2.1) + + + + + TPEG Pti13_5, deprecated (SIRI 2.1) + + + + + TPEG Pti13_6, deprecated (SIRI 2.1) + + + + + TPEG Pti13_7, deprecated (SIRI 2.1) + + + + + TPEG Pti13_8, deprecated (SIRI 2.1) + + + + + TPEG Pti13_10, deprecated (SIRI 2.1) + + + + + TPEG Pti13_11, deprecated (SIRI 2.1) + + + + + TPEG Pti13_12, deprecated (SIRI 2.1) + + + + + TPEG Pti13_13, deprecated (SIRI 2.1) + + + + + TPEG Pti13_14, deprecated (SIRI 2.1) + + + + + TPEG Pti13_15, deprecated (SIRI 2.1) + + + + + TPEG Pti13_16, deprecated (SIRI 2.1) + + + + + TPEG Pti13_17, deprecated (SIRI 2.1) + + + + + TPEG Pti13_18, deprecated (SIRI 2.1) + + + + + TPEG Pti13_19, deprecated (SIRI 2.1) + + + + + TPEG Pti13_255, deprecated (SIRI 2.1) + + + + + + + + Classification of verification status - TPEG Pti032 + + + + + + + + Values for TPEG Pti032 - VerificationStatus + + + + + TPEG Pti32_0, unknown + + + + + TPEG Pti32_1, unverified + + + + + TPEG Pti32_?, verified + + + + + TPEG Pti32_?, verifiedAsDuplicate + + + + + TPEG Pti32_255 ? + + + + + + + + Classification of Predictability status. + + + + + + + + Values for Predictability Status. + + + + + + + +       diff --git a/xsd/siri_model/siri_situationIdentity.xsd b/xsd/siri_model/siri_situationIdentity.xsd index c1eb84e1..2261094b 100644 --- a/xsd/siri_model/siri_situationIdentity.xsd +++ b/xsd/siri_model/siri_situationIdentity.xsd @@ -1,247 +1,247 @@ - - - - - - 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/schema/2.0/xsd/siri_utility/}siri_situationIdentity.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri_uility/siri_participant.xsd - - - Kizoom CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIG CML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI-SX XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Common SITUATION Identity elements. - Standard -       -       - SIRI-SX Situation IDentifiers. -       - - - - - - - - - References to a SITUATION. - - - - - - - - - Reference to a SITUATION associated with the element. - - - - - Type for reference to a SITUATION. - - - - - - Reference to a SITUATION. Elements of SITUATION identfier are expressed as atomic elements. - - - - - - - - - Reference to a SITUATION associated with the element. - - - - - Type for identifier of a SITUATION. Includes the Participant identifier and version components of the identifier. - - - - - - Type for reference to a SITUATION. Includes the Particpant identifier and version components of the identifier. - - - - - - - - - Identifier of SITUATION within a Participant. Exclude versionr. - - - - - Type for a referenceUnique identifier of a SITUATION within participant. - - - - - - - - Type for SITUATION 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. Elements 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. - - - - - - - - - Elements 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. - - - - -       + + + + + + 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/schema/2.0/xsd/siri_utility/}siri_situationIdentity.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri_uility/siri_participant.xsd + + + Kizoom CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG CML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI-SX XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Common SITUATION Identity elements. + Standard +       +       + SIRI-SX Situation IDentifiers. +       + + + + + + + + + References to a SITUATION. + + + + + + + + + Reference to a SITUATION associated with the element. + + + + + Type for reference to a SITUATION. + + + + + + Reference to a SITUATION. Elements of SITUATION identfier are expressed as atomic elements. + + + + + + + + + Reference to a SITUATION associated with the element. + + + + + Type for identifier of a SITUATION. Includes the Participant identifier and version components of the identifier. + + + + + + Type for reference to a SITUATION. Includes the Particpant identifier and version components of the identifier. + + + + + + + + + Identifier of SITUATION within a Participant. Exclude versionr. + + + + + Type for a referenceUnique identifier of a SITUATION within participant. + + + + + + + + Type for SITUATION 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. Elements 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. + + + + + + + + + Elements 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. + + + + +       diff --git a/xsd/siri_model/siri_situationReasons.xsd b/xsd/siri_model/siri_situationReasons.xsd index 1c5a6c17..2e304571 100644 --- a/xsd/siri_model/siri_situationReasons.xsd +++ b/xsd/siri_model/siri_situationReasons.xsd @@ -1,1370 +1,1370 @@ - - - - - - main schema - e-service developers - Add names - Europe - Drafted for version 1.0 Kizoom Incident Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk - - 2004-09-29 - - - 2004-10-01 - - - 2005-02-14 - - - 2007-05-14 - - - 2008-07-05 - - - - 2009-03-31 - - - - 2018-11-13 - - - - 2014-06-23 - - - - 2019-09-01 - - - -

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

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

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

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

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/standards/siri/schema/2.0/xsd/siri_model/}siri_situationServiceTypes.xsd - [ISO 639-2/B] ENG - CEN - - - - Kizoom 2000-2007, CEN 2009-2021 - - -
        -
      • Schema derived Derived from the Kizoom XTIS schema
        • -
      • Derived from the TPEG2 PTS schemas
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - Xml Schema for PT Incidents. Service subschema - Standard -       -       -       - - - - - Scope of incident - TPEG Pti27 ReportType - - - - - Values for TPEG Pti27 - ReportType - - - - - TPEG Pti27_0, unknown - - - - - TPEG Pti27_1, incident - - - - - TPEG Pti27_1_1, general - - - - - TPEG Pti27_1_2, operator - - - - - TPEG Pti27_1_3, network - - - - - TPEG Pti27_2, station terminal - - - - - TPEG Pti27_2_1, stoppoint - - - - - TPEG Pti27_2_2, connection link - - - - - TPEG Pti27_2_3, point - - - - - TPEG Pti27_3, route - - - - - TPEG Pti27_4, individual service - - - - - TPEG Pti27_255, undefined type - - - - - - - - Status of a SERVICE JOURNEY INTERCHANGE - TPEG Pti31 InterchangeStatus - - - - - Values for TPEG Pti31 - InterchangeStatus - - - - - TPEG Pti31_0, unknown - - - - - TPEG Pti31_1, connection - - - - - TPEG Pti31_2, replacement - - - - - TPEG Pti31_3, alternative - - - - - TPEG Pti31_4, connection not held - - - - - TPEG Pti31_5, connection held - - - - - TPEG Pti31_6, status of connection undecided - - - - - TPEG Pti31_255, undefined cross reference information - - - - - Interchange is planned but was updated as a result of changes in the QUAYs or arrival/departure times. Can be used if the status is a combination of the other values. +SIRI v2.1 - - - - - An important function of connection protection is the ability to hold back a distributor VEHICLE (i.e. prolonged waiting) to allow passengers to transfer from delayed feeders. -To achieve this a distributorWaitProlonged status shall be communicated back to the feeder VEHICLEs to inform the passengers about the new departure time of the distributor or even a willWait guarantee. +SIRI v2.1 - - - - - Used to provide the passengers with information about a new departure platform of the distributor VEHICLE if the distributor changes its planned stopping position. +SIRI v2.1 - - - - - Interchange is an addition to the plan. +SIRI v2.1 - - - - - Interchange is a cancellation of an interchange in the plan. +SIRI v2.1 - - - - - Loss of the inbound connection indicates the cancellation of the visit (of the FeederJourney) to the FeederArrivalStop, or a severely delayed arrival. This can lead to the distributor VEHICLE abandoning the connection. -Reasons for the loss of a feeder include (but are not limited to) the cancellation of the feeder VEHICLE, diversion/rerouting of the feeder VEHICLE, disruption of a line section or journey part of the feeder VEHICLE etc. +SIRI v2.1 - - - - - Indicates the loss of an outbound connection, i.e., is used to signal the cancellation of the onward connection to the passengers in the feeder VEHICLEs. +SIRI v2.1 - - - - - deprecated (SIRI 2.1) - use statusOfConnectionUndecided instead - - - - - - - - Ticket restrictions - TPEG Pti025 - - - - - Values for TPEG Pti025 - TicketRestrictionType - - - - - TPEG Pti25_0, unknown - - - - - TPEG Pti25_1, all ticket classes valid - - - - - TPEG Pti25_2, full fare only - - - - - TPEG Pti25_3, certain tickets only - - - - - TPEG Pti25_4, ticket with reservation - - - - - TPEG Pti25_5, special fare - - - - - TPEG Pti25_6, only tickets of specified operator - - - - - TPEG Pti25_7, no restrictions - - - - - TPEG Pti25_8, no off-peak tickets - - - - - TPEG Pti25_9, no weekend return tickets - - - - - TPEG Pti25_10, no reduced fare tickets - - - - - TPEG Pti25_255, unknown ticket restriction - - - - - - - - Booking Status - TPEG Pti024. - - - - - Values for Values for TPEG Pti024 - BookingStatus - - - - - TPEG Pti24_0, unknown - - - - - TPEG Pti24_1, available - - - - - TPEG Pti24_2, limited - - - - - TPEG Pti24_3, very limited - - - - - TPEG Pti24_4, full - - - - - TPEG Pti24_5, waiting list - - - - - TPEG Pti24_6, no booking required - - - - - TPEG Pti24_7, booking is required - - - - - TPEG Pti24_8, booking is optional - - - - - TPEG Pti24_255, undefined booking information - - - - - - - - STOP POINT type - TPEG Pts017, ServiceDeliveryPointType - - - - - Values for TPEG Pts017 - ServiceDeliveryPointType - - - - - TPEG Pts17_0, unknown - - - - - TPEG Pts17_1, platform number - - - - - TPEG Pts17_2, terminal gate - - - - - TPEG Pts17_3, ferry berth - - - - - TPEG Pts17_4, harbour pier - - - - - TPEG Pts17_5, unknown - - - - - TPEG Pts17_6, bus stop - - - - - TPEG Pts17_255, undefined service delivery point type - - - - - deprecated (SIRI 2.1) - use undefinedStopPointType - - - - - - - - Type for ROUTE POINT. - - - - - Values for ROUTE POINT type that correspond to TPEG Pts44: StopPlaceUsage (Pti15: deprecated since SIRI v2.1). - - - - - TPEG Pti15_0, Pts44_0, unknown - - - - - TPEG Pts44_1, origin - - - - - TPEG Pti15_2, Pts44_2, destination - - - - - TPEG Pts44_3, intermediate. - - - - - TPEG Pts44_4, leg board - - - - - TPEG Pts44_5, leg intermediate - - - - - TPEG Pts44_6, leg alight - - - - - TPEG Pts44_7, first route point - - - - - TPEG Pts44_8, last route point - - - - - TPEG Pts44_9, affected stop place - - - - - TPEG Pts44_10, presented stop place - - - - - TPEG Pts44_255, undefined stop place usage - - - - - TPEG Pti15_1, start point, deprecated (SIRI v2.1) and replaced by Pts44_1 value 'origin'. - - - - - TPEG Pti15_3, stop, deprecated (SIRI v2.1) - - - - - TPEG Pti15_4, via, deprecated (SIRI v2.1) - - - - - TPEG Pti15_5, not-stopping, deprecated (SIRI v2.1) - - - - - TPEG Pti15_6, temporary stop, deprecated (SIRI v2.1) - - - - - TPEG Pti15_7, temporarily not-stopping, deprecated (SIRI v2.1) - - - - - TPEG Pti15_8, exceptional stop, deprecated (SIRI v2.1) - - - - - TPEG Pti15_9, additional stop, deprecated (SIRI v2.1) - - - - - TPEG Pti15_10, request stop, deprecated (SIRI v2.1) - - - - - TPEG Pti15_11, front train destination, deprecated (SIRI v2.1) - - - - - TPEG Pti15_12, rear train destination, deprecated (SIRI v2.1) - - - - - TPEG Pti15_13, through service destination, deprecated (SIRI v2.1) - - - - - TPEG Pti15_14, not via, deprecated (SIRI v2.1) - - - - - TPEG Pti15_15, altered start point, deprecated (SIRI v2.1) - - - - - TPEG Pti15_16, altered destination, deprecated (SIRI v2.1) - - - - - TPEG Pti15_255, undefined route point, deprecated (SIRI v2.1) - - - - - - - - Timetable type - TPEG Pti033. - - - - - Values for TPEG Pti033 - TimetableType - - - - - TPEG Pti33_0, unknown - - - - - TPEG Pti33_1, winter - - - - - TPEG Pti33_2, spring - - - - - TPEG Pti33_3, summer - - - - - TPEG Pti33_4, autumn - - - - - TPEG Pti33_5, special - - - - - TPEG Pti33_6, emergency - - - - - TPEG Pti33_255, undefined timetable type - - - - -       + + + + + + main schema + e-service developers + Add names + Europe + Drafted for version 1.0 Kizoom Incident Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk + + 2004-09-29 + + + 2004-10-01 + + + 2007-05-14 + + + 2007-05-14 + + + + 2020-01-10 + + + +

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

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

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

      -

      This sub-schema describes the TargetedVehicleJourney used in the Stop Timetable Service.

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_targetedVehicleJourney.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI XML schema. Service Interface for Real-time Information. Subschema for Stop Timetable Service. - Standard -       -       - SIRI-ST TargetedVehicleJourney for Stop Timetable Service. -       - - - - - - Timetabled VEHICLE JOURNEY. - - - - - Type for a targeted VEHICLE JOURNEY. - - - - - - - - - - - - Elements for a targeted call. - - - - - Reference to a SCHEDULED 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. - - - - - -       + + + + + + 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 + + + + 2012-03-23 + + + +

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

      +

      This sub-schema describes the TargetedVehicleJourney used in the Stop Timetable Service.

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_targetedVehicleJourney.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG XML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI XML schema. Service Interface for Real-time Information. Subschema for Stop Timetable Service. + Standard +       +       + SIRI-ST TargetedVehicleJourney for Stop Timetable Service. +       + + + + + + Timetabled VEHICLE JOURNEY. + + + + + Type for a targeted VEHICLE JOURNEY. + + + + + + + + + + + + Elements for a targeted call. + + + + + Reference to a SCHEDULED 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. + + + + + +       diff --git a/xsd/siri_model/siri_time.xsd b/xsd/siri_model/siri_time.xsd index 339f1c6f..87261913 100644 --- a/xsd/siri_model/siri_time.xsd +++ b/xsd/siri_model/siri_time.xsd @@ -1,356 +1,356 @@ - - - - - - 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 - - - - 2014-06-20 - - - - 2020-01-24 - - - -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_time.xsd - [ISO 639-2/B] ENG - CEN - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIG CML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of time types. - Standard -       -       -       - - - - - 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. - - - - - - - Type for a range of times. Both start and end time are required. - - - - - The (inclusive) start time. - - - - - The (inclusive) end time. - - - - - Precision with which to interpret the inclusive end time. Default is to the second. - - - - - - - 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 range of date times. Start time must be specified, end time is optional. - - - - - The (inclusive) start time stamp. - - - - - The (inclusive) end time stamp. - - - - - Precision with which to interpret the inclusive end time. Default is to the second. (Siri 2.0++) - - - - - - - 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 defined by end time status. - - - - - If end time not provided, whethhr to interpret range as long, term, short term or unknown length of situation. Default is unknown. (Siri 2.0++) - - - - - - - Allowed values for EndTime Precision - - - - - - - - - - - Allowed values for EndTime Status. - - - - - - - - - - - Day on which a SITUATION may apply - TPEG Pti34 DayType - - - - - Values for TPEG Pti34 - DayType - - - - - TPEG Pti34_0, unknown - - - - - TPEG Pti34_1, Monday - - - - - TPEG Pti34_2, Tuesday - - - - - TPEG Pti34_3, Wednesday - - - - - TPEG Pti34_4, Thursday - - - - - TPEG Pti34_5, Friday - - - - - TPEG Pti34_6, Saturday - - - - - TPEG Pti34_7, Sunday - - - - - TPEG Pti34_8, weekdays - - - - - TPEG Pti34_9, weekends - - - - - TPEG Pti34_10, holiday - - - - - TPEG Pti34_11, public holiday - - - - - TPEG Pti34_12, religious holiday - - - - - TPEG Pti34_13, federal holiday - - - - - TPEG Pti34_14, regional holiday - - - - - TPEG Pti34_15, national holiday - - - - - TPEG Pti34_16, Monday to Friday - - - - - TPEG Pti34_17, Monday to Saturday - - - - - TPEG Pti34_18, Sundays and public holidays - - - - - TPEG Pti34_19, school days - - - - - TPEG Pti34_20, every day - - - - - TPEG Pti34_255, undefined day type - - - - - - - Subset of TPEG Pti34 - DayType - - - - - - - - - - - - - - - - - - - Subset of TPEG Pti34 - DayType - - - - - - - - - - - - - - -       + + + + + + 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 + + + + 2014-06-20 + + + + 2020-01-24 + + + +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_time.xsd + [ISO 639-2/B] ENG + CEN + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG CML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of time types. + Standard +       +       +       + + + + + 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. + + + + + + + Type for a range of times. Both start and end time are required. + + + + + The (inclusive) start time. + + + + + The (inclusive) end time. + + + + + Precision with which to interpret the inclusive end time. Default is to the second. + + + + + + + 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 range of date times. Start time must be specified, end time is optional. + + + + + The (inclusive) start time stamp. + + + + + The (inclusive) end time stamp. + + + + + Precision with which to interpret the inclusive end time. Default is to the second. (Siri 2.0++) + + + + + + + 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 defined by end time status. + + + + + If end time not provided, whethhr to interpret range as long, term, short term or unknown length of situation. Default is unknown. (Siri 2.0++) + + + + + + + Allowed values for EndTime Precision + + + + + + + + + + + Allowed values for EndTime Status. + + + + + + + + + + + Day on which a SITUATION may apply - TPEG Pti34 DayType + + + + + Values for TPEG Pti34 - DayType + + + + + TPEG Pti34_0, unknown + + + + + TPEG Pti34_1, Monday + + + + + TPEG Pti34_2, Tuesday + + + + + TPEG Pti34_3, Wednesday + + + + + TPEG Pti34_4, Thursday + + + + + TPEG Pti34_5, Friday + + + + + TPEG Pti34_6, Saturday + + + + + TPEG Pti34_7, Sunday + + + + + TPEG Pti34_8, weekdays + + + + + TPEG Pti34_9, weekends + + + + + TPEG Pti34_10, holiday + + + + + TPEG Pti34_11, public holiday + + + + + TPEG Pti34_12, religious holiday + + + + + TPEG Pti34_13, federal holiday + + + + + TPEG Pti34_14, regional holiday + + + + + TPEG Pti34_15, national holiday + + + + + TPEG Pti34_16, Monday to Friday + + + + + TPEG Pti34_17, Monday to Saturday + + + + + TPEG Pti34_18, Sundays and public holidays + + + + + TPEG Pti34_19, school days + + + + + TPEG Pti34_20, every day + + + + + TPEG Pti34_255, undefined day type + + + + + + + Subset of TPEG Pti34 - DayType + + + + + + + + + + + + + + + + + + + Subset of TPEG Pti34 - DayType + + + + + + + + + + + + + + +       diff --git a/xsd/siri_model_discovery/siri_connectionLink.xsd b/xsd/siri_model_discovery/siri_connectionLink.xsd index 74e01670..e7aa1290 100644 --- a/xsd/siri_model_discovery/siri_connectionLink.xsd +++ b/xsd/siri_model_discovery/siri_connectionLink.xsd @@ -1,115 +1,115 @@ - - - - - - main schema - e-service developers - CEN TC278 WG3 SG7 Team - Europe - Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2013-03-07 - - -

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

      -

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

      • Service Feature discovery
      • TYPE OF PRODUCT CATEGORY Discovery
      -

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/}siri_discovery.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference.xsd - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Discovery services Derived from the NaPTAN standard .
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI_DS XML schema. Service Interface for Real-time Information. Discovery subschema. - Standard -       -       - SIRI subschema with view of SCHEDULED CONNECTION LINKS for use in Connection Link Discovery service -       - - - - - - - SCHEDULED CONNECTION LINK definition. - - - - - View of a SCHEDULED CONNECTION LINK description. - - - - - Identifer of the connection link. DetailLevel=minimum - - - - - Identifer of the feeder's stop. DetailLevel=normal - - - - - Identifer of the distributor's stop. DetailLevel=normal - - - - - Whether real-time data is available for the connection link. Default is 'true'. DetailLevel=minimum - - - - - Name of SCHEDULED CONNECTION LINK. DetailLevel=minimum - - - - - Name of the feeder's stop. DetailLevel=full - - - - - Name of the distributor's stop. DetailLevel=full - - - - - Web page associated with connection link. DetailLevel=full - - - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2013-03-07 + + +

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

      +

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

      • Service Feature discovery
      • TYPE OF PRODUCT CATEGORY Discovery
      +

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}siri_discovery.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Discovery services Derived from the NaPTAN standard .
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI_DS XML schema. Service Interface for Real-time Information. Discovery subschema. + Standard +       +       + SIRI subschema with view of SCHEDULED CONNECTION LINKS for use in Connection Link Discovery service +       + + + + + + + SCHEDULED CONNECTION LINK definition. + + + + + View of a SCHEDULED CONNECTION LINK description. + + + + + Identifer of the connection link. DetailLevel=minimum + + + + + Identifer of the feeder's stop. DetailLevel=normal + + + + + Identifer of the distributor's stop. DetailLevel=normal + + + + + Whether real-time data is available for the connection link. Default is 'true'. DetailLevel=minimum + + + + + Name of SCHEDULED CONNECTION LINK. DetailLevel=minimum + + + + + Name of the feeder's stop. DetailLevel=full + + + + + Name of the distributor's stop. DetailLevel=full + + + + + Web page associated with connection link. DetailLevel=full + + + + + +       diff --git a/xsd/siri_model_discovery/siri_feature.xsd b/xsd/siri_model_discovery/siri_feature.xsd index c3c22b71..3d7d48ac 100644 --- a/xsd/siri_model_discovery/siri_feature.xsd +++ b/xsd/siri_model_discovery/siri_feature.xsd @@ -1,158 +1,158 @@ - - - - - - main schema - e-service developers - CEN TC278 WG3 SG7 Team - Europe - Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2012-03-23 - - - 2008-11-17 - - - - 2012-03-23 - - - -

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

      -

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

      • SERVICE FEATURE discovery
      • TYPE OF PRODUCT CATEGORY Discovery
      -

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/}siri_discovery.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference.xsd - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Discovery services Derived from the NaPTAN standard .
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI_DS XML schema. Service Interface for Real-time Information. Discovery subschema. - Standard -       -       - SIRI subschema with view of classifiers for use in Discovery service -       - - - - - - - - - Category for classification of a journey as a Product - - - - - Type for TYPE OF PRODUCT CATEGORY description. - - - - - Identifier of TYPE OF PRODUCT CATEGORY classification. SIRI provides a recommended set of values covering most usages, intended to be TPEG compatible. See the SIRI facilities packaged. - - - - - Name of classification (Unbounded since SIRI 2.0) - - - - - Icon used to represent TYPE OF PRODUCT CATEGORY. - - - - - - - - Service Feature description. - - - - - Type for Service Feature description. - - - - - Identifier of classification. SIRI provides a recommended set of values covering most usages, intended to be TPEG compatible. See the SIRI facilities packaged. - - - - - Name of classification. (Unbounded since SIRI 2.0) - - - - - Icon associated with feature. - - - - - - - - Vehicle Feature description. - - - - - Type for description of feature of VEHICLE. - - - - - Identifier of feature of VEHICLE. SIRI provides a recommended set of values covering most usages, intended to be TPEG compatible. See the SIRI facilities packaged. - - - - - Name of feature of VEHICLE. (Unbounded since SIRI 2.0) - - - - - Icon used to represent feature of VEHICLE. - - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2012-03-23 + + + 2008-11-17 + + + + 2012-03-23 + + + +

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

      +

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

      • SERVICE FEATURE discovery
      • TYPE OF PRODUCT CATEGORY Discovery
      +

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}siri_discovery.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Discovery services Derived from the NaPTAN standard .
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI_DS XML schema. Service Interface for Real-time Information. Discovery subschema. + Standard +       +       + SIRI subschema with view of classifiers for use in Discovery service +       + + + + + + + + + Category for classification of a journey as a Product + + + + + Type for TYPE OF PRODUCT CATEGORY description. + + + + + Identifier of TYPE OF PRODUCT CATEGORY classification. SIRI provides a recommended set of values covering most usages, intended to be TPEG compatible. See the SIRI facilities packaged. + + + + + Name of classification (Unbounded since SIRI 2.0) + + + + + Icon used to represent TYPE OF PRODUCT CATEGORY. + + + + + + + + Service Feature description. + + + + + Type for Service Feature description. + + + + + Identifier of classification. SIRI provides a recommended set of values covering most usages, intended to be TPEG compatible. See the SIRI facilities packaged. + + + + + Name of classification. (Unbounded since SIRI 2.0) + + + + + Icon associated with feature. + + + + + + + + Vehicle Feature description. + + + + + Type for description of feature of VEHICLE. + + + + + Identifier of feature of VEHICLE. SIRI provides a recommended set of values covering most usages, intended to be TPEG compatible. See the SIRI facilities packaged. + + + + + Name of feature of VEHICLE. (Unbounded since SIRI 2.0) + + + + + Icon used to represent feature of VEHICLE. + + + + +       diff --git a/xsd/siri_model_discovery/siri_infoChannel.xsd b/xsd/siri_model_discovery/siri_infoChannel.xsd index 99c69b0e..8d0aa3cd 100644 --- a/xsd/siri_model_discovery/siri_infoChannel.xsd +++ b/xsd/siri_model_discovery/siri_infoChannel.xsd @@ -1,99 +1,99 @@ - - - - - - main schema - e-service developers - CEN TC278 WG3 SG7 Team - Europe - Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2012-03-23 - - - 2008-11-17 - - - - 2012-03-23 - - - -

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

      -

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

      • Service Feature discovery
      • TYPE OF PRODUCT CATEGORY Discovery
      -

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/}siri_discovery.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference.xsd - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Discovery services Derived from the NaPTAN standard .
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI_DS XML schema. Service Interface for Real-time Information. Discovery subschema. - Standard -       -       - SIRI subschema with view of Info channel for use in Discovery service -       - - - - - - Info Channel supported by Producer service. - - - - - Type for Info Channels description. - - - - - Identifier of classification. - - - - - Name of Info Channel. - - - - - Icon associated with Info Channel. - - - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2012-03-23 + + + 2008-11-17 + + + + 2012-03-23 + + + +

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

      +

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

      • Service Feature discovery
      • TYPE OF PRODUCT CATEGORY Discovery
      +

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}siri_discovery.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Discovery services Derived from the NaPTAN standard .
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI_DS XML schema. Service Interface for Real-time Information. Discovery subschema. + Standard +       +       + SIRI subschema with view of Info channel for use in Discovery service +       + + + + + + Info Channel supported by Producer service. + + + + + Type for Info Channels description. + + + + + Identifier of classification. + + + + + Name of Info Channel. + + + + + Icon associated with Info Channel. + + + + + +       diff --git a/xsd/siri_model_discovery/siri_line.xsd b/xsd/siri_model_discovery/siri_line.xsd index 54c132f7..2dea9ebd 100644 --- a/xsd/siri_model_discovery/siri_line.xsd +++ b/xsd/siri_model_discovery/siri_line.xsd @@ -1,241 +1,241 @@ - - - - - - main schema - e-service developers - CEN TC278 WG3 SG7 Team - Europe - Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2012-03-23 - - - 2008-11-17 - - - - 2012-03-23 - - - - 2012-05-10 - - - - 2012-06-12 - - - -

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

      -

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

      • Service Feature discovery
      • TYPE OF PRODUCT CATEGORY Discovery
      -

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/}siri_discovery.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference.xsd - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Discovery services Derived from the NaPTAN standard .
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI_DS XML schema. Service Interface for Real-time Information. Stop Discovery subschema. - Standard -       -       - SIRI subschema with view of LINE for use in Discovery service -       - - - - - - - - - - Information about LINEs covered by server. - - - - - Summary information about a LINE type. - - - - - Identifier of LINE. - - - - - Name of LINE. (Unbounded since SIRI 2.0) - - - - - Whether the LINE has real-time info. Default is 'true'. - - - - - DESTINATIONs to which the LINE runs. Detail level is 'normal' - - - - - - - - - - DIRECTIONs and Stops for the LINE. 'normal' - - - - - - Directions of Route - - - - - - - - - - - - Summary information about a Direction of a Line - - - - - - - JourneyPatterns in Direction of route (+SIRI 2.0) - - - - - - JourneyPattern. (+SIRI 2.0) - - - - - - - Name Of Journety Pattern (SIRI 2.0) - - - - - Ordered collection of STOP POINTs the LINE and direction . Detail level is 'stops'. +SIRI v2.0 - - - - - - Stop within Route of LINE. Detail level is 'stop' +SIRI v2.0 - - - - - - - - - - - - - - - - - - - Summary information about a stop within line - - - - - - - Order of STOP POINT in route +SIRI v2.0 - - - - - Plot of points from this stop to next Stop. Detail level is 'full'. +SIRI v2.0 - - - - - GIs projection of Link to the next provided StopPoint. NB Line here means Geometry Polyline, not Transmodel Transport Line. - - - - - - - - - - - Description of a DESTINATION. - - - - - Type for DESTINATION and place name. - - - - - - Name of destination TOPOGRAPHIC PLACE. (Unbounded since SIRI 2.0) - - - - - Direction in which destination lies. relatoive to currernt stop SIRI 2.0 - - - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2012-03-23 + + + 2008-11-17 + + + + 2012-03-23 + + + + 2012-05-10 + + + + 2012-06-12 + + + +

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

      +

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

      • Service Feature discovery
      • TYPE OF PRODUCT CATEGORY Discovery
      +

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

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

      -

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

      • Service Feature discovery
      • TYPE OF PRODUCT CATEGORY Discovery
      -

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/}siri_discovery.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference.xsd - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Discovery services Derived from the NaPTAN standard .
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI_DS XML schema. Service Interface for Real-time Information. Discovery subschema. - Standard -       -       - SIRI subschema with view of SCHEDUELD STOP POINT for use in Stop Discovery service -       - - - - - - - - SCHEDULED STOP POINT definition. - - - - - View of a SCHEDULED STOP POINT description. - - - - - Identifer of the stop. - - - - - - Whether real-time data is available for the stop. Default is 'true'. Detail level is 'normal'. - - - - - Name of SCHEDULED STOP POINT. Detail level is 'normal'. (Unbounded since SIRI 2.0) - - - - - Identifer of the sSTOP AREA to which SCHEDULED STOP POINT belongs. +SIRI.v2.0 - - - - - Service features of stop. Detail level is 'full' - - - - - - Description of Service features of stop. - - - - - - - - - LINEs that use stop. Detail level is 'full' - - - - - - Reference to a LINE that calls at stop. - - - - - Reference to a LINE that calls at stop. and its direction +SIRI V2.0 - - - - - - - - Coordinates to use to show stop as a poitn on map. Detail level is 'normal'.+SIRI.v2.0 - - - - - Web page associated with Stop. Detail level is 'full'+SIRI.v2.0 - - - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2012-03-23 + + + 2008-11-17 + + + + 2012-03-23 + + + + 2012-06-12 + + + +

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

      +

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

      • Service Feature discovery
      • TYPE OF PRODUCT CATEGORY Discovery
      +

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}siri_discovery.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Discovery services Derived from the NaPTAN standard .
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI_DS XML schema. Service Interface for Real-time Information. Discovery subschema. + Standard +       +       + SIRI subschema with view of SCHEDUELD STOP POINT for use in Stop Discovery service +       + + + + + + + + SCHEDULED STOP POINT definition. + + + + + View of a SCHEDULED STOP POINT description. + + + + + Identifer of the stop. + + + + + + Whether real-time data is available for the stop. Default is 'true'. Detail level is 'normal'. + + + + + Name of SCHEDULED STOP POINT. Detail level is 'normal'. (Unbounded since SIRI 2.0) + + + + + Identifer of the sSTOP AREA to which SCHEDULED STOP POINT belongs. +SIRI.v2.0 + + + + + Service features of stop. Detail level is 'full' + + + + + + Description of Service features of stop. + + + + + + + + + LINEs that use stop. Detail level is 'full' + + + + + + Reference to a LINE that calls at stop. + + + + + Reference to a LINE that calls at stop. and its direction +SIRI V2.0 + + + + + + + + Coordinates to use to show stop as a poitn on map. Detail level is 'normal'.+SIRI.v2.0 + + + + + Web page associated with Stop. Detail level is 'full'+SIRI.v2.0 + + + + + +       diff --git a/xsd/siri_productionTimetable_service.xsd b/xsd/siri_productionTimetable_service.xsd index 5fa32773..fe8989c4 100644 --- a/xsd/siri_productionTimetable_service.xsd +++ b/xsd/siri_productionTimetable_service.xsd @@ -1,514 +1,514 @@ - - - - - - main schema - e-service developers - CEN TC278 WG3 SG7 Team - Werner Kohl MDV - Europe - Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2003-02-10 - - - 2004-10-31 - - - 2005-02-14 - - - 2005-02-20 - - - 2005-05-11 - - - 2007-04-17 - - - - 2008-03-26 - - - - 2008-11-17 - - - - 2011-04-18 - - - - 2011-01-19 - - - - 2012-03-23 - - - -

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

      -

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

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

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

      +

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

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

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

      -

      This sub-schema describes the Situation Exchange Service.

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/}siri_SituationExchange_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_situation.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions.xsd - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      • categories from TPEG
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI-SX XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Situation Exchange Service Subschema - Standard -       -       - SIRI-SX Situation Exchange Service. -       - - - - - - - - - - - - - - - - - Convenience artifact to pick out main elements of the Situation Exchange Service. - - - - - - - - - - - - - - - - Request for information about Facilities status. - - - - - Type for Functional Service Request for Situation Exchange Service. - - - - - - - - - - - Version number of request. Fixed - - - - - - - - - Parameters that specify the content to be returned. Logically ANDed with other values. - - - - - Parameters to control time for which subscription applies. - - - - - Parameters to filter Situation Exchange Service requests, based on the time. Logically ANDed with other values. - - - - - - - - - - - - Parameters to filter Situation Exchange Service requests, based on the SITUATION Road. Logically ANDed with other values. - - - - - - - - - - Parameters to filter Situation Exchange Service requests, based on specific needs . - - - - - - - Parameters to filter Situation Exchange Service requests, based on the SITUATION Status. Logically ANDed with other values. - - - - - Forward duration for which SITUATIONs should be included, that is, only SITUATIONs that start before the end of this window time will be included. - - - - - Start time for selecting SITUATIONs to be sent. Only SITUATIONs or updates created after this time will be sent. This enables a restart without resending everything. - - - - - - - Parameters to filter Situation Exchange Service requests, based on the SITUATION Status. Logically ANDed with other values. - - - - - Temporal scope of Situations be included in response. The Situations must be valid within the specified period of time. (+SIRI 2.0) - - - - - Only incidents that are currently within their publication window shouldbe included. Otherwose all incidents will be included. Default is false - - - - - - - Parameters to filter Situation Exchange Service requests, based on the SITUATION Status. Logically ANDed with other values. - - - - - Whether incident has been verified or not If not specified return all. - - - - - Workflow Progress Status. One of a specified set of overall processing states assigned to SITUATION. For example, 'Draft' for not yet published; 'Published' for live SITUATIONs; 'Closed' indicates a completed SITUATION. If not specified return open, published closing and closed. l. - - - - - Whether SITUATION is real or a test. If not specified return all. - - - - - - - Parameters to filter Situation Exchange Service requests, based on the SITUATION Network. Logically ANDed with other values. - - - - - Referance to an OPERATOR. If unspecified, all OPERATOR.s. - - - - - OPERATIONAL UNIT responsible for managing services. - - - - - Reference to a NETWORK. - - - - - - Filter the results to include only the given line. - - - - - Filter the results to include only situations along the given LINEs. - - - - - - Filter the results to include only the given line. and direction - - - - - - - - - - - - - - Parameters to filter Situation Exchange Service requests, based on the STOP PLACEs affected SITUATIONs. Logically ANDed with other values. - - - - - Reference to a STOP PLACE. - - - - - Reference to part of a STOP PLACE. (+SIRI 2.0) - - - - - - - Parameters to filter Situation Exchange Service requests, based on the VEHICLE JOURNEYs affected by the SITUATION. Logically ANDed with other values. - - - - - Use of simple reference is deprecated - - - - Refercence to a VEHICLE JOURNEY framed by the day. SIRI 2.0 - - - - - - - - - - - Parameters to filter Situation Exchange Service requests, based on the SITUATION Classifiers. Logically ANDed with other values. - - - - - Severity filter value to apply: only SITUATIONs with a severity greater than or equal to the specified value will be returned. See TPEG severities. Default is '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 Service requests, based on the SITUATION Place. Logically ANDed with other values. - - - - - Reference to a COUNTRY where incident takes place If specified only incidents that affect this place country will be returned. - - - - - Reference to a TOPOGRAPHIC PLACE. Only incidents which are deemed to affect this place will be returned. - - - - - Bounding box of an arbitrary area. Only incidents geocoded as falling within area will be included. - - - - - - - Type for Parameters to filter Situation Exchange Service requests, based on the SITUATION Road, Logically ANDed with other values. - - - - - Identifier or number of the road on which the reference POINT is located. - - - - - The DIRECTION at the reference point in terms of general destination DIRECTION. If absent both. - - - - - Road reference POINT identifier, unique on the specified road. - - - - - - - Parameters that affect the request processing. - - - - - Preferred languages in which to return text values. - - - - - - The maximum number of SITUATION elements to return in a given delivery. The most recent n Events within the look ahead window are included. - - - - - - - - Request for a subscription to the Situation Exchange Service. - - - - - Parameters that affect the subscription publishing and notification processing. - - - - - Whether the producer will return the complete set of current data, or only provide updates to this data, i.e. additions, modifications and deletions. -If false or omitted, each subscription response will contain the full information as specified in this request. - - - - - - - Type for Subscription Request for Situation Exchange Service. - - - - - - - - - - - - - - - - Delivery for Situation Exchange Service. - - - - - Delivery of Situation Exchange Service included as supplement to main functional service delivery. - - - - - Payload part of Situation Exchange Service delivery. - - - - - Default context for common properties of SITUATIONs, Values specified apply to all SITUATIONs unless overridden. Can be used optionally to reduce file bulk. - - - - - SITUATIONs in Delivery. - - - - - - Description of a SITUATION. - - - - - - - - - - - Type for Delivery for Situation Exchange Service. Provides information about one or more vehicles; each has its own VEHICLE activity element. - - - - - - - Payload part of Situation Exchange Service delivery. - - - - - - - Version number of response. Fixed - - - - - - - - - - Common parameters for all SITUATIONs. - - - - - Reference to a Country of a Participant who published SITUATION. - - - - - Reference to a system publishing SITUATIONs. If SITUATIONs from other participants are included in delivery, then ParticipantRef of immediate publisher must be given here. - - - - - Refrence to a TOPOGRAPHIC PLACE (locality). Also Derivable from an individual StopRef. - - - - - Name of locality in which SITUATIONs apply. Derivable from LocalityRef. (Unbounded since SIRI 2.0) - - - - - Default language of text. - - - - - Default context for common properties of Public Transport SITUATIONs. - - - - - Actions that apply to all SITUATIONs unless overridden. - - - - - - - - Type for shared context. - - - - - Default OPERATOR for SITUATIONs. - - - - - Default Network of affected LINEs. These values apply to all SITUATIONs unless overridden on individual instances. - - - - - - - - - Type for Deliveries for Situation Exchange Service. Used in WSDL. - - - - - Delivery for Vehicle Activity Service. - - - - - - - - - Request for information about Situation Exchange Service Capabilities. Answered with a VehicleMontoringCapabilitiesResponse. - - - - - - Capabilities for Situation Exchange Service. Answers a VehicleMontoringCapabilitiesRequest. - - - - - Type for Delivery for Situation Exchange Service. - - - - - - - - - - - Version number of response. Fixed - - - - - - - - - Capabilities of Situation Exchange Service. Answers a SituationExchangeCapabilitiesRequest. - - - - - Type for SItuation Exchange Service Capabilities. - - - - - - - Filtering Capabilities. - - - - - - Default preview interval. Default is 60 minutes. - - - - - - Whether results can be filtered by location. Fixed as 'true'. - - - - - - Whether results can be filtered by MODE. Default is true.. (+SIRI v2.0) - - - - - Whether results can be filtered by NETWORKs. Default is 'true'. (+SIRI v2.0) - - - - - - - Whether results can be filtered by STOP PLACE identifvier. Default is 'false'. (+SIRI v2.0) - - - - - - - - Whether results can be filtered by Specific Needs. Default is 'true'. - - - - - Whether results can be filtered by Keywords. Default is 'false' - - - - - - - - Request Policy capabilities. - - - - - - - - - - - - - - Subscription Policy capabilities. - - - - - Optional Access control capabilities. - - - - - - - - - - - - - - - Optional Response capabilities. - - - - - - - - - - - - - Elements for volume control. - - - - - Whether a maximum number ofSITUATIONS to include can be specified. Default is 'false'. - - - - - - - - Participant's permissions to use the service. - - - - - - - - - - - - - - Type for Situation Exchange Service Permissions. - - - - - - - - - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + Drafted for version 1.1 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + + 2008-01-22 + + + 2008-01-22 + + + 2009-04-17 + + + + 2008-01-17 + + + + 2008-07-05 + + + + 2008-10-01 + + + + 2008-11-17 + + + + 2012-03-23 + + + + 2013-10-09 + + + + 2014-06-20 + + + + 2018-11-13 + + + +

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

      +

      This sub-schema describes the Situation Exchange Service.

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

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

      -

      This sub-schema describes the Stop Monitoring Service.

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

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

      +

      This sub-schema describes the Stop Monitoring Service.

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

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

      -

      This sub-schema describes the Stop Timetable Service.

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/}siri_stopTmetable_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions.xsd - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI XML schema. Service Interface for Real-time Information. Subschema for Stop Timetable Service. - Standard -       -       - SIRI-ST Stop Timetable Service. -       - - - - - - - Convenience artifact to pick out main elements of the Stop Timetable Service. - - - - - - - - - - - - - - Request for information about Stop Visits, i.e. arrival and departure at a stop. - - - - - - - Type for Functional Service Request for Stop Timetables. - - - - - - - - - - - Version number of request. Fixed - - - - - - - - - Parameters that specify the content to be returned. - - - - - Earliest and latest departure time. If absent, default to the data horizon of the service. - - - - - The stop monitoring point about which data is requested. May be a STOP POINT, timing point or other display point. - - - - - Filter the results to include only data for journeys for the given LINE. - - - - - Filter the results to include only data for journeys running in a specific relative DIRECTION, for example, "inbound" or "outbound". - - - - - - - Parameters that affect the request processing. Mostly act to reduce the number of stops returned. - - - - - Preferred languages in which to return text values. - - - - - - - - - Request for a subscription to Stop TimetablesService. - - - - - Parameters that affect the subscription publishing and notification processing. - - - - - Whether the producer should return the complete set of current data, or only provide updates to the last data returned, i.e. additions, modifications and deletions. -If false each subscription response will contain the full information as specified in this request. - - - - - The amount of change to the arrival or departure time that can happen before an update is sent (i.e. if ChangeBeforeUpdate is set to 2 minutes, the subscriber will not be told that a bus is 30 seconds delayed - an update will only be sent when the bus is at least 2 minutes delayed). Default is zero - all changes will be sent regardless. - - - - - - - Subscription Request for Stop Timetables. - - - - - - - - - - - - - - - - Delivery for Stop Timetable Service. - - - - - Data type Delivery for Stop Timetable Service. - - - - - - - - - - Version number of response. Fixed - - - - - - - - - Payload part of Stop Timetable delivery. - - - - - A visit to a stop by a VEHICLE as an arrival and /or departure, as timetabled in the production timetable. - - - - - A cancellation of a previously issued TimetabledStopVisit. - - - - - - - - Type for Timetabled Visit of a VEHICLE to a stop. May provide information about the arrival, the departure or both. - - - - - - - Reference to a stop monitoring point / LOGICAL DISPLAY to which Stop Visit applies. - - - - - - - - - - - Type for Cancellation of Timetabled Visit of a VEHICLE to a stop. May provide information about the arrival, the departure or both. - - - - - - - Reference to a stop monitoring point to which Stop Visit applies. - - - - - - - - Reason for cancellation. (Unbounded since SIRI 2.0) - - - - - - - - - - - - Type for stop timetable deliveries. Used in WSDL. - - - - - - - - - - - Request for information about Stop Timetable Service Capabilities Answered with a StopTimetableCapabilitiesResponse. - - - - - - Delivery for Stop Timetable Service. Answers a StopTimetableCapabilitiesRequest. - - - - - Type for Delivery for Stop Timetable Service. - - - - - - - - - - - Version number of response. Fixed - - - - - - - - - Capabilities of Stop Timetable Service. - - - - - Type for Capabilities of Stop Timetable Service. - - - - - - - Available Filtering Capabilities. - - - - - - - - - - - - Available request policy options. - - - - - Access control that can be used. - - - - - - - - - - - - - - - - - - - - - Type for Monitoring Service Capability Request Policy. - - - - - - - Whether results can return references for stops. Default is 'true'. - - - - - Whether results can return names for stop. - - - - - - - - - Participant's permissions to use the service. - - - - - - - - Permission for a single participant or all participants to use an aspect of the service. - - - - - - - - - - - - Type for Monitoring Service Permission. - - - - - - - - - The monitoring points that the participant may access. - - - - - - - Participant's permission for this Monitoring Point (LOGICAL DISPLAY) - - - - - - - - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2004-09-29 + + + 2004-10-01 + + + 2005-02-14 + + + 2005-02-20 + + + 2005-05-11 + + 2005-12-12 + 2005 12 07 Correct Spelling of StopMonitorPermissionTag + + 2007-04-17 + Name Space changes + + 2007-03-26 + Drop separate flatten structure on response for stopVisit + + 2008-11-17 + Revise to support substitution groups + + 2012-03-23 + +SIRI v2.0 + Improve modualirisatuioin + Factor out permissions to commomn files + factor out targeted journey, + create separate structure for StopTimetablePermissionStructure + create separate structure for StopTimetableCapabilityRequestPolicyStructure + + +

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

      +

      This sub-schema describes the Stop Timetable Service.

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}siri_stopTmetable_service.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG XML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG7 + + SIRI XML schema. Service Interface for Real-time Information. Subschema for Stop Timetable Service. + Standard +       +       + SIRI-ST Stop Timetable Service. +       + + + + + + + Convenience artifact to pick out main elements of the Stop Timetable Service. + + + + + + + + + + + + + + Request for information about Stop Visits, i.e. arrival and departure at a stop. + + + + + + + Type for Functional Service Request for Stop Timetables. + + + + + + + + + + + Version number of request. Fixed + + + + + + + + + Parameters that specify the content to be returned. + + + + + Earliest and latest departure time. If absent, default to the data horizon of the service. + + + + + The stop monitoring point about which data is requested. May be a STOP POINT, timing point or other display point. + + + + + Filter the results to include only data for journeys for the given LINE. + + + + + Filter the results to include only data for journeys running in a specific relative DIRECTION, for example, "inbound" or "outbound". + + + + + + + Parameters that affect the request processing. Mostly act to reduce the number of stops returned. + + + + + Preferred languages in which to return text values. + + + + + + + + + Request for a subscription to Stop TimetablesService. + + + + + Parameters that affect the subscription publishing and notification processing. + + + + + Whether the producer should return the complete set of current data, or only provide updates to the last data returned, i.e. additions, modifications and deletions. +If false each subscription response will contain the full information as specified in this request. + + + + + The amount of change to the arrival or departure time that can happen before an update is sent (i.e. if ChangeBeforeUpdate is set to 2 minutes, the subscriber will not be told that a bus is 30 seconds delayed - an update will only be sent when the bus is at least 2 minutes delayed). Default is zero - all changes will be sent regardless. + + + + + + + Subscription Request for Stop Timetables. + + + + + + + + + + + + + + + + Delivery for Stop Timetable Service. + + + + + Data type Delivery for Stop Timetable Service. + + + + + + + + + + Version number of response. Fixed + + + + + + + + + Payload part of Stop Timetable delivery. + + + + + A visit to a stop by a VEHICLE as an arrival and /or departure, as timetabled in the production timetable. + + + + + A cancellation of a previously issued TimetabledStopVisit. + + + + + + + + Type for Timetabled Visit of a VEHICLE to a stop. May provide information about the arrival, the departure or both. + + + + + + + Reference to a stop monitoring point / LOGICAL DISPLAY to which Stop Visit applies. + + + + + + + + + + + Type for Cancellation of Timetabled Visit of a VEHICLE to a stop. May provide information about the arrival, the departure or both. + + + + + + + Reference to a stop monitoring point to which Stop Visit applies. + + + + + + + + Reason for cancellation. (Unbounded since SIRI 2.0) + + + + + + + + + + + + Type for stop timetable deliveries. Used in WSDL. + + + + + + + + + + + Request for information about Stop Timetable Service Capabilities Answered with a StopTimetableCapabilitiesResponse. + + + + + + Delivery for Stop Timetable Service. Answers a StopTimetableCapabilitiesRequest. + + + + + Type for Delivery for Stop Timetable Service. + + + + + + + + + + + Version number of response. Fixed + + + + + + + + + Capabilities of Stop Timetable Service. + + + + + Type for Capabilities of Stop Timetable Service. + + + + + + + Available Filtering Capabilities. + + + + + + + + + + + + Available request policy options. + + + + + Access control that can be used. + + + + + + + + + + + + + + + + + + + + + Type for Monitoring Service Capability Request Policy. + + + + + + + Whether results can return references for stops. Default is 'true'. + + + + + Whether results can return names for stop. + + + + + + + + + Participant's permissions to use the service. + + + + + + + + Permission for a single participant or all participants to use an aspect of the service. + + + + + + + + + + + + Type for Monitoring Service Permission. + + + + + + + + + The monitoring points that the participant may access. + + + + + + + Participant's permission for this Monitoring Point (LOGICAL DISPLAY) + + + + + + + + + + +       diff --git a/xsd/siri_utility/siri_all_utility.xsd b/xsd/siri_utility/siri_all_utility.xsd index 82a84bd0..6160a385 100644 --- a/xsd/siri_utility/siri_all_utility.xsd +++ b/xsd/siri_utility/siri_all_utility.xsd @@ -1,14 +1,14 @@ - - - - - - - - - - - + + + + + + + + + + + diff --git a/xsd/siri_utility/siri_location.xsd b/xsd/siri_utility/siri_location.xsd index bc7d6a2f..90763b71 100644 --- a/xsd/siri_utility/siri_location.xsd +++ b/xsd/siri_utility/siri_location.xsd @@ -1,270 +1,270 @@ - - - - - - main schema - e-service developers - CEN TC278 WG3 SG9 Team. - Europe - First drafted for version 1.0 CEN TC278 WG3 SG9 Editor Nicholas Knowles. mailto:schemer@siri.org.uk - - 2004-09-29 - - - 2004-10-01 - - - 2005-02-14 - - - 2005-05-11 - - - 2005-05-04 - - - 2007-03-29 - - - 2012-03-23 - - - - 2012-05-10 - - - -

      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/schema/2.0/xsd/siri_utility/}siri_location.xsd - [ISO 639-2/B] ENG - CEN - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG9. - - SIRI XML schema. Geo spatial location subschema - Standard -       -       - SIRI Framewrok Location Types. -       - - - - - - - - Longitude from Greenwich. - - - - - - - - - Latitude from equator. - - - - - - - - - Altitude metres from sea level. - - - - - - - - - WGS84 Coordinates. - - - - - Longitude from Greenwich Meridian. -180 (West) to +180 (East). Decimal degrees, e.g. 2.356 - - - - - Latitude from equator. -90 (South) to +90 (North). Decimal degrees, e.g. 56.356 - - - - - Altitude metres from sea level. - - - - - - - Type for GM Coordinates. - - - - - - - - Type for coordinate reference system. - - - - - - GML Spatial coordinate reference system. - - - - - - Type for geospatial Position of a point. May be expressed in concrete WGS 84 Coordinates or any gml compatible point coordinates format. - - - - - - - - - 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. - - - - - - Defines a bounding box using two corner points. GML terminology. +SIRI v2.0 - - - - - Upper Left corner as a geospatial point. - - - - - Lower right corner as a geospatial point. - - - - - - - Defines a line shape +SIRI v2.0 - - - - - A geospatial point. +SIRI v2.0 - - - - - - - Type for a circular area centered around a point that may be expressed in concrete WGS 84 Coordinates or any gml compatible point coordinates format. +SIRI v2.1 - - - - - - - Radius around the center point in meters. - - - - - - - - - Bounding box, circular area or gml:polyon of the area where stops of a flexible service are called. +SIRI v2.1 -A flexible area is used in cases where a pre-booked service allows pick-up/drop-off anywhere in a designated area and provides a possible interchange to a higher-frequency service. - - - - - Flexible area specified as a rectangular bounding box. - - - - - Flexible area specified as a circular area (center coordinates and radius). - - - - - Flexible area specified as a gml:Polygon that consists of an interior and exterior linear ring. - - - - - - - - Distance (metres) as defined by http://www.ordnancesurvey.co.uk/xml/resource/units.xml#metres. ALternative units may be specifed by context. - - - - - - Distance (metres per second) ALternative unist may be specifed by context. - - - - - - Type for absolute bearing. - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG9 Team. + Europe + First drafted for version 1.0 CEN TC278 WG3 SG9 Editor Nicholas Knowles. mailto:schemer@siri.org.uk + + 2004-09-29 + + + 2004-10-01 + + + 2005-02-14 + + + 2005-05-11 + + + 2005-05-04 + + + 2007-03-29 + + + 2012-03-23 + + + + 2012-05-10 + + + +

      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/schema/2.0/xsd/siri_utility/}siri_location.xsd + [ISO 639-2/B] ENG + CEN + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG XML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG9. + + SIRI XML schema. Geo spatial location subschema + Standard +       +       + SIRI Framewrok Location Types. +       + + + + + + + + Longitude from Greenwich. + + + + + + + + + Latitude from equator. + + + + + + + + + Altitude metres from sea level. + + + + + + + + + WGS84 Coordinates. + + + + + Longitude from Greenwich Meridian. -180 (West) to +180 (East). Decimal degrees, e.g. 2.356 + + + + + Latitude from equator. -90 (South) to +90 (North). Decimal degrees, e.g. 56.356 + + + + + Altitude metres from sea level. + + + + + + + Type for GM Coordinates. + + + + + + + + Type for coordinate reference system. + + + + + + GML Spatial coordinate reference system. + + + + + + Type for geospatial Position of a point. May be expressed in concrete WGS 84 Coordinates or any gml compatible point coordinates format. + + + + + + + + + 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. + + + + + + Defines a bounding box using two corner points. GML terminology. +SIRI v2.0 + + + + + Upper Left corner as a geospatial point. + + + + + Lower right corner as a geospatial point. + + + + + + + Defines a line shape +SIRI v2.0 + + + + + A geospatial point. +SIRI v2.0 + + + + + + + Type for a circular area centered around a point that may be expressed in concrete WGS 84 Coordinates or any gml compatible point coordinates format. +SIRI v2.1 + + + + + + + Radius around the center point in meters. + + + + + + + + + Bounding box, circular area or gml:polyon of the area where stops of a flexible service are called. +SIRI v2.1 +A flexible area is used in cases where a pre-booked service allows pick-up/drop-off anywhere in a designated area and provides a possible interchange to a higher-frequency service. + + + + + Flexible area specified as a rectangular bounding box. + + + + + Flexible area specified as a circular area (center coordinates and radius). + + + + + Flexible area specified as a gml:Polygon that consists of an interior and exterior linear ring. + + + + + + + + Distance (metres) as defined by http://www.ordnancesurvey.co.uk/xml/resource/units.xml#metres. ALternative units may be specifed by context. + + + + + + Distance (metres per second) ALternative unist may be specifed by context. + + + + + + Type for absolute bearing. + + + +       diff --git a/xsd/siri_utility/siri_participant.xsd b/xsd/siri_utility/siri_participant.xsd index 73187ac5..18edb961 100644 --- a/xsd/siri_utility/siri_participant.xsd +++ b/xsd/siri_utility/siri_participant.xsd @@ -1,79 +1,79 @@ - - - - - - - main schema - e-service developers - CEN TC278 WG3 SG9 Team. - Europe - First drafted for version 1.0 CEN TC278 WG3 SG9 Editor Nicholas Knowles. mailto:schemer@siri.org.uk - - 2004-09-29 - - - 2007-05-15 - - - 2008-07-015 - - - - 2012-03-22 - - - -

      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/schema/2.0/xsd/siri_utility/}siri_participant.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIGXML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG9. - - SIRI XML schema. Participant type elements. - Standard -       -       - SIRI Framework Participant Types. -       - - - - Type for Unique identifier of participant. - - - - - - Reference to Unique identifier of participant. - - - - - -       + + + + + + + main schema + e-service developers + CEN TC278 WG3 SG9 Team. + Europe + First drafted for version 1.0 CEN TC278 WG3 SG9 Editor Nicholas Knowles. mailto:schemer@siri.org.uk + + 2004-09-29 + + + 2007-05-15 + + + 2008-07-015 + + + + 2012-03-22 + + + +

      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/schema/2.0/xsd/siri_utility/}siri_participant.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIGXML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG9. + + SIRI XML schema. Participant type elements. + Standard +       +       + SIRI Framework Participant Types. +       + + + + Type for Unique identifier of participant. + + + + + + Reference to Unique identifier of participant. + + + + + +       diff --git a/xsd/siri_utility/siri_permissions.xsd b/xsd/siri_utility/siri_permissions.xsd index 6fd10786..c106b82f 100644 --- a/xsd/siri_utility/siri_permissions.xsd +++ b/xsd/siri_utility/siri_permissions.xsd @@ -1,135 +1,135 @@ - - - - - - main schema - e-service developers - CEN TC278 WG3 SG9 Team. - Europe - First drafted for version 2.0 CEN TC278 WG3 SG9 Editor Nicholas Knowles. mailto:schemer@siri.org.uk - - 2012-03-24 - - - 2012-03-23 - - - -

      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/schema/2.0/xsd/siri_utility/}siri_permissions.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_utility.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_uility/siri_participant.xsd - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIGXML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG9. - - SIRI XML schema. Common Permission model subschema. - Standard -       -       - SIRI Framework Permission Types. -       - - - - - - - - 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 Common Access control capabilities. - - - - - Whether access control of requests is supported. Default is 'false'. - - - - - - - - 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. - - - - - - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG9 Team. + Europe + First drafted for version 2.0 CEN TC278 WG3 SG9 Editor Nicholas Knowles. mailto:schemer@siri.org.uk + + 2012-03-24 + + + 2012-03-23 + + + +

      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/schema/2.0/xsd/siri_utility/}siri_permissions.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_utility.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_uility/siri_participant.xsd + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIGXML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, +Rail transport, Roads and road transport + + CEN TC278 WG3 SG9. + + SIRI XML schema. Common Permission model subschema. + Standard +       +       + SIRI Framework Permission Types. +       + + + + + + + + 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 Common Access control capabilities. + + + + + Whether access control of requests is supported. Default is 'false'. + + + + + + + + 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. + + + + + + + + +       diff --git a/xsd/siri_utility/siri_types.xsd b/xsd/siri_utility/siri_types.xsd index a1cd32c6..51813176 100644 --- a/xsd/siri_utility/siri_types.xsd +++ b/xsd/siri_utility/siri_types.xsd @@ -1,166 +1,166 @@ - - - - - - - main schema - e-service developers - Europe - First drafted for version 1.0 CEN TC278 WG3 SG9 Editor Nicholas Knowles. mailto:schemer@siri.org.uk - - 2005-10-03 - - - 2005-10-04 - - - 2005-05-11 - - - 2007-04-17 - - - 2012-03-23 - - - -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri_utility/}siri_types.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIG CML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, - Air transport, Airports, - Ports and maritime transport, Ferries (marine), - Public transport, Bus services, Coach services, Bus stops and stations, - Rail transport, Railway stations and track, Train services, Underground trains, - Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, - Rail transport, Roads and road transport - - CEN TC278 WG3 SG9. - - SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of time types. - Standard -       -       - SIRI Framework Base Types. -       - - - - A string indicating the versioin of a SIRI data structure. - - - - - - 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. - - - - - - 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. - - - - - - Length type for short distances. System for Units can be specified on frame. Normally (metres) as defined by http://www.ordnancesurvey.co.uk/xml/resource/units.xml#metres. - - - - - - Weight type for mass. System for Units can be specified on Frame. Normal default is (kilos) as defined by http://www.ordnancesurvey.co.uk/xml/resource/units.xml#metres. - - - - - - Number of passengers - capacity. - - - - - - Specifies a percentage from 0 to 100. -The value range is normally 0-100, but could in some circumstances go beyond 100%, e.g. when representing the OccupancyPercentage of an over-crowded vehicle or in similar cases. - - - - - -       + + + + + + + main schema + e-service developers + Europe + First drafted for version 1.0 CEN TC278 WG3 SG9 Editor Nicholas Knowles. mailto:schemer@siri.org.uk + + 2005-10-03 + + + 2005-10-04 + + + 2005-05-11 + + + 2007-04-17 + + + 2012-03-23 + + + +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/siri_utility/}siri_types.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG CML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, + Air transport, Airports, + Ports and maritime transport, Ferries (marine), + Public transport, Bus services, Coach services, Bus stops and stations, + Rail transport, Railway stations and track, Train services, Underground trains, + Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, + Rail transport, Roads and road transport + + CEN TC278 WG3 SG9. + + SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of time types. + Standard +       +       + SIRI Framework Base Types. +       + + + + A string indicating the versioin of a SIRI data structure. + + + + + + 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. + + + + + + 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. + + + + + + Length type for short distances. System for Units can be specified on frame. Normally (metres) as defined by http://www.ordnancesurvey.co.uk/xml/resource/units.xml#metres. + + + + + + Weight type for mass. System for Units can be specified on Frame. Normal default is (kilos) as defined by http://www.ordnancesurvey.co.uk/xml/resource/units.xml#metres. + + + + + + Number of passengers - capacity. + + + + + + Specifies a percentage from 0 to 100. +The value range is normally 0-100, but could in some circumstances go beyond 100%, e.g. when representing the OccupancyPercentage of an over-crowded vehicle or in similar cases. + + + + + +       diff --git a/xsd/siri_utility/siri_utility.xsd b/xsd/siri_utility/siri_utility.xsd index db5cfaee..26b81dbd 100644 --- a/xsd/siri_utility/siri_utility.xsd +++ b/xsd/siri_utility/siri_utility.xsd @@ -1,301 +1,301 @@ - - - - - - - main schema - e-service developers - CEN TC278 WG3 SG9 Team. - Europe - First drafted for version 1.0 CEN TC278 WG3 SG9 Editor Nicholas Knowles. mailto:schemer@siri.org.uk - - 2008-09-307 - - - - 2007-04-17 - - -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri_utiliyty/}siri_utility.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIGXML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG9. - - SIRI XML schema. Shared utility types - Standard -       -       - SIRI Framework Utility Types. -       - - - - - - A type with no allowed content, used when simply the presence of an element is significant. - - - - - - - - - Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). - - - - - Type for Extensions to schema. Wraps an 'any' tag to ensure decidability. - - - - - Placeholder for user extensions. - - - - - - - - A list of alternative Key values for an element. +SIRI v2.1 - - - - Every Key Value Pair must be unique. - - - - - - - - - Type for a Key List. +SIRI v2.1 - - - - - Key value pair for Entity. - - - - - - - Type for a Key List. +SIRI v2.1 - - - - - Identifier of value e.g. System. - - - - - Value for alternative key. - - - - - Identifier of type of key. - - - - - - - - VALUE SETs and TYPE OF VALUEs as part of the SIRI extension model. -TYPES OF VALUE can be used to exchange metadata for validation or collection of data, -such as the description and allowed values for codes. +SIRI v2.1 - - - - VALUE SETs must be unique. - - - - - - - - Type for containment of VALUE SETs and/or TYPE OF VALUEs. +SIRI v2.1 - - - - - - - - - A code value from an extensible set which may be added to by user applications, and is used to classify other SIRI entities. +SIRI v2.1 - - - - - Type for a TYPE OF VALUE. Used to define open classifications of value types. +SIRI v2.1 - - - - - Identifier of a TYPE OF VALUE. - - - - - Name of class of which TypeOfValue is an instance. - - - - - - - - Elements for TYPE OF VALUE. +SIRI v2.1 - - - - - Name of TYPE OF VALUE. - - - - - Short Name for TYPE OF VALUE. - - - - - Description of TYPE OF VALUE. - - - - - Default image for TYPE OF VALUE. - - - - - Default URL for TYPE OF VALUE. - - - - - Arbitrary code (usually the technical part of the identifier). - - - - - - - An extensible set of code values which may be added to by user applications and is used to validate the properties of entities. -Contains TYPE OF VALUEs that are an instance of the same class. +SIRI v2.1 - - - - TYPE OF VALUEs of the set must be unique. - - - - - - - - Type for a VALUE SET. Used to define open classifications of value types. +SIRI v2.1 - - - - - Identifier of VALUE SET. - - - - - Name of Class of values in set. - - - - - - - - Elements for VALUE SET. +SIRI v2.1 - - - - - Name of set. - - - - - Values in set. - - - - - - - Type for a list of TYPE OF VALUEs. +SIRI v2.1 - - - - - - - - - Type for identifier of a TYPE OF VALUE. +SIRI v2.1 - - - - - - Type for reference to a TYPE OF VALUE. +SIRI v2.1 - - - - - - - - Type for identifier of a VALUE SET. +SIRI v2.1 - - - - - - Name of class of which TypeOfValue is an instance. Used for reflection. +SIRI v2.1 - - - - -       + + + + + + + main schema + e-service developers + CEN TC278 WG3 SG9 Team. + Europe + First drafted for version 1.0 CEN TC278 WG3 SG9 Editor Nicholas Knowles. mailto:schemer@siri.org.uk + + 2008-09-307 + + + + 2007-04-17 + + +

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

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

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

      -

      This sub-schema describes the Vehicle Monitoring Service.

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/}siri_vehicleMonitoring_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_reference.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions.xsd - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport, Ports and maritime transport, Public transport, -Rail transport, Roads and road transport - - CEN TC278 WG3 SG7 - - SIRI-VM XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Vehicle Monitoring Subschema - Standard -       -       - SIRI-VM Vehicle Monitoring Service. -       - - - - - - - - Convenience artifact to pick out main elements of the Vehicle Monitoring Service. - - - - - - - - - - - - - - - - Request for information about Vehicle Movements. - - - - - Type for Functional Service Request for Vehicle Monitoring Service. - - - - - - - - - - - Version number of request. Fixed - - - - - - - - - Detail Levels for Request. - - - - - Return only the minimum amount of optional data for each stop event to provide a display, A time, line name and destination name. - - - - - Return minimum and other available basic details for each stop event. Do not include data on time at next stop or destination. - - - - - Return all basic data, and also arrival times at DESTINATION. - - - - - Return all available data for each stop event, including previous and onward CALLs with passing times for JOURNEY PATTERN. - - - - - - - Parameters that specify the content to be returned. - - - - - A predefined scope for making VEHICLE requests. - - - - - - Reference to a specific VEHICLE about which data is requested. - - - - - Filter the results to include only vehicles for the specific LINE. - - - - - - Filter the results to include only VEHICLEs going to this DIRECTION. - - - - - - - Parameters that affect the request processing. - - - - - Preferred languages in which to return text values. - - - - - - The maximum number of MONITORED VEHICLE JOURNEYs to include in a given delivery. The most recent n Events within the look ahead window are included. - - - - - Level of detail to include in response. - - - - - If calls are to be returned, maximum number of calls to include in response. If absent, exclude all calls. +SIRI v2.0. - - - - - - Maximum number of previous calls to include. Only applies if VehicleMonitoringDetailLevel of Calls specified. Zero for none. If VehicleMonitoringDetailLevel of Calls specified but MaximumNumberOfCalls.Previous absent, include all previous calls. +SIRI v2.0. - - - - - Maximum number of onwards calls to include. Zero for none. Only applies if VehicleMonitoringDetailLevel of 'calls' specified. Zero for none. If VehicleMonitoringDetailLevel calls specified but MaximumNumberOfCalls.Onwards absent, include all onwards calls. +SIRI v2.0. - - - - - - - - Whether any related Situations should be included in the ServiceDelivery. Default is 'false'. +SIRI v2.0 - - - - - - - - Request for a subscription to the Vehicle Monitoring Service. - - - - - Parameters that affect the subscription publishing and notification processing. - - - - - Whether the producer will return the complete set of current data, or only provide updates to this data, i.e. additions, modifications and deletions. -If false or omitted, each subscription response will contain the full information as specified in this request. - - - - - - The amount of change to the VEHICLE expected arrival time at next stop that can happen before an update is sent (i.e. if ChangeBeforeUpdate is set to 2 minutes, the subscriber will not be told that a bus is 30 seconds delayed - an update will only be sent when the bus is at least 2 minutes delayed). - - - - - Time interval in seconds in which new data is to be transmitted. If unspecified, default to system configuration. - - - - - - - - Type for Subscription Request for Vehicle Monitoring Service. - - - - - - - - - - - - - - - - Delivery for Vehicle Monitoring Service. - - - - - Payload part of Vehicle Monitoring delivery. - - - - - Describes the progress of a VEHICLE along its route. - - - - - Reference to an previously communicated VEHICLE activity which should now be removed from the system. - - - - - Annotation to accompany of Vehicle Activities. - - - - - - - Type for Delivery for Vehicle Monitoring Service. Provides information about one or more vehicles; each has its own VEHICLE activity element. - - - - - - - - - - Version number of response. Fixed - - - - - - - - - - Type for a Vehicle Activity. - - - - - - - Time until when data is valid. - - - - - Reference to monitored VEHICLE or GROUP OF VEHICLEs. - - - - - Name associated with Monitoring Reference. Supports SIRI LITE servcies (+SIRI v2.0). - - - - - Provides information about the progress of the VEHICLE along its current link, that is link from previous visited top to current position. - - - - - Monitored VEHICLE JOURNEY that VEHICLE is following. - - - - - - - - - - Text associated with Delivery. - - - - - - - - - - Identifier of a Vehicle Monitoring scope. - - - - - - Type for reference to a Vehicle Monitoring scope - - - - - - - - - Type for cancellation of an earlier Vehicle Activity. - - - - - - - - - Reason for cancellation. (Unbounded since SIRI 2.0) - - - - - - - - - - Identifiers of Vehicle Activity. - - - - - - Reference to VEHICLE JOURNEY that VEHICLE is making. - - - - - - - - - Type for Deliveries for VEHICLE monitoring services Used in WSDL. - - - - - Delivery for Vehicle Moniroting Service. - - - - - - - - Request for information about Vehicle Monitoring Service Capabilities. Answered with a VehicleMontoringCapabilitiesResponse. - - - - - Type for capability request policy. - - - - - - - Whether results should return references. - - - - - Whether results should return references. - - - - - - - - - Capabilities of Vehicle Monitoring Service. - - - - - - Capabilities for Vehicle Monitoring Service. Answers a VehicleMontoringCapabilitiesRequest. - - - - - Type for Delivery for Vehicle Monitoring Service. - - - - - - - - - - - Version number of response. Fixed - - - - - - - - - Type for Vehicle Monitoring Capabilities. - - - - - - - Topic Filtering Capabilities. - - - - - - Default preview interval. Default is 60 minutes. - - - - - Whether results can be filtered by Vehicle Monitoring Fixed as 'true'. - - - - - - - - - - - Request Policy capabilities. - - - - - - - - - - - - - - Subscription Policy capabilities. - - - - - Optional Access control capabilities. - - - - - - - - - - If access control is supported, whether access control by monitoring point is supported. Default is 'true'. - - - - - - - - - - Optional Response capabilities. - - - - - - Whether result has location. Default is 'true'. - - - - - Whether result supports SITUATION REFERENCESs. Default is 'false'. +SIRI v2.0 - - - - - - - - - - - - - Elements for volume control. - - - - - Whether Detail level filtering is supported. Default is ' false'. - - - - - Detail level. Default Normal. - - - - - Whether results can be limited to a maximum number. Default is 'true'. - - - - - If system can return detailed calling pattern, whether a number of calls to include can be specified. Default is 'false'. +SIRI 2.0 - - - - - If system can return detailed calling pattern, whether a number of onwards calls to include can be specified. Default is 'false'. +SIRI 2.0 - - - - - If system can return detailed calling pattern, whether a number of previous calls to include can be specified. Default is 'false'. +SIRI 2.0 - - - - - - - Participant's permissions to use the service. - - - - - - - - Permissions for use of VEHICLE MONITORING. Can be used to specify which Consumers can see which vehicles - - - - - - - - - - - Type for Monitoring Service Permissions. - - - - - - - - - The Vehicle Monitors (DIUSPLAY ASSIGNMENTs) that the participant may access. - - - - - - - Participant's permission for this Vehicle Monitor (DISPLAY SSIGNMENT). - - - - - - - - - - - - - Type for MonitoringPoint Permission. - - - - - - - Vehicle Monitoring reference for which permission is made. - - - - - - -       + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2004-09-29 + + + 2004-10-01 + + + 2005-02-14 + + + 2005-02-20 + + + 2005-05-11 + + + 2007-04-17 + + + + 2007-03-26 + + + + 2008-11-17 + + + + 2012-03-23 + + + + 2012-04-29 + + + + 2013-02-11 + + + +

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

      +

      This sub-schema describes the Vehicle Monitoring Service.

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

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

      -

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

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

      -

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

      -

      SIRI includes common mechanisms and messages for system status management.

      -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0}siri.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/siri_wsCOnsumer-Document.wsdl - - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, -Rail transport, Roads and road transport. - - CEN TC278 WG3 SG7 - - XSD elements for WSDL Consumer (Document Wrapped style) interface for SIRI XML schema. Service Interface for Real Time Information relating to Public Transport Operations. - Standard -       -       -       - - - - Type for Heartbeat Notifcation - - - - - - - - - - - - Type for Data Ready Notication - - - - - - - - - - - Type for TerminateSubscription Notication - - - - - - -       + + + + + + + main schema + e-service developers + Christophe Duquesne, Aurige, Guyancourt FRANCE + Michel Etienne, Cityway, Paris FRANCE + Robin Vettier, RATP, Paris FRANCE + Nicholas Knowles, KIZOOM LTD., London EC4A 1LT + Europe + >Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Christophe Duquesne, Aurige + + 2012-05-29 + + +

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

      +

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

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

      +

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

      +

      SIRI includes common mechanisms and messages for system status management.

      +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0}siri.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/siri_wsCOnsumer-Document.wsdl + + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG XML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, +Rail transport, Roads and road transport. + + CEN TC278 WG3 SG7 + + XSD elements for WSDL Consumer (Document Wrapped style) interface for SIRI XML schema. Service Interface for Real Time Information relating to Public Transport Operations. + Standard +       +       +       + + + + Type for Heartbeat Notifcation + + + + + + + + + + + + Type for Data Ready Notication + + + + + + + + + + + Type for TerminateSubscription Notication + + + + + + +       diff --git a/xsd/wsdl_model/siri_wsConsumer-Services.xsd b/xsd/wsdl_model/siri_wsConsumer-Services.xsd index 4e9cd132..b46e9dd3 100644 --- a/xsd/wsdl_model/siri_wsConsumer-Services.xsd +++ b/xsd/wsdl_model/siri_wsConsumer-Services.xsd @@ -1,155 +1,155 @@ - - - - - - - main schema - e-service developers - Christophe Duquesne, Aurige, Guyancourt FRANCE - Michel Etienne, Cityway, Paris FRANCE - Robin Vettier, RATP, Paris FRANCE - Nicholas Knowles, KIZOOM LTD., London EC4A 1LT - Europe - >Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Christophe Duquesne, Aurige - - 2012-05-29 - - -

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

      -

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

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

      -

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

      -

      SIRI includes common mechanisms and messages for system status management.

      -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0}siri.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/siri_wsCOnsumer-Document.wsdl - - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, -Rail transport, Roads and road transport. - - CEN TC278 WG3 SG7 - - XSD elements for WSDL Consumer (Document Wrapped style) interface for SIRI XML schema. Service Interface for Real Time Information relating to Public Transport Operations. - Standard -       -       -       - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -       + + + + + + + main schema + e-service developers + Christophe Duquesne, Aurige, Guyancourt FRANCE + Michel Etienne, Cityway, Paris FRANCE + Robin Vettier, RATP, Paris FRANCE + Nicholas Knowles, KIZOOM LTD., London EC4A 1LT + Europe + >Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Christophe Duquesne, Aurige + + 2012-05-29 + + +

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

      +

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

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

      +

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

      +

      SIRI includes common mechanisms and messages for system status management.

      +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0}siri.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/siri_wsCOnsumer-Document.wsdl + + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG XML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, +Rail transport, Roads and road transport. + + CEN TC278 WG3 SG7 + + XSD elements for WSDL Consumer (Document Wrapped style) interface for SIRI XML schema. Service Interface for Real Time Information relating to Public Transport Operations. + Standard +       +       +       + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +       diff --git a/xsd/wsdl_model/siri_wsProducer-DiscoveryCapability.xsd b/xsd/wsdl_model/siri_wsProducer-DiscoveryCapability.xsd index e49acf1f..304b05c6 100644 --- a/xsd/wsdl_model/siri_wsProducer-DiscoveryCapability.xsd +++ b/xsd/wsdl_model/siri_wsProducer-DiscoveryCapability.xsd @@ -1,123 +1,123 @@ - - - - - - - main schema - e-service developers - Christophe Duquesne, Aurige, Guyancourt FRANCE - Michel Etienne, Cityway, Paris FRANCE - Robin Vettier, RATP, Paris FRANCE - Nicholas Knowles, KIZOOM LTD., London EC4A 1LT - Europe - >Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Christophe Duquesne, Aurige - - 2012-05-29 - - -

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

      -

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

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

      -

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

      -

      SIRI includes common mechanisms and messages for system status management.

      -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0}siri.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/siri_wsCOnsumer-Document.wsdl - - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, -Rail transport, Roads and road transport. - - CEN TC278 WG3 SG7 - - XSD elements for WSDL Consumer (Document Wrapped style) interface for SIRI XML schema. Service Interface for Real Time Information relating to Public Transport Operations. - Standard -       -       -       - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -       + + + + + + + main schema + e-service developers + Christophe Duquesne, Aurige, Guyancourt FRANCE + Michel Etienne, Cityway, Paris FRANCE + Robin Vettier, RATP, Paris FRANCE + Nicholas Knowles, KIZOOM LTD., London EC4A 1LT + Europe + >Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Christophe Duquesne, Aurige + + 2012-05-29 + + +

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

      +

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

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

      +

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

      +

      SIRI includes common mechanisms and messages for system status management.

      +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0}siri.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/siri_wsCOnsumer-Document.wsdl + + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG XML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, +Rail transport, Roads and road transport. + + CEN TC278 WG3 SG7 + + XSD elements for WSDL Consumer (Document Wrapped style) interface for SIRI XML schema. Service Interface for Real Time Information relating to Public Transport Operations. + Standard +       +       +       + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +       diff --git a/xsd/wsdl_model/siri_wsProducer-Framework.xsd b/xsd/wsdl_model/siri_wsProducer-Framework.xsd index d9b7dc1d..64f1375f 100644 --- a/xsd/wsdl_model/siri_wsProducer-Framework.xsd +++ b/xsd/wsdl_model/siri_wsProducer-Framework.xsd @@ -1,138 +1,138 @@ - - - - - - - main schema - e-service developers - Christophe Duquesne, Aurige, Guyancourt FRANCE - Michel Etienne, Cityway, Paris FRANCE - Robin Vettier, RATP, Paris FRANCE - Nicholas Knowles, KIZOOM LTD., London EC4A 1LT - Europe - >Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Christophe Duquesne, Aurige - - 2012-05-29 - - -

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

      -

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

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

      -

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

      -

      SIRI includes common mechanisms and messages for system status management.

      -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0}siri.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/siri_wsCOnsumer-Document.wsdl - - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, -Rail transport, Roads and road transport. - - CEN TC278 WG3 SG7 - - XSD elements for WSDL Consumer (Document Wrapped style) interface for SIRI XML schema. Service Interface for Real Time Information relating to Public Transport Operations. - Standard -       -       -       - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -       + + + + + + + main schema + e-service developers + Christophe Duquesne, Aurige, Guyancourt FRANCE + Michel Etienne, Cityway, Paris FRANCE + Robin Vettier, RATP, Paris FRANCE + Nicholas Knowles, KIZOOM LTD., London EC4A 1LT + Europe + >Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Christophe Duquesne, Aurige + + 2012-05-29 + + +

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

      +

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

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

      +

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

      +

      SIRI includes common mechanisms and messages for system status management.

      +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0}siri.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/siri_wsCOnsumer-Document.wsdl + + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG XML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, +Rail transport, Roads and road transport. + + CEN TC278 WG3 SG7 + + XSD elements for WSDL Consumer (Document Wrapped style) interface for SIRI XML schema. Service Interface for Real Time Information relating to Public Transport Operations. + Standard +       +       +       + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +       diff --git a/xsd/wsdl_model/siri_wsProducer-Services.xsd b/xsd/wsdl_model/siri_wsProducer-Services.xsd index 67c9fbf1..bfcaf85f 100644 --- a/xsd/wsdl_model/siri_wsProducer-Services.xsd +++ b/xsd/wsdl_model/siri_wsProducer-Services.xsd @@ -1,263 +1,263 @@ - - - - - - - main schema - e-service developers - Christophe Duquesne, Aurige, Guyancourt FRANCE - Michel Etienne, Cityway, Paris FRANCE - Robin Vettier, RATP, Paris FRANCE - Nicholas Knowles, KIZOOM LTD., London EC4A 1LT - Europe - >Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Christophe Duquesne, Aurige - - 2012-05-29 - - -

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

      -

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

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

      -

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

      -

      SIRI includes common mechanisms and messages for system status management.

      -

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

      -       - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0}siri.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/siri_wsCOnsumer-Document.wsdl - - - - CEN, VDV, RTIG 2004-2021 - - -
        -
      • Derived from the VDV, RTIG XML and Trident standards.
        • -
      - - Version 2.1 - - Arts, recreation and travel, Tourism, Travel (tourism), Transport, -Air transport, Airports, -Ports and maritime transport, Ferries (marine), -Public transport, Bus services, Coach services, Bus stops and stations, -Rail transport, Railway stations and track, Train services, Underground trains, -Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, -Rail transport, Roads and road transport. - - CEN TC278 WG3 SG7 - - XSD elements for WSDL Consumer (Document Wrapped style) interface for SIRI XML schema. Service Interface for Real Time Information relating to Public Transport Operations. - Standard -       -       -       - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -       + + + + + + + main schema + e-service developers + Christophe Duquesne, Aurige, Guyancourt FRANCE + Michel Etienne, Cityway, Paris FRANCE + Robin Vettier, RATP, Paris FRANCE + Nicholas Knowles, KIZOOM LTD., London EC4A 1LT + Europe + >Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Christophe Duquesne, Aurige + + 2012-05-29 + + +

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

      +

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

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

      +

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

      +

      SIRI includes common mechanisms and messages for system status management.

      +

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

      +       + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0}siri.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/siri_wsCOnsumer-Document.wsdl + + + + CEN, VDV, RTIG 2004-2021 + + +
        +
      • Derived from the VDV, RTIG XML and Trident standards.
        • +
      + + Version 2.1 + + Arts, recreation and travel, Tourism, Travel (tourism), Transport, +Air transport, Airports, +Ports and maritime transport, Ferries (marine), +Public transport, Bus services, Coach services, Bus stops and stations, +Rail transport, Railway stations and track, Train services, Underground trains, +Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, +Rail transport, Roads and road transport. + + CEN TC278 WG3 SG7 + + XSD elements for WSDL Consumer (Document Wrapped style) interface for SIRI XML schema. Service Interface for Real Time Information relating to Public Transport Operations. + Standard +       +       +       + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +       diff --git a/xsd/xml/2008/09/xsd.xsl b/xsd/xml/2008/09/xsd.xsl index 6c3b7fcd..cacffdb9 100644 --- a/xsd/xml/2008/09/xsd.xsl +++ b/xsd/xml/2008/09/xsd.xsl @@ -1,997 +1,997 @@ - - - - - - - - - - - - - - - ]> - - - - - - - - - - - - - - - - - - - - - Schema document for - - - namespace - - - - unspecified namespace - - - - - - - - - - - - - - text/css - .bodytext .bodytext { - margin-left: 0; - margin-right: 0; - } - .bodytext { - margin-left: 15%; - margin-right: 2%; - } - .annotation { - - - } - .same-ns { - color: Green; - } - .diff-ns { - color: maroon; - } - .warning { - color: red; - } - p.note { - font-style: italic; - } - p.dt { - font-weight: bold; - } - span.rfc { - font-variant: small-caps; - } - - - - - - - - * * - - - - - - - - - - - bodytext - - - - - - - - - - - - - - - - - - - - - - annotation - - - - - - Annotation - - - - - - - - bodytext - - - - - - - - - - - - - - ! Unrecognized children in xs:documentation element - - - - - - - - - - - - - - - - - - - - - - -   - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - bodytext - - - - - Notes - - - - - External documentation at - - - - - - - - - - - - - - - Formal declaration in XSD source form - - - - - - - - - - - - - - - - - - - - - - - - - - - - - < - - - - - break - nobreak - - - - - - - - - - - > - - </ - - > - - /> - - - - - - - - - nobreak - - - - - - - - - - - - - - - - - - - - - - - =" - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - " - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Warning: not matched. - - warning - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - external-link same-ns - - - - - - external-link diff-ns - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - attnames - - - - - - attvals - - - - - - - - - - - - - - - - - - unknown - - - - - - - - 0 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + ]> + + + + + + + + + + + + + + + + + + + + + Schema document for + + + namespace + + + + unspecified namespace + + + + + + + + + + + + + + text/css + .bodytext .bodytext { + margin-left: 0; + margin-right: 0; + } + .bodytext { + margin-left: 15%; + margin-right: 2%; + } + .annotation { + + + } + .same-ns { + color: Green; + } + .diff-ns { + color: maroon; + } + .warning { + color: red; + } + p.note { + font-style: italic; + } + p.dt { + font-weight: bold; + } + span.rfc { + font-variant: small-caps; + } + + + + + + + + * * + + + + + + + + + + + bodytext + + + + + + + + + + + + + + + + + + + + + + annotation + + + + + + Annotation + + + + + + + + bodytext + + + + + + + + + + + + + + ! Unrecognized children in xs:documentation element + + + + + + + + + + + + + + + + + + + + + + +   + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + bodytext + + + + + Notes + + + + + External documentation at + + + + + + + + + + + + + + + Formal declaration in XSD source form + + + + + + + + + + + + + + + + + + + + + + + + + + + + + < + + + + + break + nobreak + + + + + + + + + + + > + + </ + + > + + /> + + + + + + + + + nobreak + + + + + + + + + + + + + + + + + + + + + + + =" + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + " + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Warning: not matched. + + warning + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + external-link same-ns + + + + + + external-link diff-ns + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + attnames + + + + + + attvals + + + + + + + + + + + + + + + + + + unknown + + + + + + + + 0 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/xsd/xml/2009/01/XMLSchema.xsd b/xsd/xml/2009/01/XMLSchema.xsd index 27c60c08..b5baeb33 100644 --- a/xsd/xml/2009/01/XMLSchema.xsd +++ b/xsd/xml/2009/01/XMLSchema.xsd @@ -1,286 +1,286 @@ - - - - - - -
      -

      About the XML namespace

      - -
      -

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

      -

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

      -

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

      -

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

      -
      -
      -       -       - - - - -
      - -

      lang (as an attribute name)

      -

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

      - -
      -
      -

      Notes

      -

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

      -

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

      -

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

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

      space (as an attribute name)

      -

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

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

      base (as an attribute name)

      -

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

      - -

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

      -
      -       -       -       - - - - -
      - -

      id (as an attribute name)

      -

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

      - -

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

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

      Father (in any context at all)

      - -
      -

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

      -
      -

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

      -
      -
      -
      -       -       - - - -
      -

      About this schema document

      - -
      -

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

      -

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

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

      - or -

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

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

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

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

      -
      -
      -       -       - - - -
      -

      Versioning policy for this schema document

      -
      -

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

      -

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

      -

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

      -

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

      - -
      -
      -       -       - -       + + + + + + +
      +

      About the XML namespace

      + +
      +

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

      +

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

      +

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

      +

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

      +
      +
      +       +       + + + + +
      + +

      lang (as an attribute name)

      +

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

      + +
      +
      +

      Notes

      +

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

      +

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

      +

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

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

      space (as an attribute name)

      +

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

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

      base (as an attribute name)

      +

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

      + +

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

      +
      +       +       +       + + + + +
      + +

      id (as an attribute name)

      +

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

      + +

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

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

      Father (in any context at all)

      + +
      +

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

      +
      +

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

      +
      +
      +
      +       +       + + + +
      +

      About this schema document

      + +
      +

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

      +

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

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

      + or +

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

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

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

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

      +
      +
      +       +       + + + +
      +

      Versioning policy for this schema document

      +
      +

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

      +

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

      +

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

      +

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

      + +
      +
      +       +       + +       From 9a3b3f4f362a6106086573afd217860b9b184efb Mon Sep 17 00:00:00 2001 From: u215619 Date: Thu, 8 Apr 2021 14:04:30 +0200 Subject: [PATCH 265/290] DATEXII set to version 2.0 missing comments for JAXB in AppInfo elements --- xsd/datex2/DATEXIISchema.xsd | 2 +- xsd/datex2/DATEXIISchemaWithDefinitions.xsd | 2 +- xsd/ifopt/ifopt_location.xsd | 4 ++-- xsd/ifopt/ifopt_stop.xsd | 4 ++-- xsd/siri.xsd | 26 ++++++++++----------- xsd/siri_model/siri_interchangeJourney.xsd | 2 +- 6 files changed, 20 insertions(+), 20 deletions(-) diff --git a/xsd/datex2/DATEXIISchema.xsd b/xsd/datex2/DATEXIISchema.xsd index 86819714..a26f54ac 100644 --- a/xsd/datex2/DATEXIISchema.xsd +++ b/xsd/datex2/DATEXIISchema.xsd @@ -1,5 +1,5 @@ - + diff --git a/xsd/datex2/DATEXIISchemaWithDefinitions.xsd b/xsd/datex2/DATEXIISchemaWithDefinitions.xsd index 7149d081..e201e2ba 100644 --- a/xsd/datex2/DATEXIISchemaWithDefinitions.xsd +++ b/xsd/datex2/DATEXIISchemaWithDefinitions.xsd @@ -1,5 +1,5 @@ - + A traffic condition which is not normal. diff --git a/xsd/ifopt/ifopt_location.xsd b/xsd/ifopt/ifopt_location.xsd index 9081a640..4bc0d688 100644 --- a/xsd/ifopt/ifopt_location.xsd +++ b/xsd/ifopt/ifopt_location.xsd @@ -14,13 +14,13 @@ 2006-09-22 2007-03-22 - 2007 03 23 Revise projections + 2007-06-12 2011-04-19 - Correct siri: namespace +

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

      diff --git a/xsd/ifopt/ifopt_stop.xsd b/xsd/ifopt/ifopt_stop.xsd index 87325769..7c2def98 100644 --- a/xsd/ifopt/ifopt_stop.xsd +++ b/xsd/ifopt/ifopt_stop.xsd @@ -17,10 +17,10 @@ 2007-03-29 2012-03-12 - Change IdentifertYpe to normalizedString + 2018-11-13 - [vdv] Enum "ferrytPort" in StopPlaceTypeEnumeration changed to "ferryPort" +

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

      diff --git a/xsd/siri.xsd b/xsd/siri.xsd index 3a41b38c..e495ed0e 100644 --- a/xsd/siri.xsd +++ b/xsd/siri.xsd @@ -69,35 +69,35 @@ mailto:schemer@siri.org.uk 2007-02-02 2007-04-17 - Name Space changes + 2008-11-17 - Change to use common 1_2. Add in mussing StopMonitoringMultipelRequest - Rename groups to identify common SIRI elements + 2009-03-03 - Corrrect cardinality on facility and Service Monitoring Delivery request + 2011-04-18 - Updated journey, request and other subpackages - see readme + 2012-03-23 - SIRI Version 2.0 + 2012-05-18 - SIRI Version 2.0 - Correct error in SituationExchangeCapabilitiesReponse include + 2012-08-01 - SIRI Version 2.0 - Correct delegation elements + 2014-03-31 - +SIRI v2.0 Comments - - Add terminate subscription notification +

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

      diff --git a/xsd/siri_model/siri_interchangeJourney.xsd b/xsd/siri_model/siri_interchangeJourney.xsd index 1b949ab1..b4d1808f 100644 --- a/xsd/siri_model/siri_interchangeJourney.xsd +++ b/xsd/siri_model/siri_interchangeJourney.xsd @@ -11,7 +11,7 @@ Europe Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk 2012-03-29 - Factored out of conection timnetable servcie + 2012-03-20 +SIRI v2.0 From adef34f6da1889be60ddc04caec6754aa313e7ba Mon Sep 17 00:00:00 2001 From: u215619 Date: Tue, 20 Apr 2021 15:18:01 +0200 Subject: [PATCH 266/290] DATEXII compability additions for UmS included This changes were included previously in V1 file which was deleted in the meantime because no longer in use. --- xsd/datex2/DATEXIISchema.xsd | 3 +++ xsd/datex2/DATEXIISchemaWithDefinitions.xsd | 15 +++++++++++++++ xsd/siri_model/siri_situation.xsd | 12 ++++++------ xsd/siri_model/siri_situationAffects.xsd | 2 +- 4 files changed, 25 insertions(+), 7 deletions(-) diff --git a/xsd/datex2/DATEXIISchema.xsd b/xsd/datex2/DATEXIISchema.xsd index a26f54ac..2fb16df8 100644 --- a/xsd/datex2/DATEXIISchema.xsd +++ b/xsd/datex2/DATEXIISchema.xsd @@ -2641,14 +2641,17 @@ + + + diff --git a/xsd/datex2/DATEXIISchemaWithDefinitions.xsd b/xsd/datex2/DATEXIISchemaWithDefinitions.xsd index e201e2ba..9fbab2b3 100644 --- a/xsd/datex2/DATEXIISchemaWithDefinitions.xsd +++ b/xsd/datex2/DATEXIISchemaWithDefinitions.xsd @@ -8284,6 +8284,11 @@ A station dedicated to the monitoring of the road network by processing microwave information.       + + + Value was added in SIRI 2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. See also 'microwaveMonitoringStation' + + A caller using a mobile telephone (who may or may not be on the road network). @@ -8294,6 +8299,11 @@ Emergency service patrols other than police. + + + Value was added in SIRI 2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. See also 'nonPoliceEmergencyServicePatrol' + + Other sources of information. @@ -8324,6 +8334,11 @@ A motorist who is an officially registered observer. + + + Value was added in SIRI 2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. See also 'registeredMotoristObserver' + + A road authority. diff --git a/xsd/siri_model/siri_situation.xsd b/xsd/siri_model/siri_situation.xsd index 5ac25271..88f8f904 100644 --- a/xsd/siri_model/siri_situation.xsd +++ b/xsd/siri_model/siri_situation.xsd @@ -159,7 +159,7 @@ Rail transport, Roads and road transport - Time at which SITUATION element was versioned. Once versioned, no furtr changes can be made. + Time at which SITUATION element was versioned. Once versioned, no further changes can be made.       @@ -1235,7 +1235,7 @@ Note: this means that ReasonName is NOT a complete message, but only a (few) wor       - Condition(s) of effect of disruptione. + Condition(s) of effect of disruptions. @@ -1316,12 +1316,12 @@ Note: this means that ConditionName is NOT a complete message, but only a (few) - Type of boarding and alighting allowed at stop. Default is 'Alighting'. + Type of alighting allowed at stop. Default is 'Alighting'. - Type of alighting allowed at stop. Default is 'Boarding'. + Type of boarding allowed at stop. Default is 'Boarding'. @@ -1456,12 +1456,12 @@ Alternatively, AdviceRef can be used to reference a (complete) standardised advi - Whether information about parts of the network identified by Affects should be blocked from computation made by a Journey Planner that has a real-tiem feed of the SITUATIONs. Default is 'false'; do not suppress. + Whether information about parts of the network identified by Affects should be blocked from computation made by a Journey Planner that has a real-time feed of the SITUATIONs. Default is 'false'; do not suppress. - Whether information about parts of the network identified by Affects should be blocked from real-time departureinfo systems. Default is 'false'; do not suppress. + Whether information about parts of the network identified by Affects should be blocked from real-time departure info systems. Default is 'false'; do not suppress. diff --git a/xsd/siri_model/siri_situationAffects.xsd b/xsd/siri_model/siri_situationAffects.xsd index c6e34943..e1fccfc9 100644 --- a/xsd/siri_model/siri_situationAffects.xsd +++ b/xsd/siri_model/siri_situationAffects.xsd @@ -883,7 +883,7 @@ Rail transport, Roads and road transport - Origin SCHEDULED STOP POINTs from which the LINE runs. [equivalent to pti15 1 start_point route_description_type] + Restricts the affected scope to the specified ORIGINs from which the LINE runs. [equivalent to pti15 1 start_point route_description_type] From 20d48b756f73f042631810ddc5e1d0bff5a61f59 Mon Sep 17 00:00:00 2001 From: u215619 Date: Tue, 20 Apr 2021 16:31:31 +0200 Subject: [PATCH 267/290] CR-090 fix annotation boarding / new value in AdviceType --- xsd/siri_model/siri_journey.xsd | 2 +- xsd/siri_model/siri_situation.xsd | 9 +++++++-- 2 files changed, 8 insertions(+), 3 deletions(-) diff --git a/xsd/siri_model/siri_journey.xsd b/xsd/siri_model/siri_journey.xsd index b4335f26..8284d2b8 100644 --- a/xsd/siri_model/siri_journey.xsd +++ b/xsd/siri_model/siri_journey.xsd @@ -959,7 +959,7 @@ Inheritable property. Can be omitted if the same as the DeparturePlatformName If - Type of boarding and alighting allowed at stop. Default is 'Alighting'. + Type of alighting allowed at stop. Default is 'Alighting'. diff --git a/xsd/siri_model/siri_situation.xsd b/xsd/siri_model/siri_situation.xsd index 88f8f904..894a78b6 100644 --- a/xsd/siri_model/siri_situation.xsd +++ b/xsd/siri_model/siri_situation.xsd @@ -1441,9 +1441,14 @@ Alternatively, AdviceRef can be used to reference a (complete) standardised advi no advice - + + + take detour + + + - TPEG Pts39_255, undefined advice + change accessibility From 283be7bf1898e59d07b937b7d1cc9b4da7576a8c Mon Sep 17 00:00:00 2001 From: u215619 Date: Wed, 21 Apr 2021 13:40:43 +0200 Subject: [PATCH 268/290] upper case of some transmodel objects --- xsd/acsb/acsb_accessibility.xsd | 4 +-- xsd/datex2/DATEXIISchemaWithDefinitions.xsd | 4 +-- xsd/ifopt/ifopt_allStopPlace.xsd | 2 +- xsd/ifopt/ifopt_modes.xsd | 4 +-- xsd/ifopt/ifopt_path.xsd | 4 +-- xsd/siri_discovery.xsd | 4 +-- xsd/siri_facilityMonitoring_service.xsd | 4 +-- xsd/siri_model/siri_facility.xsd | 4 +-- .../siri_monitoredVehicleJourney.xsd | 4 +-- xsd/siri_model/siri_situation.xsd | 6 ++-- xsd/siri_model/siri_situationAffects.xsd | 34 +++++++++---------- xsd/siri_model/siri_situationServiceTypes.xsd | 6 ++-- 12 files changed, 40 insertions(+), 40 deletions(-) diff --git a/xsd/acsb/acsb_accessibility.xsd b/xsd/acsb/acsb_accessibility.xsd index 79bb5ede..715e1c09 100644 --- a/xsd/acsb/acsb_accessibility.xsd +++ b/xsd/acsb/acsb_accessibility.xsd @@ -59,13 +59,13 @@ Rail transport, Roads and road transport - Type for identifier of a hazard within a stop place. + Type for identifier of a hazard within a STOP PLACE. - Type for reference to an identifier of a hazard within a stop place. + Type for reference to an identifier of a hazard within a STOP PLACE. diff --git a/xsd/datex2/DATEXIISchemaWithDefinitions.xsd b/xsd/datex2/DATEXIISchemaWithDefinitions.xsd index 9fbab2b3..500aa072 100644 --- a/xsd/datex2/DATEXIISchemaWithDefinitions.xsd +++ b/xsd/datex2/DATEXIISchemaWithDefinitions.xsd @@ -5709,12 +5709,12 @@ - Operator action originated externally to the authority which is taking the action. + OPERATOR action originated externally to the authority which is taking the action. - Operator action originated within the authority which is taking the action. + OPERATOR action originated within the authority which is taking the action. diff --git a/xsd/ifopt/ifopt_allStopPlace.xsd b/xsd/ifopt/ifopt_allStopPlace.xsd index bd231b33..b5b91b8f 100644 --- a/xsd/ifopt/ifopt_allStopPlace.xsd +++ b/xsd/ifopt/ifopt_allStopPlace.xsd @@ -1,5 +1,5 @@ - diff --git a/xsd/ifopt/ifopt_modes.xsd b/xsd/ifopt/ifopt_modes.xsd index aef9d00b..49e8d5d0 100644 --- a/xsd/ifopt/ifopt_modes.xsd +++ b/xsd/ifopt/ifopt_modes.xsd @@ -54,7 +54,7 @@ Rail transport, Roads and road transport - Allowed categories of stop place. + Allowed categories of STOP PLACE. @@ -71,7 +71,7 @@ Rail transport, Roads and road transport - Allowed categroies of access to stop place. + Allowed categroies of access to STOP PLACE. diff --git a/xsd/ifopt/ifopt_path.xsd b/xsd/ifopt/ifopt_path.xsd index 9119ccb4..d9028287 100644 --- a/xsd/ifopt/ifopt_path.xsd +++ b/xsd/ifopt/ifopt_path.xsd @@ -14,7 +14,7 @@ 2007-03-29 -

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

      +

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

       text/xml @@ -44,7 +44,7 @@ Rail transport, Roads and road transport CEN TC278 WG3 SG6 - IFOPT Fixed Objects in Public Transport - Stop place Base Types. + IFOPT Fixed Objects in Public Transport - STOP PLACE Base Types. Standard diff --git a/xsd/siri_discovery.xsd b/xsd/siri_discovery.xsd index 9f224c51..014476d5 100644 --- a/xsd/siri_discovery.xsd +++ b/xsd/siri_discovery.xsd @@ -42,9 +42,9 @@ diff --git a/xsd/siri_facilityMonitoring_service.xsd b/xsd/siri_facilityMonitoring_service.xsd index 1274e156..f675cee6 100644 --- a/xsd/siri_facilityMonitoring_service.xsd +++ b/xsd/siri_facilityMonitoring_service.xsd @@ -191,12 +191,12 @@ Rail transport, Roads and road transport - Reference to a stop place. + Reference to a STOP PLACE. - Reference to a stop place component. + Reference to a STOP PLACE component. diff --git a/xsd/siri_model/siri_facility.xsd b/xsd/siri_model/siri_facility.xsd index a70f6dcb..f3b33e7a 100644 --- a/xsd/siri_model/siri_facility.xsd +++ b/xsd/siri_model/siri_facility.xsd @@ -195,12 +195,12 @@ Rail transport, Roads and road transport - Reference to a Stop Place. + Reference to a STOP PLACE. - System identifier of Stop Place component. Unique at least within Stop Place and concrete component type. + System identifier of STOP PLACE component. Unique at least within STOP PLACE and concrete component type. diff --git a/xsd/siri_model/siri_monitoredVehicleJourney.xsd b/xsd/siri_model/siri_monitoredVehicleJourney.xsd index 1bca27b4..1cec149d 100644 --- a/xsd/siri_model/siri_monitoredVehicleJourney.xsd +++ b/xsd/siri_model/siri_monitoredVehicleJourney.xsd @@ -313,7 +313,7 @@ For SIRI-VM this is the most recent stop visited by the VEHICLE. - Operator of JOURNEY PART. +SIRI v2.0 + OPERATOR of JOURNEY PART. +SIRI v2.0 @@ -342,7 +342,7 @@ A journey does always have one or more JOURNEY PARTs for which the train formati - Operator of JOURNEY PART. + OPERATOR of JOURNEY PART. diff --git a/xsd/siri_model/siri_situation.xsd b/xsd/siri_model/siri_situation.xsd index 894a78b6..c49d82e8 100644 --- a/xsd/siri_model/siri_situation.xsd +++ b/xsd/siri_model/siri_situation.xsd @@ -332,7 +332,7 @@ Rail transport, Roads and road transport - Structured model identifiying parts of transport network affected by SITUATION. Operator and Network values will be defaulted to values in general Context unless explicitly overridden. + Structured model identifiying parts of transport network affected by SITUATION. OPERATOR and Network values will be defaulted to values in general Context unless explicitly overridden. @@ -813,7 +813,7 @@ Note: this means that ReasonName is NOT a complete message, but only a (few) wor       - TPEG Pts36_1, stop place + TPEG Pts36_1, STOP PLACE @@ -853,7 +853,7 @@ Note: this means that ReasonName is NOT a complete message, but only a (few) wor - stop place component + STOP PLACE component diff --git a/xsd/siri_model/siri_situationAffects.xsd b/xsd/siri_model/siri_situationAffects.xsd index e1fccfc9..fba15f5f 100644 --- a/xsd/siri_model/siri_situationAffects.xsd +++ b/xsd/siri_model/siri_situationAffects.xsd @@ -142,12 +142,12 @@ Rail transport, Roads and road transport       - Reference of Stop Place related to this affected StopPoint. + Reference of STOP PLACE related to this affected StopPoint. - Name of Stop Place related to this affected StopPoint. (Unbounded to allow a text for every language) + Name of STOP PLACE related to this affected StopPoint. (Unbounded to allow a text for every language) @@ -592,7 +592,7 @@ Rail transport, Roads and road transport - Restricts the affected scope to the specified ORIGINs + Restricts the affected scope to the specified origins @@ -631,7 +631,7 @@ Rail transport, Roads and road transport - Used to restrict lines to some stop points + Restricts the affected scope to the specified SCHEDULED STOP POINTs @@ -641,7 +641,7 @@ Rail transport, Roads and road transport - Used to restrict lines to some stop places + Restricts the affected scope to the specified STOP PLACEs @@ -818,7 +818,7 @@ Rail transport, Roads and road transport - Reference to a service VEHICLE JOURNEY affected by a SITUATION. + DEPRECATED (SIRI 2.1) - use only FramedVehicleJourneyRef @@ -883,7 +883,7 @@ Rail transport, Roads and road transport - Restricts the affected scope to the specified ORIGINs from which the LINE runs. [equivalent to pti15 1 start_point route_description_type] + Restricts the affected scope to the specified origins from which the LINE runs. [equivalent to pti15 1 start_point route_description_type] @@ -908,12 +908,12 @@ Rail transport, Roads and road transport - DESTINATION name shown for journey at the origin. Can be Used to identify joruney for user. (+SIRI 2.0), + DESTINATION name shown for journey at the origin. Can be Used to identify journey for user. (+SIRI 2.0), - DESTINATION name shown for journey at the origin. Can be Used to identify joruney for user. (+SIRI 2.0) + DESTINATION name shown for journey at the origin. Can be Used to identify journey for user. (+SIRI 2.0) @@ -923,7 +923,7 @@ Rail transport, Roads and road transport - enum Status of service for this Vehicle Journey - TPEG value. Multiple Conditions can be valid at the same time. (+SIRI 2.0) + Status of service for this Vehicle Journey - TPEG value. Multiple Conditions can be valid at the same time. (+SIRI 2.0) @@ -1173,24 +1173,24 @@ Rail transport, Roads and road transport       - Type for information about the Stop Places affected by an SITUATION. + Type for information about the STOP PLACEs affected by an SITUATION. - Stop Place affected by SITUATION. + Identifier of STOP PLACE affected by SITUATION. - Name of stop place. (Unbounded since SIRI 2.0) + Name of STOP PLACE. (Unbounded since SIRI 2.0) - Type of Stop Place. + Type of STOP PLACE. @@ -1233,7 +1233,7 @@ Rail transport, Roads and road transport - Used to restrict stop places to some lines + Used to restrict STOP PLACEs to some lines @@ -1255,7 +1255,7 @@ Rail transport, Roads and road transport - Reference to a Stop Place. + Reference to a STOP PLACE. @@ -1417,7 +1417,7 @@ Rail transport, Roads and road transport - TPEG Pts41_255, undefined stop place type + TPEG Pts41_255, undefined STOP PLACE type diff --git a/xsd/siri_model/siri_situationServiceTypes.xsd b/xsd/siri_model/siri_situationServiceTypes.xsd index 8b2e19ea..1f7e99ed 100644 --- a/xsd/siri_model/siri_situationServiceTypes.xsd +++ b/xsd/siri_model/siri_situationServiceTypes.xsd @@ -488,17 +488,17 @@ Reasons for the loss of a feeder include (but are not limited to) the cancellati - TPEG Pts44_9, affected stop place + TPEG Pts44_9, affected STOP PLACE - TPEG Pts44_10, presented stop place + TPEG Pts44_10, presented STOP PLACE - TPEG Pts44_255, undefined stop place usage + TPEG Pts44_255, undefined STOP PLACE usage From 7400ddd9bf0888de528c3434cbc3cd0150458768 Mon Sep 17 00:00:00 2001 From: u215619 Date: Thu, 22 Apr 2021 07:05:43 +0200 Subject: [PATCH 269/290] AdviceType Typo: undefined should be called undefinedAdvice in PTS039 https://3.basecamp.com/3256016/buckets/9672657/messages/3692967317 --- xsd/siri_model/siri_situation.xsd | 7 ++++++- xsd/siri_model/siri_situationAffects.xsd | 2 +- 2 files changed, 7 insertions(+), 2 deletions(-) diff --git a/xsd/siri_model/siri_situation.xsd b/xsd/siri_model/siri_situation.xsd index c49d82e8..05c21056 100644 --- a/xsd/siri_model/siri_situation.xsd +++ b/xsd/siri_model/siri_situation.xsd @@ -1441,12 +1441,17 @@ Alternatively, AdviceRef can be used to reference a (complete) standardised advi no advice + + + TPEG Pts39_255, undefined advice + + take detour - + change accessibility diff --git a/xsd/siri_model/siri_situationAffects.xsd b/xsd/siri_model/siri_situationAffects.xsd index fba15f5f..c4c581ba 100644 --- a/xsd/siri_model/siri_situationAffects.xsd +++ b/xsd/siri_model/siri_situationAffects.xsd @@ -337,7 +337,7 @@ Rail transport, Roads and road transport - Mode Submode and OPERATOR. Overrides any value sspecified for (i) Affected Network (ii) General Context. + Mode Submode. Overrides any value sspecified for (i) Affected Network (ii) General Context. From 7cbbfdde9b025a78585848395fc0eb1bec4b13a7 Mon Sep 17 00:00:00 2001 From: u215619 Date: Tue, 27 Apr 2021 14:21:40 +0200 Subject: [PATCH 270/290] CR-090 annotations improvements (sync with document) --- .../VDV736_exm/SX_1010_first_message.xml | 4 +- xsd/acsb/acsb_accessibility.xsd | 4 +- xsd/acsb/acsb_limitations.xsd | 16 ++-- .../siri_monitoredVehicleJourney.xsd | 2 +- xsd/siri_model/siri_situation.xsd | 4 +- xsd/siri_model/siri_situationActions.xsd | 75 ++++++++++--------- xsd/siri_model/siri_situationAffects.xsd | 12 +-- 7 files changed, 60 insertions(+), 57 deletions(-) diff --git a/examples/siri_exm_SX/VDV736_exm/SX_1010_first_message.xml b/examples/siri_exm_SX/VDV736_exm/SX_1010_first_message.xml index 18dc5f39..16534ce6 100644 --- a/examples/siri_exm_SX/VDV736_exm/SX_1010_first_message.xml +++ b/examples/siri_exm_SX/VDV736_exm/SX_1010_first_message.xml @@ -35,7 +35,6 @@ DE Unterbruch zwischen Luzernerhof und Verkehrshaus Line disruption between Luzernerhof and Verkehrshaus - @@ -66,8 +65,7 @@ - - false + true diff --git a/xsd/acsb/acsb_accessibility.xsd b/xsd/acsb/acsb_accessibility.xsd index 715e1c09..ecf70753 100644 --- a/xsd/acsb/acsb_accessibility.xsd +++ b/xsd/acsb/acsb_accessibility.xsd @@ -84,7 +84,7 @@ Rail transport, Roads and road transport - Validty condition governing applicability of LIMITATION. + Validity condition governing applicability of LIMITATION. @@ -111,7 +111,7 @@ Rail transport, Roads and road transport - The accessibility limitations of a component. + The accessibility limitations on navigation. diff --git a/xsd/acsb/acsb_limitations.xsd b/xsd/acsb/acsb_limitations.xsd index 5869e977..51a0de13 100644 --- a/xsd/acsb/acsb_limitations.xsd +++ b/xsd/acsb/acsb_limitations.xsd @@ -83,12 +83,12 @@ Rail transport, Roads and road transport - Whether a PLACE / SITE ELEMENT has Audible signals for the viusally impaired. + Whether a PLACE / SITE ELEMENT has Audible signals for the visually impaired. Default is 'false'. - Whether a PLACE / SITE ELEMENT has Visual signals for the hearing impaired. + Whether a PLACE / SITE ELEMENT has Visual signals for the hearing impaired. Default is 'unknown'. @@ -104,32 +104,32 @@ Rail transport, Roads and road transport - Whether a PLACE / SITE ELEMENT is wheelchair accessible. + Whether a PLACE / SITE ELEMENT is wheelchair accessible. Default is 'false'. - Whether a PLACE / SITE ELEMENT has step free access. + Whether a PLACE / SITE ELEMENT has step free access. Default is 'unknown'. - Whether a PLACE / SITE ELEMENT has escalator free access. + Whether a PLACE / SITE ELEMENT has escalator free access. Default is 'unknown'. - Whether a PLACE / SITE ELEMENT has lift free access. + Whether a PLACE / SITE ELEMENT has lift free access. Default is 'unknown'. - Whether a PLACE / SITE ELEMENT is wheelchair accessible. + Whether a PLACE / SITE ELEMENT is wheelchair accessible. Default is 'false'. - Whether a PLACE / SITE ELEMENT has Visual signals availble for the free access. + Whether a PLACE / SITE ELEMENT has Visual signals available for the visually impaired. diff --git a/xsd/siri_model/siri_monitoredVehicleJourney.xsd b/xsd/siri_model/siri_monitoredVehicleJourney.xsd index 1cec149d..a3e2d603 100644 --- a/xsd/siri_model/siri_monitoredVehicleJourney.xsd +++ b/xsd/siri_model/siri_monitoredVehicleJourney.xsd @@ -400,7 +400,7 @@ A journey does always have one or more JOURNEY PARTs for which the train formati - Description of position of Train BLOCK Part within Train to guide passengers where to find it. E.g. 'Front four coaches'. + Description of position of train BLOCK part within Train to guide passengers where to find it. E.g. 'Front four coaches'. diff --git a/xsd/siri_model/siri_situation.xsd b/xsd/siri_model/siri_situation.xsd index 05c21056..29053373 100644 --- a/xsd/siri_model/siri_situation.xsd +++ b/xsd/siri_model/siri_situation.xsd @@ -452,12 +452,12 @@ Rail transport, Roads and road transport - AFfected Road as described by a Date2x location. + Affected Road as described by a Date2x location. - Optional spatial projection of road. Can be used to distriute the path of the road to systems that do not already hold it. To pass just a Reference, use Datex2 location. + Optional spatial projection of road. Can be used to distribute the path of the road to systems that do not already hold it. To pass just a Reference, use Datex2 location. diff --git a/xsd/siri_model/siri_situationActions.xsd b/xsd/siri_model/siri_situationActions.xsd index bf3a641a..eb1f1222 100644 --- a/xsd/siri_model/siri_situationActions.xsd +++ b/xsd/siri_model/siri_situationActions.xsd @@ -125,7 +125,7 @@ Rail transport, Roads and road transport - Processing Status of action at time of SITUATION publication. + Processing Status of action at time of SITUATION publication. Default is 'open'. @@ -150,7 +150,7 @@ Rail transport, Roads and road transport - Defines a number of validity periods. When not sent, then the validity periods of higher level are valid. Can be overwritten by deeper level. + Defines a number of publication windows. When not sent, then the publication windows of higher level are valid. Can be overwritten by deeper level. @@ -255,12 +255,12 @@ Rail transport, Roads and road transport - Action: Publish SITUATION To Web. + Action: Publish SITUATION To Web channel. - Type for Action Publish SITUATION To Web. + Type for Action Publish SITUATION To Web channel. @@ -282,7 +282,7 @@ Rail transport, Roads and road transport - Include in social NETWORK indicated by this name. Possible value could be "twitter.com", "facebook.com", "vk.com" and so on. Parameters may be specifed as Action data. (SIRIv 2.10) + Include in social NETWORK indicated by this name. Possible value could be "twitter.com", "facebook.com", "vk.com" and so on. Parameters may be specified as Action data. Default is 'false' (SIRI 2.1) @@ -291,12 +291,12 @@ Rail transport, Roads and road transport - Action: Publish SITUATION To WAP and PDA. + Action: Publish SITUATION To Mobile Applications. - Type for Action Publish SITUATION To Displays. + Type for Action Publish SITUATION To Mobile Applications. @@ -317,12 +317,12 @@ Rail transport, Roads and road transport - Action: Publish SITUATION To Displays. + Action: Publish SITUATION To Display channel. - Type for Action Publish SITUATION To Web. + Type for Action Publish SITUATION To Display channel. @@ -343,12 +343,12 @@ Rail transport, Roads and road transport - Action: Publish SITUATION To Alert Service. + Action: Publish SITUATION To Alert channel. - Type for Action Publish SITUATION To Alert Service. + Type for Action Publish SITUATION To Alert channel. @@ -369,12 +369,12 @@ Rail transport, Roads and road transport - Action: Publish SITUATION To TvService. + Action: Publish SITUATION To TV channel. - Type for Notify SITUATION to Tv. + Type for Notify SITUATION to TV channel. @@ -396,7 +396,7 @@ Rail transport, Roads and road transport - Action: Publish SITUATION Manually. i.e. a procedure must be carried out. + Action: Publish SITUATION to Manual publication channel. @@ -406,7 +406,7 @@ Rail transport, Roads and road transport - Type for Action Publish SITUATION Manual process. + Type for Action Publish SITUATION to Manual publication channel. @@ -414,24 +414,24 @@ Rail transport, Roads and road transport - Action: Publish SITUATION to an individual by SMS. + Action: Publish SITUATION to an individual user by SMS. - Type for Notify user by SMS. + Type for Notify an individual user by SMS. - MSISDN of user to which to send messages. + MSISDN of user to which to send messages. Default is 'true'. - Whether content is flagged as subject to premium charge. + Whether content is flagged as subject to premium charge. Default is 'false'. @@ -440,12 +440,12 @@ Rail transport, Roads and road transport - Action: Publish SITUATION to a named workgroup or individual by email. + Action: Publish SITUATION to a named workgroup or individual user by email. - Type for Notify user by Email. + Type for Notify a named workgroup or individual user by email. @@ -473,12 +473,12 @@ Rail transport, Roads and road transport - Reference to a pager group to be notfied. + Reference to a pager group to be notified. - Pager number of pager to be notfied. + Pager number of pager to be notified. Default is 'true'. @@ -487,7 +487,7 @@ Rail transport, Roads and road transport - Action: Publish SITUATION To User. + Action: Publish SITUATION To User by other means. @@ -499,7 +499,7 @@ Rail transport, Roads and road transport - Workgroup of user to be notified. + Workgroup of user to be notified. Default is 'true'. @@ -509,7 +509,7 @@ Rail transport, Roads and road transport - Reference to a user to be notified. + Reference to a user to be notified. Default is 'true'. @@ -521,7 +521,7 @@ Rail transport, Roads and road transport - Description of SITUATION. Should not repeat any strap line included in Summary. + Description of passenger information action in a specific language. Should not repeat any strap line included in Summary. @@ -536,7 +536,7 @@ Rail transport, Roads and road transport - Further consequence to passengers. + Consequence of passenger information action in a specific language. @@ -551,7 +551,8 @@ Rail transport, Roads and road transport - Further information about the duration to passengers. + Indicates the currently expected duration of a SITUATION in a specific language. An estimation should be given here, because an indefinite duration is not helpful to the passenger. The duration can be adjusted at any time, if the traffic operator has additional information. + @@ -568,7 +569,7 @@ Rail transport, Roads and road transport - The time of the last update + The time of the last update. This must be the timestamp of the original data source and not that of an intermediate system, such as a data hub. This timestamp has to be changed by the source system with every update. @@ -599,7 +600,7 @@ Rail transport, Roads and road transport - All texts of the passenger information. + The actual, structured passenger information. @@ -633,7 +634,7 @@ Rail transport, Roads and road transport - Reason of passenger information action. + Reason of passenger information action in a specific language. @@ -642,7 +643,7 @@ Rail transport, Roads and road transport - Further recommendation to passengers. + Recommendation of passenger information action in a specific language. @@ -672,7 +673,7 @@ Rail transport, Roads and road transport - Summary of passenger information action. + Summary of passenger information action in a specific language. @@ -684,7 +685,11 @@ Rail transport, Roads and road transport Class of size, e.g. L (large), M (medium), S (small) - + + + Limits the distribution to publication channels in addition to perspective + + Content for summary of a passenger information action diff --git a/xsd/siri_model/siri_situationAffects.xsd b/xsd/siri_model/siri_situationAffects.xsd index c4c581ba..1b7e7eab 100644 --- a/xsd/siri_model/siri_situationAffects.xsd +++ b/xsd/siri_model/siri_situationAffects.xsd @@ -985,12 +985,12 @@ Rail transport, Roads and road transport - Reference to VEHICLE JOURNEY that VEHICLE is making. + Reference to VEHICLE JOURNEY framed by the day which the VEHICLE is running. - Location where the VEHICLE was when the situation arosse + Location where the VEHICLE was when the situation arose @@ -1006,7 +1006,7 @@ Rail transport, Roads and road transport - If a VEHICLE JOURNEY is a coupled journey, i.e. comprises several coupled BLOCKparts, there will be a separate delivery for each BLOCKp art and this element will indicate the vehicles that the journey part uses. + If a VEHICLE JOURNEY is a coupled journey, i.e. comprises several coupled BLOCK PARTs, there will be a separate delivery for each BLOCK PART and this element will indicate the vehicles that the journey part uses. @@ -1037,7 +1037,7 @@ Rail transport, Roads and road transport - Order of visit to stop within JORUNYE PATTERN of journey. + Order of visit to stop within JOURNEY PATTERN of journey. @@ -1142,12 +1142,12 @@ Rail transport, Roads and road transport - Category of TOPGRAPHIC PLACE or SITE. + Category of TOPOGRAPHIC PLACE or SITE. - Reference to an EQUIPMENT found at location. + Reference to an EQUIPMENT found at SITE. From 6b8562411be2288efb51f46bd9a4c85f08fa8b51 Mon Sep 17 00:00:00 2001 From: u215619 Date: Tue, 27 Apr 2021 14:24:18 +0200 Subject: [PATCH 271/290] CR-090 comments in German deleted --- .../siri_exm_SX/VDV736_exm/SX_1022_main_message.xml | 12 ++++++------ .../VDV736_exm/SX_1135_main_message_update.xml | 2 +- .../siri_exm_SX/VDV736_exm/SX_1247_end_message.xml | 2 +- 3 files changed, 8 insertions(+), 8 deletions(-) diff --git a/examples/siri_exm_SX/VDV736_exm/SX_1022_main_message.xml b/examples/siri_exm_SX/VDV736_exm/SX_1022_main_message.xml index fb0f9892..89d77161 100644 --- a/examples/siri_exm_SX/VDV736_exm/SX_1022_main_message.xml +++ b/examples/siri_exm_SX/VDV736_exm/SX_1022_main_message.xml @@ -694,7 +694,7 @@ - + ch:vbl:VBL014 14 @@ -733,7 +733,7 @@ - + @@ -1297,7 +1297,7 @@ Büttenhalde - + ch:vbl:618::03 Brüelstrasse(B) @@ -1342,7 +1342,7 @@ Würzenbach - + ch:vbl:618::03 Brüelstrasse(B) @@ -1779,7 +1779,7 @@ stopPoint L - + Unterbruch zwischen Luzernerhof und Verkehrshaus Line disruption between Luzernerhof and Verkehrshaus @@ -1806,7 +1806,7 @@ - ch:vbl:VBLEBUS diff --git a/examples/siri_exm_SX/VDV736_exm/SX_1135_main_message_update.xml b/examples/siri_exm_SX/VDV736_exm/SX_1135_main_message_update.xml index b80ee76c..1556b96b 100644 --- a/examples/siri_exm_SX/VDV736_exm/SX_1135_main_message_update.xml +++ b/examples/siri_exm_SX/VDV736_exm/SX_1135_main_message_update.xml @@ -2093,7 +2093,7 @@ ch:vbl:VBL002 2 - + ch:vbl:VBL002:A Bahnhof diff --git a/examples/siri_exm_SX/VDV736_exm/SX_1247_end_message.xml b/examples/siri_exm_SX/VDV736_exm/SX_1247_end_message.xml index ba27997c..8b7625d0 100644 --- a/examples/siri_exm_SX/VDV736_exm/SX_1247_end_message.xml +++ b/examples/siri_exm_SX/VDV736_exm/SX_1247_end_message.xml @@ -22,7 +22,7 @@ VBL closing - + 2017-05-28T12:22:00+02:00 2017-05-28T17:10:00+02:00 From 12cac57a1954cbd141580125b4cef53be0aa9d02 Mon Sep 17 00:00:00 2001 From: u215619 Date: Tue, 4 May 2021 09:00:00 +0200 Subject: [PATCH 272/290] CR-090 aligned default value --- xsd/siri_situationExchange_service.xsd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xsd/siri_situationExchange_service.xsd b/xsd/siri_situationExchange_service.xsd index 58406ec2..f88e20ae 100644 --- a/xsd/siri_situationExchange_service.xsd +++ b/xsd/siri_situationExchange_service.xsd @@ -344,9 +344,9 @@ Rail transport, Roads and road transport Parameters to filter Situation Exchange Service requests, based on the SITUATION Classifiers. Logically ANDed with other values. - + - Severity filter value to apply: only SITUATIONs with a severity greater than or equal to the specified value will be returned. See TPEG severities. Default is 'all'. + Severity filter value to apply: only SITUATIONs with a severity greater than or equal to the specified value will be returned. See TPEG severities. Default is 'normal'. From a9cd1e05a436397c87b4945a8a1495957f9a3a14 Mon Sep 17 00:00:00 2001 From: u215619 Date: Tue, 4 May 2021 11:14:37 +0200 Subject: [PATCH 273/290] CR-090 fixed deleting German comment --- examples/siri_exm_SX/VDV736_exm/SX_1022_main_message.xml | 3 --- 1 file changed, 3 deletions(-) diff --git a/examples/siri_exm_SX/VDV736_exm/SX_1022_main_message.xml b/examples/siri_exm_SX/VDV736_exm/SX_1022_main_message.xml index 89d77161..f37ac6dd 100644 --- a/examples/siri_exm_SX/VDV736_exm/SX_1022_main_message.xml +++ b/examples/siri_exm_SX/VDV736_exm/SX_1022_main_message.xml @@ -1806,9 +1806,6 @@ - - Bei einer anderen Meldung wurde der Entlastungsbus mit ch:vbl:Entlastungsbus bezeichnet. Welche Bezeichnung soll verwendet werden? - --> ch:vbl:VBLEBUS EBUS From 6917f067a4e226752761069f63165965475455ac Mon Sep 17 00:00:00 2001 From: tim-rivett <56296031+tim-rivett@users.noreply.github.com> Date: Tue, 4 May 2021 17:08:15 +0100 Subject: [PATCH 274/290] remove IFOPT reference remove IFOPT reference in FacilityLocationStructure documentation tag --- xsd/siri_model/siri_facility.xsd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xsd/siri_model/siri_facility.xsd b/xsd/siri_model/siri_facility.xsd index d715aa7d..cb75a629 100644 --- a/xsd/siri_model/siri_facility.xsd +++ b/xsd/siri_model/siri_facility.xsd @@ -160,7 +160,7 @@ Rail transport, Roads and road transport - Describes where the facility is located. The location is a Transmodel object reference or an IFOPT object reference. + Describes where the facility is located. The location is a Transmodel object reference or an NeTEx object reference. From 07770371fcaaa67556bc4c618ebb81c482a80e85 Mon Sep 17 00:00:00 2001 From: u215619 Date: Tue, 11 May 2021 15:42:34 +0200 Subject: [PATCH 275/290] typo --- xsd/siri_model/siri_journey_support.xsd | 2 +- xsd/siri_model/siri_situation.xsd | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/xsd/siri_model/siri_journey_support.xsd b/xsd/siri_model/siri_journey_support.xsd index 02f9f85e..2c368d00 100644 --- a/xsd/siri_model/siri_journey_support.xsd +++ b/xsd/siri_model/siri_journey_support.xsd @@ -727,7 +727,7 @@ Corresponds to NeTEX TYPE OF SERVICe. - Data has confidence lvel of reliabel (3/5). + Data has confidence lvel of reliable (3/5). diff --git a/xsd/siri_model/siri_situation.xsd b/xsd/siri_model/siri_situation.xsd index 29053373..5da7bdf4 100644 --- a/xsd/siri_model/siri_situation.xsd +++ b/xsd/siri_model/siri_situation.xsd @@ -615,7 +615,7 @@ Rail transport, Roads and road transport - Likellihoo of a future sutuation happening. + Likellihood of a future situation happening. From 4562b3e8a58460a3f6c802dbb5b8036749285812 Mon Sep 17 00:00:00 2001 From: u215619 Date: Tue, 11 May 2021 15:44:28 +0200 Subject: [PATCH 276/290] XML Files Version reset to 2.0 --- .../exa_checkStatus_request.xml | 4 ++-- .../exa_checkStatus_response.xml | 2 +- .../exa_dataReady_request.xml | 2 +- .../exa_dataReady_response.xml | 2 +- .../exa_dataReceived_response.xml | 2 +- .../exa_dataSupply_request.xml | 2 +- .../exa_heartbeat_request.xml | 2 +- .../exa_requestSubscription_response.xml | 2 +- ...xa_subscriptionTerminated_notification.xml | 2 +- .../exa_terminateSubscription_request.xml | 2 +- .../exa_terminateSubscription_response.xml | 2 +- ...exa_terminateSubscription_response_err.xml | 2 +- ...nnectionMonitoringDistributor_response.xml | 4 ++-- ...xc_connectionMonitoringFeeder_response.xml | 4 ++-- ...nectionMonitoring_capabilitiesResponse.xml | 2 +- .../exc_connectionMonitoring_request.xml | 6 ++--- ...nnectionMonitoring_subscriptionRequest.xml | 4 ++-- ...nnectionTimetable_capabilitiesResponse.xml | 2 +- .../exc_connectionTimetable_request.xml | 4 ++-- .../exc_connectionTimetable_response.xml | 4 ++-- ...onnectionTimetable_subscriptionRequest.xml | 4 ++-- ...stimatedTimetable_capabilitiesResponse.xml | 2 +- .../ext_estimatedTimetable_request.xml | 4 ++-- .../ext_estimatedTimetable_response.xml | 4 ++-- ...estimatedTimetable_subscriptionRequest.xml | 4 ++-- ...acilityMonitoring_capabilitiesResponse.xml | 2 +- .../exf_facilityMonitoring_request.xml | 4 ++-- .../exf_facilityMonitoring_response.xml | 4 ++-- ...facilityMonitoring_subscriptionRequest.xml | 6 ++--- .../exm_generalMessage_capabilityResponse.xml | 2 +- .../exm_generalMessage_request.xml | 4 ++-- .../exm_generalMessage_response.xml | 4 ++-- .../exm_generalMessage_response_embed.xml | 6 ++--- ...exm_generalMessage_subscriptionRequest.xml | 4 ++-- ...oductionTimetable_capabilitiesResponse.xml | 2 +- .../ext_productionTimetable_request.xml | 4 ++-- .../ext_productionTimetable_response.xml | 4 ++-- ...roductionTimetable_subscriptionRequest.xml | 4 ++-- ...xs_stopMonitoring_capabilitiesResponse.xml | 2 +- .../exs_stopMonitoring_request.xml | 4 ++-- .../exs_stopMonitoring_request_simple.xml | 4 ++-- .../exs_stopMonitoring_response.xml | 4 ++-- .../exs_stopMonitoring_response_complex.xml | 4 ++-- .../exs_stopMonitoring_response_simple.xml | 4 ++-- ...exs_stopMonitoring_subscriptionRequest.xml | 8 +++---- ...pMonitoring_subscriptionRequest_simple.xml | 4 ++-- ...exs_stopTimetable_capabilitiesResponse.xml | 2 +- .../siri_exm_ST/exs_stopTimetable_request.xml | 4 ++-- .../exs_stopTimetable_response.xml | 4 ++-- .../exs_stopTimetable_subscriptionRequest.xml | 4 ++-- .../VDV736_exm/SX_1010_first_message.xml | 4 ++-- .../VDV736_exm/SX_1022_main_message.xml | 4 ++-- .../SX_1135_main_message_update.xml | 4 ++-- .../VDV736_exm/SX_1247_end_message.xml | 4 ++-- .../exx_situationExchangeResponse.xml | 4 ++-- ...x_situationExchange_capabilityResponse.xml | 2 +- .../exx_situationExchange_request.xml | 4 ++-- .../exx_situationExchange_request_simple.xml | 4 ++-- .../exx_situationExchange_response.xml | 4 ++-- ..._situationExchange_subscriptionRequest.xml | 4 ++-- ...vehicleMonitoring_capabilitiesResponse.xml | 2 +- .../exv_vehicleMonitoring_request.xml | 4 ++-- .../exv_vehicleMonitoring_request_simple.xml | 4 ++-- .../exv_vehicleMonitoring_response.xml | 4 ++-- .../exv_vehicleMonitoring_response_simple.xml | 4 ++-- ...exv_vehicleMonitoring_responsex_simple.xml | 4 ++-- ..._vehicleMonitoring_subscriptionRequest.xml | 6 ++--- .../exd_allServices_capabilitiesRequest.xml | 24 +++++++++---------- .../exd_allServices_capabilitiesResponse.xml | 24 +++++++++---------- .../exd_lines_discoveryRequest.xml | 4 ++-- .../exd_lines_discoveryResponse.xml | 4 ++-- ...exd_productCategories_discoveryRequest.xml | 4 ++-- ...xd_productCategories_discoveryResponse.xml | 4 ++-- .../exd_serviceFeatures_discoveryRequest.xml | 4 ++-- .../exd_serviceFeatures_discoveryResponse.xml | 4 ++-- .../exd_stopPoints_discoveryRequest.xml | 4 ++-- .../exd_stopPoints_discoveryResponse.xml | 4 ++-- .../exd_vehicleFeatures_discoveryRequest.xml | 4 ++-- .../exd_vehicleFeatures_discoveryResponse.xml | 4 ++-- 79 files changed, 163 insertions(+), 163 deletions(-) diff --git a/examples/siri_exa_framework/exa_checkStatus_request.xml b/examples/siri_exa_framework/exa_checkStatus_request.xml index 40ae1202..8a3d8b7c 100644 --- a/examples/siri_exa_framework/exa_checkStatus_request.xml +++ b/examples/siri_exa_framework/exa_checkStatus_request.xml @@ -1,8 +1,8 @@ - + - + 2004-12-17T09:30:47-05:00 EREWHON diff --git a/examples/siri_exa_framework/exa_checkStatus_response.xml b/examples/siri_exa_framework/exa_checkStatus_response.xml index c9b81709..cd361cad 100644 --- a/examples/siri_exa_framework/exa_checkStatus_response.xml +++ b/examples/siri_exa_framework/exa_checkStatus_response.xml @@ -1,6 +1,6 @@ - + 2001-12-17T09:30:47-05:00 true diff --git a/examples/siri_exa_framework/exa_dataReady_request.xml b/examples/siri_exa_framework/exa_dataReady_request.xml index c3d16e45..2df43564 100644 --- a/examples/siri_exa_framework/exa_dataReady_request.xml +++ b/examples/siri_exa_framework/exa_dataReady_request.xml @@ -1,6 +1,6 @@ - + 2004-12-17T09:30:47-05:00 KUBRICK diff --git a/examples/siri_exa_framework/exa_dataReady_response.xml b/examples/siri_exa_framework/exa_dataReady_response.xml index 146e6c4c..85b7899d 100644 --- a/examples/siri_exa_framework/exa_dataReady_response.xml +++ b/examples/siri_exa_framework/exa_dataReady_response.xml @@ -1,6 +1,6 @@ - + 2004-12-17T09:30:47-05:00 NADER diff --git a/examples/siri_exa_framework/exa_dataReceived_response.xml b/examples/siri_exa_framework/exa_dataReceived_response.xml index 604cf8fb..b9f1a160 100644 --- a/examples/siri_exa_framework/exa_dataReceived_response.xml +++ b/examples/siri_exa_framework/exa_dataReceived_response.xml @@ -1,6 +1,6 @@ - + 2001-12-17T09:30:47-05:00 NADER diff --git a/examples/siri_exa_framework/exa_dataSupply_request.xml b/examples/siri_exa_framework/exa_dataSupply_request.xml index 2eb98a43..cebea5b8 100644 --- a/examples/siri_exa_framework/exa_dataSupply_request.xml +++ b/examples/siri_exa_framework/exa_dataSupply_request.xml @@ -1,6 +1,6 @@ - + 2004-12-17T09:30:47-05:00 NADER diff --git a/examples/siri_exa_framework/exa_heartbeat_request.xml b/examples/siri_exa_framework/exa_heartbeat_request.xml index 7336f549..cfeb8d67 100644 --- a/examples/siri_exa_framework/exa_heartbeat_request.xml +++ b/examples/siri_exa_framework/exa_heartbeat_request.xml @@ -1,6 +1,6 @@ - + 2004-12-17T09:30:47-05:00 KUBRICK diff --git a/examples/siri_exa_framework/exa_requestSubscription_response.xml b/examples/siri_exa_framework/exa_requestSubscription_response.xml index 75770eff..ca033b8d 100644 --- a/examples/siri_exa_framework/exa_requestSubscription_response.xml +++ b/examples/siri_exa_framework/exa_requestSubscription_response.xml @@ -1,6 +1,6 @@ - + 2004-12-17T09:30:47-05:00 EREWHON diff --git a/examples/siri_exa_framework/exa_subscriptionTerminated_notification.xml b/examples/siri_exa_framework/exa_subscriptionTerminated_notification.xml index 7091b843..8323ca00 100644 --- a/examples/siri_exa_framework/exa_subscriptionTerminated_notification.xml +++ b/examples/siri_exa_framework/exa_subscriptionTerminated_notification.xml @@ -1,6 +1,6 @@ - + 2004-12-17T09:30:47-05:00 KUBRICK diff --git a/examples/siri_exa_framework/exa_terminateSubscription_request.xml b/examples/siri_exa_framework/exa_terminateSubscription_request.xml index 4bd376d5..b8822f72 100644 --- a/examples/siri_exa_framework/exa_terminateSubscription_request.xml +++ b/examples/siri_exa_framework/exa_terminateSubscription_request.xml @@ -1,6 +1,6 @@ - + 2004-12-17T09:30:47-05:00 NADER diff --git a/examples/siri_exa_framework/exa_terminateSubscription_response.xml b/examples/siri_exa_framework/exa_terminateSubscription_response.xml index adff2aa2..aebd926b 100644 --- a/examples/siri_exa_framework/exa_terminateSubscription_response.xml +++ b/examples/siri_exa_framework/exa_terminateSubscription_response.xml @@ -1,6 +1,6 @@ - + 2004-12-17T09:30:47-05:00 KUBRICK diff --git a/examples/siri_exa_framework/exa_terminateSubscription_response_err.xml b/examples/siri_exa_framework/exa_terminateSubscription_response_err.xml index 664f61a5..e26d5ec5 100644 --- a/examples/siri_exa_framework/exa_terminateSubscription_response_err.xml +++ b/examples/siri_exa_framework/exa_terminateSubscription_response_err.xml @@ -1,6 +1,6 @@ - + 2004-12-17T09:30:47-05:00 KUBRICK diff --git a/examples/siri_exm_CM/exc_connectionMonitoringDistributor_response.xml b/examples/siri_exm_CM/exc_connectionMonitoringDistributor_response.xml index eb686154..da2bcbc7 100644 --- a/examples/siri_exm_CM/exc_connectionMonitoringDistributor_response.xml +++ b/examples/siri_exm_CM/exc_connectionMonitoringDistributor_response.xml @@ -1,13 +1,13 @@ - + 2004-12-17T09:30:46-05:00 KUBRICK true - + 2001-12-17T09:30:47.0Z 12345 true diff --git a/examples/siri_exm_CM/exc_connectionMonitoringFeeder_response.xml b/examples/siri_exm_CM/exc_connectionMonitoringFeeder_response.xml index 7e186f37..d9fcfef2 100644 --- a/examples/siri_exm_CM/exc_connectionMonitoringFeeder_response.xml +++ b/examples/siri_exm_CM/exc_connectionMonitoringFeeder_response.xml @@ -1,6 +1,6 @@ - + 2004-12-17T09:30:46-05:00 @@ -8,7 +8,7 @@ true false - + 2001-12-17T09:30:47-05:00 http://www.xmlspy.com true diff --git a/examples/siri_exm_CM/exc_connectionMonitoring_capabilitiesResponse.xml b/examples/siri_exm_CM/exc_connectionMonitoring_capabilitiesResponse.xml index 88fcd3ed..1f6b5161 100644 --- a/examples/siri_exm_CM/exc_connectionMonitoring_capabilitiesResponse.xml +++ b/examples/siri_exm_CM/exc_connectionMonitoring_capabilitiesResponse.xml @@ -1,6 +1,6 @@ - + 2001-12-17T09:30:47.0Z http://www.mytransportco.eu true diff --git a/examples/siri_exm_CM/exc_connectionMonitoring_request.xml b/examples/siri_exm_CM/exc_connectionMonitoring_request.xml index d94783c2..0df04e9f 100644 --- a/examples/siri_exm_CM/exc_connectionMonitoring_request.xml +++ b/examples/siri_exm_CM/exc_connectionMonitoring_request.xml @@ -1,11 +1,11 @@ - + 2004-12-17T09:30:47-05:00 NADER - + 2004-12-17T09:30:47-05:00 @@ -16,7 +16,7 @@ - + 2004-12-17T09:30:47-05:00 PT10M diff --git a/examples/siri_exm_CM/exc_connectionMonitoring_subscriptionRequest.xml b/examples/siri_exm_CM/exc_connectionMonitoring_subscriptionRequest.xml index 36ea5958..c5bea571 100644 --- a/examples/siri_exm_CM/exc_connectionMonitoring_subscriptionRequest.xml +++ b/examples/siri_exm_CM/exc_connectionMonitoring_subscriptionRequest.xml @@ -1,6 +1,6 @@ - + 2004-12-17T09:30:47-05:00 NADER @@ -8,7 +8,7 @@ NADER 000234 2004-12-17T09:30:47-05:00 - + 2004-12-17T09:30:47-05:00 EH00001 diff --git a/examples/siri_exm_CT/exc_connectionTimetable_capabilitiesResponse.xml b/examples/siri_exm_CT/exc_connectionTimetable_capabilitiesResponse.xml index f5d0d55f..27bc88cb 100644 --- a/examples/siri_exm_CT/exc_connectionTimetable_capabilitiesResponse.xml +++ b/examples/siri_exm_CT/exc_connectionTimetable_capabilitiesResponse.xml @@ -1,6 +1,6 @@ - + 2001-12-17T09:30:47.0Z http://www.mytransportco.eu true diff --git a/examples/siri_exm_CT/exc_connectionTimetable_request.xml b/examples/siri_exm_CT/exc_connectionTimetable_request.xml index f4dbadeb..9141bf5a 100644 --- a/examples/siri_exm_CT/exc_connectionTimetable_request.xml +++ b/examples/siri_exm_CT/exc_connectionTimetable_request.xml @@ -1,11 +1,11 @@ - + 2004-12-17T09:30:47-05:00 NADER - + 2004-12-17T09:30:47-05:00 diff --git a/examples/siri_exm_CT/exc_connectionTimetable_response.xml b/examples/siri_exm_CT/exc_connectionTimetable_response.xml index 725cda7d..c93d465a 100644 --- a/examples/siri_exm_CT/exc_connectionTimetable_response.xml +++ b/examples/siri_exm_CT/exc_connectionTimetable_response.xml @@ -1,6 +1,6 @@ - + 2004-12-17T09:30:46-05:00 @@ -8,7 +8,7 @@ true false - + 2001-12-17T09:30:47-05:00 http://www.xmlspy.com true diff --git a/examples/siri_exm_CT/exc_connectionTimetable_subscriptionRequest.xml b/examples/siri_exm_CT/exc_connectionTimetable_subscriptionRequest.xml index 7c0d7c2c..70a7e386 100644 --- a/examples/siri_exm_CT/exc_connectionTimetable_subscriptionRequest.xml +++ b/examples/siri_exm_CT/exc_connectionTimetable_subscriptionRequest.xml @@ -1,6 +1,6 @@ - + 2004-12-17T09:30:47-05:00 NADER @@ -11,7 +11,7 @@ NADER 000234 2004-12-17T09:30:47-05:00 - + 2004-12-17T09:30:47-05:00 diff --git a/examples/siri_exm_ET/ext_estimatedTimetable_capabilitiesResponse.xml b/examples/siri_exm_ET/ext_estimatedTimetable_capabilitiesResponse.xml index e1420e1b..0c019fb2 100644 --- a/examples/siri_exm_ET/ext_estimatedTimetable_capabilitiesResponse.xml +++ b/examples/siri_exm_ET/ext_estimatedTimetable_capabilitiesResponse.xml @@ -1,6 +1,6 @@ - + 2001-12-17T09:30:47.0Z http://www.mytransportco.eu true diff --git a/examples/siri_exm_ET/ext_estimatedTimetable_request.xml b/examples/siri_exm_ET/ext_estimatedTimetable_request.xml index 24faf55d..a3e683eb 100644 --- a/examples/siri_exm_ET/ext_estimatedTimetable_request.xml +++ b/examples/siri_exm_ET/ext_estimatedTimetable_request.xml @@ -1,12 +1,12 @@ - + 2004-12-17T09:30:47-05:00 NADER - + 2001-12-17T09:30:47-05:00 P1Y2M3DT10H30M 0008 diff --git a/examples/siri_exm_ET/ext_estimatedTimetable_response.xml b/examples/siri_exm_ET/ext_estimatedTimetable_response.xml index a1e4d6b2..59203036 100644 --- a/examples/siri_exm_ET/ext_estimatedTimetable_response.xml +++ b/examples/siri_exm_ET/ext_estimatedTimetable_response.xml @@ -1,6 +1,6 @@ - + 2004-12-17T09:30:46-05:00 @@ -8,7 +8,7 @@ true false - + 2001-12-17T09:30:47-05:00 NADER 0004 diff --git a/examples/siri_exm_ET/ext_estimatedTimetable_subscriptionRequest.xml b/examples/siri_exm_ET/ext_estimatedTimetable_subscriptionRequest.xml index 2311bc09..7da31a1b 100644 --- a/examples/siri_exm_ET/ext_estimatedTimetable_subscriptionRequest.xml +++ b/examples/siri_exm_ET/ext_estimatedTimetable_subscriptionRequest.xml @@ -1,6 +1,6 @@ - + 2004-12-17T09:30:47-05:00 @@ -10,7 +10,7 @@ NADER 000765 2001-12-17T09:30:47-05:00 - + 2001-12-17T09:30:47-05:00 P1Y2M3DT10H30M 0008 diff --git a/examples/siri_exm_FM/exf_facilityMonitoring_capabilitiesResponse.xml b/examples/siri_exm_FM/exf_facilityMonitoring_capabilitiesResponse.xml index 5c9cc831..bdd9f36f 100644 --- a/examples/siri_exm_FM/exf_facilityMonitoring_capabilitiesResponse.xml +++ b/examples/siri_exm_FM/exf_facilityMonitoring_capabilitiesResponse.xml @@ -1,6 +1,6 @@ - + 2001-12-17T09:30:47.0Z http://www.mytransportco.eu true diff --git a/examples/siri_exm_FM/exf_facilityMonitoring_request.xml b/examples/siri_exm_FM/exf_facilityMonitoring_request.xml index e1d0cb4e..e1b5acb3 100644 --- a/examples/siri_exm_FM/exf_facilityMonitoring_request.xml +++ b/examples/siri_exm_FM/exf_facilityMonitoring_request.xml @@ -1,6 +1,6 @@ - + @@ -14,7 +14,7 @@ 2004-12-17T09:30:47-05:00 NADER - + 2004-12-17T09:30:47-05:00 P10M diff --git a/examples/siri_exm_FM/exf_facilityMonitoring_response.xml b/examples/siri_exm_FM/exf_facilityMonitoring_response.xml index c6433f64..b247da82 100644 --- a/examples/siri_exm_FM/exf_facilityMonitoring_response.xml +++ b/examples/siri_exm_FM/exf_facilityMonitoring_response.xml @@ -1,6 +1,6 @@ - + 2004-12-17T09:30:46-05:00 @@ -8,7 +8,7 @@ true false - + 2004-12-17T09:30:47-05:00 NADER 2004-12-17T09:30:47-05:00 diff --git a/examples/siri_exm_FM/exf_facilityMonitoring_subscriptionRequest.xml b/examples/siri_exm_FM/exf_facilityMonitoring_subscriptionRequest.xml index 7f073bab..33b82c74 100644 --- a/examples/siri_exm_FM/exf_facilityMonitoring_subscriptionRequest.xml +++ b/examples/siri_exm_FM/exf_facilityMonitoring_subscriptionRequest.xml @@ -1,6 +1,6 @@ - + 2004-12-17T09:30:47-05:00 NADER @@ -11,7 +11,7 @@ NADER 000234 2004-12-17T09:30:47-05:00 - + 2004-12-17T15:30:47-05:00 PT30M abcdfr @@ -22,7 +22,7 @@ 000234 2004-12-17T15:30:47-05:01 - + 2004-12-17T09:30:47-05:05 PT30M diff --git a/examples/siri_exm_GM/exm_generalMessage_capabilityResponse.xml b/examples/siri_exm_GM/exm_generalMessage_capabilityResponse.xml index be81c2da..ce73e525 100644 --- a/examples/siri_exm_GM/exm_generalMessage_capabilityResponse.xml +++ b/examples/siri_exm_GM/exm_generalMessage_capabilityResponse.xml @@ -1,6 +1,6 @@ - + 2001-12-17T09:30:47-05:00 http://www.mytransportco.eu true diff --git a/examples/siri_exm_GM/exm_generalMessage_request.xml b/examples/siri_exm_GM/exm_generalMessage_request.xml index ae11f8e6..a8710a18 100644 --- a/examples/siri_exm_GM/exm_generalMessage_request.xml +++ b/examples/siri_exm_GM/exm_generalMessage_request.xml @@ -1,6 +1,6 @@ - + @@ -14,7 +14,7 @@ 2004-12-17T09:30:47-05:00 NADER - + 2004-12-17T09:30:47-05:00 WARNING diff --git a/examples/siri_exm_GM/exm_generalMessage_response.xml b/examples/siri_exm_GM/exm_generalMessage_response.xml index 8d31814f..f2d8cb13 100644 --- a/examples/siri_exm_GM/exm_generalMessage_response.xml +++ b/examples/siri_exm_GM/exm_generalMessage_response.xml @@ -1,6 +1,6 @@ - + 2004-12-17T09:30:46-05:00 @@ -8,7 +8,7 @@ true false - + 2001-12-17T09:30:47.0Z 12345 true diff --git a/examples/siri_exm_GM/exm_generalMessage_response_embed.xml b/examples/siri_exm_GM/exm_generalMessage_response_embed.xml index 6b5b61f2..64e82053 100644 --- a/examples/siri_exm_GM/exm_generalMessage_response_embed.xml +++ b/examples/siri_exm_GM/exm_generalMessage_response_embed.xml @@ -1,12 +1,12 @@ - + 2005-12-17T09:30:46-05:00 KUBRICK - + 2005-12-17T09:30:47.0Z 12345 true @@ -17,7 +17,7 @@ WARNINGS 2005-12-17T09:30:47.0Z - + 2005-08-18T10:58:11Z diff --git a/examples/siri_exm_GM/exm_generalMessage_subscriptionRequest.xml b/examples/siri_exm_GM/exm_generalMessage_subscriptionRequest.xml index 1cacc293..51de6f07 100644 --- a/examples/siri_exm_GM/exm_generalMessage_subscriptionRequest.xml +++ b/examples/siri_exm_GM/exm_generalMessage_subscriptionRequest.xml @@ -1,6 +1,6 @@ - + 2004-12-17T09:30:47-05:00 NADER @@ -11,7 +11,7 @@ NADER 000234 2004-12-17T09:30:47-05:00 - + 2004-12-17T15:30:47-05:00 diff --git a/examples/siri_exm_PT/ext_productionTimetable_capabilitiesResponse.xml b/examples/siri_exm_PT/ext_productionTimetable_capabilitiesResponse.xml index 409aa54c..9f4e1e5a 100644 --- a/examples/siri_exm_PT/ext_productionTimetable_capabilitiesResponse.xml +++ b/examples/siri_exm_PT/ext_productionTimetable_capabilitiesResponse.xml @@ -1,6 +1,6 @@ - + 2001-12-17T09:30:47.0Z http://www.altova.com true diff --git a/examples/siri_exm_PT/ext_productionTimetable_request.xml b/examples/siri_exm_PT/ext_productionTimetable_request.xml index bc863c82..405f1712 100644 --- a/examples/siri_exm_PT/ext_productionTimetable_request.xml +++ b/examples/siri_exm_PT/ext_productionTimetable_request.xml @@ -1,11 +1,11 @@ - + 2004-12-17T09:30:47-05:00 NADER - + 2001-12-17T09:30:47-05:00 2001-12-17T14:20:00 diff --git a/examples/siri_exm_PT/ext_productionTimetable_response.xml b/examples/siri_exm_PT/ext_productionTimetable_response.xml index 31373fe1..fe2ecb26 100644 --- a/examples/siri_exm_PT/ext_productionTimetable_response.xml +++ b/examples/siri_exm_PT/ext_productionTimetable_response.xml @@ -1,6 +1,6 @@ - + 2004-12-17T09:30:46-05:00 @@ -8,7 +8,7 @@ true false - + 2001-12-17T09:30:47-05:00 NADER 00123456 diff --git a/examples/siri_exm_PT/ext_productionTimetable_subscriptionRequest.xml b/examples/siri_exm_PT/ext_productionTimetable_subscriptionRequest.xml index 14a4951c..37885aeb 100644 --- a/examples/siri_exm_PT/ext_productionTimetable_subscriptionRequest.xml +++ b/examples/siri_exm_PT/ext_productionTimetable_subscriptionRequest.xml @@ -1,6 +1,6 @@ - + 2004-12-17T09:30:47-05:00 @@ -10,7 +10,7 @@ NADER 0000456 2001-12-17T09:30:47-05:00 - + 2001-12-17T09:30:47-05:00 2001-12-17T14:20:00 diff --git a/examples/siri_exm_SM/exs_stopMonitoring_capabilitiesResponse.xml b/examples/siri_exm_SM/exs_stopMonitoring_capabilitiesResponse.xml index ac5d8c08..9aa4e8a5 100644 --- a/examples/siri_exm_SM/exs_stopMonitoring_capabilitiesResponse.xml +++ b/examples/siri_exm_SM/exs_stopMonitoring_capabilitiesResponse.xml @@ -4,7 +4,7 @@ This example describes a set of capabilities & permissions describing a SIRI-SM Service (C) Copyright 2005-2012 CEN SIRI --> - + 2005-11-17T09:30:47-05:00 12536 true diff --git a/examples/siri_exm_SM/exs_stopMonitoring_request.xml b/examples/siri_exm_SM/exs_stopMonitoring_request.xml index b7d9c79f..429cfd27 100644 --- a/examples/siri_exm_SM/exs_stopMonitoring_request.xml +++ b/examples/siri_exm_SM/exs_stopMonitoring_request.xml @@ -6,7 +6,7 @@ See also simple request for minimal version (C) Copyright 2005-2012 CEN SIRI --> - + @@ -22,7 +22,7 @@ MONTECHRISTO 2B|~2B NADER - + 2004-12-17T09:30:47-05:00 diff --git a/examples/siri_exm_SM/exs_stopMonitoring_request_simple.xml b/examples/siri_exm_SM/exs_stopMonitoring_request_simple.xml index 163d8b59..4a9166b6 100644 --- a/examples/siri_exm_SM/exs_stopMonitoring_request_simple.xml +++ b/examples/siri_exm_SM/exs_stopMonitoring_request_simple.xml @@ -4,11 +4,11 @@ This example describes a minimal request to fetch stop real-time data using a SIRI-SM Service (C) Copyright 2005-2012 CEN SIRI --> - + 2004-12-17T09:30:47-05:00 NADER - + 2004-12-17T09:30:47-05:00 EH00001 diff --git a/examples/siri_exm_SM/exs_stopMonitoring_response.xml b/examples/siri_exm_SM/exs_stopMonitoring_response.xml index 92b3eb54..2bbffa75 100644 --- a/examples/siri_exm_SM/exs_stopMonitoring_response.xml +++ b/examples/siri_exm_SM/exs_stopMonitoring_response.xml @@ -8,7 +8,7 @@ See also simple response for minimal version (C) Copyright 2005-2012 CEN SIRI --> - + 2004-12-17T09:30:46-05:00 @@ -16,7 +16,7 @@ true false - + 2004-12-17T09:30:47-05:00 NADER 2004-12-17T09:30:47-05:00 diff --git a/examples/siri_exm_SM/exs_stopMonitoring_response_complex.xml b/examples/siri_exm_SM/exs_stopMonitoring_response_complex.xml index 94fac0ef..8c6347dd 100644 --- a/examples/siri_exm_SM/exs_stopMonitoring_response_complex.xml +++ b/examples/siri_exm_SM/exs_stopMonitoring_response_complex.xml @@ -8,7 +8,7 @@ See also simple response for minimal version (C) Copyright 2005-2012 CEN SIRI --> - + 2004-12-17T09:30:46-05:00 @@ -16,7 +16,7 @@ true false - + 2004-12-17T09:30:47-05:00 NADER 2004-12-17T09:30:47-05:00 diff --git a/examples/siri_exm_SM/exs_stopMonitoring_response_simple.xml b/examples/siri_exm_SM/exs_stopMonitoring_response_simple.xml index 27bc59b9..c2396dc2 100644 --- a/examples/siri_exm_SM/exs_stopMonitoring_response_simple.xml +++ b/examples/siri_exm_SM/exs_stopMonitoring_response_simple.xml @@ -4,14 +4,14 @@ This example describes a simple departure board (C) Copyright 2005-2012 CEN SIRI --> - + 2004-12-17T09:30:46-05:00 KUBRICK true - + 2004-12-17T09:30:47-05:00 NADER 2004-12-17T09:30:47-05:00 diff --git a/examples/siri_exm_SM/exs_stopMonitoring_subscriptionRequest.xml b/examples/siri_exm_SM/exs_stopMonitoring_subscriptionRequest.xml index 8dc3e7c3..535d9b56 100644 --- a/examples/siri_exm_SM/exs_stopMonitoring_subscriptionRequest.xml +++ b/examples/siri_exm_SM/exs_stopMonitoring_subscriptionRequest.xml @@ -6,7 +6,7 @@ See also simple request for minimal version (C) Copyright 2005-2012 CEN SIRI --> - + 2004-12-17T09:30:47-05:00 NADER @@ -17,7 +17,7 @@ NADER 000234 2004-12-17T09:30:47-05:00 - + 2004-12-17T15:30:47-05:00 PT30M POIT5678 @@ -38,7 +38,7 @@ 000234 2004-12-17T15:30:47-05:01 - + 2004-12-17T09:30:47-05:05 PT30M POIT5678 @@ -51,7 +51,7 @@ 000235 2004-12-17T15:30:47-05:01 - + 2004-12-17T09:30:47-05:06 PT30M POIT5678 diff --git a/examples/siri_exm_SM/exs_stopMonitoring_subscriptionRequest_simple.xml b/examples/siri_exm_SM/exs_stopMonitoring_subscriptionRequest_simple.xml index b5896366..bd736369 100644 --- a/examples/siri_exm_SM/exs_stopMonitoring_subscriptionRequest_simple.xml +++ b/examples/siri_exm_SM/exs_stopMonitoring_subscriptionRequest_simple.xml @@ -6,7 +6,7 @@ See also simple request for minimal version. (C) Copyright 2005-2012 CEN SIRI --> - + 2004-12-17T09:30:47-05:00 NADER @@ -14,7 +14,7 @@ NADER 000234 2004-12-17T09:30:47-05:00 - + 2004-12-17T15:30:47-05:00 POIT5678 normal diff --git a/examples/siri_exm_ST/exs_stopTimetable_capabilitiesResponse.xml b/examples/siri_exm_ST/exs_stopTimetable_capabilitiesResponse.xml index 78963a49..762a7f0d 100644 --- a/examples/siri_exm_ST/exs_stopTimetable_capabilitiesResponse.xml +++ b/examples/siri_exm_ST/exs_stopTimetable_capabilitiesResponse.xml @@ -1,6 +1,6 @@ - + 2001-12-17T09:30:47-05:00 http://www.mytransportco.eu true diff --git a/examples/siri_exm_ST/exs_stopTimetable_request.xml b/examples/siri_exm_ST/exs_stopTimetable_request.xml index c912fc3c..c1bf679a 100644 --- a/examples/siri_exm_ST/exs_stopTimetable_request.xml +++ b/examples/siri_exm_ST/exs_stopTimetable_request.xml @@ -4,12 +4,12 @@ This example describes a request to fetch stop timetabkle data using a SIRI-ST Service. (C) Copyright 2005-2012 CEN SIRI --> - + 2004-12-17T09:30:47-05:00 NADER - + 2004-12-17T09:30:47-05:00 diff --git a/examples/siri_exm_ST/exs_stopTimetable_response.xml b/examples/siri_exm_ST/exs_stopTimetable_response.xml index 424b47dd..bcf99ad1 100644 --- a/examples/siri_exm_ST/exs_stopTimetable_response.xml +++ b/examples/siri_exm_ST/exs_stopTimetable_response.xml @@ -1,13 +1,13 @@ - + 2004-12-17T09:30:46-05:00 KUBRICK true - + 2004-12-17T09:30:47-05:00 NADER 2004-12-17T09:30:47-05:00 diff --git a/examples/siri_exm_ST/exs_stopTimetable_subscriptionRequest.xml b/examples/siri_exm_ST/exs_stopTimetable_subscriptionRequest.xml index 4e15a7f9..4ea1d626 100644 --- a/examples/siri_exm_ST/exs_stopTimetable_subscriptionRequest.xml +++ b/examples/siri_exm_ST/exs_stopTimetable_subscriptionRequest.xml @@ -1,6 +1,6 @@ - + 2004-12-17T09:30:47-05:00 NADER @@ -11,7 +11,7 @@ NADER 000234 2004-12-17T09:30:47-05:00 - + 2004-12-17T09:30:47-05:00 diff --git a/examples/siri_exm_SX/VDV736_exm/SX_1010_first_message.xml b/examples/siri_exm_SX/VDV736_exm/SX_1010_first_message.xml index 16534ce6..15022cc5 100644 --- a/examples/siri_exm_SX/VDV736_exm/SX_1010_first_message.xml +++ b/examples/siri_exm_SX/VDV736_exm/SX_1010_first_message.xml @@ -1,5 +1,5 @@ - + 2018-10-04T10:11:00+00:00 ch:VBL @@ -7,7 +7,7 @@ t3xWB5cY3 true false - + 2018-10-04T10:11:00+00:00 ch:VBL 40599x2dsjmu8yjzy diff --git a/examples/siri_exm_SX/VDV736_exm/SX_1022_main_message.xml b/examples/siri_exm_SX/VDV736_exm/SX_1022_main_message.xml index f37ac6dd..98975ece 100644 --- a/examples/siri_exm_SX/VDV736_exm/SX_1022_main_message.xml +++ b/examples/siri_exm_SX/VDV736_exm/SX_1022_main_message.xml @@ -1,5 +1,5 @@ - + 2018-10-16T10:22:30+00:00 ch:VBL @@ -7,7 +7,7 @@ Pgfkw0GAsg true false - + 2018-10-16T10:22:30+00:00 ch:VBL 40599x2dsjmu8yjzy diff --git a/examples/siri_exm_SX/VDV736_exm/SX_1135_main_message_update.xml b/examples/siri_exm_SX/VDV736_exm/SX_1135_main_message_update.xml index 1556b96b..b458303c 100644 --- a/examples/siri_exm_SX/VDV736_exm/SX_1135_main_message_update.xml +++ b/examples/siri_exm_SX/VDV736_exm/SX_1135_main_message_update.xml @@ -1,5 +1,5 @@ - + 2018-10-16T10:22:30+00:00 ch:VBL @@ -7,7 +7,7 @@ Pgfkw0GAsg true false - + 2018-10-16T10:22:30+00:00 ch:VBL 40599x2dsjmu8yjzy diff --git a/examples/siri_exm_SX/VDV736_exm/SX_1247_end_message.xml b/examples/siri_exm_SX/VDV736_exm/SX_1247_end_message.xml index 8b7625d0..6010821b 100644 --- a/examples/siri_exm_SX/VDV736_exm/SX_1247_end_message.xml +++ b/examples/siri_exm_SX/VDV736_exm/SX_1247_end_message.xml @@ -1,5 +1,5 @@ - + 2018-10-04T12:22:00+00:00 ch:VBL @@ -7,7 +7,7 @@ JFI2d2mWP true false - + 2018-10-04T12:22:00+00:00 ch:VBL 40599x2dsjmu8yjzy diff --git a/examples/siri_exm_SX/exx_situationExchangeResponse.xml b/examples/siri_exm_SX/exx_situationExchangeResponse.xml index 3df28732..3a400eb8 100644 --- a/examples/siri_exm_SX/exx_situationExchangeResponse.xml +++ b/examples/siri_exm_SX/exx_situationExchangeResponse.xml @@ -1,6 +1,6 @@ - + 2004-12-17T09:30:46-05:00 @@ -8,7 +8,7 @@ true false - + 2004-12-17T09:30:46-05:00 diff --git a/examples/siri_exm_SX/exx_situationExchange_capabilityResponse.xml b/examples/siri_exm_SX/exx_situationExchange_capabilityResponse.xml index 02ca5f45..5c224c5f 100644 --- a/examples/siri_exm_SX/exx_situationExchange_capabilityResponse.xml +++ b/examples/siri_exm_SX/exx_situationExchange_capabilityResponse.xml @@ -1,6 +1,6 @@ - + 2001-12-17T09:30:47-05:00 http://www.mytransportco.eu true diff --git a/examples/siri_exm_SX/exx_situationExchange_request.xml b/examples/siri_exm_SX/exx_situationExchange_request.xml index 72cbbec1..b17fdad1 100644 --- a/examples/siri_exm_SX/exx_situationExchange_request.xml +++ b/examples/siri_exm_SX/exx_situationExchange_request.xml @@ -6,7 +6,7 @@ See also simple request for minimal version (C) Copyright 2005-2012 CEN SIRI --> - + @@ -20,7 +20,7 @@ 2004-12-17T09:30:47-05:00 NADER - + 2004-12-17T09:30:47-05:00 2004-12-17T09:30:47-05:00 diff --git a/examples/siri_exm_SX/exx_situationExchange_request_simple.xml b/examples/siri_exm_SX/exx_situationExchange_request_simple.xml index 6c25828d..f1e2158d 100644 --- a/examples/siri_exm_SX/exx_situationExchange_request_simple.xml +++ b/examples/siri_exm_SX/exx_situationExchange_request_simple.xml @@ -6,11 +6,11 @@ See also request for verbose version (C) Copyright 2005-2012 CEN SIRI --> - + 2004-12-17T09:30:47-05:00 NADER - + 2004-12-17T09:30:47-05:00 line diff --git a/examples/siri_exm_SX/exx_situationExchange_response.xml b/examples/siri_exm_SX/exx_situationExchange_response.xml index 559f2edc..8646260e 100644 --- a/examples/siri_exm_SX/exx_situationExchange_response.xml +++ b/examples/siri_exm_SX/exx_situationExchange_response.xml @@ -1,6 +1,6 @@ - + 2004-12-17T09:30:46-05:00 @@ -8,7 +8,7 @@ true false - + 2004-12-17T09:30:46-05:00 diff --git a/examples/siri_exm_SX/exx_situationExchange_subscriptionRequest.xml b/examples/siri_exm_SX/exx_situationExchange_subscriptionRequest.xml index 07d33360..0faa2997 100644 --- a/examples/siri_exm_SX/exx_situationExchange_subscriptionRequest.xml +++ b/examples/siri_exm_SX/exx_situationExchange_subscriptionRequest.xml @@ -1,6 +1,6 @@ - + 2004-12-17T09:30:47-05:00 NADER @@ -11,7 +11,7 @@ NADER 000234 2004-12-17T09:30:47-05:00 - + 2004-12-17T15:30:47-05:00 severe diff --git a/examples/siri_exm_VM/exv_vehicleMonitoring_capabilitiesResponse.xml b/examples/siri_exm_VM/exv_vehicleMonitoring_capabilitiesResponse.xml index 47c915df..997d3fd4 100644 --- a/examples/siri_exm_VM/exv_vehicleMonitoring_capabilitiesResponse.xml +++ b/examples/siri_exm_VM/exv_vehicleMonitoring_capabilitiesResponse.xml @@ -1,6 +1,6 @@ - + 2001-12-17T09:30:47.0Z http://www.mytransportco.eu true diff --git a/examples/siri_exm_VM/exv_vehicleMonitoring_request.xml b/examples/siri_exm_VM/exv_vehicleMonitoring_request.xml index 1e562ad0..663b72fb 100644 --- a/examples/siri_exm_VM/exv_vehicleMonitoring_request.xml +++ b/examples/siri_exm_VM/exv_vehicleMonitoring_request.xml @@ -6,7 +6,7 @@ See also simple request for minimal version (C) Copyright 2005-2012 CEN SIRI --> - + @@ -20,7 +20,7 @@ 2004-12-17T09:30:47-05:00 NADER - + 2004-12-17T09:30:47-05:00 VEHPT55 diff --git a/examples/siri_exm_VM/exv_vehicleMonitoring_request_simple.xml b/examples/siri_exm_VM/exv_vehicleMonitoring_request_simple.xml index 8320e4e9..d8b582e5 100644 --- a/examples/siri_exm_VM/exv_vehicleMonitoring_request_simple.xml +++ b/examples/siri_exm_VM/exv_vehicleMonitoring_request_simple.xml @@ -6,12 +6,12 @@ See also verbose request for a more complex version (C) Copyright 2005-2012 CEN SIRI --> - + 2004-12-17T09:30:47-05:00 NADER - + 2004-12-17T09:30:47-05:00 VEHPT55 diff --git a/examples/siri_exm_VM/exv_vehicleMonitoring_response.xml b/examples/siri_exm_VM/exv_vehicleMonitoring_response.xml index 211f5dba..46ec6c3f 100644 --- a/examples/siri_exm_VM/exv_vehicleMonitoring_response.xml +++ b/examples/siri_exm_VM/exv_vehicleMonitoring_response.xml @@ -8,7 +8,7 @@ See also simple response for minimal version (C) Copyright 2005-2012 CEN SIRI --> - + 2004-12-17T09:30:47-05:00 @@ -17,7 +17,7 @@ true false - + 2004-12-17T09:30:47-05:00 NADER 00047 diff --git a/examples/siri_exm_VM/exv_vehicleMonitoring_response_simple.xml b/examples/siri_exm_VM/exv_vehicleMonitoring_response_simple.xml index f4c4c3b5..fa3ddab1 100644 --- a/examples/siri_exm_VM/exv_vehicleMonitoring_response_simple.xml +++ b/examples/siri_exm_VM/exv_vehicleMonitoring_response_simple.xml @@ -6,13 +6,13 @@ See also verbose response for complex version (C) Copyright 2005-2012 CEN SIRI --> - + 2004-12-17T09:30:47-05:00 NADER - + 2004-12-17T09:30:47-05:00 NADER 00047 diff --git a/examples/siri_exm_VM/exv_vehicleMonitoring_responsex_simple.xml b/examples/siri_exm_VM/exv_vehicleMonitoring_responsex_simple.xml index f4c4c3b5..fa3ddab1 100644 --- a/examples/siri_exm_VM/exv_vehicleMonitoring_responsex_simple.xml +++ b/examples/siri_exm_VM/exv_vehicleMonitoring_responsex_simple.xml @@ -6,13 +6,13 @@ See also verbose response for complex version (C) Copyright 2005-2012 CEN SIRI --> - + 2004-12-17T09:30:47-05:00 NADER - + 2004-12-17T09:30:47-05:00 NADER 00047 diff --git a/examples/siri_exm_VM/exv_vehicleMonitoring_subscriptionRequest.xml b/examples/siri_exm_VM/exv_vehicleMonitoring_subscriptionRequest.xml index e28fad6e..d385ae88 100644 --- a/examples/siri_exm_VM/exv_vehicleMonitoring_subscriptionRequest.xml +++ b/examples/siri_exm_VM/exv_vehicleMonitoring_subscriptionRequest.xml @@ -1,6 +1,6 @@ - + 2004-12-17T09:30:47-05:00 @@ -10,7 +10,7 @@ 00000456 2004-12-17T09:30:47-05:00 - + 2004-12-17T09:30:47-05:00 VIS123 @@ -20,7 +20,7 @@ 00000457 2004-12-17T09:30:47-05:00 - + 2004-12-17T09:30:47-05:00 diff --git a/examples/siri_exu_capability/exd_allServices_capabilitiesRequest.xml b/examples/siri_exu_capability/exd_allServices_capabilitiesRequest.xml index 16484fe1..40f13a4c 100644 --- a/examples/siri_exu_capability/exd_allServices_capabilitiesRequest.xml +++ b/examples/siri_exu_capability/exd_allServices_capabilitiesRequest.xml @@ -1,37 +1,37 @@ - - + + 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/examples/siri_exu_capability/exd_allServices_capabilitiesResponse.xml b/examples/siri_exu_capability/exd_allServices_capabilitiesResponse.xml index f65d2e7e..74143dac 100644 --- a/examples/siri_exu_capability/exd_allServices_capabilitiesResponse.xml +++ b/examples/siri_exu_capability/exd_allServices_capabilitiesResponse.xml @@ -1,10 +1,10 @@ - - + + 2004-12-17T09:30:47-05:00 KUBRICK - + 2004-12-17T09:30:47-05:00 true @@ -48,7 +48,7 @@ - + 2004-12-17T09:30:47-05:00 true @@ -92,7 +92,7 @@ - + 2004-12-17T09:30:47-05:00 my123 true @@ -135,7 +135,7 @@ - + 2004-12-17T09:30:47-05:00 my123 true @@ -196,7 +196,7 @@ - + 2004-12-17T09:30:47-05:00 abcde true @@ -253,7 +253,7 @@ - + 2004-12-17T09:30:47-05:00 abcde true @@ -298,7 +298,7 @@ - + 2004-12-17T09:30:47-05:00 abcde true @@ -343,7 +343,7 @@ - + 2004-12-17T09:30:47-05:00 abcde true @@ -381,7 +381,7 @@ - + 2004-12-17T09:30:47-05:00 abcde true @@ -437,7 +437,7 @@ - + 2004-12-17T09:30:47-05:00 abcde true diff --git a/examples/siri_exu_discovery/exd_lines_discoveryRequest.xml b/examples/siri_exu_discovery/exd_lines_discoveryRequest.xml index dfb70907..8c7afd68 100644 --- a/examples/siri_exu_discovery/exd_lines_discoveryRequest.xml +++ b/examples/siri_exu_discovery/exd_lines_discoveryRequest.xml @@ -1,7 +1,7 @@ - - + + 2004-12-17T09:30:47-05:00 NADER MYAGENCY diff --git a/examples/siri_exu_discovery/exd_lines_discoveryResponse.xml b/examples/siri_exu_discovery/exd_lines_discoveryResponse.xml index 7e593de1..95868ef5 100644 --- a/examples/siri_exu_discovery/exd_lines_discoveryResponse.xml +++ b/examples/siri_exu_discovery/exd_lines_discoveryResponse.xml @@ -1,7 +1,7 @@ - - + + 2004-12-17T09:30:47-05:00 true diff --git a/examples/siri_exu_discovery/exd_productCategories_discoveryRequest.xml b/examples/siri_exu_discovery/exd_productCategories_discoveryRequest.xml index b43b6308..f44cc2e2 100644 --- a/examples/siri_exu_discovery/exd_productCategories_discoveryRequest.xml +++ b/examples/siri_exu_discovery/exd_productCategories_discoveryRequest.xml @@ -1,7 +1,7 @@ - - + + 2004-12-17T09:30:47-05:00 NADER diff --git a/examples/siri_exu_discovery/exd_productCategories_discoveryResponse.xml b/examples/siri_exu_discovery/exd_productCategories_discoveryResponse.xml index 9ba6abc6..1268e0e7 100644 --- a/examples/siri_exu_discovery/exd_productCategories_discoveryResponse.xml +++ b/examples/siri_exu_discovery/exd_productCategories_discoveryResponse.xml @@ -1,7 +1,7 @@ - - + + 2004-12-17T09:30:47-05:00 true diff --git a/examples/siri_exu_discovery/exd_serviceFeatures_discoveryRequest.xml b/examples/siri_exu_discovery/exd_serviceFeatures_discoveryRequest.xml index 123c7e2e..a92f5f99 100644 --- a/examples/siri_exu_discovery/exd_serviceFeatures_discoveryRequest.xml +++ b/examples/siri_exu_discovery/exd_serviceFeatures_discoveryRequest.xml @@ -1,7 +1,7 @@ - - + + 2004-12-17T09:30:47-05:00 NADER diff --git a/examples/siri_exu_discovery/exd_serviceFeatures_discoveryResponse.xml b/examples/siri_exu_discovery/exd_serviceFeatures_discoveryResponse.xml index a60e8270..743e3484 100644 --- a/examples/siri_exu_discovery/exd_serviceFeatures_discoveryResponse.xml +++ b/examples/siri_exu_discovery/exd_serviceFeatures_discoveryResponse.xml @@ -1,7 +1,7 @@ - - + + 2004-12-17T09:30:47-05:00 true diff --git a/examples/siri_exu_discovery/exd_stopPoints_discoveryRequest.xml b/examples/siri_exu_discovery/exd_stopPoints_discoveryRequest.xml index 70e377e3..1561c216 100644 --- a/examples/siri_exu_discovery/exd_stopPoints_discoveryRequest.xml +++ b/examples/siri_exu_discovery/exd_stopPoints_discoveryRequest.xml @@ -5,8 +5,8 @@ (C) Copyright 2005-2012 CEN SIRI --> - - + + 2004-12-17T09:30:47-05:00 NADER diff --git a/examples/siri_exu_discovery/exd_stopPoints_discoveryResponse.xml b/examples/siri_exu_discovery/exd_stopPoints_discoveryResponse.xml index e385eb56..8f1c01a8 100644 --- a/examples/siri_exu_discovery/exd_stopPoints_discoveryResponse.xml +++ b/examples/siri_exu_discovery/exd_stopPoints_discoveryResponse.xml @@ -1,7 +1,7 @@ - - + + 2004-12-17T09:30:47-05:00 true diff --git a/examples/siri_exu_discovery/exd_vehicleFeatures_discoveryRequest.xml b/examples/siri_exu_discovery/exd_vehicleFeatures_discoveryRequest.xml index 74a921dd..cd5e5274 100644 --- a/examples/siri_exu_discovery/exd_vehicleFeatures_discoveryRequest.xml +++ b/examples/siri_exu_discovery/exd_vehicleFeatures_discoveryRequest.xml @@ -1,7 +1,7 @@ - - + + 2004-12-17T09:30:47-05:00 NADER diff --git a/examples/siri_exu_discovery/exd_vehicleFeatures_discoveryResponse.xml b/examples/siri_exu_discovery/exd_vehicleFeatures_discoveryResponse.xml index 0fc767a5..78f8af7b 100644 --- a/examples/siri_exu_discovery/exd_vehicleFeatures_discoveryResponse.xml +++ b/examples/siri_exu_discovery/exd_vehicleFeatures_discoveryResponse.xml @@ -1,7 +1,7 @@ - - + + 2004-12-17T09:30:47-05:00 VF01 From 7b08378e76c54f6671f6cb48a8de94aeb31cef1f Mon Sep 17 00:00:00 2001 From: u215619 Date: Thu, 17 Jun 2021 16:53:49 +0200 Subject: [PATCH 277/290] CR-090 fixing spelling in Platform, remove default=true in NotifyUserActionStructure WorkgroupRef and UserRef --- .../VDV736_exm/SX_1010_first_message.xml | 4 ++-- .../VDV736_exm/SX_1022_main_message.xml | 4 ++-- .../VDV736_exm/SX_1135_main_message_update.xml | 4 ++-- .../siri_exm_SX/VDV736_exm/SX_1247_end_message.xml | 4 ++-- .../siri_exm_SX/exx_situationExchangeResponse.xml | 4 ++-- examples/siri_exm_SX/exx_situationExchange_Pt.xml | 2 +- .../siri_exm_SX/exx_situationExchange_response.xml | 4 ++-- .../siri_exm_SX/exx_situationExchange_road.xml | 2 +- xsd/ifopt/ifopt_stop.xsd | 14 ++++++++++++-- xsd/siri_model/siri_situationActions.xsd | 10 +++++----- 10 files changed, 31 insertions(+), 21 deletions(-) diff --git a/examples/siri_exm_SX/VDV736_exm/SX_1010_first_message.xml b/examples/siri_exm_SX/VDV736_exm/SX_1010_first_message.xml index 15022cc5..16534ce6 100644 --- a/examples/siri_exm_SX/VDV736_exm/SX_1010_first_message.xml +++ b/examples/siri_exm_SX/VDV736_exm/SX_1010_first_message.xml @@ -1,5 +1,5 @@ - + 2018-10-04T10:11:00+00:00 ch:VBL @@ -7,7 +7,7 @@ t3xWB5cY3 true false - + 2018-10-04T10:11:00+00:00 ch:VBL 40599x2dsjmu8yjzy diff --git a/examples/siri_exm_SX/VDV736_exm/SX_1022_main_message.xml b/examples/siri_exm_SX/VDV736_exm/SX_1022_main_message.xml index 98975ece..f37ac6dd 100644 --- a/examples/siri_exm_SX/VDV736_exm/SX_1022_main_message.xml +++ b/examples/siri_exm_SX/VDV736_exm/SX_1022_main_message.xml @@ -1,5 +1,5 @@ - + 2018-10-16T10:22:30+00:00 ch:VBL @@ -7,7 +7,7 @@ Pgfkw0GAsg true false - + 2018-10-16T10:22:30+00:00 ch:VBL 40599x2dsjmu8yjzy diff --git a/examples/siri_exm_SX/VDV736_exm/SX_1135_main_message_update.xml b/examples/siri_exm_SX/VDV736_exm/SX_1135_main_message_update.xml index b458303c..1556b96b 100644 --- a/examples/siri_exm_SX/VDV736_exm/SX_1135_main_message_update.xml +++ b/examples/siri_exm_SX/VDV736_exm/SX_1135_main_message_update.xml @@ -1,5 +1,5 @@ - + 2018-10-16T10:22:30+00:00 ch:VBL @@ -7,7 +7,7 @@ Pgfkw0GAsg true false - + 2018-10-16T10:22:30+00:00 ch:VBL 40599x2dsjmu8yjzy diff --git a/examples/siri_exm_SX/VDV736_exm/SX_1247_end_message.xml b/examples/siri_exm_SX/VDV736_exm/SX_1247_end_message.xml index 6010821b..8b7625d0 100644 --- a/examples/siri_exm_SX/VDV736_exm/SX_1247_end_message.xml +++ b/examples/siri_exm_SX/VDV736_exm/SX_1247_end_message.xml @@ -1,5 +1,5 @@ - + 2018-10-04T12:22:00+00:00 ch:VBL @@ -7,7 +7,7 @@ JFI2d2mWP true false - + 2018-10-04T12:22:00+00:00 ch:VBL 40599x2dsjmu8yjzy diff --git a/examples/siri_exm_SX/exx_situationExchangeResponse.xml b/examples/siri_exm_SX/exx_situationExchangeResponse.xml index 3a400eb8..45af095d 100644 --- a/examples/siri_exm_SX/exx_situationExchangeResponse.xml +++ b/examples/siri_exm_SX/exx_situationExchangeResponse.xml @@ -69,7 +69,7 @@ BAR00021 - Platfrom 3 + Platform 3 @@ -169,7 +169,7 @@ BAR00021 - Platfrom 3 + Platform 3 diff --git a/examples/siri_exm_SX/exx_situationExchange_Pt.xml b/examples/siri_exm_SX/exx_situationExchange_Pt.xml index 6300c46d..31355973 100644 --- a/examples/siri_exm_SX/exx_situationExchange_Pt.xml +++ b/examples/siri_exm_SX/exx_situationExchange_Pt.xml @@ -58,7 +58,7 @@ BAR00021 - Platfrom 3 + Platform 3 diff --git a/examples/siri_exm_SX/exx_situationExchange_response.xml b/examples/siri_exm_SX/exx_situationExchange_response.xml index 8646260e..441d422b 100644 --- a/examples/siri_exm_SX/exx_situationExchange_response.xml +++ b/examples/siri_exm_SX/exx_situationExchange_response.xml @@ -69,7 +69,7 @@ BAR00021 - Platfrom 3 + Platform 3 @@ -169,7 +169,7 @@ BAR00021 - Platfrom 3 + Platform 3 diff --git a/examples/siri_exm_SX/exx_situationExchange_road.xml b/examples/siri_exm_SX/exx_situationExchange_road.xml index 8abeeff7..691f7585 100644 --- a/examples/siri_exm_SX/exx_situationExchange_road.xml +++ b/examples/siri_exm_SX/exx_situationExchange_road.xml @@ -58,7 +58,7 @@ BAR00021 - Platfrom 3 + Platform 3 diff --git a/xsd/ifopt/ifopt_stop.xsd b/xsd/ifopt/ifopt_stop.xsd index 7c2def98..0edbd5bd 100644 --- a/xsd/ifopt/ifopt_stop.xsd +++ b/xsd/ifopt/ifopt_stop.xsd @@ -305,7 +305,12 @@ Rail transport, Roads and road transport - + + + + deprecated + + @@ -358,7 +363,12 @@ Rail transport, Roads and road transport - + + + + deprecated + + diff --git a/xsd/siri_model/siri_situationActions.xsd b/xsd/siri_model/siri_situationActions.xsd index eb1f1222..bb40ffb2 100644 --- a/xsd/siri_model/siri_situationActions.xsd +++ b/xsd/siri_model/siri_situationActions.xsd @@ -497,9 +497,9 @@ Rail transport, Roads and road transport - + - Workgroup of user to be notified. Default is 'true'. + Workgroup of user to be notified. @@ -507,9 +507,9 @@ Rail transport, Roads and road transport Name of user to be notified. - + - Reference to a user to be notified. Default is 'true'. + Reference to a user to be notified. @@ -579,7 +579,7 @@ Rail transport, Roads and road transport - The system which created this passenger information. If absent, is the same version as the enclosing Situation + The system which created this passenger information. If absent, the same system as the PtSituationElement.ParticipantRef. From 1642bee2c3bf24fb4b599f7a3c7a7223b093c523 Mon Sep 17 00:00:00 2001 From: u215619 Date: Tue, 22 Jun 2021 07:28:37 +0200 Subject: [PATCH 278/290] CR-084 description aligned to original documentation description --- xsd/siri_model/siri_situation.xsd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xsd/siri_model/siri_situation.xsd b/xsd/siri_model/siri_situation.xsd index 5da7bdf4..7f79a980 100644 --- a/xsd/siri_model/siri_situation.xsd +++ b/xsd/siri_model/siri_situation.xsd @@ -1466,12 +1466,12 @@ Alternatively, AdviceRef can be used to reference a (complete) standardised advi - Whether information about parts of the network identified by Affects should be blocked from computation made by a Journey Planner that has a real-time feed of the SITUATIONs. Default is 'false'; do not suppress. + Whether information about parts of the NETWORK identified by AffectsScope should be blocked from the Journey Planner. Default is false; do not suppress. - Whether information about parts of the network identified by Affects should be blocked from real-time departure info systems. Default is 'false'; do not suppress. + Whether information about parts of the NETWORK identified by AffectsScope should be blocked from real-time departure info systems. Default is false; do not suppress. From 1430620c33335b37707197e19e370b7a3cb4e66c Mon Sep 17 00:00:00 2001 From: u215619 Date: Tue, 6 Jul 2021 17:06:16 +0200 Subject: [PATCH 279/290] Request for changes in https://github.com/SIRI-CEN/SIRI/pull/76 --- .../exd_vehicleFeatures_discoveryResponse.xml | 4 ++-- xsd/acsb/acsb_all.xsd | 2 +- xsd/ifopt/ifopt_allStopPlace.xsd | 2 +- xsd/siri/siri_all_framework.xsd | 2 +- xsd/siri_model/siri_all.xsd | 2 +- xsd/siri_model/siri_all_journeyModel.xsd | 2 +- xsd/siri_model/siri_all_model.xsd | 2 +- xsd/siri_model/siri_all_situation.xsd | 2 +- xsd/siri_model/siri_journey_support.xsd | 2 +- xsd/siri_model/siri_situationActions.xsd | 14 +++++++------- xsd/siri_utility/siri_all_utility.xsd | 2 +- 11 files changed, 18 insertions(+), 18 deletions(-) diff --git a/examples/siri_exu_discovery/exd_vehicleFeatures_discoveryResponse.xml b/examples/siri_exu_discovery/exd_vehicleFeatures_discoveryResponse.xml index 78f8af7b..8741ccfb 100644 --- a/examples/siri_exu_discovery/exd_vehicleFeatures_discoveryResponse.xml +++ b/examples/siri_exu_discovery/exd_vehicleFeatures_discoveryResponse.xml @@ -1,5 +1,5 @@ - + 2004-12-17T09:30:47-05:00 @@ -10,7 +10,7 @@ VF02 - Wheelkchair + Wheelchair spastic.gif diff --git a/xsd/acsb/acsb_all.xsd b/xsd/acsb/acsb_all.xsd index 358a9a71..75a718db 100644 --- a/xsd/acsb/acsb_all.xsd +++ b/xsd/acsb/acsb_all.xsd @@ -1,6 +1,6 @@ diff --git a/xsd/ifopt/ifopt_allStopPlace.xsd b/xsd/ifopt/ifopt_allStopPlace.xsd index b5b91b8f..1458717f 100644 --- a/xsd/ifopt/ifopt_allStopPlace.xsd +++ b/xsd/ifopt/ifopt_allStopPlace.xsd @@ -1,6 +1,6 @@ diff --git a/xsd/siri_model/siri_all.xsd b/xsd/siri_model/siri_all.xsd index 0ab0d00f..268e3964 100644 --- a/xsd/siri_model/siri_all.xsd +++ b/xsd/siri_model/siri_all.xsd @@ -1,6 +1,6 @@ diff --git a/xsd/siri_model/siri_all_journeyModel.xsd b/xsd/siri_model/siri_all_journeyModel.xsd index 48079667..022fcb50 100644 --- a/xsd/siri_model/siri_all_journeyModel.xsd +++ b/xsd/siri_model/siri_all_journeyModel.xsd @@ -1,6 +1,6 @@ diff --git a/xsd/siri_model/siri_all_model.xsd b/xsd/siri_model/siri_all_model.xsd index 984702ec..841cfc9d 100644 --- a/xsd/siri_model/siri_all_model.xsd +++ b/xsd/siri_model/siri_all_model.xsd @@ -1,6 +1,6 @@ diff --git a/xsd/siri_model/siri_all_situation.xsd b/xsd/siri_model/siri_all_situation.xsd index 2c0f6a2c..81156990 100644 --- a/xsd/siri_model/siri_all_situation.xsd +++ b/xsd/siri_model/siri_all_situation.xsd @@ -1,6 +1,6 @@ diff --git a/xsd/siri_model/siri_journey_support.xsd b/xsd/siri_model/siri_journey_support.xsd index 2c368d00..3ebcd139 100644 --- a/xsd/siri_model/siri_journey_support.xsd +++ b/xsd/siri_model/siri_journey_support.xsd @@ -727,7 +727,7 @@ Corresponds to NeTEX TYPE OF SERVICe. - Data has confidence lvel of reliable (3/5). + Data has confidence level of reliable (3/5). diff --git a/xsd/siri_model/siri_situationActions.xsd b/xsd/siri_model/siri_situationActions.xsd index bb40ffb2..8176a710 100644 --- a/xsd/siri_model/siri_situationActions.xsd +++ b/xsd/siri_model/siri_situationActions.xsd @@ -280,9 +280,9 @@ Rail transport, Roads and road transport Include in moving ticker band. Default is 'false'. - + - Include in social NETWORK indicated by this name. Possible value could be "twitter.com", "facebook.com", "vk.com" and so on. Parameters may be specified as Action data. Default is 'false' (SIRI 2.1) + Include in social NETWORK indicated by this name. Possible value could be "twitter.com", "facebook.com", "vk.com" and so on. Parameters may be specified as Action data. (SIRI 2.1) @@ -424,9 +424,9 @@ Rail transport, Roads and road transport - + - MSISDN of user to which to send messages. Default is 'true'. + MSISDN of user to which to send messages. @@ -476,9 +476,9 @@ Rail transport, Roads and road transport Reference to a pager group to be notified. - + - Pager number of pager to be notified. Default is 'true'. + Pager number of pager to be notified. @@ -600,7 +600,7 @@ Rail transport, Roads and road transport - The actual, structured passenger information. + The actual, structured passenger information for a specific TextualContentSize. diff --git a/xsd/siri_utility/siri_all_utility.xsd b/xsd/siri_utility/siri_all_utility.xsd index 6160a385..cea265c9 100644 --- a/xsd/siri_utility/siri_all_utility.xsd +++ b/xsd/siri_utility/siri_all_utility.xsd @@ -1,6 +1,6 @@ From 65af433ec6f85c07d9d77f031e54d5dac61495ec Mon Sep 17 00:00:00 2001 From: u215619 Date: Tue, 23 Nov 2021 15:29:33 +0100 Subject: [PATCH 280/290] init VehicleModesOfTransportEnumeration with new compability values for UmS --- xsd/siri_model/siri_modes.xsd | 168 +++++++++++++++++++++++++++------- 1 file changed, 133 insertions(+), 35 deletions(-) diff --git a/xsd/siri_model/siri_modes.xsd b/xsd/siri_model/siri_modes.xsd index 09304d9e..86e46598 100644 --- a/xsd/siri_model/siri_modes.xsd +++ b/xsd/siri_model/siri_modes.xsd @@ -121,103 +121,201 @@ Rail transport, Roads and road transport Values for ModesOfTransport : TPEG pti_table 01. - + + TPEG pti1_0, deprecated (SIRI 2.1) + - + + TPEG pti1_1, deprecated (SIRI 2.1) + See pti2_x. - - + + See also 'railwayService', deprecated (SIRI 2.1) + + + Value was added in SIRI 2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. + See also 'railwayService'. + + + Value was added in SIRI 2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. + See also 'railwayService'. + + + TPEG pti1_2, deprecated (SIRI 2.1) + See pti3_x. - - + + See also 'coachService', deprecated (SIRI 2.1) + + + TPEG pti1_3, deprecated (SIRI 2.1) + - - + + See also 'suburbanRailwayService', deprecated (SIRI 2.1) + + + TPEG pti1_4, deprecated (SIRI 2.1) + See pti4_x. - - + + See also 'urbanRail', deprecated (SIRI 2.1) + + + TPEG pti1_5, deprecated (SIRI 2.1) + - - + + See also 'metroService', deprecated (SIRI 2.1) + + + TPEG pti1_6, deprecated (SIRI 2.1) + - - + + See also 'undergroundService', deprecated (SIRI 2.1) + + + TPEG pti1_7, deprecated (SIRI 2.1) + See pti5_x. - - + + See also 'busService', deprecated (SIRI 2.1) + + + TPEG pti1_8, deprecated (SIRI 2.1) + - - + + See also 'trolleyBusService', deprecated (SIRI 2.1) + + + TPEG pti1_9, deprecated (SIRI 2.1) + See pti6_x. - - + + See also 'tramService', deprecated (SIRI 2.1) + + + TPEG pti1_10, deprecated (SIRI 2.1) + See pti7_x. - - + + See also 'waterTransportService', deprecated (SIRI 2.1) + + + Value was added in SIRI 2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. + See also 'waterTransportService' + + + TPEG pti1_11, deprecated (SIRI 2.1) + See pti8_x. - - + + See also 'airService', deprecated (SIRI 2.1) + + + TPEG pti1_12, deprecated (SIRI 2.1) + - - + + See also 'waterTransportService', deprecated (SIRI 2.1) + + + TPEG pti1_13, deprecated (SIRI 2.1) + See pti9_x. - - + + Value was added in SIRI 2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. + See also 'telecabinService' + + + Value was added in SIRI 2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. + See also 'telecabinService' + + + Value was added in SIRI 2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. + See also 'telecabinService' + + + See also 'telecabinService', deprecated (SIRI 2.1) + + + TPEG pti1_14, deprecated (SIRI 2.1) + See pti10_x. - - + + See also 'funicalarService', deprecated (SIRI 2.1) + + + TPEG pti1_15, deprecated (SIRI 2.1) + pti11_x. - - + + See also 'taxiService', deprecated (SIRI 2.1) + + + TPEG pti1_16, deprecated (SIRI 2.1) + See pti12_x. + + Value was added in SIRI 2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. + See also 'selfDrive' + + + + TPEG pti1_17, deprecated (SIRI 2.1) - - - + + deprecated (SIRI 2.1) + + + TPEG pti1_18, deprecated (SIRI 2.1) + From e22942f3fbd319780f0724a76b2c3e4a13a0ee0a Mon Sep 17 00:00:00 2001 From: u215619 Date: Wed, 24 Nov 2021 14:08:02 +0100 Subject: [PATCH 281/290] undo deprecated values used in NeTEx, Siri services other than SX --- xsd/siri_model/siri_modes.xsd | 57 +++++++++-------------------------- 1 file changed, 15 insertions(+), 42 deletions(-) diff --git a/xsd/siri_model/siri_modes.xsd b/xsd/siri_model/siri_modes.xsd index 86e46598..bcd34b27 100644 --- a/xsd/siri_model/siri_modes.xsd +++ b/xsd/siri_model/siri_modes.xsd @@ -133,9 +133,7 @@ Rail transport, Roads and road transport See pti2_x. - - See also 'railwayService', deprecated (SIRI 2.1) - + Value was added in SIRI 2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. See also 'railwayService'. @@ -152,16 +150,12 @@ Rail transport, Roads and road transport See pti3_x. - - See also 'coachService', deprecated (SIRI 2.1) - + TPEG pti1_3, deprecated (SIRI 2.1) - - See also 'suburbanRailwayService', deprecated (SIRI 2.1) - + TPEG pti1_4, deprecated (SIRI 2.1) @@ -170,16 +164,12 @@ Rail transport, Roads and road transport See pti4_x. - - See also 'urbanRail', deprecated (SIRI 2.1) - + TPEG pti1_5, deprecated (SIRI 2.1) - - See also 'metroService', deprecated (SIRI 2.1) - + TPEG pti1_6, deprecated (SIRI 2.1) @@ -195,16 +185,12 @@ Rail transport, Roads and road transport See pti5_x. - - See also 'busService', deprecated (SIRI 2.1) - + TPEG pti1_8, deprecated (SIRI 2.1) - - See also 'trolleyBusService', deprecated (SIRI 2.1) - + TPEG pti1_9, deprecated (SIRI 2.1) @@ -213,9 +199,7 @@ Rail transport, Roads and road transport See pti6_x. - - See also 'tramService', deprecated (SIRI 2.1) - + TPEG pti1_10, deprecated (SIRI 2.1) @@ -239,16 +223,12 @@ Rail transport, Roads and road transport See pti8_x. - - See also 'airService', deprecated (SIRI 2.1) - + TPEG pti1_12, deprecated (SIRI 2.1) - - See also 'waterTransportService', deprecated (SIRI 2.1) - + TPEG pti1_13, deprecated (SIRI 2.1) @@ -269,9 +249,8 @@ Rail transport, Roads and road transport Value was added in SIRI 2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. See also 'telecabinService' - - See also 'telecabinService', deprecated (SIRI 2.1) - + + TPEG pti1_14, deprecated (SIRI 2.1) @@ -280,9 +259,7 @@ Rail transport, Roads and road transport See pti10_x. - - See also 'funicalarService', deprecated (SIRI 2.1) - + TPEG pti1_15, deprecated (SIRI 2.1) @@ -291,9 +268,7 @@ Rail transport, Roads and road transport pti11_x. - - See also 'taxiService', deprecated (SIRI 2.1) - + TPEG pti1_16, deprecated (SIRI 2.1) @@ -310,9 +285,7 @@ Rail transport, Roads and road transport TPEG pti1_17, deprecated (SIRI 2.1) - - deprecated (SIRI 2.1) - + TPEG pti1_18, deprecated (SIRI 2.1) From ca53ee595046c52a43ce2ac8d35ad49af5a608bf Mon Sep 17 00:00:00 2001 From: u215619 Date: Sun, 28 Nov 2021 22:48:02 +0100 Subject: [PATCH 282/290] init VehicleModesOfTransportEnumeration with new compability values for UmS --- xsd/siri_model/siri_modes.xsd | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/xsd/siri_model/siri_modes.xsd b/xsd/siri_model/siri_modes.xsd index bcd34b27..d55cc75f 100644 --- a/xsd/siri_model/siri_modes.xsd +++ b/xsd/siri_model/siri_modes.xsd @@ -125,6 +125,10 @@ Rail transport, Roads and road transport TPEG pti1_0, deprecated (SIRI 2.1) + + Value was added in SIRI 2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. + See also 'unknown'. + TPEG pti1_1, deprecated (SIRI 2.1) From 48aeab2f665e2634cd864288ca3b590bf72ad975 Mon Sep 17 00:00:00 2001 From: u215619 Date: Sun, 28 Nov 2021 23:09:34 +0100 Subject: [PATCH 283/290] undo deprecating existing Siri values --- xsd/siri_model/siri_modes.xsd | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/xsd/siri_model/siri_modes.xsd b/xsd/siri_model/siri_modes.xsd index d55cc75f..8aea0afe 100644 --- a/xsd/siri_model/siri_modes.xsd +++ b/xsd/siri_model/siri_modes.xsd @@ -178,9 +178,7 @@ Rail transport, Roads and road transport TPEG pti1_6, deprecated (SIRI 2.1) - - See also 'undergroundService', deprecated (SIRI 2.1) - + TPEG pti1_7, deprecated (SIRI 2.1) @@ -212,9 +210,7 @@ Rail transport, Roads and road transport See pti7_x. - - See also 'waterTransportService', deprecated (SIRI 2.1) - + Value was added in SIRI 2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. See also 'waterTransportService' From 6ca71f213232a077691388065147855507e891f4 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Mon, 21 Feb 2022 23:45:44 +0100 Subject: [PATCH 284/290] harmonize VehicleMode enums with NeTEx and TPEG Pts --- xsd/siri_model/siri_modes.xsd | 2413 +++++++++++++++++++++++++++------ 1 file changed, 2022 insertions(+), 391 deletions(-) diff --git a/xsd/siri_model/siri_modes.xsd b/xsd/siri_model/siri_modes.xsd index 0f1e8d1d..10ed3238 100644 --- a/xsd/siri_model/siri_modes.xsd +++ b/xsd/siri_model/siri_modes.xsd @@ -32,9 +32,10 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - + + Kizoom 2000-2005, CEN 2009-2021 - +
      • Schema derived Derived from the Kizoom XTIS schema
        • @@ -88,7 +89,7 @@ Rail transport, Roads and road transport - Non PT Road Submodes. + Non-PT Road Submodes. @@ -113,565 +114,2056 @@ Rail transport, Roads and road transport - Vehicle mode- Tpeg ModeType pti1. + Vehicle mode or mode of transport. - Values for ModesOfTransport : TPEG pti_table 01. + Values for ModesOfTransport : TPEG Pti01 and Pts001 "ModeOfTransport". - - TPEG pti1_0, deprecated (SIRI 2.1) + + + + + + + (SIRI 2.1) + - - - Value was added in SIRI 2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. - See also 'unknown'. + + + + + + + + (SIRI 2.1) + - - TPEG pti1_1, deprecated (SIRI 2.1) + + + + + (SIRI 2.1) + - + - See pti2_x. + Placeholder value if mode of transport is different from all other enumerations in this list (SIRI 2.1) - same meaning as 'undefinedModeOfTransport'. - - - Value was added in SIRI 2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. - See also 'railwayService'. + + + + + TPEG Pts1_0 - mode of transport is not known to the source system. + - - Value was added in SIRI 2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. - See also 'railwayService'. + + + TPEG Pts1_1 - use 'air' instead. + - - TPEG pti1_2, deprecated (SIRI 2.1) - - + - See pti3_x. + TPEG Pts1_2 (SIRI 2.1) - see also 'cableway'. - - - TPEG pti1_3, deprecated (SIRI 2.1) + + + TPEG Pts1_3 (SIRI 2.1) + - - - - TPEG pti1_4, deprecated (SIRI 2.1) + + + TPEG Pts1_4 (SIRI 2.1) - use 'lift' instead. + + + + + TPEG Pts1_5 - use 'rail' instead. + - See pti4_x. + TPEG Pts1_6 - see also 'urbanRail'. - - - TPEG pti1_5, deprecated (SIRI 2.1) + + + TPEG Pts1_7 (SIRI 2.1) + - - - - TPEG pti1_6, deprecated (SIRI 2.1) + + + TPEG Pts1_8 (SIRI 2.1) + - - - - TPEG pti1_7, deprecated (SIRI 2.1) + + + TPEG Pts1_9 - use 'funicular' instead. + - See pti5_x. + TPEG Pts1_10 - use 'bus' instead. - - - TPEG pti1_8, deprecated (SIRI 2.1) + + + TPEG Pts1_11 (SIRI 2.1) - use 'trolleyBus' instead. + - - - - TPEG pti1_9, deprecated (SIRI 2.1) + + + TPEG Pts1_12 - use 'coach' instead. + - + - See pti6_x. + TPEG Pts1_13 - use 'taxi' instead. - - - TPEG pti1_10, deprecated (SIRI 2.1) + + + TPEG Pts1_14 (SIRI 2.1) + - See pti7_x. + TPEG Pts1_15 - use 'water' instead. - - Value was added in SIRI 2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. - See also 'waterTransportService' + + TPEG Pts1_16 (SIRI 2.1) + - - TPEG pti1_11, deprecated (SIRI 2.1) + + + TPEG Pts1_255 (SIRI 2.1) - mode of transport is not supported in this list. + - + + + + - See pti8_x. + See also 'suburbanRail'. - - - TPEG pti1_12, deprecated (SIRI 2.1) + + + + + See also 'underground'. + - - - - TPEG pti1_13, deprecated (SIRI 2.1) + + + Use 'metro' instead. + - + - See pti9_x. + Use 'trolleyBus' instead. - - Value was added in SIRI 2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. - See also 'telecabinService' + + + Use 'tram' instead. + - - Value was added in SIRI 2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. - See also 'telecabinService' + + + Use 'water' instead. + - - Value was added in SIRI 2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. - See also 'telecabinService' + + + Use 'ferry' instead. + - - - TPEG pti1_14, deprecated (SIRI 2.1) + + See also 'cableway'. + + + + See also 'telecabin'. + - + + + + - See pti10_x. + See also 'all'. - - - TPEG pti1_15, deprecated (SIRI 2.1) + + + + + + deprecated (SIRI 2.1) + - + - pti11_x. + deprecated (SIRI 2.1) - - - TPEG pti1_16, deprecated (SIRI 2.1) + + + deprecated (SIRI 2.1) + - + - See pti12_x. + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) - - Value was added in SIRI 2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. - See also 'selfDrive' + + + deprecated (SIRI 2.1) + - TPEG pti1_17, deprecated (SIRI 2.1) + + deprecated (SIRI 2.1) + - - - TPEG pti1_18, deprecated (SIRI 2.1) + + deprecated (SIRI 2.1) + - - TPEG pti02 Rail submodes loc13. + TPEG Pti02, Pts102 "RailwayService" and train link loc13 submodes. - Values for Rail ModesOfTransport: TPEG pti_table_02, train link loc_table_13. + Values for Rail ModesOfTransport: TPEG pti_table_02, pts_table_102 "RailwayService" and train link loc_table_13. - - - - - - - - - - - - - - - - - + + + + TPEG Pts102_0 - submode of transport is not known to the source system. + + + + + + (SIRI 2.1) + + + - - + + + (SIRI 2.1) + + + + + (SIRI 2.1) + + + + + + TPEG Pts105_6 + + + + + (SIRI 2.1) + + + - + + + (SIRI 2.1) + + - - - - - - - - - - - - - - - - - + + + TPEG Pts105_13 + + + + + (SIRI 2.1) + + + + + (SIRI 2.1) + + - - - - - - - - - + + + - DEPRECATED since SIRI 2.1 + TPEG Pts102_1 - see also 'highSpeedRail'. - - - - - - 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 Pts102_2 (SIRI 2.1) - see also 'international'. + + + + + TPEG Pts102_3 (SIRI 2.1) - see also 'longDistance'. + + + + + TPEG Pts102_4 (SIRI 2.1) + + + + + TPEG Pts105_5 - see also 'interregionalRail'. + + + + + TPEG Pts105_7 (SIRI 2.1) + + + + + TPEG Pts105_8 (SIRI 2.1) - see also 'regionalRail'. + + + + + TPEG Pts105_9 (SIRI 2.1) - see also 'touristRailway'. + + + + + TPEG Pts105_10 (SIRI 2.1) - see also 'railShuttle'. + + + + + TPEG Pts105_11 (SIRI 2.1) + + + + + TPEG Pts105_12 (SIRI 2.1) - see also 'nightRail'. + + + + + TPEG Pts105_14 (SIRI 2.1) - see also 'specialTrain'. + + + + + TPEG Pts105_15 + + + + + TPEG Pts105_17 (SIRI 2.1) - see also 'vehicleRailTransportService'. + + + + + TPEG Pts105_18 (SIRI 2.1) + + + + + TPEG Pts105_19 (SIRI 2.1) - see also 'additionalTrainService'. + + + + + TPEG Pts105_255 (SIRI 2.1) - see also 'undefined'. + + + + + + + See also 'longDistance'. + + + + + + + + + + Submode of transport is not supported in this list. + + + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + + + + TPEG Pti03 and Pts103 "CoachService" submodes. + + + + + Values for Coach ModesOfTransport: TPEG pti_table_03 and pts_table_103. + + + + + + TPEG Pts103_0 - submode of transport is not known to the source system. + + + + + Submode of transport is not supported in this list. + + + + + (SIRI 2.1) - see also 'internationalCoachService'. + + + + + (SIRI 2.1) - see also 'nationalCoachService'. + + + + + (SIRI 2.1) - see also 'shuttleCoachService'. + + + + + (SIRI 2.1) - see also 'regionalCoachService'. + + + + + (SIRI 2.1) - see also 'specialCoachService'. + + + + + (SIRI 2.1) + + + + + (SIRI 2.1) - see also 'sightseeingCoachService'. + + + + + (SIRI 2.1) - see also 'touristCoachService'. + + + + + (SIRI 2.1) - see also 'commuterCoachService'. + + + + + + + TPEG Pts103_1 + + + + + TPEG Pts103_2 + + + + + TPEG Pts103_3 + + + + + TPEG Pts103_4 + + + + + TPEG Pts103_5 (SIRI 2.1) + + + + + TPEG Pts103_6 (SIRI 2.1) + + + + + TPEG Pts103_7 + + + + + TPEG Pts103_8 + + + + + TPEG Pts103_9 + + + + + TPEG Pts103_10 + + + + + TPEG Pts103_11 (SIRI 2.1) + + + + + TPEG Pts103_255 (SIRI 2.1) - see also 'undefined'. + + + + + + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + + + + TPEG Pti04 metro and Pts104 "UrbanRailwayService" submodes. + + + + + Values for Metro ModesOfTransport: TPEG pti_table_04 and pts_table_104. + + + + + + + TPEG Pts104_0 - submode of transport is not known to the source system. + + + + + Submode of transport is not supported in this list. + + + + + + + + + + + TPEG Pts104_1 (SIRI 2.1) - see also 'metro'. + + + + + TPEG Pts104_2 (SIRI 2.1) + + + + + TPEG Pts104_3 (SIRI 2.1) + + + + + TPEG Pts104_255 (SIRI 2.1) - see also 'undefined'. + + + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + - TPEG pti05 Bus submodes. + TPEG Pti05 and Pts105 "BusService" submodes. - Values for Bus ModesOfTransport: TPEG pti_table_05, loc_table_10. + Values for Bus ModesOfTransport: TPEG pti_table_05, pts_table_105 and loc_table_10. - - - - - + + + + TPEG Pts105_0 - submode of transport is not known to the source system. + + + + + Submode of transport is not supported in this list. + + + + + (SIRI 2.1) - see also 'localBusService'. + + - - - - - - - - - - - - - - - - - - - - + + + (SIRI 2.1) + + + + + (SIRI 2.1) + + - - - - - - - - - - + + + + + TPEG Pts105_1 (SIRI 2.1) - see also 'regionalBus'. + + + + + TPEG Pts105_2 (SIRI 2.1) + + + + + TPEG Pts105_3 (SIRI 2.1) - see also 'expressBus'. + + + + + TPEG Pts105_4 (SIRI 2.1) + + + + + TPEG Pts105_5 (SIRI 2.1) + + + + + TPEG Pts105_6 (SIRI 2.1) - see also 'nightBus'. + + + + + TPEG Pts105_7 (SIRI 2.1) - see also 'postBus'. + + + + + TPEG Pts105_8 (SIRI 2.1) - see also 'specialNeedsBus'. + + + + + TPEG Pts105_9 (SIRI 2.1) - see also 'mobilityBus'. + + + + + TPEG Pts105_10 (SIRI 2.1) - see also 'mobilityBusForRegisteredDisabled'. + + + + + TPEG Pts105_11 (SIRI 2.1) - see also 'sightseeingBus'. + + + + + TPEG Pts105_12 (SIRI 2.1) - see also 'shuttleBus'. + + + + + TPEG Pts105_13 (SIRI 2.1) - see also 'schoolBus'. + + + + + TPEG Pts105_14 (SIRI 2.1) - see also 'schoolAndPublicServiceBus'. + + + + + TPEG Pts105_15 (SIRI 2.1) - see also 'railReplacementBus'. + + + + + TPEG Pts105_16 (SIRI 2.1) - see also 'demandAndResponseBus'. + + + + + TPEG Pts105_255 (SIRI 2.1) - see also 'undefined'. + + + + + + + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + - TPEG pti06 Tram submodes. + TPEG Pti06 tram and Pts104 "UrbanRailwayService" submodes. - Values for Tram ModesOfTransport: TPEG pti_table_06, loc_table_12. + Values for Tram ModesOfTransport: TPEG pti_table_06, pts_table_104 and loc_table_12. - - - - - + + + + TPEG Pts104_0 - submode of transport is not known to the source system. + + + + + (SIRI 2.1) - see also 'undefinedTramService'. + + - + + + (SIRI 2.1) - see also 'localTramService'. + + + + + + + + (SIRI 2.1) + + + + + + + TPEG Pts104_4 (SIRI 2.1) + + + + + TPEG Pts104_5 (SIRI 2.1) - see also 'cityTram'. + + + + + TPEG Pts104_6 (SIRI 2.1) - see also 'regionalTram'. + + + + + TPEG Pts104_7 (SIRI 2.1) - see also 'sightseeingTram'. + + + + + TPEG Pts104_8 (SIRI 2.1) + + + + + TPEG Pts104_9 (SIRI 2.1) - see also 'shuttleTram'. + + + + + TPEG Pts104_255 (SIRI 2.1) - see also 'undefined'. + + + + - - - - - - - - + + + Submode of transport is not supported in this list. + + - - - + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + - TPEG pti07 Water submodes. + TPEG Pti07 and Pts107 "WaterTransportService" submodes. - Values for Water ModesOfTransport: TPEG pti_table_07. + Values for Water ModesOfTransport: TPEG pti_table_07 and pts_table_107. - - - - - - - - - - - + + + + TPEG Pts107_0 - submode of transport is not known to the source system. + + + + + (SIRI 2.1) - see also 'undefinedWaterTransport'. + + + + + (SIRI 2.1) - see also 'internationalCarFerryService'. + + + + + (SIRI 2.1) - see also 'nationalCarFerryService'. + + + + + (SIRI 2.1) - see also 'regionalCarFerryService'. + + + + + (SIRI 2.1) - see also 'localCarFerryService'. + + - - - - - - - - - - - - - - - - + + + (SIRI 2.1) + + + + + + + TPEG Pts107_2 + + + + + TPEG Pts107_3 + + + + + TPEG Pts107_4 + + + + + TPEG Pts107_5 + + + + + TPEG Pts107_6 (SIRI 2.1) - see also 'internationalPassengerFerry'. + + + + + TPEG Pts107_7 (SIRI 2.1) - see also 'nationalPassengerFerry'. + + + + + TPEG Pts107_8 (SIRI 2.1) - see also 'regionalPassengerFerry'. + + + + + TPEG Pts107_9 (SIRI 2.1) - see also 'localPassengerFerry'. + + + + + TPEG Pts107_10 (SIRI 2.1) - see also 'postBoat'. + + + + + TPEG Pts107_11 (SIRI 2.1) - see also 'trainFerry'. + + + + + TPEG Pts107_12 (SIRI 2.1) - see also 'roadFerryLink'. + + + + + TPEG Pts107_13 (SIRI 2.1) - see also 'airportBoatLink'. + + + + + TPEG Pts107_14 (SIRI 2.1) - see also 'highSpeedVehicleService'. + + + + + TPEG Pts107_15 (SIRI 2.1) - see also 'highSpeedPassengerService'. + + + + + TPEG Pts107_16 (SIRI 2.1) - see also 'scheduledFerry'. + + + + + TPEG Pts107_17 (SIRI 2.1) + + + + + TPEG Pts107_18 (SIRI 2.1) + + + + + TPEG Pts107_19 (SIRI 2.1) - see also 'sightseeingService'. + + + + + TPEG Pts107_20 (SIRI 2.1) - see also 'schoolBoat'. + + + + + TPEG Pts107_21 (SIRI 2.1) - see also 'riverBus'. + + + + + TPEG Pts107_22 (SIRI 2.1) - see also 'scheduledFerry'. + + + + + TPEG Pts107_23 (SIRI 2.1) - see also 'shuttleFerry'. + + + + + TPEG Pts107_255 (SIRI 2.1) - see also 'undefinedWaterTransport'. + + + + + + + Submode of transport is not supported in this list. + + - - + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + - TPEG pti08 Air submodes. + TPEG Pti08 and Pts108 "AirService" submodes. - Values for Air ModesOfTransport: TPEG pti_table_08. + Values for Air ModesOfTransport: TPEG pti_table_08 and pts_table_108. - - - - - + + + + TPEG Pts108_0 - submode of transport is not known to the source system. + + + + + (SIRI 2.1) - see also 'undefinedAircraftService'. + + - - - - - - - - - - - - - - - - - - - - - - + + + TPEG Pts108_13 + + + + + + + + TPEG Pts108_1 (SIRI 2.1) - see also 'internationalFlight'. + + + + + TPEG Pts108_2 (SIRI 2.1) - see also 'domesticFlight'. + + + + + TPEG Pts108_3 (SIRI 2.1) - see also 'intercontinentalFlight'. + + + + + TPEG Pts108_4 (SIRI 2.1) - see also 'domesticScheduledFlight'. + + + + + TPEG Pts108_5 (SIRI 2.1) - see also 'shuttleFlight'. + + + + + TPEG Pts108_6 (SIRI 2.1) - see also 'intercontinentalCharterFlight'. + + + + + TPEG Pts108_7 (SIRI 2.1) - see also 'intercontinentalCharterFlight'. + + + + + TPEG Pts108_8 (SIRI 2.1) - see also 'roundTripCharterFlight'. + + + + + TPEG Pts108_9 (SIRI 2.1) - see also 'sightseeingFlight'. + + + + + TPEG Pts108_10 (SIRI 2.1) - see also 'helicopterService'. + + + + + TPEG Pts108_11 (SIRI 2.1) - see also 'domesticCharterFlight'. + + + + + TPEG Pts108_12 (SIRI 2.1) - see also 'SchengenAreaFlight'. + + + + + TPEG Pts108_14 (SIRI 2.1) + + + + + TPEG Pts108_15 (SIRI 2.1) - see also 'undefinedAircraftService'. + + + + + + + Submode of transport is not supported in this list. + + - - - - - + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + - TPEG pti09 Telecabin submodes. + TPEG Pti09 telecabin and Pts109 "GondolaCableCarService" submodes. - Values for Telecabin ModesOfTransport: TPEG pti_table_09, loc_table_14. + Values for Telecabin ModesOfTransport: TPEG pti_table_09, pts_table_109 and loc_table_14. - - - - - + + + + TPEG Pts109_0 - submode of transport is not known to the source system. + + + + + Submode of transport is not supported in this list. + + - - - - - - - - - + + + + + + TPEG Pts109_1 (SIRI 2.1) + + + + + TPEG Pts109_2 (SIRI 2.1) + + + + + TPEG Pts109_255 (SIRI 2.1) - see also 'undefined'. + + + + - - - - - - - - + + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + @@ -685,15 +2177,53 @@ Rail transport, Roads and road transport Values for Funicular ModesOfTransport: TPEG pti_table_10. - - - - + + + + Submode of transport is not known to the source system. + + - + + + (SIRI 2.1) + + - - + + + Submode of transport is not supported in this list. + + + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + + + deprecated (SIRI 2.1) + + @@ -707,24 +2237,81 @@ Rail transport, Roads and road transport Values for Taxi ModesOfTransport: TPEG pti_table_11. - - - + + + + Submode of transport is not known to the source system. + + + + + (SIRI 2.1) - see also 'undefinedTaxiService'. + + - + + + (SIRI 2.1) + + - - - - - - - + + + Submode of transport is not supported in this list. + + + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + @@ -738,20 +2325,64 @@ Rail transport, Roads and road transport Values for SelfDrive ModesOfTransport: TPEG pti_table_12. - - - + + + + Submode of transport is not known to the source system. + + + + + (SIRI 2.1) - see also 'undefinedHireVehicle'. + + - - - - - - + + + Submode of transport is not supported in this list. + + + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + + + + deprecated (SIRI 2.1) + + From eee58e9d3e2f5fa3d8aa9f2935f150ab4395c2f0 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 22 Feb 2022 00:36:32 +0100 Subject: [PATCH 285/290] siri_modes.xsd:289 element annotation fix --- xsd/siri_model/siri_modes.xsd | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/xsd/siri_model/siri_modes.xsd b/xsd/siri_model/siri_modes.xsd index 10ed3238..8e8592da 100644 --- a/xsd/siri_model/siri_modes.xsd +++ b/xsd/siri_model/siri_modes.xsd @@ -285,10 +285,11 @@ Rail transport, Roads and road transport Use 'ferry' instead. - - - See also 'cableway'. - + + + See also 'cableway'. + + See also 'telecabin'. From 381dc925fcf99be6fb77c6bcfbe10f6cb28b0cc6 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 2 Mar 2022 11:56:13 +0100 Subject: [PATCH 286/290] issues/78: add choice for new occupancy/capacity model to Monitored-/OnwardCall of VM --- xsd/siri_model/siri_journey.xsd | 84 ++++++++++++++++++--------------- 1 file changed, 46 insertions(+), 38 deletions(-) diff --git a/xsd/siri_model/siri_journey.xsd b/xsd/siri_model/siri_journey.xsd index 8284d2b8..0dc06c7a 100644 --- a/xsd/siri_model/siri_journey.xsd +++ b/xsd/siri_model/siri_journey.xsd @@ -34,35 +34,35 @@ 2012-03-22 + [VDV] Add EarliestExpectedArrivalTimeForVehicle to Arrival Times Group + [VDV] Add ProvisionalExpectedDepartureTime to Departure Times Group + [VDV] Add LatestExpectedArrivalTimeForVehicle to Departure Times Group + [VDV] Add ViaPriority to ViaNames using a new ViaNameStructure SIRI-PT, SIRI-ET, SIRI-SM. SIRI-VM + [VDV] Add Velocity to MonitoredVehicleJourney SIRI-SM and SIRI-VM + Add JOURNEY PARTs to Vehicle INFO TODO + [VDV] Add Public and Contact Details to JourneyInfo : SIRI-PT, SIRI-ET, SIRI-SM. SIRI-VM + [VDV] at DirectionAtOrigin name to JourneyInfo SIRI-PT, SIRI-ET, SIRI-SM. SIRI-VM + + [MTA] Add ArrivalProximityText to Arrival Times on MonitoredCall and OnwardsCall : SIRI-SM and SIRI-VM + [MTA] Add ArrivalProximityText to Departure Times on MonitoredCall and OnwardsCall : SIRI-SM and SIRI-VM + + [FR] Add AimedLatestPassengerAccessTime to TargetedCall : SIRI-ST + [FR] Add AimedLatestPassengerAccessTime to MonitoredCall and OnwardsCall : SIRI-SM and SIRI-VM + [FR] Add ExpectedLatestPassengerAccessTime to MonitoredCall and OnwardsCall : SIRI-SM and SIRI-VM + [FR] add ArrivalOperatorRefs and DepartureOperatorRefs to Call arrival and Departure + + [Fr] Add FirstOrLastJourney to JourneyTimesGroup : SIRI-SM and SIRI-VM + [DE] Add Driver Name + --> 2012-04-27 + [DE] Add ExpectedDeparturePredictionQuality to OnwardVehicleDepartureTimes + --> 2013-01-25 @@ -93,10 +93,10 @@ http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd - - - CEN, VDV, RTIG 2004-2021 - + + + CEN, VDV, RTIG 2004-2021 +
        • Derived from the VDV, RTIG CML and Trident standards.
          • @@ -501,8 +501,16 @@ Rail transport, Roads and road transport - - + + + + + + + + + + @@ -1062,27 +1070,27 @@ It is advised to specify a reference point that is meaningful for passengers on - Real-time occupancies of a VEHICLE and reservations after departing from a given stop. +SIRI v2.1 + Expected/Predicted real-time occupancies of a VEHICLE and reservations after departing from a given stop. +SIRI v2.1 - Real-time capacities (number of available seats) of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. +SIRI v2.1 + Expected/Predicted real-time capacities (number of available seats) of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. +SIRI v2.1 - + - OPERATORs of service for departure and onwards. May change from that for arrival. +SIRI v2.0. + Actually recorded/counted occupancies of a VEHICLE and reserved seats after departing from a given stop. +SIRI v2.1 - + - Recorded occupancies of a VEHICLE and reserved seats after departing from a given stop. +SIRI v2.1 + Actually recorded/counted capacities of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. +SIRI v2.1 - + - Recorded capacities of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. +SIRI v2.1 + OPERATORs of service for departure and onwards. May change from that for arrival. +SIRI v2.0. From 506f23e7d89fee4a932f10b3b325133ef76ba110 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 2 Mar 2022 13:46:47 +0100 Subject: [PATCH 287/290] issues/78: add new occupancy/capacity model to PreviousCall of VM --- .../siri_monitoredVehicleJourney.xsd | 87 ++++++++++--------- 1 file changed, 47 insertions(+), 40 deletions(-) diff --git a/xsd/siri_model/siri_monitoredVehicleJourney.xsd b/xsd/siri_model/siri_monitoredVehicleJourney.xsd index a3e2d603..a34f9d26 100644 --- a/xsd/siri_model/siri_monitoredVehicleJourney.xsd +++ b/xsd/siri_model/siri_monitoredVehicleJourney.xsd @@ -23,42 +23,47 @@ 2007-03-29 - 2008-11-13 - - - 2011-04-18 - - - 2012-03-22 - - - 2012-04-27 - - - 2012-04-27 - - + + 2008-11-13 + + + + 2011-04-18 + + + + 2012-03-22 + + + + 2012-04-27 + + + + 2012-04-27 + +

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

          This subschema defines common journey elements.

          @@ -74,10 +79,10 @@ http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd - - - CEN, VDV, RTIG 2004-2021 - + + + CEN, VDV, RTIG 2004-2021 +
          • Derived from the VDV, RTIG CML and Trident standards.
            • @@ -509,6 +514,8 @@ A journey does always have one or more JOURNEY PARTs for which the train formati + + From 2060bdb12bdacf76501c0192ef27e3b0476f85ff Mon Sep 17 00:00:00 2001 From: Adrian A Date: Fri, 6 May 2022 12:20:12 +0200 Subject: [PATCH 288/290] issues/88: make TotalNumberOfReservedSeats optional --- xsd/siri_model/siri_journey.xsd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xsd/siri_model/siri_journey.xsd b/xsd/siri_model/siri_journey.xsd index 0dc06c7a..0282384d 100644 --- a/xsd/siri_model/siri_journey.xsd +++ b/xsd/siri_model/siri_journey.xsd @@ -1522,7 +1522,7 @@ More accurate data can be provided by the individual occupancies or capacities b - + Total number of booked seats from individual and group reservations. From 599c460a5b391511afb8a2cfedf012eb89c79c04 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Wed, 11 May 2022 20:06:44 +0200 Subject: [PATCH 289/290] CR046: add missing references in TrainFormationReferenceGroup --- xsd/siri_model/siri_journey_support.xsd | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/xsd/siri_model/siri_journey_support.xsd b/xsd/siri_model/siri_journey_support.xsd index 3ebcd139..76c7ecdd 100644 --- a/xsd/siri_model/siri_journey_support.xsd +++ b/xsd/siri_model/siri_journey_support.xsd @@ -495,8 +495,14 @@ Has the following uses: - - + + + + + + + + From ce97bedbba540028b8cdf2ea758ffaae3589cb40 Mon Sep 17 00:00:00 2001 From: Adrian A Date: Tue, 25 Oct 2022 15:36:35 +0200 Subject: [PATCH 290/290] harmonize SIRI version references in descriptions --- xsd/datex2/DATEXIISchemaWithDefinitions.xsd | 6 +- xsd/siri.xsd | 2 +- xsd/siri/siri_common_services.xsd | 12 +- xsd/siri/siri_request_errorConditions.xsd | 60 +-- xsd/siri/siri_request_support.xsd | 6 +- xsd/siri/siri_requests.xsd | 24 +- xsd/siri_connectionMonitoring_service.xsd | 6 +- xsd/siri_connectionTimetable_service.xsd | 6 +- xsd/siri_discovery.xsd | 90 ++-- xsd/siri_estimatedTimetable_service.xsd | 14 +- xsd/siri_facilityMonitoring_service.xsd | 2 +- xsd/siri_generalMessage_service.xsd | 2 +- xsd/siri_model/siri_datedVehicleJourney.xsd | 44 +- .../siri_estimatedVehicleJourney.xsd | 47 +- xsd/siri_model/siri_facility.xsd | 6 +- xsd/siri_model/siri_interchangeJourney.xsd | 2 +- xsd/siri_model/siri_journey.xsd | 220 ++++----- xsd/siri_model/siri_journey_support.xsd | 58 +-- xsd/siri_model/siri_modelPermissions.xsd | 4 +- xsd/siri_model/siri_modes.xsd | 426 +++++++++--------- .../siri_monitoredVehicleJourney.xsd | 40 +- xsd/siri_model/siri_reference.xsd | 10 +- xsd/siri_model/siri_situation.xsd | 10 +- xsd/siri_model/siri_situationAffects.xsd | 30 +- xsd/siri_model/siri_situationClassifiers.xsd | 38 +- xsd/siri_model/siri_situationReasons.xsd | 220 ++++----- xsd/siri_model/siri_situationServiceTypes.xsd | 54 +-- .../siri_targetedVehicleJourney.xsd | 2 +- xsd/siri_model/siri_time.xsd | 2 +- xsd/siri_model_discovery/siri_line.xsd | 12 +- xsd/siri_model_discovery/siri_stopPoint.xsd | 2 +- xsd/siri_productionTimetable_service.xsd | 14 +- xsd/siri_situationExchange_service.xsd | 12 +- xsd/siri_stopMonitoring_service.xsd | 28 +- xsd/siri_stopTimetable_service.xsd | 2 +- xsd/siri_utility/siri_location.xsd | 10 +- xsd/siri_utility/siri_utility.xsd | 32 +- xsd/siri_vehicleMonitoring_service.xsd | 20 +- 38 files changed, 787 insertions(+), 788 deletions(-) diff --git a/xsd/datex2/DATEXIISchemaWithDefinitions.xsd b/xsd/datex2/DATEXIISchemaWithDefinitions.xsd index 500aa072..defb867e 100644 --- a/xsd/datex2/DATEXIISchemaWithDefinitions.xsd +++ b/xsd/datex2/DATEXIISchemaWithDefinitions.xsd @@ -8286,7 +8286,7 @@ - Value was added in SIRI 2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. See also 'microwaveMonitoringStation' + See also 'microwaveMonitoringStation' @@ -8301,7 +8301,7 @@ - Value was added in SIRI 2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. See also 'nonPoliceEmergencyServicePatrol' + See also 'nonPoliceEmergencyServicePatrol' @@ -8336,7 +8336,7 @@ - Value was added in SIRI 2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. See also 'registeredMotoristObserver' + See also 'registeredMotoristObserver' diff --git a/xsd/siri.xsd b/xsd/siri.xsd index e495ed0e..27b085e0 100644 --- a/xsd/siri.xsd +++ b/xsd/siri.xsd @@ -96,7 +96,7 @@ mailto:schemer@siri.org.uk Correct delegation elements--> 2014-03-31 - diff --git a/xsd/siri/siri_common_services.xsd b/xsd/siri/siri_common_services.xsd index 254c18cf..2ec9aa86 100644 --- a/xsd/siri/siri_common_services.xsd +++ b/xsd/siri/siri_common_services.xsd @@ -30,17 +30,17 @@ -- Revise for substitution groups and move down to siri subdirectory 2012-03-23 - +SIRI v2.0 + (since SIRI 2.0) - Add DataReady to Check Status - Add DistanceUnits and VelocityUnits to ServiceRequestContext - [FR] Add Extensions tag to Terminate SubscriptionRequest 2014-03-31 - +SIRI v2.0 Comments + (since SIRI 2.0) Comments - Add terminate subscription notification 2014-06-23 - +SIRI v2.0 Comments + (since SIRI 2.0) Comments - Revise terminate subscription erroc condition to be consistent with other services @@ -345,12 +345,12 @@ Rail transport, Roads and road transport - Units for Distance Type. Default is metres. +SIRI v2.0 + Units for Distance Type. Default is metres. (since SIRI 2.0) - Units for Distance Type. Default is metres per second. +SIRI v2.0 + Units for Distance Type. Default is metres per second. (since SIRI 2.0) @@ -395,7 +395,7 @@ Rail transport, Roads and road transport - If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 + If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. (since SIRI 2.0) diff --git a/xsd/siri/siri_request_errorConditions.xsd b/xsd/siri/siri_request_errorConditions.xsd index 555f32f6..581abebd 100644 --- a/xsd/siri/siri_request_errorConditions.xsd +++ b/xsd/siri/siri_request_errorConditions.xsd @@ -26,15 +26,15 @@ Add new error conditions - UnknownParticipant Recipient for a message to be distributed is unknown. +SIRI v2.0 - UnknownEndpoint Endpoint to which a message is to be distributed is unknown. +SIRI v2.0 - EndpointDeniedAccess Distribution message could not be delivered because not authorised.. +SIRI v2.0 - EndpointNotAvailable Recipient of a message to be distributed is not available. +SIRI v2.0 - UnapprovedKey User authorisation Key is not enabled. +SIRI v2.0 + UnknownParticipant Recipient for a message to be distributed is unknown. (since SIRI 2.0) + UnknownEndpoint Endpoint to which a message is to be distributed is unknown. (since SIRI 2.0) + EndpointDeniedAccess Distribution message could not be delivered because not authorised.. (since SIRI 2.0) + EndpointNotAvailable Recipient of a message to be distributed is not available. (since SIRI 2.0) + UnapprovedKey User authorisation Key is not enabled. (since SIRI 2.0) - InvalidDataReferences Request contains references to identifiers that are not known. +SIRI v2.0 - ParametersIgnored Request contained parameters that were not supported by the producer. A response has been provided but some parameters have been ignored. +SIRI v2.0 - UnknownExtensions Request contained extensions that were not supported bu the producer. A response has been provided but some or all extensions have been ignored.. +SIRI v2.0 --> + InvalidDataReferences Request contains references to identifiers that are not known. (since SIRI 2.0) + ParametersIgnored Request contained parameters that were not supported by the producer. A response has been provided but some parameters have been ignored. (since SIRI 2.0) + UnknownExtensions Request contained extensions that were not supported bu the producer. A response has been provided but some or all extensions have been ignored.. (since SIRI 2.0) --> 2012-03-23 @@ -204,16 +204,16 @@ Rail transport, Roads and road transport - + - Errors that may arise in the execution of a delegated distribution request. +SIRI v2.0 + Errors that may arise in the execution of a delegated distribution request. (since SIRI 2.0) - Error: Recipient for a message to be distributed is unknown. I.e. delegatior is found, but +SIRI v2.0 + Error: Recipient for a message to be distributed is unknown. I.e. delegatior is found, but (since SIRI 2.0) @@ -224,12 +224,12 @@ Rail transport, Roads and road transport - Error:Recipient of a message to be distributed is not available. +SIRI v2.0 + Error:Recipient of a message to be distributed is not available. (since SIRI 2.0) - Type for Error: UnapprovedKey +SIRI v2.0 + Type for Error: UnapprovedKey (since SIRI 2.0) @@ -246,12 +246,12 @@ Rail transport, Roads and road transport - Error: Recipient for a message to be distributed is unknown. +SIRI v2.0 + Error: Recipient for a message to be distributed is unknown. (since SIRI 2.0) - Type for Error: Unknown Participant. +SIRI v2.0 + Type for Error: Unknown Participant. (since SIRI 2.0) @@ -268,12 +268,12 @@ Rail transport, Roads and road transport - Error: Recipient for a message to be distributed is unknown. +SIRI v2.0 + Error: Recipient for a message to be distributed is unknown. (since SIRI 2.0) - Type for Error: Unknown Endpoint +SIRI v2.0 + Type for Error: Unknown Endpoint (since SIRI 2.0) @@ -290,12 +290,12 @@ Rail transport, Roads and road transport - Error:Endpoint to which a message is to be distributed did not allow access by the cloient. +SIRI v2.0 + Error:Endpoint to which a message is to be distributed did not allow access by the cloient. (since SIRI 2.0) - Type for Error: EndpointDeniedAccess +SIRI v2.0 + Type for Error: EndpointDeniedAccess (since SIRI 2.0) @@ -312,12 +312,12 @@ Rail transport, Roads and road transport - Error:Recipient of a message to be distributed is not available. +SIRI v2.0 + Error:Recipient of a message to be distributed is not available. (since SIRI 2.0) - Type for Error: EndpointNotAvailable +SIRI v2.0 + Type for Error: EndpointNotAvailable (since SIRI 2.0) @@ -344,14 +344,14 @@ Rail transport, Roads and road transport - Error: Data period or subscription period is outside of period covered by service. +SIRI v2.0. + Error: Data period or subscription period is outside of period covered by service. (since SIRI 2.0). - Error: Request contained extensions that were not supported by the producer. A response has been provided but some or all extensions have been ignored. +SIRI v2.0. + Error: Request contained extensions that were not supported by the producer. A response has been provided but some or all extensions have been ignored. (since SIRI 2.0). @@ -373,7 +373,7 @@ Rail transport, Roads and road transport - Expected time fro reavailability of servcie. +SIRI v2.0 + Expected time fro reavailability of servcie. (since SIRI 2.0) @@ -448,12 +448,12 @@ Rail transport, Roads and road transport - Error: Request contains references to identifiers that are not known. +SIRI v2.0. + Error: Request contains references to identifiers that are not known. (since SIRI 2.0). - Type for InvalidDataReferencesError:. +SIRI v2.0. + Type for InvalidDataReferencesError:. (since SIRI 2.0). @@ -470,12 +470,12 @@ Rail transport, Roads and road transport - Error: Request contained parameters that were not supported by the producer. A response has been provided but some parameters have been ignored. +SIRI v2.0. + Error: Request contained parameters that were not supported by the producer. A response has been provided but some parameters have been ignored. (since SIRI 2.0). - Type for Parameters Ignored Error:. +SIRI v2.0. + Type for Parameters Ignored Error:. (since SIRI 2.0). @@ -492,12 +492,12 @@ Rail transport, Roads and road transport - Error: Request contained extensions that were not supported by the producer. A response has been provided but some or all extensions have been ignored.. +SIRI v2.0. + Error: Request contained extensions that were not supported by the producer. A response has been provided but some or all extensions have been ignored.. (since SIRI 2.0). - Type for Unknown Extensions Error:. +SIRI v2.0. + Type for Unknown Extensions Error:. (since SIRI 2.0). diff --git a/xsd/siri/siri_request_support.xsd b/xsd/siri/siri_request_support.xsd index ca07a583..00aabbc7 100644 --- a/xsd/siri/siri_request_support.xsd +++ b/xsd/siri/siri_request_support.xsd @@ -155,17 +155,17 @@ Where multiple values are returned The first element returned will be used as th - Whether SERVICE JOURNEY INTERCHANGE data is to be transmitted or not. Default is 'true'. +SIRI v2.1 + Whether SERVICE JOURNEY INTERCHANGE data is to be transmitted or not. Default is 'true'. (since SIRI 2.1) - Whether JOURNEY RELATION data is to be transmitted or not. Default is 'true'. +SIRI v2.1 + Whether JOURNEY RELATION data is to be transmitted or not. Default is 'true'. (since SIRI 2.1) - Whether TRAIN (ELEMENT), COMPOUND TRAIN and TRAIN STOP ASSIGNMENT data is to be transmitted or not. Default is 'true'. +SIRI v2.1 + Whether TRAIN (ELEMENT), COMPOUND TRAIN and TRAIN STOP ASSIGNMENT data is to be transmitted or not. Default is 'true'. (since SIRI 2.1) diff --git a/xsd/siri/siri_requests.xsd b/xsd/siri/siri_requests.xsd index 3c72224c..75abe55a 100644 --- a/xsd/siri/siri_requests.xsd +++ b/xsd/siri/siri_requests.xsd @@ -154,17 +154,17 @@ Roads and road transport - Elemenst for authecticiation. +SIRI v2.0 + Elemenst for authecticiation. (since SIRI 2.0) - Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . +SIRI v2.0 + Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) - Authentication key for request. May be used to authenticate requests from a particular account. +SIRI v2.0 + Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) @@ -180,7 +180,7 @@ Roads and road transport - If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 + If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. (since SIRI 2.0) @@ -212,12 +212,12 @@ Roads and road transport - Address of original Consumer, i.e. requesting system to which delegating response is to be returned. +SIRI 2.0 + Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) - Identifier of delegating system that originated message. +SIRI 2.0 + Identifier of delegating system that originated message. (since SIRI 2.0) @@ -295,7 +295,7 @@ Roads and road transport By using this element, the subscriber asks the data provider for an extension of the InitialTerminationTime of the subscription. -If SubscriptionRenewal is omitted, this request is to be treated as a re-subscription and therefore all data corresponding to the SubscriptionRequest must be sent in the initial response (or a portion of the data if MoreData is set to 'true'). +SIRI v2.1 +If SubscriptionRenewal is omitted, this request is to be treated as a re-subscription and therefore all data corresponding to the SubscriptionRequest must be sent in the initial response (or a portion of the data if MoreData is set to 'true'). (since SIRI 2.1) @@ -400,7 +400,7 @@ If SubscriptionRenewal is omitted, this request is to be treated as a re-subscri - If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 + If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. (since SIRI 2.0) @@ -575,7 +575,7 @@ If SubscriptionRenewal is omitted, this request is to be treated as a re-subscri - If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 + If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. (since SIRI 2.0) @@ -609,7 +609,7 @@ If SubscriptionRenewal is omitted, this request is to be treated as a re-subscri - If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 + If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. (since SIRI 2.0) @@ -689,7 +689,7 @@ If SubscriptionRenewal is omitted, this request is to be treated as a re-subscri - If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 + If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. (since SIRI 2.0) @@ -979,7 +979,7 @@ If SubscriptionRenewal is omitted, this request is to be treated as a re-subscri - Whether producer can provide multiple translations of NL text elements +SIRI 2.0 + Whether producer can provide multiple translations of NL text elements (since SIRI 2.0) diff --git a/xsd/siri_connectionMonitoring_service.xsd b/xsd/siri_connectionMonitoring_service.xsd index bf9c5122..52945aba 100644 --- a/xsd/siri_connectionMonitoring_service.xsd +++ b/xsd/siri_connectionMonitoring_service.xsd @@ -32,11 +32,11 @@ Revise to support substitution groups 2012-03-23 - +SIRI v2.0 + (since SIRI 2.0) Add SuggestedWaitDecisionTime to MonitoredArrival 2012-04-18 - +SIRI v2.0 + (since SIRI 2.0) Add ValidUntil Time to MonitoredFeederArrival * [FR] Add Extensions tag to ConnectionMonitoringSubscriptionRequest @@ -366,7 +366,7 @@ Rail transport, Roads and road transport - Latest time by which the feeder needs informationabout the connection from the distributor as to whether it will wait and for how long. +SIRI v2.0 + Latest time by which the feeder needs informationabout the connection from the distributor as to whether it will wait and for how long. (since SIRI 2.0) diff --git a/xsd/siri_connectionTimetable_service.xsd b/xsd/siri_connectionTimetable_service.xsd index 3acbb411..d9c3d293 100644 --- a/xsd/siri_connectionTimetable_service.xsd +++ b/xsd/siri_connectionTimetable_service.xsd @@ -39,12 +39,12 @@ 2012-03-23 - + 2012-04-18 @@ -251,7 +251,7 @@ Rail transport, Roads and road transport - Time until when data is valid. +SIRI 2.0 + Time until when data is valid. (since SIRI 2.0) diff --git a/xsd/siri_discovery.xsd b/xsd/siri_discovery.xsd index 014476d5..a7f83107 100644 --- a/xsd/siri_discovery.xsd +++ b/xsd/siri_discovery.xsd @@ -39,7 +39,7 @@ 2012-03-23 - @@ -176,12 +176,12 @@ Rail transport, Roads and road transport - Parameters that specify the content to be returned. (+SIRI v2.0) + Parameters that specify the content to be returned. ((since SIRI 2.0)) - Parameters that affect the request processing. Mostly act to reduce the number of stops returned. (+SIRI v2.0) + Parameters that affect the request processing. Mostly act to reduce the number of stops returned. ((since SIRI 2.0)) @@ -197,58 +197,58 @@ Rail transport, Roads and road transport - Parameters that specify the STOP POINTs to be returned. +SIRI v2.0 + Parameters that specify the STOP POINTs to be returned. (since SIRI 2.0) - Rectangle containing stops be returned. (+SIRI v2.0) + Rectangle containing stops be returned. ((since SIRI 2.0)) - Circle containing stops be returned. Point indicates centre, precision indicates radius (+SIRI v2.0) + Circle containing stops be returned. Point indicates centre, precision indicates radius ((since SIRI 2.0)) - Filter the results to include only stops associated with the PLACE . (+SIRI v2.0) + Filter the results to include only stops associated with the PLACE . ((since SIRI 2.0)) - Filter the results to include only stops run by the specified OPERATOR. (+SIRI v2.0) + Filter the results to include only stops run by the specified OPERATOR. ((since SIRI 2.0)) - Filter the results to include only stops for the given LINE. (+SIRI v2.0) + Filter the results to include only stops for the given LINE. ((since SIRI 2.0)) - Parameters that affect the request processing. Mostly act to reduce the number of stops returned. +SIRI v2.0 + Parameters that affect the request processing. Mostly act to reduce the number of stops returned. (since SIRI 2.0) - Preferred languages in which to return text values. +SIRI v2.0 + Preferred languages in which to return text values. (since SIRI 2.0) - Level of detail to include in response. Default is 'normal'. +SIRI v2.0 + Level of detail to include in response. Default is 'normal'. (since SIRI 2.0) - Detail Levels for Stop Points Discovery Request. +SIRI v2.0 + Detail Levels for Stop Points Discovery Request. (since SIRI 2.0) @@ -322,24 +322,24 @@ Rail transport, Roads and road transport - Parameters that specify the LINEs to be returned. +SIRI v2.0 + Parameters that specify the LINEs to be returned. (since SIRI 2.0) - Rectangle containing stops of lines be returned. (+SIRI v2.0) + Rectangle containing stops of lines be returned. ((since SIRI 2.0)) - Circle containing stops for lines be returned. Point indicates centre, precision indicates radius (+SIRI v2.0) + Circle containing stops for lines be returned. Point indicates centre, precision indicates radius ((since SIRI 2.0)) - Filter the results to include only lines for stops assoicated with the place . (+SIRI v2.0) + Filter the results to include only lines for stops assoicated with the place . ((since SIRI 2.0)) @@ -351,31 +351,31 @@ Rail transport, Roads and road transport - Filter the results to include only Stop d run by the specified OPERATOR. (+SIRI v2.0) + Filter the results to include only Stop d run by the specified OPERATOR. ((since SIRI 2.0)) - Parameters that affect the request processing. Mostly act to reduce the number of Linesreturned. +SIRI v2.0 + Parameters that affect the request processing. Mostly act to reduce the number of Linesreturned. (since SIRI 2.0) - Preferred languages in which to return text values. +SIRI v2.0 + Preferred languages in which to return text values. (since SIRI 2.0) - Level of detail to include in response. Default is 'normal'. +SIRI v2.0 + Level of detail to include in response. Default is 'normal'. (since SIRI 2.0) - Detail Levels for Lines Discovery Request. +SIRI v2.0 + Detail Levels for Lines Discovery Request. (since SIRI 2.0) @@ -448,12 +448,12 @@ Rail transport, Roads and road transport - Parameters that affect the request processing. Mostly act to reduce the number of Facilities returned. +SIRI v2.0 + Parameters that affect the request processing. Mostly act to reduce the number of Facilities returned. (since SIRI 2.0) - Preferred languages in which to return text values. +SIRI v2.0 + Preferred languages in which to return text values. (since SIRI 2.0) @@ -510,12 +510,12 @@ Rail transport, Roads and road transport - Parameters that affect the request processing. Mostly act to reduce the number of Facilities returned. +SIRI v2.0 + Parameters that affect the request processing. Mostly act to reduce the number of Facilities returned. (since SIRI 2.0) - Preferred languages in which to return text values. +SIRI v2.0 + Preferred languages in which to return text values. (since SIRI 2.0) @@ -622,53 +622,53 @@ Rail transport, Roads and road transport - Parameters that specify the Facilities to be returned. +SIRI v2.0 + Parameters that specify the Facilities to be returned. (since SIRI 2.0) - Rectangle containing Facilities be returned. (+SIRI v2.0) + Rectangle containing Facilities be returned. ((since SIRI 2.0)) - Filter the results to include only Facilities associated with the TOPOGRAPHIC PLACE . (+SIRI v2.0) + Filter the results to include only Facilities associated with the TOPOGRAPHIC PLACE . ((since SIRI 2.0)) - Filter the results to include only Facilities run by the specified OPERATOR. (+SIRI v2.0) + Filter the results to include only Facilities run by the specified OPERATOR. ((since SIRI 2.0)) - Filter the results to include only Facilities for the given LINE. (+SIRI v2.0) + Filter the results to include only Facilities for the given LINE. ((since SIRI 2.0)) - Parameters that affect the request processing. Mostly act to reduce the number of Facilities returned. +SIRI v2.0 + Parameters that affect the request processing. Mostly act to reduce the number of Facilities returned. (since SIRI 2.0) - Preferred languages in which to return text values. +SIRI v2.0 + Preferred languages in which to return text values. (since SIRI 2.0) - Level of detail to include in response. Default is 'normal'. +SIRI v2.0 + Level of detail to include in response. Default is 'normal'. (since SIRI 2.0) - Detail Levels for Facility Points Request. +SIRI v2.0 + Detail Levels for Facility Points Request. (since SIRI 2.0) @@ -774,12 +774,12 @@ Rail transport, Roads and road transport - Requests a list of the CONNECTION LINKs covered by a Producer. +SIRI v2.0 + Requests a list of the CONNECTION LINKs covered by a Producer. (since SIRI 2.0) - Requests for CONNECTION LINK data for use in service requests. +SIRI v2.0 + Requests for CONNECTION LINK data for use in service requests. (since SIRI 2.0) @@ -798,7 +798,7 @@ Rail transport, Roads and road transport - Parameters that specify the CONNECTION LINKs to be returned. +SIRI v2.0 + Parameters that specify the CONNECTION LINKs to be returned. (since SIRI 2.0) @@ -834,24 +834,24 @@ Rail transport, Roads and road transport - Parameters that affect the request processing. Mostly act to reduce the number of ConnectionLinks returned. +SIRI v2.0 + Parameters that affect the request processing. Mostly act to reduce the number of ConnectionLinks returned. (since SIRI 2.0) - Preferred languages in which to return text values. +SIRI v2.0 + Preferred languages in which to return text values. (since SIRI 2.0) - Level of detail to include in response. Default is 'normal'. +SIRI v2.0 + Level of detail to include in response. Default is 'normal'. (since SIRI 2.0) - Detail Levels for CONNECTION LINKs Discovery Request. +SIRI v2.0 + Detail Levels for CONNECTION LINKs Discovery Request. (since SIRI 2.0) @@ -874,7 +874,7 @@ Rail transport, Roads and road transport - Returns the CONNECTION LINKs covered by a web service. Answers a LINEsRequest. +Siri v2.0 + Returns the CONNECTION LINKs covered by a web service. Answers a LINEsRequest. (since SIRI 2.0) diff --git a/xsd/siri_estimatedTimetable_service.xsd b/xsd/siri_estimatedTimetable_service.xsd index e1e414a3..873dcb08 100644 --- a/xsd/siri_estimatedTimetable_service.xsd +++ b/xsd/siri_estimatedTimetable_service.xsd @@ -37,7 +37,7 @@ Drop use of As Flat Groups for EstimatedCalls 2012-03-23 - +SIRI v2.0 + (since SIRI 2.0) - Add EstimatedServiceJourneyInterchange (i.e. Estimated Connection of VEHICLE) to EstimatedTimetableDelivery - [FR] Add Extensions tag to EstimatedTimetableSubscriptionRequest - [DE] Add ExpectedDeparturePredictionQuality to OnwardVehicleDepartureTimes @@ -169,17 +169,17 @@ Rail transport, Roads and road transport - Filter the results to include only journeys of the specified VEHICLE MODE. +SIRI v2.1 + Filter the results to include only journeys of the specified VEHICLE MODE. (since SIRI 2.1) - Filter the results to include only journeys of the specified TYPE OF PRODUCT CATEGORY. +SIRI v2.1 + Filter the results to include only journeys of the specified TYPE OF PRODUCT CATEGORY. (since SIRI 2.1) - Filter the results to include only journeys with a CALL at the specified STOP POINT. +SIRI v2.1 + Filter the results to include only journeys with a CALL at the specified STOP POINT. (since SIRI 2.1) @@ -251,7 +251,7 @@ Rail transport, Roads and road transport 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 (++SIRI 2.0). +If false each subscription response will contain the full information as specified in this request (+(since SIRI 2.0)). @@ -261,7 +261,7 @@ If false each subscription response will contain the full information as specifi - Indicates whether actual arrival-/departure times should be delivered as incremental updates, i.e. whether RECORDED CALL updates are transmitted immediately after an event occurs. +SIRI v2.1 + Indicates whether actual arrival-/departure times should be delivered as incremental updates, i.e. whether RECORDED CALL updates are transmitted immediately after an event occurs. (since SIRI 2.1) - 'false': Specifies that the data producer should transmit RECORDED CALL data, in particular actual arrival-/departure information as an incremental update immediately after an event occurs (with hysteresis taken into account) as is generally the case. The server will automatically proceed with 'false' if capability is not supported. - 'true': Can be requested if the data traffic is to be reduced and an immediate transmissions is not required in any of the consumer systems. @@ -271,7 +271,7 @@ The server will automatically proceed with 'false' if capability is not supporte - Indicates whether ONLY actual arrival-/departure times should be delivered. In other words, whether all updates related to ESTIMATED CALL should be skipped. +SIRI v2.1 + Indicates whether ONLY actual arrival-/departure times should be delivered. In other words, whether all updates related to ESTIMATED CALL should be skipped. (since SIRI 2.1) - 'false': Specifies that the data producer should transmit ESTIMATED and RECORDED CALL data as an incremental update immediately after an event occurs (with hysteresis taken into account) as is generally the case. The server will automatically proceed with 'false' if capability is not supported. - 'true': Can be requested if a consumer system is only interested in the actual times / recorded events because it only wants to check the performance for example. diff --git a/xsd/siri_facilityMonitoring_service.xsd b/xsd/siri_facilityMonitoring_service.xsd index f675cee6..8e8ce6f0 100644 --- a/xsd/siri_facilityMonitoring_service.xsd +++ b/xsd/siri_facilityMonitoring_service.xsd @@ -26,7 +26,7 @@ Revise in line with FM spec - add filters 2012-03-23 - +SIRI v2.0 + (since SIRI 2.0) Add Extensions tag to FacilityMonitoringSubscriptionRequest diff --git a/xsd/siri_generalMessage_service.xsd b/xsd/siri_generalMessage_service.xsd index dd4bc36f..6b2e5dd6 100644 --- a/xsd/siri_generalMessage_service.xsd +++ b/xsd/siri_generalMessage_service.xsd @@ -41,7 +41,7 @@ 2012-03-23 - +

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

            diff --git a/xsd/siri_model/siri_datedVehicleJourney.xsd b/xsd/siri_model/siri_datedVehicleJourney.xsd index 9539794d..972fb8d7 100644 --- a/xsd/siri_model/siri_datedVehicleJourney.xsd +++ b/xsd/siri_model/siri_datedVehicleJourney.xsd @@ -43,7 +43,7 @@ 2012-03-23 Factor out fropm ProductionTimetable package - +SIRI v2.0 Add ServiceJourneyInterchange (i.e. Monitored Connection) + (since SIRI 2.0) Add ServiceJourneyInterchange (i.e. Monitored Connection) [VDV] Add additional times to TargetedServiceInterchange MinimumTransferTime, MaximimTransferTime, StandardTransferTime, MaximumAUtomaticWaitTime, StandardWaitTime. [VDV] Add Public and Contact Details to JourneyInfo [VDV] Add AimedLatestPassengerAccessTime to TargetedCall @@ -139,7 +139,7 @@ Rail transport, Roads and road transport - Type for previously planned VEHICLE JOURNEY that is removed from the data producer when using incremental updates. +SIRI v2.1 + Type for previously planned VEHICLE JOURNEY that is removed from the data producer when using incremental updates. (since SIRI 2.1) @@ -176,7 +176,7 @@ Rail transport, Roads and road transport - Description of the origin stop (vehicle signage) to show on vehicle, Can be overwritten for a journey, and then also section by section by the entry in an Individual Call. (+SIRI 2.0) + Description of the origin stop (vehicle signage) to show on vehicle, Can be overwritten for a journey, and then also section by section by the entry in an Individual Call. (since SIRI 2.0) @@ -191,7 +191,7 @@ Rail transport, Roads and road transport - Whether journey is first or last jouurney of day. +SIRI v2.0 + Whether journey is first or last jouurney of day. (since SIRI 2.0) @@ -246,7 +246,7 @@ Rail transport, Roads and road transport - A planned SERVICE JOURNEY INTERCHANGE between two journeys. +SIRI v2.0 + A planned SERVICE JOURNEY INTERCHANGE between two journeys. (since SIRI 2.0) @@ -277,7 +277,7 @@ Rail transport, Roads and road transport - A planned SERVICE JOURNEY INTERCHANGE from a journey. +SIRI v2.0 + A planned SERVICE JOURNEY INTERCHANGE from a journey. (since SIRI 2.0) @@ -304,7 +304,7 @@ Rail transport, Roads and road transport - A planned SERVICE JOURNEY INTERCHANGE to a journey. +SIRI v2.0 + A planned SERVICE JOURNEY INTERCHANGE to a journey. (since SIRI 2.0) @@ -331,7 +331,7 @@ Rail transport, Roads and road transport - A planned SERVICE JOURNEY INTERCHANGE between two journeys. +SIRI v2.0 + A planned SERVICE JOURNEY INTERCHANGE between two journeys. (since SIRI 2.0) @@ -362,7 +362,7 @@ Rail transport, Roads and road transport - Type for a previously planned SERVICE JOURNEY INTERCHANGE that a data producer wants to silently remove from the plan (because it is erroneous data). Careful: Removal is different from Cancellation. +SIRI v2.1 + Type for a previously planned SERVICE JOURNEY INTERCHANGE that a data producer wants to silently remove from the plan (because it is erroneous data). Careful: Removal is different from Cancellation. (since SIRI 2.1) @@ -438,7 +438,7 @@ Rail transport, Roads and road transport - Maximum automatic wait time that Distributor will wait for Feeder for INTERCHANGE. +SIRI v2.0 + Maximum automatic wait time that Distributor will wait for Feeder for INTERCHANGE. (since SIRI 2.0) @@ -626,34 +626,34 @@ Rail transport, Roads and road transport - Identifier of SERVICE JOURNEY INTERCHANGE. +SIRI v2.0 + Identifier of SERVICE JOURNEY INTERCHANGE. (since SIRI 2.0) - Whether this interchange is an addition to the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the interchange is not an addition. +SIRI v2.1 + Whether this interchange is an addition to the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the interchange is not an addition. (since SIRI 2.1) Whether this interchange is a cancellation of a previously announced interchange (or planned according to the long-term timetable. -Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the interchange is not cancelled. +SIRI v2.1 +Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the interchange is not cancelled. (since SIRI 2.1)                         - The data producer must provide a reason, e.g. type of error and description, in case he wants to silently remove (instead of cancel) a journey or an interchange from the plan. +SIRI v2.1 + The data producer must provide a reason, e.g. type of error and description, in case he wants to silently remove (instead of cancel) a journey or an interchange from the plan. (since SIRI 2.1) - Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 + Reference to a feeder VEHICLE JOURNEY. (since SIRI 2.0) - SCHEDULED STOP POINT at which feeder journey arrives. +SIRI v2.0 + SCHEDULED STOP POINT at which feeder journey arrives. (since SIRI 2.0) @@ -664,22 +664,22 @@ Can only be used when both participants recognise the same schedule version. If For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. -ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 +ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. (since SIRI 2.1) - Planned time at which feeder VEHICLE is scheduled to arrive. SIRI v2.1 + Planned time at which feeder VEHICLE is scheduled to arrive. (since SIRI 2.1) - Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 + Reference to a feeder VEHICLE JOURNEY. (since SIRI 2.0) - SCHEDULED STOP POINT at which distributor journet departs. +SIRI v2.0 + SCHEDULED STOP POINT at which distributor journet departs. (since SIRI 2.0) @@ -690,12 +690,12 @@ ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL i For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. -ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 +ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. (since SIRI 2.1) - Planned time at which distributor VEHICLE is scheduled to depart. SIRI v2.1 + Planned time at which distributor VEHICLE is scheduled to depart. (since SIRI 2.1) diff --git a/xsd/siri_model/siri_estimatedVehicleJourney.xsd b/xsd/siri_model/siri_estimatedVehicleJourney.xsd index 9cce5107..43c7b16a 100644 --- a/xsd/siri_model/siri_estimatedVehicleJourney.xsd +++ b/xsd/siri_model/siri_estimatedVehicleJourney.xsd @@ -42,7 +42,7 @@ 2012-03-23 - @@ -148,7 +148,7 @@ DEPRECATED from SIRI 2.0 - A real-time SERVICE JOURNEY INTERCHANGE that may be made between the stops of two monitored journeys. It includes the current real-time predicted transfer and wait times. +SIRI v2.0 + A real-time SERVICE JOURNEY INTERCHANGE that may be made between the stops of two monitored journeys. It includes the current real-time predicted transfer and wait times. (since SIRI 2.0) @@ -161,17 +161,17 @@ DEPRECATED from SIRI 2.0 - Identifier of ESTIMATED SERVICE JOURNEY INTERCHANGE in case it is an addition to the plan. +SIRI v2.1 + Identifier of ESTIMATED SERVICE JOURNEY INTERCHANGE in case it is an addition to the plan. (since SIRI 2.1) - Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY INTERCHANGE takes place. +SIRI v2.0 + Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY INTERCHANGE takes place. (since SIRI 2.0) - Reference to a connecting feeder VEHICLE JOURNEY. +SIRI v2.0 + Reference to a connecting feeder VEHICLE JOURNEY. (since SIRI 2.0) @@ -179,7 +179,7 @@ DEPRECATED from SIRI 2.0 SCHEDULED STOP POINT at which feeder journey arrives. Assuming, for example, that the feeder is redirected to another QUAY by a dispositive measure in order to shorten the transfer time, how do we communicate this change in the interchange? If the STOP POINTs are modelled QUAY accurate, FeederArrivalStopRef should always -reference the STOP POINT of the new/expected QUAY (which was transmitted in the ESTIMATED VEHICLE JOURNEY). +SIRI v2.1 +reference the STOP POINT of the new/expected QUAY (which was transmitted in the ESTIMATED VEHICLE JOURNEY). (since SIRI 2.1) @@ -191,24 +191,24 @@ reference the STOP POINT of the new/expected QUAY (which was transmitted in the For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of -despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 +despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. (since SIRI 2.1) - Planned time at which feeder VEHICLE is scheduled to arrive. SIRI v2.1 + Planned time at which feeder VEHICLE is scheduled to arrive. (since SIRI 2.1) - Reference to a connecting distributor VEHICLE JOURNEY. +SIRI v2.0 + Reference to a connecting distributor VEHICLE JOURNEY. (since SIRI 2.0) SCHEDULED STOP POINT at which distributor journey departs. Assuming that the distributor is directed to another QUAY (and that STOP POINTs are modelled QUAY accurate), DistributorDepartureStopRef -should always reference the STOP POINT of the new/expected QUAY (which was transmitted in the ESTIMATED VEHICLE JOURNEY). +SIRI v2.1 +should always reference the STOP POINT of the new/expected QUAY (which was transmitted in the ESTIMATED VEHICLE JOURNEY). (since SIRI 2.1) @@ -220,26 +220,26 @@ should always reference the STOP POINT of the new/expected QUAY (which was trans For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of -despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1 +despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. (since SIRI 2.1) - Planned time at which distributor VEHICLE is scheduled to depart. SIRI v2.1 + Planned time at which distributor VEHICLE is scheduled to depart. (since SIRI 2.1) Properties of SERVICE JOURNEY INTERCHANGE. It is important to note that the InterchangePropertyGroup displays planning data whereas, for example, InterchangeStatus or Will(Not)Wait contain the real-time data. A SERVICE JOURNEY INTERCHANGE may be transmitted with "Guaranteed=true", but also WillNotWait due to major despatching alterations. -However, Will(Not)Wait will always take precedence over the property Guaranteed, which means that WillNotWait breaks the connection regardless of whether Guarateed was transmitted. +SIRI v2.1 +However, Will(Not)Wait will always take precedence over the property Guaranteed, which means that WillNotWait breaks the connection regardless of whether Guarateed was transmitted. (since SIRI 2.1) - Whether this interchange is planned, updated, additional or cancelled. +SIRI v2.1 + Whether this interchange is planned, updated, additional or cancelled. (since SIRI 2.1) @@ -250,30 +250,30 @@ However, Will(Not)Wait will always take precedence over the property Guaranteed, - Details about how (long) the distributor services may be held in order to guarantee the connection. +SIRI v2.0 + Details about how (long) the distributor services may be held in order to guarantee the connection. (since SIRI 2.0) - Time at which feeder VEHICLE is expected to arrive. +SIRI v2.1 + Time at which feeder VEHICLE is expected to arrive. (since SIRI 2.1) - Time at which distributor VEHICLE is expected to depart. +SIRI v2.0 + Time at which distributor VEHICLE is expected to depart. (since SIRI 2.0) - Whether connection monitoring is active or not for this connection. +SIRI v2.0 + Whether connection monitoring is active or not for this connection. (since SIRI 2.0) Contains various types of transfer and wait times of a SERVICE JOURNEY INTERCHANGE. Implementation Note: what happens if, for example, the interchange times and a QUAY change in xxxStopAssignment of the ESTIMATED VEHICLE JOURNEY suggest contradictory transfer/wait times? -In case of doubt, the interchange times are to be favoured because they are transmitted explicitly. +SIRI v2.1 +In case of doubt, the interchange times are to be favoured because they are transmitted explicitly. (since SIRI 2.1) @@ -286,19 +286,18 @@ In case of doubt, the interchange times are to be favoured because they are tran - Time up until which the distributor will wait. +SIRI v2.0 + Time up until which the distributor will wait. (since SIRI 2.0) - Whether an acknowledgement has been received that the driver will wait. -DEPRECATED since SIRI v2.1 + DEPRECATED since SIRI 2.1 - Whether an acknowledgement has been received that the driver will wait. +SIRI v2.1 + Whether an acknowledgement has been received that the driver will wait. (since SIRI 2.1) @@ -312,7 +311,7 @@ DEPRECATED since SIRI v2.1 - Time at which data of individual journey was recorded if differet from that of frame. (+SIRI 2.0.) + Time at which data of individual journey was recorded if differet from that of frame. ((since SIRI 2.0).) diff --git a/xsd/siri_model/siri_facility.xsd b/xsd/siri_model/siri_facility.xsd index 59d54629..84717ed9 100644 --- a/xsd/siri_model/siri_facility.xsd +++ b/xsd/siri_model/siri_facility.xsd @@ -30,7 +30,7 @@ 2012-03-23 - +

            SIRI is a European CEN standard for the exchange of real-time information. @@ -722,7 +722,7 @@ Rail transport, Roads and road transport - Information about a change of the formation (e.g. TRAIN composition) or changes of vehicles within the formation. +SIRI v2.1 + Information about a change of the formation (e.g. TRAIN composition) or changes of vehicles within the formation. (since SIRI 2.1) @@ -742,7 +742,7 @@ Rail transport, Roads and road transport - Classification of vehicle energy type. See Transmodel TypeOfFuel. +SIRI v2.1 + Classification of vehicle energy type. See Transmodel TypeOfFuel. (since SIRI 2.1) diff --git a/xsd/siri_model/siri_interchangeJourney.xsd b/xsd/siri_model/siri_interchangeJourney.xsd index b4d1808f..a95c1549 100644 --- a/xsd/siri_model/siri_interchangeJourney.xsd +++ b/xsd/siri_model/siri_interchangeJourney.xsd @@ -14,7 +14,7 @@ 2012-03-20 - +SIRI v2.0 + (since SIRI 2.0)

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

            diff --git a/xsd/siri_model/siri_journey.xsd b/xsd/siri_model/siri_journey.xsd index 0282384d..9f76c81e 100644 --- a/xsd/siri_model/siri_journey.xsd +++ b/xsd/siri_model/siri_journey.xsd @@ -146,12 +146,12 @@ Rail transport, Roads and road transport - Contact details for use by members of public. +SIRI v2.0 + Contact details for use by members of public. (since SIRI 2.0) - Contact details for use by operational staff. +SIRI v2.0 + Contact details for use by operational staff. (since SIRI 2.0)             @@ -163,12 +163,12 @@ Rail transport, Roads and road transport - Phone number +SIRI v2.0 + Phone number (since SIRI 2.0) - Url for contact +SIRI v2.0 + Url for contact (since SIRI 2.0) @@ -203,7 +203,7 @@ Rail transport, Roads and road transport             - DIRECTION name shown for jurney at the origin. +SIRI v2.0 + DIRECTION name shown for jurney at the origin. (since SIRI 2.0) @@ -228,7 +228,7 @@ Rail transport, Roads and road transport - Origin name shown for jourey at the destination +SIRI v2.0 + Origin name shown for jourey at the destination (since SIRI 2.0) @@ -242,7 +242,7 @@ Rail transport, Roads and road transport - Relative priority to give to VIA name in displays. 1=high. Default is 2. +SIRI v2.0 + Relative priority to give to VIA name in displays. 1=high. Default is 2. (since SIRI 2.0) @@ -308,7 +308,7 @@ Rail transport, Roads and road transport             - Whether journey is first or last journey of day. +SIRI v2.0 + Whether journey is first or last journey of day. (since SIRI 2.0) @@ -349,17 +349,17 @@ Rail transport, Roads and road transport - Refercence to other VEHICLE Journeys (+SIRI v2.0) + Refercence to other VEHICLE Journeys ((since SIRI 2.0)) - A reference to the DRIVER or Crew currently logged in to operate a monitored VEHICLE. May be omitted if real-time data is not available - i.e. it is timetabled data. +SIRI v2.0 + A reference to the DRIVER or Crew currently logged in to operate a monitored VEHICLE. May be omitted if real-time data is not available - i.e. it is timetabled data. (since SIRI 2.0) - The name oo the Driver or Crew +SIRI v2.0 + The name oo the Driver or Crew (since SIRI 2.0) @@ -439,7 +439,7 @@ Rail transport, Roads and road transport - Assignment of planned arrival at scheduled STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. +SIRI v2.0. + Assignment of planned arrival at scheduled STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. (since SIRI 2.0). @@ -480,7 +480,7 @@ Rail transport, Roads and road transport - Assignment of planned, expected and/or recorded arrival at STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. +SIRI v2.0. + Assignment of planned, expected and/or recorded arrival at STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. (since SIRI 2.0). @@ -533,7 +533,7 @@ Rail transport, Roads and road transport - Origin to show for the VEHICLE at the specific stop (vehicle signage), if different to the Origin Name for the full journey. (+Siri 2.0) + Origin to show for the VEHICLE at the specific stop (vehicle signage), if different to the Origin Name for the full journey. (since SIRI 2.0) @@ -606,12 +606,12 @@ Rail transport, Roads and road transport - Latest time at which a VEHICLE will arrive at stop. +SIRI v2.1 + Latest time at which a VEHICLE will arrive at stop. (since SIRI 2.1) - Prediction quality, either as approximate level, or more quantitative percentile range of predictions that will fall within a given range of times. +SIRI v2.0 + Prediction quality, either as approximate level, or more quantitative percentile range of predictions that will fall within a given range of times. (since SIRI 2.0) @@ -623,7 +623,7 @@ Rail transport, Roads and road transport (iii) drop/omit ExpectedArrivalTime (iv) set ArrivalStatus to 'noReport' However, this might introduce ambiguity: e.g. option (iii) might be interpreted as "on time" by one consumer, but also as "indefinite delay" by another consumer. -To avoid this, the producer should transmit xxxPredictionUnknown instead of any expected times. +SIRI v2.1 +To avoid this, the producer should transmit xxxPredictionUnknown instead of any expected times. (since SIRI 2.1) @@ -640,17 +640,17 @@ To avoid this, the producer should transmit xxxPredictionUnknown instead of any - Expected departure time of VEHICLE without waiting time due to operational actions. For people at stop this would normally be shown if different from Expected departure time. So if servcie decides not to wait may leave earler than expected departure time +SIRI v2.0. + Expected departure time of VEHICLE without waiting time due to operational actions. For people at stop this would normally be shown if different from Expected departure time. So if servcie decides not to wait may leave earler than expected departure time (since SIRI 2.0). - Earliest time at which VEHICLE may leave the stop. Used to secure connections. Used for passenger announcements. Passengers must be at boarding point by this time to be sure of catching VEHICLE. i.e. "Vehicle will not leave before this time" - may be revised from original aimed time. +SIRI v2.0 + Earliest time at which VEHICLE may leave the stop. Used to secure connections. Used for passenger announcements. Passengers must be at boarding point by this time to be sure of catching VEHICLE. i.e. "Vehicle will not leave before this time" - may be revised from original aimed time. (since SIRI 2.0) - Prediction quality, either as approximate level, or more quantitative percentile range of predictions that will fall within a given range of times. +SIRI v2.0 + Prediction quality, either as approximate level, or more quantitative percentile range of predictions that will fall within a given range of times. (since SIRI 2.0) @@ -662,7 +662,7 @@ To avoid this, the producer should transmit xxxPredictionUnknown instead of any (iii) drop/omit ExpectedDepartureTime (iv) set DepartureStatus to 'noReport' However, this might introduce ambiguity: e.g. option (iii) might be interpreted as "on time" by one consumer, but also as "indefinite delay" by another consumer. -To avoid this, the producer should transmit xxxPredictionUnknown instead of any expected times. +SIRI v2.1 +To avoid this, the producer should transmit xxxPredictionUnknown instead of any expected times. (since SIRI 2.1) @@ -679,17 +679,17 @@ To avoid this, the producer should transmit xxxPredictionUnknown instead of any             - Elements describing the distance from the stop of a VEHICLE. +SIRI v2.0. + Elements describing the distance from the stop of a VEHICLE. (since SIRI 2.0). - Distance of VEHICLE from stop of CALL as measured along ROUTE track. Only shown if detail level is 'calls' or higher. Positive value denotes distance before stop. +SIRI v2.0. + Distance of VEHICLE from stop of CALL as measured along ROUTE track. Only shown if detail level is 'calls' or higher. Positive value denotes distance before stop. (since SIRI 2.0). - Count of stops along SERVICE PATTERN between current position of VEHICLE and stop of CALL as measured along ROUTE track. Only shown if detail level is 'calls' or higher. +SIRI v2.0. + Count of stops along SERVICE PATTERN between current position of VEHICLE and stop of CALL as measured along ROUTE track. Only shown if detail level is 'calls' or higher. (since SIRI 2.0). @@ -701,23 +701,23 @@ To avoid this, the producer should transmit xxxPredictionUnknown instead of any - An approxiimate characterisation of prediction quality as one of five values. +SIRI v2.0 + An approxiimate characterisation of prediction quality as one of five values. (since SIRI 2.0) - Percentile associated with range as specified by lower and upper bound. +SIRI v2.0 + Percentile associated with range as specified by lower and upper bound. (since SIRI 2.0) - Lower bound on time of prediction for confidence level if different from defaults. +SIRI v2.0 + Lower bound on time of prediction for confidence level if different from defaults. (since SIRI 2.0) - Upper bound on time of prediction for confidence level if different from defaults. +SIRI v2.0 + Upper bound on time of prediction for confidence level if different from defaults. (since SIRI 2.0) @@ -726,23 +726,23 @@ To avoid this, the producer should transmit xxxPredictionUnknown instead of any - Area that encompasses the scheduled flexible stop locations according to the planned timetable. +SIRI v2.1 + Area that encompasses the scheduled flexible stop locations according to the planned timetable. (since SIRI 2.1) - Reference to the scheduled location or flexible area. +SIRI v2.1 + Reference to the scheduled location or flexible area. (since SIRI 2.1) - Name or description (e.g. address) of the scheduled location or flexible area. +SIRI v2.1 + Name or description (e.g. address) of the scheduled location or flexible area. (since SIRI 2.1) - Elements for location of flexible stops or service that allows pickup anywhere in a designated area. +SIRI v2.1 + Elements for location of flexible stops or service that allows pickup anywhere in a designated area. (since SIRI 2.1) @@ -775,37 +775,37 @@ To avoid this, the producer should transmit xxxPredictionUnknown instead of any - Elements for assignment of a SCHEDULED STOP POINT to a specific QUAY or platform. +SIRI v2.1 + Elements for assignment of a SCHEDULED STOP POINT to a specific QUAY or platform. (since SIRI 2.1) - Physical QUAY to use according to the planned timetable. +SIRI v2.0 + Physical QUAY to use according to the planned timetable. (since SIRI 2.0) - Scheduled Platform name. Can be used to indicate platfrom change. +SIRI v2.0 + Scheduled Platform name. Can be used to indicate platfrom change. (since SIRI 2.0) - Physical QUAY to use according to the real-time prediction. +SIRI v2.0 + Physical QUAY to use according to the real-time prediction. (since SIRI 2.0) - Expected Platform name. Can be used to indicate real-time prediction. +SIRI v2.1 + Expected Platform name. Can be used to indicate real-time prediction. (since SIRI 2.1) - Physical QUAY actually used. +SIRI v2.0 + Physical QUAY actually used. (since SIRI 2.0) - Actual Platform name. Can be used to indicate recorded platform. +SIRI v2.1 + Actual Platform name. Can be used to indicate recorded platform. (since SIRI 2.1) @@ -814,7 +814,7 @@ To avoid this, the producer should transmit xxxPredictionUnknown instead of any - Elements for assignment of a SCHEDULED STOP POINT to a specific BOARDING POSITION or location on a QUAY. +SIRI v2.1 + Elements for assignment of a SCHEDULED STOP POINT to a specific BOARDING POSITION or location on a QUAY. (since SIRI 2.1) @@ -852,7 +852,7 @@ To avoid this, the producer should transmit xxxPredictionUnknown instead of any - Type for assignment of a SCHEDULED STOP POINT to a physical location, in particular to a QUAY or BOARDING POSITION. +SIRI v2.0. + Type for assignment of a SCHEDULED STOP POINT to a physical location, in particular to a QUAY or BOARDING POSITION. (since SIRI 2.0). @@ -865,19 +865,19 @@ To avoid this, the producer should transmit xxxPredictionUnknown instead of any - Type for assignment of a SCHEDULED STOP POINT to a physical location, in particular to a QUAY or BOARDING POSITION, according to the planned timetable. +SIRI v2.0. + Type for assignment of a SCHEDULED STOP POINT to a physical location, in particular to a QUAY or BOARDING POSITION, according to the planned timetable. (since SIRI 2.0). - Physical QUAY to use according to the planned timetable. +SIRI v2.0 + Physical QUAY to use according to the planned timetable. (since SIRI 2.0) - Scheduled Platform name. +SIRI v2.0 + Scheduled Platform name. (since SIRI 2.0) @@ -885,12 +885,12 @@ To avoid this, the producer should transmit xxxPredictionUnknown instead of any - Physical BOARDING POSITION to use according to the planned timetable. +SIRI v2.1 + Physical BOARDING POSITION to use according to the planned timetable. (since SIRI 2.1) - Scheduled BOARDING POSITION name. +SIRI v2.1 + Scheduled BOARDING POSITION name. (since SIRI 2.1) @@ -904,7 +904,7 @@ To avoid this, the producer should transmit xxxPredictionUnknown instead of any Indicates the type of a nested QUAY in case of detailed STOP PLACE models. -A QUAY may be part of a group of QUAYs, or may be divided into sectors, i.e., smaller sub-QUAYs. +SIRI v2.1 +A QUAY may be part of a group of QUAYs, or may be divided into sectors, i.e., smaller sub-QUAYs. (since SIRI 2.1) @@ -916,7 +916,7 @@ If prediction is degraded, e.g. because of a situation, PredictionInaccurate is - Can be used to inform the passenger about the reason for a change of the prediction (in)accuracy in case PredictionInaccurate is set to 'true'. +SIRI v2.1 + Can be used to inform the passenger about the reason for a change of the prediction (in)accuracy in case PredictionInaccurate is set to 'true'. (since SIRI 2.1) @@ -948,12 +948,12 @@ Occupancies and capacities for individual VEHICLEs, e.g. parts of a COMPOUND TRA - Text annotation to be used in cases where ArrivalStatus is set to 'cancelled'. +SIRI v2.1 + Text annotation to be used in cases where ArrivalStatus is set to 'cancelled'. (since SIRI 2.1) - Arbitrary text string to show to indicate the status of the departure of the VEHICLE for example, “Enroute”, “5 Km”, “Approaching”. May depend on the policy of the OPERATOR, for example show “Approaching” if less than 200metres away from stop. +SIRI v2.0 + Arbitrary text string to show to indicate the status of the departure of the VEHICLE for example, “Enroute”, “5 Km”, “Approaching”. May depend on the policy of the OPERATOR, for example show “Approaching” if less than 200metres away from stop. (since SIRI 2.0) @@ -972,12 +972,12 @@ Inheritable property. Can be omitted if the same as the DeparturePlatformName If - Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). If not given, assume same as for departure. +SIRI v2.1 + Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). If not given, assume same as for departure. (since SIRI 2.1) - Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. +SIRI v2.1 + Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. (since SIRI 2.1) Examples: - "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle arriving at sector A first when approaching the QUAY with sectors A-B-C-D. If the arriving vehicle is represented as an arrow, "towards A" would be abstracted as "=> A-B-C-D". - "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle arriving at this reference point first when approaching the QUAY. If the arriving vehicle is represented as an arrow, "towards 0" would be abstracted as "=> 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). @@ -987,7 +987,7 @@ It is advised to specify a reference point that is meaningful for passengers on - OPERATORs of of service up until arrival. May change for departure. +SIRI v2.0. + OPERATORs of of service up until arrival. May change for departure. (since SIRI 2.0). @@ -1021,12 +1021,12 @@ It is advised to specify a reference point that is meaningful for passengers on - Latest target time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. +SIRI 2.0 + Latest target time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. (since SIRI 2.0) - Latest expected time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. +SIRI 2.0 + Latest expected time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. (since SIRI 2.0) @@ -1036,12 +1036,12 @@ It is advised to specify a reference point that is meaningful for passengers on - Text annotation to be used in cases where DepartureStatus is set to 'cancelled'. +SIRI v2.1 + Text annotation to be used in cases where DepartureStatus is set to 'cancelled'. (since SIRI 2.1) - Arbitrary text string to show to indicate the status of the departure of the vehicle, for example, “Boarding”, “GatesClosed”. +SIRI v2.0 + Arbitrary text string to show to indicate the status of the departure of the vehicle, for example, “Boarding”, “GatesClosed”. (since SIRI 2.0) @@ -1056,12 +1056,12 @@ It is advised to specify a reference point that is meaningful for passengers on - Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). +SIRI v2.1 + Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). (since SIRI 2.1) - Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. +SIRI v2.1 + Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. (since SIRI 2.1) Examples: - "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle departing in the direction of sector A on a QUAY with sectors A-B-C-D. If the departing vehicle is represented as an arrow, "towards A" would be abstracted as "<= A-B-C-D". - "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle departing in the direction of this reference point. If the departing vehicle is represented as an arrow, "towards 0" would be abstracted as "<= 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). @@ -1070,27 +1070,27 @@ It is advised to specify a reference point that is meaningful for passengers on - Expected/Predicted real-time occupancies of a VEHICLE and reservations after departing from a given stop. +SIRI v2.1 + Expected/Predicted real-time occupancies of a VEHICLE and reservations after departing from a given stop. (since SIRI 2.1) - Expected/Predicted real-time capacities (number of available seats) of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. +SIRI v2.1 + Expected/Predicted real-time capacities (number of available seats) of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. (since SIRI 2.1) - Actually recorded/counted occupancies of a VEHICLE and reserved seats after departing from a given stop. +SIRI v2.1 + Actually recorded/counted occupancies of a VEHICLE and reserved seats after departing from a given stop. (since SIRI 2.1) - Actually recorded/counted capacities of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. +SIRI v2.1 + Actually recorded/counted capacities of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. (since SIRI 2.1) - OPERATORs of service for departure and onwards. May change from that for arrival. +SIRI v2.0. + OPERATORs of service for departure and onwards. May change from that for arrival. (since SIRI 2.0). @@ -1134,7 +1134,7 @@ It is advised to specify a reference point that is meaningful for passengers on - Provides information about relations to other journeys. +SIRI v2.1 + Provides information about relations to other journeys. (since SIRI 2.1) @@ -1144,7 +1144,7 @@ It is advised to specify a reference point that is meaningful for passengers on - Specifies the type of the relation, e.g., joining, splitting, replacement etc. +SIRI v2.1 + Specifies the type of the relation, e.g., joining, splitting, replacement etc. (since SIRI 2.1) @@ -1153,24 +1153,24 @@ It is advised to specify a reference point that is meaningful for passengers on - Specifies which CALL or JOURNEY PART of the JOURNEY has a JOURNEY RELATION. +SIRI v2.1 + Specifies which CALL or JOURNEY PART of the JOURNEY has a JOURNEY RELATION. (since SIRI 2.1) - Information about the stop at which the JOURNEY is related to another JOURNEY. +SIRI v2.1 + Information about the stop at which the JOURNEY is related to another JOURNEY. (since SIRI 2.1) - Information about the JOURNEY PARTs for which the JOURNEY has a JOURNEY RELATION. +SIRI v2.1 + Information about the JOURNEY PARTs for which the JOURNEY has a JOURNEY RELATION. (since SIRI 2.1) - Information about related parts of JOURNEY. +SIRI v2.1 + Information about related parts of JOURNEY. (since SIRI 2.1) @@ -1181,7 +1181,7 @@ It is advised to specify a reference point that is meaningful for passengers on - The JOURNEY RELATION refers to this CALL. +SIRI v2.1 + The JOURNEY RELATION refers to this CALL. (since SIRI 2.1) @@ -1194,7 +1194,7 @@ It is advised to specify a reference point that is meaningful for passengers on - The JOURNEY RELATION refers to this JOURNEY PART. +SIRI v2.1 + The JOURNEY RELATION refers to this JOURNEY PART. (since SIRI 2.1) @@ -1202,7 +1202,7 @@ It is advised to specify a reference point that is meaningful for passengers on - Refers to the JOURNEY to which the current JOURNEY is related. +SIRI v2.1 + Refers to the JOURNEY to which the current JOURNEY is related. (since SIRI 2.1) @@ -1219,7 +1219,7 @@ It is advised to specify a reference point that is meaningful for passengers on Groups relevant elements of the formation model that are used on JOURNEY level. The TRAIN conceptual model represents VEHICLE TYPE properties that are peculiar to TRAINs. A TRAIN may comprise not just a single VEHICLE but a chain of carriages, TRAIN ELEMENTS, assembled as TRAIN COMPONENTs. -Groups of carriages may be managed as sections by composing TRAINs into a COMPOUND TRAIN made up of multiple TRAIN IN COMPOUND TRAIN, for example in a train that joins or splits. +SIRI v2.1 +Groups of carriages may be managed as sections by composing TRAINs into a COMPOUND TRAIN made up of multiple TRAIN IN COMPOUND TRAIN, for example in a train that joins or splits. (since SIRI 2.1) @@ -1250,7 +1250,7 @@ Groups of carriages may be managed as sections by composing TRAINs into a COMPOU - Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. +SIRI v2.1 + Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. (since SIRI 2.1) Examples: - "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle arriving or departing in the direction of sector A on a QUAY with sectors A-B-C-D. If the arriving vehicle is represented as an arrow, "towards A" would be abstracted as "=> A-B-C-D". If the departing vehicle is represented as an arrow, "towards A" would be abstracted as "<= A-B-C-D". - "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle arriving or departing in the direction of this reference point. If the arriving vehicle is represented as an arrow, "towards 0" would be abstracted as "=> 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). If the departing vehicle is represented as an arrow, "towards 0" would be abstracted as "<= 0...100". @@ -1262,7 +1262,7 @@ It is advised to specify a reference point that is meaningful for passengers on - Assignment of the arrival/departure of a VEHICLE within a formation, e.g. carriage in a TRAIN composition, to a physical QUAY or nested QUAY (i.e. platform or sector of a platform). +SIRI v2.1 + Assignment of the arrival/departure of a VEHICLE within a formation, e.g. carriage in a TRAIN composition, to a physical QUAY or nested QUAY (i.e. platform or sector of a platform). (since SIRI 2.1) @@ -1281,12 +1281,12 @@ If a QUAY is divided into sub-QUAYs or sectors (with the help of STOP ASSIGNMENT - Information about a change of the formation (e.g. TRAIN composition) or changes of vehicles within the formation. +SIRI v2.1 + Information about a change of the formation (e.g. TRAIN composition) or changes of vehicles within the formation. (since SIRI 2.1) - Type for FORMATION CONDITION. +SIRI v2.1 + Type for FORMATION CONDITION. (since SIRI 2.1) @@ -1339,7 +1339,7 @@ If a QUAY is divided into sub-QUAYs or sectors (with the help of STOP ASSIGNMENT - Elements for FormationStatus that further describe the status of the formation, e.g. whether the accessibility has changed. +SIRI v2.1 + Elements for FormationStatus that further describe the status of the formation, e.g. whether the accessibility has changed. (since SIRI 2.1) @@ -1373,10 +1373,10 @@ If a QUAY is divided into sub-QUAYs or sectors (with the help of STOP ASSIGNMENT - + - Elements for a PASSENGER CAPACITY. Used to indicate the maximum capacities of a TRAIN ELEMENT or the estimated/recorded capacities of a VEHICLE at a given stop, i.e., the number of seats available. +SIRI v2.1 + Elements for a PASSENGER CAPACITY. Used to indicate the maximum capacities of a TRAIN ELEMENT or the estimated/recorded capacities of a VEHICLE at a given stop, i.e., the number of seats available. (since SIRI 2.1) @@ -1423,7 +1423,7 @@ If a QUAY is divided into sub-QUAYs or sectors (with the help of STOP ASSIGNMENT - The intersection of supplied elements describes the extent that the Occupancy values applies to. +SIRI v2.1 + The intersection of supplied elements describes the extent that the Occupancy values applies to. (since SIRI 2.1) Only vehicle-centric filter (measurement in a part or at an entrance of a TRAIN) are available here, but a stop-centric filtering (measurement in a sector or at a position on a QUAY) can be achieved indirectly via Arrival-/DepartureFormationAssignment. @@ -1442,7 +1442,7 @@ Only vehicle-centric filter (measurement in a part or at an entrance of a TRAIN) - Occupancy values applying to indicated scope. +SIRI v2.1 + Occupancy values applying to indicated scope. (since SIRI 2.1) @@ -1500,7 +1500,7 @@ More accurate data can be provided by the individual occupancies or capacities b - Used to specify that a travel group has booked a section of the vehicle for a part of the journey, and if so under what name. +SIRI v2.1 + Used to specify that a travel group has booked a section of the vehicle for a part of the journey, and if so under what name. (since SIRI 2.1) @@ -1517,7 +1517,7 @@ More accurate data can be provided by the individual occupancies or capacities b - Real-time occupancies of a VEHICLE (by fare class). Could be feedback from an automatic passenger counting system (APC) or estimated values from statistics. +SIRI v2.1 + Real-time occupancies of a VEHICLE (by fare class). Could be feedback from an automatic passenger counting system (APC) or estimated values from statistics. (since SIRI 2.1) @@ -1536,22 +1536,22 @@ More accurate data can be provided by the individual occupancies or capacities b - Real-time capacities of a VEHICLE (by fare class), i.e., number of available seats. Alternative way to communicate occupancy measurements. +SIRI v2.1 + Real-time capacities of a VEHICLE (by fare class), i.e., number of available seats. Alternative way to communicate occupancy measurements. (since SIRI 2.1) - + - An elementary component of a TRAIN, e.g. wagon or locomotive. +SIRI v2.1 + An elementary component of a TRAIN, e.g. wagon or locomotive. (since SIRI 2.1) - Type for TRAIN ELEMENT. +SIRI v2.1 + Type for TRAIN ELEMENT. (since SIRI 2.1) @@ -1565,7 +1565,7 @@ More accurate data can be provided by the individual occupancies or capacities b - Elements for a TRAIN ELEMENT. +SIRI v2.1 + Elements for a TRAIN ELEMENT. (since SIRI 2.1) @@ -1581,15 +1581,15 @@ More accurate data can be provided by the individual occupancies or capacities b - + - Specifies the order of a certain TRAIN ELEMENT within a TRAIN and how the TRAIN ELEMENT is labeled in that context. +SIRI v2.1 + Specifies the order of a certain TRAIN ELEMENT within a TRAIN and how the TRAIN ELEMENT is labeled in that context. (since SIRI 2.1) - Type for TRAIN COMPONENT. +SIRI v2.1 + Type for TRAIN COMPONENT. (since SIRI 2.1) @@ -1607,7 +1607,7 @@ More accurate data can be provided by the individual occupancies or capacities b - Elements for a TRAIN COMPONENT. +SIRI v2.1 + Elements for a TRAIN COMPONENT. (since SIRI 2.1) @@ -1631,15 +1631,15 @@ More accurate data can be provided by the individual occupancies or capacities b - + - A vehicle composed of TRAIN ELEMENTs assembled in a certain order (so called TRAIN COMPONENTs), i.e. wagons assembled together and propelled by a locomotive or one of the wagons. +SIRI v2.1 + A vehicle composed of TRAIN ELEMENTs assembled in a certain order (so called TRAIN COMPONENTs), i.e. wagons assembled together and propelled by a locomotive or one of the wagons. (since SIRI 2.1) - Type for TRAIN. +SIRI v2.1 + Type for TRAIN. (since SIRI 2.1) @@ -1653,7 +1653,7 @@ More accurate data can be provided by the individual occupancies or capacities b - Elements for TRAIN. +SIRI v2.1 + Elements for TRAIN. (since SIRI 2.1) @@ -1679,16 +1679,16 @@ More accurate data can be provided by the individual occupancies or capacities b - + - Groups of carriages may be managed as sections by composing TRAINs into a COMPOUND TRAIN, for example if a TRAIN joins (or splits from) another TRAIN. +SIRI v2.1 + Groups of carriages may be managed as sections by composing TRAINs into a COMPOUND TRAIN, for example if a TRAIN joins (or splits from) another TRAIN. (since SIRI 2.1) TRAINs within a COMPOUND TRAIN may have different origins and destinations due to joining/splitting. A COMPOUND TRAIN may be stable for one or multiple JOURNEY PARTs and change at a certain STOP POINT due to planned joining/splitting, despatching alterations or a situation. - Type for COMPOUND TRAIN. +SIRI v2.1 + Type for COMPOUND TRAIN. (since SIRI 2.1) @@ -1712,12 +1712,12 @@ TRAINs within a COMPOUND TRAIN may have different origins and destinations due t - Specifies the order of a certain TRAIN within a COMPOUND TRAIN and how the TRAIN is labeled in that context. +SIRI v2.1 + Specifies the order of a certain TRAIN within a COMPOUND TRAIN and how the TRAIN is labeled in that context. (since SIRI 2.1) - Type for a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 + Type for a TRAIN IN COMPOUND TRAIN. (since SIRI 2.1) @@ -1735,7 +1735,7 @@ TRAINs within a COMPOUND TRAIN may have different origins and destinations due t - Elements for a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 + Elements for a TRAIN IN COMPOUND TRAIN. (since SIRI 2.1) @@ -1772,7 +1772,7 @@ TRAINs within a COMPOUND TRAIN may have different origins and destinations due t - Indicates whether passengers have access to adjacent TRAINs or TRAIN COMPONENTs within a COMPOUND TRAIN, i.e., whether passage between those wagons/coaches is possible. +SIRI v2.1 + Indicates whether passengers have access to adjacent TRAINs or TRAIN COMPONENTs within a COMPOUND TRAIN, i.e., whether passage between those wagons/coaches is possible. (since SIRI 2.1) @@ -1780,10 +1780,10 @@ TRAINs within a COMPOUND TRAIN may have different origins and destinations due t - + - Elements for a VEHICLE TYPE. +SIRI v2.1 + Elements for a VEHICLE TYPE. (since SIRI 2.1) @@ -1821,7 +1821,7 @@ TRAINs within a COMPOUND TRAIN may have different origins and destinations due t - Property elements for the abstract VEHICLE TYPE. +SIRI v2.1 + Property elements for the abstract VEHICLE TYPE. (since SIRI 2.1) @@ -1860,7 +1860,7 @@ TRAINs within a COMPOUND TRAIN may have different origins and destinations due t - Elements specifying Requirement properties of VEHICLE TYPE. Vehicle should satisfy these requirements. +SIRI v2.1 + Elements specifying Requirement properties of VEHICLE TYPE. Vehicle should satisfy these requirements. (since SIRI 2.1) @@ -1882,7 +1882,7 @@ TRAINs within a COMPOUND TRAIN may have different origins and destinations due t - Dimension elements for a VEHICLE TYPE. +SIRI v2.1 + Dimension elements for a VEHICLE TYPE. (since SIRI 2.1) diff --git a/xsd/siri_model/siri_journey_support.xsd b/xsd/siri_model/siri_journey_support.xsd index 76c7ecdd..431e9400 100644 --- a/xsd/siri_model/siri_journey_support.xsd +++ b/xsd/siri_model/siri_journey_support.xsd @@ -371,13 +371,13 @@ Rail transport, Roads and road transport - Type for identifier of a TRAIN ELEMENT. An elementary component of a TRAIN (e.g. wagon, locomotive etc.). +SIRI v2.1 + Type for identifier of a TRAIN ELEMENT. An elementary component of a TRAIN (e.g. wagon, locomotive etc.). (since SIRI 2.1) - Type for reference to a TRAIN ELEMENT. +SIRI v2.1 + Type for reference to a TRAIN ELEMENT. (since SIRI 2.1) @@ -385,18 +385,18 @@ Rail transport, Roads and road transport - Reference to a TRAIN ELEMENT. +SIRI v2.1 + Reference to a TRAIN ELEMENT. (since SIRI 2.1) - Type for identifier of a TRAIN COMPONENT. A TRAIN ELEMENT with a specific order within a TRAIN. +SIRI v2.1 + Type for identifier of a TRAIN COMPONENT. A TRAIN ELEMENT with a specific order within a TRAIN. (since SIRI 2.1) - Type for reference to a TRAIN COMPONENT. +SIRI v2.1 + Type for reference to a TRAIN COMPONENT. (since SIRI 2.1) @@ -404,18 +404,18 @@ Rail transport, Roads and road transport - Reference to a TRAIN COMPONENT. +SIRI v2.1 + Reference to a TRAIN COMPONENT. (since SIRI 2.1) - Type for identifier of a TRAIN. An ordered sequence of TRAIN ELEMENTs or TRAIN COMPONENTs respectively. +SIRI v2.1 + Type for identifier of a TRAIN. An ordered sequence of TRAIN ELEMENTs or TRAIN COMPONENTs respectively. (since SIRI 2.1) - Type for reference to a TRAIN. +SIRI v2.1 + Type for reference to a TRAIN. (since SIRI 2.1) @@ -423,18 +423,18 @@ Rail transport, Roads and road transport - Reference to a TRAIN. +SIRI v2.1 + Reference to a TRAIN. (since SIRI 2.1) - Type for identifier of a COMPOUND TRAIN. An ordered sequence of TRAINs or TRAIN IN COMPOUND TRAINs respectively. +SIRI v2.1 + Type for identifier of a COMPOUND TRAIN. An ordered sequence of TRAINs or TRAIN IN COMPOUND TRAINs respectively. (since SIRI 2.1) - Type for reference to a COMPOUND TRAIN. +SIRI v2.1 + Type for reference to a COMPOUND TRAIN. (since SIRI 2.1) @@ -442,18 +442,18 @@ Rail transport, Roads and road transport - Reference to a COMPOUND TRAIN. +SIRI v2.1 + Reference to a COMPOUND TRAIN. (since SIRI 2.1) - Type for identifier of a TRAIN IN COMPOUND TRAIN. A TRAIN with a specific order within a COMPOUND TRAIN. +SIRI v2.1 + Type for identifier of a TRAIN IN COMPOUND TRAIN. A TRAIN with a specific order within a COMPOUND TRAIN. (since SIRI 2.1) - Type for reference to a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 + Type for reference to a TRAIN IN COMPOUND TRAIN. (since SIRI 2.1) @@ -461,18 +461,18 @@ Rail transport, Roads and road transport - Reference to a TRAIN IN COMPOUND TRAIN. +SIRI v2.1 + Reference to a TRAIN IN COMPOUND TRAIN. (since SIRI 2.1) - Type for identifier of an ENTRANCE TO VEHICLE, e.g. a door of a TRAIN ELEMENT. +SIRI v2.1 + Type for identifier of an ENTRANCE TO VEHICLE, e.g. a door of a TRAIN ELEMENT. (since SIRI 2.1) - Type for reference to an ENTRANCE TO VEHICLE. +SIRI v2.1 + Type for reference to an ENTRANCE TO VEHICLE. (since SIRI 2.1) @@ -480,13 +480,13 @@ Rail transport, Roads and road transport - Reference to an ENTRANCE TO VEHICLE. +SIRI v2.1 + Reference to an ENTRANCE TO VEHICLE. (since SIRI 2.1) - Groups together the relevant references needed in a formation. +SIRI v2.1 + Groups together the relevant references needed in a formation. (since SIRI 2.1) Has the following uses: - Either the smallest part of a formation, a TRAIN COMPONENT, is referenced or the TRAIN itself. The former is ideally used in a FORMATION ASSIGNMENT, i.e. QUAY (sector) assignment, to provide the highest level of detail for passenger orientation. - If the formation consists of multiple coupled TRAINs, a reference to the COMPOUND TRAIN is also possible. This might be used in a FORMATION CONDITION to signal a change of the train composition. @@ -855,7 +855,7 @@ Passengers don't need to change vehicles. The new journey is not communicated as - Allowed values for characterisation of nested QUAYs as part of a STOP ASSIGNMENT. +SIRI v2.1 + Allowed values for characterisation of nested QUAYs as part of a STOP ASSIGNMENT. (since SIRI 2.1) @@ -884,7 +884,7 @@ The first class carriage of a TRAIN might, for example, be assigned to sector "A - Allowed values for TYPE OF TRAIN ELEMENT. +SIRI v2.1 + Allowed values for TYPE OF TRAIN ELEMENT. (since SIRI 2.1) @@ -899,7 +899,7 @@ The first class carriage of a TRAIN might, for example, be assigned to sector "A - Allowed values for TRAIN SIZE. +SIRI v2.1 + Allowed values for TRAIN SIZE. (since SIRI 2.1) @@ -909,7 +909,7 @@ The first class carriage of a TRAIN might, for example, be assigned to sector "A - Allowed values for TYPE OF FUEL. +SIRI v2.1 + Allowed values for TYPE OF FUEL. (since SIRI 2.1) @@ -924,23 +924,23 @@ The first class carriage of a TRAIN might, for example, be assigned to sector "A - Classification of FARE CLASSes. +SIRI v2.1 + Classification of FARE CLASSes. (since SIRI 2.1) - List of FARE CLASSes. +SIRI v2.1 + List of FARE CLASSes. (since SIRI 2.1) - List of values for FARE CLASSes. +SIRI v2.1 + List of values for FARE CLASSes. (since SIRI 2.1) - Values for Fare Class Facility. +SIRI v2.1 + Values for Fare Class Facility. (since SIRI 2.1) @@ -990,7 +990,7 @@ The first class carriage of a TRAIN might, for example, be assigned to sector "A - Allowed values for VEHICLE IN FORMATION STATUS CODE. +SIRI v2.1 + Allowed values for VEHICLE IN FORMATION STATUS CODE. (since SIRI 2.1) @@ -1008,7 +1008,7 @@ The first class carriage of a TRAIN might, for example, be assigned to sector "A - Allowed values for FORMATION CHANGE CODE. +SIRI v2.1 + Allowed values for FORMATION CHANGE CODE. (since SIRI 2.1) diff --git a/xsd/siri_model/siri_modelPermissions.xsd b/xsd/siri_model/siri_modelPermissions.xsd index 09a3a899..67726d65 100644 --- a/xsd/siri_model/siri_modelPermissions.xsd +++ b/xsd/siri_model/siri_modelPermissions.xsd @@ -252,12 +252,12 @@ Rail transport, Roads and road transport - Whether results can be filtered by VEHICLE MODE. Default is 'true'. +SIRI v2.1 + Whether results can be filtered by VEHICLE MODE. Default is 'true'. (since SIRI 2.1) - Whether results can be filtered by PRODUCT CATEGORY. Default is 'true'. +SIRI v2.1 + Whether results can be filtered by PRODUCT CATEGORY. Default is 'true'. (since SIRI 2.1) diff --git a/xsd/siri_model/siri_modes.xsd b/xsd/siri_model/siri_modes.xsd index 8e8592da..d1a31138 100644 --- a/xsd/siri_model/siri_modes.xsd +++ b/xsd/siri_model/siri_modes.xsd @@ -305,100 +305,100 @@ Rail transport, Roads and road transport - + - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 @@ -578,152 +578,152 @@ Rail transport, Roads and road transport - + - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 @@ -861,60 +861,60 @@ Rail transport, Roads and road transport - + - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 @@ -969,35 +969,35 @@ Rail transport, Roads and road transport - + - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 @@ -1145,157 +1145,157 @@ Rail transport, Roads and road transport - + - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - + - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 @@ -1383,66 +1383,66 @@ Rail transport, Roads and road transport - + - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 @@ -1636,120 +1636,120 @@ Rail transport, Roads and road transport - + - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 @@ -1875,147 +1875,147 @@ Rail transport, Roads and road transport - + - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - + - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 @@ -2072,97 +2072,97 @@ Rail transport, Roads and road transport - + - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - + - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 @@ -2197,32 +2197,32 @@ Rail transport, Roads and road transport - + - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - + - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 @@ -2267,50 +2267,50 @@ Rail transport, Roads and road transport - + - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 @@ -2348,40 +2348,40 @@ Rail transport, Roads and road transport - + - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 - deprecated (SIRI 2.1) + DEPRECATED since SIRI 2.1 diff --git a/xsd/siri_model/siri_monitoredVehicleJourney.xsd b/xsd/siri_model/siri_monitoredVehicleJourney.xsd index a34f9d26..626b52f5 100644 --- a/xsd/siri_model/siri_monitoredVehicleJourney.xsd +++ b/xsd/siri_model/siri_monitoredVehicleJourney.xsd @@ -200,12 +200,12 @@ MonitoringError must not be used if Monitored is omitted or set to 'true'. - Velocity of VEHICLE. EIther actual speed or average speed may be used. +SIRI v2.0 + Velocity of VEHICLE. EIther actual speed or average speed may be used. (since SIRI 2.0) - Whether the engine of the vehicle is on. Default is 'true' (+SIRI 2.0) + Whether the engine of the vehicle is on. Default is 'true' (since SIRI 2.0) @@ -221,7 +221,7 @@ MonitoringError must not be used if Monitored is omitted or set to 'true'. - An classification of the progress state of running of this VEHICLE JOURNEY. +SIRI 2.0 + An classification of the progress state of running of this VEHICLE JOURNEY. (since SIRI 2.0) @@ -252,7 +252,7 @@ MonitoringError must not be used if Monitored is omitted or set to 'true'. - Relative priority for incliding via in displays. 1 Is high 3 is low. +SIRI v2.0 + Relative priority for incliding via in displays. 1 Is high 3 is low. (since SIRI 2.0) @@ -303,27 +303,27 @@ For SIRI-VM this is the most recent stop visited by the VEHICLE. - Type for a reference to JOURNEY PART. +SIRI v2.0 + Type for a reference to JOURNEY PART. (since SIRI 2.0) - Reference to a JOURNEY part. +SIRI v2.0 + Reference to a JOURNEY part. (since SIRI 2.0) - Train Number for JOURNEY PART +SIRI v2.0 + Train Number for JOURNEY PART (since SIRI 2.0) - OPERATOR of JOURNEY PART. +SIRI v2.0 + OPERATOR of JOURNEY PART. (since SIRI 2.0) - Reference to COMPOUND TRAIN that represents the train formation/composition as a whole (for this JOURNEY PART). +SIRI v2.1 + Reference to COMPOUND TRAIN that represents the train formation/composition as a whole (for this JOURNEY PART). (since SIRI 2.1) A journey does always have one or more JOURNEY PARTs for which the train formation/composition remains unchanged. @@ -332,7 +332,7 @@ A journey does always have one or more JOURNEY PARTs for which the train formati - Type for a reference to JOURNEY PART. +SIRI v2.1 + Type for a reference to JOURNEY PART. (since SIRI 2.1) @@ -352,7 +352,7 @@ A journey does always have one or more JOURNEY PARTs for which the train formati - Reference to COMPOUND TRAIN that represents the train formation/composition as a whole (for this JOURNEY PART). +SIRI v2.1 + Reference to COMPOUND TRAIN that represents the train formation/composition as a whole (for this JOURNEY PART). (since SIRI 2.1) A journey does always have one or more JOURNEY PARTs for which the train formation/composition remains unchanged. @@ -362,7 +362,7 @@ A journey does always have one or more JOURNEY PARTs for which the train formati - If no JOURNEY PART reference is available (or in addition to the reference), identify it indirectly by From-/ToStopPointRef and Start-/EndTime (i.e. the scheduled times at these stops). +SIRI v2.1 + If no JOURNEY PART reference is available (or in addition to the reference), identify it indirectly by From-/ToStopPointRef and Start-/EndTime (i.e. the scheduled times at these stops). (since SIRI 2.1) @@ -423,7 +423,7 @@ A journey does always have one or more JOURNEY PARTs for which the train formati - TRAIN NUMBERs for journey. +SIRI v2.0 + TRAIN NUMBERs for journey. (since SIRI 2.0) @@ -443,7 +443,7 @@ A journey does always have one or more JOURNEY PARTs for which the train formati - Information about Parts of JOURNEY +SIRI v2.0 + Information about Parts of JOURNEY (since SIRI 2.0) @@ -465,7 +465,7 @@ A journey does always have one or more JOURNEY PARTs for which the train formati - TRAIN NUMBERs for journey. +SIRI v2.0 + TRAIN NUMBERs for journey. (since SIRI 2.0) @@ -485,7 +485,7 @@ A journey does always have one or more JOURNEY PARTs for which the train formati - Information about Parts of JOURNEY +SIRI v2.0 + Information about Parts of JOURNEY (since SIRI 2.0) @@ -603,7 +603,7 @@ A journey does always have one or more JOURNEY PARTs for which the train formati - Latest time at which a VEHICLE will arrive at stop. +SIRI v2.0 + Latest time at which a VEHICLE will arrive at stop. (since SIRI 2.0) @@ -626,17 +626,17 @@ A journey does always have one or more JOURNEY PARTs for which the train formati - Expected departure time of VEHICLE without waiting time due to operational actions. For people at stop this would normally be shown if different from Expected Departure time. +SIRI v2.0. + Expected departure time of VEHICLE without waiting time due to operational actions. For people at stop this would normally be shown if different from Expected Departure time. (since SIRI 2.0). - Earliest time at which VEHICLE may leave the stop. Used to secure connections. Passengers must be at boarding point by this time to be sure of catching VEHICLE. +SIRI v2.0 + Earliest time at which VEHICLE may leave the stop. Used to secure connections. Passengers must be at boarding point by this time to be sure of catching VEHICLE. (since SIRI 2.0) - Prediction quality, either as approcimate level, or more quantitatyive percentile range of predictions will fall within a given range of times. +SIRI v2.0 + Prediction quality, either as approcimate level, or more quantitatyive percentile range of predictions will fall within a given range of times. (since SIRI 2.0) diff --git a/xsd/siri_model/siri_reference.xsd b/xsd/siri_model/siri_reference.xsd index e930abea..d74be412 100644 --- a/xsd/siri_model/siri_reference.xsd +++ b/xsd/siri_model/siri_reference.xsd @@ -473,12 +473,12 @@ Values for these elements can be specified on an annual schedule and will be inh - Reference to a BRANDING. +SIRI v2.1 + Reference to a BRANDING. (since SIRI 2.1) - An arbitrary marketing classification. +SIRI v2.1 + An arbitrary marketing classification. (since SIRI 2.1) @@ -796,13 +796,13 @@ Values for these elements can be specified on an annual schedule and will be inh - Type for identifier of a BRANDING. +SIRI v2.1 + Type for identifier of a BRANDING. (since SIRI 2.1) - Type for reference to a BRANDING. +SIRI v2.1 + Type for reference to a BRANDING. (since SIRI 2.1) @@ -810,7 +810,7 @@ Values for these elements can be specified on an annual schedule and will be inh - An arbitrary marketing classification. +SIRI v2.1 + An arbitrary marketing classification. (since SIRI 2.1) diff --git a/xsd/siri_model/siri_situation.xsd b/xsd/siri_model/siri_situation.xsd index 7f79a980..47d5f1f0 100644 --- a/xsd/siri_model/siri_situation.xsd +++ b/xsd/siri_model/siri_situation.xsd @@ -57,7 +57,7 @@ siri_model\siri_situation-v2.0.xsd: 2012-03-23 - + @@ -1080,14 +1080,14 @@ Rail transport, Roads and road transport - + - Type for information about a FACILITY affected by an SITUATION. (+SIRI 2.0) + Type for information about a FACILITY affected by an SITUATION. (since SIRI 2.0) @@ -1195,13 +1195,13 @@ Rail transport, Roads and road transport - Facilities available for VEHICLE JOURNEY (+SIRI 2.0) + Facilities available for VEHICLE JOURNEY (since SIRI 2.0) - Facililitiy available for VEHICLE JOURNEY (+SIRI 2.0) + Facililitiy available for VEHICLE JOURNEY (since SIRI 2.0) @@ -1281,13 +1281,13 @@ Rail transport, Roads and road transport - Facilities available for component (+SIRI 2.0) + Facilities available for component (since SIRI 2.0) - Facility available for VEHICLE JOURNEY (+SIRI 2.0) + Facility available for VEHICLE JOURNEY (since SIRI 2.0) diff --git a/xsd/siri_model/siri_situationClassifiers.xsd b/xsd/siri_model/siri_situationClassifiers.xsd index b96289b4..3a39b7a8 100644 --- a/xsd/siri_model/siri_situationClassifiers.xsd +++ b/xsd/siri_model/siri_situationClassifiers.xsd @@ -20,7 +20,7 @@ 2019-09-01 - 2019-09-01 - @@ -115,39 +115,39 @@ Rail transport, Roads and road transport - DEPRECATED (SIRI 2.1) - use only AlertCause. + DEPRECATED since SIRI 2.1 - use only AlertCause. - DEPRECATED (SIRI 2.1) - use only AlertCause. + DEPRECATED since SIRI 2.1 - use only AlertCause. - DEPRECATED (SIRI 2.1) - use only AlertCause. + DEPRECATED since SIRI 2.1 - use only AlertCause. - DEPRECATED (SIRI 2.1) - use only AlertCause. + DEPRECATED since SIRI 2.1 - use only AlertCause. - DEPRECATED (SIRI 2.1) - use only AlertCause. + DEPRECATED since SIRI 2.1 - use only AlertCause. - DEPRECATED (SIRI 2.1) - use only AlertCause. + DEPRECATED since SIRI 2.1 - use only AlertCause. - DEPRECATED (SIRI 2.1) - use only TpegReasonGroup. + DEPRECATED since SIRI 2.1 - use only AlertCause. @@ -863,453 +863,453 @@ Rail transport, Roads and road transport - TPEG Pti19_1, deprecated (SIRI 2.1) + TPEG Pti19_1, DEPRECATED since SIRI 2.1 - TPEG Pti19_1_2, deprecated (SIRI 2.1) + TPEG Pti19_1_2, DEPRECATED since SIRI 2.1 - TPEG Pti19_1_5, deprecated (SIRI 2.1) - replaced by Pts38_33, door failure + TPEG Pti19_1_5, DEPRECATED since SIRI 2.1 - replaced by Pts38_33, door failure - TPEG Pti19_1_7, deprecated (SIRI 2.1) + TPEG Pti19_1_7, DEPRECATED since SIRI 2.1 - TPEG Pti19_1_8, deprecated (SIRI 2.1) + TPEG Pti19_1_8, DEPRECATED since SIRI 2.1 - TPEG Pti19_1_12, deprecated (SIRI 2.1) - replaced by Pts38_32, service disruption + TPEG Pti19_1_12, DEPRECATED since SIRI 2.1 - replaced by Pts38_32, service disruption - TPEG Pti19_2, deprecated (SIRI 2.1) + TPEG Pti19_2, DEPRECATED since SIRI 2.1 - TPEG Pti19_3_2, deprecated (SIRI 2.1) + TPEG Pti19_3_2, DEPRECATED since SIRI 2.1 - TPEG Pti19_3_6, deprecated (SIRI 2.1) + TPEG Pti19_3_6, DEPRECATED since SIRI 2.1 - TPEG Pti19_3_7, deprecated (SIRI 2.1) + TPEG Pti19_3_7, DEPRECATED since SIRI 2.1 - TPEG Pti19_3_8, deprecated (SIRI 2.1) + TPEG Pti19_3_8, DEPRECATED since SIRI 2.1 - TPEG Pti19_3_9, deprecated (SIRI 2.1) + TPEG Pti19_3_9, DEPRECATED since SIRI 2.1 - TPEG Pti19_3_10, deprecated (SIRI 2.1) + TPEG Pti19_3_10, DEPRECATED since SIRI 2.1 - TPEG Pti19_3_13, deprecated (SIRI 2.1) + TPEG Pti19_3_13, DEPRECATED since SIRI 2.1 - TPEG Pti19_3_16, deprecated (SIRI 2.1) + TPEG Pti19_3_16, DEPRECATED since SIRI 2.1 - TPEG Pti19_4_1, deprecated (SIRI 2.1) + TPEG Pti19_4_1, DEPRECATED since SIRI 2.1 - TPEG Pti19_5_1, deprecated (SIRI 2.1) + TPEG Pti19_5_1, DEPRECATED since SIRI 2.1 - TPEG Pti19_5_2, deprecated (SIRI 2.1) + TPEG Pti19_5_2, DEPRECATED since SIRI 2.1 - TPEG Pti19_5_3, deprecated (SIRI 2.1) + TPEG Pti19_5_3, DEPRECATED since SIRI 2.1 - TPEG Pti19_5_4, deprecated (SIRI 2.1) + TPEG Pti19_5_4, DEPRECATED since SIRI 2.1 - TPEG Pti19_5_5, deprecated (SIRI 2.1) + TPEG Pti19_5_5, DEPRECATED since SIRI 2.1 - TPEG Pti19_6_1, deprecated (SIRI 2.1) + TPEG Pti19_6_1, DEPRECATED since SIRI 2.1 - TPEG Pti19_6_2, deprecated (SIRI 2.1) + TPEG Pti19_6_2, DEPRECATED since SIRI 2.1 - TPEG Pti19_6_3, deprecated (SIRI 2.1) - replaced by Pts38_79, person hit by vehicle + TPEG Pti19_6_3, DEPRECATED since SIRI 2.1 - replaced by Pts38_79, person hit by vehicle - TPEG Pti19_6_4, deprecated (SIRI 2.1) + TPEG Pti19_6_4, DEPRECATED since SIRI 2.1 - TPEG Pti19_6_5, deprecated (SIRI 2.1) - replaced by Pts38_14, emergency medical services + TPEG Pti19_6_5, DEPRECATED since SIRI 2.1 - replaced by Pts38_14, emergency medical services - TPEG Pti19_8, deprecated (SIRI 2.1) + TPEG Pti19_8, DEPRECATED since SIRI 2.1 - TPEG Pti19_10, deprecated (SIRI 2.1) + TPEG Pti19_10, DEPRECATED since SIRI 2.1 - TPEG Pti19_11, deprecated (SIRI 2.1) + TPEG Pti19_11, DEPRECATED since SIRI 2.1 - TPEG Pti19_14, deprecated (SIRI 2.1) + TPEG Pti19_14, DEPRECATED since SIRI 2.1 - TPEG Pti19_15_1, deprecated (SIRI 2.1) - replaced by Pts38_23, border control + TPEG Pti19_15_1, DEPRECATED since SIRI 2.1 - replaced by Pts38_23, border control - TPEG Pti19_15_2, deprecated (SIRI 2.1) + TPEG Pti19_15_2, DEPRECATED since SIRI 2.1 - TPEG Pti19_18_1, deprecated (SIRI 2.1) - replaced by Pts38_64, level crossing blocked + TPEG Pti19_18_1, DEPRECATED since SIRI 2.1 - replaced by Pts38_64, level crossing blocked - TPEG Pti19_19_3, deprecated (SIRI 2.1) - replaced by Pts38_81, vehicle struck animal + TPEG Pti19_19_3, DEPRECATED since SIRI 2.1 - replaced by Pts38_81, vehicle struck animal - TPEG Pti19_19_4, deprecated (SIRI 2.1) - replaced by Pts38_80, vehicle struck object + TPEG Pti19_19_4, DEPRECATED since SIRI 2.1 - replaced by Pts38_80, vehicle struck object - TPEG Pti19_23_2, deprecated (SIRI 2.1) + TPEG Pti19_23_2, DEPRECATED since SIRI 2.1 - TPEG Pti19_23_3, deprecated (SIRI 2.1) + TPEG Pti19_23_3, DEPRECATED since SIRI 2.1 - TPEG Pti19_23_4, deprecated (SIRI 2.1) + TPEG Pti19_23_4, DEPRECATED since SIRI 2.1 - TPEG Pti19_24_1, deprecated (SIRI 2.1) + TPEG Pti19_24_1, DEPRECATED since SIRI 2.1 - TPEG Pti19_24_5, deprecated (SIRI 2.1) + TPEG Pti19_24_5, DEPRECATED since SIRI 2.1 - TPEG Pti19_24_6, deprecated (SIRI 2.1) + TPEG Pti19_24_6, DEPRECATED since SIRI 2.1 - TPEG Pti19_24_7, deprecated (SIRI 2.1) + TPEG Pti19_24_7, DEPRECATED since SIRI 2.1 - TPEG Pti19_25, deprecated (SIRI 2.1) - replaced by Pts38_68, bridge damage + TPEG Pti19_25, DEPRECATED since SIRI 2.1 - replaced by Pts38_68, bridge damage - TPEG Pti19_25_1, deprecated (SIRI 2.1) + TPEG Pti19_25_1, DEPRECATED since SIRI 2.1 - TPEG Pti19_26, deprecated (SIRI 2.1) + TPEG Pti19_26, DEPRECATED since SIRI 2.1 - TPEG Pti19_255, deprecated (SIRI 2.1) + TPEG Pti19_255, DEPRECATED since SIRI 2.1 - TPEG Pti19_255_1, deprecated (SIRI 2.1) + TPEG Pti19_255_1, DEPRECATED since SIRI 2.1 - TPEG Pti19_255_2, deprecated (SIRI 2.1) + TPEG Pti19_255_2, DEPRECATED since SIRI 2.1 - TPEG Pti19_255, deprecated (SIRI 2.1) - replaced by Pts38_255, undefined alert cause + TPEG Pti19_255, DEPRECATED since SIRI 2.1 - replaced by Pts38_255, undefined alert cause - TPEG Pti20_1_1, deprecated (SIRI 2.1) + TPEG Pti20_1_1, DEPRECATED since SIRI 2.1 - TPEG Pti20_1_2, deprecated (SIRI 2.1) + TPEG Pti20_1_2, DEPRECATED since SIRI 2.1 - TPEG Pti20_3, deprecated (SIRI 2.1) + TPEG Pti20_3, DEPRECATED since SIRI 2.1 - TPEG Pti20_4, deprecated (SIRI 2.1) + TPEG Pti20_4, DEPRECATED since SIRI 2.1 - TPEG Pti20_5_1, deprecated (SIRI 2.1) + TPEG Pti20_5_1, DEPRECATED since SIRI 2.1 - TPEG Pti20_6, deprecated (SIRI 2.1) + TPEG Pti20_6, DEPRECATED since SIRI 2.1 - TPEG Pti20_255, deprecated (SIRI 2.1) - replaced by Pts38_255, undefined alert cause + TPEG Pti20_255, DEPRECATED since SIRI 2.1 - replaced by Pts38_255, undefined alert cause - TPEG Pti21_3_1, deprecated (SIRI 2.1) + TPEG Pti21_3_1, DEPRECATED since SIRI 2.1 - TPEG Pti21_4_1, deprecated (SIRI 2.1) + TPEG Pti21_4_1, DEPRECATED since SIRI 2.1 - TPEG Pti21_6_1, deprecated (SIRI 2.1) + TPEG Pti21_6_1, DEPRECATED since SIRI 2.1 - TPEG Pti21_6_2, deprecated (SIRI 2.1) - replaced by Pts38_53, defective vehicle + TPEG Pti21_6_2, DEPRECATED since SIRI 2.1 - replaced by Pts38_53, defective vehicle - TPEG Pti21_8_3, deprecated (SIRI 2.1) + TPEG Pti21_8_3, DEPRECATED since SIRI 2.1 - TPEG Pti21_8_4, deprecated (SIRI 2.1) + TPEG Pti21_8_4, DEPRECATED since SIRI 2.1 - TPEG Pti21_8_5, deprecated (SIRI 2.1) + TPEG Pti21_8_5, DEPRECATED since SIRI 2.1 - TPEG Pti21_8_6, deprecated (SIRI 2.1) + TPEG Pti21_8_6, DEPRECATED since SIRI 2.1 - TPEG Pti21_8_7, deprecated (SIRI 2.1) + TPEG Pti21_8_7, DEPRECATED since SIRI 2.1 - TPEG Pti21_8_8, deprecated (SIRI 2.1) + TPEG Pti21_8_8, DEPRECATED since SIRI 2.1 - TPEG Pti21_8_9, deprecated (SIRI 2.1) + TPEG Pti21_8_9, DEPRECATED since SIRI 2.1 - TPEG Pti21_11_1, deprecated (SIRI 2.1) + TPEG Pti21_11_1, DEPRECATED since SIRI 2.1 - TPEG Pti21_11_2, deprecated (SIRI 2.1) + TPEG Pti21_11_2, DEPRECATED since SIRI 2.1 - TPEG Pti21_13, deprecated (SIRI 2.1) + TPEG Pti21_13, DEPRECATED since SIRI 2.1 - TPEG Pti21_18, deprecated (SIRI 2.1) + TPEG Pti21_18, DEPRECATED since SIRI 2.1 - TPEG Pti21_19, deprecated (SIRI 2.1) + TPEG Pti21_19, DEPRECATED since SIRI 2.1 - TPEG Pti21_21_1, deprecated (SIRI 2.1) + TPEG Pti21_21_1, DEPRECATED since SIRI 2.1 - TPEG Pti21_22, deprecated (SIRI 2.1) + TPEG Pti21_22, DEPRECATED since SIRI 2.1 - TPEG Pti21_255, deprecated (SIRI 2.1) - replaced by Pts38_255, undefined alert cause + TPEG Pti21_255, DEPRECATED since SIRI 2.1 - replaced by Pts38_255, undefined alert cause - TPEG Pti22_5_1, deprecated (SIRI 2.1) + TPEG Pti22_5_1, DEPRECATED since SIRI 2.1 - TPEG Pti22_6, deprecated (SIRI 2.1) + TPEG Pti22_6, DEPRECATED since SIRI 2.1 - TPEG Pti22_9_1, deprecated (SIRI 2.1) + TPEG Pti22_9_1, DEPRECATED since SIRI 2.1 - TPEG Pti22_9_3, deprecated (SIRI 2.1) + TPEG Pti22_9_3, DEPRECATED since SIRI 2.1 - TPEG Pti22_10, deprecated (SIRI 2.1) + TPEG Pti22_10, DEPRECATED since SIRI 2.1 - TPEG Pti22_11_1, deprecated (SIRI 2.1) + TPEG Pti22_11_1, DEPRECATED since SIRI 2.1 - TPEG Pti22_14, deprecated (SIRI 2.1) + TPEG Pti22_14, DEPRECATED since SIRI 2.1 - TPEG Pti22_255_2, deprecated (SIRI 2.1) + TPEG Pti22_255_2, DEPRECATED since SIRI 2.1 - TPEG Pti22_255, deprecated (SIRI 2.1) - replaced by Pts38_255, undefined alert cause + TPEG Pti22_255, DEPRECATED since SIRI 2.1 - replaced by Pts38_255, undefined alert cause - + - Value was added in SIRI v2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. See also TPEG Pts38_8 value 'fireAtStation'. + See also TPEG Pts38_8 value 'fireAtStation'. - Value was added in SIRI v2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. See also TPEG Pts38_43 value 'breakDown'. + See also TPEG Pts38_43 value 'breakDown'. - Value was added in SIRI v2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. See also TPEG Pts38_64 value 'levelCrossingIncident'. + See also TPEG Pts38_64 value 'levelCrossingIncident'. - Value was added in SIRI v2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. See also TPEG Pts38_87 value 'heavySnowFall'. + See also TPEG Pts38_87 value 'heavySnowFall'. - Value was added in SIRI v2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. See also TPEG Pts38_130 value 'awaitingShuttle'. + See also TPEG Pts38_130 value 'awaitingShuttle'. - Value was added in SIRI v2.1 to ensure compatibility with VDV736 / UmS profile (v1.0) of CEN SIRI SX. See also TPEG Pts38_134 value 'awaitingApproach'. + See also TPEG Pts38_134 value 'awaitingApproach'. @@ -1317,54 +1317,54 @@ Rail transport, Roads and road transport - TPEG Pts38_0, unknown alert cause. Additionally, deprecated (SIRI v2.1) TPEG Pti18_0, unknown event reason. + DEPRECATED since SIRI 2.1 (TPEG Pti18_0 - unknown event reason). - TPEG Pts38_255, undefined alert cause. Additionally, deprecated (SIRI v2.1) TPEG Pti18_255, undefined event reason. + DEPRECATED since SIRI 2.1 (TPEG Pti18_255 - undefined event reason). - DEPRECATED and changed to nmtoken since SIRI v2.1 (TPEG Pti19 - Miscellaneous Event Reason) + DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti19 - Miscellaneous Event Reason) - DEPRECATED and changed to nmtoken since SIRI v2.1 (TPEG Pti19 - Miscellaneous Event Reason) + DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti19 - Miscellaneous Event Reason) - DEPRECATED and changed to nmtoken since SIRI v2.1 (TPEG Pti20 - Personnel Event Reason) + DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti20 - Personnel Event Reason) - DEPRECATED and changed to nmtoken since SIRI v2.1 (TPEG Pti20 - Personnel Event Reason) + DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti20 - Personnel Event Reason) - DEPRECATED and changed to nmtoken since SIRI v2.1 (TPEG Pti21 - Equipment Event Reason) + DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti21 - Equipment Event Reason) - DEPRECATED and changed to nmtoken since SIRI v2.1 (TPEG Pti21 - Equipment Event Reason) + DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti21 - Equipment Event Reason) - DEPRECATED and changed to nmtoken since SIRI v2.1 (TPEG Pti22 - Environment Event Reason) + DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti22 - Environment Event Reason) - DEPRECATED and changed to nmtoken since SIRI v2.1 (TPEG Pti22 - Environment Event Reason) + DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti22 - Environment Event Reason) \ No newline at end of file diff --git a/xsd/siri_model/siri_situationServiceTypes.xsd b/xsd/siri_model/siri_situationServiceTypes.xsd index 1f7e99ed..d4623be5 100644 --- a/xsd/siri_model/siri_situationServiceTypes.xsd +++ b/xsd/siri_model/siri_situationServiceTypes.xsd @@ -24,7 +24,7 @@ 2020-01-10 - @@ -194,44 +194,44 @@ Rail transport, Roads and road transport - Interchange is planned but was updated as a result of changes in the QUAYs or arrival/departure times. Can be used if the status is a combination of the other values. +SIRI v2.1 + Interchange is planned but was updated as a result of changes in the QUAYs or arrival/departure times. Can be used if the status is a combination of the other values. (since SIRI 2.1) An important function of connection protection is the ability to hold back a distributor VEHICLE (i.e. prolonged waiting) to allow passengers to transfer from delayed feeders. -To achieve this a distributorWaitProlonged status shall be communicated back to the feeder VEHICLEs to inform the passengers about the new departure time of the distributor or even a willWait guarantee. +SIRI v2.1 +To achieve this a distributorWaitProlonged status shall be communicated back to the feeder VEHICLEs to inform the passengers about the new departure time of the distributor or even a willWait guarantee. (since SIRI 2.1) - Used to provide the passengers with information about a new departure platform of the distributor VEHICLE if the distributor changes its planned stopping position. +SIRI v2.1 + Used to provide the passengers with information about a new departure platform of the distributor VEHICLE if the distributor changes its planned stopping position. (since SIRI 2.1) - Interchange is an addition to the plan. +SIRI v2.1 + Interchange is an addition to the plan. (since SIRI 2.1) - Interchange is a cancellation of an interchange in the plan. +SIRI v2.1 + Interchange is a cancellation of an interchange in the plan. (since SIRI 2.1) Loss of the inbound connection indicates the cancellation of the visit (of the FeederJourney) to the FeederArrivalStop, or a severely delayed arrival. This can lead to the distributor VEHICLE abandoning the connection. -Reasons for the loss of a feeder include (but are not limited to) the cancellation of the feeder VEHICLE, diversion/rerouting of the feeder VEHICLE, disruption of a line section or journey part of the feeder VEHICLE etc. +SIRI v2.1 +Reasons for the loss of a feeder include (but are not limited to) the cancellation of the feeder VEHICLE, diversion/rerouting of the feeder VEHICLE, disruption of a line section or journey part of the feeder VEHICLE etc. (since SIRI 2.1) - Indicates the loss of an outbound connection, i.e., is used to signal the cancellation of the onward connection to the passengers in the feeder VEHICLEs. +SIRI v2.1 + Indicates the loss of an outbound connection, i.e., is used to signal the cancellation of the onward connection to the passengers in the feeder VEHICLEs. (since SIRI 2.1) - deprecated (SIRI 2.1) - use statusOfConnectionUndecided instead + DEPRECATED since SIRI 2.1 - use statusOfConnectionUndecided instead @@ -425,7 +425,7 @@ Reasons for the loss of a feeder include (but are not limited to) the cancellati - deprecated (SIRI 2.1) - use undefinedStopPointType + DEPRECATED since SIRI 2.1 - use undefinedStopPointType @@ -438,7 +438,7 @@ Reasons for the loss of a feeder include (but are not limited to) the cancellati - Values for ROUTE POINT type that correspond to TPEG Pts44: StopPlaceUsage (Pti15: deprecated since SIRI v2.1). + Values for ROUTE POINT type that correspond to TPEG Pts44: StopPlaceUsage (Pti15: deprecated since SIRI 2.1). @@ -503,82 +503,82 @@ Reasons for the loss of a feeder include (but are not limited to) the cancellati - TPEG Pti15_1, start point, deprecated (SIRI v2.1) and replaced by Pts44_1 value 'origin'. + DEPRECATED since SIRI 2.1 and replaced by Pts44_1 value 'origin' (TPEG Pti15_1 - start point) . - TPEG Pti15_3, stop, deprecated (SIRI v2.1) + DEPRECATED since SIRI 2.1 (TPEG Pti15_3 - stop) - TPEG Pti15_4, via, deprecated (SIRI v2.1) + DEPRECATED since SIRI 2.1 (TPEG Pti15_4 - via) - TPEG Pti15_5, not-stopping, deprecated (SIRI v2.1) + DEPRECATED since SIRI 2.1 (TPEG Pti15_5 - not-stopping) - TPEG Pti15_6, temporary stop, deprecated (SIRI v2.1) + DEPRECATED since SIRI 2.1 (TPEG Pti15_6 - temporary stop) - TPEG Pti15_7, temporarily not-stopping, deprecated (SIRI v2.1) + DEPRECATED since SIRI 2.1 (TPEG Pti15_7 - temporarily not-stopping) - TPEG Pti15_8, exceptional stop, deprecated (SIRI v2.1) + DEPRECATED since SIRI 2.1 (TPEG Pti15_8 - exceptional stop) - TPEG Pti15_9, additional stop, deprecated (SIRI v2.1) + DEPRECATED since SIRI 2.1 (TPEG Pti15_9 - additional stop) - TPEG Pti15_10, request stop, deprecated (SIRI v2.1) + DEPRECATED since SIRI 2.1 (TPEG Pti15_10 - request stop) - TPEG Pti15_11, front train destination, deprecated (SIRI v2.1) + DEPRECATED since SIRI 2.1 (TPEG Pti15_11 - front train destination) - TPEG Pti15_12, rear train destination, deprecated (SIRI v2.1) + DEPRECATED since SIRI 2.1 (TPEG Pti15_12 - rear train destination) - TPEG Pti15_13, through service destination, deprecated (SIRI v2.1) + DEPRECATED since SIRI 2.1 (TPEG Pti15_13 - through service destination) - TPEG Pti15_14, not via, deprecated (SIRI v2.1) + DEPRECATED since SIRI 2.1 (TPEG Pti15_14 - not via) - TPEG Pti15_15, altered start point, deprecated (SIRI v2.1) + DEPRECATED since SIRI 2.1 (TPEG Pti15_15 - altered start point) - TPEG Pti15_16, altered destination, deprecated (SIRI v2.1) + DEPRECATED since SIRI 2.1 (TPEG Pti15_16 - altered destination) - TPEG Pti15_255, undefined route point, deprecated (SIRI v2.1) + DEPRECATED since SIRI 2.1 (TPEG Pti15_255 - undefined route point) diff --git a/xsd/siri_model/siri_targetedVehicleJourney.xsd b/xsd/siri_model/siri_targetedVehicleJourney.xsd index d41a8238..b3639b94 100644 --- a/xsd/siri_model/siri_targetedVehicleJourney.xsd +++ b/xsd/siri_model/siri_targetedVehicleJourney.xsd @@ -40,7 +40,7 @@ 2012-03-23 - +

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

            diff --git a/xsd/siri_model/siri_time.xsd b/xsd/siri_model/siri_time.xsd index 87261913..61c24112 100644 --- a/xsd/siri_model/siri_time.xsd +++ b/xsd/siri_model/siri_time.xsd @@ -31,7 +31,7 @@ 2020-01-24 - diff --git a/xsd/siri_model_discovery/siri_line.xsd b/xsd/siri_model_discovery/siri_line.xsd index 2dea9ebd..4c44ec17 100644 --- a/xsd/siri_model_discovery/siri_line.xsd +++ b/xsd/siri_model_discovery/siri_line.xsd @@ -145,13 +145,13 @@ Rail transport, Roads and road transport - JourneyPatterns in Direction of route (+SIRI 2.0) + JourneyPatterns in Direction of route (since SIRI 2.0) - JourneyPattern. (+SIRI 2.0) + JourneyPattern. (since SIRI 2.0) @@ -163,13 +163,13 @@ Rail transport, Roads and road transport - Ordered collection of STOP POINTs the LINE and direction . Detail level is 'stops'. +SIRI v2.0 + Ordered collection of STOP POINTs the LINE and direction . Detail level is 'stops'. (since SIRI 2.0) - Stop within Route of LINE. Detail level is 'stop' +SIRI v2.0 + Stop within Route of LINE. Detail level is 'stop' (since SIRI 2.0) @@ -195,12 +195,12 @@ Rail transport, Roads and road transport - Order of STOP POINT in route +SIRI v2.0 + Order of STOP POINT in route (since SIRI 2.0) - Plot of points from this stop to next Stop. Detail level is 'full'. +SIRI v2.0 + Plot of points from this stop to next Stop. Detail level is 'full'. (since SIRI 2.0) diff --git a/xsd/siri_model_discovery/siri_stopPoint.xsd b/xsd/siri_model_discovery/siri_stopPoint.xsd index 4f5bf2ee..4957adbb 100644 --- a/xsd/siri_model_discovery/siri_stopPoint.xsd +++ b/xsd/siri_model_discovery/siri_stopPoint.xsd @@ -136,7 +136,7 @@ Rail transport, Roads and road transport - Reference to a LINE that calls at stop. and its direction +SIRI V2.0 + Reference to a LINE that calls at stop. and its direction (since SIRI 2.0)             diff --git a/xsd/siri_productionTimetable_service.xsd b/xsd/siri_productionTimetable_service.xsd index fe8989c4..61e16bbe 100644 --- a/xsd/siri_productionTimetable_service.xsd +++ b/xsd/siri_productionTimetable_service.xsd @@ -49,7 +49,7 @@ 2012-03-23 - @@ -224,7 +224,7 @@ Rail transport, Roads and road transport - Temporal scope of Situations be included in response. The Situations must be valid within the specified period of time. (+SIRI 2.0) + Temporal scope of Situations be included in response. The Situations must be valid within the specified period of time. (since SIRI 2.0) @@ -314,7 +314,7 @@ Rail transport, Roads and road transport - Reference to part of a STOP PLACE. (+SIRI 2.0) + Reference to part of a STOP PLACE. (since SIRI 2.0) @@ -663,19 +663,19 @@ If false or omitted, each subscription response will contain the full informatio - Whether results can be filtered by MODE. Default is true.. (+SIRI v2.0) + Whether results can be filtered by MODE. Default is true.. ((since SIRI 2.0)) - Whether results can be filtered by NETWORKs. Default is 'true'. (+SIRI v2.0) + Whether results can be filtered by NETWORKs. Default is 'true'. ((since SIRI 2.0)) - Whether results can be filtered by STOP PLACE identifvier. Default is 'false'. (+SIRI v2.0) + Whether results can be filtered by STOP PLACE identifvier. Default is 'false'. ((since SIRI 2.0)) diff --git a/xsd/siri_stopMonitoring_service.xsd b/xsd/siri_stopMonitoring_service.xsd index 4b0866c7..4ec8a6d5 100644 --- a/xsd/siri_stopMonitoring_service.xsd +++ b/xsd/siri_stopMonitoring_service.xsd @@ -45,22 +45,22 @@ On SiriRequest change the element type of MaximumNumberOfCalls and MaximumNumberOfCallsOnwards from xsd:positiveInteger to xsd:nonNegativeInteger 2012-03-23 - +SIRI v2.0 + (since SIRI 2.0) [VDV] Add Minimum-StopVisits�PerVia to STopMonitoringRequestPolicy [VDV] Add HasMinimum-StopVisits�Via to STopMonitoringCapabilities [VDV] Revise MonitoredVehicleJourney to include additioanl result files [FR] Add Servcie Exception element [VDV] Add delivery variant to LineNote [SIRI-LITE] Allow a monitoring name in results. - [SIRI-LITE] Whether any related Situations should be included in the ServiceDelivery. Default is 'false'. +SIRI v2.0 + [SIRI-LITE] Whether any related Situations should be included in the ServiceDelivery. Default is 'false'. (since SIRI 2.0) 2012-04-18 - +SIRI v2.0 + (since SIRI 2.0) [VDV] Add ValidUntil Time to MonitoredStopVisit Correct comment on MaximumNumberOfCalls elements 2012-04-18 - +SIRI v2.0 + (since SIRI 2.0) [VDV] Add normal realtiem service Time to MonitoredStopVisit Geeneral update permissions to include has SItuations @@ -213,7 +213,7 @@ Rail transport, Roads and road transport - The minimum number of Stop Visits for a given LINE and VIA combination to include in a given delivery. As for MinimumStopVisitsPerLine but with Via also taken into account. SIRI+v2.0 + The minimum number of Stop Visits for a given LINE and VIA combination to include in a given delivery. As for MinimumStopVisitsPerLine but with Via also taken into account. (since SIRI 2.0) @@ -229,7 +229,7 @@ Rail transport, Roads and road transport - Whether any related SITUATIONs should be included in the ServiceDelivery. Default is 'false'. +SIRI v2.0 + Whether any related SITUATIONs should be included in the ServiceDelivery. Default is 'false'. (since SIRI 2.0) @@ -428,7 +428,7 @@ If false each subscription response will contain the full information as specifi - Name to use to describe monitoring point (Stop or display). Normally Consumer will already have access to this in its reference data but may be included to increase utility of delivery data i to devices that do not hold reference data, e.g. for SIRI LITE services(+SIRI v2.0). + Name to use to describe monitoring point (Stop or display). Normally Consumer will already have access to this in its reference data but may be included to increase utility of delivery data i to devices that do not hold reference data, e.g. for SIRI LITE services((since SIRI 2.0)). @@ -484,7 +484,7 @@ If false each subscription response will contain the full information as specifi - Time until when data is valid. +SIRI 2.0 + Time until when data is valid. (since SIRI 2.0) @@ -600,7 +600,7 @@ If false each subscription response will contain the full information as specifi - Name or Number by which the LINE is known to the public. +SIRI v2.0 + Name or Number by which the LINE is known to the public. (since SIRI 2.0) @@ -610,7 +610,7 @@ If false each subscription response will contain the full information as specifi - Variant of a notice for use in a particular media channel. +SIRI v2.0 + Variant of a notice for use in a particular media channel. (since SIRI 2.0) @@ -621,12 +621,12 @@ If false each subscription response will contain the full information as specifi - Type for Delivery Variant +SIRI v2.0 + Type for Delivery Variant (since SIRI 2.0) - Classification of DELIVERY VARIANT +SIRI v2.0. + Classification of DELIVERY VARIANT (since SIRI 2.0). @@ -925,7 +925,7 @@ If false each subscription response will contain the full information as specifi - Whether result supports SITUATION REFERENCESs. Default is 'false'. +SIRI v2.0 + Whether result supports SITUATION REFERENCESs. Default is 'false'. (since SIRI 2.0) @@ -1002,7 +1002,7 @@ If false each subscription response will contain the full information as specifi - Whether results can be limited to include a minimum numVIA (i.e. per JOURNEY PATTERN). +SIRI v2.0. + Whether results can be limited to include a minimum numVIA (i.e. per JOURNEY PATTERN). (since SIRI 2.0). default is 'false'. diff --git a/xsd/siri_stopTimetable_service.xsd b/xsd/siri_stopTimetable_service.xsd index 5b925dc3..92c30b07 100644 --- a/xsd/siri_stopTimetable_service.xsd +++ b/xsd/siri_stopTimetable_service.xsd @@ -36,7 +36,7 @@ Revise to support substitution groups 2012-03-23 - +SIRI v2.0 + (since SIRI 2.0) Improve modualirisatuioin Factor out permissions to commomn files factor out targeted journey, diff --git a/xsd/siri_utility/siri_location.xsd b/xsd/siri_utility/siri_location.xsd index 90763b71..12af18dc 100644 --- a/xsd/siri_utility/siri_location.xsd +++ b/xsd/siri_utility/siri_location.xsd @@ -182,7 +182,7 @@ Rail transport, Roads and road transport - Defines a bounding box using two corner points. GML terminology. +SIRI v2.0 + Defines a bounding box using two corner points. GML terminology. (since SIRI 2.0) @@ -199,19 +199,19 @@ Rail transport, Roads and road transport - Defines a line shape +SIRI v2.0 + Defines a line shape (since SIRI 2.0) - A geospatial point. +SIRI v2.0 + A geospatial point. (since SIRI 2.0) - Type for a circular area centered around a point that may be expressed in concrete WGS 84 Coordinates or any gml compatible point coordinates format. +SIRI v2.1 + Type for a circular area centered around a point that may be expressed in concrete WGS 84 Coordinates or any gml compatible point coordinates format. (since SIRI 2.1) @@ -227,7 +227,7 @@ Rail transport, Roads and road transport - Bounding box, circular area or gml:polyon of the area where stops of a flexible service are called. +SIRI v2.1 + Bounding box, circular area or gml:polyon of the area where stops of a flexible service are called. (since SIRI 2.1) A flexible area is used in cases where a pre-booked service allows pick-up/drop-off anywhere in a designated area and provides a possible interchange to a higher-frequency service. diff --git a/xsd/siri_utility/siri_utility.xsd b/xsd/siri_utility/siri_utility.xsd index 26b81dbd..c71e0055 100644 --- a/xsd/siri_utility/siri_utility.xsd +++ b/xsd/siri_utility/siri_utility.xsd @@ -85,7 +85,7 @@ Rail transport, Roads and road transport - A list of alternative Key values for an element. +SIRI v2.1 + A list of alternative Key values for an element. (since SIRI 2.1) @@ -98,7 +98,7 @@ Rail transport, Roads and road transport - Type for a Key List. +SIRI v2.1 + Type for a Key List. (since SIRI 2.1) @@ -110,7 +110,7 @@ Rail transport, Roads and road transport - Type for a Key List. +SIRI v2.1 + Type for a Key List. (since SIRI 2.1) @@ -135,7 +135,7 @@ Rail transport, Roads and road transport VALUE SETs and TYPE OF VALUEs as part of the SIRI extension model. TYPES OF VALUE can be used to exchange metadata for validation or collection of data, -such as the description and allowed values for codes. +SIRI v2.1 +such as the description and allowed values for codes. (since SIRI 2.1) @@ -147,7 +147,7 @@ such as the description and allowed values for codes. +SIRI v2.1 - Type for containment of VALUE SETs and/or TYPE OF VALUEs. +SIRI v2.1 + Type for containment of VALUE SETs and/or TYPE OF VALUEs. (since SIRI 2.1) @@ -156,12 +156,12 @@ such as the description and allowed values for codes. +SIRI v2.1 - A code value from an extensible set which may be added to by user applications, and is used to classify other SIRI entities. +SIRI v2.1 + A code value from an extensible set which may be added to by user applications, and is used to classify other SIRI entities. (since SIRI 2.1) - Type for a TYPE OF VALUE. Used to define open classifications of value types. +SIRI v2.1 + Type for a TYPE OF VALUE. Used to define open classifications of value types. (since SIRI 2.1) @@ -179,7 +179,7 @@ such as the description and allowed values for codes. +SIRI v2.1 - Elements for TYPE OF VALUE. +SIRI v2.1 + Elements for TYPE OF VALUE. (since SIRI 2.1) @@ -217,7 +217,7 @@ such as the description and allowed values for codes. +SIRI v2.1 An extensible set of code values which may be added to by user applications and is used to validate the properties of entities. -Contains TYPE OF VALUEs that are an instance of the same class. +SIRI v2.1 +Contains TYPE OF VALUEs that are an instance of the same class. (since SIRI 2.1) @@ -229,7 +229,7 @@ Contains TYPE OF VALUEs that are an instance of the same class. +SIRI v2.1 - Type for a VALUE SET. Used to define open classifications of value types. +SIRI v2.1 + Type for a VALUE SET. Used to define open classifications of value types. (since SIRI 2.1) @@ -247,7 +247,7 @@ Contains TYPE OF VALUEs that are an instance of the same class. +SIRI v2.1 - Elements for VALUE SET. +SIRI v2.1 + Elements for VALUE SET. (since SIRI 2.1) @@ -264,7 +264,7 @@ Contains TYPE OF VALUEs that are an instance of the same class. +SIRI v2.1 - Type for a list of TYPE OF VALUEs. +SIRI v2.1 + Type for a list of TYPE OF VALUEs. (since SIRI 2.1) @@ -273,13 +273,13 @@ Contains TYPE OF VALUEs that are an instance of the same class. +SIRI v2.1 - Type for identifier of a TYPE OF VALUE. +SIRI v2.1 + Type for identifier of a TYPE OF VALUE. (since SIRI 2.1) - Type for reference to a TYPE OF VALUE. +SIRI v2.1 + Type for reference to a TYPE OF VALUE. (since SIRI 2.1) @@ -287,13 +287,13 @@ Contains TYPE OF VALUEs that are an instance of the same class. +SIRI v2.1 - Type for identifier of a VALUE SET. +SIRI v2.1 + Type for identifier of a VALUE SET. (since SIRI 2.1) - Name of class of which TypeOfValue is an instance. Used for reflection. +SIRI v2.1 + Name of class of which TypeOfValue is an instance. Used for reflection. (since SIRI 2.1) diff --git a/xsd/siri_vehicleMonitoring_service.xsd b/xsd/siri_vehicleMonitoring_service.xsd index ac3611c0..98491a1e 100644 --- a/xsd/siri_vehicleMonitoring_service.xsd +++ b/xsd/siri_vehicleMonitoring_service.xsd @@ -41,7 +41,7 @@ [MTA] Add MaximumNumberOfCalls to request [SIRI-LITE] Allow a monitoring name in VehicleActivity results. [VDV] Revise MonitoredVehicleJourney to include additional result files - [SIRI-LITE] Whether any related Situations should be included in the ServiceDelivery. Default is 'false'. +SIRI v2.0 --> + [SIRI-LITE] Whether any related Situations should be included in the ServiceDelivery. Default is 'false'. (since SIRI 2.0) --> 2012-04-29 @@ -222,18 +222,18 @@ Rail transport, Roads and road transport - If calls are to be returned, maximum number of calls to include in response. If absent, exclude all calls. +SIRI v2.0. + If calls are to be returned, maximum number of calls to include in response. If absent, exclude all calls. (since SIRI 2.0). - Maximum number of previous calls to include. Only applies if VehicleMonitoringDetailLevel of Calls specified. Zero for none. If VehicleMonitoringDetailLevel of Calls specified but MaximumNumberOfCalls.Previous absent, include all previous calls. +SIRI v2.0. + Maximum number of previous calls to include. Only applies if VehicleMonitoringDetailLevel of Calls specified. Zero for none. If VehicleMonitoringDetailLevel of Calls specified but MaximumNumberOfCalls.Previous absent, include all previous calls. (since SIRI 2.0). - Maximum number of onwards calls to include. Zero for none. Only applies if VehicleMonitoringDetailLevel of 'calls' specified. Zero for none. If VehicleMonitoringDetailLevel calls specified but MaximumNumberOfCalls.Onwards absent, include all onwards calls. +SIRI v2.0. + Maximum number of onwards calls to include. Zero for none. Only applies if VehicleMonitoringDetailLevel of 'calls' specified. Zero for none. If VehicleMonitoringDetailLevel calls specified but MaximumNumberOfCalls.Onwards absent, include all onwards calls. (since SIRI 2.0). @@ -241,7 +241,7 @@ Rail transport, Roads and road transport - Whether any related Situations should be included in the ServiceDelivery. Default is 'false'. +SIRI v2.0 + Whether any related Situations should be included in the ServiceDelivery. Default is 'false'. (since SIRI 2.0) @@ -359,7 +359,7 @@ If false or omitted, each subscription response will contain the full informatio - Name associated with Monitoring Reference. Supports SIRI LITE servcies (+SIRI v2.0). + Name associated with Monitoring Reference. Supports SIRI LITE servcies ((since SIRI 2.0)). @@ -587,7 +587,7 @@ If false or omitted, each subscription response will contain the full informatio - Whether result supports SITUATION REFERENCESs. Default is 'false'. +SIRI v2.0 + Whether result supports SITUATION REFERENCESs. Default is 'false'. (since SIRI 2.0)             @@ -620,17 +620,17 @@ If false or omitted, each subscription response will contain the full informatio             - If system can return detailed calling pattern, whether a number of calls to include can be specified. Default is 'false'. +SIRI 2.0 + If system can return detailed calling pattern, whether a number of calls to include can be specified. Default is 'false'. (since SIRI 2.0) - If system can return detailed calling pattern, whether a number of onwards calls to include can be specified. Default is 'false'. +SIRI 2.0 + If system can return detailed calling pattern, whether a number of onwards calls to include can be specified. Default is 'false'. (since SIRI 2.0) - If system can return detailed calling pattern, whether a number of previous calls to include can be specified. Default is 'false'. +SIRI 2.0 + If system can return detailed calling pattern, whether a number of previous calls to include can be specified. Default is 'false'. (since SIRI 2.0)