Skip to content

Conversation

@vulnmaster
Copy link

Adds investigation:Technician as a new role class to the CASE investigation ontology, addressing Issue #184.

A technician is a forensics role focused on technical tasks during investigations, such as evidence collection, preservation, processing, initial analysis, and repair.

Changes:

  • Added investigation:Technician class definition to investigation.ttl
  • Created comprehensive test example (technician_role_PASS.json) demonstrating Identity-role-performer pattern with temporal tracking
  • Updated test suite (Makefile and test_validation.py)
  • Updated ChangeLog

The implementation follows the established pattern used by other role classes (Attorney, Examiner, Investigator, Subject) and maintains backward compatibility.

Tests demonstrate:

  • Technician role instances with appointment dates (startTime)
  • Identity linked to Technician role via uco-core:role
  • Technician role as performer of InvestigativeAction
  • Integration with Investigation, File, and ProvenanceRecord

All SHACL validation tests pass.

This is a low risk addition to CASE.

Ready for solution review.

Adds investigation:Technician as a new role class to the CASE
investigation ontology, addressing Issue casework#184.

A technician is a forensics role focused on technical tasks during
investigations, such as evidence collection, preservation, processing,
initial analysis, and repair.

Changes:
- Added investigation:Technician class definition to investigation.ttl
- Created comprehensive test example (technician_role_PASS.json)
  demonstrating Identity-role-performer pattern with temporal tracking
- Updated test suite (Makefile and test_validation.py)
- Updated ChangeLog

The implementation follows the established pattern used by other role
classes (Attorney, Examiner, Investigator, Subject) and maintains
backward compatibility.

Tests demonstrate:
- Technician role instances with appointment dates (startTime)
- Identity linked to Technician role via uco-core:role
- Technician role as performer of InvestigativeAction
- Integration with Investigation, File, and ProvenanceRecord

All SHACL validation tests pass.

Closes casework#184
@vulnmaster vulnmaster added Community-Vote Thumbs up or down for voting on a change. Project-NewObject Add a new object to the ontology. labels Oct 22, 2025
@vulnmaster vulnmaster removed their assignment Oct 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Community-Vote Thumbs up or down for voting on a change. Project-NewObject Add a new object to the ontology.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants