A data transformation framework. A presentation inviting commentary.

[dieter]

"F.R." <anthra.norell at bluewin.ch> writes:

> ...
> In an effort to do some serious cleaning up of a hopelessly cluttered
> working environment, I developed a modular data transformation system
> that pretty much stands. I am very pleased with it. I expect huge time
> savings. I would share it, if had a sense that there is an interest
> out there and would appreciate comments. Here's a description. I named
> the module TX:
>
> The nucleus of the TX system is a Transformer class, a wrapper for any
> kind of transformation functionality. The Transformer takes input as
> calling argument and returns it transformed. This design allows the
> assembly of transformation chains, either nesting calls or better,
> using the class Chain, derived from 'Transformer' and 'list'. A Chain
> consists of a sequence of Transformers and is functionally equivalent
> to an individual Transformer. A high degree of modularity results:
> ...

This high level description much resembles "Products.PortalTransforms",
a transformation package used in a "Plone" context.
This package is targeted towards "MIME type" based transformations,
i.e. input objects have a "MIME type" and you specify the target
"MIME type". A transform registry knows about the available
(elementary) transformations and determines a chain of transformations
to achieve a desired one.