group "StopArrivalGroup"
Namespace:
http://www.siri.org.uk/siri
Content:
10 elements
Defined:
globally in siri_monitoredVehicleJourney-v2.0.xsd; see XML source
Used:
at 1 location
Complex Content Model
AimedArrivalTime?, (ActualArrivalTime? | ExpectedArrivalTime?), LatestExpectedArrivalTime?, ArrivalStatus?, ArrivalProximityText?, ArrivalPlatformName?, ArrivalBoardingActivity?, ArrivalStopAssignment?, ArrivalOperatorRefs*
Content Model Elements (10):
ActualArrivalTime, AimedArrivalTime, ArrivalBoardingActivity, ArrivalOperatorRefs (type OperatorRefStructure), ArrivalPlatformName, ArrivalProximityText, ArrivalStatus, ArrivalStopAssignment (type StopAssignmentStructure), ExpectedArrivalTime, LatestExpectedArrivalTime (in MonitoredCall)
Known Usage Locations
Annotation
Elements describing the the arrival of a VEHICLE at a stop.
XML Source (see within schema source)
<xsd:group name="StopArrivalGroup">
<xsd:annotation>
<xsd:documentation>
Elements describing the the arrival of a VEHICLE at a stop.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="MonitoredCallArrivalTimesGroup"/>
</xsd:sequence>
</xsd:group>
Content Element Detail (all declarations; 10/10)
ActualArrivalTime
Type:
xsd:dateTime, predefined, simple content
Defined:
by reference within VehicleArrivalTimesGroup group
Observed time of arrival of VEHICLE.
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="ActualArrivalTime">
<xsd:annotation>
<xsd:documentation>Observed time of arrival of VEHICLE.</xsd:documentation>
</xsd:annotation>
</xsd:element>
AimedArrivalTime
Type:
xsd:dateTime, predefined, simple content
Defined:
by reference within VehicleArrivalTimesGroup group
Target arrival time of VEHICLE according to latest working timetable.
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="AimedArrivalTime">
<xsd:annotation>
<xsd:documentation>
Target arrival time of VEHICLE according to latest working timetable.
</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>
ExpectedArrivalTime
Type:
xsd:dateTime, predefined, simple content
Defined:
by reference within VehicleArrivalTimesGroup group
Estimated time of arriival of VEHICLE.
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="ExpectedArrivalTime">
<xsd:annotation>
<xsd:documentation>Estimated time of arriival of VEHICLE.</xsd:documentation>
</xsd:annotation>
</xsd:element>
LatestExpectedArrivalTime
Type:
xsd:dateTime, predefined, simple content
Defined:
locally within MonitoredCallArrivalTimesGroup group
Latest time at which a VEHICLE will arrive at stop. +SIRI v2.0
XML Source (see within schema source)
<xsd:element minOccurs="0" name="LatestExpectedArrivalTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
Latest time at which a VEHICLE will arrive at stop. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</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:
  • 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/