- From: Alex Miłowski <alex@milowski.com>
- Date: Tue, 3 Jun 2014 13:29:24 -0700
- To: XProc WG <public-xml-processing-model-wg@w3.org>
Comments: 1. I'm not so sure about conflating operations with p:zip: * create/update make sense to do with the same step. * delete does not not make sense to me to have on zip (or possibly at all). * extracting a manifest seems like a p:unzip operation 2. I think p:unzip should work load p:load and shouldn't have an input. 3. I don't think we should necessarily use c:file or c:directory for entries. There are plenty of other bits of information related to zip file manifests that aren't attributes of files. 4. Entries in a zip file can occur in any order but directories generally precede files. Still, you can have entries like "content/", then "foo.xml", and then "content/bar.xml". 5. The minimal story feels like: * zip a set of files/directories * unzip to disk * zip/unzip from within the pipeline Next step up is: * update a zip I am less concerned about merging zip files or deleting content. -- --Alex Milowski "The excellence of grammar as a guide is proportional to the paucity of the inflexions, i.e. to the degree of analysis effected by the language considered." Bertrand Russell in a footnote of Principles of Mathematics
Received on Tuesday, 3 June 2014 20:29:52 UTC