OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Commented: (OFFICE-2577) Public Comment:Multiple RDF files and the Single XML document



    [ http://tools.oasis-open.org/issues/browse/OFFICE-2577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18940#action_18940 ] 

Michael Stahl  commented on OFFICE-2577:
----------------------------------------

1. Multiple RDF files

Unlike, say, HTML documents, ODF documents are not meant to be produced by one
application and then displayed by another application.  The main use case for
ODF documents is that they are loaded by an office application, modified, and
then stored again.  This means that metadata is not only added and displayed,
but may also be edited and removed.

Now assume that some component of the application that handles some kind
of metadata wants to remove its metadata from the document.
If all the RDF statements are in one graph, how does it find out which
statements it should remove?
If it removes too few statements, then the user may have a privacy issue.
If it removes too many statements, then unrelated components may break,
because their RDF statements are gone.
Because RDF vocabularies may be reused, different components of an
application (or different extensions of an application) may reasonably use
the same predicates and types in the RDF statements they add.
By giving each component their own RDF graph in the document, we can
isolate them much better, thus enabling modularization.
Deleting all metadata of one component simply means removing its RDF graph.

Furthermore, consider the possibility that a document has more than one author.

I am not sure if there are performance advantages to having a single RDF file.
Maybe an application is only interested in a single RDF graph; such an
application would perform better in a multi-file design, because it need
not load all triples, but only the manifest and the file it is interested in.

So there is no need for change here.

2. RDF in flat file ODF

Indeed it is currently not specified how RDF metadata could be stored in a
flat
file ODF document.
Some clarification regarding the future (if any) of flat file ODF
documents would be helpful.


> Public Comment: Multiple RDF files and the Single XML document
> --------------------------------------------------------------
>
>                 Key: OFFICE-2577
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-2577
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Metadata
>    Affects Versions: ODF 1.2 Part 1 CD 4 
>            Reporter: Robert Weir 
>            Assignee: Svante Schubert 
>            Priority: Blocker
>
> Copied from office-comment list
> Original author: Søren Roug <soren.roug@eea.europa.eu> 
> Original date: 28 Feb 2010 12:53:07 -0000
> Original URL: http://lists.oasis-open.org/archives/office-comment/201002/msg00038.html

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]