A guide to migration from CASE 0.1.0 is here.
CASE version 0.2.0 is focused on moving past the CASE prototype implementation that backed initial research, implementations, and example data. CASE has established its ontological distinction in its relationship with the Unified Cyber Ontology (UCO).
Work leading to version 0.2.0 was on establishing committee governance and development workflows, updating example data, and resolving fundamental conceptual relationship matters. The CASE ontology files have reduced in size significantly from the prototype implementation. The prototype had copied many concepts from UCO. CASE now imports UCO to provide the same access to those concepts without redundant and potentially confusing implementation.
(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.)
ChangeLogfile of the "develop" branch:
(These are changes to ontologies, classes or properties in the preexisting ontology that make the new release non-backward-compatible.)
https://caseontology.org/ontology/case/investigation. Enumerations supporting this sub-ontology are in the vocabulary sub-ontology, with the IRI
https://caseontology.org/ontology/case/vocabulary. These files were imported without revision, aside from minimal IRI string substitution, from UCO 0.4.0.
PropertyBundleand the property
propertyBundle, are no longer in use. These concepts were synonymic with concepts in UCO, and several attempts to implement "
CyberItem," etc., proved to result in significant adoption complications. In their stead, the concepts
uco-core:facetsshould be used.
case.ttlfile has been removed, as has the initial documentation generation mechanism. A different mechanism for generating documentation is being planned for posting to the CASE website.