XML Schema "siri_base-v2.0.xsd"
Target Namespace:
http://www.siri.org.uk/siri
Version:
2.0
Defined Components:
elements (5 global + 1 local), complexTypes (7), element groups (8)
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
C:\Users\Tony\eclipse_workspace\siri-20-java\xsd\siri\siri_base-v2.0.xsd; see XML source
Includes Schemas (1):
siri_common_services-v2.0.xsd [src]
Included in Schemas (1):
siriSg.xsd [src]
Annotation
SIRI Common Request Fra,mework
All Element Summary
CapabilitiesRequest
Requests a the current capabilities of the server.
Type:
CapabilitiesRequestStructure
Content:
complex, 1 attribute, 9 elements
Defined:
globally; see XML source
Used:
at 1 location
CapabilitiesResponse
Responses with the capabilities of an implementation.
Type:
CapabilitiesResponseStructure
Content:
complex, 8 elements
Defined:
globally; see XML source
Used:
at 1 location
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, 11 elements
Defined:
globally; see XML source
Used:
at 1 location
ServiceRequest
Request from Consumer to Producer for immediate delivery of data.
Type:
anonymous complexType (extension of ServiceRequestStructure)
Content:
complex, 10 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
at 1 location
SubscriptionRequest
Request from Subscriber to Producer for a subscription.
Type:
anonymous complexType (extension of SubscriptionRequestStructure)
Content:
complex, 12 elements
Defined:
globally; see XML source
Used:
at 1 location
Complex Type Summary
CapabilitiesRequestStructure
Type for Requests for capabilities of the current system.
Content:
complex, 1 attribute, 9 elements
Defined:
globally; see XML source
Includes:
definitions of 1 attribute, 1 element
Used:
at 1 location
CapabilitiesResponseStructure
Type for the capabilities of an implementation.
Content:
complex, 8 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
at 1 location
ServiceDeliveryBodyStructure
Type for SIRI Service Delivery type.
Content:
complex, 1 attribute, 4 elements
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
never
ServiceDeliveryStructure
Type for SIRI Service Delivery.
Content:
complex, 1 attribute, 11 elements
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
at 1 location
ServiceRequestStructure
SIRI Service Request.
Content:
complex, 9 elements
Defined:
globally; see XML source
Used:
at 1 location
SiriSchema
Content:
complex, 1 attribute, 18 elements
Defined:
globally; see XML source
Includes:
definitions of 1 attribute, 1 element
Used:
never
SubscriptionRequestStructure
Type for SIRI Subscription Request.
Content:
complex, 12 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
at 1 location
Element Group Summary
DeliveryResponseGroup
Responses that deliver payload content.
Content:
3 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
at 1 location
DiscoveryRequestGroup
Requests for reference data for use in service requests.
Content:
2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
at 1 location
DiscoveryResponseGroup
Responses with reference data for use in service requests.
Content:
2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
at 1 location
RequestGroup
SIRI Requests.
Content:
9 elements
Defined:
globally; see XML source
Used:
at 2 locations
ResponseGroup
SIRI Service Responses.
Content:
8 elements
Defined:
globally; see XML source
Used:
at 2 locations
ServiceDeliveryBodyGroup
Elements for SIRI Service Delivery type.
Content:
4 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
at 2 locations
ServiceRequestGroup
Requests for service provision.
Content:
3 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
at 1 location
ServiceResponseGroup
Responses to requests other than deliveries and status information.
Content:
2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
at 1 location
XML Source
<?xml version="1.0" encoding="UTF-8"?>
<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>
<Contributor>
Dipl.-Kfm. Winfried Bruns, Verband Deutscher, Köln
</Contributor>
<Contributor>
Mark Cartwright, Centaur Consulting Limited, Guildford
</Contributor>
<Contributor>
Christophe Duquesne, PDG Consultant en systémes, Dryade Guyancourt
</Contributor>
<Contributor>Stefan Fjällemark, HUR - Hovedstadens, Valby</Contributor>
<Contributor>Jonas Jäderberg, Columna, Borlänge</Contributor>
<Contributor>
Dipl.-Ing. Sven Juergens psitrans juergens@psitrans.de
</Contributor>
<Contributor>Nicholas Knowles, KIZOOM Limited, London EC4A 1LT</Contributor>
<Contributor>
Werner Kohl, Mentz Datenverarbeitung GmbH, München
</Contributor>
<Contributor>
Peter Miller, ACIS Research and Development, Cambridge CB4 0DL
</Contributor>
<Contributor>Dr. Martin Siczkowski, West Yorkshire PTE, Leeds</Contributor>
<Contributor>Gustav Thiessen BLIC thi@BLIC.DE</Contributor>
<Contributor>Dr Bartak, bartak@apex-jesenice.cz</Contributor>
<Contributor>
Dr. Franz-Josef Czuka, Beratungsgesellschaft für, Düsseldorf
</Contributor>
<Contributor>
Dr.-Ing. Klaus-Peter Heynert, PSI Transportation GmbH, Berlin
</Contributor>
<Contributor>Jean-Laurant Franchineau, CONNEX-EUROLUM, PARIS</Contributor>
<Contributor>
Dipl.-Ing. (FH) Rainer Ganninger, init innovation in, Karlsruhe
</Contributor>
<Contributor>
Dipl.-Ing. HTL Peter Machalek, Siemens Transit, Neuhausen am Rheinfall
</Contributor>
<Contributor>
El Ing. Ernst Pfister, Siemens Transit, Neuhausen am Rheinfall
</Contributor>
<Contributor>
Dipl.-Ing. Berthold Radermacher, Verband Deutscher, Köln
</Contributor>
<Contributor>
Dr. Friedemann Weik, Hamburger Berater Team GmbH, Hamburg
</Contributor>
<Coverage>Europe</Coverage>
<Creator>
&gt;Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk
</Creator>
<Date>
<Created>2012-06-17</Created>
<!-- Update version number to 2.0 -->
</Date>
<Date>
<Created>2009-11-17</Created>
<!-- created from SIRI common -->
</Date>
<Date>
<Modified>2008-11-17</Modified>
<!-- Revised s -->
</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 :
<p>
This schema provdies a generic base schema that can be used to
</p>
</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, 109-123 Clifton Street, London EC4A 4LD</Publisher>
<Relation>
<Requires>
http://www.siri.org.uk/schema/2.0/xsd/siri__common_services-v1.3xsd
</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 relating to Public Transport Operations Generic base schema.
</Title>
<Type>Standard</Type>
</Metadata>
</xsd:appinfo>
<xsd:documentation>SIRI Common Request Fra,mework</xsd:documentation>
</xsd:annotation>
<!-- ======================================================================= -->
<xsd:include schemaLocation="siri_common_services-v2.0.xsd"/>
<!-- ======================================================================= -->
<xsd:complexType name="SiriSchema">
<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="xsd:NMTOKEN" use="optional"/>
</xsd:complexType>
<!--== Requests ===================================================================== -->
<xsd:group name="RequestGroup">
<xsd:annotation>
<xsd:documentation>SIRI Requests.</xsd:documentation>
</xsd:annotation>
<xsd:choice>
<xsd:group ref="ServiceRequestGroup"/>
<xsd:group ref="DeliveryRequestGroup"/>
<xsd:group ref="StatusRequestGroup"/>
<xsd:group ref="DiscoveryRequestGroup"/>
</xsd:choice>
</xsd:group>
<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>
<!--===GS: Service Request ==================================================================== -->
<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:sequence>
<xsd:element maxOccurs="unbounded" ref="AbstractFunctionalServiceRequest"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="ServiceRequestStructure">
<xsd:annotation>
<xsd:documentation>SIRI Service Request.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ContextualisedRequestStructure"/>
</xsd:complexContent>
</xsd:complexType>
<!--===GS: Subscriptions 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:element maxOccurs="unbounded" ref="AbstractFunctionalServiceSubscriptionRequest"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!-- ===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="DiscoveryResponseGroup"/>
</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 Delviery -->
<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 type.</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 type.</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:element maxOccurs="unbounded" ref="AbstractFunctionalServiceDelivery"/>
</xsd:sequence>
</xsd:group>
<!-- ===Discovery==================================================================== -->
<xsd:group name="DiscoveryRequestGroup">
<xsd:annotation>
<xsd:documentation>
Requests for reference data for use in service requests.
</xsd:documentation>
</xsd:annotation>
<xsd:choice>
<xsd:element ref="CapabilitiesRequest"/>
<xsd:element ref="AbstractDiscoveryRequest"/>
</xsd:choice>
</xsd:group>
<xsd:group name="DiscoveryResponseGroup">
<xsd:annotation>
<xsd:documentation>
Responses with reference data for use in 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:element ref="AbstractDiscoveryDelivery"/>
</xsd:choice>
</xsd:group>
<!-- ===Capabilities ============================================================== -->
<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="RequestStructure">
<xsd:sequence>
<xsd:element ref="AbstractFunctionalServiceCapabilitiesRequest"/>
</xsd:sequence>
<xsd:attribute default="2.0" name="version" type="VersionString" use="optional"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<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:element ref="AbstractFunctionalServiceCapabilitiesResponse"/>
</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/