Dear TC members,
from the feedback of my colleagues, I did the following minor fixes to
the metadata proposal and uploaded it to:
http://www.oasis-open.org/committees/download.php/30371/08-12-12-ODF-Metadata-Change-Request.odt
1) As only relative URLs should be used to refer to inner package
resources within RDF/XML, the OWL properties 'pkg:idref', 'pkg:path'
and 'pkg:hasPart' (the pkg:hasPart to express the relationship of an
xml file and xml element with ID) become redundant.
In addition the wording of the relative URLs for inner package
references had been improved.
2) As stated previously GRDDL will extract the RDFa from content.xml
and styles.xml to RDF/XML and map the OpenDocument XML of the meta.xml
to RDF/XML via XSLT.
I was asked to add explicitly in the specification that the common
meta.xml elements should be mapped to RDF by an ODF application in a
defined way:
"All OpenDocument elements of the meta.xml should
be mapped to RDF.
The algorithm is provided by the OASIS hosted XSL stylesheet.
[Editor's
Note: Add link]
"
The stylesheet is an implementation detail, but a mapping from meta.xml
to RDF could be done as the following:
meta.xml:
<office:document-meta xmlns:office="....>
<office:meta>
<meta:print-date>2004-08-20T07:38:27</meta:print-date>
<meta:user-defined meta:name="achieved
at">26.08.2004</meta:user-defined>
<meta:user-defined meta:name="working
hours">5</meta:user-defined>
<meta:document-statistic meta:table-count="5"
meta:image-count="3" />
RDF (N3):
<DOCUMENT_IRI> meta:print-date "2004-08-20T07:38:27" .
<DOCUMENT_IRI> meta:document-statistic [meta:table-count "5";
meta:image-count="3"]
<DOCUMENT_IRI> meta:user-defined [meta:name "working hours";
meta:value "5"] .
<DOCUMENT_IRI> meta:user-defined [meta:name "working hours";
meta:value "26.08.2004"] .
Where <DOCUMENT_IRI> is the IRI to the document of the meta.xml
(document root).
E.g. the <DOCUMENT_IRI> for the meta.xml of the root document of
the uploaded proposal would be:
http://www.oasis-open.org/committees/download.php/30371/08-12-12-ODF-Metadata-Change-Request.odt/
Regards,
Svante
Svante Schubert wrote:
49402FBB.5040309@sun.com" type="cite">
Dear TC members,
As the previous approved metadata proposal was yet not integrated, I
have updated and uploaded a new draft based on the prior with change
tracking enabled [1] and will assist Patrick in its integration after
an agreement.
For now I would like to set this metadata proposal on the agenda of the
next TC call.
If you have any questions regarding the proposal, please send them to
me prior to the call. I believe the overall proposal is not
controversial and the discussion will take us less time than for a
single proposal.
Kind regards,
Svante
[1]
http://www.oasis-open.org/apps/org/workgroup/office-metadata/download.php/30347/08-12-10-ODF-Metadata-Change-Request.odt
Svante Schubert wrote:
493FE194.4010400@sun.com" type="cite">Dear TC
members,
from my feedback of the W3C Semantic Web Interest group I would like to
combine the previous three existing proposal parts to a single metadata
proposal, consisting of three parts:
Adaption
of W3C RDFa standard
Previously RDFa was not a W3C Recommendation and could not be reused in
our spec, now we are able to adapt the official standard.
Usage
of W3C GRDDL standard
Meant for non ODF applications to extract the RDF graph from our
content.xml, styles.xml and meta.xml streams via a referenced XSL
stylesheet.
Similar adapted by XHTML files using RDFa standard. The location of the
XSL stylesheet is resolved via the URL of the root namespace (ie. XHTML
use case) or via a GRDDL attribute in the root element (i.e. ODF use
case as namespace is an URN and no URL).
Therefore the only effort for ODF applications is a new root element
attribute, the effect enormous.
(After proposal acceptance I would create the XSL stylesheets and place
it on an OASIS server).
Adaption
of RDF mapping to relative URLs
Currently in the new RDF mapping file (manifest.rdf) an arbitrary URN
is
being invented for every ODF element described in the RDF graph. But
this creates troublesome URL alias. Instead the standard will require
that a resource (ODF element) will be mapped directly to its relative
URL.
Currently I am finalizing the overall proposal. In case I will be ready
this evening, I would set it on the agenda of the next TC call.
PS: The previous announced ODF 1.2 proposal of fragment identifier for
URLs
to ODF mime types is being withdrawn by myself, due to the amount of
proposals that have been requested to be considered for ODF 1.2.
Regards,
Svante
--
Sun Microsystems GmbH Svante Schubert
Nagelsweg 55 Software Engineer
20097 Hamburg StarOffice / OpenOffice.org Development
Germany Phone: +49(0)40 236 46 500
http://www.sun.com Svante.Schubert@sun.com
Sitz der Gesellschaft:
Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten
Amtsgericht Muenchen: HRB 161028
Geschaeftsfuehrer: Wolfgang Engels, Dr. Roland Boemer
Vorsitzender des Aufsichtsrates: Martin Haering
--
Sun Microsystems GmbH Svante Schubert
Nagelsweg 55 Software Engineer
20097 Hamburg StarOffice / OpenOffice.org Development
Germany Phone: +49(0)40 236 46 500
http://www.sun.com Svante.Schubert@sun.com
Sitz der Gesellschaft:
Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten
Amtsgericht Muenchen: HRB 161028
Geschaeftsfuehrer: Wolfgang Engels, Dr. Roland Boemer
Vorsitzender des Aufsichtsrates: Martin Haering
--
Sun Microsystems GmbH Svante Schubert
Nagelsweg 55 Software Engineer
20097 Hamburg StarOffice / OpenOffice.org Development
Germany Phone: +49(0)40 236 46 500
http://www.sun.com Svante.Schubert@sun.com
Sitz der Gesellschaft:
Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten
Amtsgericht Muenchen: HRB 161028
Geschaeftsfuehrer: Wolfgang Engels, Dr. Roland Boemer
Vorsitzender des Aufsichtsrates: Martin Haering
|