[
https://issues.apache.org/jira/browse/ODFTOOLKIT-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tao Lin updated ODFTOOLKIT-50:
------------------------------
Attachment: odfdom-metadata_20120814.patch
Dear Svante,
Please check the latest patch (20120814). Here're the improvement description
of the problems you mentioned last time:
1) I've fixed the bug by modify ResourceUtilities, so that all URI path is of
"file:///" the 3 slash style.
2)
a) Yes, the package names of Jena in Apache are not changed. Maybe they
consider backward compatibility.
b) Jena provides the RDF API with the most popularity. If we switch to other
RDF engines, how to deal with the API? What class of object will be return, if
we call getRDFaMetadata()?
c) I've changed URIExtractor10 to URIExtractorImpl, and remove the public
modifier of some classes.
e) It seems that only BookmarkRDFMetadataExtractor should be put into
...dom.rdfa. The others are mainly about RDFa parsing. I saw that XML Dom
parsing is put in ...pkg, such as OdfFileSaxHandler. I think for RDFa parsing,
the code should be in ...pkg.rdfa. I've made changes in this way.
For github, please push my last work (20120806) into the github as a fork.
Please also add my account ([email protected]) to the github project with
commit authentication right, so that I can push that of 20120814. Thanks a lot!
Best regards,
Tao Lin
> [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, odfdom-metadata_20120718.patch,
> odfdom-metadata_20120722.patch, odfdom-metadata_20120725.patch,
> odfdom-metadata_20120729.patch, odfdom-metadata_20120802.patch,
> odfdom-metadata_20120806.patch, odfdom-metadata_20120814.patch,
> patch_20120618.txt, patch_20120710.txt, patch_20120711.txt, patch.txt,
> schema2templates-metadata_20120718.patch,
> schema2templates-metadata_20120806.patch, test_rdfmeta.odt, test_rdfmeta.odt,
> test_rdfmeta.odt, 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
