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=17788#action_17788 ] 

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

Dennis, I'm trying to understand what the purpose of the conformance clause you are proposing is.

You are right that mimetype file and the <mainfest:file-entry> with manifest:full-path="/"  are optional (while recommended) for conforming OpenDocument packages, but they are mandatory for the individual OpenDocument document types we specify in part 1. For instance

For instance, (D3.2) of part 1 states:

If the document is an OpenDocument package then it shall contain a file named mimetype containing one of these strings: "application/vnd.oasis.opendocument.text", "application/vnd.oasis.opendocument.text-template" or "application/vnd.oasis.opendocument.text-master".

So, what is the benefit of having this additional conformance class?

> 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

        


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