Namespace: |
|
Content: |
14 elements |
Defined: |
globally in siri_monitoredVehicleJourney-v2.0.xsd; see XML source |
Used: |
at 1 location |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Elements describing the the departure of a VEHICLE from a stop.
</xsd:documentation>
<xsd:sequence>
</xsd:sequence>
</xsd:group>
|
Type: |
xsd:dateTime, predefined, simple content
|
Defined: |
<xsd:annotation>
<xsd:documentation>Observed time of departure of VEHICLE from stop.</xsd:documentation>
</xsd:annotation>
</xsd:element>
|
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: |
xsd:dateTime, predefined, simple content
|
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Target Latest time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times as itmay include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data) If absent assume to be the same as Earliest expected departure time, +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: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Departure QUAY ( Bay or platform) name. Defaulted taken from from planned timetable..
</xsd:documentation>
</xsd:element>
|
Type: |
NaturalLanguageStringStructure, simple content
|
Defined: |
Type: |
CallStatusEnumeration, simple content
|
Defined: |
Type: |
StopAssignmentStructure, complex content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Assignments of departure platfiorm for Scheduled STOP POINT to a physical QUAY. +SIRI v2.0.
</xsd:documentation>
</xsd:element>
|
Type: |
xsd:dateTime, predefined, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Earliest time at which VEHICLE may leave the stop. Used to secure connections. Passengers must be at boarding point by this time to be sure of catching VEHICLE. +SIRI v2.0
</xsd:documentation>
</xsd:element>
|
Type: |
PredictionQualityStructure, complex content |
Defined: |
<xsd:element minOccurs="0" name="ExpectedDeparturePredictionQuality" type="PredictionQualityStructure">
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Prediction quality, either as approcimate level, or more quantitatyive percentile range of predictions will fall within a given range of times. +SIRI v2.0
</xsd:documentation>
</xsd:element>
|
Type: |
xsd:dateTime, predefined, simple content
|
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Estimated time of departure of VEHICLE from stop. May include waiting time. For people on a VEHICLE this is the time that would normally be shown.
</xsd:documentation>
</xsd:element>
|
Type: |
xsd:dateTime, predefined, simple content
|
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Expected Latest time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times as it may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data) If absent assume to be the same as Earliest expected departure time, +SIRI v2.0
</xsd:documentation>
</xsd:element>
|
Type: |
xsd:dateTime, predefined, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Expected departure time of VEHICLE without waiting time due to operational actions. For people at stop this would normally be shown if different from Expected Departure time. +SIRI v2.0.
</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/
|