XML Schema "siri_journey_support-v2.0.xsd"
Target Namespace:
http://www.siri.org.uk/siri
Version:
2.0
Defined Components:
elements (6 global + 14 local), complexTypes (12), simpleTypes (18), element groups (4)
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
C:\Users\Tony\eclipse_workspace\siri-20-java\xsd\siri_model\siri_journey_support-v2.0.xsd; see XML source
Includes Schemas (1):
siri_reference-v2.0.xsd [src]
Included in Schemas (1):
siri_facility-v2.0.xsd [src]
Annotation
SIRI Journey Model Identifiers.
All Element Summary (local elements unified by type)
DataFrameRef (type DataFrameRefStructure)
identifier of data frame within particpant service.
Type:
DataFrameRefStructure
Content:
simple
Defined:
locally within FramedVehicleJourneyRefStructure complexType; see XML source
DatedVehicleJourneyRef
Reference to a DATED VEHICLE JOURNEY.
Type:
DatedVehicleJourneyRefStructure
Content:
simple
Defined:
globally; see XML source
Used:
at 1 location
DatedVehicleJourneyRef (type DatedVehicleJourneyCodeType)
Type:
DatedVehicleJourneyCodeType
Content:
simple
Defined:
locally at 3 locations
DestinationRef
Reference to the destination SCHEDULED STOP POINT of the journey.
Type:
DestinationRefStructure
Content:
simple
Defined:
globally; see XML source
Used:
at 2 locations
DirectionRef (type DirectionRefStructure)
Type:
DirectionRefStructure
Content:
simple
Defined:
locally at 20 locations
FramedVehicleJourneyRef (type FramedVehicleJourneyRefStructure)
Type:
FramedVehicleJourneyRefStructure
Content:
complex, 2 elements
Defined:
locally at 8 locations
InterchangeRef
Reference to a SERVCIE JOURNEY INTERCHANGE.
Type:
InterchangeRefStructure
Content:
simple
Defined:
globally; see XML source
Used:
at 4 locations
LineRef (type LineRefStructure)
Type:
LineRefStructure
Content:
simple
Defined:
locally at 23 locations
OperatorRef (type OperatorRefStructure)
Type:
OperatorRefStructure
Content:
simple
Defined:
locally at 12 locations
OriginRef
Reference to the origin SCHEDULED STOP POINT of the journey.
Type:
JourneyPlaceRefStructure
Content:
simple
Defined:
globally; see XML source
Used:
at 2 locations
ParticipantRef (type ParticipantRefStructure)
Type:
ParticipantRefStructure
Content:
simple
Defined:
locally at 6 locations
ProductCategoryRef (type ProductCategoryRefStructure)
Product Classification of VEHICLE JOURNEY- subdivides a transport mode. e.g. express, loacl.
Type:
ProductCategoryRefStructure
Content:
simple
Defined:
locally within BasicServiceInfoGroup group; see XML source
VehicleFeatureRef (type VehicleFeatureRefStructure)
Features of VEHICLE providing journey.
Type:
VehicleFeatureRefStructure
Content:
simple
Defined:
locally within ServiceInfoGroup group; see XML source
VehicleJourneyRef
Reference to a VEHICLE JOURNEY.
Type:
VehicleJourneyRefStructure
Content:
simple
Defined:
globally; see XML source
Used:
at 4 locations
ViaRef
Reference to a SCHEDULED STOP POINT that is a VIA point on the journey.
Type:
JourneyPlaceRefStructure
Content:
simple
Defined:
globally; see XML source
Used:
at 1 location
Complex Type Summary
BlockRefStructure
Type for reference to a BLOCK.
Content:
simple
Defined:
globally; see XML source
Used:
at 1 location
ConnectingJourneyRefStructure
Type for a reference to a connecting journey.
Content:
complex, 3 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
at 4 locations
CourseOfJourneyRefStructure
Type for reference to a COURSE OF JOURNEY (Run).
Content:
simple
Defined:
globally; see XML source
Used:
at 1 location
DataFrameRefStructure
Type for identifier of a data VERSION FRAME.
Content:
simple
Defined:
globally; see XML source
Used:
at 1 location
DatedVehicleJourneyRefStructure
Type for reference to a Dated VEHICLE JOURNEY.
Content:
simple
Defined:
globally; see XML source
Used:
at 4 locations
DestinationRefStructure
Type for reference to a DESTINATION.
Content:
simple
Defined:
globally; see XML source
Used:
at 2 locations
FramedVehicleJourneyRefStructure
Type for identifer of a VEHICLE JOURNEY within data Horizon of a service.
Content:
complex, 2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
at 4 locations
InterchangeRefStructure
Type for reference to a SERVCIE JOURNEY INTERCHANGE.
Content:
simple
Defined:
globally; see XML source
Used:
at 2 locations
JourneyPartRefStructure
Type for reference to a JOURNEY PART
Content:
simple
Defined:
globally; see XML source
Used:
never
TrainNumberRefStructure
Type for reference to a TRAIN NUMBER
Content:
simple
Defined:
globally; see XML source
Used:
at 1 location
TrainPartRefStructure
Type for reference to a Train Part.
Content:
simple
Defined:
globally; see XML source
Used:
at 1 location
VehicleJourneyRefStructure
Type for reference to a VEHICLE JOURNEY.
Content:
simple
Defined:
globally; see XML source
Used:
at 2 locations
Simple Type Summary
ArrivalBoardingActivityEnumeration
Allowed types activity for Alighting.
Defined:
globally; see XML source
Used:
at 2 locations
BlockNumber
Type for identifier of an BLOCK.
Defined:
globally; see XML source
Used:
at 1 location
BoardingActivityEnumeration
Allowed types activity for Boarding and Alighting.
Defined:
globally; see XML source
Used:
never
CallStatusEnumeration
Classification of the timeliness of the CALL, according to a fixed list of values.
Defined:
globally; see XML source
Used:
at 2 locations
CourseOfJourneyNumber
Type for identifier of a COURSE OF JOURNEY (Run).
Defined:
globally; see XML source
Used:
at 1 location
DataFrameQualifierType
Type for identifier of a data VERSION FRAME.
Defined:
globally; see XML source
Used:
at 1 location
DatedVehicleJourneyCodeType
Type for identifier of a Dated VEHICLE JOURNEY.
Defined:
globally; see XML source
Used:
at 3 locations
DepartureBoardingActivityEnumeration
Allowed types activity for Boarding.
Defined:
globally; see XML source
Used:
at 2 locations
EstimatedVehicleJourneyCodeType
Type for identifier of a Realtime VEHICLE JOURNEY.
Defined:
globally; see XML source
Used:
at 1 location
FirstOrLastJourneyEnumeration
Allowed types activity for FirstOrLastJourney.
Defined:
globally; see XML source
Used:
at 2 locations
InterchangeCodeType
Type for identifer of a SERVCIE JOURNEY INTERCHANGE.
Defined:
globally; see XML source
Used:
at 2 locations
JourneyPartIdType
Type for identifier of an JOURNEY PART
Defined:
globally; see XML source
Used:
at 1 location
ProgressRateEnumeration
Classification of the rate of progress of VEHICLE according a fixed list of values.
Defined:
globally; see XML source
Used:
at 1 location
QualityIndexEnumeration
Classification of the quality of the prediction of the CALL, according to a fixed list of values.
Defined:
globally; see XML source
Used:
at 2 locations
TrainNumber
Type for identifier of an TRAIN NUMBER
Defined:
globally; see XML source
Used:
at 1 location
TrainPartCodeType
Type for identifier of Train Part.
Defined:
globally; see XML source
Used:
at 1 location
VehicleJourneyCodeType
Type for identifier of a VEHICLE JOURNEY.
Defined:
globally; see XML source
Used:
at 1 location
VehicleStatusEnumeration
Classification of the State of the VEHICLE JORUNEY according to a fixed list of values.
Defined:
globally; see XML source
Used:
at 1 location
Element Group Summary
BasicServiceInfoGroup
Information that classifies journey.
Content:
3 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
at 1 location
JourneyIdentityGroup
Elements identifying VEHICLE JOURNEY.
Content:
3 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
at 3 locations
MonitoredJourneyIdentityGroup
Elements identifying a VEHICLE JOURNEY.
Content:
3 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
at 1 location
ServiceInfoGroup
Elements classifying the Service or journey.
Content:
4 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
at 7 locations
XML Source
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" id="siri_journey_support" 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
Create from siri_journey
Add TrainNumber
Add departed, missed states to ProgressStatusEnum (arrivalStatus and DepartureStatus)
Add VehicleStatusEnum
</Date>
<Date>
<Modified>2013-02-11</Modified>
SIRI 2.0
Add notExpected state to ProgressStatusEnum
Corrected enumeration value cancellled in VehicleStatusEnum
</Date>
<Description>
<p>
SIRI is a European CEN technical standard for the exchange of real-time information .
</p>
<p>
This subschema defines identifer definitions for 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_journey_support.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/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 identifers common journey elements
</Title>
<Type>Standard</Type>
</Metadata>
</xsd:appinfo>
<xsd:documentation>SIRI Journey Model Identifiers.</xsd:documentation>
</xsd:annotation>
<!-- ======================================================================= -->
<xsd:include schemaLocation="siri_reference-v2.0.xsd"/>
<!-- ==== Journey == ============================================= -->
<xsd:group name="JourneyIdentityGroup">
<xsd:annotation>
<xsd:documentation>Elements identifying VEHICLE JOURNEY.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="LineRef" type="LineRefStructure">
<xsd:annotation>
<xsd:documentation>Reference to a LINE.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="DirectionRef" type="DirectionRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to a DIRECTION, typically outward or return.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="FramedVehicleJourneyRef" type="FramedVehicleJourneyRefStructure">
<xsd:annotation>
<xsd:documentation>
A reference to the dated VEHICLE JOURNEY that the VEHICLE is making.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:annotation>
<xsd:documentation>
Elements identifying a VEHICLE JOURNEY. LINE and DIRECTION will be same as for journey unless overridden.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="LineRef" type="LineRefStructure">
<xsd:annotation>
<xsd:documentation>Reference to LINE of journey.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="DirectionRef" type="DirectionRefStructure">
<xsd:annotation>
<xsd:documentation>Reference to DIRECTION of journey.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="FramedVehicleJourneyRef" type="FramedVehicleJourneyRefStructure">
<xsd:annotation>
<xsd:documentation>
A reference to the DATED VEHICLE JOURNEY that the VEHICLE is making, unique with the data horizon of the service.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<!-- =====VEHICLE JOURNEY identfiers=============================================================== -->
<xsd:simpleType name="VehicleJourneyCodeType">
<xsd:annotation>
<xsd:documentation>Type for identifier of a VEHICLE JOURNEY.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN"/>
</xsd:simpleType>
<xsd:complexType name="VehicleJourneyRefStructure">
<xsd:annotation>
<xsd:documentation>Type for reference to a VEHICLE JOURNEY.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="VehicleJourneyCodeType"/>
</xsd:simpleContent>
</xsd:complexType>
<xsd:element name="VehicleJourneyRef" type="VehicleJourneyRefStructure">
<xsd:annotation>
<xsd:documentation>Reference to a VEHICLE JOURNEY.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:simpleType name="DatedVehicleJourneyCodeType">
<xsd:annotation>
<xsd:documentation>Type for identifier of a Dated VEHICLE JOURNEY.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN"/>
</xsd:simpleType>
<xsd:complexType name="DatedVehicleJourneyRefStructure">
<xsd:annotation>
<xsd:documentation>Type for reference to a Dated VEHICLE JOURNEY.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="DatedVehicleJourneyCodeType"/>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>Reference to a DATED VEHICLE JOURNEY.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:simpleType name="EstimatedVehicleJourneyCodeType">
<xsd:annotation>
<xsd:documentation>
Type for identifier of a Realtime VEHICLE JOURNEY. Used for adhoc journeys.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN"/>
</xsd:simpleType>
<!-- =====VEHICLE JOURNEY identfiers=============================================================== -->
<xsd:complexType name="ConnectingJourneyRefStructure">
<xsd:annotation>
<xsd:documentation>Type for a reference to a connecting journey.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="FramedVehicleJourneyRef" type="FramedVehicleJourneyRefStructure">
<xsd:annotation>
<xsd:documentation>
A reference to the DATE VEHICLE JOURNEY that the VEHICLE is making, unique with the data horizon of the service.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="LineRef" type="LineRefStructure">
<xsd:annotation>
<xsd:documentation>LINE Reference.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="ParticipantRef" type="ParticipantRefStructure"/>
</xsd:sequence>
</xsd:complexType>
<!-- ===== INTERCHANGE identfiers=============================================================== -->
<xsd:simpleType name="InterchangeCodeType">
<xsd:annotation>
<xsd:documentation>
Type for identifer of a SERVCIE JOURNEY INTERCHANGE.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN"/>
</xsd:simpleType>
<xsd:complexType name="InterchangeRefStructure">
<xsd:annotation>
<xsd:documentation>
Type for reference to a SERVCIE JOURNEY INTERCHANGE.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="InterchangeCodeType"/>
</xsd:simpleContent>
</xsd:complexType>
<xsd:element name="InterchangeRef" type="InterchangeRefStructure">
<xsd:annotation>
<xsd:documentation>Reference to a SERVCIE JOURNEY INTERCHANGE.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<!-- ======================================================================= -->
<xsd:complexType name="FramedVehicleJourneyRefStructure">
<xsd:annotation>
<xsd:documentation>
Type for identifer of a VEHICLE JOURNEY within data Horizon of a service.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="DataFrameRef" type="DataFrameRefStructure">
<xsd:annotation>
<xsd:documentation>
identifier of data frame within particpant service. Used to ensure that the Reference to a DATED VEGICLE JOURNEY is unique with the data horizon of the service. Often the OperationalDayType is used for this purpose.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
A reference to the dated VEHICLE JOURNEY that the VEHICLE is making.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:simpleType name="DataFrameQualifierType">
<xsd:annotation>
<xsd:documentation>Type for identifier of a data VERSION FRAME.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN"/>
</xsd:simpleType>
<xsd:complexType name="DataFrameRefStructure">
<xsd:annotation>
<xsd:documentation>Type for identifier of a data VERSION FRAME.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="DataFrameQualifierType"/>
</xsd:simpleContent>
</xsd:complexType>
<!-- ====== TRAIN PART identifiers=================================================== -->
<xsd:simpleType name="TrainPartCodeType">
<xsd:annotation>
<xsd:documentation>Type for identifier of Train Part.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN"/>
</xsd:simpleType>
<xsd:complexType name="TrainPartRefStructure">
<xsd:annotation>
<xsd:documentation>Type for reference to a Train Part.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="TrainPartCodeType"/>
</xsd:simpleContent>
</xsd:complexType>
<!-- ====== Block Identifiers=================================================== -->
<xsd:simpleType name="BlockNumber">
<xsd:annotation>
<xsd:documentation>Type for identifier of an BLOCK.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN"/>
</xsd:simpleType>
<xsd:complexType name="BlockRefStructure">
<xsd:annotation>
<xsd:documentation>Type for reference to a BLOCK.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="BlockNumber"/>
</xsd:simpleContent>
</xsd:complexType>
<xsd:simpleType name="CourseOfJourneyNumber">
<xsd:annotation>
<xsd:documentation>Type for identifier of a COURSE OF JOURNEY (Run).</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN"/>
</xsd:simpleType>
<xsd:complexType name="CourseOfJourneyRefStructure">
<xsd:annotation>
<xsd:documentation>Type for reference to a COURSE OF JOURNEY (Run).</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="CourseOfJourneyNumber"/>
</xsd:simpleContent>
</xsd:complexType>
<!-- ====== JOURNEY PART Identifiers=================================================== -->
<xsd:simpleType name="JourneyPartIdType">
<xsd:annotation>
<xsd:documentation>Type for identifier of an JOURNEY PART</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN"/>
</xsd:simpleType>
<xsd:complexType name="JourneyPartRefStructure">
<xsd:annotation>
<xsd:documentation>Type for reference to a JOURNEY PART</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="JourneyPartIdType"/>
</xsd:simpleContent>
</xsd:complexType>
<xsd:simpleType name="TrainNumber">
<xsd:annotation>
<xsd:documentation>Type for identifier of an TRAIN NUMBER</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN"/>
</xsd:simpleType>
<xsd:complexType name="TrainNumberRefStructure">
<xsd:annotation>
<xsd:documentation>Type for reference to a TRAIN NUMBER</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="TrainNumber"/>
</xsd:simpleContent>
</xsd:complexType>
<!-- =====MonitoredCallPoint============================================================ -->
<xsd:simpleType name="BoardingActivityEnumeration">
<xsd:annotation>
<xsd:documentation>
Allowed types activity for Boarding and Alighting.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="boardingAndAlighting"/>
<xsd:enumeration value="noBoarding"/>
<xsd:enumeration value="noAlighting"/>
<xsd:enumeration value="passThru"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="ArrivalBoardingActivityEnumeration">
<xsd:annotation>
<xsd:documentation>Allowed types activity for Alighting.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="alighting"/>
<xsd:enumeration value="noAlighting"/>
<xsd:enumeration value="passThru"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="DepartureBoardingActivityEnumeration">
<xsd:annotation>
<xsd:documentation>Allowed types activity for Boarding.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="boarding"/>
<xsd:enumeration value="noBoarding"/>
<xsd:enumeration value="passThru"/>
</xsd:restriction>
</xsd:simpleType>
<!-- ======================================================================= -->
<!-- ==== LINE and DESTINATION identifiers-->
<xsd:element name="OriginRef" type="JourneyPlaceRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to the origin SCHEDULED STOP POINT of the journey.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ViaRef" type="JourneyPlaceRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to a SCHEDULED STOP POINT that is a VIA point on the journey.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="DestinationRef" type="DestinationRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to the destination SCHEDULED STOP POINT of the journey.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="DestinationRefStructure">
<xsd:annotation>
<xsd:documentation>Type for reference to a DESTINATION.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="DestinationCodeType"/>
</xsd:simpleContent>
</xsd:complexType>
<!-- ======================================================================= -->
<xsd:group name="BasicServiceInfoGroup">
<xsd:annotation>
<xsd:documentation>Information that classifies journey.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="OperatorRef" type="OperatorRefStructure">
<xsd:annotation>
<xsd:documentation>
OPERATOR of a VEHICLE JOURNEY. Note that the operator may change over the course of a journey. This shoudl show teh operator for the curent point in the journey. Use Journey Parts tp record all the operators in the whole journeyh.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="ProductCategoryRef" type="ProductCategoryRefStructure">
<xsd:annotation>
<xsd:documentation>
Product Classification of VEHICLE JOURNEY- subdivides a transport mode. e.g. express, loacl.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="ServiceFeatureRef">
<xsd:annotation>
<xsd:documentation>
Classification of service into arbitrary Service categories, e.g. school bus. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package.
Corresponds to NeTEX TYPE OF SERVICe.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:group name="ServiceInfoGroup">
<xsd:annotation>
<xsd:documentation>
Elements classifying the Service or journey. Values for these elements can be specified on a timetabled schedule and will be inherited, unless overriden, onto the production timetable and then onto the individul dated VEHICLE JOURNEYs of the timetable. Each monitored journey takes its values from the dated VEHICLE JOURNEY that it follows. The absence of a value on an entity at a given level indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="BasicServiceInfoGroup"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="VehicleFeatureRef" type="VehicleFeatureRefStructure">
<xsd:annotation>
<xsd:documentation>
Features of VEHICLE providing journey. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<!-- ====Status QUality=========================================================== -->
<xsd:simpleType name="ProgressRateEnumeration">
<xsd:annotation>
<xsd:documentation>
Classification of the rate of progress of VEHICLE according a fixed list of values.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="noProgress">
<xsd:annotation>
<xsd:documentation>Vehicle is stationary.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="slowProgress">
<xsd:annotation>
<xsd:documentation>Vehicle is proceeding slower than normal.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="normalProgress">
<xsd:annotation>
<xsd:documentation>Vehicle is proceeding at a normal rate.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="fastProgress">
<xsd:annotation>
<xsd:documentation>Vehicle is proceeding faster than normal.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="unknown">
<xsd:annotation>
<xsd:documentation>There is no data.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="CallStatusEnumeration">
<xsd:annotation>
<xsd:documentation>
Classification of the timeliness of the CALL, according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are still classified as on-time. Applications may use this to guide their own presentation of times.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="onTime">
<xsd:annotation>
<xsd:documentation>Service is on time.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="early">
<xsd:annotation>
<xsd:documentation>Service is earlier than expected.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="delayed">
<xsd:annotation>
<xsd:documentation>Service is delayed.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="cancelled">
<xsd:annotation>
<xsd:documentation>Service is cancelled.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="arrived">
<xsd:annotation>
<xsd:documentation>Service has arrived.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="departed"/>
<xsd:enumeration value="missed"/>
<xsd:enumeration value="noReport">
<xsd:annotation>
<xsd:documentation>There is no information about the service.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="notExpected">
<xsd:annotation>
<xsd:documentation>
Service is not expected to call this stop. For instance a flexible service that has not yet been preordered.
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="VehicleStatusEnumeration">
<xsd:annotation>
<xsd:documentation>
Classification of the State of the VEHICLE JORUNEY according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are still classified as on-time. Applications may use this to guide their own presentation of times.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="expected">
<xsd:annotation>
<xsd:documentation>Service is expected to be performed.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="notExpected">
<xsd:annotation>
<xsd:documentation>
Service is not expected to be run. For instance a flexible service that has not yet been preordered.
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="cancelled"/>
<xsd:enumeration value="assigned"/>
<xsd:enumeration value="signedOn"/>
<xsd:enumeration value="atOrigin"/>
<xsd:enumeration value="inProgress">
<xsd:annotation>
<xsd:documentation>Service has departed from first stop.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="aborted"/>
<xsd:enumeration value="offRoute"/>
<xsd:enumeration value="completed">
<xsd:annotation>
<xsd:documentation>
It has been detected that the Service was completed.
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="assumedCompleted">
<xsd:annotation>
<xsd:documentation>It is assumed that the Service has completed.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="notRun"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="QualityIndexEnumeration">
<xsd:annotation>
<xsd:documentation>
Classification of the quality of the prediction of the CALL, according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are stiull classified as on-time. Applications may use this to guide their own presentation of times.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="certain">
<xsd:annotation>
<xsd:documentation>Data is certain (1/5).</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="veryReliable">
<xsd:annotation>
<xsd:documentation>Data has confidence level of very reliable (2/5).</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="reliable">
<xsd:annotation>
<xsd:documentation>Data has confidence lvel of reliabel (3/5).</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="probablyReliable">
<xsd:annotation>
<xsd:documentation>Data is thought to be reliable (4/5)</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="unconfirmed">
<xsd:annotation>
<xsd:documentation>Data is unconfirmed (5/5).</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="FirstOrLastJourneyEnumeration">
<xsd:annotation>
<xsd:documentation>Allowed types activity for FirstOrLastJourney.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="firstServiceOfDay"/>
<xsd:enumeration value="otherService"/>
<xsd:enumeration value="lastServiceOfDay"/>
<xsd:enumeration value="unspecified"/>
</xsd:restriction>
</xsd:simpleType>
</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/