XML Schema "siri_vehicleMonitoring_service.xsd"
Target Namespace:
http://www.siri.org.uk/siri
Version:
2.0
Defined Components:
elements (7 global + 48 local), complexTypes (12), simpleTypes (2), element groups (7)
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
C:\Users\Tony\eclipse_workspace\siri-20-java\xsd\siri_vehicleMonitoring_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-VM Vehicle Monitoring Service.
All Element Summary (local elements unified by type)
AccessControl (in VehicleMonitoringServiceCapabilities)
Optional Access control capabilities.
Type:
anonymous complexType (extension of CapabilityAccessControlStructure)
Content:
complex, 4 elements
Defined:
Includes:
definitions of 3 elements
ChangeBeforeUpdates (type DurationType)
Type:
Content:
simple
Defined:
locally at 2 locations
CheckVehicleMonitoringRef (in AccessControl in VehicleMonitoringServiceCapabilities)
If access control is supported, whether access control by monitoring point is supported.
Type:
xsd:boolean
Content:
simple
Defined:
locally within AccessControl element; see XML source
DefaultDetailLevel (in RequestPolicy in VehicleMonitoringServiceCapabilities)
Detail level.
Type:
Content:
simple
Defined:
DefaultPreviewInterval (type PositiveDurationType)
Type:
Content:
simple
Defined:
locally at 8 locations
DirectionRef (type DirectionRefStructure)
Type:
Content:
simple
Defined:
locally at 20 locations
FilterByVehicleMonitoringRef (in TopicFiltering in VehicleMonitoringServiceCapabilities)
Whether results can be filtered by Vehicle Monitoring Fixed as 'true'.
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
HasLocation (in ResponseFeatures in VehicleMonitoringServiceCapabilities)
Whether result has location.
Type:
xsd:boolean
Content:
simple
Defined:
locally within ResponseFeatures element; see XML source
HasMaximumNumberOfCalls (in RequestPolicy in VehicleMonitoringServiceCapabilities)
If system can return detailed calling pattern, whether a number of calls to include can be specified.
Type:
xsd:boolean
Content:
simple
Defined:
HasMaximumVehicles (in RequestPolicy in VehicleMonitoringServiceCapabilities)
Whether results can be limited to a maximum number.
Type:
xsd:boolean
Content:
simple
Defined:
HasNames (type xsd:boolean)
Whether results should return references.
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
HasReferences (type xsd:boolean)
Whether results should return references.
Type:
xsd:boolean
Content:
simple
Defined:
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:language)
Type:
xsd:language
Content:
simple
Defined:
locally at 18 locations
LineRef (type LineRefStructure)
Type:
Content:
simple
Defined:
locally at 23 locations
MaximumNumberOfCalls (in VehicleMonitoringRequest)
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
MaximumVehicles (in VehicleMonitoringRequest)
The maximum number of MONITORED VEHICLE JOURNEYs to include in a given delivery.
Type:
xsd:positiveInteger
Content:
simple
Defined:
MonitoredVehicleJourney (in VehicleActivity)
Monitored VEHICLE JOURNEY that VEHICLE is following.
Type:
anonymous complexType (extension of MonitoredVehicleJourneyStructure)
Content:
empty
Defined:
MonitoringName (type NaturalLanguageStringStructure)
Type:
Content:
simple, 1 attribute
Defined:
locally at 2 locations
Onwards (type xsd:nonNegativeInteger)
Type:
xsd:nonNegativeInteger
Content:
simple
Defined:
locally at 2 locations
Previous (type xsd:nonNegativeInteger)
Type:
xsd:nonNegativeInteger
Content:
simple
Defined:
locally at 2 locations
ProgressBetweenStops (in VehicleActivity)
Provides information about the progress of the VEHICLE along its current link, that is link from previous visited top to current position.
Type:
Content:
complex, 2 elements
Defined:
Reason (type NaturalLanguageStringStructure)
Type:
Content:
simple, 1 attribute
Defined:
locally at 9 locations
RequestPolicy (in VehicleMonitoringServiceCapabilities)
Request Policy capabilities.
Type:
anonymous complexType (extension of CapabilityRequestPolicyStructure)
Content:
complex, 10 elements
Defined:
ResponseFeatures (in VehicleMonitoringServiceCapabilities)
Optional Response capabilities.
Type:
anonymous complexType
Content:
complex, 2 elements
Defined:
Includes:
definitions of 2 elements
SubscriptionPolicy (type CapabilitySubscriptionPolicyStructure)
Type:
Content:
complex, 2 elements
Defined:
locally at 9 locations
TopicFiltering (in VehicleMonitoringServiceCapabilities)
Topic Filtering Capabilities.
Type:
anonymous complexType
Content:
complex, 5 elements
Defined:
Includes:
definitions of 5 elements
UpdateInterval (in VehicleMonitoringSubscriptionRequest)
Time interval in seconds in which new data is to be transmitted.
Type:
Content:
simple
Defined:
ValidUntilTime (type xsd:dateTime)
Type:
xsd:dateTime
Content:
simple
Defined:
locally at 5 locations
VehicleActivity (in VehicleMonitoringDelivery)
Describes the progress of a VEHICLE along its route.
Type:
Content:
complex, 9 elements
Defined:
VehicleActivityCancellation (in VehicleMonitoringDelivery)
Reference to an previously communicated VEHICLE activity which should now be removed from the system.
Type:
Content:
complex, 16 elements
Defined:
VehicleActivityNote (type NaturalLanguageStringStructure)
Type:
Content:
simple, 1 attribute
Defined:
locally at 2 locations
VehicleJourneyRef (type FramedVehicleJourneyRefStructure)
Type:
Content:
complex, 2 elements
Defined:
locally at 6 locations
VehicleMonitoringCapabilitiesRequest
Request for information about Vehicle Monitoring Service Capabilities.
Type:
Content:
complex, 1 attribute, 4 elements
Subst.Gr:
Defined:
globally; see XML source
Used:
VehicleMonitoringCapabilitiesResponse
Capabilities for Vehicle Monitoring Service.
Type:
Content:
complex, 1 attribute, 9 elements
Subst.Gr:
Defined:
globally; see XML source
Used:
VehicleMonitoringDelivery
Delivery for Vehicle Monitoring Service.
Type:
Content:
complex, 1 attribute, 16 elements
Subst.Gr:
Defined:
globally; see XML source
Used:
VehicleMonitoringDetailLevel (in VehicleMonitoringRequest)
Level of detail to include in response.
Type:
Content:
simple
Defined:
VehicleMonitoringPermission (in VehicleMonitoringPermissions)
Permissions for use of VEHICLE MONITORING.
Type:
Content:
complex, 7 elements
Defined:
VehicleMonitoringPermissions
Participant's permissions to use the service.
Type:
anonymous complexType (extension of PermissionsStructure)
Content:
complex, 2 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
VehicleMonitoringPermissions (in VehicleMonitoringPermission)
The Vehicle Monitors (DIUSPLAY ASSIGNMENTs) that the participant may access.
Type:
anonymous complexType
Content:
complex, 2 elements
Defined:
Includes:
definitions of 2 elements
VehicleMonitoringRef (type VehicleMonitoringRefStructure)
Type:
Content:
simple
Defined:
locally at 4 locations
VehicleMonitoringRequest
Request for information about Vehicle Movements.
Type:
Content:
complex, 1 attribute, 13 elements
Subst.Gr:
Defined:
globally; see XML source
Used:
VehicleMonitoringServiceCapabilities
Capabilities of Vehicle Monitoring Service.
Type:
Content:
complex, 8 elements
Defined:
globally; see XML source
Used:
VehicleMonitoringSubscriptionRequest
Request for a subscription to the Vehicle Monitoring Service.
Type:
Content:
complex, 8 elements
Subst.Gr:
Defined:
globally; see XML source
Used:
VehicleMonitorPermission (in VehicleMonitoringPermissions in VehicleMonitoringPermission)
Participant's permission for this Vehicle Monitor (DISPLAY SSIGNMENT).
Type:
Content:
complex, 2 elements
Defined:
VehicleRef (type VehicleRefStructure)
Type:
Content:
simple
Defined:
locally at 2 locations
Complex Type Summary
Type for cancellation of an earlier Vehicle Activity.
Content:
complex, 16 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
Type for a Vehicle Activity.
Content:
complex, 9 elements
Defined:
globally; see XML source
Includes:
definitions of 7 elements
Used:
Type for Delivery for Vehicle Monitoring Service.
Content:
complex, 1 attribute, 9 elements
Defined:
globally; see XML source
Includes:
definitions of 1 attribute, 3 elements
Used:
Type for capability request policy.
Content:
complex, 6 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
never
Type for Deliveries for VEHICLE monitoring services Used in WSDL.
Content:
complex, 1 element
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
never
Type for Delivery for Vehicle Monitoring Service.
Content:
complex, 1 attribute, 16 elements
Defined:
globally; see XML source
Includes:
definitions of 1 attribute, 1 element
Used:
Type for reference to a Vehicle Monitoring scope
Content:
simple
Defined:
globally; see XML source
Used:
Type for Functional Service Request for Vehicle Monitoring Service.
Content:
complex, 1 attribute, 13 elements
Defined:
globally; see XML source
Includes:
definitions of 1 attribute, 1 element
Used:
Type for Vehicle Monitoring Capabilities.
Content:
complex, 8 elements
Defined:
globally; see XML source
Includes:
definitions of 6 elements
Used:
Type for Monitoring Service Permissions.
Content:
complex, 7 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
Type for Subscription Request for Vehicle Monitoring Service.
Content:
complex, 8 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
Type for MonitoringPoint Permission.
Content:
complex, 2 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
Simple Type Summary
Identifier of a Vehicle Monitoring scope.
Defined:
globally; see XML source
Used:
Detail Levels for Request.
Defined:
globally; see XML source
Used:
Element Group Summary
Convenience artifact to pick out main elements of the Vehicle Monitoring Service.
Content:
Defined:
globally; see XML source
Includes:
definitions of 5 elements
Used:
never
Identifiers of Vehicle Activity.
Content:
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
Payload part of Vehicle Monitoring delivery.
Content:
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
Parameters that affect the request processing.
Content:
Defined:
globally; see XML source
Includes:
definitions of 6 elements
Used:
Parameters that affect the subscription publishing and notification processing.
Content:
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
Parameters that specify the content to be returned.
Content:
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
Elements for volume control.
Content:
Defined:
globally; see XML source
Includes:
definitions of 6 elements
Used:
XML Source
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" id="siri_vehicleMonitoring_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>2007-03-26</Modified>
Drop separate flatten structure on response for VehicleActivity
</Date>
<Date>
<Modified>2008-11-17</Modified>
Revise to support substitution groups
</Date>
<Date>
<Modified>2012-03-23</Modified>
+SIRI v2.0

[MTA] Add MaximumNumberOfCalls to request
[SIRI-LITE] Allow a monitoring name in VehicleActivity results.
[VDV] Revise MonitoredVehicleJourney to include additional result files
[SIRI-LITE] Whether any related Situations should be included in the ServiceDelivery. Default is 'false'. +SIRI v2.0
</Date>
<Date>
<Modified>2012-04-29</Modified>
+SIRI v2.0

- [MTA]Modify MaximumNumberOfCalls to be consistent with SM
- [General] Add hasSItuations and hasMaximumNumberOfCalls to Capabilities
- [FR] Add Extensions tag to VehicleMonitoringSubscriptionRequest
</Date>
<Date>
<Modified>2013-02-11</Modified>
Revised VehicleActivityCancellationIdentityGroup making elements optional
</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 Vehicle 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/xsd/}siri_vehicleMonitoring_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_reference-v2.0.xsd
</Requires>
<Requires>
http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions-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-VM XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Vehicle Monitoring Subschema
</Title>
<Type>Standard</Type>
</Metadata>
</xsd:appinfo>
<xsd:documentation>SIRI-VM Vehicle 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:annotation>
<xsd:documentation>
Convenience artifact to pick out main elements of the Vehicle Monitoring Service.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="VehicleMonitoringRequest"/>
<xsd:element ref="VehicleMonitoringDelivery"/>
<xsd:sequence>
</xsd:sequence>
</xsd:sequence>
</xsd:group>
<!-- ====REQUESTS ====================================================== -->
<!-- ==== FS: Vehicle Monitoring Request========================================== -->
<xsd:annotation>
<xsd:documentation>Request for information about Vehicle Movements.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="VehicleMonitoringRequestStructure">
<xsd:annotation>
<xsd:documentation>
Type for Functional Service Request for Vehicle Monitoring Service.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractFunctionalServiceRequestStructure">
<xsd:sequence>
<xsd:group ref="VehicleMonitoringTopicGroup"/>
<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. Fixed
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:simpleType name="VehicleMonitoringDetailEnumeration">
<xsd:annotation>
<xsd:documentation>Detail Levels for 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 event to provide a display, A time, 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 event. Do not include data on time 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 arrival times at DESTINATION.
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="calls">
<xsd:annotation>
<xsd:documentation>
Return all available data for each stop event, including previous and onward CALLs with passing times for JOURNEY PATTERN.
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>
<xsd:group name="VehicleMonitoringTopicGroup">
<xsd:annotation>
<xsd:documentation>
Parameters that specify the content to be returned.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="VehicleMonitoringRef" type="VehicleMonitoringRefStructure">
<xsd:annotation>
<xsd:documentation>A predefined scope for making VEHICLE requests.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:choice minOccurs="0">
<xsd:element name="VehicleRef" type="VehicleRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to a specific VEHICLE about which data is requested.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="LineRef" type="LineRefStructure">
<xsd:annotation>
<xsd:documentation>
Filter the results to include only vehicles for the specific LINE.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
<xsd:element minOccurs="0" name="DirectionRef" type="DirectionRefStructure">
<xsd:annotation>
<xsd:documentation>
Filter the results to include only VEHICLEs going to this DIRECTION.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:annotation>
<xsd:documentation>Parameters that affect the request processing.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element default="en" minOccurs="0" name="Language" type="xsd:language">
<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="MaximumVehicles" type="xsd:positiveInteger">
<xsd:annotation>
<xsd:documentation>
The maximum number of MONITORED VEHICLE JOURNEYs to include in a given delivery. The most recent n Events within the look ahead window are included.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="VehicleMonitoringDetailLevel" type="VehicleMonitoringDetailEnumeration">
<xsd:annotation>
<xsd:documentation>Level of detail to include in response.</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. +SIRI v2.0.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element minOccurs="0" name="Previous" type="xsd:nonNegativeInteger">
<xsd:annotation>
<xsd:documentation>
Maximum number of previous calls to include. Only applies if VehicleMonitoringDetailLevel of Calls specified. Zero for none. If VehicleMonitoringDetailLevel of Calls specified but MaximumNumberOfCalls.Previous absent, include all previous calls. +SIRI v2.0.
</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. Zero for none. Only applies if VehicleMonitoringDetailLevel of 'calls' specified. Zero for none. If VehicleMonitoringDetailLevel calls specified but MaximumNumberOfCalls.Onwards absent, include all onwards calls. +SIRI v2.0.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</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:sequence>
</xsd:group>
<!-- ==== FS: Vehicle Monitoring Subscription Request===================================== -->
<xsd:annotation>
<xsd:documentation>
Request for a subscription to the Vehicle 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 will return the complete set of current data, or only provide updates to this data, i.e. additions, modifications and deletions.
If false or omitted, each subscription response will contain the full information as specified in this request.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:choice>
<xsd:element minOccurs="0" name="ChangeBeforeUpdates" type="DurationType">
<xsd:annotation>
<xsd:documentation>
The amount of change to the VEHICLE expected arrival time at next stop 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).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="UpdateInterval" type="PositiveDurationType">
<xsd:annotation>
<xsd:documentation>
Time interval in seconds in which new data is to be transmitted. If unspecified, default to system configuration.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
</xsd:sequence>
</xsd:group>
<xsd:annotation>
<xsd:documentation>
Type for Subscription Request for Vehicle Monitoring Service.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractSubscriptionStructure">
<xsd:sequence>
<xsd:element ref="VehicleMonitoringRequest"/>
<xsd:element minOccurs="0" ref="Extensions"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!-- ====RESPONSES=========================================================== -->
<!-- ==== FS: Vehicle Monitoring Delivery ===================================== -->
<xsd:annotation>
<xsd:documentation>Delivery for Vehicle Monitoring Service.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>Payload part of Vehicle Monitoring delivery.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="VehicleActivity" type="VehicleActivityStructure">
<xsd:annotation>
<xsd:documentation>
Describes the progress of a VEHICLE along its route.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="VehicleActivityCancellation" type="VehicleActivityCancellationStructure">
<xsd:annotation>
<xsd:documentation>
Reference to an previously communicated VEHICLE activity which should now be removed from the system.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="VehicleActivityNote" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>Annotation to accompany of Vehicle Activities.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:complexType name="VehicleMonitoringDeliveryStructure">
<xsd:annotation>
<xsd:documentation>
Type for Delivery for Vehicle Monitoring Service. Provides information about one or more vehicles; each has its own VEHICLE activity element.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractServiceDeliveryStructure">
<xsd:sequence>
<xsd:group ref="VehicleMonitoringPayloadGroup"/>
<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>
<!-- ====Data============================================================= -->
<xsd:complexType name="VehicleActivityStructure">
<xsd:annotation>
<xsd:documentation>Type for a Vehicle Activity.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractIdentifiedItemStructure">
<xsd:sequence>
<xsd:element name="ValidUntilTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>Time until when data is valid.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="VehicleMonitoringRef" type="VehicleMonitoringRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to monitored VEHICLE or GROUP OF VEHICLEs.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="MonitoringName" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
Name associated with Monitoring Reference. Supports SIRI LITE servcies (+SIRI v2.0).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="ProgressBetweenStops" type="ProgressBetweenStopsStructure">
<xsd:annotation>
<xsd:documentation>
Provides information about the progress of the VEHICLE along its current link, that is link from previous visited top to current position.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="MonitoredVehicleJourney">
<xsd:annotation>
<xsd:documentation>
Monitored VEHICLE JOURNEY that VEHICLE is following.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="MonitoredVehicleJourneyStructure"/>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="VehicleActivityNote" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>Text associated with Delivery.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="Extensions"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:simpleType name="VehicleMonitoringCodeType">
<xsd:annotation>
<xsd:documentation>Identifier of a Vehicle Monitoring scope.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN"/>
</xsd:simpleType>
<xsd:complexType name="VehicleMonitoringRefStructure">
<xsd:annotation>
<xsd:documentation>Type for reference to a Vehicle Monitoring scope</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="VehicleMonitoringCodeType"/>
</xsd:simpleContent>
</xsd:complexType>
<!-- ====Data============================================================= -->
<xsd:complexType name="VehicleActivityCancellationStructure">
<xsd:annotation>
<xsd:documentation>
Type for cancellation of an earlier Vehicle Activity.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractReferencingItemStructure">
<xsd:sequence>
<xsd:group ref="VehicleActivityCancellationIdentityGroup"/>
<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>Identifiers of Vehicle Activity.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="VehicleMonitoringRef" type="VehicleMonitoringRefStructure"/>
<xsd:element minOccurs="0" name="VehicleJourneyRef" type="FramedVehicleJourneyRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to VEHICLE JOURNEY that VEHICLE is making.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group minOccurs="0" ref="LineIdentityGroup"/>
</xsd:sequence>
</xsd:group>
<!-- ==== WSDL=========================================-->
<xsd:complexType name="VehicleMonitoringDeliveriesStructure">
<xsd:annotation>
<xsd:documentation>
Type for Deliveries for VEHICLE monitoring services Used in WSDL.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" ref="VehicleMonitoringDelivery">
<xsd:annotation>
<xsd:documentation>Delivery for Vehicle Moniroting Service.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<!-- ==== CS: Capability Request=================================================================== -->
<xsd:annotation>
<xsd:documentation>
Request for information about Vehicle Monitoring Service Capabilities. Answered with a VehicleMontoringCapabilitiesResponse.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>Type for capability request policy.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="CapabilityRequestPolicyStructure">
<xsd:sequence>
<xsd:element minOccurs="0" name="HasReferences" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>Whether results should return references.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="false" minOccurs="0" name="HasNames" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>Whether results should return references.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>Capabilities of Vehicle Monitoring Service.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<!-- ==== CS: Capability Response ================================================================== -->
<xsd:annotation>
<xsd:documentation>
Capabilities for Vehicle Monitoring Service. Answers a VehicleMontoringCapabilitiesRequest.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>Type for Delivery for Vehicle Monitoring Service.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractServiceCapabilitiesResponseStructure">
<xsd:sequence>
<xsd:element minOccurs="0" ref="VehicleMonitoringServiceCapabilities"/>
<xsd:element minOccurs="0" ref="VehicleMonitoringPermissions"/>
<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>Type for Vehicle Monitoring Capabilities.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractCapabilitiesStructure">
<xsd:sequence>
<xsd:element minOccurs="0" name="TopicFiltering">
<xsd:annotation>
<xsd:documentation>Topic 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 fixed="true" name="FilterByVehicleMonitoringRef" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether results can be filtered by Vehicle Monitoring Fixed as 'true'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="FilterByVehicleRef"/>
<xsd:element minOccurs="0" ref="FilterByLineRef"/>
<xsd:element minOccurs="0" ref="FilterByDirectionRef"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element minOccurs="0" name="RequestPolicy">
<xsd:annotation>
<xsd:documentation>Request Policy capabilities.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="CapabilityRequestPolicyStructure">
<xsd:sequence>
<xsd:group ref="VehicleMonitoringVolumeGroup"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element minOccurs="0" name="SubscriptionPolicy" type="CapabilitySubscriptionPolicyStructure">
<xsd:annotation>
<xsd:documentation>Subscription Policy capabilities.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="AccessControl">
<xsd:annotation>
<xsd:documentation>Optional Access control capabilities.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="CapabilityAccessControlStructure">
<xsd:sequence>
<xsd:element minOccurs="0" ref="CheckOperatorRef"/>
<xsd:element minOccurs="0" ref="CheckLineRef"/>
<xsd:element default="true" minOccurs="0" name="CheckVehicleMonitoringRef" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
If access control is supported, whether access control by monitoring point is supported. Default is 'true'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element minOccurs="0" name="ResponseFeatures">
<xsd:annotation>
<xsd:documentation>Optional Response capabilities.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element default="true" minOccurs="0" name="HasLocation" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>Whether result has location. 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:element minOccurs="0" ref="Extensions"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:group name="VehicleMonitoringVolumeGroup">
<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="VehicleMonitoringDetailEnumeration">
<xsd:annotation>
<xsd:documentation>Detail level. Default Normal.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="true" minOccurs="0" name="HasMaximumVehicles" 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="false" minOccurs="0" name="HasMaximumNumberOfCalls" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
If system can return detailed calling pattern, whether a number of calls to include can be specified. Default is 'false'. +SIRI 2.0
</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'. +SIRI 2.0
</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 previous calls to include can be specified. Default is 'false'. +SIRI 2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:element name="VehicleMonitoringPermissions">
<xsd:annotation>
<xsd:documentation>Participant's permissions to use the service.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="PermissionsStructure">
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="VehicleMonitoringPermission" type="VehicleMonitoringServicePermissionStructure">
<xsd:annotation>
<xsd:documentation>
Permissions for use of VEHICLE MONITORING. Can be used to specify which Consumers can see which vehicles
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<!-- ====permissions=================================================================== -->
<xsd:annotation>
<xsd:documentation>Type for Monitoring Service Permissions.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractPermissionStructure">
<xsd:sequence>
<xsd:element ref="OperatorPermissions"/>
<xsd:element ref="LinePermissions"/>
<xsd:element name="VehicleMonitoringPermissions">
<xsd:annotation>
<xsd:documentation>
The Vehicle Monitors (DIUSPLAY ASSIGNMENTs) that the participant may access.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:choice>
<xsd:element ref="AllowAll"/>
<xsd:element maxOccurs="unbounded" name="VehicleMonitorPermission" type="VehicleMonitorPermissionStructure">
<xsd:annotation>
<xsd:documentation>
Participant's permission for this Vehicle Monitor (DISPLAY SSIGNMENT).
</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:complexType name="VehicleMonitorPermissionStructure">
<xsd:annotation>
<xsd:documentation>Type for MonitoringPoint Permission.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractTopicPermissionStructure">
<xsd:sequence>
<xsd:element name="VehicleMonitoringRef" type="VehicleMonitoringRefStructure">
<xsd:annotation>
<xsd:documentation>
Vehicle Monitoring reference for which permission is made.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</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/