XSD is a W3C XML Schema to C++ translator. Provided with an XML instance specification (XML Schema), it generates C++ classes that represent the given vocabulary as well as parsing and serialization code. You can then access the data stored in XML using types and functions that semantically correspond to your application domain rather than dealing with elements, attributes, and text in a direct representation of XML such as DOM or SAX. XSD features support for in-memory and stream-oriented processing models, comprehensive XML Schema feature coverage, easy integration, and more.
XSH (the XML Editing Shell) is a very powerful command-line shell designed to allow easy navigation and manipulation of XML documents. XSH may be used either interactively or for off-line XML processing (like bash). XPath can be used to select parts of an XML document to be listed or processed. The system shell and Perl are also accessible from XSH in a very natural way. XSH itself is written in Perl using the XML::LibXML bindings of the libxml2 library.
The XEVM is an XML processing engine. It's a multi-threaded, Pub/Sub environment for dynamic programming on an event-driven state machine with TCP communications, tight fault free memory management, powerful set algebra, and a magical database. It is 100% C++ (25,000 LOC), with a thin porting layer; there are implementations for POSIX (Mac/Linux) and Win32. The XEVM is for processing XEPL (the Xepl Engine Programming Language).
Zimplit CMS is a Web-based content management system which enables users to create professional Web sites without being a Web developer or hiring one. Editing a Web site is extremely easy thanks to an "On-site" editor. The editor is on the Web site like an ordinary visitor, except that on every editable page, a small toolbar makes it possible to create pages, change texts, and add pictures, galleries, and videos. Users can use any CSS/HTML template they wish.
Bibgrep indexes and efficiently searches BibTex files. Its usage is similar to the command grep and the queries use a Google-like syntax. Bibgrep will create an index for each BibTex file it touches, and keep the result within "~/.bibgrep.idx" (by defaults). It watches the modification date and the size of the original BibTex file, and will update (and delete) its index as needed.