While Elba is written to be database-aware and to guide the user through the workflow of creating a conceptual system on top of a relational database, Siena does similar things without the need of a database. This is achieved by a lot of shared code, so many forthcoming features will appear in both editors at once and will be perfectly synchronized.

Siena does not yet allow to edit the data directly, it is planned to add support for editing many-valued contexts in a spreadsheet like fashion, but we don't have any timeframe for this. At the moment the data is imported from two different formats: the plain text based Burmeister format (*.cxt) and the XML export of Cernato -- a commercial Formal Concept Analysis tool and probably the most sophisticated tool for memory-mapped data around.

Another feature set of Siena is about a technique called Temporal Concept Analysis, where states and their transitions are displayed in a concept lattice. These states and transitions can be calculated, displayed, animated and exported as sequences of images.

This already covers most Siena-specific features. It also inherits many of Elba's features by sharing code, in fact most of Elba's features that are not database-specific are available in Siena, too.