XML Schema "siri_estimatedVehicleJourney-v2.0.xsd"
Target Namespace:
http://www.siri.org.uk/siri
Version:
2.0
Defined Components:
elements (4 global + 31 local), complexTypes (6), element groups (5)
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
C:\Users\Tony\eclipse_workspace\siri-20-java\xsd\siri_model\siri_estimatedVehicleJourney-v2.0.xsd; see XML source
Includes Schemas (1):
siri_journey-v2.0.xsd [src]
Included in Schemas (1):
siri_estimatedTimetable_service.xsd [src]
Annotation
SIRI-ET Estimated Timetable Service.
All Element Summary (local elements unified by type)
AimedArrivalTime (type xsd:dateTime)
Type:
xsd:dateTime
Content:
simple
Defined:
locally at 3 locations
AimedDepartureTime (type xsd:dateTime)
Type:
xsd:dateTime
Content:
simple
Defined:
locally at 2 locations
Cancellation (type xsd:boolean)
Type:
xsd:boolean
Content:
simple
Defined:
locally at 4 locations
ConnectionMonitoring (in EstimatedServiceJourneyInterchange)
Whether connection monitoring is active or not for this connection +SIRI v2.0
Type:
xsd:boolean
Content:
simple
Defined:
locally within EstimatedServiceJourneyInterchangeStructure complexType; see XML source
DatedVehicleJourneyIndirectRef (in EstimatedVehicleJourney)
If no VEHICLE JOURNEY reference is available, identify it by origin and destination and the scheduled times at these stops.
Type:
DatedVehicleJourneyIndirectRefStructure
Content:
complex, 4 elements
Defined:
locally within EstimatedTimetableAlterationGroup group; see XML source
DatedVehicleJourneyRef (type DatedVehicleJourneyRefStructure)
Type:
DatedVehicleJourneyRefStructure
Content:
simple
Defined:
locally at 2 locations
DestinationRef (in DatedVehicleJourneyIndirectRef)
The destination is used to help identify the VEHICLE JOURNEY.
Type:
StopPointRefStructure
Content:
simple
Defined:
locally within DatedVehicleJourneyIndirectRefStructure complexType; see XML source
DistributorJourneyRef (in EstimatedServiceJourneyInterchange)
Reference to a connecting distributor VEHICLE JOURNEY.
Type:
ConnectingJourneyRefStructure
Content:
complex, 3 elements
Defined:
locally within EstimatedServiceJourneyInterchangeStructure complexType; see XML source
DriverHasAcknowledgeWIllWait (in WillWait)
Whether an acknowledgement has been received that the driver will wait.
Type:
xsd:boolean
Content:
simple
Defined:
locally within WillWaitStructure complexType; see XML source
EstimatedCall
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:
EstimatedCallStructure
Content:
complex, 44 elements
Defined:
globally; see XML source
Used:
at 1 location
EstimatedCalls (in EstimatedVehicleJourney)
Estimated call tmes for journey
Type:
anonymous complexType
Content:
complex, 1 element
Defined:
locally within EstimatedVehicleJourneyStructure complexType; see XML source
Includes:
definition of 1 element
EstimatedServiceJourneyInterchange
A VEHICLE JOURNEY taking place on a particular date that will be managed by an AVMs.
Type:
EstimatedServiceJourneyInterchangeStructure
Content:
complex, 7 elements
Defined:
globally; see XML source
Used:
never
EstimatedVehicleJourney
A VEHICLE JOURNEY taking place on a particular date that will be managed by an AVMs.
Type:
EstimatedVehicleJourneyStructure
Content:
complex, 52 elements
Defined:
globally; see XML source
Used:
never
EstimatedVehicleJourneyCode (in EstimatedVehicleJourney)
If this is the first message about an extra unplanned VEHICLE JOURNEY, a new and unique code must be given for it.
Type:
EstimatedVehicleJourneyCodeType
Content:
simple
Defined:
locally within EstimatedTimetableAlterationGroup group; see XML source
ExpectedDepartureTimeOfDistributor (in EstimatedServiceJourneyInterchange)
Time at which distributor VEHICLE is expected to depart.
Type:
xsd:dateTime
Content:
simple
Defined:
locally within EstimatedServiceJourneyInterchangeStructure complexType; see XML source
ExtraCall (type xsd:boolean)
Type:
xsd:boolean
Content:
simple
Defined:
locally at 2 locations
ExtraJourney (type xsd:boolean)
Type:
xsd:boolean
Content:
simple
Defined:
locally at 2 locations
FeederJourneyRef (in EstimatedServiceJourneyInterchange)
Reference to a connecting distributor VEHICLE JOURNEY.
Type:
ConnectingJourneyRefStructure
Content:
complex, 3 elements
Defined:
locally within EstimatedServiceJourneyInterchangeStructure complexType; see XML source
HeadwayService (type xsd:boolean)
Type:
xsd:boolean
Content:
simple
Defined:
locally at 4 locations
IsCompleteStopSequence (in EstimatedVehicleJourney)
Type:
xsd:boolean
Content:
simple
Defined:
locally at 2 locations
Monitored (type xsd:boolean)
Type:
xsd:boolean
Content:
simple
Defined:
locally at 8 locations
Occupancy (type OccupancyEnumeration)
Type:
OccupancyEnumeration
Content:
simple
Defined:
locally at 3 locations
OriginRef (in DatedVehicleJourneyIndirectRef)
The origin is used to help identify the VEHICLE JOURNEY.
Type:
StopPointRefStructure
Content:
simple
Defined:
locally within DatedVehicleJourneyIndirectRefStructure complexType; see XML source
PredictionInaccurate (type xsd:boolean)
Type:
xsd:boolean
Content:
simple
Defined:
locally at 3 locations
RecordedAtTime (type xsd:dateTime)
Type:
xsd:dateTime
Content:
simple
Defined:
locally at 2 locations
RecordedCall
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:
RecordedCallStructure
Content:
complex, 20 elements
Defined:
globally; see XML source
Used:
at 1 location
RecordedCalls (in EstimatedVehicleJourney)
Observed call tmes for that art of teh journey that has already been completed. (+ SIRI 2..0)
Type:
anonymous complexType
Content:
complex, 1 element
Defined:
locally within EstimatedVehicleJourneyStructure complexType; see XML source
Includes:
definition of 1 element
WaitUntilTime (in WillWait)
Time up until which the distributor will wait.
Type:
xsd:dateTime
Content:
simple
Defined:
locally within WillWaitStructure complexType; see XML source
WillNotWait (in EstimatedServiceJourneyInterchange)
Distributor will not wait (i.e. connection broken) SIRI w.0
Type:
EmptyType
Content:
simple
Defined:
locally within EstimatedServiceJourneyInterchangeStructure complexType; see XML source
WillWait (in EstimatedServiceJourneyInterchange)
Nature of wait that distributer will make.
Type:
WillWaitStructure
Content:
complex, 2 elements
Defined:
locally within EstimatedServiceJourneyInterchangeStructure complexType; see XML source
Complex Type Summary
DatedVehicleJourneyIndirectRefStructure
Type for Origin and Destination stop of a VEHICLE JOURNEY.
Content:
complex, 4 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
at 1 location
EstimatedCallStructure
Type for Rea-ltime info about a VEHICLE JOURNEY Stop.
Content:
complex, 44 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
at 1 location
EstimatedServiceJourneyInterchangeStructure
Type for Estimated SERVICE JOURNEY INTERCHANGE.
Content:
complex, 7 elements
Defined:
globally; see XML source
Includes:
definitions of 7 elements
Used:
at 1 location
EstimatedVehicleJourneyStructure
Type for Real-time info about a VEHICLE JOURNEY.
Content:
complex, 52 elements
Defined:
globally; see XML source
Includes:
definitions of 5 elements
Used:
at 1 location
RecordedCallStructure
Type for recroded Real-time info about a VEHICLE JOURNEY Stop.
Content:
complex, 20 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
at 1 location
WillWaitStructure
Type for Will Wait details
Content:
complex, 2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
at 1 location
Element Group Summary
CallRealTimeInfoGroup
Information relating to real-time properties of call.
Content:
2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
at 2 locations
EstimatedJourneyInfoGroup
General properties of the journey.
Content:
2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
at 1 location
EstimatedRealtimeInfoGroup
Real-time properties of the journey.
Content:
3 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
at 1 location
EstimatedTimetableAlterationGroup
If the journey is an alteration to a timetable, indicates the original journey and the nature of the difference.
Content:
5 elements
Defined:
globally; see XML source
Includes:
definitions of 5 elements
Used:
at 1 location
RecordedCallGroup
Information relating to recorded real-time properties of call.
Content:
11 elements
Defined:
globally; see XML source
Includes:
definitions of 11 elements
Used:
at 1 location
XML Source
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" id="siri_estimatedVehicleJourney" 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>
<Contributor>Werner Kohl MDV</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>2003-02-10</Created>
</Date>
<Date>
<Modified>2004-10-31</Modified>
</Date>
<Date>
<Modified>2005-02-14</Modified>
</Date>
<Date>
<Modified>2005-02-20</Modified>
</Date>
<Date>
<Modified>2005-05-11</Modified>
</Date>
<Date>
<Modified>2007-04-17</Modified>
Name Space changes
</Date>
<Date>
<Modified>2008-03-26</Modified>
Add wrapper tag for Line DIRECTION to help binding to Axis
</Date>
<Date>
<Modified>2008-11-17</Modified>
Revise to support substitution groups
</Date>
<Date>
<Modified>2011-01-19</Modified>
Drop use of As Flat Groups for EstimatedCalls
</Date>
<Date>
<Modified>2012-03-23</Modified>
+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
</Date>
<Description>
<p>
SIRI is a European CEN standard for the exchange of Public Transport real-time information.
</p>
<p>
This sub-schema describes the Estimated Timetable Service.
</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_estimatedVehicleJourney.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_model/siri_journey-v2.0.xsd
</Requires>
</Relation>
<Rights>
Unclassified
<Copyright>CEN, VDV, RTIG 2004-2012</Copyright>
</Rights>
<Source>
<ul>
<li>
Derived from the VDV, RTIG XML 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-ET XML schema. Service Interface for Real-time Information. Estimated Timetable Service.
</Title>
<Type>Standard</Type>
</Metadata>
</xsd:appinfo>
<xsd:documentation>SIRI-ET Estimated Timetable Service.</xsd:documentation>
</xsd:annotation>
<!-- ==== Dependencies=========================================-->
<xsd:include schemaLocation="siri_journey-v2.0.xsd"/>
<!-- ======================================================================= -->
<xsd:annotation>
<xsd:documentation>
A VEHICLE JOURNEY taking place on a particular date that will be managed by an AVMs.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
If the journey is an alteration to a timetable, indicates the original journey and the nature of the difference.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:choice>
<xsd:element name="DatedVehicleJourneyRef" type="DatedVehicleJourneyRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to a dated VEHICLE JOURNEY. This will be 'framed' ie be with the data context of the ESTIMATED Timetable.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
If no VEHICLE JOURNEY reference is available, identify it by origin and destination and the scheduled times at these stops.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
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'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
<xsd:choice>
<xsd:element default="false" minOccurs="0" name="ExtraJourney" type="xsd:boolean">
<xsd:annotation>
<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>
</xsd:annotation>
</xsd:element>
<xsd:element default="false" minOccurs="0" name="Cancellation" type="xsd:boolean">
<xsd:annotation>
<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>
</xsd:annotation>
</xsd:element>
</xsd:choice>
</xsd:sequence>
</xsd:group>
<xsd:group name="EstimatedJourneyInfoGroup">
<xsd:annotation>
<xsd:documentation>General properties of the journey.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="HeadwayService" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
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.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="FirstOrLastJourney"/>
</xsd:sequence>
</xsd:group>
<xsd:group name="EstimatedRealtimeInfoGroup">
<xsd:annotation>
<xsd:documentation>Real-time properties of the journey.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="Monitored" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
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.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="false" minOccurs="0" name="PredictionInaccurate" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether the prediction for the journey is considered to be of a useful accuracy or not. Default is 'false'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="Occupancy" type="OccupancyEnumeration">
<xsd:annotation>
<xsd:documentation>
How full the bus is. If omitted: Passenger load is unknown.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:annotation>
<xsd:documentation>
Type for Origin and Destination stop of a VEHICLE JOURNEY.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="OriginRef" type="StopPointRefStructure">
<xsd:annotation>
<xsd:documentation>
The origin is used to help identify the VEHICLE JOURNEY.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="AimedDepartureTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>Departure time from origin SCHEDULED STOP POINT.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="DestinationRef" type="StopPointRefStructure">
<xsd:annotation>
<xsd:documentation>
The destination is used to help identify the VEHICLE JOURNEY.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="AimedArrivalTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>Arrival time at destination SCHEDULED STOP POINT.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<!-- ======================================================================= -->
<xsd:annotation>
<xsd:documentation>
A VEHICLE JOURNEY taking place on a particular date that will be managed by an AVMs.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>Type for Estimated SERVICE JOURNEY INTERCHANGE.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:choice>
<xsd:element ref="InterchangeRef"/>
<xsd:sequence>
<xsd:element name="FeederJourneyRef" type="ConnectingJourneyRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to a connecting distributor VEHICLE JOURNEY. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
Reference to a connecting distributor VEHICLE JOURNEY. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:choice>
<xsd:choice>
<xsd:element name="WillNotWait" type="EmptyType">
<xsd:annotation>
<xsd:documentation>
Distributor will not wait (i.e. connection broken) SIRI w.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="WillWait" type="WillWaitStructure">
<xsd:annotation>
<xsd:documentation>
Nature of wait that distributer will make. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
<xsd:element minOccurs="0" name="ExpectedDepartureTimeOfDistributor" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
Time at which distributor VEHICLE is expected to depart. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="ConnectionMonitoring" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether connection monitoring is active or not for this connection +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="WillWaitStructure">
<xsd:annotation>
<xsd:documentation>Type for Will Wait details</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="WaitUntilTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
Time up until which the distributor will wait. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="DriverHasAcknowledgeWIllWait" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether an acknowledgement has been received that the driver will wait. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<!-- ======================================================================= -->
<xsd:complexType name="EstimatedVehicleJourneyStructure">
<xsd:annotation>
<xsd:documentation>Type for Real-time info about a VEHICLE JOURNEY.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="RecordedAtTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
Time at which data of individual journey was recorded if differet from that of frame. (+SIRI 2.0.)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group ref="LineIdentityGroup"/>
<xsd:group minOccurs="0" ref="JourneyPatternInfoGroup"/>
<xsd:group ref="JourneyEndNamesGroup"/>
<xsd:group minOccurs="0" ref="ServiceInfoGroup"/>
<xsd:group minOccurs="0" ref="JourneyInfoGroup"/>
<xsd:group minOccurs="0" ref="EstimatedJourneyInfoGroup"/>
<xsd:group ref="DisruptionGroup"/>
<xsd:group minOccurs="0" ref="EstimatedRealtimeInfoGroup"/>
<xsd:group ref="OperationalInfoGroup"/>
<xsd:sequence>
<xsd:element minOccurs="0" name="RecordedCalls">
<xsd:annotation>
<xsd:documentation>
Observed call tmes for that art of teh journey that has already been completed. (+ SIRI 2..0)
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" ref="RecordedCall"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element minOccurs="0" name="EstimatedCalls">
<xsd:annotation>
<xsd:documentation>Estimated call tmes for journey</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" ref="EstimatedCall"/>
</xsd:sequence>
</xsd:complexType>
</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 SERVICE PATTERN and so can be used to replace a previous call sequence. Default is 'false'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:element minOccurs="0" ref="Extensions"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="EstimatedCall" type="EstimatedCallStructure">
<xsd:annotation>
<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>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="EstimatedCallStructure">
<xsd:annotation>
<xsd:documentation>
Type for Rea-ltime info about a VEHICLE JOURNEY Stop.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="StopPointInSequenceGroup"/>
<xsd:choice minOccurs="0">
<xsd:element minOccurs="0" name="ExtraCall" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
This call is additional and unplanned. If omitted: CALL is planned.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="Cancellation" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
This call is a cancellation of a previously announced call.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
<xsd:group ref="CallRealTimeInfoGroup"/>
<xsd:group ref="CallPropertyGroup"/>
<xsd:group ref="CallNoteGroup"/>
<xsd:group ref="DisruptionGroup"/>
<xsd:group ref="OnwardsCallGroup"/>
<xsd:element minOccurs="0" ref="Extensions"/>
</xsd:sequence>
</xsd:complexType>
<xsd:group name="CallRealTimeInfoGroup">
<xsd:annotation>
<xsd:documentation>
Information relating to real-time properties of call.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="PredictionInaccurate" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
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]
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="Occupancy" type="OccupancyEnumeration">
<xsd:annotation>
<xsd:documentation>
How full the bus is at the stop. If omitted: Passenger load is unknown.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<!-- ======================================================================= -->
<xsd:element name="RecordedCall" type="RecordedCallStructure">
<xsd:annotation>
<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>
</xsd:annotation>
</xsd:element>
<xsd:group name="RecordedCallGroup">
<xsd:annotation>
<xsd:documentation>
Information relating to recorded real-time properties of call.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" ref="AimedArrivalTime"/>
<xsd:element minOccurs="0" ref="ExpectedArrivalTime"/>
<xsd:element minOccurs="0" ref="ActualArrivalTime"/>
<xsd:element minOccurs="0" ref="ArrivalPlatformName">
<xsd:annotation>
<xsd:documentation>
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.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="AimedDepartureTime">
<xsd:annotation>
<xsd:documentation>
Target departure time of VEHICLE according to latest working timetable.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="ExpectedDepartureTime">
<xsd:annotation>
<xsd:documentation>Estimated time of departure of VEHICLE.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="DeparturePlatformName">
<xsd:annotation>
<xsd:documentation>
Departure QUAY ( Bay or platform) name. Defaulted taken from from planned timetable..
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="ActualDepartureTime">
<xsd:annotation>
<xsd:documentation>Estimated time of departure of VEHICLE.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="AimedHeadwayInterval"/>
<xsd:element minOccurs="0" ref="ExpectedHeadwayInterval"/>
<xsd:element minOccurs="0" ref="ActualHeadwayInterval"/>
</xsd:sequence>
</xsd:group>
<xsd:complexType name="RecordedCallStructure">
<xsd:annotation>
<xsd:documentation>
Type for recroded Real-time info about a VEHICLE JOURNEY Stop.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="StopPointInSequenceGroup"/>
<xsd:choice minOccurs="0">
<xsd:element minOccurs="0" name="ExtraCall" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
This call is additional and unplanned. If omitted: CALL is planned.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="Cancellation" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
This call is a cancellation of a previously announced call.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
<xsd:group ref="CallRealTimeInfoGroup"/>
<xsd:group ref="RecordedCallGroup"/>
<xsd:element minOccurs="0" ref="Extensions"/>
</xsd:sequence>
</xsd:complexType>
<!-- ======================================================================= -->
</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/