XML Schema "siri.xsd"
Target Namespace:
http://www.siri.org.uk/siri
Version:
2.0
Defined Components:
elements (6 global + 2 local), complexTypes (8), element groups (13)
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
C:\Users\Tony\eclipse_workspace\siri-20-java\xsd\siri.xsd; see XML source
Includes Schemas (2):
siri_all_functionalServices.xsd [src], siri_common_services-v2.0.xsd [src]
Annotation
SIRI Service Interface for Real-time Information relating to Public Transport Operations. - XML Schema with explicit functional services
All Element Summary
Address (type EndpointAddress)
Type:
Content:
simple
Defined:
locally at 6 locations
CapabilitiesRequest
Requests a the current capabilities of the server.
Type:
Content:
complex, 1 attribute, 17 elements
Defined:
globally; see XML source
Used:
CapabilitiesResponse
Responses with the capabilities of an implementation.
Type:
Content:
complex, 1 attribute, 17 elements
Defined:
globally; see XML source
Used:
MoreData (type xsd:boolean)
Type:
xsd:boolean
Content:
simple
Defined:
locally at 2 locations
ServiceDelivery
Response from Producer to Consumer to deliver payload data.
Type:
anonymous complexType (extension of ServiceDeliveryStructure)
Content:
complex, 1 attribute, 21 elements
Defined:
globally; see XML source
Used:
ServiceRequest
Request from Consumer to Producer for immediate delivery of data.
Type:
anonymous complexType (extension of ServiceRequestStructure)
Content:
complex, 20 elements
Defined:
globally; see XML source
Used:
Siri
SIRI Service Interface for Real-time Operation.
Type:
anonymous complexType
Content:
complex, 1 attribute, 33 elements
Defined:
globally; see XML source
Includes:
definitions of 1 attribute, 1 element
Used:
never
SubscriptionRequest
Request from Subscriber to Producer for a subscription.
Type:
anonymous complexType (extension of SubscriptionRequestStructure)
Content:
complex, 21 elements
Defined:
globally; see XML source
Used:
Complex Type Summary
Type for Requests for capabilities of the current system.
Content:
complex, 1 attribute, 17 elements
Defined:
globally; see XML source
Includes:
definitions of 1 attribute, 2 elements
Used:
Type for the capabilities of an implementation.
Content:
complex, 1 attribute, 17 elements
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
Type for SIRI Service Delivery Body..
Content:
complex, 1 attribute, 14 elements
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
never
Type for SIRI Service Delivery.
Content:
complex, 1 attribute, 21 elements
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
SIRI Service Request.
Content:
complex, 20 elements
Defined:
globally; see XML source
Used:
Type for a SIRI SIRI Functional Service Delivery types.Used for WSDL.
Content:
complex, 11 elements
Defined:
globally; see XML source
Used:
never
Type for SIRI Functional Service Subscription types.
Content:
complex, 10 elements
Defined:
globally; see XML source
Used:
never
Type for SIRI Subscription Request.
Content:
complex, 21 elements
Defined:
globally; see XML source
Used:
Element Group Summary
Responses that deliver payload content.
Content:
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
SIRI All Requests.
Content:
Defined:
globally; see XML source
Used:
SIRI Service Responses.
Content:
Defined:
globally; see XML source
Used:
Elements for SIRI Service Delivery.
Content:
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
Requests for service provision.
Content:
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
Responses to requests other than deliveries and status information.
Content:
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
Requests for reference data for use in SIRI Functional Service requests.
Content:
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
Responses with reference data for use in SIRI Functional Service requests.
Content:
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
Defines the capabilities of an individual SIRI service request functions.
Content:
Defined:
globally; see XML source
Includes:
definitions of 10 elements
Used:
Defines the capabilities of an individual SIRI service response functions.
Content:
Defined:
globally; see XML source
Includes:
definitions of 10 elements
Used:
SIRI Functional Service Delivery types.
Content:
Defined:
globally; see XML source
Includes:
definitions of 11 elements
Used:
SIRI Functional Service Concrete Requests.
Content:
Defined:
globally; see XML source
Includes:
definitions of 11 elements
Used:
SIRI Functional Service Subscription types.
Content:
Defined:
globally; see XML source
Includes:
definitions of 10 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" 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>
<!-- SIRI v1.0 -->
<Contributor>
Dipl.-Kfm. Winfried Bruns, Verband Deutscher, Köln, de v1.0
</Contributor>
<Contributor>
Mark Cartwright, Centaur Consulting Limited, Guildford, uk v1.0
</Contributor>
<Contributor>
Christophe Duquesne, PDG Consultant en systémes, Dryade Guyancourt, fr v1.0
</Contributor>
<Contributor>
Stefan Fjällemark, HUR - Hovedstadens, Valby, dk v1.0
</Contributor>
<Contributor>Jonas Jäderberg, Columna, Borlänge, fi v1.0</Contributor>
<Contributor>
Dipl.-Ing. Sven Juergens psitrans juergens@psitrans.de v1.0
</Contributor>
<Contributor>
Nicholas Knowles, KIZOOM Limited, London EC4A 1LT, uk v1.0
</Contributor>
<Contributor>
Werner Kohl, Mentz Datenverarbeitung GmbH, München,de v1.0
</Contributor>
<Contributor>
Peter Miller, ACIS Research and Development, Cambridge CB4 0DL, uk v1.0
</Contributor>
<Contributor>
Dr. Martin Siczkowski, West Yorkshire PTE, Leeds, uk v1.0
</Contributor>
<Contributor>Gustav Thiessen BLIC thi@BLIC.DE, de v1.0</Contributor>
<Contributor>Dr Bartak, bartak@apex-jesenice.cz v1.0</Contributor>
<Contributor>
Dr. Franz-Josef Czuka, Beratungsgesellschaft für, Düsseldorf, de v1.0
</Contributor>
<Contributor>
Dr.-Ing. Klaus-Peter Heynert, PSI Transportation GmbH, Berlin, de v1.0
</Contributor>
<Contributor>
Jean-Laurant Franchineau, CONNEX-EUROLUM, PARIS, fr v1.0
</Contributor>
<Contributor>
Dipl.-Ing. (FH) Rainer Ganninger, init innovation in, Karlsruhe, de v1.0
</Contributor>
<Contributor>
Dipl.-Ing. HTL Peter Machalek, Siemens Transit, Neuhausen am Rheinfall, ch v1.0
</Contributor>
<Contributor>
El Ing. Ernst Pfister, Siemens Transit, Neuhausen am Rheinfall, ch v1.0
</Contributor>
<Contributor>
Dipl.-Ing. Berthold Radermacher, Verband Deutscher, Köln, de v1.0
</Contributor>
<Contributor>
Dr. Friedemann Weik, Hamburger Berater Team GmbH, Hamburg, de v1.0
</Contributor>
<!-- Fixes and feed back -->
<Contributor>Robin Vettier, ixxi.com, fr v1.3</Contributor>
<Contributor>Ofer Porat, fr v1.3</Contributor>
<Contributor>Burt Alexander', sigtec.com</Contributor>
<Contributor>Michelle Etienne, Dryade, Paris fr, v1.3</Contributor>
<Contributor>Brian Ferris onebusaway.org, us, v1.3</Contributor>
<Contributor>Manuem Mahne Siemens.com</Contributor>
<!--SIRI v2.0 -->
<Contributor>Ulf Bjersing, Hogia - Stenungsgrund, se v2.0</Contributor>
<Contributor>
Dipl.-Math Christoph Blendinger, DB, Frankfort, de v2.0
</Contributor>
<Contributor>
Dipl.-Kfm. Winfried Bruns, Verband Deutscher, Köln, de v2.0
</Contributor>
<Contributor>
Christophe Duquesne, PDG Consultant en systémes, Auriga, fr v2.0
</Contributor>
<Contributor>
Gerald Dury, Trapeze Neuhausen am Rhein, ch, fr v2.0
</Contributor>
<Contributor>Michelle Etienne, Dryade, Paris fr v2.0</Contributor>
<Contributor>Michael Frumin, MTA, us, v2.0</Contributor>
<Contributor>
Nicholas Knowles, Trapeze Limited, London, uk v2.0
</Contributor>
<Contributor>
Werner Kohl, Mentz Datenverarbeitung GmbH, München, de v2.0
</Contributor>
<Contributor>Davide Lallouche, RATP, Paris, fr v2.0</Contributor>
<Contributor>Jeff Maki, us, v2.0</Contributor>
<Contributor>
Daniel Rubli, Trapeze Neuhausen am Rhein, ch, fr v2.0
</Contributor>
<Contributor>Gustav Thiessen BLIC thi@BLIC.DE, de 2.0 v1.0</Contributor>
<Coverage>Europe</Coverage>
<Creator>
&gt;Drafted for version 1.0 &amp; Version 2.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-02-02</Modified>
</Date>
<Date>
<Modified>2007-04-17</Modified>
Name Space changes
</Date>
<Date>
<Modified>2008-11-17</Modified>
Change to use common 1_2. Add in mussing StopMonitoringMultipelRequest
Rename groups to identify common SIRI elements
</Date>
<Date>
<Modified>2009-03-03</Modified>
Corrrect cardinality on facility and Service Monitoring Delivery request
</Date>
<Date>
<Modified>2011-04-18</Modified>
Updated journey, request and other subpackages - see readme
</Date>
<Date>
<Modified>2012-03-23</Modified>
SIRI Version 2.0
Model subpackages Refactored to improve modularisation.
[SIRI-LITE] Add authentication Key
See Readme.txt for list of changes
</Date>
<Date>
<Modified>2012-05-18</Modified>
SIRI Version 2.0
Correct error in SituationExchangeCapabilitiesReponse include
</Date>
<Date>
<Modified>2012-08-01</Modified>
SIRI Version 2.0
Correct delegation elements
</Date>
<Date>
<Modified>2014-03-31</Modified>
+SIRI v2.0 Comments
- Add terminate subscription notification
</Date>
<Description>
<p>
SIRI is a European CEN technical standard for the exchange of real-time information.
</p>
<p>
SIRI is defined by XMLschemas and comprises a general protocol for communication, and a modular set of functional services as follows :
<ul>
<li>
SIRI-PT Production Timetable: Exchanges planned timetables.
</li>
<li>
SIRI-ET Estimated Timetable: Exchanges real-time updates to timetables.
</li>
<li>
SIRI-ST Stop Timetable: Provides timetable information about stop departures and arrivals.
</li>
<li>
SIRI-SM Stop Monitoring: Provides real-time information about stop departures and arrivals.
</li>
<li>
SIRI-VM Vehicle Monitoring: Provides real-time information about VEHICLE movements.
</li>
<li>
SIRI-CT Connection Timetable: Provides timetabled information about feeder and distributor arrivals and departures at a connection point.
</li>
<li>
SIRI-VM Connection Monitoring: Provides real-time information about feeder and distributor arrivals and departures at a a connection point. Can be used to support "Connection protection".
</li>
<li>
SIRI-GM General Message: Exchanges general information messages between participants
</li>
<li>
SIRI-FM Facility Monitoring: Provides real-time information about facilities.
</li>
<li>
SIRI-SX Situation Exchange: Provides real-time information about Incidents.
</li>
</ul>
</p>
<p>
SIRI supports both direct request/response and publish subscribe patterns of interaction.
</p>
<p>
SIRI includes common mechanisms and messages for system status management.
</p>
<p>
SIRI documents can be exchanged using http post, and/or SOAP.
</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.xsd</Identifier>
<Language>[ISO 639-2/B] ENG</Language>
<Publisher>
Kizoom Software Ltd 16 High Holborn, London WC1V 6BX
</Publisher>
<Relation>
<Requires>
http://www.siri.org.uk/schema/2.0/xsd/siri__common_services.xsd
</Requires>
<Requires>
http://www.siri.org.uk/schema/2.0/xsd/siri__estimatedTimetable_service.xsd
</Requires>
<Requires>
http://www.siri.org.uk/schema/2.0/xsd/siri__productionTimetable_service.xsd
</Requires>
<Requires>
http://www.siri.org.uk/schema/2.0/xsd/siri__stopMonitoring_service.xsd
</Requires>
<Requires>
http://www.siri.org.uk/schema/2.0/xsd/siri__vehicleMonitoring_service.xsd
</Requires>
<Requires>
http://www.siri.org.uk/schema/2.0/xsd/siri__connectionTimetable_service.xsd
</Requires>
<Requires>
http://www.siri.org.uk/schema/2.0/xsd/siri__connectionMonitoring_service.xsd
</Requires>
<Requires>
http://www.siri.org.uk/schema/2.0/xsd/siri__generalMessage_service.xsd
</Requires>
<Requires>
http://www.siri.org.uk/schema/2.0/xsd/siri__discovery.xsd
</Requires>
<Requires>
http://www.siri.org.uk/schema/2.0/xsd/siri__situationExchange_service.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 Version with cumulative fixes</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 relating to Public Transport Operations.
</Title>
<Type>Standard</Type>
</Metadata>
</xsd:appinfo>
<xsd:documentation>
SIRI Service Interface for Real-time Information relating to Public Transport Operations. - XML Schema with explicit functional services
</xsd:documentation>
</xsd:annotation>
<!-- ======================================================================= -->
<xsd:include schemaLocation="siri/siri_common_services-v2.0.xsd"/>
<xsd:include schemaLocation="siri_all_functionalServices.xsd"/>
<!-- ======================================================================= -->
<xsd:element name="Siri">
<xsd:annotation>
<xsd:documentation>SIRI Service Interface for Real-time Operation.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:choice>
<xsd:group ref="RequestGroup"/>
<xsd:group ref="ResponseGroup"/>
<xsd:element minOccurs="0" ref="Extensions"/>
</xsd:choice>
<xsd:attribute default="2.0" name="version" type="VersionString"/>
</xsd:complexType>
</xsd:element>
<!--== Requests ===================================================================== -->
<xsd:group name="RequestGroup">
<xsd:annotation>
<xsd:documentation>SIRI All Requests.</xsd:documentation>
</xsd:annotation>
<xsd:choice>
<xsd:group ref="ServiceRequestGroup"/>
<xsd:group ref="DeliveryRequestGroup"/>
<xsd:group ref="StatusRequestGroup"/>
<xsd:group ref="SiriDiscoveryRequestGroup"/>
</xsd:choice>
</xsd:group>
<!-- ===GS: ServceRequest================================================ -->
<xsd:element name="ServiceRequest">
<xsd:annotation>
<xsd:documentation>
Request from Consumer to Producer for immediate delivery of data. Answered with a ServiceDelivery (or a DataReadyRequest)
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="ServiceRequestStructure"/>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:group name="ServiceRequestGroup">
<xsd:annotation>
<xsd:documentation>Requests for service provision.</xsd:documentation>
</xsd:annotation>
<xsd:choice>
<xsd:element ref="ServiceRequest"/>
<xsd:element ref="SubscriptionRequest"/>
<xsd:element ref="TerminateSubscriptionRequest"/>
</xsd:choice>
</xsd:group>
<xsd:complexType name="ServiceRequestStructure">
<xsd:annotation>
<xsd:documentation>SIRI Service Request.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ContextualisedRequestStructure">
<xsd:group ref="SiriServiceRequestGroup"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:group name="SiriServiceRequestGroup">
<xsd:annotation>
<xsd:documentation>SIRI Functional Service Concrete Requests.</xsd:documentation>
</xsd:annotation>
<xsd:choice>
<xsd:element maxOccurs="unbounded" ref="ProductionTimetableRequest"/>
<xsd:element maxOccurs="unbounded" ref="EstimatedTimetableRequest"/>
<xsd:element maxOccurs="unbounded" ref="StopTimetableRequest"/>
<xsd:element maxOccurs="unbounded" ref="StopMonitoringMultipleRequest"/>
<xsd:element maxOccurs="unbounded" ref="StopMonitoringRequest"/>
<xsd:element maxOccurs="unbounded" ref="VehicleMonitoringRequest"/>
<xsd:element maxOccurs="unbounded" ref="ConnectionTimetableRequest"/>
<xsd:element maxOccurs="unbounded" ref="ConnectionMonitoringRequest"/>
<xsd:element maxOccurs="unbounded" ref="GeneralMessageRequest"/>
<xsd:element maxOccurs="unbounded" ref="FacilityMonitoringRequest"/>
<xsd:element maxOccurs="unbounded" ref="SituationExchangeRequest"/>
</xsd:choice>
</xsd:group>
<!--===GS: Subscription REquest ==================================================================== -->
<xsd:element name="SubscriptionRequest">
<xsd:annotation>
<xsd:documentation>
Request from Subscriber to Producer for a subscription. Answered with a SubscriptionResponse.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="SubscriptionRequestStructure"/>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="SubscriptionRequestStructure">
<xsd:annotation>
<xsd:documentation>Type for SIRI Subscription Request.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractSubscriptionRequestStructure">
<xsd:sequence>
<xsd:group ref="SiriSubscriptionRequestGroup"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="SiriSubscriptionRequestStructure">
<xsd:annotation>
<xsd:documentation>
Type for SIRI Functional Service Subscription types. Used for WSDL exchanges.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="SiriSubscriptionRequestGroup"/>
</xsd:sequence>
</xsd:complexType>
<xsd:group name="SiriSubscriptionRequestGroup">
<xsd:annotation>
<xsd:documentation>
SIRI Functional Service Subscription types. For a given SubscriptionRequest, must all be of the same service type.
</xsd:documentation>
</xsd:annotation>
<xsd:choice>
<xsd:element maxOccurs="unbounded" ref="ProductionTimetableSubscriptionRequest"/>
<xsd:element maxOccurs="unbounded" ref="EstimatedTimetableSubscriptionRequest"/>
<xsd:element maxOccurs="unbounded" ref="StopTimetableSubscriptionRequest"/>
<xsd:element maxOccurs="unbounded" ref="StopMonitoringSubscriptionRequest"/>
<xsd:element maxOccurs="unbounded" ref="VehicleMonitoringSubscriptionRequest"/>
<xsd:element maxOccurs="unbounded" ref="ConnectionTimetableSubscriptionRequest"/>
<xsd:element maxOccurs="unbounded" ref="ConnectionMonitoringSubscriptionRequest"/>
<xsd:element maxOccurs="unbounded" ref="GeneralMessageSubscriptionRequest"/>
<xsd:element maxOccurs="unbounded" ref="FacilityMonitoringSubscriptionRequest"/>
<xsd:element maxOccurs="unbounded" ref="SituationExchangeSubscriptionRequest"/>
</xsd:choice>
</xsd:group>
<!-- === RESPONSES ================================================================== -->
<xsd:group name="ResponseGroup">
<xsd:annotation>
<xsd:documentation>SIRI Service Responses.</xsd:documentation>
</xsd:annotation>
<xsd:choice>
<xsd:group ref="ServiceResponseGroup"/>
<xsd:group ref="DeliveryResponseGroup"/>
<xsd:group ref="StatusResponseGroup"/>
<xsd:group ref="SiriDiscoveryResponseGroup"/>
</xsd:choice>
</xsd:group>
<xsd:group name="ServiceResponseGroup">
<xsd:annotation>
<xsd:documentation>
Responses to requests other than deliveries and status information.
</xsd:documentation>
</xsd:annotation>
<xsd:choice>
<xsd:element ref="SubscriptionResponse"/>
<xsd:element ref="TerminateSubscriptionResponse"/>
</xsd:choice>
</xsd:group>
<!-- ===Data Delivery ============================================================== -->
<xsd:group name="DeliveryResponseGroup">
<xsd:annotation>
<xsd:documentation>Responses that deliver payload content.</xsd:documentation>
</xsd:annotation>
<xsd:choice>
<xsd:element ref="DataReadyAcknowledgement"/>
<xsd:element ref="ServiceDelivery"/>
<xsd:element ref="DataReceivedAcknowledgement"/>
</xsd:choice>
</xsd:group>
<!-- ===GS: Service Delivery==================================================================== -->
<xsd:element name="ServiceDelivery">
<xsd:annotation>
<xsd:documentation>
Response from Producer to Consumer to deliver payload data. Either answers a direct ServiceRequest, or asynchronously satisfies a subscription. May be sent directly in one step, or fetched in response to a DataSupply Request.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="ServiceDeliveryStructure"/>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="ServiceDeliveryStructure">
<xsd:annotation>
<xsd:documentation>Type for SIRI Service Delivery.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ProducerResponseStructure">
<xsd:sequence>
<xsd:group ref="ServiceDeliveryBodyGroup"/>
</xsd:sequence>
<xsd:attribute name="srsName" type="SrsNameType">
<xsd:annotation>
<xsd:documentation>
Default gml coordinate format for eny location elements in response; applies if Coordinates element is used to specify points. May be overridden on individual points.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ServiceDeliveryBodyStructure">
<xsd:annotation>
<xsd:documentation>Type for SIRI Service Delivery Body..</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="ServiceDeliveryBodyGroup"/>
</xsd:sequence>
<xsd:attribute name="srsName" type="SrsNameType">
<xsd:annotation>
<xsd:documentation>
Default gml coordinate format for eny location elements in response; applies if Coordinates element is used to specify points. May be overridden on individual points.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
<xsd:group name="ServiceDeliveryBodyGroup">
<xsd:annotation>
<xsd:documentation>Elements for SIRI Service Delivery.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="ServiceDeliveryRequestStatusGroup"/>
<xsd:element default="false" minOccurs="0" name="MoreData" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether there is a further delvery message with more current updates that follows this one. Default is 'false'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group ref="SiriServiceDeliveryGroup"/>
</xsd:sequence>
</xsd:group>
<xsd:complexType name="SiriServiceDeliveryStructure">
<xsd:annotation>
<xsd:documentation>
Type for a SIRI SIRI Functional Service Delivery types.Used for WSDL.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="SiriServiceDeliveryGroup"/>
</xsd:sequence>
</xsd:complexType>
<xsd:group name="SiriServiceDeliveryGroup">
<xsd:annotation>
<xsd:documentation>SIRI Functional Service Delivery types.</xsd:documentation>
</xsd:annotation>
<xsd:choice>
<xsd:element maxOccurs="unbounded" ref="ProductionTimetableDelivery"/>
<xsd:element maxOccurs="unbounded" ref="EstimatedTimetableDelivery"/>
<xsd:element maxOccurs="unbounded" ref="StopTimetableDelivery"/>
<xsd:element maxOccurs="unbounded" ref="StopMonitoringDelivery">
<xsd:annotation>
<xsd:documentation>Delviery for Stop Event service.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" ref="VehicleMonitoringDelivery">
<xsd:annotation>
<xsd:documentation>Delviery for Vehicle Activity Service.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" ref="ConnectionTimetableDelivery"/>
<xsd:element maxOccurs="unbounded" ref="ConnectionMonitoringFeederDelivery">
<xsd:annotation>
<xsd:documentation>
Delivery for Connection Protection Fetcher Service.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" ref="ConnectionMonitoringDistributorDelivery">
<xsd:annotation>
<xsd:documentation>
Delivery for Connection Protection Fetcher Service.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" ref="GeneralMessageDelivery">
<xsd:annotation>
<xsd:documentation>Delivery for general Message service.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" ref="FacilityMonitoringDelivery"/>
<xsd:element maxOccurs="unbounded" ref="SituationExchangeDelivery"/>
</xsd:choice>
</xsd:group>
<!-- ===Discovery==================================================================== -->
<xsd:group name="SiriDiscoveryRequestGroup">
<xsd:annotation>
<xsd:documentation>
Requests for reference data for use in SIRI Functional Service requests.
</xsd:documentation>
</xsd:annotation>
<xsd:choice>
<xsd:element ref="CapabilitiesRequest"/>
</xsd:choice>
</xsd:group>
<xsd:group name="SiriDiscoveryResponseGroup">
<xsd:annotation>
<xsd:documentation>
Responses with reference data for use in SIRI Functional Service requests.
</xsd:documentation>
</xsd:annotation>
<xsd:choice>
<xsd:element ref="CapabilitiesResponse">
<xsd:annotation>
<xsd:documentation>
Responses with the capabilities of an implementation. Answers a CapabilityRequest.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
</xsd:group>
<!-- === Capabilities ============================================================== -->
<!-- ===GS: Capabilities Request==================================================================== -->
<xsd:annotation>
<xsd:documentation>
Requests a the current capabilities of the server. Answred with a CpabailitiesResponse.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="CapabilitiesRequestStructure">
<xsd:annotation>
<xsd:documentation>
Type for Requests for capabilities of the current system.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AuthenticatedRequestStructure">
<xsd:sequence>
<xsd:element minOccurs="0" name="Address" type="EndpointAddress">
<xsd:annotation>
<xsd:documentation>
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="RequestorRef"/>
<xsd:group ref="DelegatorEndpointGroup">
<xsd:annotation>
<xsd:documentation>
If request has been proxied by an intermediate aggregting system, trackng informattion relating to the original requestor. This allows the aggregation to be stateless
</xsd:documentation>
</xsd:annotation>
</xsd:group>
</xsd:sequence>
<xsd:attribute default="2.0" name="version" type="VersionString"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
Defines the capabilities of an individual SIRI service request functions.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" ref="ProductionTimetableCapabilitiesRequest"/>
<xsd:element minOccurs="0" ref="EstimatedTimetableCapabilitiesRequest"/>
<xsd:element minOccurs="0" ref="StopTimetableCapabilitiesRequest"/>
<xsd:element minOccurs="0" ref="StopMonitoringCapabilitiesRequest"/>
<xsd:element minOccurs="0" ref="VehicleMonitoringCapabilitiesRequest"/>
<xsd:element minOccurs="0" ref="ConnectionTimetableCapabilitiesRequest"/>
<xsd:element minOccurs="0" ref="ConnectionMonitoringCapabilitiesRequest"/>
<xsd:element minOccurs="0" ref="GeneralMessageCapabilitiesRequest"/>
<xsd:element minOccurs="0" ref="FacilityMonitoringCapabilitiesRequest"/>
<xsd:element minOccurs="0" ref="SituationExchangeCapabilitiesRequest"/>
</xsd:sequence>
</xsd:group>
<!-- ===GS: Capabilities Delivery==================================================================== -->
<xsd:annotation>
<xsd:documentation>
Responses with the capabilities of an implementation.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="CapabilitiesResponseStructure">
<xsd:annotation>
<xsd:documentation>Type for the capabilities of an implementation.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ProducerResponseStructure">
<xsd:sequence> </xsd:sequence>
<xsd:attribute default="2.0" name="version" type="VersionString"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
Defines the capabilities of an individual SIRI service response functions.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" ref="ProductionTimetableCapabilitiesResponse"/>
<xsd:element minOccurs="0" ref="EstimatedTimetableCapabilitiesResponse"/>
<xsd:element minOccurs="0" ref="StopTimetableCapabilitiesResponse"/>
<xsd:element minOccurs="0" ref="StopMonitoringCapabilitiesResponse"/>
<xsd:element minOccurs="0" ref="VehicleMonitoringCapabilitiesResponse"/>
<xsd:element minOccurs="0" ref="ConnectionTimetableCapabilitiesResponse"/>
<xsd:element minOccurs="0" ref="ConnectionMonitoringCapabilitiesResponse"/>
<xsd:element minOccurs="0" ref="GeneralMessageCapabilitiesResponse"/>
<xsd:element minOccurs="0" ref="FacilityMonitoringCapabilitiesResponse"/>
<xsd:element minOccurs="0" ref="SituationExchangeCapabilitiesResponse"/>
</xsd:sequence>
</xsd:group>
<!-- ======================================================================= -->
</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/