complexType "DatedVehicleJourneyStructure"
Namespace:
Content:
complex, 31 elements
Defined:
Includes:
definitions of 3 elements
Used:
XML Representation Summary
<...>
   
Content: 
</...>
Content Model Elements (31):
BlockRef (type BlockRefStructure), Cancellation (type xsd:boolean), CourseOfJourneyRef (type CourseOfJourneyRefStructure), DatedCalls (in DatedVehicleJourney), DatedVehicleJourneyCode (in DatedVehicleJourney), DestinationDisplay (type NaturalLanguageStringStructure), DirectionName (type NaturalLanguageStringStructure), Extensions, ExternalLineRef (type LineRefStructure), ExtraJourney (type xsd:boolean), FirstOrLastJourney (in DatedVehicleJourney), FramedVehicleJourneyRef (type FramedVehicleJourneyRefStructure), GroupOfLinesRef (type GroupOfLinesRefStructure), HeadwayService (type xsd:boolean), JourneyNote, JourneyPatternName (type NaturalLanguageStringStructure), JourneyPatternRef (type JourneyPatternRefStructure), LineNote (in DatedVehicleJourney), Monitored (type xsd:boolean), OperationsContact (type SimpleContactStructure), OperatorRef (type OperatorRefStructure), OriginDisplay (type NaturalLanguageStringStructure), ProductCategoryRef (type ProductCategoryRefStructure), PublicContact (type SimpleContactStructure), PublishedLineName, RouteRef (type RouteRefStructure), ServiceFeatureRef, VehicleFeatureRef (type VehicleFeatureRefStructure), VehicleJourneyName (type NaturalLanguageStringStructure), VehicleJourneyRef, VehicleMode (type VehicleModesEnumeration)
All Direct / Indirect Based Elements (1):
DatedVehicleJourney
Known Usage Locations
Annotation
Type for Planned VEHICLE JOURNEY (Production Timetable Service).
XML Source (see within schema source)
<xsd:complexType name="DatedVehicleJourneyStructure">
<xsd:annotation>
<xsd:documentation>
Type for Planned VEHICLE JOURNEY (Production Timetable Service).
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="DatedVehicleJourneyCode" type="DatedVehicleJourneyCodeType">
<xsd:annotation>
<xsd:documentation>Identifier for a VEHICLE JOURNEY.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group minOccurs="0" ref="TimetableAlterationGroup"/>
<xsd:group ref="JourneyPatternInfoGroup"/>
<xsd:group ref="ServiceInfoGroup"/>
<xsd:group ref="JourneyInfoGroup"/>
<xsd:group ref="DatedServiceInfoGroup"/>
<xsd:group ref="TimetableRealtimeInfoGroup"/>
<xsd:group minOccurs="0" ref="OperationalBlockGroup"/>
<xsd:element name="DatedCalls">
<xsd:annotation>
<xsd:documentation>
Complete sequence of stops along the route path, in calling order.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="2" ref="DatedCall"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element minOccurs="0" ref="Extensions"/>
</xsd:sequence>
</xsd:complexType>
Content Element Detail (all declarations; 31/31)
BlockRef
Type:
BlockRefStructure, simple content
Defined:
BLOCK that VEHICLE is running.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="BlockRef" type="BlockRefStructure">
<xsd:annotation>
<xsd:documentation>BLOCK that VEHICLE is running.</xsd:documentation>
</xsd:annotation>
</xsd:element>

Cancellation
Type:
xsd:boolean, predefined, simple content
Default:
"false"
Defined:
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.
XML Source (see within schema source)
<xsd:element default="false" minOccurs="0" name="Cancellation" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
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:element>

CourseOfJourneyRef
Type:
Defined:
COURSE OF JOURNEY ('Run') that VEHICLE is running.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="CourseOfJourneyRef" type="CourseOfJourneyRefStructure">
<xsd:annotation>
<xsd:documentation>
COURSE OF JOURNEY ('Run') that VEHICLE is running.
</xsd:documentation>
</xsd:annotation>
</xsd:element>

DatedCalls
Type:
anonymous complexType, complex content
Defined:
locally within (this) DatedVehicleJourneyStructure complexType
Complete sequence of stops along the route path, in calling order.
XML Source (see within schema source)
<xsd:element name="DatedCalls">
<xsd:annotation>
<xsd:documentation>
Complete sequence of stops along the route path, in calling order.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="2" ref="DatedCall"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>

DatedVehicleJourneyCode
Type:
Defined:
locally within (this) DatedVehicleJourneyStructure complexType
Identifier for a VEHICLE JOURNEY.
XML Source (see within schema source)
<xsd:annotation>
<xsd:documentation>Identifier for a VEHICLE JOURNEY.</xsd:documentation>
</xsd:annotation>
</xsd:element>

DestinationDisplay
Type:
Defined:
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)
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="DestinationDisplay" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
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:annotation>
</xsd:element>

DirectionName
Type:
Defined:
Description of the DIRECTION. May correspond to a DESTINATION DISPLAY. (Unbounded since SIRI 2.0)
XML Source (see within schema source)
<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>

Extensions
Type:
ExtensionsStructure, complex content
Defined:
by reference within (this) DatedVehicleJourneyStructure complexType
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="Extensions"/>

ExternalLineRef
Type:
LineRefStructure, simple content
Defined:
Alternative identifier of LINE that an external system may associate with journey.
XML Source (see within schema source)
<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>

ExtraJourney
Type:
xsd:boolean, predefined, simple content
Default:
"false"
Defined:
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.
XML Source (see within schema source)
<xsd:element default="false" minOccurs="0" name="ExtraJourney" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
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>

FirstOrLastJourney
Type:
Default:
"unspecified"
Defined:
Whether journey is first or last jouurney of day. +SIRI v2.0
XML Source (see within schema source)
<xsd:element default="unspecified" minOccurs="0" name="FirstOrLastJourney" type="FirstOrLastJourneyEnumeration">
<xsd:annotation>
<xsd:documentation>
Whether journey is first or last jouurney of day. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>

FramedVehicleJourneyRef
Type:
Defined:
Refecence to a VEHICLE JOURNEY framed by the day. SIRI 2.0
XML Source (see within schema source)
<xsd:annotation>
<xsd:documentation>
Refecence to a VEHICLE JOURNEY framed by the day. SIRI 2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>

GroupOfLinesRef
Type:
GroupOfLinesRefStructure, simple content
Defined:
Reference to a GROUP OF LINEs to which journey belongs. SIRI 2.0
XML Source (see within schema source)
<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>

HeadwayService
Type:
xsd:boolean, predefined, simple content
Defined:
Whether this is a Headway Service, that is, one shown as operating at a prescribed interval rather than to a fixed timetable.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="HeadwayService" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
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>

JourneyNote
Type:
Defined:
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="JourneyNote"/>

JourneyPatternName
Type:
Defined:
Name of Joruney Pattern
XML Source (see within schema source)
<xsd:element minOccurs="0" name="JourneyPatternName" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>Name of Joruney Pattern</xsd:documentation>
</xsd:annotation>
</xsd:element>

JourneyPatternRef
Type:
Defined:
Identifier of JOURNEY PATTERN that journey follows.
XML Source (see within schema source)
<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>

LineNote
Type:
Defined:
Additional Text associated with LINE. (Unbounded since SIRI 2.0)
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="LineNote" type="NaturalLanguagePlaceNameStructure">
<xsd:annotation>
<xsd:documentation>
Additional Text associated with LINE. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>

Monitored
Type:
xsd:boolean, predefined, simple content
Default:
"true"
Defined:
Whether VEHICLE JOURNEYs of LINE are normally monitored. Provides a default value for the Monitored element on individual journeys of the timetable.
XML Source (see within schema source)
<xsd:element default="true" minOccurs="0" name="Monitored" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
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:element>

OperationsContact
Type:
SimpleContactStructure, complex content
Defined:
Contact details for use by operational staff. +SIRI v2.0
XML Source (see within schema source)
<xsd:element minOccurs="0" name="OperationsContact" type="SimpleContactStructure">
<xsd:annotation>
<xsd:documentation>
Contact details for use by operational staff. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>

OperatorRef
Type:
OperatorRefStructure, simple content
Defined:
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.
XML Source (see within schema source)
<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>

OriginDisplay
Type:
Defined:
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)
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="OriginDisplay" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
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:annotation>
</xsd:element>

ProductCategoryRef
Type:
Defined:
Product Classification of VEHICLE JOURNEY- subdivides a transport mode. e.g. express, loacl.
XML Source (see within schema source)
<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>

PublicContact
Type:
SimpleContactStructure, complex content
Defined:
Contact details for use by members of public. +SIRI v2.0
XML Source (see within schema source)
<xsd:element minOccurs="0" name="PublicContact" type="SimpleContactStructure">
<xsd:annotation>
<xsd:documentation>
Contact details for use by members of public. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>

PublishedLineName
Type:
Defined:
Name or Number by which the LINE is known to the public. (Unbounded since SIRI 2.0)
XML Source (see within schema source)
<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>

RouteRef
Type:
RouteRefStructure, simple content
Defined:
Identifier of ROUTE that journey follows.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="RouteRef" type="RouteRefStructure">
<xsd:annotation>
<xsd:documentation>Identifier of ROUTE that journey follows.</xsd:documentation>
</xsd:annotation>
</xsd:element>

ServiceFeatureRef
Type:
Defined:
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.
XML Source (see within schema source)
<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>

VehicleFeatureRef
Type:
Defined:
Features of VEHICLE providing journey. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package.
XML Source (see within schema source)
<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>

VehicleJourneyName
Type:
Defined:
For train services with named journeys. Train name, e.g. “West Coast Express”. If omitted: No train name. Inherited property. (Unbounded since SIRI 2.0)
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="VehicleJourneyName" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
For train services with named journeys. Train name, e.g. &#8220;West Coast Express&#8221;. If omitted: No train name. Inherited property. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>

VehicleJourneyRef
Type:
Defined:
XML Source (see within schema source)
<xsd:element ref="VehicleJourneyRef"/>

VehicleMode
Type:
VehicleModesEnumeration, simple content
Defined:
A means of transportation such as bus, rail, etc.
XML Source (see within schema source)
<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>

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/