[OASIS Issue Tracker] Commented: (OFFICE-3740) 4.8.14.2 ODF 1.2 Requiring <manifest:manifest> manifest:version breaks downlevel and early 1.2 implementations

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

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

Andreas Guelzow  commented on OFFICE-3740:
------------------------------------------

ODF 1.2 always required that attribute. So saying "So an ODF 1.2 consumer is likely to ignore this attribute so that it won't reject documents from earlier versions of itself and of related implementations." doesn't really make sense. The real problem is that the OpenOffice/LibreOffice implementations prematurely started to create so called ODF 1.2 files.  So this looks to me like changing ODF 1.2 in a significant way to fix a bug in that code base.

Suddenly making this attribute optional and discouraging its production penalizes those implementations that have in accordance with the ODF 1.2 specification have in fact added this attribute since they are suddenly singled out by having only their files flagged as needing "repair". 

> 4.8.14.2 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
>             Fix For: ODF 1.2 Errata 01
>
>
> In ODF 1.2-3 4.8.14.2, 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