Repository navigation
Reason codes for skipped criteria - #11
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Every skipped criterion carries a reason_code as defined under Results in CRITERIA-FORMAT.md of dpp-criteria (PR 17): not_applicable for conditions that do not hold, no DID, no RelatedResource or key_from that is not a DID; no_evidence for a passport without integrity proof or a DID document without payloadHash; not_evaluated for unsupported proof formats, unreachable didlint, missing shapes, history-based criteria, POST without product identifier and unusable patterns. The summary counts them per code in skipped_by_reason. The start page shows the reason per criterion and the breakdown; Swagger and README document both fields.