Suggested Changes on the Metadata proposal

[Svante Schubert <Svante.Schubert@Sun.COM>]

Greetings!

in general based on a detailed feedback from Michael we made up a list 
of suggested changes.
As it does not scale to discuss every wording change in the TC, nor has 
this been done earlier for the main spec, I separated the issues in two 
lists.

a) Issues to be discussed
b) List of editorial changes

Please note both lists is not complete yet, but should give us already a 
change to start discussing.
Patrick's idea was to start a thread on each issue. The idea is to come 
to an agreement on the list and approve the outcome on the items of a) 
during next TC call.

Note: Although I have already done changes on the working draft, the 
majority of the SC was against an update, therefore I won't make the 
working document public.

Issues to be discussed:
======================
I) Exchange of occurrences of OpenOffice to OpenDocument (Resolved)
Resolution: Agreed: On TC call on 07/06/06 to add the new elements to 
the spec.

II) Change of RDF/XML describing terms
Michael suggests to that description of RDF vocabulary uses no longer 
XML terms but RDF terms using node/property instead of element/attribute.
Furthermore the XML related brackets for elements '<' and '>' should be 
removed as well.

III) Removal of definition of non persistent odf:value property
Michael suggested to remove the following paragraph, as the described 
RDF property is not stored, but only available at runtime. Due to this 
case, the property would be out of scope of our metadata format 
specification.
“For every IRI representing an OpenDocument element an RDF statement can 
be made about the element content. In this RDF statement the element IRI 
is the RDF subject, the property of odf:content is the RDF predicate and 
the content literal of the OpenDocument element is the RDF object.”

IV) OWL definition of odf:path
Property has only been defined in OWL for odf:File not for odf:Element

V) Removal of odf:mimeType
Property would be redundant to MIME information of original manifest


List of editorial changes:
======================
1) Removal of sentence with duplicate content, mentioned in the previous 
introduction
"In addition to the metadata RDF/XML files, metadata may also be 
specified in content using the in content metadata (see section 1.2)."

2) Changed wording from:
"The metadata manifest file shall be stored at “/”. The metadata 
manifest file shall be named “manifest.rdf”."
to
"The metadata manifest file shall be named “manifest.rdf”, and shall be 
stored in root of the package."

3) Changed wording from:
"The metadata manifest file is based on RDF/XML and fulfills two basic 
functions:"
to
“The metadata manifest file fulfills two basic functions”.
That it is RDF/XML is said below already, and not related to the purpose 
of the file.

4) Changed wording from:
"The package (i.e. the document) is identified by the IRI of the 
rdf:about attribute on the <odf:Package> ."
to
"The identifier (IRI) of the odf:Package RDF node becomes also the 
identifier of the document which contains the metadata manifest."

5) Moved Ontology definition from the owl schema of "Metadata Package" 
section to "Metadata Manifest".

6) Minor fixes in first OWL schema comment (ie. title, date and copyright)

7) Changed wording from:
"The <odf:ContentFile> class represents the content.xml file. "
to
"The <odf:ContentFile> class represents a content.xml file."
(The above is done analogue for odf:StylesFile)

8) Changed wording from.
"The <odf:Element> class represents an XML element of the OpenDocument 
format."
to
"The <odf:Element> class represents an XML element in a content.xml or 
styles.xml file."

9) Removal of redundant sentence:
"An <odf:Element> class represents an OpenDocument element found in an 
content.xml or styles.xml file."

10) Removal of redundant sentence:
"The IRI of an <odf:Element> class is used within a RDF/XML metadata 
file to refer to an OpenDocument element."

11) Changed wording from:
"In content metadata can be used to treat the literal content from the 
content.xml and styles.xml files as an RDF object."
to
"In content metadata can be used to make some literal content of 
content.xml or styles.xml files into the objects of RDF statements."

12) Changed wording from:
"The following attributes are used for in content metadata:"
to
"The following attributes can be attached to above elements to specify 
in content metadata"

13) Renaming "common-meta-attlist" to "common-in-content-meta-attlist"

14) Structure changes:
For consistency reasons define all in content metadata attributes in an 
individual section, as it will be the case in the main specification.


Regards,
Svante