[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Issue Comment Edited: (OFFICE-2306) PublicComment: Comments on ODF 1.2 CD Part 3: Packages
[ http://tools.oasis-open.org/issues/browse/OFFICE-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19005#action_19005 ]
Michael Brauer edited comment on OFFICE-2306 at 4/30/10 8:46 AM:
-----------------------------------------------------------------
Re 1.5: This type should be corrected. Correction appears in OpenDocument-v1.2-part3-cd01-rev03
Re 2.1-2.3: Covered by sub task OFFICE-2654.
Re 2.3 Mime Media Type:
The comment regarding the encoding is a duplicate to OFFICE-2192
A reference to RFC4288 may be helpful. Correction appears in OpenDocument-v1.2-part3-cd01-rev03
Since the specification does not state that trailing or leading spaces are allowed, they would be considered to be part of the media type. They are therefore not permitted.
Whether a producer encrypts the mimetype file is implementation specific. Given the purpose of the file, this obviously would not be reasonable, but their may be of cause circumstances, where a producer wishes also to encrypt the media type. It therefore does not appear to be reasonable to forbid that.
All other information that is asked for is contained in the conformance clauses.
Re 2.4 Encryption
Making clear that some or all file may be encrypted is reasonable. Correction appears in OpenDocument-v1.2-part3-cd01-rev03
Regarding the encryption of the mimetype file see 2.3
Regarding the summary of the encryption process: The summary describes a typical and simple scenario. It does not exclude more complex scenarios.
Allowing non-compressed encrypted files is a feature request. OFFICE-2655 has been created for this.
Digital signatures and encryption are independent features, that may be applied to stream independently. An encrypted stream may be included in a signature, and a signature may be encrypted. However, what is indeed missing is the information that an unencrypted signature shall not decrypt any references, while an encrypted signature as to decrypt all references. OFFICE-2565 was created for this.
Re 2.4.2:
The term "password" is used here because it a) easy to understand and b) the typical way how office documents are protected. It shall not mean that other kind of keys are excluded. We may replace "password" with "key", but that may make the descriptions more difficult to understand. I therefore suggest the stay with "password" for now.
Re 2.5: Digital Signatures
The ODF digital signature feature is based on the W3C DSig specification, and technically it is possible to sign only parts of a document. But in practice, this is an extremely difficult topic, because what parts of document must be visualized to the user in a way that the user clearly knows what is signed, and what isn't. Another questions are whether or not styles should be signed or not. Because of this complexity and the various use cases that exist and that all may have different requirements, the ODF specification does not define signatures for document part as a specific feature.
The ODF digital signature feature is based on the W3C DSig specification, which is a well defined standards for digital signatures. Using metadata instead does not appear to be reasonable.
Re 2.7: Usage of IRIs Within Packages
"Zip" should be used consistently. Correction appears in OpenDocument-v1.2-part3-cd01-rev03
Part 3 is about packages. Flat ODF files are not subject to part 3, but there are also no specific rules for relative IRIs in flat XML documents.
There are no constrains on character sets.
Relative references may start with ".." and therefore can also move up in the hierarchy. They may also leave a package.
Nothing is said about absolute IRI references, because they don't need any special processing.
Re 2.8: Preview Image
Adding a "typically" to a normative statement weakens the statement, and is therefore not reasonable.
A reference to the PNG specification appears in OpenDocument-v1.2-part3-cd012-rev02.
There are no further constrains regarding the PNG files. The comments contains several suggestions that may be considered in future ODF versions. OFFICE-2657 has been created for this.
was (Author: michael.brauer):
Re 1.5: This type should be corrected. Correction appears in OpenDocument-v1.2-part3-cd01-rev03
Re 2.1-2.3: Covered by sub task OFFICE-2654.
Re 2.3 Mime Media Type:
The comment regarding the encoding is a duplicate to OFFICE-2192
A reference to RFC4288 may be helpful. Correction appears in OpenDocument-v1.2-part3-cd01-rev03
Since the specification does not state that trailing or leading spaces are allowed, they would be considered to be part of the media type. They are therefore not permitted.
Whether a producer encrypts the mimetype file is implementation specific. Given the purpose of the file, this obvioisly would not be reasonable, but their may be of cause circumstances, where a producer wishes also to encrypt the media type. It therefore does not appear to be reasonable to forbid that.
All other information that is asked for is contained in the conformance clauses.
Re 2.4 Encryption
Making clear that some or all file may be encrypted is reasonable. Correction appears in OpenDocument-v1.2-part3-cd01-rev03
Regarding the encryption of the mimetype file see 2.3
Allowing non-compressed encrypted files is a feature request. OFFICE-2655 has been created for this.
Digital signatures and encryption are independent features, that may be applied to stream independently. An encrypted stream may be included in a signature, and a signature may be encrypted. However, what is indeed missing is the information that an unencrypted signature shall not decrypt any references, while an encrypted signature as to decrypt all references.
> Public Comment: Comments on ODF 1.2 CD Part 3: Packages
> -------------------------------------------------------
>
> Key: OFFICE-2306
> URL: http://tools.oasis-open.org/issues/browse/OFFICE-2306
> Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
> Issue Type: Bug
> Components: Packaging
> Affects Versions: ODF 1.2 Part 3 CD 1
> Reporter: Robert Weir
>
> Copied from office-comment list
> Original author: Michiel Leenaars <Michiel.ml@nlnet.nl>
> Original date: 13 Jan 2010 02:08:03 -0000
> Original URL: http://lists.oasis-open.org/archives/office-comment/201001/msg00006.html
--
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]