[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [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
[ http://tools.oasis-open.org/issues/browse/OFFICE-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=29280#action_29280 ]
Svante Schubert edited comment on OFFICE-3740 at 1/25/12 10:59 AM:
--------------------------------------------------------------------
I agree with Andreas, that we should not alter the spec to reach a larger amount of valid documents, when early implementation just made mistakes.
The specification should be a guidance and not be altered by random user errors. Especially as this version attribute does make sense. It is necessary to know the version to know about the potential feature set of the ODF package.
Therefore I suggest to drop this issue for ODF 1.2 and switch this issue to an ODF 1.0/1.1 issue due to the following:
"1.5 Document Processing and Conformance
Documents that conform to the OpenDocument specification may contain elements and attributes not specified within the OpenDocument schema. Such elements and attributes must not be part of a namespace that is defined within this specification and are called foreign elements and attributes."
See http://docs.oasis-open.org/office/v1.1/OS/OpenDocument-v1.1-html/OpenDocument-v1.1.html#outline%3A1.5.Document_Processing_and_Conformance (or ODF 1.0 PDF see http://docs.oasis-open.org/office/v1.0/OpenDocument-v1.0-os.pdf )
ODF 1.0/1..1 does not allow new attributes & elements with the same namespace. But we extended the schema reusing namespaces for ODF 1.2.
Perhaps there was earlier idea to switch the namespace for the next ODF version, but it was found out, that would be a compatibility nightmare as a new namespace URL is like completely new XML.
Another evidence is that the XML namespace embraces as well 1.0 version number, e.g. urn:oasis:names:tc:opendocument:xmlns:animation:1.0
Nowadays we know that URL are better than URI, but we can not improve decision of the past easily.
As fix I suggest an additional sentence as
"Future versions of OpenDocument schema might use element and attributes part of a namespace defined within this specification."
PS: I did not find easily the latest ODF 1.1 errata document, to double check, if a similar fix might be already in there. Anyone got a reference?
was (Author: svante.schubert):
I agree with Andreas, that we should not alter the spec to reach a larger amount of valid documents, when early implementation just made mistakes.
The specification should be a guidance and not be altered by random user errors. Especially as this version attribute does make sense. It is necessary to know the version to know about the potential feature set of the ODF package.
Therefore I suggest to drop this issue for ODF 1.2 and switch this issue to an ODF 1.0/1.1 issue due to the following:
"1.5 Document Processing and Conformance
Documents that conform to the OpenDocument specification may contain elements and attributes not specified within the OpenDocument schema. Such elements and attributes must not be part of a namespace that is defined within this specification and are called foreign elements and attributes."
See http://docs.oasis-open.org/office/v1.1/OS/OpenDocument-v1.1-html/OpenDocument-v1.1.html#outline%3A1.5.Document_Processing_and_Conformance (or ODF 1.0 PDF)
or http://docs.oasis-open.org/office/v1.0/OpenDocument-v1.0-os.pdf
ODF 1.0/1..1 does not allow new attributes & elements with the same namespace. But we extended the schema reusing namespaces for ODF 1.2.
Perhaps there was earlier idea to switch the namespace for the next ODF version, but it was found out, that would be a compatibility nightmare as a new namespace URL is like completely new XML.
Another evidence is that the XML namespace embraces as well 1.0 version number, e.g. urn:oasis:names:tc:opendocument:xmlns:animation:1.0
Nowadays we know that URL are better than URI, but we can not improve decision of the past easily.
As fix I suggest an additional sentence as
"Future versions of OpenDocument schema might use element and attributes part of a namespace defined within this specification."
PS: I did not find easily the latest ODF 1.1 errata document, to double check, if a similar fix might be already in there. Anyone got a reference?
> 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]