Skip to content

Commit 5072faa

Browse files
committed
update validation
1 parent 34e6196 commit 5072faa

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

docs/manifest/reading/validation.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,11 @@ Need a high-level summary of full validation, what we're looking for, etc.
1515

1616
## Validation errors in manifests
1717

18-
When you load an asset, all the manifests in the manifest store are validated and any [failure codes](https://c2pa.org/specifications/specifications/2.2/specs/C2PA_Specification.html#_failure_codes) are assigned to the `validation_status` array. Inspect the array to find the validation errors.
18+
When you load an asset, all the manifests in the manifest store are validated and any [failure codes](https://c2pa.org/specifications/specifications/2.2/specs/C2PA_Specification.html#_failure_codes) are assigned to the `validation_status` array. Inspect the array to find the validation errors.
19+
20+
`Reader` has these validation methods:
21+
- `validation_state()` returns `ValidationState`, which can be `Invalid`, `Valid` or `Trusted`.
22+
- `validation_results()` returns `ValidationResults`, which returns `success`, `informational`, and `failure` codes for the active manifest and ingredients. NOTE: `ValidationStatus` is deprecated in favor of `ValidationResults`.
1923

2024
:::tip
2125
Validation returns ONLY error codes; success is not explicitly indicated. If there are no validation errors, then the manifest won't have the `validation_status` element.

0 commit comments

Comments
 (0)