Re: [WIDGETS] Zip Support (request for comments)

Ok, here is some draft text if we were to go down the OCF route for
Zip. The only bit I would change is to relax and clarify the UTF-8
conformance requirement in OCF. I've also now allowed Zip64.

=Zip files=

For the purposes of this specification, A valid Zip file is a data
object that conforms to the production of a Zip Container as defined
in Section 4 of the [OCF] specification. In the event that a widget
user agents encounters Zip file that is in error, the widget user
agent must abort any processing of the Zip file and should inform the
end-user with an appropriate localized error dialog:

As with [OCF], Zip files must not be split into multiple files or span
multiple volumes. Zip files that are split into multiple files or span
multiple volumes are non-conforming. A widget user agent must treat
Zip files that have been split into multiple files or span multiple
volumes as being in error.

As with [OCF], Zip files must be created using the Deflate compression
algorithm as specified in the [Zip] specification. Zip files
compressed with any other compression algorithm are non-conforming. A
widget user agent must treat Zip files created using other compression
algorithms as being in error.

As with [OCF], A Zip file may be created using the ZIP64 extensions
defined in [Zip].

As with [OCF], A Zip file must not be created using either the
traditional PKWARE Encryption or Strong Encryption methods, or any
other future encryption method, defined in the Zip File Format
Specification. Widget user agents must treat encrypted Zip files as
being in error.

The names of files and directories within a Zip file should be encoded
in US-ASCII within the valid range of characters for file and
directory names (defined elsewhere).

As with [OCF], the names of files and directories within a Zip file
may be encoded in UTF-8 but only in conformance with Section 3.3 (File
Names) of the [OCF] specification. A widget user agent must treat Zip
files that don't conform to Section 3.3 of the [OCF] specification as
being in error.

Note: Please also refer to Appendix D - Language Encoding (EFS) in the
[Zip] specification for the technical details of how to indicate that
a Zip file contains UTF-8 names.

Issue: Using proprietary extensions to the [Zip] specification makes a
widget resource non-conforming.

Kind regards,

-- 
Marcos Caceres
http://datadriven.com.au

Received on Friday, 5 October 2007 07:05:20 UTC