Normalization of ODF XML (Earlier - Re: IRC log from today's meeting - 2013-10-09)

[Svante Schubert <svante.schubert@gmail.com>]

For the description of ODF XML test output and for the comparison of ODF XML of different applications an ODF normalization is useful.

In our last meeting we listed already several points, where ODF XML may differ, but the ODF document not:

Am 09.10.2013 16:18, schrieb Svante Schubert:

[15:52] Svante Schubert: Other examples of ODF variations of the same document lead to in different XML:

[15:52] Svante Schubert: 1) Order of automatic styles

[15:52] Svante Schubert: 2) automatic style names

[15:52] Svante Schubert: 3) text:space elements might be split or a single one (similar to span)

[15:52] Svante Schubert: 4) span can also be nested or split

[15:52] Svante Schubert: 5) Hyperlink can be split as well

[15:52] Svante Schubert: 6) Further existence of optional elements/attributes..

[15:55] Svante Schubert: An implementation note: Nesting spans should be avoided it just makes things complicated (traversing recursivly content, searching for spans, inheriting.. etc.)

In addition I would like to add that the text properties of an automatic paragraph style are equal to the text properties of an automatic text style, which uses a span embracing the full paragraph content.

This will be mapped, when two paragraphs will be merged and the text properties of the automatic paragraph style of the second paragraph will be mapped as span around the remaining content of the second.

In addition, whenever an ODF application does a "Clear Formatting", which removes all the "hard" text attributes. The automatic text properties of automatic paragraph styles are being mapped to spans to the remaining "uncleared" area of the paragraph.

Does anyone know further examples or categories of examples?

Thanks,
Svante