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-2259) Invert Special-Casefor Conformant OpenDocument Packages

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

Dennis Hamilton commented on OFFICE-2259:

It is awkward that this was simply retargeted to CD06, since CD05 is different than the version that this issue was against.

In CD05 Part 3, section 2.1, the only thing different about an OpenDocument Extended Package is that the use of META-INF/* is not restricted as it is for OpenDocument Package.  [I won't belabor why that is an inversion of inheritance as normally described.]

In CD05 Part 3, section 2.1, there is currently no mention of manifest:full-path="/" and the statement about mimetype is that it should be there, not that it shall be there.  There is nothing here about them having the same value or even both being present in Section 2.1.

In CD05 Part 3, section 3.2, however,  a manifest:full-path="/" should be provided and it shall be provided if there is a mimetype.

In CD05 Part 3, section 3.3, however, if a mimetype file is present, and there's a <manifest:file-entry> with manifest:full-path="/" then the value of the mimetype file data shall be the same as the manifest:media-type value.


If there are both mimetype and full-path="/" the two mimetype values must agree.

There may be a full-path="/" with no mimetype file

There shall be a full-path="/" if there is a mimetype file

There can be neither full-path="/" nor mimetype file.

So it seems that Michael's proposal is implemented except that a manifest:full-path="/" does not require presence of a manifest file.  There seems little cause to press on that for CD06.  Part 1 does what it does with this as a foundation.

> 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
>             Fix For: ODF 1.2 CD 06
> 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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]