OpenLink Virtuoso is a scalable, high-performance SQL-200n compliant object-relational database engine. It provide sophisticated database management for SQL, XML, and RDF. All interaction with Virtuoso occurs via its support of industry standard query languages, protocols, APIs, and data formats such as: ODBC, JDBC, OLE-DB, ADO.NET, XMLA, SQL, SPARQL, XQuery, SOAP, HTTP, WebDAV, SyncML, Atom (Publishing and Syndication), RSS, RDF, and more.
Redland is a set of C libraries providing a high-level API for the Resource Description Framework (RDF), allowing it to be stored, parsed, serialized, queried, and manipulated. It has an object-based, modular design and comes with detailed reference documentation and examples. Redland supports all RDF vocabularies such as FOAF, RSS 1.0, Dublin Core, DOAP, and OWL, the query languages SPARQL and RDQL, and all RDF syntaxes including Turtle, RDF/XML, RDF/JSON, RSS, Atom, RDFa, and GRDDL.
Originally named Sync4j, the Funambol Mobile Application server includes a suite of tools to develop, deploy, and manage mobile projects. It includes push email functionality and is a certified implementation of SyncML (OMA DS/DM standard). It includes a mobile application server with connectors to SQL relational databases, Microsoft Exchange, Lotus Domino, and SugarCRM, applications for Outlook, Windows Mobile PocketPC, BlackBerry, Palm, and iPod for synchronizing address books and calendars, and a gateway for supporting mobile email. An SDK and an OMA DM server for remotely managing mobile devices are also included.
The unixODBC project provides Unix applications with the same ODBC 3.51 API and facilities available under Windows. It provides a Driver Manager that supports the full ODBC API and performs the ODBC 3 to ODBC 2 translations with UNICODE to ANSI conversion. It also includes a set of graphical utilities that allow users to specify connections to DBMSes to be used by applications, a collection of ODBC drivers including a simple text based driver, an NNTP driver, a Postgres driver and others, and a selection of templates and libraries that to aid in the construction of ODBC drivers. It works with MySQL, Postgres, StarOffice/OpenOffice, Applixware, iHTML, PHP, Perl DBD::ODBC, and many other applications and drivers. Connection pooling is also provided to increase performance with applications such as PHP.
CLIP is a Clipper/XBase compatible compiler with initial support other xBase dialects. It features support for international languages and character sets. It also features OOP, a multiplatform GUI based on GTK/GTKextra, all SIX/Comix features (including hypertext indexing), SQL and ODBC drivers, a C-API for third-party developers, a few wrappers for popular libraries (such as BZIP, GZIP, GD, Crypto, and Fcgi), a multitasking client and application server based on TCP/IP sockets, object data base utilities, and a functions library.
PostGIS adds support for geographic objects to the PostgreSQL object-relational database. In effect, PostGIS "spatially enables" the PostgreSQL server, allowing it to be used as a backend spatial database for geographic information systems (GIS), much like ESRI's SDE or Oracle's Spatial extension.
My Handy Restaurant is software created to help restaurant waiters and managers in their job. Waiters can choose a restaurant table, assign orders to it and have them automatically printed on printers. "Normal" dishes can also be modified, by adding or removing ingredients. Bills can be printed automatically, even for separated bills. The accounting section allows a restaurant manager to easily administrate the whole accounting (bank accounts, employees, suppliers, income) in an easy way. Stock management is also available, and items quantity is automatically updated. The interface is handheld-sized and is written to be compatible with most handheld browsers.
Tokyo Cabinet is a library of routines for managing a database. It is the successor of QDBM. Tokyo Cabinet runs very fast. For example, the time required to store 1 million records is 1.5 seconds for a hash database and 2.2 seconds for a B+ tree database. Moreover, the database size is very small. For example, the overhead for a record is 16 bytes for a hash database, and 5 bytes for a B+ tree database. Furthermore, the scalability of Tokyo Cabinet is great. The database size can be up to 8EB.