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) 4.8.14.2 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=29257#action_29257 ] 

Dennis Hamilton commented on OFFICE-3740:
-----------------------------------------

Brought back from OFFICE-2244 (misplaced there):

Dennis says: 

The addition of manifest:version to the <manifest:manifest> tag wasn't put into a working draft until 2010-02-25. I'm not sure it was in Committee Draft that received Public Review until we sent out the full package for its first combined Public Review. I will have to check. 

With regard to penalization, I don't see the penalty. If you acept it optionally and you produce it, there is no harm except for downlevel consumers (like Excel 2007) that will warn about it. 
[ Show » ] Dennis Hamilton added a comment - 23/Jan/12 09:35 AM Andreas, The addition of manifest:version to the <manifest:manifest> tag wasn't put into a working draft until 2010-02-25. I'm not sure it was in Committee Draft that received Public Review until we sent out the full package for its first combined Public Review. I will have to check. With regard to penalization, I don't see the penalty. If you acept it optionally and you produce it, there is no harm except for downlevel consumers (like Excel 2007) that will warn about it. 


Andreas says:
From a user point of view, if Gnumeric, OOo, LO etc create valid ODF files but only files created by Gnumeric cause Excel to show this warning, the user will blame Gnumeric. That is penalizing Gnumeric.

Added:

We are talking about complaints from ODF 1.1 consumers.  But the practice so far is OOo-oriented folk claim that Office has a bug and it is just evidence for how poorly Microsoft does ODF.  There are no winners here.

Andreas, Gnumeric is permitted to continue to produce the attribute.  We can even say that it SHOULD be produced, but I think it should be optional for consumers and for documents.  

Ideally, the attribute should be produced only when the package uses a feature that will be processed incorrectly if the feature is ignored.  (Not the document - the package itself.)  That's probably not too demanding.  

Svante: Remember, the Package Specification is independent of the document specification and there is no required connection between the package manifest version level and the features used in the document, not just the package. 

> 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




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