So in 1997 we at Fouthought decided to put together a knowledge
management suite that could manage documents put into the then brand new
XML format. We were a Python shop but couldn't find good enough Python
tools for XML processing in a distributed environment, and we pounced on
the weak ties between DOM and CORBA. We decided to make the core XML
toolkit open source a few months later and 4DOM was born. The
transformability of XML was always what attracted me to the technology,
and so once XSLT came out we quickly put together an implementation and
open-sourced that, too. 4Suite was born. 4Suite had an interesting
life, with 4DOM and then the original Python-based XPath and XSLT
spinning off into PyXML, replaced in 4Suite by code with a heavy C
component.
For a while 4Suite has been good enough for a lot of work, and I've been
through some work transition, which has included the sidelining of
Fourthought. We've prototyped work to help with performance, and I
developed Amara XML Toolkit because the 4Suite interfaces were too
XML-oriented, and not Pythonic enough. Amara has been a resounding
success, and I've realized it should be a leading, not a trailing part
of the 4Suite project family. Happily, we've had some impetus to take
the project to the next level. I won't repeat all the details I posted
here:
http://lists.fourthought.com/pipermail/4suite-dev/2008-March/002264.html
But in short 4Suite 1.x and Amara 1.x plus the planned improvements will
now become Amara 2.x. I'm hoping you will be able to help. The roadmap
is here:
An architectural overview here:
http://wiki.xml3k.org/Amara2/Architecture
We will be using Mercurial for VCS. I have checked in a skeleton of
work here
Preliminary, real code should follow shortly :-)
--
Uche Ogbuji http://uche.ogbuji.net
Founding Partner, Zepheira http://zepheira.com
Linked-in profile: http://www.linkedin.com/in/ucheogbuji
Articles: http://uche.ogbuji.net/tech/publications/