Date: 2021-03-19
A guide to migration from CASE 0.2.0 is here.
Note that this CASE release contains no CASE ontology changes that would affect instance data. The one breaking change would affect a querying practice. However, the UCO version being adopted in this release changed the names of many widely-used concepts, so for migration guidance, it is best to refer to UCO 0.5.0's listing of breaking changes.
CASE version 0.3.0 is focused on further development process refining, with initial revisions of modeling concepts in the Investigation namespace. This release of CASE incorporates significant developments done in collaboration with the Unified Cyber Ontology (UCO) 0.5.0 release.
(These are changes to ontologies, classes or properties in the preexisting ontology.)
Throughout this section, many of the notes are tied to Change Proposals. These proposals are available on CASE's Reference Material page.
(These are changes to ontology development practice, and are not necessarily changes to ontology data.)
(These are changes to ontologies, classes or properties in the preexisting ontology that make the new release non-backward-compatible.)
uco-role:Role are now direct subclasses of uco-role:Role, instead of subclasses of intermediary uco-role:Role subclasses. This could impact any users running queries for all subclasses of uco-role:BenevolentRole or uco-role:MaliciousRole.(These are general changes to the preexisting ontology that are not breaking or range changes.)