Adding ODF 1.3 support to the ODF Toolkit

[svanteschubert]

I have started a branch of the 0.9.0 version to support ODF 1.3.
but decided in discussions with Michael Stahl and Oliver Rau afterwards that it might be easier to have an ODF 1.3 support based solely on the upcoming ODF 1.0.0 version.
The reason for this is that 1.0.0 is the merge of a several-year-old merge form Open-XChange using ODFDOM for their backend of their new OX Documents.

In the following, I am starting a listing what needs to be fixed - this is likely being updated during the lifetime of this issue.
This documentation should be added to our SITE documentation to describe how to do an ODF version change in the future.

Changes expected so far:

1. The generator project needs to generate new ODFDOM typed DOM classes from the new ODF XML schema/grammar files. These files need to replace the ODFDOM prior classes for elements and attributes.

2. The generator tests have to be adopted to embrace ODF 1.3.

3. The ODF Validator needs to have an ODF 1.3 instead of an ODF 1.2 option.

4. The ODF templates within ODFDOM - being used when creating new documents from the scratch needs to be added to ODF 1.3.
   I did this usually by editing the XML within the ZIP using JEdit with its archive and its XML extension.

[svanteschubert]

For simplicity reason, we are not providing yet the support of multiple versions at the time or the transformation of one version to the other.
IMHO this functionality should be described at the specification level, explaining the differences to the prior ODF version in a way that transformations can be generated.

[svanteschubert]

5. The HTML form of the ODF specification has to be exchanged with all its images.
   Test the HTML specification - should already be done on TC level, but better be safe than sorry:
   5a: A broken link check should be done
   5b: OLE objects in the specification should have been exchanged with images, otherwise they won't be visible in the HTML version - for instance by taking a look at into the ODT if there are still OLE objects.
6. The taglet module, which is doing insertions of in the ODFDOM JavaDoc to the HTML form of the ODF specification has to be updated to reference to a new specification.

[svanteschubert]

NOTE: The current ODF 1.3 branch based on the master will be abandoned and new ODF 1.3 branch will be created for the 1.0.0 release branch.

[svanteschubert]

There are 36 new feature/enhancement in ODF 1.3.
They are described in detail in the OASIS JIRA bugtracker, there is a query for ODF 1.3 feature/enhancment.

An overview of the changes from “Open Document Format for Office Applications (OpenDocument) v1.2”
can be found in the end/appendix of each ODF 1.3 specification part:

• Part 2: Packages
• Part 3: OpenDocument Schema
• Part 4: Recalculated Formula (OpenFormula) Format

PS: I am about to start a GitHub for the OASIS TC to bundle tools for the specification & test documents at OASIS standard level.