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

 


Help: OASIS Mailing Lists Help | MarkMail Help

office-metadata message

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


Subject: Minor fixes on the metadata manifest


Some problems found in the metadata manifest and suggestions how to fix 
them:

1)
Adding NamedGraph to the mm:Entry, as rdf:type not possible in a typed 
node (see. 
http://www.w3.org/TR/rdf-syntax-grammar/#section-Syntax-typed-nodes).
But we would simply rename Entry to NamedGraph and we archieved the same.

2)
I realized have not added the document base ID to the spec so far. It 
could be:
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#";>
    <rdf:Description rdf:about=".">
        <rdf:type 
rdf:resource="http://docs.oasis-open.org/office/2007/03/meta/manifest#Manifest";>
        <mm:baseId>urn:odf:122015dd-e58e-411f-8c3e-dd0b6d7be7d6</mm:baseId>
       ..

Which is similar to the typed node:
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"; 
xmlns:mm="http://docs.oasis-open.org/office/2007/03/meta/manifest#";>
    <mm:manifest mm:baseId="urn:odf:122015dd-e58e-411f-8c3e-dd0b6d7be7d6">
    ...

3) We had in every entry (now NamedGraph) a type. The idea was to 
specify the problematic the plug-in is solving by the type (e.g. VCard).
Although this not our direct scope as it is already application logic, 
it is necessary for the plug-ins to 'find' their RDF/XML, after a 
document is loaded ( they should not rely on file names).

The question arises: What is the relation between this type and a 
NamedGraph (in RDF/XML always a file)?

Let's examine the following scenario:
A plug-in uses an address book with a NamedGraph/File with VCard 
information and a citation plug-in would use a NamedGraph/File with 
VCard information in the same document.
For me as a user, I do not want to have every VCard entry of the 
citation in my address book!

Therefore the relation is: one type can have multiple NamedGraphs.
To underline this I would suggest to bundle a set of NamedGraphs to 
build up a hierarchy.

4)
We have the idea the binding between RDF statements and  ODF elements is 
made by ODF related RDF in the various RDF/XML.
Florian would be happy, if we would move these bindings as sub-elements 
of an entry (NamedGraphs).
I support this idea, as the binding via xml:id between the RDF/XML files 
and the Office XML files is only in one place.

Svante


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