Skip to content
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

Confirm an InvestigativeAction results in at least one ProvenanceRecord #147

Draft
wants to merge 3 commits into
base: develop
Choose a base branch
from

Commits on Jan 23, 2024

  1. Confirm an InvestigativeAction results in at least one ProvenanceRecord

    This new shape stemmed from discussion on CASE Issue 136.
    
    As a matter of preserving backwards compatibility, this patch introduces
    the shape requiring `ProvenanceRecord`s with a `sh:Warning`-level
    severity.  In CASE 2.0.0, this requirement will be strengthened into a
    `sh:Violation`.
    
    A separate proposal will be filed with UCO to test the minimum qualified
    cardinality OWL structure.  A draft of that syntax review system was
    used to test this patch.
    
    This patch adds a version floor for pySHACL to ensure an update in
    qualified value shape handling is included, which is necessary for the
    new property shape to function when using pySHACL.
    
    Disclaimer:
    
    References:
    * RDFLib/pySHACL#213
    * #136
    * #146
    
    Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
    ajnelson-nist committed Jan 23, 2024
    Configuration menu
    Copy the full SHA
    a4802b5 View commit details
    Browse the repository at this point in the history

Commits on Feb 9, 2024

  1. Configuration menu
    Copy the full SHA
    c3d7a34 View commit details
    Browse the repository at this point in the history

Commits on May 3, 2024

  1. Configuration menu
    Copy the full SHA
    078030a View commit details
    Browse the repository at this point in the history