[OASIS Issue Tracker] Commented: (OFFICE-2259) Invert Special-Casefor Conformant OpenDocument Packages

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Michael Brauer commented on OFFICE-2259:
----------------------------------------

The only difference between the new conformance class and the Conforming OpenDocument Package class is that the mimetype file and the entry for "/" shall exist. That they have the same value is already said in clause (PD1.3.4).

We further state in part 1 that for all ODF document types the mimetype file must be present.

Therefor the new conformance class would only have an impact on non ODF document types, and would replace the "shoulds" regarding the existence of mimetype information with a shall. Does this justify a new conformance class, if we on the other hand discuss to remove the extended conformance class?

But maybe your concern is that we currently allow the situation where a mimetype stream is present but to file entry for "/" in the manifest and vise versa. One indeed could consider that to be an issue, or at least to be unintended. So, what about the following: Instead of adding a new conformance class, adapt the conforming package class as follows:

(PD1.2.8)The [META-INF/manifest.xml]  file should contain a <manifest:file-entry> element whose manifest:full-path attribute has the value "/". This entry shall provide information regarding the content stored in the package. *This entry shall exist if the package contains a file "mimetype"*.

(PD1.3.4)If the file named "META-INF/manifest.xml" contains a <manifest:file-entry> element whose manifest:full-path attribute has the value "/", then *a "mimetype" file shall exist, and* the content of the "mimetype" file shall be equal to the value of the manifest:media-type attribute  3.8.10 of that element.


> Invert Special-Case for Conformant OpenDocument Packages
> --------------------------------------------------------
>
>                 Key: OFFICE-2259
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-2259
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Improvement
>          Components: Conformance, Packaging
>    Affects Versions: ODF 1.2 Part 3 CD 1
>         Environment: This issue applies to ODF 1.2 Part 3 CD01 (file OpenDocument-v1.2-part3-cd01.odt plus the PDF and HTML formats)
>            Reporter: Dennis Hamilton
>            Assignee: Dennis Hamilton
>
> This issue is a companion to OFFICE-2257.
> 1. The changes proposed in OFFICE-2257 continue to allow mimetype and <mainfest:file-entry> with manifest:full-path="/" to be optional (though recommended).  There are no conditions placed on the values when both are present.  That becomes the situation for Conforming OpenDocument Packages.   
> 2. If it is desired to distinguish a specialization of Conforming OpenDocument Packages that is the prefered case for normative profiling in ODF 1.2 Part 1, that can be done by adding a specialized for that is a logical subclass of Conforming OpenDocument Package, rather than an extension beyond it.
> 3. This issue proposes one way to do that.   The advantage is that everything that applies to Conforming OpenDocument Packages applies to the specialized target.  There is no need to mention the specialized target except in section 7.2.2.   This is then available for reference from other specifications in profiling their use of ODF 1.2 Part 3 Packages.

-- 
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