Skip to content
Cyber-investigation Analysis Standard Expression (CASE) Ontology
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
docs
examples
.gitignore Rename 'Encrypted', 'Encoded', and 'Compressed' to 'Encryption', 'Enc… Sep 21, 2016
LICENSE Create LICENSE Dec 19, 2018
README.md
_config.yml Set theme jekyll-theme-slate Jan 11, 2017
case-v0.1.0-natural-language-glossary.html Natural language glossary for CASE v0.1.0 Jan 11, 2017
case.md Add Volume manager properties and property bundles. Feb 24, 2017
case.ttl Add Volume manager properties and property bundles. Feb 24, 2017
generate_doc.py
glossary.md Updated the file.json example. Added writeup to explain how the file.… Oct 24, 2016
requirements.txt Add requirements.txt Dec 2, 2016

README.md

Cyber-investigation Analysis Standard Expression (CASE)

Read the Wiki tab to learn everything you need to know about the Cyber-investigation Analysis Standard Expression (CASE) ontology. For learning about the Unified Cyber Ontology, CASE's parent, see UCO.

Examples in this Repository

These will eventually be moved to the Wiki (likely Mapping Guide). Mapping notes & respective JSON-LD output:

I have a question!

Before you post a Github issue or send an email ensure you've done this checklist:

  1. Determined scope of your task. It is not necessary for most parties to understand all aspects of the ontology, mapping methods, and supporting tools.

  2. Familiarize yourself with the labels and search the Issues tab. Typically, only light-blue and red labels should be used by non-admin Github users while the others should be used by CASE Github admins. All but the red Project labels are found in every casework repository.

You can’t perform that action at this time.