2024-02-15 CDO Ontology Committees

10m

Constraining ObservableRelationship

@Alexander Nelson

• [VOTE] Requirements Review
  `observable:ObservableRelationship` should constrain the types on the objects it is relating · Issue #573 · ucoProject/UCO
  https://unifiedcyberontology.atlassian.net/browse/OC-302

10m

Disjointedness enforcements

@Alexander Nelson

• [VOTE] Requirements Review
  Disjointedness already denoted in UCO should be enforced · Issue #586 · ucoProject/UCO
  https://unifiedcyberontology.atlassian.net/browse/OC-305

15m

Investigative Actions requiring Provenance Record result

@Alexander Nelson

• [VOTE] Requirements Review
  `InvestigativeAction`s should be required to produce at least one `ProvenanceRecord` · Issue #146 · casework/CASE
  https://cyberontology.atlassian.net/browse/ONT-493

15m

Review of OWL cardinalities

@Alexander Nelson

• [VOTE] Requirements Review
  UCO's OWL syntax review should test cardinality restrictions · Issue #591 · ucoProject/UCO
  https://unifiedcyberontology.atlassian.net/browse/OC-306

5m

Alternate Data Stream

@Alexander Nelson

• [Discussion] Next steps
  `observable:AlternateDataStream` is not a subclass of `FileSystemObject`, but `File` and `ReparsePoint` are · Issue #590 · ucoProject/UCO

  • Two-step fix - change superclass for UCO 2.0.0 as step 2; warn if ADS object not also multi-typed as FileSystemObject for UCO 1.4.0?

20m

Software contexts

@Sean Barnum

• [NOT voting] Requirements discussion
  Need improved and extended abilities to express contextual details around software such as its build, configuration, and deployment · Issue #583 · ucoProject/UCO

  • We are only not voting because of proposal size.

  • Let us consider the digestible next-steps on this proposal.
    
    

5m

Semi-open vocabulary syntax

@Alexander Nelson

• [Discussion]
  UCO semi-open vocabularies seem to use `owl:onDatatype` incorrectly · Issue #593 · ucoProject/UCO