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-2404) NEEDS-DISCUSSION: manifest.rdf, mandatory or not ?

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

Michael Brauer commented on OFFICE-2404:

Dennis: First of all, this issue has been set to resolved to indicate that there is a resolution. Of cause, any resolution may be discussed or refined, but we need to advance the status of the issue to indicate that there is something to review.

But you are right. It should be "manifest.rdf" rather than "manifest.xml". And it also should not read package, but document and  subdocument. So an updated proposal is:

Add to Part3, Section 2.6, third paragraph: 

The "manifest.rdf" file may list other files which are contained in the document or sub document that contain RDF metadata, like files that contain RDFa metadata. The "manifest.rdf" need not exist if a document or sub document does not contain any files that contain RDF metadata. 

Change 2nd paragraph of section 4.2.1 to:

In addition to the mechanism defined in Part 3 of this specification ** RDF metadata can be attached to elements *in the "content.xml" and "styles.xml" file.* Elements supporting this *kind of* metadata have the following attributes: xhtml:about 19.907, xhtml:property 19.910, xhtml:content 19.908, and xhtml:datatype 19.909. When metadata is added using *these* attributes, it is referred to as in content metatada. *"content.xml" and "styles.xml" files that contain in content metadata shall be listed in the document's or sub document's "manifest.rdf" file.*

The purpose of the manifest.rdf file is that it provides a single entry point for an RDF-aware application to all RDF metadata in a document. It is therefore reasonable that is it required and lists all files containing RDF metadata. Otherwise an application would have to scan all files for RDF metadata, what may become expensive.

> NEEDS-DISCUSSION: manifest.rdf, mandatory or not ?
> ----------------------------------------------------------
>                 Key: OFFICE-2404
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-2404
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Improvement
>          Components: Metadata
>    Affects Versions: ODF 1.2 Part 3 CD 1, ODF 1.2 Part 1 CD 4 
>            Reporter: Bart Hanssens
>            Assignee: Michael Brauer
>            Priority: Minor
>             Fix For: ODF 1.2 Part 3 CD 2
> says
> "The OpenDocument document contains a metadata manifest,"
> Reading part 3, section 2.6 Metadata
> "A document or sub document that is stored in a package may contain an arbitrary number of metadata files....
> All metadata files of a document or sub document shall be listed in a separate metadata manifest file, which has the file name "manifest.rdf""
> So it seems that it is absolutely required to have a metadata.rdf manifest file, even if there are no RDF metadata files at all ? Is that correct ?

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]