- From: <vojtech.toman@emc.com>
- Date: Tue, 24 Apr 2012 04:22:12 -0400
- To: <public-xml-processing-model-wg@w3.org>
What I meant was just the ability to use pxp:zip to put non-XML data in a ZIP file. My idea was that it would be nice if you could tell pxp:zip to unwrap (+ base64-decode if needed) c:data documents before compressing. Vojtech -- Vojtech Toman Consultant Software Engineer EMC | Information Intelligence Group vojtech.toman@emc.com http://developer.emc.com/xmltech > -----Original Message----- > From: Alex Milowski [mailto:alex@milowski.com] > Sent: Tuesday, April 24, 2012 3:31 AM > To: public-xml-processing-model-wg@w3.org > Subject: Re: Some notes about pxp:zip and pxp:unzip > > On Fri, Apr 20, 2012 at 3:21 AM, <vojtech.toman@emc.com> wrote: > > One more thing that I forgot about pxp:zip: it would be nice if it > were possible to compress non-XML data as well (in a similar way that > p:http-request allows sending non-XML request bodies). Otherwise things > such as creating an EPUB with images would still be impossible with > standard XProc. > > > > Compression is always good but I don't understand the epub w/ images > reference. Images rarely compress well with LZW. > > So, what does that mean for the p:data element? The base64 encoded > data is the compressed non-XML data? We'd need one more bit of data > on p:data (the compression algorithm). > > -- > --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, 24 April 2012 08:23:09 UTC