Issue 178 addition of CASE investigation:Investigator subclasses #183
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add new subclasses to investigation:Investigator per CASE change proposal 178
Add change for CASE issue 178 - addition of investigation:Investigator subclasses
13 tasks
|
This PR passed Solutions Review by the CDO OC on 10/21/2025. It can be merged once @ajnelson-nist is ready. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This Pull Request resolves all requirements of Issue # 178 .
Summary
Added investigator role subclasses and SHACL shapes in ontology/investigation/investigation.ttl:
Academic, Civil Society, Corporate, Human Rights, Insurance, Intelligence, Law Enforcement, Military, Private, Regulatory
Updated ChangeLog to note CASE Issue 178.
Rationale
These subclasses make investigator roles explicit to support clearer modeling, validation, and downstream reasoning across CASE implementations.
Scope of change
Additions only; no breaking removals or cardinality changes anticipated.
Files touched:
ontology/investigation/investigation.ttl
ChangeLog
Risk and compatibility
Low risk, additive changes; backward compatible with existing data and tooling.
Validation
Shapes defined alongside classes to support validation.
Ontology compiles and normalizes as expected with standard CASE workflows.