Purpose

Data storage is a diverse landscape of technologies. Triple stores, graph databases, persistent event streaming are but a few technologies that have become commonplace. We want Ampersand to link up with such technologies to serve a wider spectrum of problems.

Ampersand is prepared for this by the plug-mechanism.

Purpose

To take an API in production, it needs to be documented. For this purpose we want to generate Swagger files.

Purpose

One purpose of Ampersand is to generate a web-application. Currently, the generator and the generated application follow this architecture:

The architecture is explained in more detail in .

Summary

This chapter discusses future plans. Click on the hyperlinks for details

• In this video discusses the plans in 7min30 (in Dutch)

• To understand our plans, this section describes .

• Instead of storing data to an SQL database only, we want to other types of databases to work with Ampersand as well. Especially (e.g. triple stores, graph databases, persistent event streaming) seem very suited for Ampersand.

• To generate APIs is what Ampersand does already. We also want to to make it more useful in real life.

• To work closer in sync with the semantic web we want to accept . Currently Ampersand accepts Ampersand-syntax, Archimate-xml, and Excel as input.

• To generate reactive web-applications instead of a classical object-oriented web-application is why we want to .

Purpose

Ampersand and semantic web technologies have much in common. To explore this topic and to benefit from available ontologies expressed in RDF and OWL, we want to make an OWL/RDFS parser so we can interpret ontologies in Ampersand.

Purpose

The current front-end is based on the Angular-JS framework. To enter the world of reactive programming, we want to refactor the front-end.