element <TargetedVehicleJourney> (global)
Namespace:
Type:
Content:
complex, 33 elements
Defined:
Used:
never
XML Representation Summary
<TargetedVehicleJourney>
   
Content: 
</TargetedVehicleJourney>
Content model elements (33):
DestinationAimedArrivalTime (type xsd:dateTime), DestinationDisplayAtOrigin (type NaturalLanguagePlaceNameStructure), DestinationName (type NaturalLanguageStringStructure), DestinationRef, DestinationShortName (type NaturalLanguagePlaceNameStructure), DirectionName (type NaturalLanguageStringStructure), DirectionRef (type DirectionRefStructure), ExternalLineRef (type LineRefStructure), FirstOrLastJourney, FramedVehicleJourneyRef (type FramedVehicleJourneyRefStructure), GroupOfLinesRef (type GroupOfLinesRefStructure), HeadwayService (type xsd:boolean), JourneyNote, JourneyPatternName (type NaturalLanguageStringStructure), JourneyPatternRef (type JourneyPatternRefStructure), LineRef (type LineRefStructure), OperationsContact (type SimpleContactStructure), OperatorRef (type OperatorRefStructure), OriginAimedDepartureTime (type xsd:dateTime), OriginDisplayAtDestination (type NaturalLanguagePlaceNameStructure), OriginName (type NaturalLanguagePlaceNameStructure), OriginRef, OriginShortName (type NaturalLanguagePlaceNameStructure), ProductCategoryRef (type ProductCategoryRefStructure), PublicContact (type SimpleContactStructure), PublishedLineName, RouteRef (type RouteRefStructure), ServiceFeatureRef, TargetedCall, VehicleFeatureRef (type VehicleFeatureRefStructure), VehicleJourneyName (type NaturalLanguageStringStructure), VehicleMode (type VehicleModesEnumeration), Via (type ViaNameStructure)
Annotation
Timetabled VEHICLE JOURNEY.
XML Source (see within schema source)
<xsd:element name="TargetedVehicleJourney" type="TargetedVehicleJourneyStructure">
<xsd:annotation>
<xsd:documentation>Timetabled VEHICLE JOURNEY.</xsd:documentation>
</xsd:annotation>
</xsd:element>
Content Element Detail (all declarations; 33/33)
DestinationAimedArrivalTime
Type:
xsd:dateTime, predefined, simple content
Defined:
Timetabled arrival time at Destination.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="DestinationAimedArrivalTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>Timetabled arrival time at Destination.</xsd:documentation>
</xsd:annotation>
</xsd:element>

DestinationDisplayAtOrigin
Type:
Defined:
DIRECTION name shown for jurney at the origin. +SIRI v2.0
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="DestinationDisplayAtOrigin" type="NaturalLanguagePlaceNameStructure">
<xsd:annotation>
<xsd:documentation>
DIRECTION name shown for jurney at the origin. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>

DestinationName
Type:
Defined:
Description of the destination stop (vehicle signage), 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="DestinationName" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
Description of the destination stop (vehicle signage), 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>

DestinationRef
Type:
DestinationRefStructure, simple content
Defined:
Reference to a DESTINATION.
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="DestinationRef">
<xsd:annotation>
<xsd:documentation>Reference to a DESTINATION.</xsd:documentation>
</xsd:annotation>
</xsd:element>

DestinationShortName
Type:
Defined:
Short name of the DESTINATION.of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as DestinationName. (Unbounded since SIRI 2.0)
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="DestinationShortName" type="NaturalLanguagePlaceNameStructure">
<xsd:annotation>
<xsd:documentation>
Short name of the DESTINATION.of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as DestinationName. (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>

DirectionRef
Type:
DirectionRefStructure, simple content
Defined:
Reference to a DIRECTION, typically outward or return.
XML Source (see within schema source)
<xsd:element name="DirectionRef" type="DirectionRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to a DIRECTION, typically outward or return.
</xsd:documentation>
</xsd:annotation>
</xsd:element>

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>

FirstOrLastJourney
Type:
Default:
"unspecified"
Defined:
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="FirstOrLastJourney"/>

FramedVehicleJourneyRef
Type:
Defined:
A reference to the dated VEHICLE JOURNEY that the VEHICLE is making.
XML Source (see within schema source)
<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>

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

LineRef
Type:
LineRefStructure, simple content
Defined:
Reference to a LINE.
XML Source (see within schema source)
<xsd:element name="LineRef" type="LineRefStructure">
<xsd:annotation>
<xsd:documentation>Reference to a LINE.</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>

OriginAimedDepartureTime
Type:
xsd:dateTime, predefined, simple content
Defined:
Timetabled departure time from Origin.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="OriginAimedDepartureTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>Timetabled departure time from Origin.</xsd:documentation>
</xsd:annotation>
</xsd:element>

OriginDisplayAtDestination
Type:
Defined:
Origin name shown for jourey at the destination +SIRI v2.0
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="OriginDisplayAtDestination" type="NaturalLanguagePlaceNameStructure">
<xsd:annotation>
<xsd:documentation>
Origin name shown for jourey at the destination +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>

OriginName
Type:
Defined:
Name of the origin of the journey. (Unbounded since SIRI 2.0)
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="OriginName" type="NaturalLanguagePlaceNameStructure">
<xsd:annotation>
<xsd:documentation>
Name of the origin of the journey. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>

OriginRef
Type:
JourneyPlaceRefStructure, simple content
Defined:
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="OriginRef"/>

OriginShortName
Type:
Defined:
Short name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as Origin Name.
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="OriginShortName" type="NaturalLanguagePlaceNameStructure">
<xsd:annotation>
<xsd:documentation>
Short name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as Origin Name.
</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>

TargetedCall
Type:
TargetedCallStructure, complex content
Defined:
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="TargetedCall"/>

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>

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>

Via
Type:
ViaNameStructure, complex content
Defined:
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.
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="Via" type="ViaNameStructure">
<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: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/