Use any existing TIME hints in graph to do further ordering. #54
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Alex Nelson <[email protected]>
Member
Author
|
I'm postponing this for after Some example two-node graphs should be written to show how each of the Allen algebra1 properties render with the graph flow direction already used by the PROV-O properties. Footnotes
|
No effects were observed on Make-managed files. Signed-off-by: Alex Nelson <[email protected]>
ajnelson-nist
force-pushed
the
use_temporal_sorting_hints
branch
from
a00a4d3 to
cc74f04
Compare
References: * https://www.w3.org/TR/owl-time/#fig-thirteen-elementary-possible-relations-between-time-periods-af-97 Signed-off-by: Alex Nelson <[email protected]>
ajnelson-nist
added a commit
that referenced
this pull request
May 18, 2023
…nodes This patch uses the inherence UUID functions from `case-utils` PR 112 to replace the blank nodes generared with SPARQL Construct queries. As side effects of this migration, some bugs were fixed with generating some associations, and inherence modeling assumptions are now specified in code comments. This patch also adds `prov:Start` and `prov:End` nodes to reify `prov:Activity` (and `case-investigation:InvestigativeAction`) time boundaries. This will be a significant assistance in OWL-Time-based visualization under development for `case-prov` PR 54. Creating the `prov:Start` and `prov:End` nodes as IRI-identified is also necessary because of a bug observed in `rdf-toolkit`; see their Issue 52. Since `case_prov_rdf` will now be able to generate non-blank nodes, it has picked up two behaviors used in other projects importing `case-utils`: * The `--use-deterministic-uuids` flag has been added. * The `CASE_DEMO_NONRANDOM_UUID_BASE` environment variable can now be used to make non-inherent deterministic UUIDs. A follow-on patch will regenerate Make-managed files. References: * #54 * casework/CASE-Utilities-Python#112 * edmcouncil/rdf-toolkit#52 Signed-off-by: Alex Nelson <[email protected]>
ajnelson-nist
added a commit
that referenced
this pull request
May 18, 2023
…nodes This patch uses the inherence UUID functions from `case-utils` PR 112 to replace the blank nodes generated with SPARQL Construct queries. As side effects of this migration, some bugs were fixed with generating some associations, and inherence modeling assumptions are now specified in code comments. This patch also adds `prov:Start` and `prov:End` nodes to reify `prov:Activity` (and `case-investigation:InvestigativeAction`) time boundaries. This will be a significant assistance in OWL-Time-based visualization under development for `case-prov` PR 54. Creating the `prov:Start` and `prov:End` nodes as IRI-identified is also necessary because of a bug observed in `rdf-toolkit`; see their Issue 52. Since `case_prov_rdf` will now be able to generate non-blank nodes, it has picked up two behaviors used in other projects importing `case-utils`: * The `--use-deterministic-uuids` flag has been added. * The `CASE_DEMO_NONRANDOM_UUID_BASE` environment variable can now be used to make non-inherent deterministic UUIDs. A follow-on patch will regenerate Make-managed files. References: * #54 * casework/CASE-Utilities-Python#112 * edmcouncil/rdf-toolkit#52 Signed-off-by: Alex Nelson <[email protected]>
Merged
This merge re-applied changes done for `case_prov_dot.py`, with some fixes applied for issues reported by `mypy`. No effects were observed on Make-managed files.
No effects were observed on Make-managed files. Signed-off-by: Alex Nelson <[email protected]>
This figure shows only two of the Allen interval-relations are handled by the ordering logic now. However, the figure does show time flowing "downward" by seeing the before & after `*-i` intervals are above the `*-j` intervals. A follow-on patch will regenerate Make-managed files. Signed-off-by: Alex Nelson <[email protected]>
Signed-off-by: Alex Nelson <[email protected]>
This patch enables `pytest`'s doctest mode and adds a first doctest to ensure `pytest` doesn't fail due to finding no tests to run. Follow-on patches will add new functions with more demanding doctests. No effects were observed on Make-managed files. References: * https://docs.pytest.org/en/7.1.x/how-to/doctest.html * casework/CASE-Utilities-Python#111 Signed-off-by: Alex Nelson <[email protected]>
This function is added independently, without usage yet, to isolate test effects. No effects were observed on Make-managed files. Signed-off-by: Alex Nelson <[email protected]>
This function is added independently, without usage yet, to isolate test effects. No effects were observed on Make-managed files. Signed-off-by: Alex Nelson <[email protected]>
This patch adds inferential analysis to define temporal interval boundaries and apply timeline sorting, both topologically and lexicographically. CASE Investigative Actions are already inferred by current `case_prov_rdf` and `case_prov_dot` practice to be PROV Activities. This patch takes inference further to interpret PROV Activities as OWL-Time Proper Intervals. Further, PROV Instantaneous Events are inferred to be OWL-Time Instants, and their relationships to Entities and Activities are used to establish topological order according to PROV (English) definitions. All OWL-Time Instants, and nodes inferred to be OWL-Time Instants, are assigned `xsd:dateTimeStamp` values in GMT (where possible) to enable a timeline based on lexicographic sorting. Figures' and tests' Makefiles are updated to add new graphs to display. A follow-on patch will regenerate Make-managed files, and track new figures. The last planned follow-on patch will add OWL-Time documentation to the top README. Signed-off-by: Alex Nelson <[email protected]>
Signed-off-by: Alex Nelson <[email protected]>
A follow-on patch will regenerate Make-managed files. The patch afterwards will add OWL-Time documentation to the top README. Signed-off-by: Alex Nelson <[email protected]>
Signed-off-by: Alex Nelson <[email protected]>
Signed-off-by: Alex Nelson <[email protected]>
Member
Author
|
The PR now contains an implementation of OWL-Time ordering. The README and recent patch notes document rationales and demonstrate new illustrations. The SIEM scenario sketch from this PR's initial comment now looks like this:
The Urgent Evidence Activities graph is, to me, the most interestingly effected of the examples in this repository. Investigative Actions were loosely piled topologically due to most not having information about how they influenced one another. With timestamps now influencing vertical sort order, the provenantial links remain the same but the display is now ordered in a decent semblance of a timeline. Here is the visual diff. |
The RDFLib issue referenced in the comment summarizes the type-safety matter. No effects were observed on Make-managed files. Signed-off-by: Alex Nelson <[email protected]>
kchason
approved these changes
Jun 12, 2023
ajnelson-nist
added a commit
to usnistgov/CASE-Implementation-PROV-O
that referenced
this pull request
Jun 12, 2025
This patch revises `case_prov_dot` to make use of updates in code review practice and upstream typing support since the script was originally written. The original version of `case_prov_dot` relied on many conversions of RDFLib types to strings. This induced some reinvention of logical organization of concepts into IRI strings vs. quickly-instantiated and -discarded `rdflib.URIRef` objects. Some usage of `URIRef`s as strings was covered by `URIRef`s being implemented in RDFLib as subclasses of string. As work progressed on adding TIME concept support (see PR 54), it became unnecessarily burdensome to handle some work with managing untyped strings under specialized consideration, versus constructing sets of `rdflib.URIRef`s to designate nodes. Managing potential blank nodes also became a challenge with casts to strings. This patch revises the base work in `case_prov_dot` to be oriented on analyzing sets of `rdflib.term.IdentifiedNode`s (encompassing `URIRef`s and `BNode`s). A roadmap/codemap is also added in inline documentation to describe sections of code behavior. Revision of the code flow also settled some design issues that were previously unnecessarily isolating the various chains from one another, especially where some chains needed to be handled as a mutual union, and another needed to be handled as an intersection, when various subsets of the provenance graph are requested. So this patch also adds the various pairs of chains as demonstrations under the Urgent Evidence example. A follow-on patch will regenerate Make-managed files. References: * casework#54 Signed-off-by: Alex Nelson <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch is written for the benefit of this scenario sketch. The additional linkage manages to reduce the lateral "sprawl" of the illustration.
Before (
developat351afb9):After (this branch):
An assumption of an alignment of PROV-O with W3C TIME is assumed, and cited in an inlined comment.