Date: 2026-07-24
UCO 1.5.0 incorporates required refinements and updates, building on the stable 1.0.0 release. Following SemVer, additive improvements will continue to be accepted, but backwards-incompatible changes will be scheduled only for the 2.0.0 release, which will come after at least 6 months to possibly 12 months.
This release introduces a mechanism for framework developers to manage a catalogue of enumerated classes of actions. The UCO Action namespace now defines UCO’s first meta-class, Technique, whose instances are themselves specialized subclasses of Action. This adds a third tier above the usual two-tier class structure: the Technique meta-class, the Technique classes that instantiate it, and the Actions that instantiate those. This design allows a specific Action to follow a general Technique explicitly by being typed with that Technique class, and enables SHACL validation of requirements specific to that Technique. For instance, a disk imaging Technique can require a device of a certain class, such as a hardware write blocker. Then an Action can follow this Technique using a specific disk imaging tool with a given hardware write blocker. A Technique class can refine one or more parent Techniques bringing the benefits of inheretance and multi-classing. The design supports controlled collection of Action-subclasses within a framework, and also supports extension of one framework’s Techniques by another, while keeping clear the framework within which any Technique—extension or not—is defined.
(These are changes to ontologies, classes or properties in the preexisting ontology that make the new release non-backward-compatible.)
(These are changes to ontologies, classes or properties in the preexisting ontology.)
core:UcoType and core:Technique (GitHub Issue 666)(These are bugs found within the preexisting ontology that have been fixed.)
rdfs:label for observable:MessageThread (GitHub Issue 667)rdfs:comment for types:Thread (GitHub Issue 669)rdfs:comment for observable:bluetoothDeviceName (GitHub Issue 670)Generated documentation is available at this site:
https://ontology.unifiedcyberontology.org/
Be aware that the documentation at that site will only show the most recent release. The upper-left corner of the documentation pages shows the ontology version being reviewed.
After the following UCO release, users interested seeing the rendered documentation at this version “Back in time” should locally clone the repository, check out this branch, and follow the deployment directions in CONTRIBUTE.md.