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=29246#action_29246 ] 

Dennis Hamilton commented on OFFICE-3740:

The manifest:version attribute was originally introduced as only on the <manifest:file> entry, and it is an optional attribute there.

The addition of it as a <manifest:manifest> with a mandatory value was a late addition.  In part 3, there is no provision for consumers not supporting a provisioni as there is in part 1, and that has been true since ODF 1.0.  The downlevel impact was over-looked.  It was also over-looked that there were already documents identified as ODF 1.2 documents that do not have the attribute.

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.  In addition, not producing it will reduce the likelihood of a strict down-level consumer derailing on an attribute it cannot assess the significance of.

With regard to the practical consequences of the ritualistic addition of this attribute to <manifest:manifest>: The Microsoft Office ODF 1.1 consumers will warn that the document is malformed (true for ODF 1.1) and while it will "repair and continue" it creates obstacles.

Furthermore, no stable release of OpenOffice.org (i.e., earleri than OO.o-dev 3.4.0) produces the attribute.   The same is true of Symphony 3 FP3 (I haven't looked at Symphony 3.01) and of the LibreOffice 3.3.x releases.  So none of these documents will pass validation with a final-schema  ODF 1.2 validator.

Like it or not, it causes far more pain to be puristic about this, with incredible support and finger-pointing problems, than anything that is lost by making the attribute optional and discouraging its production at this time. 

> 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, 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]