Release 2.0g TransXChange is will contain any fixes that are incldued in the be a final version  

    It shares common NaPT data types with the NaPTAN 2.0d release which is released simultaneously 

    It has been tested against Java and MS validators.

    It is accompanied by a set of  example documents available at www.transxchange.org.uk.
        - The examples are intended to demonstrate the use of all the main TXC features and every possible route topology.
          An index page shows which features are used one each example.
        - Each example is explained by a web page with timetable and route maps.
        - Some further examples covering partial exchange of data are planned.
    
    A revised version of the Schema Guide is available with minor revisions.
    
  

=============
Revisions in 2.0g

The following is a list of the main changes in 2.0g from 2.0f

Changes that may cause breakage in 2.0e implementations are marked with a ++ 

 03/11/2004
     * [NaPT]  Restrict lengths on NaPTAN Names  to 48 character
 11/11/2004
    * [NaPT dates]   [NaPT dates correction Make NotThursday   NotFriday AllHolidaysSinceChristmas empty type
    * [common]   Make OffPeak empty type
    * [TransXChange_Registration constraints] Separated Unique and key constraints 
    * [TransXChange_Registration & General constraints] Fix key selector of  Garages
    
 15/12/2004   
     * NaPT base types revised to 2.0d. See Naptan Change notes