All Element Summary |
||||||||||||
|
||||||||||||
Requests a the current capabilities of the server.
|
||||||||||||
Responses with the capabilities of an implementation.
|
||||||||||||
MoreData (type xsd:boolean) |
|
|||||||||||
Response from Producer to Consumer to deliver payload data.
|
||||||||||||
Request from Consumer to Producer for immediate delivery of data.
|
||||||||||||
SIRI Service Interface for Real-time Operation.
|
||||||||||||
Request from Subscriber to Producer for a subscription.
|
Complex Type Summary |
||||||||||
Type for Requests for capabilities of the current system.
|
||||||||||
Type for the capabilities of an implementation.
|
||||||||||
Type for SIRI Service Delivery Body..
|
||||||||||
Type for SIRI Service Delivery.
|
||||||||||
SIRI Service Request.
|
||||||||||
Type for a SIRI SIRI Functional Service Delivery types.Used for WSDL.
|
||||||||||
Type for SIRI Functional Service Subscription types.
|
||||||||||
Type for SIRI Subscription Request.
|
Element Group Summary |
||||||||||
Responses that deliver payload content.
|
||||||||||
SIRI All Requests.
|
||||||||||
SIRI Service Responses.
|
||||||||||
Elements for SIRI Service Delivery.
|
||||||||||
Requests for service provision.
|
||||||||||
Responses to requests other than deliveries and status information.
|
||||||||||
Requests for reference data for use in SIRI Functional Service requests.
|
||||||||||
Responses with reference data for use in SIRI Functional Service requests.
|
||||||||||
Defines the capabilities of an individual SIRI service request functions.
|
||||||||||
Defines the capabilities of an individual SIRI service response functions.
|
||||||||||
SIRI Functional Service Delivery types.
|
||||||||||
SIRI Functional Service Concrete Requests.
|
||||||||||
SIRI Functional Service Subscription types.
|
<?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>
</xsd:annotation>
<Metadata xmlns="http://www.govtalk.gov.uk/CM/gms-xs">
</xsd:appinfo>
<Aggregation>main schema</Aggregation>
</Metadata>
<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>
>Drafted for version 1.0 & Version 2.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom.
</Creator>
mailto:schemer@siri.org.uk <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>
</Date>
Name Space changes
<Date>
<Modified>2008-11-17</Modified>
</Date>
Change to use common 1_2. Add in mussing StopMonitoringMultipelRequest
Rename groups to identify common SIRI elements <Date>
<Modified>2009-03-03</Modified>
</Date>
Corrrect cardinality on facility and Service Monitoring Delivery request
<Date>
<Modified>2011-04-18</Modified>
</Date>
Updated journey, request and other subpackages - see readme
<Date>
<Modified>2012-03-23</Modified>
</Date>
SIRI Version 2.0
Model subpackages Refactored to improve modularisation. [SIRI-LITE] Add authentication Key See Readme.txt for list of changes <Date>
<Modified>2012-05-18</Modified>
</Date>
SIRI Version 2.0
Correct error in SituationExchangeCapabilitiesReponse include <Date>
<Modified>2012-08-01</Modified>
</Date>
SIRI Version 2.0
Correct delegation elements <Date>
<Modified>2014-03-31</Modified>
</Date>
+SIRI v2.0 Comments
- Add terminate subscription notification <Description>
<p>
</Description>
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 :
</p>
<ul>
<li>
</ul>
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>
<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>
<Format>
<MediaType>text/xml</MediaType>
</Format>
<Syntax>http://www.w3.org/2001/XMLSchema</Syntax>
<Description>XML schema, W3C Recommendation 2001</Description>
<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>
</Relation>
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>
<Rights>
Unclassified
</Rights>
<Copyright>CEN, VDV, RTIG 2004-2012</Copyright>
<Source>
<ul>
</Source>
<li>
</ul>
Derived from the VDV, RTIG XML and Trident standards.
</li>
<Status>Version 2.0 Version with cumulative fixes</Status>
<Subject>
<Category>
</Subject>
Arts, recreation and travel, Tourism, Travel (tourism), Transport,
</Category>
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. <Project>CEN TC278 WG3 SG7</Project>
<Title>
SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations.
</Title>
<Type>Standard</Type>
SIRI Service Interface for Real-time Information relating to Public Transport Operations. - XML Schema with explicit functional services
</xsd:documentation>
<!-- ======================================================================= -->
<!-- ======================================================================= -->
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
</xsd:element>
<!--== Requests ===================================================================== -->
<xsd:annotation>
</xsd:annotation>
</xsd:group>
<xsd:choice>
</xsd:choice>
<!-- ===GS: ServceRequest================================================ -->
<xsd:annotation>
</xsd:element>
</xsd:group>
<xsd:documentation>
</xsd:annotation>
</xsd:complexType>
Request from Consumer to Producer for immediate delivery of data. Answered with a ServiceDelivery (or a DataReadyRequest)
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:complexContent>
</xsd:complexContent>
<xsd:annotation>
</xsd:annotation>
</xsd:group>
<xsd:choice>
</xsd:choice>
<!--===GS: Subscription REquest ==================================================================== -->
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
</xsd:complexType>
Request from Subscriber to Producer for a subscription. Answered with a SubscriptionResponse.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:complexContent>
</xsd:complexContent>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
Type for SIRI Functional Service Subscription types. Used for WSDL exchanges.
</xsd:documentation>
<xsd:sequence>
</xsd:sequence>
<xsd:annotation>
</xsd:group>
<xsd:documentation>
</xsd:annotation>
SIRI Functional Service Subscription types. For a given SubscriptionRequest, must all be of the same service type.
</xsd:documentation>
<xsd:choice>
</xsd:choice>
<!-- === RESPONSES ================================================================== -->
<xsd:annotation>
</xsd:annotation>
</xsd:group>
<xsd:choice>
</xsd:choice>
<xsd:annotation>
</xsd:group>
<xsd:documentation>
</xsd:annotation>
Responses to requests other than deliveries and status information.
</xsd:documentation>
<xsd:choice>
</xsd:choice>
<!-- ===Data Delivery ============================================================== -->
<xsd:annotation>
</xsd:annotation>
</xsd:group>
<xsd:choice>
</xsd:choice>
<!-- ===GS: Service Delivery==================================================================== -->
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
</xsd:complexType>
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:annotation>
</xsd:complexType>
<xsd:complexContent>
<xsd:extension base="ProducerResponseStructure">
</xsd:complexContent>
<xsd:sequence>
</xsd:sequence>
</xsd:extension>
<xsd:annotation>
</xsd:attribute>
<xsd:documentation>
</xsd:annotation>
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:annotation>
</xsd:complexType>
<xsd:sequence>
</xsd:sequence>
<xsd:annotation>
</xsd:attribute>
<xsd:documentation>
</xsd:annotation>
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:annotation>
</xsd:group>
<xsd:sequence>
<xsd:group ref="ServiceDeliveryRequestStatusGroup"/>
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Whether there is a further delvery message with more current updates that follows this one. Default is 'false'.
</xsd:documentation>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
Type for a SIRI SIRI Functional Service Delivery types.Used for WSDL.
</xsd:documentation>
<xsd:sequence>
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:group>
<xsd:choice>
<xsd:element maxOccurs="unbounded" ref="ProductionTimetableDelivery"/>
</xsd:choice>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<!-- ===Discovery==================================================================== -->
<xsd:annotation>
</xsd:group>
<xsd:documentation>
</xsd:annotation>
Requests for reference data for use in SIRI Functional Service requests.
</xsd:documentation>
<xsd:choice>
</xsd:choice>
<xsd:annotation>
</xsd:group>
<xsd:documentation>
</xsd:annotation>
Responses with reference data for use in SIRI Functional Service requests.
</xsd:documentation>
<xsd:choice>
<xsd:element ref="CapabilitiesResponse">
</xsd:choice>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Responses with the capabilities of an implementation. Answers a CapabilityRequest.
</xsd:documentation>
<!-- === Capabilities ============================================================== -->
<!-- ===GS: Capabilities Request==================================================================== -->
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Requests a the current capabilities of the server. Answred with a CpabailitiesResponse.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:complexContent>
<xsd:extension base="AuthenticatedRequestStructure">
</xsd:complexContent>
<xsd:sequence>
</xsd:extension>
<xsd:element minOccurs="0" name="Address" type="EndpointAddress">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data.
</xsd:documentation>
<xsd:annotation>
</xsd:group>
<xsd:documentation>
</xsd:annotation>
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:documentation>
</xsd:annotation>
Defines the capabilities of an individual SIRI service request functions.
</xsd:documentation>
<xsd:sequence>
</xsd:sequence>
<!-- ===GS: Capabilities Delivery==================================================================== -->
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:complexContent>
</xsd:complexContent>
<xsd:annotation>
</xsd:group>
<xsd:documentation>
</xsd:annotation>
Defines the capabilities of an individual SIRI service response functions.
</xsd:documentation>
<xsd:sequence>
</xsd:sequence>
<!-- ======================================================================= -->
</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:
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/
|