[ 
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_20120722.patch

Hi Svante,

1) DOCUMENT_URL is originally used as a parameter by odf2rdf.xsl. Now I modify 
odf2rdf and rename the parameter to sourceBaseURL, in order to avoid adding a 
new semantically identical parameter.
As for the file URI, one slash and three slashes are both valid in ordinary 
java programming. However, Jena recognizes only the three slashes style as the 
RDF base URI. Therefore I just modify OdfPackage.getBaseURLFromFile() to make 
it return the three slashes style URI.

2) I have added the licence headers. Thanks for the reminder.

3) I've expanded the tests with the 5 elements:
<table:covered-table-cell> <table:table-cell> <text:h> <text:meta> <text:p> 
The SafeCURIE and CURIE are also tested.

In the next step, I will work on the special <bookmark-start>. The bookmark can 
start and end at any arbitrary text positions in the document. I'm troubled by 
extracting the the literal content between the <text:bookmark-start> and 
<text:bookmark-end>. Any suggestion? If I cache the bookmark RDF triples during 
parsing, the cache should be updated whenever users change any of the text 
literal between them. It's difficult to track the changes. Could you tell me 
how to deal with bookmark? Any better approaches?

Thanks in advance!
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, patch.txt, patch_20120618.txt, 
> patch_20120710.txt, patch_20120711.txt, 
> schema2templates-metadata_20120718.patch, 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

        

Reply via email to