RtigXml Schema Structure 1.2

The RtigXml schema uses a modular structure, broken down into a number of packages. Schema and subschemas may be used by instance documents that comply with RtigXml.

  • Version 1.1 of RtigXml referenced all the TRIDENT modules (including many that were not used) and provided a simple implementation of the general TRIDENT request/response and publish subscribe messages that was not directly coupled to the RtigXml service messages.
    • The general messages had XML 'any' tags at the point at which concrete RtigXml service messages should be included. Instance documents cannot be directly validated in a single step.
  • Version 1.2 of RtigXml uses a simplified, self contained set of modules, including its own definitions of just those TRIDENT data types that are used, and retaining all the TRIDENT names and general messages usage. The internal structure of the RtigXml XML modules is revised and improved for actual use, but the resulting end schemas are equivalent, and documents that validate against version 1.1 should also validate against version 1.2.
    • rtig_reference.xsd provides concrete service messages (exactly equivalent to Version 1.1 of RtigXml trident_rt_schema.xsd).
    • rtig_request_response.xsd provides a schema for general TRIDENT message exchange (exactly equivalent to Version 1.1 of RtigXml trident_xml_request-response.xsd).
    • In addition, a single concrete schema, RtigXml.xsd, is provided that can be used to validate instance documents. This combines the RTIG service messages with TRIDENT protocols without the use of 'any' tags.

RtigXml 1.2 Schema Packages:

RtigXml Schema Modules: See Schema References

The RtigSchema contains type and element definitions based on the Trident Schema.

(C) Copyright 2001, 2, 4 TRIDENT consortium, All Rights Reserved.

Common

  • The common TRIDENT based request response protocol for RTIG-XML is contained in rtig_request_response.xsd (blue in diagram) These are intended as general-purpose implementation of the TRIDENT standard.
  • The generic stop status and vehicle status services are contained in rtig_common.xsd. (blue in diagram) These are intended as general-purpose implementation of the StopStatus and VehicleStatus messages, following TRIDENT conventions.
  • The base types, including definitions of any TRIDENT types used are in rtig_types.xsd(shown in green).

Bus

  • The UK bus related RTIG-XML service protocol is contained in rtig_reference.xsd. This is a small extension schema, to rtig_common.xsd.
  • RtigXml.xsd is a concrete schema that groups together the separate bus real time request and delivery for presentation & documentation purposes.
  • RtigXml_abstract.xsd is a convenience artefact used to group together the separate bus real time request and delivery for documentation purposes.
  • RTIG bus real time instance documents will normally reference rtig_request_response.xsd and rtig_reference.xsd.

Rail

  • The UK rail related RTIG-XML service protocol is contained in rtti_reference.xsd This is a small extension schema to rtig_common.xsd.
  • RttiXml.xsd is a convenience artefact used to group together the separate bus real time request and delivery for presentation & documentation purposes.
  • RTIG bus real time instance documents will normally reference rtig_request_response.xsd and rtti_reference.xsd.