[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=31545#action_31545 ]
Svante Schubert commented on OFFICE-3740:
------------------------------------------
We should resolve issue. My opinion was stated earlier -
https://tools.oasis-open.org/issues/browse/OFFICE-3740?focusedCommentId=29280&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_29280
Let us find our common ground:
1) We need to allow new ODF elements in future documents to be able to extend the standard.
2) Elder spec say that no ODF namespace should be used by 3rd party applications
3) Fact is that the elder spec was misinterpreted by former ODF applications that all new ODF XML is being treated as invalid documents, although unknown XML should be simply ignored.
The solution for new applications can not be to neglect the new ODF XML so older applications refer to those documents as valid.
Instead we should change our wording in ODF 1.1 errata that there are new ODF XML nodes planned for the future, but those namespaces are restricted to the use of the TC.
> 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
> Assignee: Patrick Durusau
> 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]