[
https://issues.apache.org/jira/browse/ODFTOOLKIT-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svante Schubert updated ODFTOOLKIT-458:
---------------------------------------
Attachment: Gephi-GraphML-Odf-Table-View.png
table_table.graphml
After building generator/schema2template of the codegenerator branch of my
GitHub fork, there will be GraphML files for all XML element of PuzzlePieces
(see https://incubator.apache.org/odftoolkit/0.6.2-incubating/schema2template/)
under
<TOOLKIT_ROOT>/generator/schema2template/target/graphML/<SCHEMA_FILE_NAME>
For instance, OpenDocument-v1_2-os-schema_rng/ as <SCHEMA_FILE_NAME>
The table_table.graphml file is attached similar a screenshot from the rendered
GraphML in Gephi, after using the forceLayout and several layout extensions.
(Gephi is basically an Application build on top of Netbeans). A description
how you tune the layout can be found at
https://gephi.org/tutorials/gephi-tutorial-visualization.pdf
Note: The graphml screenshot is of the previous version, the current one alrady
marks graph edges representing a sequence green and providing an order
attribute.
> Map the ODF XML RelaxNG schema into a GraphDB for Analysis
> ----------------------------------------------------------
>
> Key: ODFTOOLKIT-458
> URL: https://issues.apache.org/jira/browse/ODFTOOLKIT-458
> Project: ODF Toolkit
> Issue Type: Wish
> Reporter: Svante Schubert
> Assignee: Svante Schubert
> Attachments: Gephi-GraphML-Odf-Table-View.png, edge.properties,
> odf12-graph.xml, table_table.graphml, vertex.properties
>
>
> *PROBLEM*
> The ODF XML (RelaxNG) schema is too big to easily read or be analysed by
> humans.
> In version ODF 1.2 it has 598 elements and 1300 attributes.
> *SOLUTION*
> Therefore I would love to load the ODF XML RelaxNG schema into a GraphDB (for
> instance Neo4J) and do some basic analysis (sanity checks) on it.
> For instance, I am curious on query questions as:
> a) is a certain ODF element able to become nested (e.g. <text: p>)
> b) is every ODF element with an ID allowed to exist more than once (this
> issue occurred)
> c) what is the minimum mandatory ODF XML document
> etc.
> These queries could help a lot to understand and test the XML schema.
> Certainly, I would love to have afterwards more tooling.
> For instance, to be able to add metadata to the nodes to categorise nodes
> (which are meant for metadata, styles, text container, which are just plain
> boilerplate (e.g. office:body)
> The idea is to improve the generation of ODFDOM source code to allow easier
> maintainability.
> *DESIGN IDEA*
> Instead of reading plain RelaxNG, I thought it might be a better idea to read
> already a 'normalised' document the dumped internal model from MSV. You may
> find the dump for each ODF version as test references from
> <ODFTOOLKIT_ROOT>/generator/schema2template/src/test/resources/examples/odf
> e.g.
> http://svn.apache.org/viewvc/incubator/odf/trunk/generator/schema2template/src/test/resources/examples/odf/odf12-msvtree.ref?revision=1167972&view=co
>
> NOTE:
> You may find more about the information on the dump and the MSV model in:
> <ODFTOOLKIT_ROOT>/generator/schema2template/src/main/java/schema2template/example/odf/OdfHelper.java
> and
> <ODFTOOLKIT_ROOT>/generator/schema2template/target/apidocs/index.html
> https://incubator.apache.org/odftoolkit/0.6.2-incubating/schema2template/
> I would love to have a discussion on further thoughts of yours on the list.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
