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: ODF 1.0 metadata notes

As I was just looking at the existing ODF metadata support again, some 
quick notes on how it lines up with RDF, and with my argument on 
requirements ...

Taking an ODF document, I made the following changes, which validated 
as RDF:

1)  moved the "office:version" property attribute on the root to a 
child element of "office:document-meta"
2)  changed the "office:document-meta" root to "rdf:RDF"
3)  added an "rdf:about" attribute to the "office:meta" element

That's it. It's valid.

An alternative would be:

1)  change the "office:document-meta" root to "meta:Document"
2)  add an "rdf:about" attribute to the root
3)  removed the "office:meta" child
3)  add "office:version" as child of root

Also valid. Looks like so:

<?xml version="1.0" encoding="UTF-8"?>
     <meta:initial-creator>Bruce D&apos;Arcus</meta:initial-creator>
     <dc:creator>Bruce D&apos;Arcus</dc:creator>
     <meta:user-defined meta:name="Info 1"/>
     <meta:user-defined meta:name="Info 2"/>
     <meta:user-defined meta:name="Info 3"/>
     <meta:user-defined meta:name="Info 4"/>
     <meta:document-statistic meta:table-count="0" meta:image-count="0" 
       meta:page-count="1" meta:paragraph-count="5" meta:word-count="32" 

To find a document title, then, the xpaths (assuming the document as 
root) are:

	original: "office:document-meta/office:meta/dc:title"
	RDF option 1 above: "rdf:RDF/meta:Document/dc:title"
	RDF option 2: "meta:Document/dc:title"

In fact, the first two could be represented with a generic xpath that 
covered both:


Instant compatibility at the xpath level between ODF 1.0 and 1.2 

The xpath to a grab a title for the bibliographic data I am imagining? 
The same!

(though of course one would be grabbing a different sub-document, and 
accessing it by URI value)

This is just to emphasize what I've been saying all along: that adding 
RDF support to ODF could be -- from the perspective of backward 
compatibility -- an absolutely trivial change, but also add tremendous 
power going forward.

The existing metadata support is already almost-RDF, the metadata 
contents already are stored apart from the document and registered 
using the manifest, and they already have some expectations about 

My requirements thus build on this.

More on Thursday of course ...


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