Versioning within a data model

For upcoming work we need the ability to define a subscope of a data model (example: A data model covers all aspects of a house, the subscope is the bathroom that is up for a makeover). I suggest this to be implemented as a new base class like “Cognite_versionable”. This needs to encompass both the values stored in the model, but also the structure of the model.

Again - the bathroom example:

Version 1: The same structure as the original bathroom just different specs (values) like for replacing stuff with better products.
Version 2: Replace the shower with a bathtub and add an extra sink

In V2 above this also means a different structure of elements linked to the bathroom.