main schema e-service developers Revised for version 2.0 Kizoom Limited, by Tom White, Nicholas Knowles. mailto:schemer@kizoom.com Roger Slevin [Roger.Slevin@dft.gsi.gov.uk] Paul Robinson [Paul.Robinson@carlbro.com] Richard Mejia [Richard.Mejia@carlbro.com] United Kingdom Created as W3C .xsd schema by CGEY as 1.1 XML schema, Ross Dixon, Kieran Holmes mailto:ross.dixon@cgey.com 2001-05-20 2003-09-11 2004-02-01 2004-03-08

The TransXChange is a UK nationwide system for exchanging bus schedules. It is used both for the electronic registration of bus routes with the Traffic Area Networks (TAN), and for the exchange of bus routes with other systems such as journey planners and real-time tracking systems.

There are two closely related but distinct TransXChange XML schemas:

  • A Registration schema for registering a bus timetable. Includes mandatory elements.
  • A General schema for exchanging bus timetable data between systems of all sorts.

This document is the registration schema.

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 http://www.transxchange.org.uk/schemas/2.0c/TransXChange_registration.xsd [ISO 639-2/B] ENG Department for Transport, Great Minster House, 76 Marsham Street, London SW1P 4DR http://www.transxchange.org.uk/schemas/2.0c/TransXChange_common.xsd http://www.transxchange.org.uk/schemas/2.0c/TransXChange_common.xsd Unclassified Crown Copyright 2000-2004
  • Originally developed as Version 1.0 in 2000 By Ross Dixon and Kieran Holmes of CGEY.
  • Revised as Version 1.1, 2001 by Ross Dixon
  • Revised as Version 1.2, 2002 by Ross Dixon
Version 2.0 Draft for approval Arts, recreation and travel, Tourism, Travel (tourism), Transport, Public transport, Bus services, Coach services, Bus stops and stations Rail transport, Infrastructure (railways), Train services, Roads and road transport Transport Direct TransXChange Registration Schema, an XML format for registering bus timetables. Standard Schema for exchanging a bus schedule for registration with a Traffic Area Network. @xml:lang @CreationDateTime, @ModificationDateTime, @Modification, @RevisionNumber, @FileName, @SchemaVersion, @MappingSystem, @LocationSystem. Definitions of Serviced Organisations and their working and non-working days. Local Stop definitions for Stops used in services. Normally Stops will be defined simply by referencing their NaPTAN AtcoCode in a StopPointRef. Stops can also be defined locally here. Local StopArea definitions. Normally StopAreas will be defined as part of their NaPTAN Definition. Areas can be defined locally here. Definitions of geographical zones of operation, used to describe flexible services. Definitions of the Route Sections, i.e. collections of of route links, making up all or part of a Route. These are used in Route definitions. Definitions of Transport Routes. Definitions of Journey Pattern sections. Description of the Services to be registered. Definitions of Vehicle Journeys, used in one or more Services. Additional documents describing the Service. Data system to use for location coordinate references within the document. This is fixed to be Grid for registration documents. A collection of standard and flexible services. A specific scheduled journey by an individual vehicle making up a regular part of the service. @CreationDateTime, @ModificationDateTime, @Modification, @RevisionNumber. A service meeting the criteria for flexibly routed services, that is with variable stopping points and no fixed timetable in accordance with the regulations. @CreationDateTime, @ModificationDateTime, @Modification, @RevisionNumber. Abstract type for elements common to all service types. Code that uniquely identifies the Service. The line or lines that make up the service. A Line by which all or part of the service is known. @id. Public identifier of the service. E.g. "N73". Whether a Service is part of a pair (i.e. is comprised of an inbound and an outbound journey). Inclusive period within which Service runs. Nature of Service. The ServiceType affects rules of usage of data. Required for Registration Schema, but not General Schema. The identifier used by the ticket machine system to refer to the service. Information needed to register a bus route with a TAN. Required for Registration Schema, but not General Schema. Registered Operator of Service - i.e. with responsibility for the service. @CreationDateTime, @ModificationDateTime, @Modification, @RevisionNumber. Operator associated with the Service who is NOT the Registered Operator. @CreationDateTime, @ModificationDateTime, @Modification, @RevisionNumber. Required for Registration Schema, but not General Schema. Dates on which the service runs. Special operation days and exclusion periods for the route. Descriptive note about the service. Information about other services with which the registered service will be jointly marketed. Classification and description of the bus service. Does not identify the individual bus journeys (defined as part of VehicleJourney). Public name of place where the Service Starts. @lang. Public name of place where the Service Ends. @lang. Whether Service to be registered will use all the stops along its Route. Pattern of journeys making up the service. @id, @CreationDateTime, @ModificationDateTime, @Modification, @RevisionNumber. Description of Interchange(s) used to connect two or more journey patterns of a service. @id, @JourneyPatternInterchangeId. @CreationDateTime, @ModificationDateTime, @Modification, @RevisionNumber. Description of a flexible bus service. Points at which the service will pick up passengers. Points at which the service will set down passengers. Timebands during which the flexible service runs during a day. Date of Registration submission. Reference number for registration (allocated by TAN). Whether the registration should be considered to be new, a chargeable modification of an existing registration, a non-chargeable modification of an existing registration or a cancellation of a registration. Enumerated value. Variation number of the Registration. Signatory of the submission - i.e. upon whose authority the submission is made. Collection of Traffic Areas with full or partial responsibility for the registration of the submission. Collection of Authorities circulated with record. Information about any subsidy provided for the route. Required for Registration, but not General. Additional documents that support the registration. Additional information to support a Registration with less than the statutory period of notice. Full name of Operator (i.e. as appears on licence). Required for Registration Schema, but not General Schema. @lang. Enquiry telephone number of Operator. Contact telephone number of Operator. Contact telephone number of Operator. Required for Registration Schema, but not General Schema. Required for Registration, but not General. Enumerated value. The email address of the operator. It is up to the operator whether an individual's address, or a generic company e-mail address is used.