Namespace: |
|
Content: |
complex, 31 elements |
Defined: |
globally in siri_datedVehicleJourney-v2.0.xsd; see XML source |
Includes: |
definitions of 3 elements |
Used: |
at 1 location |
XML Representation Summary |
|||
<...> |
|||
</...> |
<xsd:annotation>
<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:element>
<xsd:documentation>Identifier for a VEHICLE JOURNEY.</xsd:documentation>
</xsd:annotation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Complete sequence of stops along the route path, in calling order.
</xsd:documentation>
<xsd:complexType>
</xsd:complexType>
</xsd:complexType>
|
Type: |
BlockRefStructure, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>BLOCK that VEHICLE is running.</xsd:documentation>
</xsd:annotation>
</xsd:element>
|
Type: |
xsd:boolean, predefined, simple content |
Default: |
"false" |
Defined: |
<xsd:annotation>
<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:element>
|
Type: |
CourseOfJourneyRefStructure, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
COURSE OF JOURNEY ('Run') that VEHICLE is running.
</xsd:documentation>
</xsd:element>
|
Type: |
anonymous complexType, complex content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Complete sequence of stops along the route path, in calling order.
</xsd:documentation>
<xsd:complexType>
</xsd:complexType>
</xsd:element>
|
Type: |
DatedVehicleJourneyCodeType, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>Identifier for a VEHICLE JOURNEY.</xsd:documentation>
</xsd:annotation>
</xsd:element>
|
Type: |
NaturalLanguageStringStructure, simple content |
Defined: |
<xsd:element maxOccurs="unbounded" minOccurs="0" name="DestinationDisplay" type="NaturalLanguageStringStructure">
<xsd:annotation>
<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>
|
Type: |
NaturalLanguageStringStructure, simple content |
Defined: |
<xsd:element maxOccurs="unbounded" minOccurs="0" name="DirectionName" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Description of the DIRECTION. May correspond to a DESTINATION DISPLAY. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:element>
|
Type: |
ExtensionsStructure, complex content
|
Defined: |
Type: |
LineRefStructure, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Alternative identifier of LINE that an external system may associate with journey.
</xsd:documentation>
</xsd:element>
|
Type: |
xsd:boolean, predefined, simple content |
Default: |
"false" |
Defined: |
<xsd:annotation>
<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:element>
|
Type: |
FirstOrLastJourneyEnumeration, simple content |
Default: |
"unspecified" |
Defined: |
<xsd:element default="unspecified" minOccurs="0" name="FirstOrLastJourney" type="FirstOrLastJourneyEnumeration">
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Whether journey is first or last jouurney of day. +SIRI v2.0
</xsd:documentation>
</xsd:element>
|
Type: |
FramedVehicleJourneyRefStructure, complex content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Refecence to a VEHICLE JOURNEY framed by the day. SIRI 2.0
</xsd:documentation>
</xsd:element>
|
Type: |
GroupOfLinesRefStructure, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Reference to a GROUP OF LINEs to which journey belongs. SIRI 2.0
</xsd:documentation>
</xsd:element>
|
Type: |
xsd:boolean, predefined, simple content |
Defined: |
<xsd:annotation>
<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:element>
|
Type: |
NaturalLanguageStringStructure, simple content
|
Defined: |
Type: |
NaturalLanguageStringStructure, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>Name of Joruney Pattern</xsd:documentation>
</xsd:annotation>
</xsd:element>
|
Type: |
JourneyPatternRefStructure, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Identifier of JOURNEY PATTERN that journey follows.
</xsd:documentation>
</xsd:element>
|
Type: |
NaturalLanguagePlaceNameStructure, simple content |
Defined: |
<xsd:element maxOccurs="unbounded" minOccurs="0" name="LineNote" type="NaturalLanguagePlaceNameStructure">
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Additional Text associated with LINE. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:element>
|
Type: |
xsd:boolean, predefined, simple content |
Default: |
"true" |
Defined: |
<xsd:annotation>
<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:element>
|
Type: |
SimpleContactStructure, complex content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Contact details for use by operational staff. +SIRI v2.0
</xsd:documentation>
</xsd:element>
|
Type: |
OperatorRefStructure, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
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:element>
|
Type: |
NaturalLanguageStringStructure, simple content |
Defined: |
<xsd:element maxOccurs="unbounded" minOccurs="0" name="OriginDisplay" type="NaturalLanguageStringStructure">
<xsd:annotation>
<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>
|
Type: |
ProductCategoryRefStructure, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Product Classification of VEHICLE JOURNEY- subdivides a transport mode. e.g. express, loacl.
</xsd:documentation>
</xsd:element>
|
Type: |
SimpleContactStructure, complex content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Contact details for use by members of public. +SIRI v2.0
</xsd:documentation>
</xsd:element>
|
Type: |
NaturalLanguageStringStructure, simple content
|
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Name or Number by which the LINE is known to the public. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:element>
|
Type: |
RouteRefStructure, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>Identifier of ROUTE that journey follows.</xsd:documentation>
</xsd:annotation>
</xsd:element>
|
Type: |
ServiceFeatureRefStructure, simple content
|
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
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.
</xsd:documentation>
Corresponds to NeTEX TYPE OF SERVICe. </xsd:element>
|
Type: |
VehicleFeatureRefStructure, simple content |
Defined: |
<xsd:element maxOccurs="unbounded" minOccurs="0" name="VehicleFeatureRef" type="VehicleFeatureRefStructure">
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
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:element>
|
Type: |
NaturalLanguageStringStructure, simple content |
Defined: |
<xsd:element maxOccurs="unbounded" minOccurs="0" name="VehicleJourneyName" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
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)
</xsd:documentation>
</xsd:element>
|
Type: |
VehicleJourneyRefStructure, simple content
|
Defined: |
Type: |
VehicleModesEnumeration, simple content |
Defined: |
<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:
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/
|