All Downloads are FREE. Search and download functionalities are using the official Maven repository.

siri-2.0.xsd.siri.siri_common_services-v2.0.xsd Maven / Gradle / Ivy

The newest version!





	
		
			
				main schema
				e-service developers
				CEN TC278 WG3 SG7 Team
				Europe
				First drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:[email protected]
				
					2004-09-29
				
				
					2005-02-14
				
				
					2005-02-20
				
				
					2005-05-11
				
				
					2007-04-17
					 - Name Space changes 
				
				
					2008-10-09
					 -- Add Subscriber ref to TermninateSubscription Request 
				
				
					2008-11-17
					 -- Revise for substitution groups and move down to siri subdirectory 
				
				
					2012-03-23
					 +SIRI v2.0
					   - Add DataReady to Check Status
					   - Add DistanceUnits and VelocityUnits to ServiceRequestContext
					   - [FR]    Add Extensions tag to Terminate SubscriptionRequest
				
				
					2014-03-31
					 +SIRI v2.0 Comments
					   - Add terminate subscription notification
				
				
					2014-06-23
					 +SIRI v2.0 Comments
					   - Revise  terminate subscription erroc condition to be consistent with other services
				
				
					

SIRI is a European CEN standard for the exchange of real-time information.

This subschema describes common communication requests that are the same for all services.

It contains the following request

  • GS: Terminate Subscription Resquest
  • GS: Terminate Subscription Response
  • GS: Subscription Response
  • GS: Data Ready Notification
  • GS: Data Ready Acknowledgement
  • GS: Data Supply Request
  • GS: Data Received Response
  • GS: Check Status Request
  • GS: Check Status Response
  • GS: Heartbeat Request

Siri supports both direct requests and publish subscribe patterns of interaction

text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schema/2.0/xsd/siri/}siri_common_services.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests-v2.0.xsd Unclassified CEN, VDV, RTIG 2004-2012
  • Derived from the VDV, RTIG XML and Trident standards.
Version 2.0 Draft 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 CEN TC278 WG3 SG7 SIRI XML schema. Service Interface for Real-time Information. Common Requests Standard
SIRI Framework - Common Requests.
Convenience artefact to pick out main elements of the common requests. Requests about system status. Type for General SIRI Request. General request properties - typically configured rather than repeated on request. Address elements for SIRI messages to the Producer server. Address to which CheckStatus requests are to be sent. Address to which subscription requests are to be sent. Address to which subscription requests are to be sent. If absent, same as SubscribeAddress. Address to which requests are to return data. Address elements for SIRI messages to the Subscriber/Consumer client. Address to which CheckStatus responses and heartbeats are to be sent. If absent, same as SubscriberAddress. Address to which subscription responses are to be sent. Address to which notifcations requests are to be sent. If absent, same as SubscriberAddress. Address to which data is to be sent. If absent, same as NotifyAddress. Configurable context for requests. Intended Primarily as a documentation mechanism. Delivery options. Whether Delivery is fetched or retrieved. Whether multi-part delivery is allowed, i.e. the breaking up of updates into more than one delivery messages with a MoreData flag, Whether Consumers should issue an acknowledgement on successful receipt of a delivery. Default is ' false'. Delivery Method: Fetched or Direct Delivery. Prediction options. Who may make a prediction. Name of prediction method used. Allowed values for predictors. Timing related elements in Request Context: Maximum data horizon for requests. Timeout for requests. [Should this be separate for each type?] Name spaces. Name space for STOP POINTs. Name space for LINE names and DIRECTIONss. Name space for Product Categories. Name space for service features. Name space for VEHICLE features. Namespace related elements in Request Context. Default names pace used to scope data identifiers. Preferred language in which to return text values. Default geospatial Coordinates used by service. Geospatial coordinates are given as Wgs 84 Latiude and longitude, decimial degrees of arc. Name of GML Coordinate format used for Geospatial points in responses. Units for Distance Type. Default is metres. +SIRI v2.0 Units for Distance Type. Default is metres per second. +SIRI v2.0 Resources related elements in Request Context. Maximum Number of subscriptions that can be sustained by the subscriber. If absent no limit. groups the subscription request. Request from Subscriber to Subscription Manager to terminate a subscription. Answered with a TerminateSubscriptionResponse. Type for request to terminate a subscription or subscriptions. If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 Parameters that specify the content to be processed. Participant identifier of Subscriber. Subscription ref will be unique within this. Terminate all subscriptions for the requestor. Terminate the subscription identfiied by the reference. Status Info. Status of each subscription termnination response. Request from Subscriber to Subscription Manager to terminate a subscription. Answered with a TerminateSubscriptionResponse. Type for Response to a request to terminate a subscription or subscriptions. Type for Status of termination response. Description of any error or warning condition. Text description of error. Notification from Subscriber to Subscription Manager to terminate a subscription. Type for Notification to terminate a subscription or subscriptions. Text description providing additional information about the reason for the subscription termination. Responses that infrom about the service status. Type for Response Status. Description of any error or warning condition. Contains infromation about the processing of a an individual service subscription - either success info or an error condition. (VDV Acknowledgement). Response from Producer to Consumer to inform whether subscriptions have been created. Answers a previous SubscriptionRequest. Type for Subscription Response. Subscription Response content. Endpoint address of subscription manager if different from that of the Producer or known default. Time at which service providing the subscription was last started. Can be used to detect restarts. If absent, unknown. General requests for fetched data delivery. Request from Producer to Consumer to notify that data update is ready to fetch. Answered with a DataReadyResponse. Groups the data supply messages. Type for Request from Producer to Consumer to notify that data update is ready to fetch. Answered with a DataReadyResponse. Response from Consumer to Producer to acknowledge to Producer that a DataReadyRequest has been received. Type for Data ready Acknowledgement Response. Description of any error or warning condition as to why Consumer cannot fetch data. Text description of error. Request from Consumer to Producer to fetch update previously notified by a Data ready message. Answered with a Service Delivery. Type for Data supply Request. Specifies content to be included in data supply. Reference to a specific notification message for which data is to be fetched. Can be used to distinguish between notfcatiosn for the same service and subscriber but for different filters.If none specified, Whether to return all data, or just new updates since the last delivery. Default false, i.e. just updates. Response from Consumer to Producer to acknowledge that data hase been received. Used as optioanl extra step if reliable delivery is needed. Answers a ServiceDelivery. Data received Acknowledgement content. Description of any error or warning condition. Text description of error. Type for Data received Acknowledgement Response. Elements identifying data Consumer, i.e. requestor, if synchronous delivery or subscriber if asynchronous. Reference to an arbitrary unique reference associated with the request which gave rise to this response. Request from Consumer to Producer to check whether services is working. Answers a CheckStatusRequest. Type for check status request. Version number of request. Data received AcknowledgementService Status Check Request content. Whether data delivery is ready to be fetched SIRI v 2.0 Description of any error or warning condition that applies to the status check. Text description of error. Time at which current instantiation of service started. Response from Producer to Consumer to inform whether services is working. Answers a CheckStatusRequest. Type for Service Status Check Response. Notification from Producer to Consumer to indicate that the service is running normally. Type for Service Heartbeat Notification. Type for Body of Subscription Response. Used in WSDL. Endpoint address of subscription manager if different from that of the Producer or known default. Time at which service providing the subscription was last started. Can be used to detect restarts. If absent, unknown. Type for Body of Terminate Subscription Request content. Used in WSDL. Type for Body of Data Supply Request. Used in WSDL. Type for Body of Service Status Check Response. Used in WSDL. Same as CheckStatusResponseStructure, but without extension to be consistent with the other operation definition.




© 2015 - 2025 Weber Informatics LLC | Privacy Policy