RTIG Examples 1.2c - Using Loose Conformance

Information

• Overview
• Schema
• Examples Concrete 1.2c
• Examples Loose 1.2c
• Documentation
• Versioning
• Implementations
• History
• Terms of Use
• Contact

Related Standards

• NaPTAN
• National PT Gazetteer
• JourneyWeb
• TransXChange
• RtigXml
• GovTalk & e-Gif

The following XML examples demonstrate the use of RTIG to encode requests and responses.  The message parts are coded to conform to RTIG, but the general exchange messages and the service content are only loosely coupled (in contrast to referencing a single concrete  RtigXML schema). 

For each example, both the request and the response are shown. For each service request or service response, separate instance documents are shown (i) for the enclosing general TRIDENT get, register or deliver messages (validating against the rtig_request_response.xsd schema), and (ii) for the RtigXml 'payload' service message contained between the 'any' tags  (validating against  rtig_reference.xsd).

 

Group	Name	Request	Response
Common	Subscription	register See Stop Status & Vehicle Status  Subscriptions	registrationResponse registrationResponse error
		unregister	registrationDropped
Service
	Stop Status	StopStatusRequest get StopStatusRequest  payload	StopStatusDelivery deliver StopStatusDelivery payload Minimum StopStatus Delivery  payload
		StopStatusSubscription  register StopStatusSubscription  payload	StopStatusDelivery 1  deliver StopStatusDelivery 1 payload StopStatusDelivery 2 deliver StopStatusDelivery 1 payload
	Vehicle Status	VehicleStatusRequest  get VehicleStatusRequest    payload	VehicleStatusDelivery  deliver VehicleStatusDelivery   payload Minimum VehicleStatus Delivery payload
		VehicleStatusSubscription      register VehicleStatusSubscription      payload
Discovery	Points	(StopPointRequest)	(StopPointsDelivery)
	Lines	(LinesRequest)	(LinesDelivery)

© RTIG copyright 2000-2004.
Page last updated: 2004/10/01