TransXChange Publisher Version 2.1_1

(c) 2005-2007 Crown Copyright.
Developed by Kizoom limited. http://www.kizoom.com

15 February September 2007

============================================================
See also 

   a) Publisher 2_2_1 Readme
   b) TransXChange Technical FAQ at  http://www.kizoom.com
   c) TransXChange Schema  Guide
   d) Suggestions for 2.2a schema

The TransXChange schema is complex and can be populated in a wide number of ways by different tools. 
The TransXChangePublisher necessarily makes a number of assumptions about how documents are encoded, and does not optimise its output for every case.   
Like all software, it also subject to bugs, both in the Publisher Application and in tthe udnerlyign framwroks and platforms that it uses.

As new considerations arise, the features, optimisation of the Publisher will be improved, and bugs corrected. 


Note that in some cases a workaround exists for a specific presentation issue by encoding a TXC document in a  particular way. In other cases a fix or enhancement to the publisher will be needed. 
 
In thsi docuemnt we list known issues, with status and work arounds.
 


The following are known issues with the 2_1_1 version of the TransXchange Publisher

2_1_1_issue_1. Blank Rows in Matrix Timetable

   If the same journey pattern is used for weekday and Saturday journeys and some stops are not visited on say the weekend days,    unnecessary rows showing stops with no times may appear in the matrix.  
    
   ==>Status. This is a missing optimisation in the publisher and will be corrected in the gui2_1_2 & ws2_1_2 versions of the publisher to suppress such rows.
  
   ==>Workaround. Use a different joruney pattern for each different day group, omitting the unvisted stops.
 

 
2_1_1_issue_2. Repeated Rows in Matrix Timetable

  When building the matrix rows,  the current version of the publisher assumes the use of  journey sections in journey patterns will be optimised   such that there will be only one journey pattern section for any given sequence of stops; consequently it places additional sections as a separate sequence after the first sequence. 
  this can result in a suboptimal presentation with the same stops being repeated many times over, causing the matrix to be extended downwards over many pages..  

   ==>Status. This is a missing optimisation in the publisher and will be corrected in the gui2_1_2 & ws2_1_2 versions of the publisher.
  
   ==>Workaround. Use explciit stop sequences ot controlk exact order, or recode the XML document not to repeat stops in different stop journey sections.