incubator-odf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "DaLi Liu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ODFTOOLKIT-97) Provide a mapping table between ODF XML (DOM API) and components (DOC API)
Date Fri, 21 Sep 2012 02:46:07 GMT

    [ https://issues.apache.org/jira/browse/ODFTOOLKIT-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13460145#comment-13460145
] 

DaLi Liu commented on ODFTOOLKIT-97:
------------------------------------

There should be three verified status of each issue:
2.not sure - I am not sure about this issue, maybe still leave to be opened
                
> Provide a mapping table between ODF XML (DOM API) and components (DOC API)
> --------------------------------------------------------------------------
>
>                 Key: ODFTOOLKIT-97
>                 URL: https://issues.apache.org/jira/browse/ODFTOOLKIT-97
>             Project: ODF Toolkit
>          Issue Type: Bug
>          Components: codegen
>    Affects Versions: 0.8
>         Environment: Operating System: All
> Platform: All
>            Reporter: Svante Schubert
>            Assignee: issues
>             Fix For: 0.8.7
>
>         Attachments: ASF.LICENSE.NOT.GRANTED--ODF-Feature-List.ods
>
>
> Instead of pushing the need of a mapping between DOM XML to DOC Component further ahead.
> I decided to publish a very early draft to base further discussions upon how the mapping
between multiple ODF XML elements and attributes to a component can be done.
> Helpful might be the presentation about ODF Modularization that I held on the ODF Plugfest
in Granada recently (see http://plugfest.opendocsociety.org/lib/exe/fetch.php?media=plugfests:201004_granada:odfmodularization.odp).
> Prerequisites:
> 1) In the end all ODF XML should be mapped to ODF Components.
> The definition of the mapping file will allow us to track the current status of implementation,
the coverage of ODF elements by convenient API.
> 2) As we need this mapping for code generation it should be available for automatic processing
(preferable XML).
> This mapping configuration file does not have to be a plain XML file, but might as well
be a ODF Spreadsheet document to allow formatting, spellchecking and sort functionality of
columns/rows.
> 3) The overall count of XML nodes for ODF 1.2: ~600 Elements, ~1300 Attributes.
> Due to the large number, we should use as much automation of filling cells of the spreadsheet
as possible. For instance use schema2template to receive the possible children of an ODF element.
> For instance table:table is the root element for the Table component our first component.

--
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: http://www.atlassian.com/software/jira

Mime
View raw message