All Element Summary (local elements unified by type) |
||||||||||
Advertised (type xsd:boolean) |
Whether the SERVICE JOURNEY INTERCHANGE is advertised as a connection.
|
|||||||||
|
||||||||||
Cancellation (type xsd:boolean) |
|
|||||||||
Identifier of CONNECTION LINk.
|
||||||||||
|
||||||||||
Complete sequence of stops along the route path, in calling order.
|
||||||||||
Complete sequence of stops along the route path, in calling order.
|
||||||||||
A planned VEHICLE JOURNEY taking place on a particular date.
|
||||||||||
Identifier for a VEHICLE JOURNEY.
|
||||||||||
Default time (Duration) needeed to traverse SERVICE JOURNEY INTERCHANGE from feeder to distributor.
|
||||||||||
|
||||||||||
Link to Interchange stop from which the distributor journey departs.
|
||||||||||
Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY INTERCHANGE takes place.
|
||||||||||
|
||||||||||
DistributorOrder (type xsd:positiveInteger) |
|
|||||||||
|
||||||||||
Reference to a (dated) distributor VEHICLE JOURNEY.
|
||||||||||
|
||||||||||
ExtraJourney (type xsd:boolean) |
|
|||||||||
|
||||||||||
|
||||||||||
|
||||||||||
Whether journey is first or last jouurney of day.
|
||||||||||
|
||||||||||
Time needeed by a traveller whis is familiar with SERVICE JOURNEY INTERCHANGE to traverse it.
|
||||||||||
Information on any planned feeder connections.
|
||||||||||
Guaranteed (type xsd:boolean) |
Whether the SERVICE JOURNEY INTERCHANGE is guaranteed.
|
|||||||||
HeadwayService (type xsd:boolean) |
|
|||||||||
Time needeed by a traveller wos is mobility impaired to traverse SERVICE JOURNEY INTERCHANGE.
|
||||||||||
|
||||||||||
Additional Text associated with LINE.
|
||||||||||
MaximumAutomaticWaitTime (type xsd:duration) |
Maximum automatic wait time that Distributor will wait for Feeder for INTERCHANGE.
|
|||||||||
MaximumTransferTime (type xsd:duration) |
Maximum transfer duration for INTERCHANGE.
|
|||||||||
MaximumWaitTime (type xsd:duration) |
Maximum time that Distributor will wait for Feeder for INTERCHANGE.
|
|||||||||
MinimumTransferTime (type xsd:duration) |
Minimum transfer duration for INTERCHANGE.
|
|||||||||
Monitored (type xsd:boolean) |
|
|||||||||
Time needeed by a traveller whis is not familiar with SERVICE JOURNEY INTERCHANGE to traverse it.
|
||||||||||
|
||||||||||
StandardTransferTime (type xsd:duration) |
Standard transfer duration for INTERCHANGE.
|
|||||||||
StandardWaitTime (type xsd:duration) |
Standard wait time for INTERCHANGE.
|
|||||||||
StaySeated (type xsd:boolean) |
Whether the passenger can remain in VEHICLE (i.e.
|
|||||||||
Information on any planned distributor connections (deprecated from SIRI V2.0 ... see 2 next attributes)
|
||||||||||
Information on any planned distributor connections.
|
Complex Type Summary |
||||||||||||
A planned SERVICE JOURNEY INTERCHANGE between two journeys.
|
||||||||||||
Connection between two stops within a connection area.
|
||||||||||||
Type for Planned VEHICLE JOURNEY Stop (Production Timetable Service).
|
||||||||||||
Type for Planned VEHICLE JOURNEY (Production Timetable Service).
|
||||||||||||
A planned SERVICE JOURNEY INTERCHANGE from a journey.
|
||||||||||||
A planned SERVICE JOURNEY INTERCHANGE between two journeys.
|
||||||||||||
Planned Connection between two VEHICLE JOURNEYs.
|
||||||||||||
A planned SERVICE JOURNEY INTERCHANGE to a journey.
|
Simple Type Summary |
||||||
Nature of Interchange management.
|
Element Group Summary |
||||||||||
Times for making SERVICE JOURNEY INTERCHANGE.
|
||||||||||
General info elements that apply to all journeys of timetable version unless overriden.
|
||||||||||
Properties of SERVICE JOURNEY INTERCHANGE.
|
||||||||||
Time Elements for SERVICE JOURNEY INTERCHANGE.
|
||||||||||
Elements for INTERCHANGE TRANSFER duration.
|
||||||||||
Elements for INTERCHANGE WAIT TIME.
|
||||||||||
If the journey is an alteration to a timetable, indicates the original journey, and the nature of the difference.
|
||||||||||
Additional descriptive properties of service.
|
<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSpy v2011 rel. 2 sp1 (x64) (http://www.altova.com) by Christophe Duquesne (Dryade) -->
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" id="siri_datedVehicleJourney" 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>
</xsd:annotation>
<Metadata xmlns="http://www.govtalk.gov.uk/CM/gms-xs">
</xsd:appinfo>
<Aggregation>main schema</Aggregation>
</Metadata>
<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>
</Date>
Name Space changes
<Date>
<Modified>2008-03-26</Modified>
</Date>
Add wrapper tag for Line DIRECTION to help binding to Axis
<Date>
<Modified>2008-11-17</Modified>
</Date>
Revise to support substitution groups
<Date>
<Modified>2011-04-18</Modified>
</Date>
- siri_productionTimetable_service.xsd Type on request ValidiyPeriod start and end should be datetime not time ..
- Change to ClosedTimestampRange instead of ClosedTimeRange. Fix Subscription request to be an element and have extensions . <Date>
<Modified>2011-01-19</Modified>
</Date>
SIRI 1.3 Drop use of As Flat Groups for DatedCalls.
<Date>
<Modified>2012-03-23</Modified>
</Date>
Factor out fropm ProductionTimetable package
+SIRI v2.0 Add ServiceJourneyInterchange (i.e. Monitored Connection) [VDV] Add additional times to TargetedServiceInterchange MinimumTransferTime, MaximimTransferTime, StandardTransferTime, MaximumAUtomaticWaitTime, StandardWaitTime. [VDV] Add Public and Contact Details to JourneyInfo [VDV] Add AimedLatestPassengerAccessTime to TargetedCall <Date>
<Modified>2013-02-11</Modified>
</Date>
SIRI v2.0 Modified ServiceJourneyInterchange SIRI:PT
<Description>
<p>
</Description>
SIRI is a European CEN standard for the exchange of Public Transport real-time information.
</p>
<p>
This sub-schema describes the Production Timetable Service.
</p>
<Format>
<MediaType>text/xml</MediaType>
</Format>
<Syntax>http://www.w3.org/2001/XMLSchema</Syntax>
<Description>XML schema, W3C Recommendation 2001</Description>
<Identifier>
{http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_datedVehicleJourney.xsd
</Identifier>
<Language>[ISO 639-2/B] ENG</Language>
<Publisher>Kizoom, 109-123 Clifton Street, London EC4A 4LD</Publisher>
<Relation>
<Requires>
</Relation>
http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey-v2.0.xsd
</Requires>
<Rights>
Unclassified
</Rights>
<Copyright>CEN, VDV, RTIG 2004-2012</Copyright>
<Source>
<ul>
</Source>
<li>
</ul>
Derived from the VDV, RTIG XML and Trident standards.
</li>
<Status>Version 2.0 Draft</Status>
<Subject>
<Category>
</Subject>
Arts, recreation and travel, Tourism, Travel (tourism), Transport,
</Category>
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 <Project>CEN TC278 WG3 SG7</Project>
<Title>
SIRI_PT XML schema. Service Interface for Real-time Information. Production Timetable Service.
</Title>
<Type>Standard</Type>
<!-- ======================================================================= -->
<!-- ======================================================================= -->
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
A planned VEHICLE JOURNEY taking place on a particular date.
</xsd:documentation>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
Type for Planned VEHICLE JOURNEY (Production Timetable Service).
</xsd:documentation>
<xsd:sequence>
<xsd:element name="DatedVehicleJourneyCode" type="DatedVehicleJourneyCodeType">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
</xsd:complexType>
Complete sequence of stops along the route path, in calling order.
</xsd:documentation>
<xsd:annotation>
</xsd:group>
<xsd:documentation>
</xsd:annotation>
General info elements that apply to all journeys of timetable version unless overriden.
</xsd:documentation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="OriginDisplay" type="NaturalLanguageStringStructure">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Description of the origin stop (vehicle signage) to show on vehicle, Can be overwritten for a journey, and then also section by section by the entry in an Individual Call. (+SIRI 2.0)
</xsd:documentation>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="DestinationDisplay" type="NaturalLanguageStringStructure">
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Description of the destination stop (vehicle signage) to show on vehicle, Can be overwritten for a journey, and then also section by section by the entry in an Individual Call. (Unbounded since SIRI 2.0)
</xsd:documentation>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="LineNote" type="NaturalLanguagePlaceNameStructure">
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Additional Text associated with LINE. (Unbounded since SIRI 2.0)
</xsd:documentation>
<xsd:element default="unspecified" minOccurs="0" name="FirstOrLastJourney" type="FirstOrLastJourneyEnumeration">
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Whether journey is first or last jouurney of day. +SIRI v2.0
</xsd:documentation>
<xsd:annotation>
</xsd:group>
<xsd:documentation>
</xsd:annotation>
If the journey is an alteration to a timetable, indicates the original journey, and the nature of the difference.
</xsd:documentation>
<xsd:sequence>
<xsd:choice minOccurs="0">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:choice>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:choice>
<xsd:element default="false" minOccurs="0" name="ExtraJourney" type="xsd:boolean">
</xsd:choice>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Whether this journey is an addition to the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to false: the journey is not an addition.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Whether this journey is a deletion of a journey in the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': Journey is not a deletion.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:group>
<xsd:sequence>
<xsd:element minOccurs="0" name="HeadwayService" type="xsd:boolean">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Whether this is a Headway Service, that is, one shown as operating at a prescribed interval rather than to a fixed timetable.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Whether VEHICLE JOURNEYs of LINE are normally monitored. Provides a default value for the Monitored element on individual journeys of the timetable.
</xsd:documentation>
<!-- ======================================================================= -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
A planned SERVICE JOURNEY INTERCHANGE between two journeys. +SIRI v2.0
</xsd:documentation>
<xsd:sequence>
<xsd:element minOccurs="0" name="InterchangeCode" type="InterchangeCodeType">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY INTERCHANGE takes place. +SIRI v2.0
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
SCHEDULED STOP POINT at which feeder journey arrives. +SIRI v2.0
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
SCHEDULED STOP POINT at which distributor journet departs. +SIRI v2.0
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN.
</xsd:documentation>
<!-- ======================================================================= -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
A planned SERVICE JOURNEY INTERCHANGE from a journey. +SIRI v2.0
</xsd:documentation>
<xsd:complexContent>
<xsd:restriction base="AbstractServiceJourneyInterchangeStructure">
</xsd:complexContent>
<xsd:sequence>
</xsd:restriction>
<xsd:element minOccurs="0" name="InterchangeCode" type="InterchangeCodeType">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY INTERCHANGE takes place. +SIRI v2.0
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
SCHEDULED STOP POINT at which feeder journey arrives. +SIRI v2.0
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN.
</xsd:documentation>
<xsd:element maxOccurs="0" minOccurs="0" name="DistributorRef" type="ConnectingJourneyRefStructure">
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="0" minOccurs="0" name="DistributorDepartureStopRef" type="StopPointRefStructure">
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
SCHEDULED STOP POINT at which distributor journet departs. +SIRI v2.0
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN.
</xsd:documentation>
<!-- ======================================================================= -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
A planned SERVICE JOURNEY INTERCHANGE to a journey. +SIRI v2.0
</xsd:documentation>
<xsd:complexContent>
<xsd:restriction base="AbstractServiceJourneyInterchangeStructure">
</xsd:complexContent>
<xsd:sequence>
</xsd:restriction>
<xsd:element minOccurs="0" name="InterchangeCode" type="InterchangeCodeType">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY INTERCHANGE takes place. +SIRI v2.0
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
SCHEDULED STOP POINT at which feeder journey arrives. +SIRI v2.0
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
SCHEDULED STOP POINT at which distributor journet departs. +SIRI v2.0
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN.
</xsd:documentation>
<!-- ======================================================================= -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
A planned SERVICE JOURNEY INTERCHANGE between two journeys. +SIRI v2.0
</xsd:documentation>
<xsd:complexContent>
<xsd:restriction base="AbstractServiceJourneyInterchangeStructure">
</xsd:complexContent>
<xsd:sequence>
</xsd:restriction>
<xsd:element minOccurs="0" name="InterchangeCode" type="InterchangeCodeType">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY INTERCHANGE takes place. +SIRI v2.0
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
SCHEDULED STOP POINT at which feeder journey arrives. +SIRI v2.0
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
SCHEDULED STOP POINT at which distributor journet departs. +SIRI v2.0
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN.
</xsd:documentation>
<!-- ======================================================================= -->
<xsd:annotation>
</xsd:annotation>
</xsd:group>
<xsd:sequence>
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:group>
<xsd:sequence>
<xsd:element minOccurs="0" name="StandardTransferTime" type="xsd:duration">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:group>
<xsd:sequence>
<xsd:element minOccurs="0" name="StandardWaitTime" type="xsd:duration">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Maximum time that Distributor will wait for Feeder for INTERCHANGE. SIRI v1.0
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Maximum automatic wait time that Distributor will wait for Feeder for INTERCHANGE. +SIRI v2.0
</xsd:documentation>
<!-- ==== CALL =========================================-->
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Complete sequence of stops along the route path, in calling order.
</xsd:documentation>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
Type for Planned VEHICLE JOURNEY Stop (Production Timetable Service).
</xsd:documentation>
<xsd:sequence>
<xsd:group ref="StopPointInSequenceGroup"/>
</xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="CallNote" type="NaturalLanguageStringStructure">
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<!-- The FacilityChangeElement has been removed here in Siri 1.1, but it is still available at the same place through the AimedCallGroup->DisruptionGroup
(DisruptionGroup has been added to AimedCallGroup) <xsd:element ref="FacilityChangeElement" minOccurs="0"/> --> <xsd:element maxOccurs="unbounded" minOccurs="0" name="TargetedInterchange" type="TargetedInterchangeStructure">
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Information on any planned distributor connections (deprecated from SIRI V2.0 ... see 2 next attributes)
</xsd:documentation>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="FromServiceJourneyInterchange" type="FromServiceJourneyInterchangeStructure">
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="ToServiceJourneyInterchange" type="ToServiceJourneyInterchangeStructure">
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Information on any planned distributor connections. SIRI 2.0
</xsd:documentation>
<!-- ==== INTERCHANGE =========================================-->
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:sequence>
<xsd:sequence>
</xsd:sequence>
<xsd:element minOccurs="0" name="InterchangeCode" type="InterchangeCodeType">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:choice>
<xsd:element name="DistributorConnectionLinkRef" type="ConnectionLinkRefStructure">
</xsd:choice>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY INTERCHANGE takes place.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Link to Interchange stop from which the distributor journey departs. If omitted: the distributor journey stop is the same as the feeder journey stop, i.e. that of theh dated call.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
For implementations for which Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then Order can be used to associate the Order as well if useful for translation.
</xsd:documentation>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
Connection between two stops within a connection area. Used within the context of one or other end.
</xsd:documentation>
<xsd:sequence>
<xsd:element minOccurs="0" name="ConnectionLinkCode" type="ConnectionLinkCodeType">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:group>
<xsd:sequence>
<xsd:element minOccurs="0" name="DefaultDuration" type="PositiveDurationType">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Default time (Duration) needeed to traverse SERVICE JOURNEY INTERCHANGE from feeder to distributor.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Time needeed by a traveller whis is familiar with SERVICE JOURNEY INTERCHANGE to traverse it. If absent, use DefaultDuration.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Time needeed by a traveller whis is not familiar with SERVICE JOURNEY INTERCHANGE to traverse it. If absent, use DefaultDuration and a standard weighting.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Time needeed by a traveller wos is mobility impaired to traverse SERVICE JOURNEY INTERCHANGE. If absent, use DefaultDuration and a standard impaired travel speed.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:group>
<xsd:sequence>
<xsd:element default="false" minOccurs="0" name="StaySeated" type="xsd:boolean">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Whether the passenger can remain in VEHICLE (i.e. BLOCKlinking). Default is 'false': the passenger must change vehicles for this connection.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Whether the SERVICE JOURNEY INTERCHANGE is guaranteed. Default is 'false'; SERVICE JOURNEY INTERCHANGE is not guaranteed.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Whether the SERVICE JOURNEY INTERCHANGE is advertised as a connection. Default is 'false'.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:simpleType>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="Planned">
</xsd:restriction>
<xsd:annotation>
</xsd:enumeration>
<xsd:documentation>
</xsd:annotation>
Interchange is considered a possible connection between journeys.
</xsd:documentation>
<xsd:enumeration value="Advertised">
<xsd:annotation>
</xsd:enumeration>
<xsd:documentation>
</xsd:annotation>
Interchange is advertised to public as a possible connection between journeys.
</xsd:documentation>
<xsd:enumeration value="Controlled">
<xsd:annotation>
</xsd:enumeration>
<xsd:documentation>
</xsd:annotation>
Interchange is actively managed as a possible connection between journeys and passengers are informed of real-time alterations.
</xsd:documentation>
<xsd:enumeration value="Guaranteed">
<xsd:annotation>
</xsd:enumeration>
<xsd:documentation>
</xsd:annotation>
Interchange is actively managed as a possible connection between journeys and distributor may be delayed in order to make a transfer possible.
</xsd:documentation>
<!-- ======================================================================= -->
</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:
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/
|