- From: Wendell Piez <wapiez@mulberrytech.com>
- Date: Tue, 01 Jun 2010 15:56:21 -0400
- To: Romain Deltour <rdeltour@gmail.com>
- Cc: xproc-dev@w3.org
Romain, At 03:19 PM 6/1/2010, you wrote: >Interesting idea. But I am having trouble understanding how the >suggested simplified XML document would be different for an actual >XProc document ? The difference(s) would be only cosmetic, but cosmetic differences can mean a lot to users. >To my understanding XProc precisely allows to specify "which >transformations are run (from a library of choices), what are their >runtime parameters, etc"... Indeed: this is why XProc is among the possibilities I am considering. (Nor have I ruled out making them write XProc directly, as I'm doing in my proof of concept.) As for 'eval', the question would be whether one can run a transform to generate a pipeline which is then provided as input to 'eval'. That looks like a normal enough pipeline, so the answer would appear to be yes, which is good news for me. Cheers, Wendell ====================================================================== Wendell Piez mailto:wapiez@mulberrytech.com Mulberry Technologies, Inc. http://www.mulberrytech.com 17 West Jefferson Street Direct Phone: 301/315-9635 Suite 207 Phone: 301/315-9631 Rockville, MD 20850 Fax: 301/315-8285 ---------------------------------------------------------------------- Mulberry Technologies: A Consultancy Specializing in SGML and XML ======================================================================
Received on Tuesday, 1 June 2010 20:01:48 UTC