group "StopMonitoringPayloadGroup"
Namespace:
http://www.siri.org.uk/siri
Content:
9 elements
Defined:
globally in siri_stopMonitoring_service.xsd; see XML source
Includes:
definitions of 9 elements
Used:
at 1 location
Complex Content Model
MonitoringRef*, MonitoringName*, MonitoredStopVisit*, MonitoredStopVisitCancellation*, StopLineNotice*, StopLineNoticeCancellation*, StopNotice*, StopNoticeCancellation*, ServiceException*
Content Model Elements (9):
MonitoredStopVisit, MonitoredStopVisitCancellation, MonitoringName (type NaturalLanguageStringStructure), MonitoringRef (type MonitoringRefStructure), ServiceException, StopLineNotice, StopLineNoticeCancellation, StopNotice, StopNoticeCancellation
Known Usage Locations
Annotation
Payload part of Stop Monitoring Service delivery.
XML Source (see within schema source)
<xsd:group name="StopMonitoringPayloadGroup">
<xsd:annotation>
<xsd:documentation>Payload part of Stop Monitoring Service delivery.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="MonitoringRef" type="MonitoringRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to a stop monitoring point (LOGICAL DISPLAY that was requested. This can a be used to return the reference to the requested Monitoring Point if there are no stop visits for the stop. Normally tere will only be one. SIRI v1.3
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="MonitoringName" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
Name to use to describe monitoring point (Stop or display). Normally Consumer will already have access to this in its reference data but may be included to increase utility of delivery data i to devices that do not hold reference data, e.g. for SIRI LITE services(+SIRI v2.0).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="MonitoredStopVisit"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="MonitoredStopVisitCancellation"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="StopLineNotice"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="StopLineNoticeCancellation"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="StopNotice">
<xsd:annotation>
<xsd:documentation>Notice for stop. (SIRI 2.0++)</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="StopNoticeCancellation">
<xsd:annotation>
<xsd:documentation>
Reference to an previously communicated Notice which should now be removed from the arrival/departure board for the stop. (SIRI 2.0++)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="ServiceException">
<xsd:annotation>
<xsd:documentation>
Information about unavailablilty of some or all services at the SIRI 2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
Content Element Detail (all declarations; 9/9)
MonitoredStopVisit
Type:
MonitoredStopVisitStructure, complex content
Defined:
by reference within (this) StopMonitoringPayloadGroup group
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="MonitoredStopVisit"/>
MonitoredStopVisitCancellation
Type:
MonitoredStopVisitCancellationStructure, complex content
Defined:
by reference within (this) StopMonitoringPayloadGroup group
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="MonitoredStopVisitCancellation"/>
MonitoringName
Type:
NaturalLanguageStringStructure, simple content
Defined:
locally within (this) StopMonitoringPayloadGroup group
Name to use to describe monitoring point (Stop or display). Normally Consumer will already have access to this in its reference data but may be included to increase utility of delivery data i to devices that do not hold reference data, e.g. for SIRI LITE services(+SIRI v2.0).
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="MonitoringName" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
Name to use to describe monitoring point (Stop or display). Normally Consumer will already have access to this in its reference data but may be included to increase utility of delivery data i to devices that do not hold reference data, e.g. for SIRI LITE services(+SIRI v2.0).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
MonitoringRef
Type:
MonitoringRefStructure, simple content
Defined:
locally within (this) StopMonitoringPayloadGroup group
Reference to a stop monitoring point (LOGICAL DISPLAY that was requested. This can a be used to return the reference to the requested Monitoring Point if there are no stop visits for the stop. Normally tere will only be one. SIRI v1.3
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="MonitoringRef" type="MonitoringRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to a stop monitoring point (LOGICAL DISPLAY that was requested. This can a be used to return the reference to the requested Monitoring Point if there are no stop visits for the stop. Normally tere will only be one. SIRI v1.3
</xsd:documentation>
</xsd:annotation>
</xsd:element>
ServiceException
Type:
ServiceExceptionStructure, complex content
Defined:
by reference within (this) StopMonitoringPayloadGroup group
Information about unavailablilty of some or all services at the SIRI 2.0
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="ServiceException">
<xsd:annotation>
<xsd:documentation>
Information about unavailablilty of some or all services at the SIRI 2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
StopLineNotice
Type:
StopLineNoticeStructure, complex content
Defined:
by reference within (this) StopMonitoringPayloadGroup group
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="StopLineNotice"/>
StopLineNoticeCancellation
Type:
StopLineNoticeCancellationStructure, complex content
Defined:
by reference within (this) StopMonitoringPayloadGroup group
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="StopLineNoticeCancellation"/>
StopNotice
Type:
StopNoticeStructure, complex content
Defined:
by reference within (this) StopMonitoringPayloadGroup group
Notice for stop. (SIRI 2.0++)
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="StopNotice">
<xsd:annotation>
<xsd:documentation>Notice for stop. (SIRI 2.0++)</xsd:documentation>
</xsd:annotation>
</xsd:element>
StopNoticeCancellation
Type:
StopNoticeCancellationStructure, complex content
Defined:
by reference within (this) StopMonitoringPayloadGroup group
Reference to an previously communicated Notice which should now be removed from the arrival/departure board for the stop. (SIRI 2.0++)
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="StopNoticeCancellation">
<xsd:annotation>
<xsd:documentation>
Reference to an previously communicated Notice which should now be removed from the arrival/departure board for the stop. (SIRI 2.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/