| Jira Legacy |
|---|
| server | jira.edmcouncil.org |
|---|
| serverId | 6465cde0-d6c9-34a0-a506-4d4ac3461fe5 |
|---|
| key | IDMP-413 |
|---|
|
| Child pages (Children Display) |
|---|
...
For now, 'breaking changes' are defined as changes in documented foundational modelling patterns that require an update of SPARQL queries for competency questions.
| Level | Use | Comment |
|---|
| major | - From version 1, any breaking change leads to increment of the major version number
| - Until the end of 2023 the major version is 0 to indicate that breaking changes can still occur without incrementing the major
- At the end of 2023 it is planned to release IDMP-O version 1. After that breaking changes will lead to an increase of the major version
|
| minor | - Any extension of the ontology with new concepts, relationships or attributes leads to an increase of the minor version number.
| - The term "minor" is a standard term for this versioning approach. It can include significant backward-compatible extensions, e.g., hundreds of new concepts.
|
| fix | - Any issue correction of the ontology (e.g., fixing a typo in a definition or label) or addition of missing links
|
|