changelog

For the core c.os model we use the following versioning scheme: functions-major.functions-minor.core-practices (fmj.fmn.cp).. For example 1.0.04
The Core Practices revision number is reset when a new Functions revision is issued.
Each domain has its own version id using the following format: core-model-version.domain-name.domain-practices (dn.dp) where domain-name is fixed. For example 1.0.04.org.001. The core model revision is the one from which the domain-level is derived. The Domain Practices component is never reset.
Editorial revisions shall be denoted using an ‘e‘ component, which will be removed in the next non-editorial version. For example, an editorial change in a function’s overview can be marked as 1.2.09.e01. When one of the model’s components advances, the new revision will be for example 1.2.10.