Releases: casework/CASE-Implementation-PROV-O
Releases · casework/CASE-Implementation-PROV-O
0.3.0
New features:
- This repository has been re-licensed under Apache 2.
- CASE 0.7.0 has been adopted.
case-prov
is now available on PyPI.case_prov_dot
now has a flag--query-ancestry
to specify a set of nodes for which the user wants to view ancestry.- Any usage of the CASE concepts
investigation:wasDerivedFrom
andinvestigation:wasInformedBy
are now mapped directly into PROV, to assist with chain-of-custody review. (Usage of the CASE concepts that is not also supported by CASEInvestigativeAction
s andProvenanceRecord
s will render as dashed lines in the PROV-O translation illustration.)
Updated documentation:
- The
prov:Derivation
construction query now documents that it intentionally creates aprov:Derivation
perprov:entity
predicate usage.
Updates for developers:
- A CODEOWNERS file has been added.
case-utils
is now imported via PyPI.- Code-review tools
black
,flake8
, andisort
are now run withpre-commit
, andpre-commit
has been added to Continuous Integration. - Unit tests within this repository now require Java >= 11, due to the toolset upgrade in UCO Issue 373.
- This repository now runs Continuous Integration tests on the same Python versions as
case-utils
.
Fixes:
- The
prov:Communication
andprov:wasInformedBy
construction queries received a logic fix and speed ugprade.
0.2.0
This release adopts CASE 0.6.0, by adopting the case_utils
0.4.0 release.
Some command interface changes have been made since the prior release:
- The argument order for
case_prov_rdf
andcase_prov_dot
now take the output file as the first argument, and the input graph files as the second and onward.- The commands now also accept multiple input graph files, aligning their behavior with other commands from
case_utils
.
- The commands now also accept multiple input graph files, aligning their behavior with other commands from
Some input data behaviors have changed since the prior release:
- The CASE
ProvenanceRecord
is now incorporated intoprov:wasInformedBy
construction. - CASE
InvestigativeAction
s that had aninstrument
but noperformer
now report theinstrument
as theprov:Agent
.
Some output effects have changed since the prior release:
- Per PROV convention found since the initial release, figures now have a temporal flow from top to bottom, which is reversed from the initial release.
- A bug with multiple-edge display has been corrected.
Some developer quality-of-life implementations have been made:
- Unit tests called with
make check
are now run as part of Continuous Integration (CI). - Unit tests now use
venv
instead ofvirtualenv
. - The CASE "Crossover" scenario has been added to the usage demonstration in this repository.
- Code in this repository is now formatted with
black
, and checked with CI. - Code in this repository is now statically type-checked with
mypy
, and checked with CI.
0.1.0
Initial release