<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#ffffff" text="#000000">
I have taken as my task to list the root problems associated with
the use of the ZIP format in document format standards.<br>
This task does not involve the suggestion or prescription of any
particular solution, and includes the understanding that WG1, SC34,
or even ISO may not be the suitable forum to resolve these issues.
<br>
<br>
The following is what I have put up on the WG1 wiki, we can develop
it further there. Please limit edits to focus on identifying the
problem and not to define solutions. (for this section of the wiki,
of course)<br>
<hr size="2" width="100%"><br>
ZIP archive compression is a long-standing, widely-adopted
technology described by PKWARE in their ZIP Application Note. This
technology is used for many purposes in the industry, from the
archiving and compression of files to packaging of applications
(Java jar/ear/war). <br>
<br>
Additionally, in recent years there have been a number of document
format standards that use ZIP as a "container file" for storing XML
and related resources. For example, OASIS ODF (ISO/IEC 26300), Ecma
OOXML (ISO/IEC 29500), IDPF EPUB and W3C Widgets. <br>
<br>
This use of the ZIP Application Note, as an external normative
reference, by International Standards or specifications which may be
on the track to become International Standards, presents the
following problems:<br>
<ul>
<li>There is no Standards Compatible Reference associated with the
.ZIP Application Note.</li>
<li>There is an ambiguous IPR landscape, especially related to the
IPR referenced in the .ZIP Application Note.<br>
</li>
<li>There are technical issues related to the use of ZIP as a
document package which are not covered by the .ZIP Application
Note</li>
<li>ZIP is a ubiquitous and highly interoperable technology, and
any standards activity relating to ZIP should not negatively
impact the current use of ZIP or its current use in standards.<br>
</li>
</ul>
<br>
<br>
As back up to the main problems identified above, here are a set of
more specific issues that fall under these categories:<br>
<ul>
<li>No Standards Compatible Reference </li>
<ul>
<li>Current Application Note is not referenceable by
International Standards</li>
<li>There is no mechanism to reference parts of the Application
Note</li>
<li>There is ambiguity in terms of the future maintenance of the
Application Note (e.g. feedback procedures and transparency)<br>
</li>
</ul>
<li>Ambiguous IPR Landscape</li>
<ul>
<li>It is not possible to identify which parts of the
Application Note are subject to IP and which are not</li>
<li>The use of ZIP in Open Standards (which are implementable in
all Open Source) requires any IP used in the standards to be
licensed under RF terms. <br>
</li>
</ul>
<li>Technical Issues related to the use of ZIP as a Document
Package</li>
<ul>
<li>Minimum feature set relevant to all document packaging use
of ZIP</li>
<li>additional syntax</li>
<li>additional objects and metadata</li>
<li>signatures and encryption</li>
<li>ZIP URL protocol & fragment identifiers<br>
</li>
</ul>
<li>Do No Harm to the Current Usage of ZIP</li>
<ul>
<li>Ubiquitous nature of ZIP creates wide reaching benefits
(utilities built into all development platforms and OSes)<br>
</li>
<li>Currently in use by wide range of standards<br>
</li>
<ul>
<li>ODF, OOXML, EPUB</li>
<li>W3C widgets</li>
<li>Java (jar, war, ear, java.util.zip)</li>
<li>XPI <br>
</li>
<li>ADL-SCORM</li>
</ul>
</ul>
</ul>
<br>
<hr size="2" width="100%"><br>
<br>
<br>
<br>
<br>
<div class="moz-signature">-- <br>
<br>
<br>
<img src="cid:part1.00000406.04060707@oracle.com" alt="Oracle
Email Signature Logo" height="26" width="114"><br>
<font size="2" color="#666666" face="Verdana, Arial, Helvetica,
sans-serif"> Andrew Rist | Interoperability Architect<br>
<font color="#ff0000">Oracle</font> Corporate Architecture Group<br>
Redwood Shores, CA | 650.506.9847
</font>
</div>
</body>
</html>