RE: xproc article on ibm

Yes - I guess I was thinking any kind of binary source. In a general
pipeline you pass in the object which I guess can be serialized to xml for
xproc (in many cases) or even serialized to binary and embedded in an input
xml document if each step understands how to decode the binary data.

 

I'm looking at the use cases in [1] just now.

 

Steven

http://livz.org

 

[1] http://www.w3.org/TR/xproc-requirements/

 

From: public-xml-processing-model-comments-request@w3.org
[mailto:public-xml-processing-model-comments-request@w3.org] On Behalf Of
mozer
Sent: 25 June 2008 10:45
To: James Fuller
Cc: Steven Livingstone-Perez; public-xml-processing-model-comments@w3.org
Subject: Re: xproc article on ibm

 

And also you can vectorize your image in SVG ...

Xmlizer




On Wed, Jun 25, 2008 at 7:01 AM, James Fuller <james.fuller.2007@gmail.com>
wrote:


On Wed, Jun 25, 2008 at 2:23 AM, Steven Livingstone-Perez

> I look forward to seeing more implementations also - I had been writing
something that was a more general case (Xml/Xslt being a specific case).

they are coming ...


> I'm still trying to figure out the pros and cons of passing, say a base64
encoded image (and I guess its associated metadata) through XProc as opposed
to just using binary as was my original intention.

--------------------------------------------

remember XProc (and all its steps) only accepts XML documents as its
input so trying to manipulate a base64 encoded image would have to be
performed in the context of this data set within an XML document
(perhaps containing the associated metadata you mention).

there are other standards for embedding metadata in an image....
something like Adobe XMP(1) and I could imagine that an XProc
implementation could implement an extension step to work with these
types of images.

cheers, Jim Fuller










1- http://www.adobe.com/products/xmp/