Namespace: |
|
Type: |
|
Content: |
complex, 20 elements |
Defined: |
globally in siri_estimatedVehicleJourney-v2.0.xsd; see XML source |
Used: |
at 1 location |
XML Representation Summary |
|||
<RecordedCall> |
|||
</RecordedCall> |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Ordered sequence of SCHEDULED STOP POINTs called at by the VEHICLE JOURNEY If IsCompleteStopSequence is false, may be just those stops that are altered.
</xsd:documentation>
</xsd:element>
|
Type: |
xsd:dateTime, predefined, simple content
|
Defined: |
Type: |
xsd:dateTime, predefined, simple content
|
Defined: |
<xsd:annotation>
<xsd:documentation>Estimated time of departure of VEHICLE.</xsd:documentation>
</xsd:annotation>
</xsd:element>
|
Type: |
PositiveDurationType, simple content
|
Defined: |
Type: |
xsd:dateTime, predefined, simple content
|
Defined: |
Type: |
xsd:dateTime, predefined, simple content
|
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Target departure time of VEHICLE according to latest working timetable.
</xsd:documentation>
</xsd:element>
|
Type: |
PositiveDurationType, simple content
|
Defined: |
Type: |
NaturalLanguageStringStructure, simple content
|
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicel to arrive at.Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is
</xsd:documentation>
(i) any arrival platform on any related dated timetable element, (ii) any departure platform name on this estimated element; (iii) any departure platform name on any related dated timetable CALL. </xsd:element>
|
Type: |
xsd:boolean, predefined, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
This call is a cancellation of a previously announced call.
</xsd:documentation>
</xsd:element>
|
Type: |
NaturalLanguageStringStructure, simple content
|
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Departure QUAY ( Bay or platform) name. Defaulted taken from from planned timetable..
</xsd:documentation>
</xsd:element>
|
Type: |
xsd:dateTime, predefined, simple content
|
Defined: |
Type: |
xsd:dateTime, predefined, simple content
|
Defined: |
<xsd:annotation>
<xsd:documentation>Estimated time of departure of VEHICLE.</xsd:documentation>
</xsd:annotation>
</xsd:element>
|
Type: |
PositiveDurationType, simple content
|
Defined: |
Type: |
ExtensionsStructure, complex content
|
Defined: |
Type: |
xsd:boolean, predefined, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
This call is additional and unplanned. If omitted: CALL is planned.
</xsd:documentation>
</xsd:element>
|
Type: |
OccupancyEnumeration, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
How full the bus is at the stop. If omitted: Passenger load is unknown.
</xsd:documentation>
</xsd:element>
|
Type: |
xsd:positiveInteger, predefined, simple content
|
Defined: |
Type: |
xsd:boolean, predefined, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Whether the prediction for the specific stop is considered to be of a useful accuracy or not. Default is 'false', i.e. prediction is not known to be inaccurate. {DOUBLE NEGATIVE IS BAD _ BETTER AS PredictionAccurate. Default is 'true'?]. If prediction is degraded, e.g. because in congestion, used to 9indicate a lowered quality of data. Inherited property. {SHOULD THIS JUST BE THE SPECIFIC InCongestion INDICATOR INSTEAD, OR IS IT MORE GENERAL]
</xsd:documentation>
</xsd:element>
|
Type: |
NaturalLanguageStringStructure, simple content
|
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Name of SCHEDULED STOP POINT. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:element>
|
Type: |
StopPointRefStructure, simple content
|
Defined: |
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/
|