element <AffectedVehicleJourney> (local)
Namespace:
Type:
Content:
complex, 23 elements
Defined:
XML Representation Summary
<AffectedVehicleJourney>
   
Content: 
</AffectedVehicleJourney>
Content model elements (23):
AccessibilityAssessment (type acsb:AccessibilityAssessmentStructure), BlockRef (type BlockRefStructure), Calls (in AffectedVehicleJourney), DatedVehicleJourneyRef (type DatedVehicleJourneyRefStructure), DestinationAimedArrivalTime (type xsd:dateTime), DestinationDisplayAtOrigin (type NaturalLanguagePlaceNameStructure), Destinations (type AffectedStopPointStructure), DirectionRef (type DirectionRefStructure), Extensions, Facilities (in AffectedVehicleJourney), FramedVehicleJourneyRef (type FramedVehicleJourneyRefStructure), JourneyCondition (in AffectedVehicleJourney), JourneyName (in AffectedVehicleJourney), JourneyParts (in AffectedVehicleJourney), LineRef (type LineRefStructure), Operator (in AffectedVehicleJourney), OriginAimedDepartureTime (type xsd:dateTime), OriginDisplayAtDestination (type NaturalLanguagePlaceNameStructure), Origins (in AffectedVehicleJourney), PublishedLineName, Route (in AffectedVehicleJourney), TrainNumbers (in AffectedVehicleJourney), VehicleJourneyRef (in AffectedVehicleJourney)
Included in content model of elements (1):
VehicleJourneys (in Affects)
Annotation
Journeys affected by the SITUATION.
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" name="AffectedVehicleJourney" type="AffectedVehicleJourneyStructure">
<xsd:annotation>
<xsd:documentation>Journeys affected by the SITUATION.</xsd:documentation>
</xsd:annotation>
</xsd:element>
Content Element Detail (all declarations; 23/23)
AccessibilityAssessment
Type:
Defined:
Accessibility Disruption status ofto JOURNEY, as affected by Situation.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="AccessibilityAssessment" type="acsb:AccessibilityAssessmentStructure">
<xsd:annotation>
<xsd:documentation>
Accessibility Disruption status ofto JOURNEY, as affected by Situation.
</xsd:documentation>
</xsd:annotation>
</xsd:element>

BlockRef
Type:
BlockRefStructure, simple content
Defined:
BLOCK which journey runs. +SIRI 2.0
XML Source (see within schema source)
<xsd:element minOccurs="0" name="BlockRef" type="BlockRefStructure">
<xsd:annotation>
<xsd:documentation>BLOCK which journey runs. +SIRI 2.0</xsd:documentation>
</xsd:annotation>
</xsd:element>

Calls
Type:
anonymous complexType, complex content
Defined:
CALLs making up VEHICLE JOURNEY [equivalent to TPEG pti15 3 stop, 15_5 not-stopping, 15-6 temporary stop route_description_type]
XML Source (see within schema source)
<xsd:element minOccurs="0" name="Calls">
<xsd:annotation>
<xsd:documentation>
CALLs making up VEHICLE JOURNEY [equivalent to TPEG pti15 3 stop, 15_5 not-stopping, 15-6 temporary stop route_description_type]
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="Call" type="AffectedCallStructure"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>

DatedVehicleJourneyRef
Type:
Defined:
Reference to a specific DATED VEHICLE JOURNEY affected by a SITUATION.
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="DatedVehicleJourneyRef" type="DatedVehicleJourneyRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to a specific DATED VEHICLE JOURNEY affected by a SITUATION.
</xsd:documentation>
</xsd:annotation>
</xsd:element>

DestinationAimedArrivalTime
Type:
xsd:dateTime, predefined, simple content
Defined:
Timetabled arrival time of journey at Destination.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="DestinationAimedArrivalTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
Timetabled arrival time of journey at Destination.
</xsd:documentation>
</xsd:annotation>
</xsd:element>

DestinationDisplayAtOrigin
Type:
Defined:
DESTINATION name shown for journey at the origin. Can be Used to identify joruney for user. (+SIRI 2.0)
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="DestinationDisplayAtOrigin" type="NaturalLanguagePlaceNameStructure">
<xsd:annotation>
<xsd:documentation>
DESTINATION name shown for journey at the origin. Can be Used to identify joruney for user. (+SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>

Destinations
Type:
Defined:
Destination SCHEDULED STOP POINTs to which the LINE runs. [equivalent to pti15 2 destination route_description_type]
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="Destinations" type="AffectedStopPointStructure">
<xsd:annotation>
<xsd:documentation>
Destination SCHEDULED STOP POINTs to which the LINE runs. [equivalent to pti15 2 destination route_description_type]
</xsd:documentation>
</xsd:annotation>
</xsd:element>

DirectionRef
Type:
DirectionRefStructure, simple content
Defined:
DIRECTION of LINE in which journey runs.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="DirectionRef" type="DirectionRefStructure">
<xsd:annotation>
<xsd:documentation>DIRECTION of LINE in which journey runs.</xsd:documentation>
</xsd:annotation>
</xsd:element>

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

Facilities
Type:
anonymous complexType, complex content
Defined:
Facilities available for VEHICLE JOURNEY (+SIRI 2.0)
XML Source (see within schema source)
<xsd:element minOccurs="0" name="Facilities">
<xsd:annotation>
<xsd:documentation>
Facilities available for VEHICLE JOURNEY (+SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="AffectedFacility" type="AffectedFacilityStructure">
<xsd:annotation>
<xsd:documentation>
Facililitiy available for VEHICLE JOURNEY (+SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>

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

JourneyCondition
Type:
Defined:
enum Status of service for this Vehicle Journey - TPEG value. Multiple Condtions can be valid at the same time. (+SIRI 2.0)
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="JourneyCondition" type="ServiceConditionEnumeration">
<xsd:annotation>
<xsd:documentation>
enum Status of service for this Vehicle Journey - TPEG value. Multiple Condtions can be valid at the same time. (+SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>

JourneyName
Type:
Defined:
Name of journey affected by a SITUATION. (Unbounded since SIRI 2.0)
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="JourneyName" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
Name of journey affected by a SITUATION. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>

JourneyParts
Type:
anonymous complexType, complex content
Defined:
JOURNEY PARTs making up JOURNEY +SIRIv2.0 e.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="JourneyParts">
<xsd:annotation>
<xsd:documentation>JOURNEY PARTs making up JOURNEY +SIRIv2.0 e.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="JourneyPartInfo" type="JourneyPartInfoStructure">
<xsd:annotation>
<xsd:documentation>Information about Parts of JOURNEY +SIRI v2.0</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>

LineRef
Type:
LineRefStructure, simple content
Defined:
Reference to the LINE of the journey affected by an SITUATION.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="LineRef" type="LineRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to the LINE of the journey affected by an SITUATION.
</xsd:documentation>
</xsd:annotation>
</xsd:element>

Operator
Type:
AffectedOperatorStructure, complex content
Defined:
OPERATOR of LINE affected by SITUATION.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="Operator" type="AffectedOperatorStructure">
<xsd:annotation>
<xsd:documentation>OPERATOR of LINE affected by SITUATION.</xsd:documentation>
</xsd:annotation>
</xsd:element>

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

OriginDisplayAtDestination
Type:
Defined:
DESTINATION name shown for journey at the origin. Can be Used to identify joruney for user. (+SIRI 2.0),
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="OriginDisplayAtDestination" type="NaturalLanguagePlaceNameStructure">
<xsd:annotation>
<xsd:documentation>
DESTINATION name shown for journey at the origin. Can be Used to identify joruney for user. (+SIRI 2.0),
</xsd:documentation>
</xsd:annotation>
</xsd:element>

Origins
Type:
Defined:
Origin SCHEDULED STOP POINTs from which the LINE runs. [equivalent to pti15 1 start_point route_description_type]
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="Origins" type="AffectedStopPointStructure">
<xsd:annotation>
<xsd:documentation>
Origin SCHEDULED STOP POINTs from which the LINE runs. [equivalent to pti15 1 start_point route_description_type]
</xsd:documentation>
</xsd:annotation>
</xsd:element>

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

Route
Type:
AffectedRouteStructure, complex content
Defined:
ROUTE affected by the SITUATION.
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" name="Route" type="AffectedRouteStructure">
<xsd:annotation>
<xsd:documentation>ROUTE affected by the SITUATION.</xsd:documentation>
</xsd:annotation>
</xsd:element>

TrainNumbers
Type:
anonymous complexType, complex content
Defined:
TRAIN NUMBERs for journey. +SIRI v2.0
XML Source (see within schema source)
<xsd:element minOccurs="0" name="TrainNumbers">
<xsd:annotation>
<xsd:documentation>TRAIN NUMBERs for journey. +SIRI v2.0</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="TrainNumberRef" type="TrainNumberRefStructure">
<xsd:annotation>
<xsd:documentation>
TRAIN NUMBER assigned to VEHICLE JOURNEY. +SIRI 2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>

VehicleJourneyRef
Type:
Defined:
Reference to a service VEHICLE JOURNEY affected by a SITUATION.
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" name="VehicleJourneyRef" type="VehicleJourneyRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to a service VEHICLE JOURNEY affected by a SITUATION.
</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/