Re-release of 3.7.0 with JSONSchema module pinned to ~4.17.3

3.7.1

• JSONSCHEMA pinned to ~4.17.3 (implying <4.18.0 releases) for now, until we can figure out why the 4.18.0 causes the severe workflow schema access bug

v3.7.0

• implementation of reasoner-validator issue #86 in which explicit validation error KP/ARA sources are reported in the validation. This change is sufficiently disruptive to the code methods and representation that 'minor' release of the repository is incremented to 3.7.
• to avoid confusion with new 'source' reporting, the pre-3.7 provenance 'sources' variable is renamed to 'target_provenance' and the variable localized directly into the BiolinkValidator constructor and included as parameter for pertinent high level method calls
• Use of Biolink Model node category biolink:BiologicalCategory which is abstract, now only triggers a validation warning, not an error. The 'exception' is currently hard coded into the validation (could have other categories added in this manner, if needed, later).

TRAPI 1.4.1 aware

• code takes TRAPI 1.4.1 as the latest schema
• further refactor of SemVer versioning code for robustness and abstraction

Temporary patch to workaround small defect in TRAPI validation

... plus some technical debt clean-up

Update to BMT 1.1.0 (Biolink Model 3.5.0)

v3.6.4

Full TRAPI 1.4.0 supported release

1.4.0 is now the full latest TRAPI release tracked by the code (for testing), but 1.4.0-beta code and unit tests being kept (for now)

Mostly refinements to support SRI Testing harness

• Various tweaks to the case 'test edge' validation code, to meet SRI Testing needs
• Split BiolinkValidator class into two parent parts, for ease of lightweight BMT wrapping reuse; for case edge validation, also look at predicate children (bullet proof validation against None BMT handle?)
• Add trapi error code for missing knowledge graph; tweak Response validation codes and docs
• Guarantee return of the original seed identifier when getting the list of aliases from Node Normalizer

SemVer fixed to handle local schema file versioning; tech docs updated

• Reversed order of codes in codes.yaml resulting in new documentation order: Critical at top, Information at the bottom
• Fixed bug with SemVer capture of local schema files: assume SemVer versioning is embedded in root file name
• Tiny tech debt clean up

Introduced new 'critical' error category for validation

This is in an initial release of code supporting a new 'critical error category for validation messages. The initial messages moved over from the original 'error' partition are:

• critical.trapi.validation
• critical.trapi.request.invalid
• critical.trapi.response.unexpected_http_code

The full list of validation codes will be reviewed for additional 'critical' error stages, and updated in future project patch releases.

Patch of v3.1.10

v3.5.11

Extend TRAPI Response sanitization (following Eric Deutsch guidance)

v3.5.10