Feature CP 43 - Recovered Object

[cyberinvestigationexpress]

Pull request instructions

Implement CP-43 based on 2018 community approved proposal for Representing Recoverability of Unallocated Files.

This Pull Request resolves all requirements of Issue #251.

Coordination

• Tracking in Jira ticket OC-119
• [x] Pull request is against correct branch
• [x] CI passes in (CASE/UCO) feature branch
• [x] CI passes in (CASE/UCO) current unstable branch (22da00c)
• [x] CI passes in CASE current unstable branch tracking UCO's unstable as submodule (skipped - additive change)
• [x] Impact on SHACL validation reviewed for CASE-Examples
• [x] Impact on SHACL validation remediated for CASE-Examples
• [x] Impact on SHACL validation reviewed for casework.github.io
• [x] Impact on SHACL validation remediated for casework.github.io (N/A)
• [x] Solutions Approval vote occurred, passing, on 2022-08-16

[ajnelson-nist]

Testing in CASE-Examples showed there are a couple more PropertyShapes per DatatypeProperty that need to be added in order to finish encoding the UCO semi-open vocabulary validation mechanism. Reviews should probably check for the drafting.ttl file within CASE-Examples PR 83.

Also, this PR looks like it wasn't started from the right state. Let's discuss in the morning.

[ajnelson-nist]

Re:

Also, this PR looks like it wasn't started from the right state. Let's discuss in the morning.

This PR's branch should have been started from develop, but we've had enough accidents in starting from master that I think we're past trying to keep that branch history pattern clean.

[ajnelson-nist]

This will have a merge conflict with the resolution of Issue #435 , due to addition of a new vocabulary.

[ajnelson-nist]

Converting to draft while checking for CASE unstable branch impact.

[ajnelson-nist]

After discussion with @b0bkaT , purely-additive changes have less need to undergo the CASE unstable review. This is ready to merge.