ZIP package format is not a unique compression system or even an ISO standard. Multiple ZIP implementations have different compression and tagging techniques. This will cause wrong operation of inverse algorithms for decompression and probable data loss. Moreover, not all ZIP compressors - decompressors are open or freely available for all computer platforms. Additionally, a password protected document implies the use of proprietary binary interpreters (such as OLE). Encrypted ZIP files are not well supported.
Declare more specific characteristics for ZIP methods and usages, including precise compression algorithms.
Packaging Conventions Part 2
ge
Proposed Disposition of DIS 29500 Comment MX-0001 (Modified: 2008-01-04) The commonly used ZIP file format specification is published by PKWARE, Inc., and is described in the resolution of CA-0004, CH-0005, CL-0038, CZ-0005, DE-0011, DK-0003, FR-0021, GB-0049, GB-0463, IN-0051, KE-0002, PT-0007, US-0039 and ZA-0005. DIS29500 uses version 6.2.0 (2004), as specified in http://www.pkware.com/documents/APPNOTE/APPNOTE_6.2.0.txt. The specific compression methods supported by DIS29500 are covered in Table C4, “Support for Compression Method field”, in Part 2, Annex C (ZIP Appnote.txt Clarifications). This commonly used ZIP file format is used by other ISO standards such as ISO/IEC IS 26300 (ODF 1.0).
It appears that this comment was chopped off in the middle. The source should be reviewed so the rest of the comment can be added.
This is an interesting objection. It appears it would apply equally to ODF, as that format uses a JAR container format, which is simply a .zip file with a Manifest included. Doesn’t ODF define the .zip format, or cite another source which does?
looks like it got stuck on an em dash which wasn’t correctly encoded. I will try and sort out any other places this happened.
turns out there are 38 posts that had the same problem. I will update them later.