XSL documents to generate XHTML and PDF reports using FOP.

As part of an application's requirements, the generation of web and PDF-based reports is required. An XML data structure containing sufficient necessary information to generate this report has already been defined (and can still be tweaked if necessary), however a translation document to convert this data to a formatted, readable document is required. ## Deliverables As this is required in a project that is based around Java/XWT with the choice made to use FOP for PDF generation, the preference is that this makes use of a single XSD that can generate both report formats. Sample output from an older version of the application will be provided, which the output is expected to closely match. Reports will need to automatically handle splitting over multiple pages, as will the media=print version of the xhtml/CSS report - that is, if the report contains more data than can be displayed on a single page of the configured size (must be configurable rather than hard-coded - ie, must support A4, Quarto, etc and be dimension independent), it must understand how to start a new page with the header, and continue printing rows/blocks of data on the following page(s), and number pages in the common footer to appear on each page. A xhtml version of the page is expected to be capable of being styled via CSS with no modification to the document itself. The reports are for presenting the results of race events, sport agnostic (eg, it could be motorsport, it could be cycling, it could be cross country running). Five reports will be required to be generated - A standard race result; A practice/qualifying report (essentially the race result but in fastest time order); A listing of lap times; A detailed listing of lap times (including sector times and speed trap times); finally a lap chart (a report which shows the position of each competitor on each lap of an event. The XML data structure, already defined, is set up in such a way that it contains Teams, and Competitors (which can be in a team or individual), all their details, race results including laps, and sector times/speed trap times for each lap. This will be looked up from the structure, rather than repeated within the XML document. Lastly, the ability to embed images, of which the location and dimensions can be specified, is desired. There are no tight performance requirements of this, but it is expected that a modern system can complete the conversion in approximately one second using the selected libraries (Java with FOP). If necessary, providing a test harness for passing an input data (XML) and schema (XSD) to produce an output file can be discussed. There is no significant time constraint on completion of this, however production of two particular reports first would be helpful to internal testing, for which payment can be incremental. Developers are expected to understand that by undertaking this work, you are assigning the employer right to use, reproduce, sell and modify this code and/or derivative works. There is no expectation of sole ownership, and the developer retains the right to use this code for their own purpose in future projects.