Include Semantic Versioning

Description

Since we already have a rather binding relation with the spatial-model-editor as an upstream project, it does make sense that we start to take care about the software version. This can make life easier to downstream developers by using semantic versioning and thus avoiding the "dependency hell".

Proposal

Start to use Semantic Versioning from version 0.0.0 in the current state of the repository and increment it according to this simple rule:

Given a version number MAJOR.MINOR.PATCH, increment the:

• MAJOR version when you make incompatible API changes,
• MINOR version when you add functionality in a backwards compatible manner, and
• PATCH version when you make backwards compatible bug fixes.

How to test the implementation?

• No immediate way.
• A non so immediate way is by counting the number of reactions to this issue in the future 😉