siri-xsd 0.1.0

Sign up to get free protection for your applications and to get access to all the features.
Files changed (107) hide show
  1. checksums.yaml +7 -0
  2. data/.gitignore +10 -0
  3. data/Gemfile +4 -0
  4. data/Gemfile.lock +47 -0
  5. data/README.md +23 -0
  6. data/bitbucket-pipelines.yml +18 -0
  7. data/exe/siri-xsd-validate +42 -0
  8. data/lib/siri/xsd/validator.rb +62 -0
  9. data/lib/siri/xsd/version.rb +5 -0
  10. data/lib/siri/xsd.rb +10 -0
  11. data/siri-xsd.gemspec +35 -0
  12. data/vendor/xsd/acsb/acsb_accessibility.xsd +138 -0
  13. data/vendor/xsd/acsb/acsb_all.xsd +11 -0
  14. data/vendor/xsd/acsb/acsb_limitations.xsd +141 -0
  15. data/vendor/xsd/acsb/acsb_passengerMobility.xsd +212 -0
  16. data/vendor/xsd/datex2/DATEXIISchema.xsd +3713 -0
  17. data/vendor/xsd/datex2/DATEXIISchemaWithDefinitions.xsd +11538 -0
  18. data/vendor/xsd/gml/basicTypes.xsd +267 -0
  19. data/vendor/xsd/gml/geometryBasic0d1d-extract.xsd +271 -0
  20. data/vendor/xsd/gml/gmlBase-extract.xsd +168 -0
  21. data/vendor/xsd/gml/gmlBasic2d-extract.xsd +120 -0
  22. data/vendor/xsd/gml/gml_extract_all_objects.xsd +12 -0
  23. data/vendor/xsd/ifopt/ifopt_administration.xsd +254 -0
  24. data/vendor/xsd/ifopt/ifopt_allStopPlace.xsd +33 -0
  25. data/vendor/xsd/ifopt/ifopt_checkpoint.xsd +222 -0
  26. data/vendor/xsd/ifopt/ifopt_countries.xsd +1320 -0
  27. data/vendor/xsd/ifopt/ifopt_equipment.xsd +207 -0
  28. data/vendor/xsd/ifopt/ifopt_location.xsd +281 -0
  29. data/vendor/xsd/ifopt/ifopt_modes.xsd +84 -0
  30. data/vendor/xsd/ifopt/ifopt_modification.xsd +173 -0
  31. data/vendor/xsd/ifopt/ifopt_path.xsd +164 -0
  32. data/vendor/xsd/ifopt/ifopt_stop.xsd +403 -0
  33. data/vendor/xsd/ifopt/ifopt_time.xsd +131 -0
  34. data/vendor/xsd/ifopt/ifopt_types.xsd +96 -0
  35. data/vendor/xsd/siri/siri_all_framework.xsd +12 -0
  36. data/vendor/xsd/siri/siri_base.xsd +315 -0
  37. data/vendor/xsd/siri/siri_common_services.xsd +900 -0
  38. data/vendor/xsd/siri/siri_request_errorConditions.xsd +590 -0
  39. data/vendor/xsd/siri/siri_request_support.xsd +210 -0
  40. data/vendor/xsd/siri/siri_requests.xsd +1072 -0
  41. data/vendor/xsd/siri.xsd +531 -0
  42. data/vendor/xsd/siriSg.xsd +149 -0
  43. data/vendor/xsd/siri_all_functionalServices.xsd +95 -0
  44. data/vendor/xsd/siri_connectionMonitoring_service.xsd +731 -0
  45. data/vendor/xsd/siri_connectionTimetable_service.xsd +485 -0
  46. data/vendor/xsd/siri_discovery.xsd +898 -0
  47. data/vendor/xsd/siri_estimatedTimetable_service.xsd +490 -0
  48. data/vendor/xsd/siri_facilityMonitoring_service.xsd +493 -0
  49. data/vendor/xsd/siri_generalMessage_service.xsd +483 -0
  50. data/vendor/xsd/siri_model/siri_all.xsd +13 -0
  51. data/vendor/xsd/siri_model/siri_all_journeyModel.xsd +21 -0
  52. data/vendor/xsd/siri_model/siri_all_model.xsd +13 -0
  53. data/vendor/xsd/siri_model/siri_all_situation.xsd +17 -0
  54. data/vendor/xsd/siri_model/siri_datedVehicleJourney.xsd +702 -0
  55. data/vendor/xsd/siri_model/siri_estimatedVehicleJourney.xsd +472 -0
  56. data/vendor/xsd/siri_model/siri_facilities.xsd +517 -0
  57. data/vendor/xsd/siri_model/siri_facility.xsd +760 -0
  58. data/vendor/xsd/siri_model/siri_feature_support.xsd +145 -0
  59. data/vendor/xsd/siri_model/siri_interchangeJourney.xsd +88 -0
  60. data/vendor/xsd/siri_model/siri_journey.xsd +1903 -0
  61. data/vendor/xsd/siri_model/siri_journey_support.xsd +1022 -0
  62. data/vendor/xsd/siri_model/siri_modelPermissions.xsd +338 -0
  63. data/vendor/xsd/siri_model/siri_modes.xsd +686 -0
  64. data/vendor/xsd/siri_model/siri_monitoredVehicleJourney.xsd +638 -0
  65. data/vendor/xsd/siri_model/siri_operator_support.xsd +87 -0
  66. data/vendor/xsd/siri_model/siri_reference.xsd +844 -0
  67. data/vendor/xsd/siri_model/siri_situation.xsd +1545 -0
  68. data/vendor/xsd/siri_model/siri_situationActions.xsd +755 -0
  69. data/vendor/xsd/siri_model/siri_situationAffects.xsd +1533 -0
  70. data/vendor/xsd/siri_model/siri_situationClassifiers.xsd +430 -0
  71. data/vendor/xsd/siri_model/siri_situationIdentity.xsd +247 -0
  72. data/vendor/xsd/siri_model/siri_situationReasons.xsd +1370 -0
  73. data/vendor/xsd/siri_model/siri_situationServiceTypes.xsd +639 -0
  74. data/vendor/xsd/siri_model/siri_targetedVehicleJourney.xsd +136 -0
  75. data/vendor/xsd/siri_model/siri_time.xsd +356 -0
  76. data/vendor/xsd/siri_model_discovery/siri_connectionLink.xsd +115 -0
  77. data/vendor/xsd/siri_model_discovery/siri_feature.xsd +158 -0
  78. data/vendor/xsd/siri_model_discovery/siri_infoChannel.xsd +99 -0
  79. data/vendor/xsd/siri_model_discovery/siri_line.xsd +241 -0
  80. data/vendor/xsd/siri_model_discovery/siri_stopPoint.xsd +158 -0
  81. data/vendor/xsd/siri_productionTimetable_service.xsd +514 -0
  82. data/vendor/xsd/siri_situationExchange_service.xsd +785 -0
  83. data/vendor/xsd/siri_stopMonitoring_service.xsd +1052 -0
  84. data/vendor/xsd/siri_stopTimetable_service.xsd +463 -0
  85. data/vendor/xsd/siri_utility/siri_all_utility.xsd +14 -0
  86. data/vendor/xsd/siri_utility/siri_location.xsd +270 -0
  87. data/vendor/xsd/siri_utility/siri_participant.xsd +79 -0
  88. data/vendor/xsd/siri_utility/siri_permissions.xsd +135 -0
  89. data/vendor/xsd/siri_utility/siri_types.xsd +166 -0
  90. data/vendor/xsd/siri_utility/siri_utility.xsd +301 -0
  91. data/vendor/xsd/siri_vehicleMonitoring_service.xsd +702 -0
  92. data/vendor/xsd/siri_wsConsumer-Document.wsdl +177 -0
  93. data/vendor/xsd/siri_wsConsumer-WSDL2.wsdl +96 -0
  94. data/vendor/xsd/siri_wsConsumer.wsdl +200 -0
  95. data/vendor/xsd/siri_wsProducer-Document.wsdl +558 -0
  96. data/vendor/xsd/siri_wsProducer-WSDL2.wsdl +229 -0
  97. data/vendor/xsd/siri_wsProducer.wsdl +629 -0
  98. data/vendor/xsd/soap.xsd +118 -0
  99. data/vendor/xsd/wsdl_model/siri-wsdl.xsd +8 -0
  100. data/vendor/xsd/wsdl_model/siri_wsConsumer-Framework.xsd +98 -0
  101. data/vendor/xsd/wsdl_model/siri_wsConsumer-Services.xsd +155 -0
  102. data/vendor/xsd/wsdl_model/siri_wsProducer-DiscoveryCapability.xsd +123 -0
  103. data/vendor/xsd/wsdl_model/siri_wsProducer-Framework.xsd +138 -0
  104. data/vendor/xsd/wsdl_model/siri_wsProducer-Services.xsd +263 -0
  105. data/vendor/xsd/xml/2008/09/xsd.xsl +997 -0
  106. data/vendor/xsd/xml/2009/01/XMLSchema.xsd +286 -0
  107. metadata +222 -0
data/vendor/xsd/siri_model/siri_estimatedVehicleJourney.xsd ADDED
@@ -0,0 +1,472 @@
1
+ <?xml version="1.0" encoding="UTF-8"?>
2
+ <xsd:schema xmlns="http://www.siri.org.uk/siri" xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.siri.org.uk/siri" elementFormDefault="qualified" attributeFormDefault="unqualified" version="2.1" id="siri_estimatedVehicleJourney">
3
+ <xsd:annotation>
4
+ <xsd:appinfo>
5
+ <Metadata xmlns="http://www.govtalk.gov.uk/CM/gms-xs">
6
+ <Aggregation>main schema</Aggregation>
7
+ <Audience>e-service developers</Audience>
8
+ <Contributor>CEN TC278 WG3 SG7 Team</Contributor>
9
+ <Contributor>Werner Kohl MDV</Contributor>
10
+ <Coverage>Europe</Coverage>
11
+ <Creator>Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk</Creator>
12
+ <Date>
13
+ <Created>2003-02-10</Created>
14
+ </Date>
15
+ <Date>
16
+ <Modified>2004-10-31</Modified>
17
+ </Date>
18
+ <Date>
19
+ <Modified>2005-02-14</Modified>
20
+ </Date>
21
+ <Date>
22
+ <Modified>2005-02-20</Modified>
23
+ </Date>
24
+ <Date>
25
+ <Modified>2005-05-11</Modified>
26
+ </Date>
27
+ <Date>
28
+ <Modified>2007-04-17</Modified>
29
+ <!-- Name Space changes -->
30
+ </Date>
31
+ <Date>
32
+ <Modified>2008-03-26</Modified>
33
+ <!-- Add wrapper tag for Line DIRECTION to help binding to Axis -->
34
+ </Date>
35
+ <Date>
36
+ <Modified>2008-11-17</Modified>
37
+ <!-- Revise to support substitution groups -->
38
+ </Date>
39
+ <Date>
40
+ <Modified>2011-01-19</Modified>
41
+ <!-- Drop use of As Flat Groups for EstimatedCalls -->
42
+ </Date>
43
+ <Date>
44
+ <Modified>2012-03-23</Modified>
45
+ <!-- +SIRI v2.0
46
+ Factored out of estimatedTimetableService
47
+ Add EstimatedServiceJourneyInterchange (i.e. Estimated Connection of VEHICLE) to EstimatedTimetableDelivery
48
+ Corrected feed and distributor Journety refs and add InterchangeRef -->
49
+ </Date>
50
+ <Description>
51
+ <p>SIRI is a European CEN standard for the exchange of Public Transport real-time information.</p>
52
+ <p>This sub-schema describes the Estimated Timetable Service.</p>
53
+ </Description>
54
+ <Format>
55
+ <MediaType>text/xml</MediaType>
56
+ <Syntax>http://www.w3.org/2001/XMLSchema</Syntax>
57
+ <Description>XML schema, W3C Recommendation 2001</Description>
58
+ </Format>
59
+ <Identifier>{http://www.siri.org.uk/schema/2.0/xsd/siri_model}siri_estimatedVehicleJourney.xsd</Identifier>
60
+ <Language>[ISO 639-2/B] ENG</Language>
61
+ <Publisher>Kizoom, 109-123 Clifton Street, London EC4A 4LD </Publisher>
62
+ <Relation>
63
+ <Requires>http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd</Requires>
64
+ </Relation>
65
+ <Rights><!--Unclassified-->
66
+ <Copyright>CEN, VDV, RTIG 2004-2021</Copyright>
67
+ </Rights>
68
+ <Source>
69
+ <ul>
70
+ <li>Derived from the VDV, RTIG XML and Trident standards.</li>
71
+ </ul>
72
+ </Source>
73
+ <Status>Version 2.1</Status>
74
+ <Subject>
75
+ <Category>Arts, recreation and travel, Tourism, Travel (tourism), Transport,
76
+ Air transport, Airports,
77
+ Ports and maritime transport, Ferries (marine),
78
+ Public transport, Bus services, Coach services, Bus stops and stations,
79
+ Rail transport, Railway stations and track, Train services, Underground trains,
80
+ Business and industry, Transport, Air transport, Ports and maritime transport, Public transport,
81
+ Rail transport, Roads and road transport
82
+ </Category>
83
+ <Project>CEN TC278 WG3 SG7</Project>
84
+ </Subject>
85
+ <Title>SIRI-ET XML schema. Service Interface for Real-time Information. Estimated Timetable Service.</Title>
86
+ <Type>Standard</Type>
87
+ </Metadata>
88
+ </xsd:appinfo>
89
+ <xsd:documentation>SIRI-ET Estimated Timetable Service.</xsd:documentation>
90
+ </xsd:annotation>
91
+ <!-- ==== Dependencies=========================================-->
92
+ <xsd:include schemaLocation="siri_monitoredVehicleJourney.xsd"/>
93
+ <xsd:include schemaLocation="siri_datedVehicleJourney.xsd"/>
94
+ <xsd:include schemaLocation="siri_situationServiceTypes.xsd"/>
95
+ <!-- ======================================================================= -->
96
+ <xsd:element name="EstimatedVehicleJourney" type="EstimatedVehicleJourneyStructure">
97
+ <xsd:annotation>
98
+ <xsd:documentation>A VEHICLE JOURNEY taking place on a particular date that will be managed by an AVMs.</xsd:documentation>
99
+ </xsd:annotation>
100
+ </xsd:element>
101
+ <xsd:group name="EstimatedTimetableAlterationGroup">
102
+ <xsd:annotation>
103
+ <xsd:documentation>If the journey is an alteration to a timetable, indicates the original journey and the nature of the difference.</xsd:documentation>
104
+ </xsd:annotation>
105
+ <xsd:sequence>
106
+ <xsd:choice>
107
+ <xsd:sequence>
108
+ <xsd:choice>
109
+ <xsd:element name="FramedVehicleJourneyRef" type="FramedVehicleJourneyRefStructure">
110
+ <xsd:annotation>
111
+ <xsd:documentation>Identifer of a VEHICLE JOURNEY within data Horizon of a service.</xsd:documentation>
112
+ </xsd:annotation>
113
+ </xsd:element>
114
+ <xsd:element name="DatedVehicleJourneyRef" type="DatedVehicleJourneyRefStructure">
115
+ <xsd:annotation>
116
+ <xsd:documentation>Reference to a dated VEHICLE JOURNEY. This will be 'framed' i.e. be with the data context of the ESTIMATED Timetable.
117
+ DEPRECATED from SIRI 2.0</xsd:documentation>
118
+ </xsd:annotation>
119
+ </xsd:element>
120
+ </xsd:choice>
121
+ <xsd:element name="DatedVehicleJourneyIndirectRef" type="DatedVehicleJourneyIndirectRefStructure" minOccurs="0">
122
+ <xsd:annotation>
123
+ <xsd:documentation>Additionally, identify the VEHICLE JOURNEY by origin and destination and the scheduled times at these stops.</xsd:documentation>
124
+ </xsd:annotation>
125
+ </xsd:element>
126
+ </xsd:sequence>
127
+ <xsd:element name="EstimatedVehicleJourneyCode" type="EstimatedVehicleJourneyCodeType">
128
+ <xsd:annotation>
129
+ <xsd:documentation>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'.
130
+ DEPRECATED from SIRI 2.0</xsd:documentation>
131
+ </xsd:annotation>
132
+ </xsd:element>
133
+ </xsd:choice>
134
+ <xsd:choice>
135
+ <xsd:element name="ExtraJourney" type="xsd:boolean" default="false" minOccurs="0">
136
+ <xsd:annotation>
137
+ <xsd:documentation>Whether this VEHICLE JOURNEY is an addition to the planning data already sent. Default is 'false': i.e. not an additional journey.</xsd:documentation>
138
+ </xsd:annotation>
139
+ </xsd:element>
140
+ <xsd:element name="Cancellation" type="xsd:boolean" default="false" minOccurs="0">
141
+ <xsd:annotation>
142
+ <xsd:documentation>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.</xsd:documentation>
143
+ </xsd:annotation>
144
+ </xsd:element>
145
+ </xsd:choice>
146
+ </xsd:sequence>
147
+ </xsd:group>
148
+ <!-- ======================================================================= -->
149
+ <xsd:element name="EstimatedServiceJourneyInterchange" type="EstimatedServiceJourneyInterchangeStructure">
150
+ <xsd:annotation>
151
+ <xsd:documentation>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</xsd:documentation>
152
+ </xsd:annotation>
153
+ </xsd:element>
154
+ <xsd:complexType name="EstimatedServiceJourneyInterchangeStructure">
155
+ <xsd:annotation>
156
+ <xsd:documentation>Type for Estimated SERVICE JOURNEY INTERCHANGE.</xsd:documentation>
157
+ </xsd:annotation>
158
+ <xsd:sequence>
159
+ <xsd:choice>
160
+ <xsd:element ref="InterchangeRef"/>
161
+ <xsd:sequence>
162
+ <xsd:element name="InterchangeCode" type="InterchangeCodeType" minOccurs="0">
163
+ <xsd:annotation>
164
+ <xsd:documentation>Identifier of ESTIMATED SERVICE JOURNEY INTERCHANGE in case it is an addition to the plan. +SIRI v2.1</xsd:documentation>
165
+ </xsd:annotation>
166
+ </xsd:element>
167
+ <xsd:element name="ConnectionLinkRef" type="ConnectionLinkRefStructure" minOccurs="0">
168
+ <xsd:annotation>
169
+ <xsd:documentation>Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY INTERCHANGE takes place. +SIRI v2.0</xsd:documentation>
170
+ </xsd:annotation>
171
+ </xsd:element>
172
+ <xsd:element name="FeederJourneyRef" type="ConnectingJourneyRefStructure">
173
+ <xsd:annotation>
174
+ <xsd:documentation>Reference to a connecting feeder VEHICLE JOURNEY. +SIRI v2.0</xsd:documentation>
175
+ </xsd:annotation>
176
+ </xsd:element>
177
+ <xsd:element name="FeederArrivalStopRef" type="StopPointRefStructure" minOccurs="0">
178
+ <xsd:annotation>
179
+ <xsd:documentation>SCHEDULED STOP POINT at which feeder journey arrives.
180
+ Assuming, for example, that the feeder is redirected to another QUAY by a dispositive measure in order to shorten the transfer time,
181
+ how do we communicate this change in the interchange? If the STOP POINTs are modelled QUAY accurate, FeederArrivalStopRef should always
182
+ reference the STOP POINT of the new/expected QUAY (which was transmitted in the ESTIMATED VEHICLE JOURNEY). +SIRI v2.1</xsd:documentation>
183
+ </xsd:annotation>
184
+ </xsd:element>
185
+ <xsd:element name="FeederVisitNumber" type="VisitNumberType" minOccurs="0">
186
+ <xsd:annotation>
187
+ <xsd:documentation>Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN.</xsd:documentation>
188
+ </xsd:annotation>
189
+ </xsd:element>
190
+ <xsd:element name="FeederStopOrder" type="xsd:positiveInteger" minOccurs="0">
191
+ <xsd:annotation>
192
+ <xsd:documentation>For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false,
193
+ 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
194
+ despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1</xsd:documentation>
195
+ </xsd:annotation>
196
+ </xsd:element>
197
+ <xsd:element name="AimedArrivalTimeOfFeeder" type="xsd:dateTime" minOccurs="0">
198
+ <xsd:annotation>
199
+ <xsd:documentation>Planned time at which feeder VEHICLE is scheduled to arrive. SIRI v2.1</xsd:documentation>
200
+ </xsd:annotation>
201
+ </xsd:element>
202
+ <xsd:element name="DistributorJourneyRef" type="ConnectingJourneyRefStructure">
203
+ <xsd:annotation>
204
+ <xsd:documentation>Reference to a connecting distributor VEHICLE JOURNEY. +SIRI v2.0</xsd:documentation>
205
+ </xsd:annotation>
206
+ </xsd:element>
207
+ <xsd:element name="DistributorDepartureStopRef" type="StopPointRefStructure" minOccurs="0">
208
+ <xsd:annotation>
209
+ <xsd:documentation>SCHEDULED STOP POINT at which distributor journey departs.
210
+ Assuming that the distributor is directed to another QUAY (and that STOP POINTs are modelled QUAY accurate), DistributorDepartureStopRef
211
+ should always reference the STOP POINT of the new/expected QUAY (which was transmitted in the ESTIMATED VEHICLE JOURNEY). +SIRI v2.1</xsd:documentation>
212
+ </xsd:annotation>
213
+ </xsd:element>
214
+ <xsd:element name="DistributorVisitNumber" type="VisitNumberType" minOccurs="0">
215
+ <xsd:annotation>
216
+ <xsd:documentation>Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN.</xsd:documentation>
217
+ </xsd:annotation>
218
+ </xsd:element>
219
+ <xsd:element name="DistributorStopOrder" type="xsd:positiveInteger" minOccurs="0">
220
+ <xsd:annotation>
221
+ <xsd:documentation>For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false,
222
+ 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
223
+ despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. +SIRI v2.1</xsd:documentation>
224
+ </xsd:annotation>
225
+ </xsd:element>
226
+ <xsd:element name="AimedDepartureTimeOfDistributor" type="xsd:dateTime" minOccurs="0">
227
+ <xsd:annotation>
228
+ <xsd:documentation>Planned time at which distributor VEHICLE is scheduled to depart. SIRI v2.1</xsd:documentation>
229
+ </xsd:annotation>
230
+ </xsd:element>
231
+ <xsd:group ref="InterchangePropertyGroup" minOccurs="0">
232
+ <xsd:annotation>
233
+ <xsd:documentation>Properties of SERVICE JOURNEY INTERCHANGE. It is important to note that the InterchangePropertyGroup displays planning data whereas, for example,
234
+ 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.
235
+ 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</xsd:documentation>
236
+ </xsd:annotation>
237
+ </xsd:group>
238
+ </xsd:sequence>
239
+ </xsd:choice>
240
+ <xsd:element name="InterchangeStatus" type="InterchangeStatusEnumeration" minOccurs="0">
241
+ <xsd:annotation>
242
+ <xsd:documentation>Whether this interchange is planned, updated, additional or cancelled. +SIRI v2.1</xsd:documentation>
243
+ </xsd:annotation>
244
+ </xsd:element>
245
+ <xsd:choice>
246
+ <xsd:element name="WillNotWait" type="EmptyType">
247
+ <xsd:annotation>
248
+ <xsd:documentation>Distributor will not wait, i.e., connection is not guaranteed or broken. SIRI 2.0</xsd:documentation>
249
+ </xsd:annotation>
250
+ </xsd:element>
251
+ <xsd:element name="WillWait" type="WillWaitStructure">
252
+ <xsd:annotation>
253
+ <xsd:documentation>Details about how (long) the distributor services may be held in order to guarantee the connection. +SIRI v2.0</xsd:documentation>
254
+ </xsd:annotation>
255
+ </xsd:element>
256
+ </xsd:choice>
257
+ <xsd:element name="ExpectedArrivalTimeOfFeeder" type="xsd:dateTime" minOccurs="0">
258
+ <xsd:annotation>
259
+ <xsd:documentation>Time at which feeder VEHICLE is expected to arrive. +SIRI v2.1</xsd:documentation>
260
+ </xsd:annotation>
261
+ </xsd:element>
262
+ <xsd:element name="ExpectedDepartureTimeOfDistributor" type="xsd:dateTime" minOccurs="0">
263
+ <xsd:annotation>
264
+ <xsd:documentation>Time at which distributor VEHICLE is expected to depart. +SIRI v2.0</xsd:documentation>
265
+ </xsd:annotation>
266
+ </xsd:element>
267
+ <xsd:element name="ConnectionMonitoring" type="xsd:boolean" minOccurs="0">
268
+ <xsd:annotation>
269
+ <xsd:documentation>Whether connection monitoring is active or not for this connection. +SIRI v2.0</xsd:documentation>
270
+ </xsd:annotation>
271
+ </xsd:element>
272
+ <xsd:group ref="InterchangeTimesGroup" minOccurs="0">
273
+ <xsd:annotation>
274
+ <xsd:documentation>Contains various types of transfer and wait times of a SERVICE JOURNEY INTERCHANGE.
275
+ 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?
276
+ In case of doubt, the interchange times are to be favoured because they are transmitted explicitly. +SIRI v2.1</xsd:documentation>
277
+ </xsd:annotation>
278
+ </xsd:group>
279
+ <xsd:element ref="Extensions" minOccurs="0"/>
280
+ </xsd:sequence>
281
+ </xsd:complexType>
282
+ <xsd:complexType name="WillWaitStructure">
283
+ <xsd:annotation>
284
+ <xsd:documentation>Type for Will Wait details</xsd:documentation>
285
+ </xsd:annotation>
286
+ <xsd:sequence>
287
+ <xsd:element name="WaitUntilTime" type="xsd:dateTime">
288
+ <xsd:annotation>
289
+ <xsd:documentation>Time up until which the distributor will wait. +SIRI v2.0</xsd:documentation>
290
+ </xsd:annotation>
291
+ </xsd:element>
292
+ <xsd:choice minOccurs="0">
293
+ <xsd:element name="DriverHasAcknowledgeWIllWait" type="xsd:boolean" minOccurs="0">
294
+ <xsd:annotation>
295
+ <xsd:documentation>Whether an acknowledgement has been received that the driver will wait.
296
+ DEPRECATED since SIRI v2.1</xsd:documentation>
297
+ </xsd:annotation>
298
+ </xsd:element>
299
+ <xsd:element name="DriverHasAcknowledgedWillWait" type="xsd:boolean" minOccurs="0">
300
+ <xsd:annotation>
301
+ <xsd:documentation>Whether an acknowledgement has been received that the driver will wait. +SIRI v2.1</xsd:documentation>
302
+ </xsd:annotation>
303
+ </xsd:element>
304
+ </xsd:choice>
305
+ </xsd:sequence>
306
+ </xsd:complexType>
307
+ <!-- ======================================================================= -->
308
+ <xsd:complexType name="EstimatedVehicleJourneyStructure">
309
+ <xsd:annotation>
310
+ <xsd:documentation>Type for Real-time info about a VEHICLE JOURNEY.</xsd:documentation>
311
+ </xsd:annotation>
312
+ <xsd:sequence>
313
+ <xsd:element name="RecordedAtTime" type="xsd:dateTime" minOccurs="0">
314
+ <xsd:annotation>
315
+ <xsd:documentation>Time at which data of individual journey was recorded if differet from that of frame. (+SIRI 2.0.)</xsd:documentation>
316
+ </xsd:annotation>
317
+ </xsd:element>
318
+ <xsd:group ref="LineIdentityGroup"/>
319
+ <xsd:group ref="EstimatedTimetableAlterationGroup">
320
+ <xsd:annotation>
321
+ <xsd:documentation>Gives the DATED VEHICLE JOURNEY
322
+ which the vehicle is running and if the journey is an alteration to the timetable indicates
323
+ the original journey and the nature of the difference.</xsd:documentation>
324
+ </xsd:annotation>
325
+ </xsd:group>
326
+ <xsd:group ref="JourneyPatternInfoGroup" minOccurs="0"/>
327
+ <xsd:group ref="JourneyEndNamesGroup"/>
328
+ <xsd:group ref="ServiceInfoGroup" minOccurs="0"/>
329
+ <xsd:group ref="JourneyInfoGroup" minOccurs="0"/>
330
+ <xsd:group ref="JourneyEndTimesGroup" minOccurs="0"/>
331
+ <xsd:group ref="DisruptionGroup"/>
332
+ <xsd:group ref="JourneyProgressGroup" minOccurs="0"/>
333
+ <xsd:group ref="TrainOperationalInfoGroup"/>
334
+ <xsd:sequence>
335
+ <xsd:element name="RecordedCalls" minOccurs="0">
336
+ <xsd:annotation>
337
+ <xsd:documentation>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)</xsd:documentation>
338
+ </xsd:annotation>
339
+ <xsd:complexType>
340
+ <xsd:sequence>
341
+ <xsd:element ref="RecordedCall" maxOccurs="unbounded"/>
342
+ </xsd:sequence>
343
+ </xsd:complexType>
344
+ </xsd:element>
345
+ <xsd:element name="EstimatedCalls" minOccurs="0">
346
+ <xsd:annotation>
347
+ <xsd:documentation>Complete sequence of stops along the route path, in calling order. Normally this is only the onwards stops from the vehicle's current position.</xsd:documentation>
348
+ </xsd:annotation>
349
+ <xsd:complexType>
350
+ <xsd:sequence>
351
+ <xsd:element ref="EstimatedCall" maxOccurs="unbounded"/>
352
+ </xsd:sequence>
353
+ </xsd:complexType>
354
+ </xsd:element>
355
+ <xsd:element name="IsCompleteStopSequence" type="xsd:boolean" default="false" minOccurs="0">
356
+ <xsd:annotation>
357
+ <xsd:documentation>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'.</xsd:documentation>
358
+ </xsd:annotation>
359
+ </xsd:element>
360
+ </xsd:sequence>
361
+ <xsd:element name="JourneyRelations" type="JourneyRelationsStructure" minOccurs="0">
362
+ <xsd:annotation>
363
+ <xsd:documentation>Relations of the journey with other journeys, e.g., in case a joining/splitting takes place or the journey substitutes for another one etc.</xsd:documentation>
364
+ </xsd:annotation>
365
+ </xsd:element>
366
+ <xsd:element ref="Extensions" minOccurs="0"/>
367
+ </xsd:sequence>
368
+ </xsd:complexType>
369
+ <!-- ======================================================================= -->
370
+ <xsd:element name="EstimatedCall" type="EstimatedCallStructure">
371
+ <xsd:annotation>
372
+ <xsd:documentation>Ordered sequence of SCHEDULED STOP POINTs called at by the VEHICLE JOURNEY. If IsCompleteStopSequence is false, may be just those stops that are altered.</xsd:documentation>
373
+ </xsd:annotation>
374
+ </xsd:element>
375
+ <xsd:element name="ExtraCall" type="xsd:boolean" default="false">
376
+ <xsd:annotation>
377
+ <xsd:documentation>This CALL is an addition to the respective journey in the production timetable or to the previously sent prediction. If omitted: CALL is planned.</xsd:documentation>
378
+ </xsd:annotation>
379
+ </xsd:element>
380
+ <xsd:simpleType name="CallCancellation">
381
+ <xsd:annotation>
382
+ <xsd:documentation>This CALL is a cancellation of a previously announced call.</xsd:documentation>
383
+ </xsd:annotation>
384
+ <xsd:restriction base="xsd:boolean"/>
385
+ </xsd:simpleType>
386
+ <!-- ======================================================================= -->
387
+ <xsd:complexType name="EstimatedCallStructure">
388
+ <xsd:annotation>
389
+ <xsd:documentation>Type for real-time info about a VEHICLE JOURNEY Stop.</xsd:documentation>
390
+ </xsd:annotation>
391
+ <xsd:sequence>
392
+ <xsd:group ref="StopPointInSequenceGroup"/>
393
+ <xsd:choice minOccurs="0">
394
+ <xsd:element ref="ExtraCall" minOccurs="0"/>
395
+ <xsd:element name="Cancellation" type="CallCancellation" default="false" minOccurs="0"/>
396
+ </xsd:choice>
397
+ <xsd:group ref="CallRealTimeInfoGroup"/>
398
+ <xsd:group ref="CallPropertyGroup"/>
399
+ <xsd:group ref="CallNoteGroup"/>
400
+ <xsd:group ref="DisruptionGroup"/>
401
+ <xsd:group ref="OnwardsCallGroup"/>
402
+ <xsd:element ref="Extensions" minOccurs="0"/>
403
+ </xsd:sequence>
404
+ </xsd:complexType>
405
+ <xsd:group name="CallRealTimeInfoGroup">
406
+ <xsd:annotation>
407
+ <xsd:documentation>Information relating to real-time properties of call.</xsd:documentation>
408
+ </xsd:annotation>
409
+ <xsd:sequence>
410
+ <xsd:element ref="PredictionInaccurate" minOccurs="0"/>
411
+ <xsd:element ref="PredictionInaccurateReason" minOccurs="0"/>
412
+ <xsd:element ref="Occupancy" minOccurs="0"/>
413
+ </xsd:sequence>
414
+ </xsd:group>
415
+ <!-- ======================================================================= -->
416
+ <xsd:element name="RecordedCall" type="RecordedCallStructure">
417
+ <xsd:annotation>
418
+ <xsd:documentation>Ordered sequence of SCHEDULED STOP POINTs called at by the VEHICLE JOURNEY. Only used if observed stop data is being recorded. (SIRI 2.0)</xsd:documentation>
419
+ </xsd:annotation>
420
+ </xsd:element>
421
+ <xsd:complexType name="RecordedCallStructure">
422
+ <xsd:annotation>
423
+ <xsd:documentation>Type for recroded Real-time info about a VEHICLE JOURNEY Stop.</xsd:documentation>
424
+ </xsd:annotation>
425
+ <xsd:sequence>
426
+ <xsd:group ref="StopPointInSequenceGroup"/>
427
+ <xsd:choice minOccurs="0">
428
+ <xsd:element ref="ExtraCall" minOccurs="0"/>
429
+ <xsd:element name="Cancellation" type="CallCancellation" default="false" minOccurs="0"/>
430
+ </xsd:choice>
431
+ <xsd:group ref="CallRealTimeInfoGroup"/>
432
+ <xsd:group ref="RecordedCallGroup"/>
433
+ <xsd:element ref="Extensions" minOccurs="0"/>
434
+ </xsd:sequence>
435
+ </xsd:complexType>
436
+ <xsd:group name="RecordedCallGroup">
437
+ <xsd:annotation>
438
+ <xsd:documentation>Information relating to recorded real-time properties of call.</xsd:documentation>
439
+ </xsd:annotation>
440
+ <xsd:sequence>
441
+ <xsd:group ref="CallPropertyGroup"/>
442
+ <xsd:group ref="CallNoteGroup"/>
443
+ <xsd:group ref="DisruptionGroup"/>
444
+ <xsd:element ref="AimedArrivalTime" minOccurs="0"/>
445
+ <xsd:element ref="ExpectedArrivalTime" minOccurs="0"/>
446
+ <xsd:element ref="ActualArrivalTime" minOccurs="0"/>
447
+ <xsd:group ref="MonitoredStopArrivalStatusGroup"/>
448
+ <!-- It should actually follow the MonitoredStopDepartureStatusGroup but because of an old mistake described below the elements have to be listed explicitly (in a slightly different order).
449
+ <xsd:group ref="MonitoredStopDepartureStatusGroup"/>-->
450
+ <xsd:element ref="AimedDepartureTime" minOccurs="0"/>
451
+ <xsd:element ref="ExpectedDepartureTime" minOccurs="0"/>
452
+ <xsd:element ref="DeparturePlatformName" minOccurs="0"/>
453
+ <xsd:element ref="ActualDepartureTime" minOccurs="0"/>
454
+ <xsd:element ref="DepartureStatus" minOccurs="0"/>
455
+ <xsd:element ref="DepartureCancellationReason" minOccurs="0"/>
456
+ <xsd:element ref="DepartureProximityText" minOccurs="0"/>
457
+ <!-- DeparturePlatformName should actually be inserted here, but by a mistake in an old version it has to be used between Expected- and ActualDepartureTime above
458
+ (which is confusing, given that this ordering is only valid in the RecordedCallStructure and nowhere else). Backward compatibility and non-determinism forbids us to correct the mistake.
459
+ <xsd:element ref="DeparturePlatformName" minOccurs="0"/>-->
460
+ <xsd:element ref="DepartureBoardingActivity" minOccurs="0"/>
461
+ <xsd:element name="DepartureStopAssignment" type="StopAssignmentStructure" minOccurs="0" maxOccurs="unbounded"/>
462
+ <xsd:element ref="DepartureFormationAssignment" minOccurs="0" maxOccurs="unbounded"/>
463
+ <xsd:element ref="DepartureOrientationRelativeToQuay" minOccurs="0" maxOccurs="unbounded"/>
464
+ <xsd:element ref="RecordedDepartureOccupancy" minOccurs="0" maxOccurs="unbounded"/>
465
+ <xsd:element ref="RecordedDepartureCapacities" minOccurs="0" maxOccurs="unbounded"/>
466
+ <xsd:element ref="DepartureOperatorRefs" minOccurs="0" maxOccurs="unbounded"/>
467
+ <xsd:group ref="HeadwayIntervalGroup"/>
468
+ <xsd:element ref="ActualHeadwayInterval" minOccurs="0"/>
469
+ </xsd:sequence>
470
+ </xsd:group>
471
+ <!-- ======================================================================= -->
472
+ </xsd:schema>