main schema e-service developers Revised for version 2.4 Kizoom Limited, , Nicholas Knowles. Revised for version 2.4 Roger Slevin [Roger Slevin dft .gsi gov.uk] 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 ] Richard Mejia [Richard Mejia carlbro ] 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 2004-07-01 2005-09-05 2005-09-27 2007-03-11 2010-02-12

The TransXChange is a UK nationwide system for exchanging bus schedules. It is used both for the electronic registration of bus routes with the Vehicle Operating Services Agency (VOSA), 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. This 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.4}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.5/txc/TXC_common-v2-5.xsd http://www.transxchange.org.uk/schemas/2.4/txc/TXC_common-v2-5.xsd Unclassified (C) Crown Copyright 2000-2010
  • Originally developed as Version 1.0 in 2000 from Transmodel and ATCO -CIF, 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
  • Revised as Version 2.1, 2005 by Nick Knowles
  • Revised as Version 2.2, 2007 by Nick Knowles
  • Revised as Version 2.4, 2010 by Nick Knowles
Version 2.4 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 TransXChange_registration Schema HEADER DOCUMENTATION Elements for a TXC registration. Definitions of Serviced Organisations and their working and non-working days. Calendars for (TXC v2.4) Names of Nptg Localities used in Local stop definitions. Allows an optional local copy of name data for localities taken from the NPTG. Locality names can be included in a TransXChange document to support the Publishing of stop names that include the locality name eg "Barset, High Street". Locality names of externally referenced NaPTAN stops should be included in the AnnotatedStopPointRef instead. 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 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. Definitions of operators. Definitions of services. Definitions of vehicle journeys, used in one or more services. Registration details, which must contain exactly one Registration element. Additional documents relating to the contents. . Documents that relate specifically to the registartion Schema for exchanging a bus schedule for registration with a Traffic Area Network. @xml:lang @CreationDateTime, @ModificationDateTime, @Modification, @RevisionNumber, @FileName, @SchemaVersion, @MappingSystem, @LocationSystem, @RegistrationDocument Data system to use for location coordinate references within the document. This is fixed to be Grid for registration documents. Internal Integrirt Rule I13. id of each DayType must be unique within document. (TXC v2.4). Integrity Rule I13. DayTypeRef instances must refer to a unique local definition of a DayType. (TXC v2.4) Internal Integrity Rule C1a. Stop Codes of local StopPoint and AnnotatedStopPointRef declarations must be unique within document. Internal Integrity Rule C1b. StopPointRef instances must reference a StopPoint or AnnotatedStopPoint declaration. Add Connecting Journey ref TXC 2.4 Internal Integrity Rule U1a. PrivateCodes of StopPoint declarations must be unique within document. Internal Integrity Rule C2a. Codes of local StopArea (Cluster) ) declarations must be unique within document. Internal Integrity Rule C2b. StopPointRef instances must reference a StopPoint or AnnotatedStopPoint declaration. See also External Integrity rule N1. Internal Integrity Rule U2a. PrivateCodes of StopArea declarations must be unique within document. Internal Integrity Rule C3a. Codes of ServicedOrganisation declarations must be unique within operator Internal Integrity Rule C3b. ServicedOrganisationRef instances must reference a local definition of a ServicedOrganisation element. Add ParentRef v2.4 Internal Integrity Rule U6a. PrivateCodes of ServicedOrganisation declarations must be unique within document. Internal Integrity Rule C4a. Code of each Service must be unique within document. Internal Integrity Rule C4b. ServiceRef instances must refer to a local definition of a Service. Internal Integrity Rule U8a. PrivateCodes of Service declarations must be unique within document. Internal Integrity Rule C5 Code of each VehicleJourney, FlexibleVehicleJourney or ConnectingVehicleJourney must be unique within document. (TXC 2.4 add connecting Journey) Internal Integrity Rule C5. VehicleJourneyRef instances must reference a local definition of a VehicleJourney. Internal Integrity Rule U3a. PrivateCodes of VehicleJourney declarations must be unique within document. Internal Integrity Rule C6a. Codes of Garage declarations must be unique within document Internal Integrity Rule C6b. GarageCodeRef instances to a Garage must reference a local definition of a Garage element. Internal Integrity Rule I1a. id of each Route must be unique within document. Internal Integrity Rule I1b. RouteRef instances must reference a local definition of a Route. Internal Integrity Rule U4a. PrivateCodes of Route declarations must be unique within document. Internal Integrity Rule I2a. id of each JourneyPattern must be unique within document. Internal Integrity Rule I2b. JourneyPatternRef instances must reference a local definition of a JourneyPattern or FlexibleJourneyPattern. Internal Integrity Rule U5a. PrivateCodes of JourneyPatterns must be unique within document Internal Integrity Rule I5a. id of each Line must be unique within document. Internal Integrity Rule I5b. LineRef instances must refer to a local definition of a Line element. Internal Integrity Rule I6a. id of each RouteSection must be unique within document. Internal Integrity Rule I6b. RouteSectionRef instances must refer to a local definition of a RouteSection. Internal Integrity Rule I7a. id of each JourneyPatternSection must be unique within document. Internal Integrity Rule I7b. JourneyPatternSectionRef instances must refer to a local definition of a JourneyPatternSection Internal Integrity Rule I8a. id of each RouteLink must be unique within document. Internal Integrity Rule I8b. iRouteLinkRef instances must reference a local definition of a RouteLink. Internal Integrity Rule I9a. id of each JourneyPatternTimingLink must be unique within document. Internal Integrity Rule I9b. JourneyPatternRef instances must reference a local definition of a JourneyPatternTimingLink. Internal Integrity Rule I10a. id of each VehicleJourneyTimingLink must be unique within document. Internal Integrity Rule I10b. VehicleJourneyRef instances must reference a local definition of a VehicleJourneyTimingLink Internal Integrity Rule I11a. id of each VehicleJourneyStopUsage must be unique within document. Internal Integrity Rule I11b. JourneyPatternStopUsageRef instances must refer to a local definition of a JourneyPatternStopUsage. Internal Integrity Rule I12a. id of each VehicleJourneyStopUsage must be unique within document. Internal Integrity Rule I13. id of each JourneyPatternInterchange must be unique within document. Internal Integrity Rule I13. JourneyPatternInterchangeRef instances must refer to a local definition of a JourneyPatternInterchange Internal Integrity Rule I14. id of each VehicleJourneyInterchange must be unique within document. Internal Integrity Rule I16a id of each Operator must be unique within document. Integrity Ruile C7a. Codes of Operator declarations must be unique within document. Integrity Ruile C16b. OperatorIdRef instances must refer to a local definition of a Operator. Integrity Ruile C17a. Codes of Licencesed Operator declarations must be unique within document. Integrity Rile C17b. RegistteredOperatorIdRef instances must refer to a local definition of a Operator. Internal Integrity Rule U7a. PrivateCodes of Operator declarations must be unique within document. Internal Integrity Rule U9a. PrivateCodes of JourneyGrouping declarations must be unique within document. Internal Integrity Rule I18a. id of each DataRight must be unique within document. Internal Integrity Rule I18b. DataRightRef instances must refer to a local definition of a DataRight Internal Integrity Rule I18b. DataRightRef instances must refer to a local definition of a DataRight