0.8.0 Release

Date: 2022-03-23

Ontology File(s)

GitHub

Release Notes

UCO 0.8.0 is primarily focused on an initial implementation of Shapes Constraint Language (SHACL) review of semi-open vocabulary usage, restructuring of all UCO ontology IRIs and file structures to enable delivery of ontology resources from a new subdomain, flattening actionActionReferencesFacet properties directly onto action:Action, normalizing decimal number properties to xsd:decimal, improvements to unit and CI testing, numerous modifications and improvements to the Observable namespace, and correcting several minor issues and bugs.

Breaking Changes

(These are changes to ontologies, classes or properties in the preexisting ontology that make the new release non-backward-compatible.)

• Remove observable:fileSystemType from FileFacet (Change Proposal 45)
• Restructured repository by moving previously prefixed uco-* ontology files under new directory /ontology/* (Change Proposal 56)
• Identifies software creators as uco-identity:Identity (Change Proposal 68)
• Normalized all decimal number properties in the ontology to xsd:decimal (Change Proposal 80)
• Make observable:AlternateDataStream into a Facet subclass (Change Proposal 87)
• Remove ActionReferenceFacet and move properties into action:Action (Change Proposal 89)
• Adds support for multiple participants in the PhoneCallFacet (Change Proposal 92)
• Implement semi-openess of vocabularies (Change Proposal 100)
  • This change implemented SHACL validation for all properties that had associated vocabulary assertions in Release 0.7.0. It did not add any new such vocabulary assertions to existing properties. For any properties without associated vocabulary assertions (e.g., core:kindOfRelationship), serialized values should be asserted simply as xsd:strings without any vocabulary-related datatype annotations. In JSON-LD that means to express a contained-within relationship, a plain "Contained_Within" string value should be used, instead of an datatype-annotating JSON dictionary {"@type": "vocabulary:ObservableObjectRelationshipVocab", "@value": "Contained_Within"}.
• Revise UCO IRI structure, similar to CASE CP-34, to utilize an “ontology” subdomain, end with a slash and remove @base (Change Proposal 107)
  • Users of UCO 0.7.0 and earlier should be aware that their UCO IRI prefixes should be adjusted. For instance, the prefix of the Action namespace https://unifiedcyberontology.org/ontology/uco/action# is now https://ontology.unifiedcyberontology.org/uco/action/.

Changes

(These are general changes to the preexisting ontology that are not breaking or range changes.)

• Add AndroidDeviceFacet, with device information as properties as a subclass of Device (Change Proposal 50)
• Updated CI testing (Makefiles) to reflect repository restructure (Change Proposal 56)
• Add vocabulary namespace to uco.ttl in uco-master (Change Proposal 82)
• Fix namespace prefix for WhoisContactTypeVocab from observable to vocabulary (Change Proposal 84)
• Remove sh:datatype property entries from observable.ttl added by SHACL data conversion errors (Change Proposal 85)
• Normalize unit tests for SHACL validation (Change Proposal 91)
• Remove duplicated and conflicting property description from uco-core:EnclosingCompilation (Change Proposal 95)
• Add missing fields for “lastTimeContacted” to the ontology (Change Proposal 97)
• Add missing “observable:to” field in EmailMessageFacet and MessageFacet (Change Proposal 102)
• Remove lower bounds in uco-observable:CallFacet to unrestrict cardinality (Change Proposal 103)
• Removes lower bounds in uco-observable:NoteFacet as described by UCO CP-103 (Change Proposal 105)
• Expand uco-observable:WirelessNetworkConnectionFacet properties support of network details (password, SecurityMode) (Change Proposal 106)
• Fix vocabulary namespace which incorrectly maps to ContactAddressScopeVocab (Change Proposal 109)

Documentation

Starting with UCO 0.8.0, generated documentation is available at this site:

https://ontology.unifiedcyberontology.org/

Be aware that the documentation will show the most recent release, until an ontology versioning strategy currently in initial implementation completes its testing. The upper-left corner of the documentation pages shows the ontology version being reviewed.