Release 2.0e TransXChange is intended to be a stable version suitable for suppliers to develop against.



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



    It has been tested against JAXB and MS validators.



    It is accompanied by a set of nine example documents available at www.transxchange.org.uk.

        - The examples are intended to demonstrate the use of every TXC feature 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 and large volumes are planned.

    

    A revised version of the Schema Guide is available with extensive revisions.





=============

The following is a list of the main changes in 2.0e 





Revisions

    * Full compatibility with NapTAN 2.0b features.



    * Revise Flexible service support to allow mixed flexible / Standard Journeys [Workshop feedback]

    

    * Revise Operational date support to be more uniform and to allow operation profiles at the Journey Pattern Level

            [Workshop feedback, AIM, Infocell]           

           

    * Revise Frequency based service support to allow end time & minutes past the hour. 

      Distinguish FrequentService.   

    

    * Allow distinction between calendar & actual Christmas day etc [AIM]

    

    * Revise dead run support to allow explicit short working.

    

    * Allow reuse of Operator definitions (This also allows TXC to be used to exchange operators details]. [Workshop feedback]

        

    * Allow annotation of associated operator role. [AIM]

    

    * Add Address, Contact Number & Location to Garage [WYSPTE ] 

    

    * Add Support for variable bay allocation. [RS]

      This allows BCQ stops to assigned to one or more BCS stops.

         Note that variable stop allocation requires the vehicle journey to be specified, so the initial

         implementation is not efficient for the exchange of bay allocations without a timetable, which

         has been noted as a further requirement [WYSPTE].

        A  backwards compatible (i.e. point release) enhancement could be made to address this.

    

    * Revise Registration/Service relationship to allow for specification of connecting services in a registration [WYSPTE]

      Introduce a LicencedOperator which so that fully specified and partially specified operator details can be specified.

    

    * Improve default and clarify semantics of journey pattern link referencing and defaulting of values.

    

    * Systemise service references in registration. 

     

    * Add Holidays only to day types  so that can specify services that only run on holidays.

    

    * Make VehicleJourneyCode mandatory [WYSPTE]

    

    * Support TicketMachineServiceCode at JP & VJ level [WYSPTE]

 

    * Add description to service. [RS]

    

    * Allow Track on  PositioningLink. [WYSPTE ] 

    

    * Allow description of School terms.    

     

    * WYSPTE Revise RunningBoard to allow separate Board, BoardNumber and BoardNote [WYSPTE ] 

    

    * Additional key ref constraints to enforce data integrity.

              

    * Rename InterchangeMode to TransferMode to avoid confusion.

    

    * Enable for future revision for exchange of just deltas to schedules.





Fixes 

   Fix undecidable Location representation