XML Schema "siri_stopMonitoring_service.xsd"
Target Namespace:
http://www.siri.org.uk/siri
Version:
2.0
Defined Components:
elements (15 global + 71 local), complexTypes (18), simpleTypes (3), element groups (9)
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
C:\Users\Tony\eclipse_workspace\siri-20-java\xsd\siri_stopMonitoring_service.xsd; see XML source
Includes Schemas (3):
siri_modelPermissions-v2.0.xsd [src], siri_monitoredVehicleJourney-v2.0.xsd [src], siri_requests-v2.0.xsd [src]
Included in Schemas (1):
siri_all_functionalServices.xsd [src]
Annotation
SIRI-SM Stop Monitoring Service.
All Element Summary (local elements unified by type)
AccessControl (in StopMonitoringServiceCapabilities)
Available Optional Access control capabilities.
Type:
Content:
complex, 4 elements
Defined:
AppliesFromTime (in StopNoticeCancellation)
In case of a delayed cancellation this time tells from when the cancellation applies.
Type:
xsd:dateTime
Content:
simple
Defined:
ByStartTime (in TopicFiltering in StopMonitoringServiceCapabilities)
Whether a start time other than now can be specified for preview interval.
Type:
xsd:boolean
Content:
simple
Defined:
locally within TopicFiltering element; see XML source
ChangeBeforeUpdates (type PositiveDurationType)
Type:
Content:
simple
Defined:
locally at 4 locations
ClearDownRef (type ClearDownRefStructure)
Type:
Content:
simple
Defined:
locally at 4 locations
Content (in DeliveryVariant)
Variant text.
Type:
Content:
simple, 1 attribute
Defined:
DefaultDetailLevel (in RequestPolicy in StopMonitoringServiceCapabilities)
Default Detail level if non specified on request.
Type:
Content:
simple
Defined:
DefaultPreviewInterval (type PositiveDurationType)
Type:
Content:
simple
Defined:
locally at 8 locations
DeliveryVariant (in StopLineNotice)
Variant of a notice for use in a particular media channel.
Type:
Content:
complex, 2 elements
Defined:
DestinationRef (type DestinationRefStructure)
Type:
Content:
simple
Defined:
locally at 3 locations
DirectionRef (type DirectionRefStructure)
Type:
Content:
simple
Defined:
locally at 20 locations
FilterByVisitType (in TopicFiltering in StopMonitoringServiceCapabilities)
Whether results can be filtered by VistitType, e.g. arrivals, departures.
Type:
xsd:boolean
Content:
simple
Defined:
locally within TopicFiltering element; see XML source
HasDetailLevel (type xsd:boolean)
Type:
xsd:boolean
Content:
simple
Defined:
locally at 2 locations
HasLineNotices (in ResponseFeatures in StopMonitoringServiceCapabilities)
Whether result supports LINE events.
Type:
xsd:boolean
Content:
simple
Defined:
locally within ResponseFeatures element; see XML source
HasMaximumVisits (in RequestPolicy in StopMonitoringServiceCapabilities)
Whether results can be limited to a maximum number.
Type:
xsd:boolean
Content:
simple
Defined:
HasMinimumVisitsPerLine (in RequestPolicy in StopMonitoringServiceCapabilities)
Whether results can be limited to include a minimum number per LINE.
Type:
xsd:boolean
Content:
simple
Defined:
HasMinimumVisitsPerVia (in RequestPolicy in StopMonitoringServiceCapabilities)
Whether results can be limited to include a minimum numVIA (i.e. per JOURNEY PATTERN).
Type:
xsd:boolean
Content:
simple
Defined:
HasNumberOfOnwardsCalls (type xsd:boolean)
Type:
xsd:boolean
Content:
simple
Defined:
locally at 2 locations
HasNumberOfPreviousCalls (type xsd:boolean)
Type:
xsd:boolean
Content:
simple
Defined:
locally at 2 locations
HasSituations (type xsd:boolean)
Type:
xsd:boolean
Content:
simple
Defined:
locally at 2 locations
IncludeSituations (type xsd:boolean)
Type:
xsd:boolean
Content:
simple
Defined:
locally at 2 locations
IncrementalUpdates (type xsd:boolean)
Type:
xsd:boolean
Content:
simple
Defined:
locally at 8 locations
Language (type xsd:boolean)
Preferred language in which to return text values.
Type:
xsd:boolean
Content:
simple
Defined:
LineNote (in StopLineNotice)
Special text associated with LINE.
Type:
Content:
simple, 1 attribute
Defined:
LineRef (type LineRefStructure)
Type:
Content:
simple
Defined:
locally at 23 locations
MaximumNumberOfCalls (defined in StopMonitoringRequestPolicyGroup group)
If calls are to be returned, maximum number of calls to include in response.
Type:
anonymous complexType
Content:
complex, 2 elements
Defined:
Includes:
definitions of 2 elements
MaximumStopVisits (type xsd:nonNegativeInteger)
The maximum number of Stop Visits to include in a given delivery.
Type:
xsd:nonNegativeInteger
Content:
simple
Defined:
MaximumTextLength (type xsd:positiveInteger)
Maximum length of text to return for text elements.
Type:
xsd:positiveInteger
Content:
simple
Defined:
MinimumStopVisitsPerLine (type xsd:nonNegativeInteger)
The minimum number of Stop Visits for a given LINE to include in a given delivery.
Type:
xsd:nonNegativeInteger
Content:
simple
Defined:
MinimumStopVisitsPerLineVia (type xsd:nonNegativeInteger)
The minimum number of Stop Visits for a given LINE and VIA combination to include in a given delivery.
Type:
xsd:nonNegativeInteger
Content:
simple
Defined:
MonitoredStopVisit
A visit to a stop by a VEHICLE as an arrival and /or departure.
Type:
Content:
complex, 9 elements
Defined:
globally; see XML source
Used:
MonitoredStopVisitCancellation
Reference to an previously communicated Stop Visit which should now be removed from the arrival/departure board for the stop.
Type:
Content:
complex, 18 elements
Defined:
globally; see XML source
Used:
MonitoredVehicleJourney (in MonitoredStopVisit)
Provides real-time information about the VEHICLE JOURNEY along which a VEHICLE is running.
Type:
MonitoredVehicleJourneyStructure
Content:
unknown
Defined:
MonitoringName (type NaturalLanguageStringStructure)
Type:
Content:
simple, 1 attribute
Defined:
locally at 2 locations
MonitoringRef (type MonitoringRefStructure)
Type:
Content:
simple
Defined:
locally at 12 locations
Note (in StopMonitoringDelivery)
Type:
Content:
simple, 1 attribute
Defined:
locally at 2 locations
Notice (in ServiceException)
Text explanation of service exception.
Type:
Content:
simple, 1 attribute
Defined:
Onwards (type xsd:nonNegativeInteger)
Type:
xsd:nonNegativeInteger
Content:
simple
Defined:
locally at 2 locations
OperatorRef (type OperatorRefStructure)
Type:
Content:
simple
Defined:
locally at 12 locations
PreviewInterval (type PositiveDurationType)
Type:
Content:
simple
Defined:
locally at 6 locations
Previous (type xsd:nonNegativeInteger)
Type:
xsd:nonNegativeInteger
Content:
simple
Defined:
locally at 2 locations
PublishedLineName (in StopLineNotice)
Name or Number by which the LINE is known to the public.
Type:
Content:
simple, 1 attribute
Defined:
Reason (type NaturalLanguageStringStructure)
Type:
Content:
simple, 1 attribute
Defined:
locally at 9 locations
RequestPolicy (in StopMonitoringServiceCapabilities)
Available Request Policy capabilities.
Type:
Content:
complex, 13 elements
Defined:
ResponseFeatures (in StopMonitoringServiceCapabilities)
Available Optional Response capabilities.
Type:
anonymous complexType
Content:
complex, 2 elements
Defined:
Includes:
definitions of 2 elements
ServiceException
Exceptions to service availability for all or some services SIRI 2.0
Type:
Content:
complex, 7 elements
Defined:
globally; see XML source
Used:
ServiceStatus (in ServiceException)
Status of service, Service not yet started, Service ended for day, no service today, etc.
Type:
Content:
simple
Defined:
SituationRef (in ServiceException)
Reference to a SITUATION providing further information about exception
Type:
Content:
simple
Defined:
StartTime (type xsd:dateTime)
Type:
xsd:dateTime
Content:
simple
Defined:
locally at 6 locations
StopFacility (in MonitoredStopVisit)
Facility associated with stop visit
Type:
Content:
simple
Defined:
StopLineNotice
LINE notice for stop.
Type:
Content:
complex, 10 elements
Defined:
globally; see XML source
Used:
StopLineNoticeCancellation
Reference to an previously communicated LINE notice which should now be removed from the arrival/departure board for the stop.
Type:
Content:
complex, 6 elements
Defined:
globally; see XML source
Used:
StopMonitoringCapabilitiesRequest
Request for information about Stop Monitoring Service Capabilities.
Type:
Content:
complex, 1 attribute, 4 elements
Subst.Gr:
Defined:
globally; see XML source
Used:
StopMonitoringCapabilitiesResponse
Capabilities for Stop Monitoring Service.
Type:
Content:
complex, 1 attribute, 9 elements
Subst.Gr:
Defined:
globally; see XML source
Used:
StopMonitoringDelivery
Delivery for Stop Monitoring Service.
Type:
Content:
complex, 1 attribute, 23 elements
Subst.Gr:
Defined:
globally; see XML source
Used:
StopMonitoringDetailLevel (type StopMonitoringDetailEnumeration)
Level of detail to include in response.
Type:
Content:
simple
Defined:
StopMonitoringFIlter (in StopMonitoringMultipleRequest)
Request particulars for an individual stop as part of a list of multiple= requests.
Type:
Content:
complex, 18 elements
Defined:
StopMonitoringMultipleRequest
Request for information about Stop Visits, i.e. arrivals and departures at multiple stops stop.
Type:
Content:
complex, 1 attribute, 3 elements
Subst.Gr:
Defined:
globally; see XML source
Used:
StopMonitoringPermission (in StopMonitoringPermissions)
Permission for a single participant or all participants to use an aspect of the service.
Type:
Content:
complex, 7 elements
Defined:
StopMonitoringPermissions
Participants permissions to use the service, Only returned if requested.
Type:
anonymous complexType (extension of PermissionsStructure)
Content:
complex, 2 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
StopMonitoringRequest
Request for information about Stop Visits, i.e. arrivals and departures at a stop.
Type:
Content:
complex, 1 attribute, 20 elements
Subst.Gr:
Defined:
globally; see XML source
Used:
StopMonitoringServiceCapabilities
Capabilities of StopMonitoring Service.
Type:
Content:
complex, 7 elements
Defined:
globally; see XML source
Used:
StopMonitoringSubscriptionRequest
Request for a subscription to Stop Monitoring Service.
Type:
Content:
complex, 7 elements
Subst.Gr:
Defined:
globally; see XML source
Used:
StopMonitorPermission (type StopMonitorPermissionStructure)
Type:
Content:
complex, 2 elements
Defined:
locally at 2 locations
StopMonitorPermissions (in StopMonitoringPermission)
The monitoring points that the participant may access.
Type:
anonymous complexType
Content:
complex, 2 elements
Defined:
Includes:
definitions of 2 elements
StopNote (in StopNotice)
Text associated with Stop Notice ed since SIRI 2.0)
Type:
Content:
simple, 1 attribute
Defined:
locally within StopNoticeStructure complexType; see XML source
StopNotice
Notice for stop.
Type:
Content:
complex, 7 elements
Defined:
globally; see XML source
Used:
StopNoticeCancellation
Reference to an previously communicated Notice which should now be removed from the arrival/departure board for the stop.
Type:
Content:
complex, 6 elements
Defined:
globally; see XML source
Used:
StopVisitNote (in MonitoredStopVisit)
Text associated with Stop Visit.
Type:
Content:
simple, 1 attribute
Defined:
StopVisitTypes (type StopVisitTypeEnumeration)
Whether to include arrival Visits, departure Visits, or all.
Type:
Content:
simple
Defined:
SubscriptionPolicy (type CapabilitySubscriptionPolicyStructure)
Type:
Content:
complex, 2 elements
Defined:
locally at 9 locations
TopicFiltering (in StopMonitoringServiceCapabilities)
Available Filtering Capabilities.
Type:
anonymous complexType
Content:
complex, 7 elements
Defined:
Includes:
definitions of 7 elements
UseNames (type xsd:boolean)
Type:
xsd:boolean
Content:
simple
Defined:
locally at 2 locations
UseReferences (type xsd:boolean)
Type:
xsd:boolean
Content:
simple
Defined:
locally at 2 locations
ValidUntilTime (type xsd:dateTime)
Type:
xsd:dateTime
Content:
simple
Defined:
locally at 5 locations
VariantType (in DeliveryVariant)
Classification of DELIVERY VARIANT +SIRI v2.0.
Type:
xsd:normalizedString
Content:
simple
Defined:
VehicleJourneyRef (type FramedVehicleJourneyRefStructure)
Type:
Content:
complex, 2 elements
Defined:
locally at 6 locations
Complex Type Summary
Type for Delviery Variant +SIRI v2.0
Content:
complex, 2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
Type for Cancellation of an earlier Stop Visit.
Content:
complex, 18 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
Type for Visit of a VEHICLE to a stop monitoring point.
Content:
complex, 9 elements
Defined:
globally; see XML source
Includes:
definitions of 5 elements
Used:
Type for whether service is unavailable for all or some services SIRI 2.0
Content:
complex, 7 elements
Defined:
globally; see XML source
Includes:
definitions of 6 elements
Used:
Type for Cancellation of an earlier Stop Line Notice.
Content:
complex, 6 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
Type for a Stop Line Notice.
Content:
complex, 10 elements
Defined:
globally; see XML source
Includes:
definitions of 6 elements
Used:
Type for Delivery for Stop Monitoring Service.
Content:
complex, 1 attribute, 9 elements
Defined:
globally; see XML source
Includes:
definitions of 1 attribute, 3 elements
Used:
Type for Monitoring Service Capability Request Policy.
Content:
complex, 6 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
Type for Deliveries for Stop Monitoring Service.
Content:
complex, 1 element
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
never
Type for Delivery for Stop Monitoring Service.
Content:
complex, 1 attribute, 23 elements
Defined:
globally; see XML source
Includes:
definitions of 1 attribute, 2 elements
Used:
Type for an individual Stop Monitoring a Multiple Request.
Content:
complex, 18 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
Type for Functional Service Request for Stop Monitoring Service on multiple stops.
Content:
complex, 1 attribute, 3 elements
Defined:
globally; see XML source
Includes:
definitions of 1 attribute, 1 element
Used:
Type for Functional Service Request for Stop Monitoring Service.
Content:
complex, 1 attribute, 20 elements
Defined:
globally; see XML source
Includes:
definitions of 1 attribute, 1 element
Used:
Type for Stop Monitoring Capabilities.
Content:
complex, 7 elements
Defined:
globally; see XML source
Includes:
definitions of 5 elements
Used:
Type for Monitoring Service Permission.
Content:
complex, 7 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
Type for Subscription Request for Stop Monitoring Service.
Content:
complex, 7 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
Type for Cancellation of an earlier Stop Notice.
Content:
complex, 6 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
Type for Notice for stop
Content:
complex, 7 elements
Defined:
globally; see XML source
Includes:
definitions of 5 elements
Used:
Simple Type Summary
Classification of the service exception
Defined:
globally; see XML source
Used:
Detail Levels for Stop Monitoring Request.
Defined:
globally; see XML source
Used:
Visit Types to Return.
Defined:
globally; see XML source
Used:
Element Group Summary
Parameters that affect the subscription publishing and notification processing.
Defined:
globally; see XML source
Used:
never
Convenience artifact to pick out main elements of the Stop Monitoring Service.
Content:
Defined:
globally; see XML source
Includes:
definitions of 6 elements
Used:
never
Payload part of Stop Monitoring Service delivery.
Content:
Defined:
globally; see XML source
Includes:
definitions of 9 elements
Used:
Parameters that affect the request processing.
Content:
Defined:
globally; see XML source
Includes:
definitions of 9 elements
Used:
Parameters that affect the subscription publishing and notification processing.
Content:
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
Parameters that specify the content to be returned.
Content:
Defined:
globally; see XML source
Includes:
definitions of 8 elements
Used:
Elements for volume control.
Content:
Defined:
globally; see XML source
Includes:
definitions of 7 elements
Used:
External identifiers of Cancelled Stop Visit.
Content:
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
External identifiers of Stop Visit.
Content:
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
XML Source
<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSpy v2011 rel. 2 sp1 (x64) (http://www.altova.com) by Christophe Duquesne (Dryade) -->
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" id="siri_stopMonitoring_service" targetNamespace="http://www.siri.org.uk/siri" version="2.0" xmlns="http://www.siri.org.uk/siri" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:annotation>
<xsd:appinfo>
<Metadata xmlns="http://www.govtalk.gov.uk/CM/gms-xs">
<Aggregation>main schema</Aggregation>
<Audience>e-service developers</Audience>
<Contributor>CEN TC278 WG3 SG7 Team</Contributor>
<Coverage>Europe</Coverage>
<Creator>
Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk
</Creator>
<Date>
<Created>2004-09-29</Created>
</Date>
<Date>
<Modified>2004-10-01</Modified>
</Date>
<Date>
<Modified>2005-02-14</Modified>
</Date>
<Date>
<Modified>2005-02-20</Modified>
</Date>
<Date>
<Modified>2005-05-11</Modified>
</Date>
<Date>
<Modified>2007-04-17</Modified>
Name Space changes
</Date>
<Date>
<Modified>2008-03-26</Modified>
Drop separate flatten structure on response for stopVisit
</Date>
<Date>
<Modified>2008-05-08</Modified>
(a) Correct missing type on FeatureRef
(b) Add optional MonitoringRef on response so that can return the identfiier even if there are no stop visits.
This allows client to be stateless -
(a) Add a StopMonitoringMultipleRequest and othe elements top support multiple stops on single request
</Date>
<Date>
<Modified>2008-10-06</Modified>
Drop redundant groups
</Date>
<Date>
<Modified>2008-11-17</Modified>
Revise to support substitution groups
</Date>
<Date>
<Modified>2009-03-30</Modified>
On SiriRequest change the element type of MaximumNumberOfCalls and MaximumNumberOfCallsOnwards from xsd:positiveInteger to xsd:nonNegativeInteger
</Date>
<Date>
<Modified>2012-03-23</Modified>
+SIRI v2.0
[VDV] Add Minimum-StopVisits&#65533;PerVia to STopMonitoringRequestPolicy
[VDV] Add HasMinimum-StopVisits&#65533;Via to STopMonitoringCapabilities
[VDV] Revise MonitoredVehicleJourney to include additioanl result files
[FR] Add Servcie Exception element
[VDV] Add delivery variant to LineNote
[SIRI-LITE] Allow a monitoring name in results.
[SIRI-LITE] Whether any related Situations should be included in the ServiceDelivery. Default is 'false'. +SIRI v2.0
</Date>
<Date>
<Modified>2012-04-18</Modified>
+SIRI v2.0
[VDV] Add ValidUntil Time to MonitoredStopVisit
Correct comment on MaximumNumberOfCalls elements
</Date>
<Date>
<Modified>2012-04-18</Modified>
+SIRI v2.0
[VDV] Add normal realtiem service Time to MonitoredStopVisit
Geeneral update permissions to include has SItuations
</Date>
<Date>
<Modified>2013-02-11</Modified>
Correction: ServiceExceptionStatus is optional
enumeration value realtmeDataAvailable corrected
StopNotice and StopNoticeCancellation added
</Date>
<Description>
<p>
SIRI is a European CEN standard for the exchange of Public Transport real-time information.
</p>
<p>
This sub-schema describes the Stop Monitoring Service.
</p>
</Description>
<Format>
<MediaType>text/xml</MediaType>
<Syntax>http://www.w3.org/2001/XMLSchema</Syntax>
<Description>XML schema, W3C Recommendation 2001</Description>
</Format>
<Identifier>
{http://www.siri.org.uk/schema/2.0/}siri_stopMonitoring_service.xsd
</Identifier>
<Language>[ISO 639-2/B] ENG</Language>
<Publisher>Kizoom, 109-123 Clifton Street, London EC4A 4LD</Publisher>
<Relation>
<Requires>
http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests-v2.0.xsd
</Requires>
<Requires>
http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey-v2.0.xsd
</Requires>
</Relation>
<Rights>
Unclassified
<Copyright>CEN, VDV, RTIG 2004-2012</Copyright>
</Rights>
<Source>
<ul>
<li>
Derived from the VDV, RTIG XML and Trident standards.
</li>
</ul>
</Source>
<Status>Version 2.0 Draft</Status>
<Subject>
<Category>
Arts, recreation and travel, Tourism, Travel (tourism), Transport,
Air transport, Airports,
Ports and maritime transport, Ferries (marine),
Public transport, Bus services, Coach services, Bus stops and stations,
Rail transport, Railway stations and track, Train services, Underground trains,
Business and industry, Transport, Air transport, Ports and maritime transport, Public transport,
Rail transport, Roads and road transport
</Category>
<Project>CEN TC278 WG3 SG7</Project>
</Subject>
<Title>
SIRI-SM XML schema. Service Interface for Real-time Information. Subschema for Stop Monitoring Service.
</Title>
<Type>Standard</Type>
</Metadata>
</xsd:appinfo>
<xsd:documentation>SIRI-SM Stop Monitoring Service.</xsd:documentation>
</xsd:annotation>
<!-- ======================================================================= -->
<xsd:include schemaLocation="siri/siri_requests-v2.0.xsd"/>
<xsd:include schemaLocation="siri_model/siri_monitoredVehicleJourney-v2.0.xsd"/>
<xsd:include schemaLocation="siri_model/siri_modelPermissions-v2.0.xsd"/>
<!-- ======================================================================= -->
<xsd:group name="SiriStopMonitoringIndexGroup">
<xsd:annotation>
<xsd:documentation>
Convenience artifact to pick out main elements of the Stop Monitoring Service.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="StopMonitoringRequest"/>
<xsd:element ref="StopMonitoringMultipleRequest">
<xsd:annotation>
<xsd:documentation>
Request for information about Stop Visits, i.e. arrivals and departures at multiple stops.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="StopMonitoringDelivery"/>
<xsd:sequence>
<xsd:element ref="StopMonitoringCapabilitiesRequest"/>
</xsd:sequence>
</xsd:sequence>
</xsd:group>
<!-- ====REQUESTS ====================================================== -->
<!-- ==== FS: Stop Monitoring Request =============================================== -->
<xsd:annotation>
<xsd:documentation>
Request for information about Stop Visits, i.e. arrivals and departures at a stop.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<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>
<xsd:annotation>
<xsd:documentation>
Parameters that affect the request processing. Mostly act to reduce the number of stops returned.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element default="false" minOccurs="0" name="Language" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Preferred language in which to return text values.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="IncludeTranslations"/>
<xsd:element minOccurs="0" name="MaximumStopVisits" type="xsd:nonNegativeInteger">
<xsd:annotation>
<xsd:documentation>
The maximum number of Stop Visits to include in a given delivery. The first n Stop Visits within the look ahead window are included. Only Visits within the Lookahead Interval are returned. The MinimumStopVisits parameter can be used to reduce the the number of entries for each LINE within the total returned.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:choice>
<xsd:element minOccurs="0" name="MinimumStopVisitsPerLine" type="xsd:nonNegativeInteger">
<xsd:annotation>
<xsd:documentation>
The minimum number of Stop Visits for a given LINE to include in a given delivery. If there are more Visits within the LookAheadInterval than allowed by MaximumStopVisits and a MinimumStopVisits value is specified, then at least the minimum number will be delivered for each LINE. I.e Stop Visits will be included even if the Stop Visits are later than those for some other LINE for which the minimum number of Stop Visits has already been supplied. This allows the Consumer to obtain at least one entry for every available LINE with vehicles approaching the stop. Only STOP Visits within the Look ahead Interval are returned.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="MinimumStopVisitsPerLineVia" type="xsd:nonNegativeInteger">
<xsd:annotation>
<xsd:documentation>
The minimum number of Stop Visits for a given LINE and VIA combination to include in a given delivery. As for MinimumStopVisitsPerLine but with Via also taken into account. SIRI+v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
<xsd:element default="30" minOccurs="0" name="MaximumTextLength" type="xsd:positiveInteger">
<xsd:annotation>
<xsd:documentation>
Maximum length of text to return for text elements. Default is 30.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="normal" minOccurs="0" name="StopMonitoringDetailLevel" type="StopMonitoringDetailEnumeration">
<xsd:annotation>
<xsd:documentation>
Level of detail to include in response. Default is 'normal'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="IncludeSituations" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether any related SITUATIONs should be included in the ServiceDelivery. Default is 'false'. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="MaximumNumberOfCalls">
<xsd:annotation>
<xsd:documentation>
If calls are to be returned, maximum number of calls to include in response. If absent, exclude all calls.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element minOccurs="0" name="Previous" type="xsd:nonNegativeInteger">
<xsd:annotation>
<xsd:documentation>
Maximum number of ONWARDS CALLs to include in results. Only applies if StopMonitoringDetailLevel of 'calls' specified. Zero for none. If StopMonitoringDetailLevel of 'calls' specified but MaximumNumberOfCalls.Previous absent, include all ONWARDS CALLs.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="Onwards" type="xsd:nonNegativeInteger">
<xsd:annotation>
<xsd:documentation>
Maximum number of ONWARDS CALLs to include in results. Zero for none. Only applies if StopMonitoringDetailLevel of 'calls'specified. Zero for none. If StopMonitoringDetailLevel of 'calls' specified but MaximumNumberOfCalls.Onwards absent, include all ONWARDS CALLs.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:simpleType name="StopMonitoringDetailEnumeration">
<xsd:annotation>
<xsd:documentation>Detail Levels for Stop Monitoring Request.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="minimum">
<xsd:annotation>
<xsd:documentation>
Return only the minimum amount of optional data for each Stop Visit to provide a display, A time at stop, LINE name and destination name.
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="basic">
<xsd:annotation>
<xsd:documentation>
Return minimum and other available basic details for each Stop Visit. Do not include data on times at next stop or destination.
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="normal">
<xsd:annotation>
<xsd:documentation>
Return all basic data, and also origin VIA points and destination.
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="calls">
<xsd:annotation>
<xsd:documentation>
Return in addition to normal data, the CALL data for each Stop Visit, including PREVIOUS and ONWARD CALLs with passing times.
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="full">
<xsd:annotation>
<xsd:documentation>
Return all available data for each Stop Visit, including calls.
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>
<!-- ======================================================================= -->
<!-- ==== FS: Stop Monitoring Multiple Request =============================================== -->
<xsd:complexType name="StopMonitoringRequestStructure">
<xsd:annotation>
<xsd:documentation>
Type for Functional Service Request for Stop Monitoring Service.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractFunctionalServiceRequestStructure">
<xsd:sequence>
<xsd:group ref="StopMonitoringTopicGroup"/>
<xsd:element minOccurs="0" ref="Extensions"/>
</xsd:sequence>
<xsd:attribute default="2.0" name="version" type="VersionString">
<xsd:annotation>
<xsd:documentation>
Version number of request.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
Request for information about Stop Visits, i.e. arrivals and departures at multiple stops stop. SIRI 1.3
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
Type for Functional Service Request for Stop Monitoring Service on multiple stops.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractFunctionalServiceRequestStructure">
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="StopMonitoringFIlter" type="StopMonitoringFilterStructure">
<xsd:annotation>
<xsd:documentation>
Request particulars for an individual stop as part of a list of multiple= requests.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute default="2.0" name="version" type="VersionString" use="optional"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="StopMonitoringFilterStructure">
<xsd:annotation>
<xsd:documentation>
Type for an individual Stop Monitoring a Multiple Request.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="StopMonitoringTopicGroup"/>
<xsd:element minOccurs="0" ref="Extensions"/>
</xsd:sequence>
</xsd:complexType>
<!-- ====Stop Monitoring Subscription Request ==================================== -->
<xsd:annotation>
<xsd:documentation>
Request for a subscription to Stop Monitoring Service.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
Parameters that affect the subscription publishing and notification processing.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element default="false" minOccurs="0" name="IncrementalUpdates" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether the producer should return the complete set of current data, or only provide updates to the last data returned, i.e. additions, modifications and deletions.
If false each subscription response will contain the full information as specified in this request.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="ChangeBeforeUpdates" type="PositiveDurationType">
<xsd:annotation>
<xsd:documentation>
The amount of change to the arrival or departure time that can happen before an update is sent (i.e. if ChangeBeforeUpdate is set to 2 minutes, the subscriber will not be told that a bus is 30 seconds delayed - an update will only be sent when the bus is at least 2 minutes delayed). Default is zero - all changes will be sent regardless.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:complexType name="StopMonitoringSubscriptionStructure">
<xsd:annotation>
<xsd:documentation>
Type for Subscription Request for Stop Monitoring Service.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractSubscriptionStructure">
<xsd:sequence>
<xsd:element ref="StopMonitoringRequest"/>
<xsd:sequence>
</xsd:sequence>
<xsd:element minOccurs="0" ref="Extensions"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!-- ====RESPONSES=========================================================== -->
<!-- ==== FS: Stop Monitoring Delivery ==================================== -->
<xsd:annotation>
<xsd:documentation>
Parameters that affect the subscription publishing and notification processing.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence/>
</xsd:group>
<xsd:annotation>
<xsd:documentation>Delivery for Stop Monitoring Service.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="StopMonitoringDeliveryStructure">
<xsd:annotation>
<xsd:documentation>Type for Delivery for Stop Monitoring Service.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractServiceDeliveryStructure">
<xsd:sequence>
<xsd:group ref="StopMonitoringPayloadGroup"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="Note" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
Text associated with whole delivery. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="Extensions"/>
</xsd:sequence>
<xsd:attribute default="2.0" name="version" type="VersionString">
<xsd:annotation>
<xsd:documentation>
Version number of response. Fixed
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<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>
<xsd:group name="StopVisitReferenceGroup">
<xsd:annotation>
<xsd:documentation>External identifiers of Stop Visit.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="MonitoringRef" type="MonitoringRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to a stop monitoring point to which Stop Visit applies.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="ClearDownRef" type="ClearDownRefStructure">
<xsd:annotation>
<xsd:documentation>
Identifier associated with Stop Visit for use in direct wireless communication between bus and stop display. Cleardown codes are short arbitrary identifiers suitable for radio transmission.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<!-- ===== Stop Visit ======================================================== -->
<xsd:annotation>
<xsd:documentation>
A visit to a stop by a VEHICLE as an arrival and /or departure.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="MonitoredStopVisitStructure">
<xsd:annotation>
<xsd:documentation>
Type for Visit of a VEHICLE to a stop monitoring point. May provide information about the arrival, the departure or both.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractIdentifiedItemStructure">
<xsd:sequence>
<xsd:element minOccurs="0" name="ValidUntilTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>Time until when data is valid. +SIRI 2.0</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group minOccurs="0" ref="StopVisitReferenceGroup"/>
<xsd:element name="MonitoredVehicleJourney" type="MonitoredVehicleJourneyStructure">
<xsd:annotation>
<xsd:documentation>
Provides real-time information about the VEHICLE JOURNEY along which a VEHICLE is running.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="StopVisitNote" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>Text associated with Stop Visit.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="StopFacility" type="FacilityRefStructure">
<xsd:annotation>
<xsd:documentation>Facility associated with stop visit</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="Extensions"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:simpleType name="StopVisitTypeEnumeration">
<xsd:annotation>
<xsd:documentation>Visit Types to Return.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="all">
<xsd:annotation>
<xsd:documentation>Return all Stop Visits.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="arrivals">
<xsd:annotation>
<xsd:documentation>Return only arrival Stop Visits.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="departures">
<xsd:annotation>
<xsd:documentation>Return only departure Stop Visits.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>
<!-- ====== Stop Visit Cancellation ================================================ -->
<xsd:annotation>
<xsd:documentation>
Reference to an previously communicated Stop Visit which should now be removed from the arrival/departure board for the stop.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>Type for Cancellation of an earlier Stop Visit.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractReferencingItemStructure">
<xsd:sequence>
<xsd:group minOccurs="0" ref="StopVisitCancellationIdentityGroup"/>
<xsd:element minOccurs="0" name="ClearDownRef" type="ClearDownRefStructure">
<xsd:annotation>
<xsd:documentation>
Cleardown identifier of Stop Visit that is being deleted.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group ref="JourneyPatternInfoGroup"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="Reason" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
Reason for cancellation. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="Extensions"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>External identifiers of Cancelled Stop Visit.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="MonitoringRef" type="MonitoringRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to a stop monitoring point to which cancellation applies.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="VisitNumber"/>
<xsd:group minOccurs="0" ref="LineIdentityGroup"/>
<xsd:element minOccurs="0" name="VehicleJourneyRef" type="FramedVehicleJourneyRefStructure">
<xsd:annotation>
<xsd:documentation>
VEHICLE JOURNEY of Stop Visit that is being cancelled.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<!-- ====Stop Line Notice ================================================= -->
<xsd:element name="StopLineNotice" type="StopLineNoticeStructure">
<xsd:annotation>
<xsd:documentation>LINE notice for stop.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="StopLineNoticeStructure">
<xsd:annotation>
<xsd:documentation>Type for a Stop Line Notice.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractIdentifiedItemStructure">
<xsd:sequence>
<xsd:element name="MonitoringRef" type="MonitoringRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to a stop monitoring point to which LINE notice applies.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group ref="LineIdentityGroup"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="PublishedLineName" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
Name or Number by which the LINE is known to the public. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="LineNote" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>Special text associated with LINE.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="DeliveryVariant" type="DeliveryVariantStructure">
<xsd:annotation>
<xsd:documentation>
Variant of a notice for use in a particular media channel. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="SituationRef"/>
<xsd:element minOccurs="0" ref="Extensions"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="DeliveryVariantStructure">
<xsd:annotation>
<xsd:documentation>Type for Delviery Variant +SIRI v2.0</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="VariantType" type="xsd:normalizedString">
<xsd:annotation>
<xsd:documentation>Classification of DELIVERY VARIANT +SIRI v2.0.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Content" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>Variant text. SIRI v".0</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<!-- ====Stop Line Notice Cancellation =================================== -->
<xsd:annotation>
<xsd:documentation>
Reference to an previously communicated LINE notice which should now be removed from the arrival/departure board for the stop.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="StopLineNoticeCancellationStructure">
<xsd:annotation>
<xsd:documentation>
Type for Cancellation of an earlier Stop Line Notice.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractReferencingItemStructure">
<xsd:sequence>
<xsd:element name="MonitoringRef" type="MonitoringRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to a stop monitoring point to which LINE notice applies.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group ref="LineIdentityGroup"/>
<xsd:element minOccurs="0" ref="Extensions"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!-- ====Stop Notice ================================================= -->
<xsd:element name="StopNotice" type="StopNoticeStructure">
<xsd:annotation>
<xsd:documentation>Notice for stop.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="StopNoticeStructure">
<xsd:annotation>
<xsd:documentation>Type for Notice for stop</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractRequiredIdentifiedItemStructure">
<xsd:sequence>
<xsd:element name="MonitoringRef" type="MonitoringRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to a stop monitoring point to which SITUATION applies.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="StopPointRef"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="SituationRef"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="StopNote" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
Text associated with Stop Notice ed since SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="Extensions"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!-- ====Stop Notice Cancellation =================================== -->
<xsd:annotation>
<xsd:documentation>
Reference to an previously communicated Notice which should now be removed from the arrival/departure board for the stop.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="StopNoticeCancellationStructure">
<xsd:annotation>
<xsd:documentation>Type for Cancellation of an earlier Stop Notice.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractRequiredReferencingItemStructure">
<xsd:sequence>
<xsd:element name="MonitoringRef" type="MonitoringRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to a stop monitoring point to which Notice applies.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="StopPointRef"/>
<xsd:element minOccurs="0" name="AppliesFromTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
In case of a delayed cancellation this time tells from when the cancellation applies.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="Extensions"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!-- ======================================================================= -->
<xsd:element name="ServiceException" type="ServiceExceptionStructure">
<xsd:annotation>
<xsd:documentation>
Exceptions to service availability for all or some services SIRI 2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="ServiceExceptionStructure">
<xsd:annotation>
<xsd:documentation>
Type for whether service is unavailable for all or some services SIRI 2.0
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractItemStructure">
<xsd:sequence>
<xsd:element minOccurs="0" ref="LineRef"/>
<xsd:element minOccurs="0" name="DirectionRef" type="DirectionRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to a LINE DIRECTION to which exception applies.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="StopPointRef"/>
<xsd:element minOccurs="0" name="ServiceStatus" type="ServiceExceptionEnumeration">
<xsd:annotation>
<xsd:documentation>
Status of service, Service not yet started, Service ended for day, no service today, etc.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="Notice" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>Text explanation of service exception.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="SituationRef" type="SituationSimpleRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to a SITUATION providing further information about exception
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:simpleType name="ServiceExceptionEnumeration">
<xsd:annotation>
<xsd:documentation>Classification of the service exception</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="beforeFirstJourney">
<xsd:annotation>
<xsd:documentation>
No transport services returned because currently before first journey of day.
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="afterLastJourney">
<xsd:annotation>
<xsd:documentation>
No transport services returned because currently after first journey of day.
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="noServiceToday">
<xsd:annotation>
<xsd:documentation>
No transport services returned because no services today.
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="transportTemporarilySuspended">
<xsd:annotation>
<xsd:documentation>
No transport services returned because services currently suspended.
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="transportLongtermSuspended">
<xsd:annotation>
<xsd:documentation>
No transport services returned because prolonged suspension of services.
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="transportSeverlyDisrupted">
<xsd:annotation>
<xsd:documentation>
Transport services returned subject to severe disruptions.
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="realtimeDataNotAvailable">
<xsd:annotation>
<xsd:documentation>
No transport services returned because real-time services not available.
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="realtimeDataAvailable"/>
</xsd:restriction>
</xsd:simpleType>
<!-- ======================================================================= -->
<!-- ==== WSDL=========================================-->
<xsd:complexType name="StopMonitoringDeliveriesStructure">
<xsd:annotation>
<xsd:documentation>
Type for Deliveries for Stop Monitoring Service. Used in WSDL.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" ref="StopMonitoringDelivery">
<xsd:annotation>
<xsd:documentation>Delivery for Stop Event service.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<!-- ======================================================================= -->
<!-- ==== CS: Capability Request=================================================================== -->
<xsd:annotation>
<xsd:documentation>
Request for information about Stop Monitoring Service Capabilities. Answered with StopMonitoringCapabilitiesResponse.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<!-- ==== CS: Capability Response =================================================================== -->
<xsd:annotation>
<xsd:documentation>
Capabilities for Stop Monitoring Service. Answers a StopMonitoringCapabilitiesRequest.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>Type for Delivery for Stop Monitoring Service.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractServiceCapabilitiesResponseStructure">
<xsd:sequence>
<xsd:element minOccurs="0" ref="StopMonitoringServiceCapabilities"/>
<xsd:element minOccurs="0" ref="StopMonitoringPermissions"/>
<xsd:element minOccurs="0" ref="Extensions"/>
</xsd:sequence>
<xsd:attribute default="2.0" name="version" type="VersionString">
<xsd:annotation>
<xsd:documentation>
Version number of response. Fixed
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>Capabilities of StopMonitoring Service.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>Type for Stop Monitoring Capabilities.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractCapabilitiesStructure">
<xsd:sequence>
<xsd:element minOccurs="0" name="TopicFiltering">
<xsd:annotation>
<xsd:documentation>Available Filtering Capabilities.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element default="PT60M" name="DefaultPreviewInterval" type="PositiveDurationType">
<xsd:annotation>
<xsd:documentation>Default preview interval. Default is 60 minutes.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="true" minOccurs="0" name="ByStartTime" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether a start time other than now can be specified for preview interval. Default is 'truet.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="FilterByMonitoringRef"/>
<xsd:element ref="FilterByLineRef"/>
<xsd:element minOccurs="0" ref="FilterByDirectionRef"/>
<xsd:element minOccurs="0" ref="FilterByDestination"/>
<xsd:element default="true" minOccurs="0" name="FilterByVisitType" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether results can be filtered by VistitType, e.g. arrivals, departures. Default True.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element minOccurs="0" name="RequestPolicy">
<xsd:annotation>
<xsd:documentation>Available Request Policy capabilities.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="StopMonitoringCapabilityRequestPolicyStructure">
<xsd:sequence>
<xsd:group ref="StopMonitoringVolumeGroup"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element minOccurs="0" name="SubscriptionPolicy" type="CapabilitySubscriptionPolicyStructure">
<xsd:annotation>
<xsd:documentation>Available Subscription Policy capabilities.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="AccessControl" type="MonitoringCapabilityAccessControlStructure">
<xsd:annotation>
<xsd:documentation>Available Optional Access control capabilities.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="ResponseFeatures">
<xsd:annotation>
<xsd:documentation>Available Optional Response capabilities.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element default="true" minOccurs="0" name="HasLineNotices" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether result supports LINE events. Default is 'true'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="false" minOccurs="0" name="HasSituations" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether result supports SITUATION REFERENCESs. Default is 'false'. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
Type for Monitoring Service Capability Request Policy.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="CapabilityRequestPolicyStructure">
<xsd:sequence>
<xsd:element default="true" minOccurs="0" name="UseReferences" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether results can return references for stops. Default is 'true'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="false" minOccurs="0" name="UseNames" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>Whether results can return names for stop.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!-- ==== Permissions =================================================== -->
<xsd:element name="StopMonitoringPermissions">
<xsd:annotation>
<xsd:documentation>
Participants permissions to use the service, Only returned if requested.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="PermissionsStructure">
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="StopMonitoringPermission" type="StopMonitoringServicePermissionStructure">
<xsd:annotation>
<xsd:documentation>
Permission for a single participant or all participants to use an aspect of the service.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:group name="StopMonitoringVolumeGroup">
<xsd:annotation>
<xsd:documentation>Elements for volume control.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element default="false" minOccurs="0" name="HasDetailLevel" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether Detail level filtering is supported. Default is ' false'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="normal" minOccurs="0" name="DefaultDetailLevel" type="StopMonitoringDetailEnumeration">
<xsd:annotation>
<xsd:documentation>
Default Detail level if non specified on request. Default Normal.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="true" minOccurs="0" name="HasMaximumVisits" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether results can be limited to a maximum number. Default is 'true'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="true" minOccurs="0" name="HasMinimumVisitsPerLine" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether results can be limited to include a minimum number per LINE. Default is 'true'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="false" minOccurs="0" name="HasMinimumVisitsPerVia" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether results can be limited to include a minimum numVIA (i.e. per JOURNEY PATTERN). +SIRI v2.0.
default is 'false'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="false" minOccurs="0" name="HasNumberOfOnwardsCalls" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
If system can return detailed calling pattern, whether a number of onwards calls to include can be specified. Default is 'false'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="false" minOccurs="0" name="HasNumberOfPreviousCalls" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
If system can return detailed calling pattern, whether a number of previouscalls to include can be specified. Default is 'false'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<!-- ====permissions=================================================================== -->
<xsd:annotation>
<xsd:documentation>Type for Monitoring Service Permission.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractPermissionStructure">
<xsd:sequence>
<xsd:element ref="OperatorPermissions"/>
<xsd:element ref="LinePermissions"/>
<xsd:element name="StopMonitorPermissions">
<xsd:annotation>
<xsd:documentation>
The monitoring points that the participant may access.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:choice>
<xsd:element ref="AllowAll"/>
<xsd:element maxOccurs="unbounded" name="StopMonitorPermission" type="StopMonitorPermissionStructure">
<xsd:annotation>
<xsd:documentation>
Participant's permission for this Monitoring Point (LOGICAL DISPLAY)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
</xsd:complexType>
</xsd:element>
<xsd:element minOccurs="0" ref="Extensions"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:schema>

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/