[
https://issues.apache.org/jira/browse/ODFTOOLKIT-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tao Lin updated ODFTOOLKIT-50:
------------------------------
Attachment: patch_20120711.txt
Hi Svante,
I used the old HP maven artifacts, because rdfa-core-java is utilized for
parsing RDFa. The latest version of rdfa-core-java depends on the old HP Jena.
I found some bugs in rdfa-core-java. We need to modify/extend the code of
rdfa-core-java before using it. That violates its licence of LGPL.
Now I switch to java-rdfa (http://code.google.com/p/rdfa-core-java/) for RDFa
sax parsing. The dependencies of odfdom-java have been changed to the new
apache Jena artifacts with the test one.
You can play with the new patch: patch_20120711.txt.
> [gsoc2012] Add ODF 1.2 RDF metadata support to ODF Toolkit
> ----------------------------------------------------------
>
> Key: ODFTOOLKIT-50
> URL: https://issues.apache.org/jira/browse/ODFTOOLKIT-50
> Project: ODF Toolkit
> Issue Type: New Feature
> Components: generator
> Affects Versions: 0.7.5
> Environment: Operating System: All
> Platform: All
> Reporter: Svante Schubert
> Labels: gsoc, gsoc2012, mentor
> Fix For: 0.8.6
>
> Attachments: grddl_test_patch.txt, patch.txt, patch_20120618.txt,
> patch_20120710.txt, patch_20120711.txt, test_rdfmeta.odt, test_rdfmeta.odt,
> test_rdfmeta.odt
>
>
> This is one of the greatest features for ODF 1.2 to allow the usage of RDF
> metadata on the document and the most important elements.
> As a co-editor of this spec, I got a special interest in making this feature
> come alive. In addition it has a positive side affect to the new OOo API,
> when scenarios are not even tested in the office, but as well from a
> different ODF library.
> Before creating a convenient API, the basic package feature has to be
> supported.
> Still I believe the usage of an RDF parser is still optional to keep ODFDOM
> small and give the user only what he really wants.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
