[OASIS Issue Tracker] Updated: (OFFICE-2257) NEEDS-DISCUSSION:Package 7.2.2 Conforming OpenDocument Extended Package Not Useful

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

     [ http://tools.oasis-open.org/issues/browse/OFFICE-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dennis Hamilton updated OFFICE-2257:
------------------------------------

    Summary: NEEDS-DISCUSSION: Package 7.2.2 Conforming OpenDocument Extended Package Not Useful  (was: Package 7.2.2 Conforming OpenDocument Extended Package Not Useful)

I am confused by the statement of resolution here.

In either case, the bigger question is whether there is any valuable purpose in establishing an Extended OpenDocument Package and whether there should be even more things added to it beyond the simple business of not requiring statement of package MIME types (mimetype and manifest.xml being allowed to state different MIME types).

I raise this to NEEDS-DISCUSSION because it needs to be resolved in conjunction with OFFICE-2532.

> NEEDS-DISCUSSION: Package 7.2.2 Conforming OpenDocument Extended Package Not Useful
> -----------------------------------------------------------------------------------
>
>                 Key: OFFICE-2257
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-2257
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          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: Michael Brauer
>             Fix For: ODF 1.2 Part 3 CD 2
>
>
> 1. In Part 3 section 7.2.2, the only difference made between a Conforming OpenDocument Package and Conforming OpenDocument Extended Package is when the optional mimetype file and the optional <manifest:file-entry> element with manifest:full-path="/" are both present.  For a Conforming OpenDocument Package, the manifest:media-type attribute value must match the mimetype file content.  For a Conforming OpenDocument Extended Package, agreement is not required.
> 2. I fear that I may have had something to do with this being in here.  Either way, I find that this is insufficient cause to define two conformance targets hinged on such a minor difference.
> 3. The consequence of this two-level approach is a great deal of effort having to say when a provision (or related conformance target) applies to Conforming OpenDocument Documents and when Conforming OpenDocument Extended Documents are also included or excluded.  
> 4. Supplementai Issue OFFICE-2259 proposes one way a specialized conformance target requiring presence and agreement between the two MIME Type occurrences.

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