XML Schema "siri_reference-v2.0.xsd"
Target Namespace:
http://www.siri.org.uk/siri
Version:
2.0
Defined Components:
elements (13 global + 19 local), complexTypes (21), simpleTypes (22), element groups (8)
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
C:\Users\Tony\eclipse_workspace\siri-20-java\xsd\siri_model\siri_reference-v2.0.xsd; see XML source
Includes Schemas (4):
siri_operator_support-v2.0.xsd [src], siri_situationIdentity-v1.1.xsd [src], siri_time-v2.0.xsd [src], siri_types-v2.0.xsd [src]
Included in Schemas (6):
siri_connectionLink-v2.0.xsd [src], siri_generalMessage_service.xsd [src], siri_infoChannel-v2.0.xsd [src], siri_journey_support-v2.0.xsd [src], siri_modelPermissions-v2.0.xsd [src], siri_stopPoint-v2.0.xsd [src]
All Element Summary (local elements unified by type)
ConnectionLinkRef
Reference to a CONNECTION link
Type:
ConnectionLinkRefStructure
Content:
simple
Defined:
globally; see XML source
Used:
at 3 locations
DestinationName (type NaturalLanguageStringStructure)
Type:
NaturalLanguageStringStructure
Content:
simple, 1 attribute
Defined:
locally at 3 locations
DirectionName (type NaturalLanguageStringStructure)
Type:
NaturalLanguageStringStructure
Content:
simple, 1 attribute
Defined:
locally at 2 locations
DirectionRef (type DirectionRefStructure)
Type:
DirectionRefStructure
Content:
simple
Defined:
locally at 20 locations
ExternalLineRef (type LineRefStructure)
Alternative identifier of LINE that an external system may associate with journey.
Type:
LineRefStructure
Content:
simple
Defined:
locally within JourneyPatternInfoGroup group; see XML source
GroupOfLinesRef (type GroupOfLinesRefStructure)
Reference to a GROUP OF LINEs to which journey belongs.
Type:
GroupOfLinesRefStructure
Content:
simple
Defined:
locally within JourneyPatternInfoGroup group; see XML source
JourneyPatternName (type NaturalLanguageStringStructure)
Name of Joruney Pattern
Type:
NaturalLanguageStringStructure
Content:
simple, 1 attribute
Defined:
locally within JourneyPatternInfoGroup group; see XML source
JourneyPatternRef
Reference to a JOURNEY PATTERN.
Type:
JourneyPatternRefStructure
Content:
simple
Defined:
globally; see XML source
Used:
at 1 location
JourneyPatternRef (type JourneyPatternRefStructure)
Identifier of JOURNEY PATTERN that journey follows.
Type:
JourneyPatternRefStructure
Content:
simple
Defined:
locally within JourneyPatternInfoGroup group; see XML source
LineRef
Reference to a LINE.
Type:
LineRefStructure
Content:
simple
Defined:
globally; see XML source
Used:
at 5 locations
LineRef (type LineRefStructure)
Type:
LineRefStructure
Content:
simple
Defined:
locally at 23 locations
Mode (type AllModesEnumeration)
A method of transportation such as bus, rail, etc.
Type:
AllModesEnumeration
Content:
simple
Defined:
locally within ModesStructure complexType; see XML source
Note (in StopMonitoringDelivery)
Type:
NaturalLanguageStringStructure
Content:
simple, 1 attribute
Defined:
locally at 2 locations
Order
For implementations for which the overall Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then can be used to associate the stop Order as well if useful.
Type:
xsd:positiveInteger
Content:
simple
Defined:
globally; see XML source
Used:
at 3 locations
PlaceName (in Via)
Names of place used to help identify the LINE.
Type:
NaturalLanguagePlaceNameStructure
Content:
simple, 1 attribute
Defined:
locally within PlaceNameStructure complexType; see XML source
PlaceRef (in Via)
Reference to a TOPOGRAPHIC PLACE.
Type:
JourneyPlaceRefStructure
Content:
simple
Defined:
locally within PlaceNameStructure complexType; see XML source
PlaceShortName (in Via)
Short name of TOPOGRAPHIC PLACE.
Type:
NaturalLanguagePlaceNameStructure
Content:
simple, 1 attribute
Defined:
locally within PlaceNameStructure complexType; see XML source
PublishedLineName
Name or Number by which the LINEis known to the public.
Type:
NaturalLanguageStringStructure
Content:
simple, 1 attribute
Defined:
globally; see XML source
Used:
at 4 locations
RouteName
Description of route by which it can be recogniozed.
Type:
NaturalLanguageStringStructure
Content:
simple, 1 attribute
Defined:
globally; see XML source
Used:
never
RouteRef (type RouteRefStructure)
Type:
RouteRefStructure
Content:
simple
Defined:
locally at 2 locations
StopPointName
Name of SCHEDULED STOP POINT.
Type:
NaturalLanguageStringStructure
Content:
simple, 1 attribute
Defined:
globally; see XML source
Used:
at 3 locations
StopPointName (type NaturalLanguageStringStructure)
Type:
NaturalLanguageStringStructure
Content:
simple, 1 attribute
Defined:
locally at 2 locations
StopPointRef
Reference to a SCHEDULED STOP POINT.
Type:
StopPointRefStructure
Content:
simple
Defined:
globally; see XML source
Used:
at 10 locations
StopPointRef (type StopPointRefStructure)
Type:
StopPointRefStructure
Content:
simple
Defined:
locally at 5 locations
TimingPoint
Whether the stop is a TIMING POINT.
Type:
xsd:boolean
Content:
simple
Defined:
globally; see XML source
Used:
at 4 locations
VehicleAtStop
Whether VEHICLE is currently at stop.
Type:
xsd:boolean
Content:
simple
Defined:
globally; see XML source
Used:
at 5 locations
VehicleMode (type VehicleModesEnumeration)
A means of transportation such as bus, rail, etc.
Type:
VehicleModesEnumeration
Content:
simple
Defined:
locally within JourneyPatternInfoGroup group; see XML source
VehicleRef
Reference to a VEHICLE.
Type:
VehicleRefStructure
Content:
simple
Defined:
globally; see XML source
Used:
at 4 locations
VersionRef
Version Identifier.
Type:
VersionCodeType
Content:
simple
Defined:
globally; see XML source
Used:
at 1 location
VisitNumber
Sequence of visit to SCHEDULED STOP POINT.within VEHICLE JOURNEY.
Type:
VisitNumberType
Content:
simple
Defined:
globally; see XML source
Used:
at 7 locations
Complex Type Summary
ClearDownRefStructure
Reference Cleardown identifier of a stop.
Content:
simple
Defined:
globally; see XML source
Used:
at 1 location
ConnectionLinkRefStructure
Type for reference to a CONNECTION link
Content:
simple
Defined:
globally; see XML source
Used:
at 3 locations
DirectionRefStructure
Reference to a DIRECTION.
Content:
simple
Defined:
globally; see XML source
Used:
at 1 location
DriverRefStructure
Reference to a DRIVER.
Content:
simple
Defined:
globally; see XML source
Used:
never
GroupOfLinesRefStructure
Reference to a GROUP OF LINEs
Content:
simple
Defined:
globally; see XML source
Used:
at 1 location
InfoChannelRefStructure
Type for reference to an Info Channel.
Content:
simple
Defined:
globally; see XML source
Used:
at 1 location
JourneyPatternRefStructure
Type for refrence to a JOURNEY PATTERN.
Content:
simple
Defined:
globally; see XML source
Used:
at 2 locations
JourneyPlaceRefStructure
Reference to a PLACE visited by a VEHICLE JOURNEY.
Content:
simple
Defined:
globally; see XML source
Used:
at 3 locations
LineDirectionStructure
Type for LINEand DIRECTION.
Content:
complex, 2 elements
Defined:
globally; see XML source
Used:
at 2 locations
LineRefStructure
Type for reference to a LINE.
Content:
simple
Defined:
globally; see XML source
Used:
at 3 locations
ModesStructure
Type for Transport MODEs.
Content:
complex, 1 attribute, 1 element
Defined:
globally; see XML source
Includes:
definitions of 1 attribute, 1 element
Used:
never
MonitoringRefStructure
Type for reference to a monitoring point (LOGICAL DISPLAY).
Content:
simple
Defined:
globally; see XML source
Used:
at 1 location
NoteStructure
DataType for a NOTICe.
Content:
complex, 4 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
never
PlaceNameStructure
Names of VIA points, used to help identify the LINE, for example, Luton to Luton via Sutton.
Content:
complex, 3 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
at 1 location
QuayRefStructure
Type for reference to a QUAY.
Content:
simple
Defined:
globally; see XML source
Used:
at 3 locations
RouteLinkRefStructure
Reference to a ROUTE LINk.
Content:
simple
Defined:
globally; see XML source
Used:
at 1 location
RouteRefStructure
Reference to a Route (Transmodel)
Content:
simple
Defined:
globally; see XML source
Used:
at 1 location
StopAreaRefStructure
Reference to a STOP AREA.
Content:
simple
Defined:
globally; see XML source
Used:
at 1 location
StopPointRefStructure
Reference to a SCHEDULED STOP POINT.
Content:
simple
Defined:
globally; see XML source
Used:
at 12 locations
VehicleRefStructure
Reference to a VEHICLE.
Content:
simple
Defined:
globally; see XML source
Used:
at 2 locations
VersionRefStructure
Type for reference Timetable Version.
Content:
simple
Defined:
globally; see XML source
Used:
at 3 locations
Simple Type Summary
AllModesEnumeration
Union of VEHICLE and continuous MODEs.
Defined:
globally; see XML source
Used:
at 1 location
ClearDownCodeType
Identifier of a Stop for Direct Cleardown.
Defined:
globally; see XML source
Used:
at 1 location
ConnectionLinkCodeType
Type for identifier of a CONNECTION link
Defined:
globally; see XML source
Used:
at 2 locations
ContinuousModesEnumeration
MODEs of transport applicable to private and non-timetabled transport.
Defined:
globally; see XML source
Used:
never
DestinationCodeType
Type for identifier of a DESTINATION.
Defined:
globally; see XML source
Used:
at 1 location
DirectionCodeType
Identifier of a DIRECTION.
Defined:
globally; see XML source
Used:
at 1 location
DriverCodeType
Identifier of a DRIVER
Defined:
globally; see XML source
Used:
at 1 location
GroupOfLinesCodeType
Identifier of a GROUP OF LINEs
Defined:
globally; see XML source
Used:
at 1 location
InfoChannelCodeType
Type for identifier of an Info Channel.
Defined:
globally; see XML source
Used:
at 2 locations
JourneyPatternCodeType
Type for identifier of a JOURNEY PATTERN.
Defined:
globally; see XML source
Used:
at 1 location
LineRefCodeType
Type for identifier of a LINE
Defined:
globally; see XML source
Used:
at 2 locations
MonitoringCode
Identifier of a monitoring point.
Defined:
globally; see XML source
Used:
at 1 location
OccupancyEnumeration
Passenger load status of a VEHICLE.
Defined:
globally; see XML source
Used:
at 1 location
QuayCodeType
Type for identifier of a QUAY (Platform, Bay, etc).
Defined:
globally; see XML source
Used:
at 1 location
RouteCodeType
Type for identifier of a Route.
Defined:
globally; see XML source
Used:
at 1 location
RouteLinkCodeType
Identifier of a ROUTE LINk.
Defined:
globally; see XML source
Used:
at 1 location
StopAreaCodeType
Type for identifier of a STOP AREA.
Defined:
globally; see XML source
Used:
at 1 location
StopPointCodeType
Type for identifier of a SCHEDULED STOP POINT.
Defined:
globally; see XML source
Used:
at 1 location
VehicleCodeType
Identifier of a VEHICLE.
Defined:
globally; see XML source
Used:
at 1 location
VehicleModesEnumeration
MODEs of transport applicable to timetabled public transport.
Defined:
globally; see XML source
Used:
at 1 location
VersionCodeType
Type for identifier of a Version.
Defined:
globally; see XML source
Used:
at 2 locations
VisitNumberType
Type for Stop Visit.
Defined:
globally; see XML source
Used:
at 3 locations
Element Group Summary
ContextualisedStopPointInSequenceGroup
Elements identifying Ordered visit to a stop within calling sequence of a SERVICE PATTERN.
Content:
4 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
at 3 locations
JourneyPatternInfoGroup
Elements describing the LINE, ROUTE and DIRECTION of a VEHICLE JOURNEYwhich are derived from the JOURNEY PATTERN associated with the journey.
Content:
8 elements
Defined:
globally; see XML source
Includes:
definitions of 8 elements
Used:
at 13 locations
JourneyPatternRefGroup
Elements describing the ROUTE and JOURNEY PATTERN Identfiers associated with a journey.
Defined:
globally; see XML source
Used:
never
LineDirectionGroup
Elements for a LINE and DIRECTION.
Content:
2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
at 1 location
LineIdentityGroup
Elements for identifying a LINE and DIRECTION.
Content:
2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
at 6 locations
PublishedLineGroup
Elements describing the LINEand DESTINATION of a journey.
Content:
2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
never
StopPointGroup
Elements for a SCHEDULED STOP POINT.
Content:
2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
never
StopPointInSequenceGroup
Elements identifying an ordered visit to a SCHEDULED STOP POINT within a SERVICE PATTERN.
Content:
4 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
at 4 locations
XML Source
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" id="siri_reference" 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-09-29</Created>
</Date>
<Date>
<Modified>2004-10-01</Modified>
</Date>
<Date>
<Modified>2005-02-14</Modified>
</Date>
<Date>
<Modified>2005-02-20</Modified>
</Date>
<Date>
<Modified>2005-03-20</Modified>
</Date>
<Date>
<Modified>2005-05-11</Modified>
</Date>
<Date>
<Modified>2007-03-29</Modified>
</Date>
<Date>
<Modified>2012-03-22</Modified>
SIRI 2.0
Refactor Monitoring code
Add QUAY Ref
</Date>
<Date>
<Modified>2012-06-22</Modified>
SIRI 2.0
Add Group of Lines to JourneyPatternInfoGroup
[CH] Set explicit default value for VehicleAtStop to be false
[DE] Add Driver Ref
</Date>
<Date>
<Modified>2013-02-11</Modified>
Correction: PlaceName unbounded to allow multiple languages
</Date>
<Description>
<p>
SIRI is a European CEN standard for the exchange of real-time information .
</p>
<p>
This package defines common basic domain model identifier elements that are used in one or more SIRI fucntional 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/utility/}siri_reference-v2.0.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. Common DomainModel elements.
</Title>
<Type>Standard</Type>
</Metadata>
</xsd:appinfo>
</xsd:annotation>
<!-- ======================================================================= -->
<xsd:include schemaLocation="../siri_utility/siri_types-v2.0.xsd"/>
<xsd:include schemaLocation="siri_operator_support-v2.0.xsd"/>
<xsd:include schemaLocation="siri_time-v2.0.xsd"/>
<xsd:include schemaLocation="siri_situationIdentity-v1.1.xsd"/>
<!-- ========= VERSION =========================================== -->
<xsd:element name="VersionRef" type="VersionCodeType">
<xsd:annotation>
<xsd:documentation>Version Identifier.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:simpleType name="VersionCodeType">
<xsd:annotation>
<xsd:documentation>Type for identifier of a Version.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN"/>
</xsd:simpleType>
<xsd:complexType name="VersionRefStructure">
<xsd:annotation>
<xsd:documentation>Type for reference Timetable Version.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="VersionCodeType"/>
</xsd:simpleContent>
</xsd:complexType>
<!-- ===== SCHEDULED STOP POINT ==================================================== -->
<xsd:simpleType name="StopPointCodeType">
<xsd:annotation>
<xsd:documentation>Type for identifier of a SCHEDULED STOP POINT.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN"/>
</xsd:simpleType>
<xsd:complexType name="StopPointRefStructure">
<xsd:annotation>
<xsd:documentation>Reference to a SCHEDULED STOP POINT.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="StopPointCodeType"/>
</xsd:simpleContent>
</xsd:complexType>
<xsd:element name="VisitNumber" type="VisitNumberType">
<xsd:annotation>
<xsd:documentation>
Sequence of visit to SCHEDULED STOP POINT.within VEHICLE JOURNEY. Increases monotonically, but not necessarily sequentially.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Order" type="xsd:positiveInteger">
<xsd:annotation>
<xsd:documentation>
For implementations for which the overall Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then can be used to associate the stop Order as well if useful.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group name="StopPointGroup">
<xsd:annotation>
<xsd:documentation>Elements for a SCHEDULED STOP POINT.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="StopPointRef" type="StopPointRefStructure">
<xsd:annotation>
<xsd:documentation>Reference to a SCHEDULED STOP POINT.</xsd:documentation>
<xsd:documentation>Reference to a STOP POINT.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="StopPointName" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
Name of SCHEDULED STOP POINT. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:element name="StopPointRef" type="StopPointRefStructure">
<xsd:annotation>
<xsd:documentation>Reference to a SCHEDULED STOP POINT.</xsd:documentation>
<xsd:documentation>Reference to a STOP POINT.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="StopPointName" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>Name of SCHEDULED STOP POINT.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group name="StopPointInSequenceGroup">
<xsd:annotation>
<xsd:documentation>
Elements identifying an ordered visit to a SCHEDULED STOP POINT within a SERVICE PATTERN.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="StopPointRef"/>
<xsd:element minOccurs="0" ref="VisitNumber"/>
<xsd:element minOccurs="0" ref="Order"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="StopPointName">
<xsd:annotation>
<xsd:documentation>
Name of SCHEDULED STOP POINT. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:annotation>
<xsd:documentation>
Elements identifying Ordered visit to a stop within calling sequence of a SERVICE PATTERN.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" ref="StopPointRef"/>
<xsd:element minOccurs="0" ref="VisitNumber"/>
<xsd:element minOccurs="0" ref="Order"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="StopPointName">
<xsd:annotation>
<xsd:documentation>
Name of SCHEDULED STOP POINT. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:simpleType name="VisitNumberType">
<xsd:annotation>
<xsd:documentation>Type for Stop Visit.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:positiveInteger"/>
</xsd:simpleType>
<xsd:simpleType name="ClearDownCodeType">
<xsd:annotation>
<xsd:documentation>
Identifier of a Stop for Direct Cleardown. Suitable for radio transmission over a constrained bandwidth channel. This may be a separate code from the full stop identifier.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN"/>
</xsd:simpleType>
<xsd:complexType name="ClearDownRefStructure">
<xsd:annotation>
<xsd:documentation>Reference Cleardown identifier of a stop.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="ClearDownCodeType"/>
</xsd:simpleContent>
</xsd:complexType>
<!-- ===== STOP AREA==================================================== -->
<xsd:simpleType name="StopAreaCodeType">
<xsd:annotation>
<xsd:documentation>Type for identifier of a STOP AREA.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN"/>
</xsd:simpleType>
<xsd:complexType name="StopAreaRefStructure">
<xsd:annotation>
<xsd:documentation>Reference to a STOP AREA.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="StopAreaCodeType"/>
</xsd:simpleContent>
</xsd:complexType>
<!--====Mode Enumerations =================================================================== -->
<xsd:simpleType name="QuayCodeType">
<xsd:annotation>
<xsd:documentation>
Type for identifier of a QUAY (Platform, Bay, etc).
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN"/>
</xsd:simpleType>
<xsd:complexType name="QuayRefStructure">
<xsd:annotation>
<xsd:documentation>Type for reference to a QUAY.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="QuayCodeType"/>
</xsd:simpleContent>
</xsd:complexType>
<!-- ==== MonitopringPoint (LOGICAL DISPLAY) ==================================================== -->
<xsd:simpleType name="MonitoringCode">
<xsd:annotation>
<xsd:documentation>
Identifier of a monitoring point. May correspond to a SCHEDULED STOP POINT or represent a group of Stops other Timing Points (i.e. LOGICAL DISPLAY)
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN"/>
</xsd:simpleType>
<xsd:complexType name="MonitoringRefStructure">
<xsd:annotation>
<xsd:documentation>
Type for reference to a monitoring point (LOGICAL DISPLAY).
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="MonitoringCode"/>
</xsd:simpleContent>
</xsd:complexType>
<!-- ====Stop Properties====================================================== -->
<xsd:element default="true" name="TimingPoint" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether the stop is a TIMING POINT. Times for stops that are not timing points are sometimes interpolated crudely from the timing points, and may represent a lower level of accuracy. Default is 'true'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="false" name="VehicleAtStop" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether VEHICLE is currently at stop. Default is false (xml default added from SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<!-- === CONNECTION link ====================================================== -->
<xsd:simpleType name="ConnectionLinkCodeType">
<xsd:annotation>
<xsd:documentation>Type for identifier of a CONNECTION link</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN"/>
</xsd:simpleType>
<xsd:element name="ConnectionLinkRef" type="ConnectionLinkRefStructure">
<xsd:annotation>
<xsd:documentation>Reference to a CONNECTION link</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="ConnectionLinkRefStructure">
<xsd:annotation>
<xsd:documentation>Type for reference to a CONNECTION link</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="ConnectionLinkCodeType"/>
</xsd:simpleContent>
</xsd:complexType>
<!--====Mode Enumerations =================================================================== -->
<xsd:simpleType name="VehicleModesEnumeration">
<xsd:annotation>
<xsd:documentation>
MODEs of transport applicable to timetabled public transport.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="air"/>
<xsd:enumeration value="bus"/>
<xsd:enumeration value="coach"/>
<xsd:enumeration value="ferry"/>
<xsd:enumeration value="metro"/>
<xsd:enumeration value="rail"/>
<xsd:enumeration value="tram"/>
<xsd:enumeration value="underground"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="ContinuousModesEnumeration">
<xsd:annotation>
<xsd:documentation>
MODEs of transport applicable to private and non-timetabled transport.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="walk"/>
<xsd:enumeration value="car"/>
<xsd:enumeration value="taxi"/>
<xsd:enumeration value="cycle"/>
<xsd:enumeration value="drt"/>
<xsd:enumeration value="movingWalkway"/>
<xsd:enumeration value="through"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="AllModesEnumeration">
<xsd:annotation>
<xsd:documentation>Union of VEHICLE and continuous MODEs.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="walk"/>
<xsd:enumeration value="car"/>
<xsd:enumeration value="taxi"/>
<xsd:enumeration value="cycle"/>
<xsd:enumeration value="drt"/>
<xsd:enumeration value="movingWalkway"/>
<xsd:enumeration value="through"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType name="ModesStructure">
<xsd:annotation>
<xsd:documentation>Type for Transport MODEs.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="Mode" type="AllModesEnumeration">
<xsd:annotation>
<xsd:documentation>
A method of transportation such as bus, rail, etc.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute default="false" name="Exclude" type="xsd:boolean" use="optional">
<xsd:annotation>
<xsd:documentation>if true, listed modes to be excluded from list.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
<!-- =====JOURNEY PATTERN identfiers=============================================================== -->
<xsd:simpleType name="JourneyPatternCodeType">
<xsd:annotation>
<xsd:documentation>Type for identifier of a JOURNEY PATTERN.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN"/>
</xsd:simpleType>
<xsd:complexType name="JourneyPatternRefStructure">
<xsd:annotation>
<xsd:documentation>Type for refrence to a JOURNEY PATTERN.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="JourneyPatternCodeType"/>
</xsd:simpleContent>
</xsd:complexType>
<xsd:element name="JourneyPatternRef" type="JourneyPatternRefStructure">
<xsd:annotation>
<xsd:documentation>Reference to a JOURNEY PATTERN.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group name="JourneyPatternRefGroup">
<xsd:annotation>
<xsd:documentation>
Elements describing the ROUTE and JOURNEY PATTERN Identfiers associated with a journey.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence/>
</xsd:group>
<!-- ==== LINE and DESTINATION elements======================================================== -->
<xsd:group name="JourneyPatternInfoGroup">
<xsd:annotation>
<xsd:documentation>
Elements describing the LINE, ROUTE and DIRECTION of a VEHICLE JOURNEYwhich are derived from the JOURNEY PATTERN associated with the journey.
Values for these elements can be specified on an annual schedule and will be inherited, unless overriden, onto the production timetable and then onto the individul dated VEHICLE JOURNEYs of the timetable. Each monitored journey takes its values from the dated VEHICLE JOURNEY that it follows. The absence of a value on an entity at a given level indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="JourneyPatternRef" type="JourneyPatternRefStructure">
<xsd:annotation>
<xsd:documentation>
Identifier of JOURNEY PATTERN that journey follows.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="JourneyPatternName" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>Name of Joruney Pattern</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="VehicleMode" type="VehicleModesEnumeration">
<xsd:annotation>
<xsd:documentation>A means of transportation such as bus, rail, etc.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="RouteRef" type="RouteRefStructure">
<xsd:annotation>
<xsd:documentation>Identifier of ROUTE that journey follows.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="PublishedLineName">
<xsd:annotation>
<xsd:documentation>
Name or Number by which the LINE is known to the public. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="GroupOfLinesRef" type="GroupOfLinesRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to a GROUP OF LINEs to which journey belongs. SIRI 2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="DirectionName" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
Description of the DIRECTION. May correspond to a DESTINATION DISPLAY. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="ExternalLineRef" type="LineRefStructure">
<xsd:annotation>
<xsd:documentation>
Alternative identifier of LINE that an external system may associate with journey.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:group name="LineIdentityGroup">
<xsd:annotation>
<xsd:documentation>Elements for identifying a LINE and DIRECTION.</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 LINE DIRECTION DIRECTION, typically outward or return.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:complexType name="LineDirectionStructure">
<xsd:annotation>
<xsd:documentation>Type for LINEand DIRECTION.</xsd:documentation>
</xsd:annotation>
<xsd:group ref="LineDirectionGroup"/>
</xsd:complexType>
<xsd:group name="LineDirectionGroup">
<xsd:annotation>
<xsd:documentation>Elements for a LINE and DIRECTION.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="LineRef" type="LineRefStructure">
<xsd:annotation>
<xsd:documentation>Line Reference.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="DirectionRef" type="DirectionRefStructure">
<xsd:annotation>
<xsd:documentation>Direction Reference.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:simpleType name="LineRefCodeType">
<xsd:annotation>
<xsd:documentation>Type for identifier of a LINE</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN"/>
</xsd:simpleType>
<xsd:element name="LineRef" type="LineRefStructure">
<xsd:annotation>
<xsd:documentation>Reference to a LINE.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="LineRefStructure">
<xsd:annotation>
<xsd:documentation>Type for reference to a LINE.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="LineRefCodeType"/>
</xsd:simpleContent>
</xsd:complexType>
<xsd:group name="PublishedLineGroup">
<xsd:annotation>
<xsd:documentation>
Elements describing the LINEand DESTINATION of a journey. Values for these elements can be specified on an annual schedule and will be inherited, unless overriden, onto the production timetable and then onto the individul dated VEHICLE JOURNEYs of the timetable. Each real-time journey takes its values from the dated VEHICLE JOURNEY that it follows. The absence of a value on an entity at a given level indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" ref="PublishedLineName"/>
<xsd:element minOccurs="0" name="DestinationName" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
Description of the destination stop (vehicle signage), if different from the that in timetable - the DESTINATION DISPLAY. Can be overwritten section by section by the entry in an individual CALL.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:annotation>
<xsd:documentation>
Name or Number by which the LINEis known to the public.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:simpleType name="GroupOfLinesCodeType">
<xsd:annotation>
<xsd:documentation>Identifier of a GROUP OF LINEs</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN"/>
</xsd:simpleType>
<xsd:complexType name="GroupOfLinesRefStructure">
<xsd:annotation>
<xsd:documentation>Reference to a GROUP OF LINEs</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="GroupOfLinesCodeType"/>
</xsd:simpleContent>
</xsd:complexType>
<!-- ====Route related elements============================================================== -->
<xsd:simpleType name="RouteCodeType">
<xsd:annotation>
<xsd:documentation>Type for identifier of a Route.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN"/>
</xsd:simpleType>
<xsd:element name="RouteName" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
Description of route by which it can be recogniozed.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="RouteRefStructure">
<xsd:annotation>
<xsd:documentation>Reference to a Route (Transmodel)</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="RouteCodeType"/>
</xsd:simpleContent>
</xsd:complexType>
<xsd:simpleType name="DirectionCodeType">
<xsd:annotation>
<xsd:documentation>Identifier of a DIRECTION.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN"/>
</xsd:simpleType>
<xsd:complexType name="DirectionRefStructure">
<xsd:annotation>
<xsd:documentation>Reference to a DIRECTION.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="DirectionCodeType"/>
</xsd:simpleContent>
</xsd:complexType>
<xsd:simpleType name="RouteLinkCodeType">
<xsd:annotation>
<xsd:documentation>Identifier of a ROUTE LINk.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN"/>
</xsd:simpleType>
<xsd:complexType name="RouteLinkRefStructure">
<xsd:annotation>
<xsd:documentation>Reference to a ROUTE LINk.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="RouteLinkCodeType"/>
</xsd:simpleContent>
</xsd:complexType>
<!-- ====Place Related elements============================================================== -->
<xsd:simpleType name="DestinationCodeType">
<xsd:annotation>
<xsd:documentation>Type for identifier of a DESTINATION.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN"/>
</xsd:simpleType>
<xsd:complexType name="JourneyPlaceRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to a PLACE visited by a VEHICLE JOURNEY.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="xsd:NMTOKEN"/>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="PlaceNameStructure">
<xsd:annotation>
<xsd:documentation>
Names of VIA points, used to help identify the LINE, for example, Luton to Luton via Sutton. Currently 3 in VDV. Should only be included if the detail level was requested.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="PlaceRef" type="JourneyPlaceRefStructure">
<xsd:annotation>
<xsd:documentation>Reference to a TOPOGRAPHIC PLACE.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="PlaceName" type="NaturalLanguagePlaceNameStructure">
<xsd:annotation>
<xsd:documentation>Names of place used to help identify the LINE.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="PlaceShortName" type="NaturalLanguagePlaceNameStructure">
<xsd:annotation>
<xsd:documentation>
Short name of TOPOGRAPHIC PLACE. Should only be included if the detail level was requested.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<!-- ======================================================================= -->
<xsd:simpleType name="VehicleCodeType">
<xsd:annotation>
<xsd:documentation>Identifier of a VEHICLE.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN"/>
</xsd:simpleType>
<xsd:complexType name="VehicleRefStructure">
<xsd:annotation>
<xsd:documentation>Reference to a VEHICLE.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="VehicleCodeType"/>
</xsd:simpleContent>
</xsd:complexType>
<xsd:element name="VehicleRef" type="VehicleRefStructure">
<xsd:annotation>
<xsd:documentation>Reference to a VEHICLE.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:simpleType name="OccupancyEnumeration">
<xsd:annotation>
<xsd:documentation>Passenger load status of a VEHICLE.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="full"/>
<xsd:enumeration value="seatsAvailable"/>
<xsd:enumeration value="standingAvailable"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="DriverCodeType">
<xsd:annotation>
<xsd:documentation>Identifier of a DRIVER</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN"/>
</xsd:simpleType>
<xsd:complexType name="DriverRefStructure">
<xsd:annotation>
<xsd:documentation>Reference to a DRIVER.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="DriverCodeType"/>
</xsd:simpleContent>
</xsd:complexType>
<!-- ======================================================================= -->
<xsd:complexType name="NoteStructure">
<xsd:annotation>
<xsd:documentation>DataType for a NOTICe.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" ref="SituationRef"/>
<xsd:element minOccurs="0" ref="SituationSimpleRef"/>
<xsd:element minOccurs="0" ref="SituationFullRef"/>
<xsd:element minOccurs="0" name="Note" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>Text annotation that applies to an element.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<!-- ======================================================================= -->
<xsd:simpleType name="InfoChannelCodeType">
<xsd:annotation>
<xsd:documentation>Type for identifier of an Info Channel.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN"/>
</xsd:simpleType>
<xsd:complexType name="InfoChannelRefStructure">
<xsd:annotation>
<xsd:documentation>Type for reference to an Info Channel.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="InfoChannelCodeType"/>
</xsd:simpleContent>
</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/