Namespace: |
|
Content: |
complex, 44 elements |
Defined: |
globally in siri_estimatedVehicleJourney-v2.0.xsd; see XML source |
Includes: |
definitions of 3 elements |
Used: |
at 1 location |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Type for Rea-ltime info about a VEHICLE JOURNEY Stop.
</xsd:documentation>
<xsd:sequence>
<xsd:group ref="StopPointInSequenceGroup"/>
</xsd:sequence>
<xsd:choice minOccurs="0">
<xsd:element minOccurs="0" name="ExtraCall" type="xsd:boolean">
</xsd:choice>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This call is additional and unplanned. If omitted: CALL is planned.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This call is a cancellation of a previously announced call.
</xsd:documentation>
</xsd:complexType>
|
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: |
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: |
ArrivalBoardingActivityEnumeration, simple content
|
Default: |
"alighting" |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Nature of boarding and alighting allowed at stop. Default is 'Alighting'.
</xsd:documentation>
</xsd:element>
|
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: |
<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: |
NaturalLanguageStringStructure, simple content
|
Defined: |
Type: |
CallStatusEnumeration, simple content
|
Defined: |
Type: |
StopAssignmentStructure, 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: |
xsd:boolean, predefined, simple content |
Default: |
"false" |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Whether this is a Hail and Ride Stop. Default is 'false'.
</xsd:documentation>
</xsd:element>
|
Type: |
NaturalLanguageStringStructure, simple content |
Defined: |
<xsd:element maxOccurs="unbounded" minOccurs="0" name="CallNote" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>Text annotation that applies to this CALL.</xsd:documentation>
</xsd:annotation>
</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: |
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: |
NaturalLanguageStringStructure, simple content |
Defined: |
<xsd:element maxOccurs="unbounded" minOccurs="0" name="DestinationDisplay" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Destination to show for the VEHICLE at the specific stop (vehicle signage), if different to the Destination Name for the full journey.
</xsd:documentation>
</xsd:element>
|
Type: |
DistanceType, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Distance of VEHICLE from stop of CALL as measured along ROUTE track. Only shown if detail level is 'calls' or higher. Positive value denotes distance before stop. +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. Used for passenger announcements. Passengers must be at boarding point by this time to be sure of catching VEHICLE. i.e. "Vehicle will not leave before this time" - may be revised from original aimed time. +SIRI v2.0
</xsd:documentation>
</xsd:element>
|
Type: |
PredictionQualityStructure, complex content |
Defined: |
<xsd:element minOccurs="0" name="ExpectedArrivalPredictionQuality" type="PredictionQualityStructure">
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Prediction quality, either as approximate level, or more quantitayive 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: |
Type: |
PredictionQualityStructure, complex content |
Defined: |
<xsd:element minOccurs="0" name="ExpectedDeparturePredictionQuality" type="PredictionQualityStructure">
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Prediction quality, either as approximate level, or more quantitayive 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, most likely taking into account all control actions such as waiting.
</xsd:documentation>
</xsd:element>
|
Type: |
PositiveDurationType, simple content
|
Defined: |
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: |
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: |
FacilityChangeStructure, complex content
|
Defined: |
Type: |
FacilityConditionStructure, complex content
|
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Information about a change of Equipment availabilti at stop or on vehicle that may affect access or use.
</xsd:documentation>
</xsd:element>
|
Type: |
xsd:nonNegativeInteger, predefined, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Count of stops along SERVICE PATTERN between current position of VEHICLE and stop of CALL as measured along ROUTE track. Only shown if detail level is 'calls' or higher. +SIRI v2.0.
</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: |
NaturalLanguageStringStructure, simple content |
Defined: |
<xsd:element maxOccurs="unbounded" minOccurs="0" name="OriginDisplay" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Origin to show for the VEHICLE at the specific stop (vehicle signage), if different to the Origin Name for the full journey. (+Siri 2.0)
</xsd:documentation>
</xsd:element>
|
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: |
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. So if servcie decides not to wait may leave earler than expected departure time +SIRI v2.0.
</xsd:documentation>
</xsd:element>
|
Type: |
xsd:boolean, predefined, simple content |
Default: |
"false" |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Whether Vehicle stops only if requested explicitly by passenger. Default is 'false'.
</xsd:documentation>
</xsd:element>
|
Type: |
SituationRefStructure, complex content
|
Defined: |
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: |
xsd:boolean, predefined, simple content
|
Default: |
"true" |
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/
|