Namespace: |
|
Content: |
20 elements |
Defined: |
globally in siri_targetedVehicleJourney-v2.0.xsd; see XML source |
Includes: |
definitions of 4 elements |
Used: |
at 1 location |
<xsd:annotation>
<xsd:documentation>Elements for a targeted call.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="StopPointRef" type="StopPointRefStructure">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Reference to a SCHEDULED STOP POINT. Normally this will omitted as will be the same as the monitoring point.
</xsd:documentation>
</xsd:group>
|
Type: |
xsd:dateTime, predefined, simple content
|
Defined: |
Type: |
xsd:dateTime, predefined, simple content
|
Defined: |
Type: |
PositiveDurationType, simple content
|
Defined: |
Type: |
xsd:dateTime, predefined, simple content
|
Defined: |
Type: |
ArrivalBoardingActivityEnumeration, simple content
|
Default: |
"alighting" |
Defined: |
Type: |
OperatorRefStructure, simple content |
Defined: |
<xsd:element maxOccurs="unbounded" minOccurs="0" name="ArrivalOperatorRefs" type="OperatorRefStructure">
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
OPERATORs of of servcie up until arrival.. May change for departure. +SIRI v2.0.
</xsd:documentation>
</xsd:element>
|
Type: |
NaturalLanguageStringStructure, simple content
|
Defined: |
Type: |
PlannedStopAssignmentStructure, complex content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Assignment of arrival of Scheduled STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure +SIRI v2.0.
</xsd:documentation>
</xsd:element>
|
Type: |
DepartureBoardingActivityEnumeration, simple content
|
Default: |
"boarding" |
Defined: |
Type: |
OperatorRefStructure, simple content |
Defined: |
<xsd:element maxOccurs="unbounded" minOccurs="0" name="DepartureOperatorRefs" type="OperatorRefStructure">
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
OPERATORs of of service for departure and onwards.. May change from that for arrival. +SIRI v2.0.
</xsd:documentation>
</xsd:element>
|
Type: |
NaturalLanguageStringStructure, simple content
|
Defined: |
Type: |
PlannedStopAssignmentStructure, complex content |
Defined: |
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: |
xsd:positiveInteger, predefined, simple content
|
Defined: |
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: |
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: |
StopPointRefStructure, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Reference to a SCHEDULED STOP POINT. Normally this will omitted as will be the same as the monitoring point.
</xsd:documentation>
</xsd:element>
|
Type: |
xsd:boolean, predefined, simple content
|
Default: |
"true" |
Defined: |
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: |
VisitNumberType, simple content
|
Defined: |
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/
|