Namespace: |
|
Type: |
|
Content: |
complex, 23 elements |
Defined: |
XML Representation Summary |
|||
<AffectedVehicleJourney> |
|||
</AffectedVehicleJourney> |
<xsd:element maxOccurs="unbounded" name="AffectedVehicleJourney" type="AffectedVehicleJourneyStructure">
<xsd:annotation>
<xsd:documentation>Journeys affected by the SITUATION.</xsd:documentation>
</xsd:annotation>
</xsd:element>
|
Type: |
acsb:AccessibilityAssessmentStructure, complex content |
Defined: |
<xsd:element minOccurs="0" name="AccessibilityAssessment" type="acsb:AccessibilityAssessmentStructure">
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Accessibility Disruption status ofto JOURNEY, as affected by Situation.
</xsd:documentation>
</xsd:element>
|
Type: |
BlockRefStructure, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>BLOCK which journey runs. +SIRI 2.0</xsd:documentation>
</xsd:annotation>
</xsd:element>
|
Type: |
anonymous complexType, complex content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
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:complexType>
<xsd:sequence>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
|
Type: |
DatedVehicleJourneyRefStructure, simple content |
Defined: |
<xsd:element maxOccurs="unbounded" minOccurs="0" name="DatedVehicleJourneyRef" type="DatedVehicleJourneyRefStructure">
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Reference to a specific DATED VEHICLE JOURNEY affected by a SITUATION.
</xsd:documentation>
</xsd:element>
|
Type: |
xsd:dateTime, predefined, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Timetabled arrival time of journey at Destination.
</xsd:documentation>
</xsd:element>
|
Type: |
NaturalLanguagePlaceNameStructure, simple content |
Defined: |
<xsd:element maxOccurs="unbounded" minOccurs="0" name="DestinationDisplayAtOrigin" type="NaturalLanguagePlaceNameStructure">
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
DESTINATION name shown for journey at the origin. Can be Used to identify joruney for user. (+SIRI 2.0)
</xsd:documentation>
</xsd:element>
|
Type: |
AffectedStopPointStructure, complex content |
Defined: |
<xsd:element maxOccurs="unbounded" minOccurs="0" name="Destinations" type="AffectedStopPointStructure">
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Destination SCHEDULED STOP POINTs to which the LINE runs. [equivalent to pti15 2 destination route_description_type]
</xsd:documentation>
</xsd:element>
|
Type: |
DirectionRefStructure, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>DIRECTION of LINE in which journey runs.</xsd:documentation>
</xsd:annotation>
</xsd:element>
|
Type: |
ExtensionsStructure, complex content
|
Defined: |
Type: |
anonymous complexType, complex content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Facilities available for VEHICLE JOURNEY (+SIRI 2.0)
</xsd:documentation>
<xsd:complexType>
<xsd:sequence>
</xsd:complexType>
<xsd:element maxOccurs="unbounded" name="AffectedFacility" type="AffectedFacilityStructure">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Facililitiy available for VEHICLE JOURNEY (+SIRI 2.0)
</xsd:documentation>
</xsd:element>
|
Type: |
FramedVehicleJourneyRefStructure, complex content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Refercence to a VEHICLE JOURENY framed by the day. SIRI 2.0
</xsd:documentation>
</xsd:element>
|
Type: |
ServiceConditionEnumeration, simple content |
Defined: |
<xsd:element maxOccurs="unbounded" minOccurs="0" name="JourneyCondition" type="ServiceConditionEnumeration">
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
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:element>
|
Type: |
NaturalLanguageStringStructure, simple content |
Defined: |
<xsd:element maxOccurs="unbounded" minOccurs="0" name="JourneyName" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Name of journey affected by a SITUATION. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:element>
|
Type: |
anonymous complexType, complex content |
Defined: |
<xsd:annotation>
<xsd:documentation>JOURNEY PARTs making up JOURNEY +SIRIv2.0 e.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
</xsd:complexType>
<xsd:element maxOccurs="unbounded" name="JourneyPartInfo" type="JourneyPartInfoStructure">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>Information about Parts of JOURNEY +SIRI v2.0</xsd:documentation>
</xsd:annotation>
</xsd:element>
|
Type: |
LineRefStructure, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Reference to the LINE of the journey affected by an SITUATION.
</xsd:documentation>
</xsd:element>
|
Type: |
AffectedOperatorStructure, complex content |
Defined: |
<xsd:annotation>
<xsd:documentation>OPERATOR of LINE affected by SITUATION.</xsd:documentation>
</xsd:annotation>
</xsd:element>
|
Type: |
xsd:dateTime, predefined, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>Timetabled departure tme of journey from Origin.</xsd:documentation>
</xsd:annotation>
</xsd:element>
|
Type: |
NaturalLanguagePlaceNameStructure, simple content |
Defined: |
<xsd:element maxOccurs="unbounded" minOccurs="0" name="OriginDisplayAtDestination" type="NaturalLanguagePlaceNameStructure">
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
DESTINATION name shown for journey at the origin. Can be Used to identify joruney for user. (+SIRI 2.0),
</xsd:documentation>
</xsd:element>
|
Type: |
AffectedStopPointStructure, complex content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Origin SCHEDULED STOP POINTs from which the LINE runs. [equivalent to pti15 1 start_point route_description_type]
</xsd:documentation>
</xsd:element>
|
Type: |
NaturalLanguageStringStructure, simple content
|
Defined: |
Type: |
AffectedRouteStructure, complex content |
Defined: |
<xsd:annotation>
<xsd:documentation>ROUTE affected by the SITUATION.</xsd:documentation>
</xsd:annotation>
</xsd:element>
|
Type: |
anonymous complexType, complex content |
Defined: |
<xsd:annotation>
<xsd:documentation>TRAIN NUMBERs for journey. +SIRI v2.0</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
</xsd:complexType>
<xsd:element maxOccurs="unbounded" name="TrainNumberRef" type="TrainNumberRefStructure">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
TRAIN NUMBER assigned to VEHICLE JOURNEY. +SIRI 2.0
</xsd:documentation>
</xsd:element>
|
Type: |
VehicleJourneyRefStructure, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Reference to a service VEHICLE JOURNEY affected by a SITUATION.
</xsd:documentation>
</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/
|