Why is a new version assigned during a smap update?

When updating, respectively distributing an update, the corresponding smap always receives a new version number. The reason for this is that the data table in the data input can change when a module is changed in the smap, so that the columns can no longer be displayed one below the other. Thus, one always receives a view of the data sets to a certain version. 

A further reason is that one can return to a certain version or create a copy of a certain smap version at a later stage, if unwanted changes within the smap were made earlier. In this way, it is possible to see exactly which status a smap had at a particular version number.