element <OnwardCall> (local)
Namespace:
http://www.siri.org.uk/siri
Type:
OnwardCallStructure
Content:
complex, 33 elements
Defined:
locally within OnwardCallsStructure complexType in siri_journey-v2.0.xsd; see XML source
XML Representation Summary
<OnwardCall>
   
Content: 
</OnwardCall>
Content model elements (33):
AimedArrivalTime, AimedDepartureTime, AimedHeadwayInterval, AimedLatestPassengerAccessTime, ArrivalBoardingActivity, ArrivalOperatorRefs (type OperatorRefStructure), ArrivalPlatformName, ArrivalProximityText, ArrivalStatus, ArrivalStopAssignment (type StopAssignmentStructure), DepartureBoardingActivity, DepartureOperatorRefs (type OperatorRefStructure), DeparturePlatformName, DepartureProximityText, DepartureStatus, DepartureStopAssignment (type StopAssignmentStructure), DistanceFromStop (type DistanceType), EarliestExpectedDepartureTime (type xsd:dateTime), ExpectedArrivalPredictionQuality (type PredictionQualityStructure), ExpectedArrivalTime, ExpectedDeparturePredictionQuality (type PredictionQualityStructure), ExpectedDepartureTime, ExpectedHeadwayInterval, ExpectedLatestPassengerAccessTime, Extensions, NumberOfStopsAway (type xsd:nonNegativeInteger), Order, ProvisionalExpectedDepartureTime (type xsd:dateTime), StopPointName, StopPointRef, TimingPoint, VehicleAtStop, VisitNumber
Included in content model of elements (1):
OnwardCalls (type OnwardCallsStructure)
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" name="OnwardCall" type="OnwardCallStructure"/>
Content Element Detail (all declarations; 33/33)
AimedArrivalTime
Type:
xsd:dateTime, predefined, simple content
Defined:
by reference within OnwardVehicleArrivalTimesGroup group
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="AimedArrivalTime"/>
AimedDepartureTime
Type:
xsd:dateTime, predefined, simple content
Defined:
by reference within OnwardVehicleDepartureTimesGroup group
Target departure time of VEHICLE according to latest working timetable.
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="AimedDepartureTime">
<xsd:annotation>
<xsd:documentation>
Target departure time of VEHICLE according to latest working timetable.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
AimedHeadwayInterval
Type:
PositiveDurationType, simple content
Defined:
by reference within HeadwayIntervalGroup group
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="AimedHeadwayInterval"/>
AimedLatestPassengerAccessTime
Type:
xsd:dateTime, predefined, simple content
Defined:
by reference within PassengerDepartureTimesGroup group
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
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="AimedLatestPassengerAccessTime">
<xsd:annotation>
<xsd:documentation>
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:annotation>
</xsd:element>
ArrivalBoardingActivity
Type:
ArrivalBoardingActivityEnumeration, simple content
Default:
"alighting"
Defined:
by reference within MonitoredStopArrivalStatusGroup group
Nature of boarding and alighting allowed at stop. Default is 'Alighting'.
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="ArrivalBoardingActivity">
<xsd:annotation>
<xsd:documentation>
Nature of boarding and alighting allowed at stop. Default is 'Alighting'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
ArrivalOperatorRefs
Type:
OperatorRefStructure, simple content
Defined:
locally within MonitoredStopArrivalStatusGroup group
OPERATORs of of servcie up until arrival.. May change for departure. +SIRI v2.0.
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="ArrivalOperatorRefs" type="OperatorRefStructure">
<xsd:annotation>
<xsd:documentation>
OPERATORs of of servcie up until arrival.. May change for departure. +SIRI v2.0.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
ArrivalPlatformName
Type:
NaturalLanguageStringStructure, simple content
Defined:
by reference within MonitoredStopArrivalStatusGroup group
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 (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.
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="ArrivalPlatformName">
<xsd:annotation>
<xsd:documentation>
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
(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:documentation>
</xsd:annotation>
</xsd:element>
ArrivalProximityText
Type:
NaturalLanguageStringStructure, simple content
Defined:
by reference within MonitoredStopArrivalStatusGroup group
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="ArrivalProximityText"/>
ArrivalStatus
Type:
CallStatusEnumeration, simple content
Defined:
by reference within MonitoredStopArrivalStatusGroup group
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="ArrivalStatus"/>
ArrivalStopAssignment
Type:
StopAssignmentStructure, complex content
Defined:
locally within MonitoredStopArrivalStatusGroup group
Assignment of arrival of Scheduled STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure +SIRI v2.0.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="ArrivalStopAssignment" type="StopAssignmentStructure">
<xsd:annotation>
<xsd:documentation>
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:annotation>
</xsd:element>
DepartureBoardingActivity
Type:
DepartureBoardingActivityEnumeration, simple content
Default:
"boarding"
Defined:
by reference within MonitoredStopDepartureStatusGroup group
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="DepartureBoardingActivity"/>
DepartureOperatorRefs
Type:
OperatorRefStructure, simple content
Defined:
locally within MonitoredStopDepartureStatusGroup group
OPERATORs of of service for departure and onwards.. May change from that for arrival. +SIRI v2.0.
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="DepartureOperatorRefs" type="OperatorRefStructure">
<xsd:annotation>
<xsd:documentation>
OPERATORs of of service for departure and onwards.. May change from that for arrival. +SIRI v2.0.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
DeparturePlatformName
Type:
NaturalLanguageStringStructure, simple content
Defined:
by reference within MonitoredStopDepartureStatusGroup group
Departure QUAY ( Bay or platform) name. Defaulted taken from from planned timetable..
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="DeparturePlatformName">
<xsd:annotation>
<xsd:documentation>
Departure QUAY ( Bay or platform) name. Defaulted taken from from planned timetable..
</xsd:documentation>
</xsd:annotation>
</xsd:element>
DepartureProximityText
Type:
NaturalLanguageStringStructure, simple content
Defined:
by reference within MonitoredStopDepartureStatusGroup group
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="DepartureProximityText"/>
DepartureStatus
Type:
CallStatusEnumeration, simple content
Defined:
by reference within MonitoredStopDepartureStatusGroup group
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="DepartureStatus"/>
DepartureStopAssignment
Type:
StopAssignmentStructure, complex content
Defined:
locally within MonitoredStopDepartureStatusGroup group
Assignments of departure platfiorm for Scheduled STOP POINT to a physical QUAY. +SIRI v2.0.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="DepartureStopAssignment" type="StopAssignmentStructure">
<xsd:annotation>
<xsd:documentation>
Assignments of departure platfiorm for Scheduled STOP POINT to a physical QUAY. +SIRI v2.0.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
DistanceFromStop
Type:
DistanceType, simple content
Defined:
locally within StopProximityGroup group
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.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="DistanceFromStop" type="DistanceType">
<xsd:annotation>
<xsd:documentation>
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:annotation>
</xsd:element>
EarliestExpectedDepartureTime
Type:
xsd:dateTime, predefined, simple content
Defined:
locally within OnwardVehicleDepartureTimesGroup group
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
XML Source (see within schema source)
<xsd:element minOccurs="0" name="EarliestExpectedDepartureTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
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:annotation>
</xsd:element>
ExpectedArrivalPredictionQuality
Type:
PredictionQualityStructure, complex content
Defined:
locally within OnwardVehicleArrivalTimesGroup group
Prediction quality, either as approximate level, or more quantitayive percentile range of predictions will fall within a given range of times. +SIRI v2.0
XML Source (see within schema source)
<xsd:element minOccurs="0" name="ExpectedArrivalPredictionQuality" type="PredictionQualityStructure">
<xsd:annotation>
<xsd:documentation>
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:annotation>
</xsd:element>
ExpectedArrivalTime
Type:
xsd:dateTime, predefined, simple content
Defined:
by reference within OnwardVehicleArrivalTimesGroup group
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="ExpectedArrivalTime"/>
ExpectedDeparturePredictionQuality
Type:
PredictionQualityStructure, complex content
Defined:
locally within OnwardVehicleDepartureTimesGroup group
Prediction quality, either as approximate level, or more quantitayive percentile range of predictions will fall within a given range of times. +SIRI v2.0
XML Source (see within schema source)
<xsd:element minOccurs="0" name="ExpectedDeparturePredictionQuality" type="PredictionQualityStructure">
<xsd:annotation>
<xsd:documentation>
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:annotation>
</xsd:element>
ExpectedDepartureTime
Type:
xsd:dateTime, predefined, simple content
Defined:
by reference within OnwardVehicleDepartureTimesGroup group
Estimated time of departure of VEHICLE, most likely taking into account all control actions such as waiting.
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="ExpectedDepartureTime">
<xsd:annotation>
<xsd:documentation>
Estimated time of departure of VEHICLE, most likely taking into account all control actions such as waiting.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
ExpectedHeadwayInterval
Type:
PositiveDurationType, simple content
Defined:
by reference within HeadwayIntervalGroup group
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="ExpectedHeadwayInterval"/>
ExpectedLatestPassengerAccessTime
Type:
xsd:dateTime, predefined, simple content
Defined:
by reference within PassengerDepartureTimesGroup group
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
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="ExpectedLatestPassengerAccessTime">
<xsd:annotation>
<xsd:documentation>
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:annotation>
</xsd:element>
Extensions
Type:
ExtensionsStructure, complex content
Defined:
by reference within OnwardCallStructure complexType
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="Extensions"/>
NumberOfStopsAway
Type:
xsd:nonNegativeInteger, predefined, simple content
Defined:
locally within StopProximityGroup group
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.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="NumberOfStopsAway" type="xsd:nonNegativeInteger">
<xsd:annotation>
<xsd:documentation>
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:annotation>
</xsd:element>
Order
Type:
xsd:positiveInteger, predefined, simple content
Defined:
by reference within ContextualisedStopPointInSequenceGroup group
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="Order"/>
ProvisionalExpectedDepartureTime
Type:
xsd:dateTime, predefined, simple content
Defined:
locally within OnwardVehicleDepartureTimesGroup group
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.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="ProvisionalExpectedDepartureTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
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:annotation>
</xsd:element>
StopPointName
Type:
NaturalLanguageStringStructure, simple content
Defined:
by reference within ContextualisedStopPointInSequenceGroup group
Name of SCHEDULED STOP POINT. (Unbounded since SIRI 2.0)
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="StopPointName">
<xsd:annotation>
<xsd:documentation>
Name of SCHEDULED STOP POINT. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
StopPointRef
Type:
StopPointRefStructure, simple content
Defined:
by reference within ContextualisedStopPointInSequenceGroup group
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="StopPointRef"/>
TimingPoint
Type:
xsd:boolean, predefined, simple content
Default:
"true"
Defined:
by reference within OnwardCallStructure complexType
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="TimingPoint"/>
VehicleAtStop
Type:
xsd:boolean, predefined, simple content
Default:
"false"
Defined:
by reference within OnwardCallStructure complexType
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="VehicleAtStop"/>
VisitNumber
Type:
VisitNumberType, simple content
Defined:
by reference within ContextualisedStopPointInSequenceGroup group
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="VisitNumber"/>
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:
  • To configure the generated documentation so much as you want. Thanks to our template technology, it was possible to support > 400 template parameters, which work the same as "options" of ordinary doc-generators. The parameters are organized in nested groups, which form a parameter tree. Most of them have their default values calculated dynamically from a few primary parameters. So, you'll never need to specify all of them. That will give you swift and effective control over the generated content!
  • To use certain features disabled in the free mode (such as the full documenting of substitution groups).
  • To select only the initial, imported, included, redefined XML schemas to be documented or only those directly specified by name.
  • To include only XML schema components specified by name.
  • To document local element components both globally and locally (similar to attributes).
  • To allow/suppress unification of local elements by type.
  • To enable/disable reproducing of namespace prefixes.
  • To use PlainDoc.tpl main template to generate all the XML schema documentation in a signle-file form as both HTML and incredible quality RTF output.
  • To format your annotations with XHTML tags and reproduce that formatting both in HTML and RTF output.
  • To insert images in your annotations using XHTML <img> tags (supported both in HTML and RTF output).
  • To remove this very advertisement text!
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/