add "backwardsCompatibility" and "identical" to types

[olinux]

add structures to reflect

"backwardsCompatibility": {
"v1.0": [],
"v2.0": ["v1.0"],
"v3.0": ["v1.0", "v2.0"]
},
"identical": [["v1.0", "v2.0"], ["v3.0"]],

[lzehl]

@olinux @annapaola could you please clarify the interpretation/format for both?
(what is now backwards compatible with what and what is identical to what?)

[olinux]

@lzehl : This issue has been created a long time ago, but to the best of my knowledge, we said that we wanted to specify if a type has changed between the versions and/or if it was remaining backwards compatible.
In the example, you would see a type which is identical in v1.0 and v2.0 but has a change in v3.0 - however, the version in v3.0 is still backwards compatible to v1.0 and v2.0

[lzehl]

@Raphael-Gazzotti I think we could track this automatically and extent the pipeline (vocab builder) with this suggestion.

[Raphael-Gazzotti]

In PR #36, the "identical" property was introduced to the vocabulary of types. However, I'm unsure about the next steps regarding the "backwardsCompatibility" property.

[lzehl]

@Raphael-Gazzotti what is unclear about the "backwardsCompatibility" property?

[Raphael-Gazzotti]

Automatically detecting backwards compatibility breaks isn’t straightforward.

• Fixing a typo is safe. But if we tweak a description’s meaning, that’s a breaking change. How do we programmatically tell the difference? (use of NLP?)
• We can catch added/removed properties or changes in data types, but how to deal with subtler changes.

Where’s the line between a harmless tweak and a breaking change?

[lzehl]

backwards compatible:

• typos in string values (e.g. for properties: instructions / descriptions / names)
• additional properties
• additional linked/embedded types
• getting rid of requirements

not backwards compatible:

• attype changes
• atid changes (instance issue)
• namespace change
• typos/changes in property names
• expected value type changes (single value to array)
• introducing requirements

@openMetadataInitiative/openminds-developers please think about this a bit more.