incubator-odf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Florian Hopf (JIRA)" <>
Subject [jira] [Updated] (ODFTOOLKIT-39) INTERNAL TOOL: Find differences between RNG schema versions
Date Wed, 19 Dec 2012 06:11:19 GMT


Florian Hopf updated ODFTOOLKIT-39:

    Fix Version/s:     (was: odfdom-0.8.7)
> INTERNAL TOOL: Find differences between RNG schema versions
> -----------------------------------------------------------
>                 Key: ODFTOOLKIT-39
>                 URL:
>             Project: ODF Toolkit
>          Issue Type: Improvement
>          Components: codegen
>    Affects Versions: simple-odfdom-0.8
>         Environment: Operating System: All
> Platform: All
>            Reporter: Svante Schubert
>            Assignee: issues
>            Priority: Minor
> If we would like to load/save different ODF version with using only one internal ODFDOM
model (most likely a model of the latest ODF), there are some prerequisites.
> Before we are able to transform one ODF version to another, we first need to know how
the ODF releases differ in terms of XML:
> a) What elements or attributes are new in an ODF release
> b) If parent or child nodes are different.
> For instance if same elements and attributes are allowed as children?
> Has the parent (of element/attribute) being changed?
> Has the attribute value set being changed?
> Are there new/changed datatypes?
> This tool might be a new functionality of relaxng2template.
> (As side information the total number of elements and attributes being used would be
of interest as info log after creating the documents, similar element/attributes with identical
local names).
> The information gathered might later being used in JavaDoc as well.
> We could use our own taglet or reuse the JDK @since 
> Later results will give us more insight about the scenarios. Perhaps an element was introduced
in 1.0, but changed in 1.1? Or even worse removed in 1.1 and readded in 1.2?
> Based on the results of this work, we can work out a mapping for a transformation and
could easily load/save ODF in arbitrary versions.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message