- From: Norman Walsh <ndw@nwalsh.com>
- Date: Thu, 13 Nov 2008 12:54:21 -0500
- To: public-xml-processing-model-comments@w3.org
- Message-ID: <m21vxf5x6a.fsf_-_@nwalsh.com>
Norman Walsh <ndw@nwalsh.com> writes: > Toman_Vojtech@emc.com writes: >> I know that XProc really is not aimed for handling binary data, but >> since we already have steps such as p:xsl-formatter that store binary >> content, and p:data/p:http-request for loading binary data into XProc, >> perhaps a binary equivalent of p:store (which would take a c:data >> wrapped content and store it as binary data) could be useful. But maybe >> not for V1. > > It's an interesting point. XProc grew a fair bit of additional > "binary" support late in the day with p:data and the various > content-type options. > > Given that you can load a PNG, it seems odd that you can't store it. > > I suppose the simplest way to fix this problem would be to take > advantage of the media-type serialization option. It would (I think) > be conformant for an implementation to accept: > > <p:store content-type="image/png" href="my.png"> > <p:input port="source"> > <p:inline> > <c:data content-type="image/png">BASE64ENCODEDDATA</c:data> > </p:inline> > </p:input> > </p:store> > > and write the decoded PNG data to my.png. > > Does anyone think that's not conformant? The WG considered this problem and concluded that a note along the lines outlined above was sufficient for V1.0. Be seeing you, norm -- Norman Walsh <ndw@nwalsh.com> | Every vice you destroy has a http://nwalsh.com/ | corresponding virtue, which perishes | along with it.--Anatole France
Received on Thursday, 13 November 2008 17:55:08 UTC