group "StopMonitoringTopicGroup"
Namespace:
http://www.siri.org.uk/siri
Content:
8 elements
Defined:
globally in siri_stopMonitoring_service.xsd; see XML source
Includes:
definitions of 8 elements
Used:
at 2 locations
Complex Content Model
PreviewInterval?, StartTime?, MonitoringRef, OperatorRef?, LineRef?, DirectionRef?, DestinationRef?, StopVisitTypes?
Content Model Elements (8):
DestinationRef (type DestinationRefStructure), DirectionRef (type DirectionRefStructure), LineRef (type LineRefStructure), MonitoringRef (type MonitoringRefStructure), OperatorRef (type OperatorRefStructure), PreviewInterval (type PositiveDurationType), StartTime (type xsd:dateTime), StopVisitTypes (type StopVisitTypeEnumeration)
Known Usage Locations
Annotation
Parameters that specify the content to be returned.
XML Source (see within schema source)
<xsd:group name="StopMonitoringTopicGroup">
<xsd:annotation>
<xsd:documentation>
Parameters that specify the content to be returned.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="PreviewInterval" type="PositiveDurationType">
<xsd:annotation>
<xsd:documentation>
Forward duration for which Visits should be included, that is, interval before predicted arrival at the stop for which to include Visits: only journeys which will arrive or depart within this time span will be returned.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="StartTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
Start time for PreviewInterval. If absent, then current time is assumed.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="MonitoringRef" type="MonitoringRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to Monitoring Point(s) about which data is requested. May be a STOP POINT, timing point, or a group of points under a single reference.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="OperatorRef" type="OperatorRefStructure">
<xsd:annotation>
<xsd:documentation>
Filter the results to include only Stop Visits for VEHICLEs run by the specified OPERATOR.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="LineRef" type="LineRefStructure">
<xsd:annotation>
<xsd:documentation>
Filter the results to include only Stop Visits for VEHICLEs for the given LINE.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="DirectionRef" type="DirectionRefStructure">
<xsd:annotation>
<xsd:documentation>
Filter the results to include only Stop Visits for vehicles running in a specific relative DIRECTION, for example, "inbound" or "outbound". (Direction does not specify a destination.)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="DestinationRef" type="DestinationRefStructure">
<xsd:annotation>
<xsd:documentation>
Filter the results to include only journeys to the DESTINATION of the journey.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="all" minOccurs="0" name="StopVisitTypes" type="StopVisitTypeEnumeration">
<xsd:annotation>
<xsd:documentation>
Whether to include arrival Visits, departure Visits, or all. Default is 'all'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
Content Element Detail (all declarations; 8/8)
DestinationRef
Type:
DestinationRefStructure, simple content
Defined:
locally within (this) StopMonitoringTopicGroup group
Filter the results to include only journeys to the DESTINATION of the journey.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="DestinationRef" type="DestinationRefStructure">
<xsd:annotation>
<xsd:documentation>
Filter the results to include only journeys to the DESTINATION of the journey.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
DirectionRef
Type:
DirectionRefStructure, simple content
Defined:
locally within (this) StopMonitoringTopicGroup group
Filter the results to include only Stop Visits for vehicles running in a specific relative DIRECTION, for example, "inbound" or "outbound". (Direction does not specify a destination.)
XML Source (see within schema source)
<xsd:element minOccurs="0" name="DirectionRef" type="DirectionRefStructure">
<xsd:annotation>
<xsd:documentation>
Filter the results to include only Stop Visits for vehicles running in a specific relative DIRECTION, for example, "inbound" or "outbound". (Direction does not specify a destination.)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
LineRef
Type:
LineRefStructure, simple content
Defined:
locally within (this) StopMonitoringTopicGroup group
Filter the results to include only Stop Visits for VEHICLEs for the given LINE.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="LineRef" type="LineRefStructure">
<xsd:annotation>
<xsd:documentation>
Filter the results to include only Stop Visits for VEHICLEs for the given LINE.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
MonitoringRef
Type:
MonitoringRefStructure, simple content
Defined:
locally within (this) StopMonitoringTopicGroup group
Reference to Monitoring Point(s) about which data is requested. May be a STOP POINT, timing point, or a group of points under a single reference.
XML Source (see within schema source)
<xsd:element name="MonitoringRef" type="MonitoringRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to Monitoring Point(s) about which data is requested. May be a STOP POINT, timing point, or a group of points under a single reference.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
OperatorRef
Type:
OperatorRefStructure, simple content
Defined:
locally within (this) StopMonitoringTopicGroup group
Filter the results to include only Stop Visits for VEHICLEs run by the specified OPERATOR.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="OperatorRef" type="OperatorRefStructure">
<xsd:annotation>
<xsd:documentation>
Filter the results to include only Stop Visits for VEHICLEs run by the specified OPERATOR.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
PreviewInterval
Type:
PositiveDurationType, simple content
Defined:
locally within (this) StopMonitoringTopicGroup group
Forward duration for which Visits should be included, that is, interval before predicted arrival at the stop for which to include Visits: only journeys which will arrive or depart within this time span will be returned.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="PreviewInterval" type="PositiveDurationType">
<xsd:annotation>
<xsd:documentation>
Forward duration for which Visits should be included, that is, interval before predicted arrival at the stop for which to include Visits: only journeys which will arrive or depart within this time span will be returned.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
StartTime
Type:
xsd:dateTime, predefined, simple content
Defined:
locally within (this) StopMonitoringTopicGroup group
Start time for PreviewInterval. If absent, then current time is assumed.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="StartTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
Start time for PreviewInterval. If absent, then current time is assumed.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
StopVisitTypes
Type:
StopVisitTypeEnumeration, simple content
Default:
"all"
Defined:
locally within (this) StopMonitoringTopicGroup group
Whether to include arrival Visits, departure Visits, or all. Default is 'all'.
XML Source (see within schema source)
<xsd:element default="all" minOccurs="0" name="StopVisitTypes" type="StopVisitTypeEnumeration">
<xsd:annotation>
<xsd:documentation>
Whether to include arrival Visits, departure Visits, or all. Default is 'all'.
</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/