XML Schema "siri_monitoredVehicleJourney-v2.0.xsd"
Target Namespace:
http://www.siri.org.uk/siri
Version:
2.0
Defined Components:
elements (45 local), complexTypes (6), element groups (13)
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
C:\Users\Tony\eclipse_workspace\siri-20-java\xsd\siri_model\siri_monitoredVehicleJourney-v2.0.xsd; see XML source
Includes Schemas (1):
siri_journey-v2.0.xsd [src]
Included in Schemas (3):
siri_situationAffects-v2.0.xsd [src], siri_stopMonitoring_service.xsd [src], siri_vehicleMonitoring_service.xsd [src]
Annotation
SIRI MONITORED VEHICLE JOURNEY Model.
All Element Summary (local elements unified by type)
Bearing (type AbsoluteBearingType)
Bearing in compass degrees in which VEHICLE is heading.
Type:
AbsoluteBearingType
Content:
simple
Defined:
locally within ProgressDataGroup group; see XML source
ConfidenceLevel (type QualityIndexEnumeration)
Confidence QUALITY LEVEL of data.
Type:
QualityIndexEnumeration
Content:
simple
Defined:
locally within ProgressDataQualityGroup group; see XML source
DataSource (type xsd:string)
System originating real-time data.
Type:
xsd:string
Content:
simple
Defined:
locally within ProgressDataQualityGroup group; see XML source
Delay (type DurationType)
Delay of VEHICLE against schedule, to a precision in seconds.
Type:
DurationType
Content:
simple
Defined:
locally within ProgressDataGroup group; see XML source
Destination (defined in ServicePointsGroup group)
Destination of VEHICLE JOURNEY.
Type:
anonymous complexType
Content:
complex, 2 elements
Defined:
locally within ServicePointsGroup group; see XML source
Includes:
definitions of 2 elements
EarliestExpectedDepartureTime (type xsd:dateTime)
Type:
xsd:dateTime
Content:
simple
Defined:
locally at 2 locations
EngineOn (type xsd:boolean)
Whether the engine of the vehicle is on.
Type:
xsd:boolean
Content:
simple
Defined:
locally within ProgressDataGroup group; see XML source
ExpectedDeparturePredictionQuality (type PredictionQualityStructure)
Type:
PredictionQualityStructure
Content:
complex, 4 elements
Defined:
locally at 2 locations
InCongestion (in AffectedVehicle)
Type:
xsd:boolean
Content:
simple
Defined:
locally at 2 locations
InPanic (in AffectedVehicle)
Type:
xsd:boolean
Content:
simple
Defined:
locally at 2 locations
IsCompleteStopSequence (in EstimatedVehicleJourney)
Type:
xsd:boolean
Content:
simple
Defined:
locally at 2 locations
JourneyPartInfo (type JourneyPartInfoStructure)
Type:
JourneyPartInfoStructure
Content:
complex, 3 elements
Defined:
locally at 2 locations
JourneyPartRef (in JourneyPartInfo)
Refrence to a JOURNEY part.
Type:
xsd:normalizedString
Content:
simple
Defined:
locally within JourneyPartInfoStructure complexType; see XML source
JourneyParts (defined in TrainOperationalInfoGroup group)
JOURNEY PARTs making up JOURNEY +SIRIv2.0 e.
Type:
anonymous complexType
Content:
complex, 1 element
Defined:
locally within TrainOperationalInfoGroup group; see XML source
Includes:
definition of 1 element
LatestExpectedArrivalTime (in MonitoredCall)
Latest time at which a VEHICLE will arrive at stop.
Type:
xsd:dateTime
Content:
simple
Defined:
locally within MonitoredCallArrivalTimesGroup group; see XML source
LocationRecordedAtTime (type xsd:dateTime)
Time at which location was recorded.
Type:
xsd:dateTime
Content:
simple
Defined:
locally within ProgressDataGroup group; see XML source
Monitored (type xsd:boolean)
Type:
xsd:boolean
Content:
simple
Defined:
locally at 8 locations
MonitoredCall (type MonitoredCallStructure)
Monitored CALL at the current stop.
Type:
MonitoredCallStructure
Content:
complex, 47 elements
Defined:
locally within MonitoredCallingPatternGroup group; see XML source
MonitoringError (type xsd:NMTOKENS)
Condition indicating nature of real-time fault.
Type:
xsd:NMTOKENS
Content:
simple
Defined:
locally within JourneyProgressGroup group; see XML source
NumberOfBlockParts (in TrainBlockPart)
Total number of BLOCK parts making up the train of which this is part.
Type:
xsd:positiveInteger
Content:
simple
Defined:
locally within TrainBlockPartStructure complexType; see XML source
Occupancy (type OccupancyEnumeration)
Type:
OccupancyEnumeration
Content:
simple
Defined:
locally at 3 locations
OnwardCalls (type OnwardCallsStructure)
Information on CALLs at the intermediate stops beyond the current stop, up to and including the destination, in order of visits.
Type:
OnwardCallsStructure
Content:
complex, 1 element
Defined:
locally within MonitoredCallingPatternGroup group; see XML source
OperatorRef (type OperatorRefStructure)
Type:
OperatorRefStructure
Content:
simple
Defined:
locally at 12 locations
Origin (defined in ServicePointsGroup group)
Origin of the VEHICLE JOURNEY.
Type:
anonymous complexType
Content:
complex, 2 elements
Defined:
locally within ServicePointsGroup group; see XML source
Includes:
definitions of 2 elements
PlatformTraversal (in MonitoredCall)
For Rail, whether this is a platform traversal at speed, typically triggering an announcement to stand back from platform.
Type:
xsd:boolean
Content:
simple
Defined:
locally within CallRailGroup group; see XML source
PositionOfTrainBlockPart (in TrainBlockPart)
Description of position of Train BLOCK Part within Train to guide passengers where to find it.
Type:
NaturalLanguageStringStructure
Content:
simple, 1 attribute
Defined:
locally within TrainBlockPartStructure complexType; see XML source
PredictionInaccurate (type xsd:boolean)
Type:
xsd:boolean
Content:
simple
Defined:
locally at 3 locations
PresentationPriority (in Via defined in ServicePointsGroup group)
Relative priority for incliding via in displays. 1 Is high 3 is low.
Type:
xsd:integer
Content:
simple
Defined:
locally within Via element; see XML source
PreviousCall (in PreviousCalls)
Type:
PreviousCallStructure
Content:
complex, 12 elements
Defined:
locally within PreviousCallsStructure complexType; see XML source
PreviousCalls (type PreviousCallsStructure)
Information on stops called at previously, origin and all intermediate stops up to but not including the current stop, in order or visits.
Type:
PreviousCallsStructure
Content:
complex, 1 element
Defined:
locally within MonitoredCallingPatternGroup group; see XML source
ProgressRate (type ProgressRateEnumeration)
Rate of progress of VEHICLE.
Type:
ProgressRateEnumeration
Content:
simple
Defined:
locally within ProgressDataGroup group; see XML source
ProgressStatus (type NaturalLanguageStringStructure)
An arbitrary textual status description of the running of this VEHICLE JOURNEY.
Type:
NaturalLanguageStringStructure
Content:
simple, 1 attribute
Defined:
locally within ProgressDataGroup group; see XML source
ProvisionalExpectedDepartureTime (type xsd:dateTime)
Type:
xsd:dateTime
Content:
simple
Defined:
locally at 2 locations
ReversesAtStop (in MonitoredCall)
Whether VEHICLE will reverse at stop.
Type:
xsd:boolean
Content:
simple
Defined:
locally within CallRailGroup group; see XML source
SignalStatus (in MonitoredCall)
Status of signal clearance for TRAIN.
Type:
xsd:NMTOKEN
Content:
simple
Defined:
locally within CallRailGroup group; see XML source
TrainBlockPart (in AffectedVehicle)
Type:
TrainBlockPartStructure
Content:
complex, 3 elements
Defined:
locally at 2 locations
TrainNumberRef (type TrainNumberRefStructure)
Type:
TrainNumberRefStructure
Content:
simple
Defined:
locally at 3 locations
TrainNumbers (defined in TrainOperationalInfoGroup group)
TRAIN NUMBERs for journey.
Type:
anonymous complexType
Content:
complex, 1 element
Defined:
locally within TrainOperationalInfoGroup group; see XML source
Includes:
definition of 1 element
TrainPartRef (in TrainBlockPart)
Reference to a train BLOCK part.
Type:
TrainPartRefStructure
Content:
simple
Defined:
locally within TrainBlockPartStructure complexType; see XML source
VehicleLocation (type LocationStructure)
Current geospatial location of VEHICLE.
Type:
LocationStructure
Content:
complex, 2 attributes, 4 elements
Defined:
locally within ProgressDataGroup group; see XML source
VehicleLocationAtStop (type LocationStructure)
Exact location that VEHICLE will take up / or has taken at STOP POINT.
Type:
LocationStructure
Content:
complex, 2 attributes, 4 elements
Defined:
locally within CallRealtimeGroup group; see XML source
VehicleStatus (type VehicleStatusEnumeration)
An classification of the progress state of running of this VEHICLE JOURNEY.
Type:
VehicleStatusEnumeration
Content:
simple
Defined:
locally within ProgressDataGroup group; see XML source
Velocity (type VelocityType)
Velocity of VEHICLE.
Type:
VelocityType
Content:
simple
Defined:
locally within ProgressDataGroup group; see XML source
Via (defined in ServicePointsGroup group)
VIA points for VEHICLE JOURNEY
Type:
anonymous complexType
Content:
complex, 3 elements
Defined:
locally within ServicePointsGroup group; see XML source
Includes:
definitions of 3 elements
Complex Type Summary
JourneyPartInfoStructure
Type for a refernces to JOURNEY PARTs.
Content:
complex, 3 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
at 1 location
MonitoredCallStructure
Type for Current CALL at stop.
Content:
complex, 47 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
at 1 location
MonitoredVehicleJourneyStructure
Type for Monitored VEHICLE JOURNEY.
Content:
complex, 66 elements
Defined:
globally; see XML source
Used:
never
PreviousCallsStructure
Type for Ordered list of CALLs at previous stop.
Content:
complex, 1 element
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
at 1 location
PreviousCallStructure
Type for CALL at previous stop.
Content:
complex, 12 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
at 1 location
TrainBlockPartStructure
Type for BLOCK part elements of VEHICLE JOURNEY.
Content:
complex, 3 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
at 1 location
Element Group Summary
CallRailGroup
Elements describing theProperties specific to a rail CALLs.
Content:
3 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
at 1 location
CallRealtimeGroup
Elements describing the Real-time CALL properties.
Content:
2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
at 2 locations
JourneyProgressGroup
Elements describing the real-time progress of a monitored VEHICLE JOURNEY.
Content:
17 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
at 1 location
MonitoredCallArrivalTimesGroup
Arrival times for CALL.
Content:
4 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
at 1 location
MonitoredCallDepartureTimesGroup
Departure times for CALL.
Content:
6 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
at 1 location
MonitoredCallGroup
Elements for a monitored CALL.
Content:
42 elements
Defined:
globally; see XML source
Used:
at 1 location
MonitoredCallingPatternGroup
The service pattern of a monitored VEHICLE JOURNEY.
Content:
4 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
at 1 location
ProgressDataGroup
Elements describing the real-time progress of a journey.
Content:
10 elements
Defined:
globally; see XML source
Includes:
definitions of 10 elements
Used:
at 1 location
ProgressDataQualityGroup
Elements describing the qua;ity of real-time progress data of a journey.
Content:
5 elements
Defined:
globally; see XML source
Includes:
definitions of 5 elements
Used:
at 1 location
ServicePointsGroup
Elements describing the main places bewteen which a VEHICLE JOURNEY runs.
Content:
3 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
never
StopArrivalGroup
Elements describing the the arrival of a VEHICLE at a stop.
Content:
10 elements
Defined:
globally; see XML source
Used:
at 1 location
StopDepartureGroup
Elements describing the the departure of a VEHICLE from a stop.
Content:
14 elements
Defined:
globally; see XML source
Used:
at 1 location
TrainOperationalInfoGroup
Operational information about the monitored VEHICLE JOURNEY.
Content:
10 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
at 1 location
XML Source
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" id="siri_journey" targetNamespace="http://www.siri.org.uk/siri" version="2.0" xmlns="http://www.siri.org.uk/siri" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:annotation>
<xsd:appinfo>
<Metadata xmlns="http://www.govtalk.gov.uk/CM/gms-xs">
<Aggregation>main schema</Aggregation>
<Audience>e-service developers</Audience>
<Contributor>Cen TC278 WG3 SG7 Team</Contributor>
<Coverage>Europe</Coverage>
<Creator>
Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk
</Creator>
<Date>
<Created>2004-03-05</Created>
</Date>
<Date>
<Modified>2004-10-06</Modified>
</Date>
<Date>
<Modified>2005-05-11</Modified>
</Date>
<Date>
<Modified>2005-11-15</Modified>
</Date>
<Date>
<Modified>2007-03-29</Modified>
</Date>
<Date>
<Modified>2008-11-13</Modified>
Correct Cardinalities on SIRI DESTINATION REF Structure
</Date>
<Date>
<Modified>2011-04-18</Modified>
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
</Date>
<Date>
<Modified>2012-03-22</Modified>
SIRI 2.0
[VDV] Add EarliestExpectedArrivalTimeForVehicle to Arrival Times Group
[VDV] Add ProvisionalExpectedDepartureTime to Departure Times Group
[VDV] Add LatestExpectedArrivalTimeForVehicle to Departure Times Group

[Fr] Add FirstOrLastJourney to JourneyTimesGroup : SIRI-SM and SIRI-VM
Add JOURNEY PARTs to Vehicle INFO TODO
[VDV] Add Public and Contact Details to JourneyInfo : SIRI-PT, SIRI-ET, SIRI-SM. SIRI-VM
[VDV] at DirectionAtOrigin name to JourneyInfo SIRI-PT, SIRI-ET, SIRI-SM. SIRI-VM

[MTA] Add ArrivalProximityText to Arrival Times on MonitoredCall and OnwardsCall : SIRI-SM and SIRI-VM
[MTA] Add ArrivalProximityText to Departure Times on MonitoredCall and OnwardsCall : SIRI-SM and SIRI-VM

[FR] Add AimedLatestPassengerAccessTime to TargetedCall : SIRI-ST
[FR] Add AimedLatestPassengerAccessTime to MonitoredCall and OnwardsCall : SIRI-SM and SIRI-VM
[FR] Add ExpectedLatestPassengerAccessTime to MonitoredCall and OnwardsCall : SIRI-SM and SIRI-VM

[VDV] Add ViaPriority to ViaNames using a new ViaNameStructure SIRI-PT, SIRI-ET, SIRI-SM. SIRI-VM
[VDV] Add Velocity to MonitoredVehicleJourney SIRI-SM and SIRI-VM
[UK] add engineOn to vehicle progress group
</Date>
<Date>
<Modified>2012-04-27</Modified>
SIRI 2.0
[MTA] Add DIstanceFromSTop and NumberOfStops away to MonitoredCall and OnwardsCall : SIRI-SM and SIRI-ET
</Date>
<Date>
<Modified>2012-04-27</Modified>
SIRI 2.0
[SE] Add Vehicle Status
</Date>
<Description>
<p>
SIRI is a European CEN technical standard for the exchange of real-time information .
</p>
<p>This subschema defines common journey elements.</p>
</Description>
<Format>
<MediaType>text/xml</MediaType>
<Syntax>http://www.w3.org/2001/XMLSchema</Syntax>
<Description>XML schema, W3C Recommendation 2001</Description>
</Format>
<Identifier>
{http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_monitoredVehicleJourney.xsd
</Identifier>
<Language>[ISO 639-2/B] ENG</Language>
<Publisher>Kizoom, 109-123 Clifton Street, London EC4A 4LD</Publisher>
<Relation>
<Requires>
http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types-v2.0.xsd
</Requires>
</Relation>
<Rights>
Unclassified
<Copyright>CEN, VDV, RTIG 2004-2012</Copyright>
</Rights>
<Source>
<ul>
<li>
Derived from the VDV, RTIG CML and Trident standards.
</li>
</ul>
</Source>
<Status>Version 2.0 Draft</Status>
<Subject>
<Category>
Arts, recreation and travel, Tourism, Travel (tourism), Transport,
Air transport, Airports,
Ports and maritime transport, Ferries (marine),
Public transport, Bus services, Coach services, Bus stops and stations,
Rail transport, Railway stations and track, Train services, Underground trains,
Business and industry, Transport, Air transport, Ports and maritime transport, Public transport,
Rail transport, Roads and road transport
</Category>
<Project>CEN TC278 WG3 SG7</Project>
</Subject>
<Title>
SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of common Journey elements
</Title>
<Type>Standard</Type>
</Metadata>
</xsd:appinfo>
<xsd:documentation>SIRI MONITORED VEHICLE JOURNEY Model.</xsd:documentation>
</xsd:annotation>
<!-- ======================================================================= -->
<xsd:include schemaLocation="siri_journey-v2.0.xsd"/>
<!-- ==== MONITORED VEHICLEJOURNEY ================================================================== -->
<xsd:complexType name="MonitoredVehicleJourneyStructure">
<xsd:annotation>
<xsd:documentation>Type for Monitored VEHICLE JOURNEY.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="MonitoredJourneyIdentityGroup"/>
<xsd:group ref="JourneyPatternInfoGroup"/>
<xsd:group ref="VehicleJourneyInfoGroup"/>
<xsd:group ref="DisruptionGroup"/>
<xsd:group ref="JourneyProgressGroup"/>
<xsd:group ref="TrainOperationalInfoGroup"/>
<xsd:group ref="MonitoredCallingPatternGroup"/>
</xsd:sequence>
</xsd:complexType>
<xsd:group name="JourneyProgressGroup">
<xsd:annotation>
<xsd:documentation>
Elements describing the real-time progress of a monitored VEHICLE JOURNEY.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="Monitored" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether there is real-time information available for journey; if not present, not known.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="MonitoringError" type="xsd:NMTOKENS">
<xsd:annotation>
<xsd:documentation>
Condition indicating nature of real-time fault. Present if VEHICLE JOURNEY is normally monitored but temporarily cannot be Monitored for a known reason.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group ref="ProgressDataQualityGroup"/>
<xsd:group ref="ProgressDataGroup"/>
</xsd:sequence>
</xsd:group>
<xsd:group name="ProgressDataQualityGroup">
<xsd:annotation>
<xsd:documentation>
Elements describing the qua;ity of real-time progress data of a journey.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="InCongestion" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether the VEHICLE iis in traffic congestion. If not, present, not known.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="false" minOccurs="0" name="InPanic" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether the panic alarm on the VEHICLE is activated. This may lead to indeterminate predictions. If absent, default is 'false'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="PredictionInaccurate" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether the prediction should be judged as inaccurate.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="DataSource" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
System originating real-time data. Can be used to make judgements of relative quality and accuracy compared to other feeds.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="reliable" minOccurs="0" name="ConfidenceLevel" type="QualityIndexEnumeration">
<xsd:annotation>
<xsd:documentation>
Confidence QUALITY LEVEL of data. Default is 'reliable'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:group name="ProgressDataGroup">
<xsd:annotation>
<xsd:documentation>
Elements describing the real-time progress of a journey.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="VehicleLocation" type="LocationStructure">
<xsd:annotation>
<xsd:documentation>
Current geospatial location of VEHICLE. Measured to front of vehicle.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="LocationRecordedAtTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
Time at which location was recorded. If not present assume that the recorded at time on the containing delivery.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="Bearing" type="AbsoluteBearingType">
<xsd:annotation>
<xsd:documentation>
Bearing in compass degrees in which VEHICLE is heading.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="ProgressRate" type="ProgressRateEnumeration">
<xsd:annotation>
<xsd:documentation>Rate of progress of VEHICLE. Default is 'normal'</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="Velocity" type="VelocityType">
<xsd:annotation>
<xsd:documentation>
Velocity of VEHICLE. EIther actual speed or average speed may be used. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="true" minOccurs="0" name="EngineOn" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether the engine of the vehicle is on. Default is 'true' (+SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="Occupancy" type="OccupancyEnumeration">
<xsd:annotation>
<xsd:documentation>How full the VEHICLE is. If omitted, not known.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="Delay" type="DurationType">
<xsd:annotation>
<xsd:documentation>
Delay of VEHICLE against schedule, to a precision in seconds. Early times are shown as negative values.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="ProgressStatus" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
An arbitrary textual status description of the running of this VEHICLE JOURNEY. (Unbounded 0:* since SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="VehicleStatus" type="VehicleStatusEnumeration">
<xsd:annotation>
<xsd:documentation>
An classification of the progress state of running of this VEHICLE JOURNEY. +SIRI 2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:group name="ServicePointsGroup">
<xsd:annotation>
<xsd:documentation>
Elements describing the main places bewteen which a VEHICLE JOURNEY runs.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="Origin">
<xsd:annotation>
<xsd:documentation>Origin of the VEHICLE JOURNEY.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element minOccurs="0" ref="OriginRef"/>
<xsd:element minOccurs="0" ref="OriginName"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="Via">
<xsd:annotation>
<xsd:documentation>VIA points for VEHICLE JOURNEY</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element minOccurs="0" ref="ViaRef"/>
<xsd:element minOccurs="0" ref="ViaName"/>
<xsd:element minOccurs="0" name="PresentationPriority" type="xsd:integer">
<xsd:annotation>
<xsd:documentation>
Relative priority for incliding via in displays. 1 Is high 3 is low. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element minOccurs="0" name="Destination">
<xsd:annotation>
<xsd:documentation>Destination of VEHICLE JOURNEY.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element minOccurs="0" ref="DestinationRef"/>
<xsd:element minOccurs="0" ref="DestinationName"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:group name="MonitoredCallingPatternGroup">
<xsd:annotation>
<xsd:documentation>
The service pattern of a monitored VEHICLE JOURNEY. CALLs should be assigned to one of three groups according to the vehicle's current position.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="PreviousCalls" type="PreviousCallsStructure">
<xsd:annotation>
<xsd:documentation>
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.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="MonitoredCall" type="MonitoredCallStructure">
<xsd:annotation>
<xsd:documentation>
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.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="OnwardCalls" type="OnwardCallsStructure">
<xsd:annotation>
<xsd:documentation>
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.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="false" minOccurs="0" name="IsCompleteStopSequence" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
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'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<!-- ==== LINE ROUTE and destination elements======================================================== -->
<xsd:complexType name="JourneyPartInfoStructure">
<xsd:annotation>
<xsd:documentation>
Type for a refernces to JOURNEY PARTs. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="JourneyPartRef" type="xsd:normalizedString">
<xsd:annotation>
<xsd:documentation>Refrence to a JOURNEY part. +SIRI v2.0</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="TrainNumberRef" type="TrainNumberRefStructure">
<xsd:annotation>
<xsd:documentation>Train Number for JOURNEY PART +SIRI v2.0</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="OperatorRef" type="OperatorRefStructure">
<xsd:annotation>
<xsd:documentation>Operator of JOURNEY PART. +SIRI v2.0</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<!-- ======================================================================= -->
<xsd:complexType name="TrainBlockPartStructure">
<xsd:annotation>
<xsd:documentation>Type for BLOCK part elements of VEHICLE JOURNEY.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="NumberOfBlockParts" type="xsd:positiveInteger">
<xsd:annotation>
<xsd:documentation>
Total number of BLOCK parts making up the train of which this is part.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="TrainPartRef" type="TrainPartRefStructure">
<xsd:annotation>
<xsd:documentation>Reference to a train BLOCK part.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="PositionOfTrainBlockPart" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
Description of position of Train BLOCK Part within Train to guide passengers where to find it. E.g. 'Front four coaches'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:group name="TrainOperationalInfoGroup">
<xsd:annotation>
<xsd:documentation>
Operational information about the monitored VEHICLE JOURNEY.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="TrainBlockPart" type="TrainBlockPartStructure">
<xsd:annotation>
<xsd:documentation>
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.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group ref="OperationalInfoGroup"/>
<xsd:element minOccurs="0" name="TrainNumbers">
<xsd:annotation>
<xsd:documentation>TRAIN NUMBERs for journey. +SIRI v2.0</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="TrainNumberRef" type="TrainNumberRefStructure">
<xsd:annotation>
<xsd:documentation>
TRAIN NUMBER assigned to VEHICLE JOURNEY. +SIRI 2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element minOccurs="0" name="JourneyParts">
<xsd:annotation>
<xsd:documentation>JOURNEY PARTs making up JOURNEY +SIRIv2.0 e.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="JourneyPartInfo" type="JourneyPartInfoStructure">
<xsd:annotation>
<xsd:documentation>Information about Parts of JOURNEY +SIRI v2.0</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:group>
<!-- ======================================================================= -->
<!-- ===== PREVIOUS CALL============================================= -->
<xsd:complexType name="PreviousCallsStructure">
<xsd:annotation>
<xsd:documentation>Type for Ordered list of CALLs at previous stop.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="PreviousCall" type="PreviousCallStructure"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="PreviousCallStructure">
<xsd:annotation>
<xsd:documentation>Type for CALL at previous stop.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractMonitoredCallStructure">
<xsd:sequence>
<xsd:element minOccurs="0" ref="VehicleAtStop"/>
<xsd:group ref="VehicleArrivalTimesGroup"/>
<xsd:group ref="VehicleDepartureTimesGroup"/>
<xsd:element minOccurs="0" ref="Extensions"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!-- ===== CALL =============================================================== -->
<xsd:complexType name="MonitoredCallStructure">
<xsd:annotation>
<xsd:documentation>Type for Current CALL at stop.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractMonitoredCallStructure">
<xsd:sequence>
<xsd:group ref="MonitoredCallGroup"/>
<xsd:element minOccurs="0" ref="Extensions"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:group name="MonitoredCallGroup">
<xsd:annotation>
<xsd:documentation>Elements for a monitored CALL.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="CallRealtimeGroup"/>
<xsd:group ref="CallRailGroup"/>
<xsd:group ref="CallPropertyGroup"/>
<xsd:group ref="CallNoteGroup"/>
<xsd:group ref="DisruptionGroup"/>
<xsd:group ref="StopArrivalGroup"/>
<xsd:group ref="StopDepartureGroup"/>
<xsd:group ref="HeadwayIntervalGroup"/>
<xsd:group ref="StopProximityGroup"/>
</xsd:sequence>
</xsd:group>
<xsd:group name="CallRealtimeGroup">
<xsd:annotation>
<xsd:documentation>
Elements describing the Real-time CALL properties.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" ref="VehicleAtStop"/>
<xsd:element minOccurs="0" name="VehicleLocationAtStop" type="LocationStructure">
<xsd:annotation>
<xsd:documentation>
Exact location that VEHICLE will take up / or has taken at STOP POINT.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:group name="CallRailGroup">
<xsd:annotation>
<xsd:documentation>
Elements describing theProperties specific to a rail CALLs.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element default="false" minOccurs="0" name="ReversesAtStop" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether VEHICLE will reverse at stop. Default is 'false'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="false" minOccurs="0" name="PlatformTraversal" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
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.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="SignalStatus" type="xsd:NMTOKEN">
<xsd:annotation>
<xsd:documentation>
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.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:group name="StopArrivalGroup">
<xsd:annotation>
<xsd:documentation>
Elements describing the the arrival of a VEHICLE at a stop.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="MonitoredCallArrivalTimesGroup"/>
</xsd:sequence>
</xsd:group>
<xsd:annotation>
<xsd:documentation>Arrival times for CALL.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="VehicleArrivalTimesGroup"/>
<xsd:element minOccurs="0" name="LatestExpectedArrivalTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
Latest time at which a VEHICLE will arrive at stop. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:group name="StopDepartureGroup">
<xsd:annotation>
<xsd:documentation>
Elements describing the the departure of a VEHICLE from a stop.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="MonitoredCallDepartureTimesGroup"/>
<xsd:group ref="PassengerDepartureTimesGroup"/>
</xsd:sequence>
</xsd:group>
<xsd:annotation>
<xsd:documentation>Departure times for CALL.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="VehicleDepartureTimesGroup"/>
<xsd:element minOccurs="0" name="ProvisionalExpectedDepartureTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
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.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="EarliestExpectedDepartureTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
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
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="ExpectedDeparturePredictionQuality" type="PredictionQualityStructure">
<xsd:annotation>
<xsd:documentation>
Prediction quality, either as approcimate level, or more quantitatyive percentile range of predictions will fall within a given range of times. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<!-- ==== Times at CALL======================================================= -->
</xsd:schema>
This XML schema documentation has been generated with DocFlex/XML 1.9.5 using DocFlex/XML XSDDoc 2.8.1 template set.
DocFlex/XML is a tool for programming and running highly sophisticated documentation and reports generators by the data obtained from any kind of XML files. The actual doc-generators are implemented in the form of special templates that are designed visually using a high-quality Template Designer GUI basing on the XML schema (or DTD) files describing the data source XML.
DocFlex/XML XSDDoc is a commercial template application of DocFlex/XML that implements a high-quality XML Schema documentation generator with simultaneous support of framed multi-file HTML, single-file HTML and RTF output formats. (More formats are planned in the future).
A commercial license for "DocFlex/XML XSDDoc" will allow you:
  • To configure the generated documentation so much as you want. Thanks to our template technology, it was possible to support > 400 template parameters, which work the same as "options" of ordinary doc-generators. The parameters are organized in nested groups, which form a parameter tree. Most of them have their default values calculated dynamically from a few primary parameters. So, you'll never need to specify all of them. That will give you swift and effective control over the generated content!
  • To use certain features disabled in the free mode (such as the full documenting of substitution groups).
  • To select only the initial, imported, included, redefined XML schemas to be documented or only those directly specified by name.
  • To include only XML schema components specified by name.
  • To document local element components both globally and locally (similar to attributes).
  • To allow/suppress unification of local elements by type.
  • To enable/disable reproducing of namespace prefixes.
  • To use PlainDoc.tpl main template to generate all the XML schema documentation in a signle-file form as both HTML and incredible quality RTF output.
  • To format your annotations with XHTML tags and reproduce that formatting both in HTML and RTF output.
  • To insert images in your annotations using XHTML <img> tags (supported both in HTML and RTF output).
  • To remove this very advertisement text!
Once having only such a license, you will be able to run the fully-featured XML schema documentation generator both with DocFlex/XML (Full Edition) and with DocFlex/XML RE, which is a reduced free edition containing only the template interpretor / output generator. No other licenses will be required!
But this is not all. In addition to it, a commercial license for "DocFlex/XML SDK" will allow you to modify the XSDDoc templates themselves as much as you want. You will be able to achieve whatever was impossible to do with the template parameters only. And, of course, you could develop any template applications by your own!
Please note that by purchasing a license for this software, you not only acquire a useful tool, you will also make an important investment in its future development, the results of which you could enjoy later by yourself. Every single your purchase matters and makes a difference for us!
To purchase a license, please follow this link: http://www.filigris.com/shop/