[OASIS Issue Tracker] Issue Comment Edited: (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=29259#action_29259 ] 

Dennis Hamilton edited comment on OFFICE-3740 at 1/23/12 11:44 AM:
-------------------------------------------------------------------

Changing the attribute to optional will not prevent you from continuing to produce it.  You just can't require it of an incoming package.

So if you consider the downlevel breakage tolerable, go ahead.  There is no issue with Gnumeric doing that.

This is not meant to be a precedent.  This is because there was inadequate attention to transition requirements and interoperability.  The presence of the attribute has nothing to do with what features are actually being used in the package and the documents in the package.

(There is a similar problem with office:version too, but that was staged from optional in ODF 1.0/1.1 to mandatory in ODF 1.2.  Even that is not a strong indicator of anything, but this was in ODF 1.2 very early.)

I don't see how OpenFormula questions help here.  OpenFormula is new in ODF 1.2 and there is no downlevel interoperability issue.  The OpenFormula namespace is distinct and its encounter by downlevel ODF 1.1 implementations does not involve any breaking changes relative to the ODF 1.0/1.1 specifications.

In any case, this is not about a precedent.  It is about a very specific interoperability situation with regard to a breaking change.  We need to stop with the hypothetical cases.  I don't know of any proposal to change the Error Values in OpenFormula.  Do you?

PS: Are you sure that OpenFormula says how error values are stored?  It says how they are named in formulas, but I'm not sure about how they are stored.  If the assumption is in the form specified by 5.12 under the provisions of 4.6, I assume any violations of those would be the subject of bug reports to the implementations.  I can see that these are rather underspecified for interoperability purposes.  There is no mandatory set of error values beyond what =NA() produces.

      was (Author: orcmid):
    Changing the attribute to optional will not prevent you from continuing to produce it.  You just can't require it of an incoming package.

So if you consider the downlevel breakage tolerable, go ahead.  There is no issue with Gnumeric doing that.

This is not meant to be a precedent.  This is because there was inadequate attention to transition requirements and interoperability.  The presence of the attribute has nothing to do with what features are actually being used in the package and the documents in the package.

(There is a similar problem with office:version too, but that was staged from optional in ODF 1.0/1.1 to mandatory in ODF 1.2.  Even that is not a strong indicator of anything, but this was in ODF 1.2 very early.)

I don't see how OpenFormula questions help here.  OpenFormula is new in ODF 1.2 and there is no downlevel interoperability issue.  The OpenFormula namespace is distinct and its encounter by downlevel ODF 1.1 implementations does not involve any breaking changes relative to the ODF 1.0/1.1 specifications.

In any case, this is not about a precedent.  It is about a very specific interoperability situation with regard to a breaking change.  We need to stop with the hypothetical cases.  I don't know of any proposal to change the Error Values in OpenFormula.  Do you?
  
> 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