-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature CP 43 - Recovered Object #408
Conversation
Fix website link in CONTRIBUTE.md
Add issue templates
Release 0.9.0
Define UnallocatedRecoverabilityFacet
Define UnallocatedRecoverabilityStatusVocab
Testing in CASE-Examples showed there are a couple more Also, this PR looks like it wasn't started from the right state. Let's discuss in the morning. |
The file `drafting.ttl` contains the contents of UCO PR 408, transcribed for the purpose of SHACL review. As SHACL review occurred, two more shapes per datatype property were added to account for validation according to the UCO semi-open vocabulary design. See Change Proposal 100 from UCO 0.8.0's release page to understand this enforcement mechanism. JSON-LD Knowledge Base concepts in this example were modified to use the `drafting:` prefix instead of the under-proposal `observable:` and `vocabulary:`-prefixed concepts. A follow-on patch will regenerate Make-managed files. References: * ucoProject/UCO#408 * https://unifiedcyberontology.org/releases/0.8.0/ Signed-off-by: Alex Nelson <[email protected]>
Edited name UnallocatedRecoverability to RecoveredObject
Edited name UnallocatedRecoverability to RecoveredObject
References: * [UCO OC-119] (CP-43) Represent recoverability of unallocated files Signed-off-by: Alex Nelson <[email protected]>
References: * [UCO OC-119] (CP-43) Represent recoverability of unallocated files Signed-off-by: Alex Nelson <[email protected]>
References: * [UCO OC-119] (CP-43) Represent recoverability of unallocated files Signed-off-by: Alex Nelson <[email protected]>
The semi-open vocabulary pattern is in conformance with the OWL enforcement designed in Issue 406. The imported concepts match the state of CASE-Examples PR 90. References: * [UCO OC-119] (CP-43) Represent recoverability of unallocated files * casework/CASE-Examples#90 * #406 Signed-off-by: Alex Nelson <[email protected]>
Re:
This PR's branch should have been started from |
This will have a merge conflict with the resolution of Issue #435 , due to addition of a new vocabulary. |
Converting to draft while checking for CASE |
After discussion with @b0bkaT , purely-additive changes have less need to undergo the CASE |
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
unstable
branch tracking UCO'sunstable
as submodule (skipped - additive change)