XML Schema "siri_stopTimetable_service.xsd"
Target Namespace:
http://www.siri.org.uk/siri
Version:
2.0
Defined Components:
elements (7 global + 20 local), complexTypes (10), element groups (5)
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
C:\Users\Tony\eclipse_workspace\siri-20-java\xsd\siri_stopTimetable_service.xsd; see XML source
Includes Schemas (3):
siri_modelPermissions-v2.0.xsd [src], siri_requests-v2.0.xsd [src], siri_targetedVehicleJourney-v2.0.xsd [src]
Included in Schemas (1):
siri_all_functionalServices.xsd [src]
Annotation
SIRI-ST Stop Timetable Service.
All Element Summary (local elements unified by type)
AccessControl (in StopTimetableServiceCapabilities)
Access control that can be used.
Type:
anonymous complexType (extension of CapabilityAccessControlStructure)
Content:
complex, 4 elements
Defined:
locally within StopTimetableServiceCapabilitiesStructure complexType; see XML source
Includes:
definitions of 3 elements
ChangeBeforeUpdates (type PositiveDurationType)
Type:
PositiveDurationType
Content:
simple
Defined:
locally at 4 locations
DepartureWindow (in StopTimetableRequest)
Earliest and latest departure time.
Type:
ClosedTimestampRangeStructure
Content:
complex, 2 elements
Defined:
locally within StopTimetableTopicGroup group; see XML source
DirectionRef (type DirectionRefStructure)
Type:
DirectionRefStructure
Content:
simple
Defined:
locally at 20 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:
LineRefStructure
Content:
simple
Defined:
locally at 23 locations
MonitoringRef (type MonitoringRefStructure)
Type:
MonitoringRefStructure
Content:
simple
Defined:
locally at 12 locations
Reason (type NaturalLanguageStringStructure)
Type:
NaturalLanguageStringStructure
Content:
simple, 1 attribute
Defined:
locally at 9 locations
RequestPolicy (in StopTimetableServiceCapabilities)
Available request policy options.
Type:
StopTimetableCapabilityRequestPolicyStructure
Content:
complex, 6 elements
Defined:
locally within StopTimetableServiceCapabilitiesStructure complexType; see XML source
StopMonitorPermission (type StopMonitorPermissionStructure)
Type:
StopMonitorPermissionStructure
Content:
complex, 2 elements
Defined:
locally at 2 locations
StopMonitorPermissions (in StopTimetablePermission)
The monitoring points that the participant may access.
Type:
anonymous complexType
Content:
complex, 2 elements
Defined:
locally within StopTimetableServicePermissionStructure complexType; see XML source
Includes:
definitions of 2 elements
StopTimetableCapabilitiesRequest
Request for information about Stop Timetable Service Capabilities Answered with a StopTimetableCapabilitiesResponse.
Type:
ServiceCapabilitiesRequestStructure
Content:
complex, 1 attribute, 4 elements
Subst.Gr:
may substitute for elements: AbstractFunctionalServiceCapabilitiesRequest, AbstractServiceRequest, AbstractRequest
Defined:
globally; see XML source
Used:
at 2 locations
StopTimetableCapabilitiesResponse
Delivery for Stop Timetable Service.
Type:
StopTimetableCapabilitiesResponseStructure
Content:
complex, 1 attribute, 9 elements
Subst.Gr:
may substitute for elements: AbstractFunctionalServiceCapabilitiesResponse, AbstractResponse
Defined:
globally; see XML source
Used:
at 2 locations
StopTimetableDelivery
Delivery for Stop Timetable Service.
Type:
StopTimetableDeliveryStructure
Content:
complex, 1 attribute, 15 elements
Subst.Gr:
may substitute for elements: AbstractFunctionalServiceDelivery, AbstractResponse
Defined:
globally; see XML source
Used:
at 3 locations
StopTimetablePermission (in StopTimetablePermissions)
Permission for a single participant or all participants to use an aspect of the service.
Type:
StopTimetableServicePermissionStructure
Content:
complex, 7 elements
Defined:
locally within StopTimetablePermissions element; see XML source
StopTimetablePermissions
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:
at 1 location
StopTimetableRequest
Request for information about Stop Visits, i.e. arrival and departure at a stop.
Type:
StopTimetableRequestStructure
Content:
complex, 1 attribute, 9 elements
Subst.Gr:
may substitute for elements: AbstractFunctionalServiceRequest, AbstractServiceRequest, AbstractRequest
Defined:
globally; see XML source
Used:
at 3 locations
StopTimetableServiceCapabilities
Capabilities of Stop Timetable Service.
Type:
StopTimetableServiceCapabilitiesStructure
Content:
complex, 6 elements
Defined:
globally; see XML source
Used:
at 1 location
StopTimetableSubscriptionRequest
Request for a subscription to Stop TimetablesService.
Type:
StopTimetableSubscriptionStructure
Content:
complex, 7 elements
Subst.Gr:
may substitute for element AbstractFunctionalServiceSubscriptionRequest
Defined:
globally; see XML source
Used:
at 2 locations
TimetabledStopVisit (in StopTimetableDelivery)
A visit to a stop by a VEHICLE as an arrival and /or departure, as timetabled in the production timetable.
Type:
TimetabledStopVisitStructure
Content:
complex, 5 elements
Defined:
locally within StopTimetablePayloadGroup group; see XML source
TimetabledStopVisitCancellation (in StopTimetableDelivery)
A cancellation of a previously issued TimetabledStopVisit.
Type:
TimetabledStopVisitCancellationStructure
Content:
complex, 17 elements
Defined:
locally within StopTimetablePayloadGroup group; see XML source
TopicFiltering (in StopTimetableServiceCapabilities)
Available Filtering Capabilities.
Type:
anonymous complexType
Content:
complex, 3 elements
Defined:
locally within StopTimetableServiceCapabilitiesStructure complexType; see XML source
Includes:
definitions of 3 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
Complex Type Summary
StopTimetableCapabilitiesResponseStructure
Type for Delivery for Stop Timetable Service.
Content:
complex, 1 attribute, 9 elements
Defined:
globally; see XML source
Includes:
definitions of 1 attribute, 3 elements
Used:
at 1 location
StopTimetableCapabilityRequestPolicyStructure
Type for Monitoring Service Capability Request Policy.
Content:
complex, 6 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
at 1 location
StopTimetableDeliveriesStructure
Type for stop timetable deliveries.
Content:
complex, 1 element
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
never
StopTimetableDeliveryStructure
Data type Delivery for Stop Timetable Service.
Content:
complex, 1 attribute, 15 elements
Defined:
globally; see XML source
Includes:
definitions of 1 attribute, 1 element
Used:
at 1 location
StopTimetableRequestStructure
Type for Functional Service Request for Stop Timetables.
Content:
complex, 1 attribute, 9 elements
Defined:
globally; see XML source
Includes:
definitions of 1 attribute, 1 element
Used:
at 1 location
StopTimetableServiceCapabilitiesStructure
Type for Capabilities of Stop Timetable Service.
Content:
complex, 6 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
at 1 location
StopTimetableServicePermissionStructure
Type for Monitoring Service Permission.
Content:
complex, 7 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
at 1 location
StopTimetableSubscriptionStructure
Subscription Request for Stop Timetables.
Content:
complex, 7 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
at 1 location
TimetabledStopVisitCancellationStructure
Type for Cancellation of Timetabled Visit of a VEHICLE to a stop.
Content:
complex, 17 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
at 1 location
TimetabledStopVisitStructure
Type for Timetabled Visit of a VEHICLE to a stop.
Content:
complex, 5 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
at 1 location
Element Group Summary
SiriStopTimetableIndexGroup
Convenience artifact to pick out main elements of the Stop Timetable Service.
Content:
5 elements
Defined:
globally; see XML source
Includes:
definitions of 5 elements
Used:
never
StopTimetablePayloadGroup
Payload part of Stop Timetable delivery.
Content:
2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
at 1 location
StopTimetableRequestPolicyGroup
Parameters that affect the request processing.
Content:
2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
at 1 location
StopTimetableSubscriptionPolicyGroup
Parameters that affect the subscription publishing and notification processing.
Content:
2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
at 1 location
StopTimetableTopicGroup
Parameters that specify the content to be returned.
Content:
4 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
at 1 location
XML Source
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" id="siri_stopTimetable_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>2005-12-12</Modified>
2005 12 07 Correct Spelling of StopMonitorPermissionTag
</Date>
<Date>
<Modified>2007-04-17</Modified>
Name Space changes
</Date>
<Date>
<Modified>2007-03-26</Modified>
Drop separate flatten structure on response for stopVisit
</Date>
<Date>
<Modified>2008-11-17</Modified>
Revise to support substitution groups
</Date>
<Date>
<Modified>2012-03-23</Modified>
+SIRI v2.0
Improve modualirisatuioin
Factor out permissions to commomn files
factor out targeted journey,
create separate structure for StopTimetablePermissionStructure
create separate structure for StopTimetableCapabilityRequestPolicyStructure
</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 Timetable 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_stopTmetable_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>
<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 XML schema. Service Interface for Real-time Information. Subschema for Stop Timetable Service.
</Title>
<Type>Standard</Type>
</Metadata>
</xsd:appinfo>
<xsd:documentation>SIRI-ST Stop Timetable Service.</xsd:documentation>
</xsd:annotation>
<!-- ======================================================================= -->
<xsd:include schemaLocation="siri/siri_requests-v2.0.xsd"/>
<xsd:include schemaLocation="siri_model/siri_targetedVehicleJourney-v2.0.xsd"/>
<xsd:include schemaLocation="siri_model/siri_modelPermissions-v2.0.xsd"/>
<xsd:group name="SiriStopTimetableIndexGroup">
<xsd:annotation>
<xsd:documentation>
Convenience artifact to pick out main elements of the Stop Timetable Service.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="StopTimetableRequest"/>
<xsd:element ref="StopTimetableDelivery"/>
<xsd:sequence>
<xsd:element ref="StopTimetableCapabilitiesRequest"/>
</xsd:sequence>
</xsd:sequence>
</xsd:group>
<xsd:annotation>
<xsd:documentation>
Request for information about Stop Visits, i.e. arrival and departure at a stop.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<!-- ====REQUESTS ====================================================== -->
<!-- ==== FS: Stop Timetable Request ============================================ -->
<xsd:complexType name="StopTimetableRequestStructure">
<xsd:annotation>
<xsd:documentation>
Type for Functional Service Request for Stop Timetables.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractFunctionalServiceRequestStructure">
<xsd:sequence>
<xsd:group ref="StopTimetableTopicGroup"/>
<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:group name="StopTimetableTopicGroup">
<xsd:annotation>
<xsd:documentation>
Parameters that specify the content to be returned.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="DepartureWindow" type="ClosedTimestampRangeStructure">
<xsd:annotation>
<xsd:documentation>
Earliest and latest departure time. If absent, default to the data horizon of the service.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="MonitoringRef" type="MonitoringRefStructure">
<xsd:annotation>
<xsd:documentation>
The stop monitoring point about which data is requested. May be a STOP POINT, timing point or other display point.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="LineRef" type="LineRefStructure">
<xsd:annotation>
<xsd:documentation>
Filter the results to include only data for journeys 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 data for journeys running in a specific relative DIRECTION, for example, "inbound" or "outbound".
</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="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:sequence>
</xsd:group>
<!-- ==== FS: Stop Timetable Subscription Request ===================================== -->
<xsd:annotation>
<xsd:documentation>
Request for a subscription to Stop TimetablesService.
</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="StopTimetableSubscriptionStructure">
<xsd:annotation>
<xsd:documentation>Subscription Request for Stop Timetables.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractSubscriptionStructure">
<xsd:sequence>
<xsd:element ref="StopTimetableRequest"/>
<xsd:element minOccurs="0" ref="Extensions"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!-- ====RESPONSES=========================================================== -->
<!-- ==== FS: Stop Timetable Delivery ============================================ -->
<xsd:annotation>
<xsd:documentation>Delivery for Stop Timetable Service.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="StopTimetableDeliveryStructure">
<xsd:annotation>
<xsd:documentation>Data type Delivery for Stop Timetable Service.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractServiceDeliveryStructure">
<xsd:sequence>
<xsd:group ref="StopTimetablePayloadGroup"/>
<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="StopTimetablePayloadGroup">
<xsd:annotation>
<xsd:documentation>Payload part of Stop Timetable delivery.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="TimetabledStopVisit" type="TimetabledStopVisitStructure">
<xsd:annotation>
<xsd:documentation>
A visit to a stop by a VEHICLE as an arrival and /or departure, as timetabled in the production timetable.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="TimetabledStopVisitCancellation" type="TimetabledStopVisitCancellationStructure">
<xsd:annotation>
<xsd:documentation>
A cancellation of a previously issued TimetabledStopVisit.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<!-- ===== Stop Visit ================================================ -->
<xsd:complexType name="TimetabledStopVisitStructure">
<xsd:annotation>
<xsd:documentation>
Type for Timetabled Visit of a VEHICLE to a stop. May provide information about the arrival, the departure or both.
</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 / LOGICAL DISPLAY to which Stop Visit applies.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="TargetedVehicleJourney"/>
<xsd:element minOccurs="0" ref="Extensions"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
Type for Cancellation of Timetabled Visit of a VEHICLE to a stop. May provide information about the arrival, the departure or both.
</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 Stop Visit applies.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="VisitNumber"/>
<xsd:group ref="JourneyIdentityGroup"/>
<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>
<!-- ======================================================================= -->
<!-- ==== WSDL=========================================-->
<xsd:complexType name="StopTimetableDeliveriesStructure">
<xsd:annotation>
<xsd:documentation>Type for stop timetable deliveries. Used in WSDL.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="StopTimetableDelivery"/>
</xsd:sequence>
</xsd:complexType>
<!-- ====Capability Request=================================================================== -->
<!-- ======================================================================= -->
<!-- ====CS: Capability Request =================================================================== -->
<xsd:annotation>
<xsd:documentation>
Request for information about Stop Timetable Service Capabilities Answered with a StopTimetableCapabilitiesResponse.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<!-- ====CS: Capability Response =================================================================== -->
<xsd:annotation>
<xsd:documentation>
Delivery for Stop Timetable Service. Answers a StopTimetableCapabilitiesRequest.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>Type for Delivery for Stop Timetable Service.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractServiceCapabilitiesResponseStructure">
<xsd:sequence>
<xsd:element minOccurs="0" ref="StopTimetableServiceCapabilities"/>
<xsd:element minOccurs="0" ref="StopTimetablePermissions"/>
<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 Stop Timetable Service.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>Type for Capabilities of Stop Timetable Service.</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 ref="FilterByMonitoringRef"/>
<xsd:element ref="FilterByLineRef"/>
<xsd:element minOccurs="0" ref="FilterByDirectionRef"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element minOccurs="0" name="RequestPolicy" type="StopTimetableCapabilityRequestPolicyStructure">
<xsd:annotation>
<xsd:documentation>Available request policy options.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="AccessControl">
<xsd:annotation>
<xsd:documentation>Access control that can be used.</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 minOccurs="0" ref="CheckMonitoringRef"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element minOccurs="0" ref="Extensions"/>
</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>
<xsd:element name="StopTimetablePermissions">
<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="StopTimetablePermission" type="StopTimetableServicePermissionStructure">
<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>
<!-- ======================================================================= -->
<!-- ====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/