Namespace: |
|
Content: |
complex, 20 elements |
Defined: |
globally in siri_situationAffects-v2.0.xsd; see XML source |
Includes: |
definitions of 14 elements |
Used: |
at 1 location |
XML Representation Summary |
|||
<...> |
|||
</...> |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Type for information about a VEHICLE affected by an SITUATION.
</xsd:documentation>
<xsd:sequence>
<xsd:element name="VehicleRef" type="VehicleRefStructure">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Reference to a specific VEHICLE affected by an SITUATION.
</xsd:documentation>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="VehicleRegistrationNumberPlate" type="xsd:normalizedString">
<xsd:annotation>
</xsd:element>
<xsd:documentation>Registration plate of VEHICLE</xsd:documentation>
</xsd:annotation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
(Mobile) phone number on which the vehicle can be called
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Internet protocol address of the VEHICLE in form 000.000.000.000
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>Radio address of the VEHICLE</xsd:documentation>
</xsd:annotation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Reference to VEHICLE JOURNEY that VEHICLE is making.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Location where the VEHICLE was when the situation arosse
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>Current Location of the VEHICLE</xsd:documentation>
</xsd:annotation>
<xsd:element minOccurs="0" name="AccessibilityAssessment" type="acsb:AccessibilityAssessmentStructure">
<xsd:annotation>
</xsd:element>
<xsd:documentation>Current Accessibility assessment of vehicle.</xsd:documentation>
</xsd:annotation>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="TrainBlockPart" type="TrainBlockPartStructure">
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
If a VEHICLE JOURNEY is a coupled journey, i.e. comprises several coupled BLOCKparts, there will be a separate delivery for each BLOCKp art and this element will indicate the vehicles that the journey part uses.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Whether the VEHICLE is in traffic congestion. If not, present, not known.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Whether the panic alarm on the VEHICLE is activated. Default is 'false'.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
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:complexType>
|
Type: |
acsb:AccessibilityAssessmentStructure, complex content |
Defined: |
<xsd:element minOccurs="0" name="AccessibilityAssessment" type="acsb:AccessibilityAssessmentStructure">
<xsd:annotation>
<xsd:documentation>Current Accessibility assessment of vehicle.</xsd:documentation>
</xsd:annotation>
</xsd:element>
|
Type: |
BlockRefStructure, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>BLOCK that VEHICLE is running.</xsd:documentation>
</xsd:annotation>
</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: |
LocationStructure, complex content |
Defined: |
<xsd:annotation>
<xsd:documentation>Current Location of the VEHICLE</xsd:documentation>
</xsd:annotation>
</xsd:element>
|
Type: |
ExtensionsStructure, complex content
|
Defined: |
Type: |
FramedVehicleJourneyRefStructure, complex content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Reference to VEHICLE JOURNEY that VEHICLE is making.
</xsd:documentation>
</xsd:element>
|
Type: |
xsd:boolean, predefined, simple content |
Default: |
"false" |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
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:element>
|
Type: |
xsd:boolean, predefined, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Whether the VEHICLE is in traffic congestion. If not, present, not known.
</xsd:documentation>
</xsd:element>
|
Type: |
xsd:boolean, predefined, simple content |
Default: |
"false" |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Whether the panic alarm on the VEHICLE is activated. Default is 'false'.
</xsd:documentation>
</xsd:element>
|
Type: |
xsd:NMTOKEN, predefined, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Internet protocol address of the VEHICLE in form 000.000.000.000
</xsd:documentation>
</xsd:element>
|
Type: |
LocationStructure, complex content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Location where the VEHICLE was when the situation arosse
</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: |
PhoneType, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
(Mobile) phone number on which the vehicle can be called
</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: |
xsd:NMTOKEN, predefined, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>Radio address of the VEHICLE</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: |
TrainBlockPartStructure, complex content |
Defined: |
<xsd:element maxOccurs="unbounded" minOccurs="0" name="TrainBlockPart" type="TrainBlockPartStructure">
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
If a VEHICLE JOURNEY is a coupled journey, i.e. comprises several coupled BLOCKparts, there will be a separate delivery for each BLOCKp art and this element will indicate the vehicles that the journey part uses.
</xsd:documentation>
</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: |
VehicleRefStructure, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Reference to a specific VEHICLE affected by an SITUATION.
</xsd:documentation>
</xsd:element>
|
Type: |
xsd:normalizedString, predefined, simple content |
Defined: |
<xsd:element maxOccurs="unbounded" minOccurs="0" name="VehicleRegistrationNumberPlate" type="xsd:normalizedString">
<xsd:annotation>
<xsd:documentation>Registration plate of VEHICLE</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/
|