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-3740) ODF 1.2 Requiring <manifest:manifest> manifest:version breaks downlevel and early 1.2 implementations

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

Dennis Hamilton commented on OFFICE-3740:

After the call, I dug further into my collection of document-forensics samples.

 1. With regard to ODF 1.2 producers that do not provide <manifest:manifest> manifest:version, but whose consumers evidently ignore the presence of such an attribute, that includes OpenOffice.org 3.3.0 and IBM Lotus Symphony 3.0.1.   These are the last stable releases of those products.  OpenOffice.org 3.3.0 was used to produce the ODF 1.2 Committee Specifications and the final OS authoritative documents.

 2. With regard to ODF 1.2 producers that do produce it but succesfully consume documents where it is absent, I can confirm that OpenOffice.org ooo-dev 3.4 (a "beta" that did not achieve stable release) produces <manifest:manifest> manifest:version="1.2" and consequently, so do all Apache OpenOffice releases so far.  I know LibreOffice 3.3.2 is in this category (3.6.2 is latest) and I suspect nearly all LibreOffice releases have been in this category.

NOTE 1: This is different than the occurence of <manifest:file-entry> manifest:version="1.2".  More products produce that *optional* attribute, especially on the file entry for content.xml, but apparently no one is bothered by its absence.

NOTE 2: With all of this fuss, there is still no explicit warning when a package is an extended package (trivia question: what makes an ODF 1.2 package extended?) or when a document is an extended document.

NOTE 3: I think it is important to keep in mind that <manifest:manifest> manifest:version is about the manifest (i.e., those things specific to packages), and should not be treated the same as office:version, which is about the document.  In that respect, <manifest:file-entry> manifest:version seems to be misnamed.  It also seems more appropriate to have it on the file-entry for "/" rather than content.xml.

> ODF 1.2 Requiring <manifest:manifest> manifest:version breaks downlevel and early 1.2 implementations
> --------------------------------------------------------------------------------------------------------------
>                 Key: OFFICE-3740
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-3740
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>    Affects Versions: ODF 1.2
>         Environment: This defect applies to ODF 1.2 Part 3 since Committee Specification 01.
>            Reporter: Dennis Hamilton
>            Assignee: Patrick Durusau
>             Fix For: ODF 1.2 Errata 01
> In ODF 1.2-3, the manifest:version="1.2" attribute is mandatory on <manifest:manifest> elements.  This attribute provision was introduced in ODF 1.2.  There were no manifest:version attributes for the <manifest:manifest> attribute in ODF 1.0 and ODF 1.1.
> The presence of this attribute prevents ODF 1.1 and earlier implementations that expect strict honoring of older <manifest:manifest> schemas from accepting ODF 1.2 documents for potential down-level acceptability.
> In addition, documents identified as ODF 1.2 documents produced before the provision was added to the ODF 1.2 specification will now be declared as non-conforming by document validators.
> The Catch 22 consists of the fact that expecting the attribute will invalidate previous documents that were identified as ODF 1.2 documents and that producing the attribute will cause error messages (at least) in down-level use of documents that may well have no specific dependency on material ODF 1.2 provisions whatsoever. 
> The provision is too brittle and causes more problems without solving very many.

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]