Skip to content

Commit 8daa7d0

Browse files
authored
Merge pull request #189 from contentauth/clarify-validation_status
Highlight note about validation_status array
2 parents bb041aa + 3ef4d97 commit 8daa7d0

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

docs/manifest/validation.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,11 @@ Processing an asset includes [validating the manifests](https://c2pa.org/specifi
77

88
## Validation errors in manifests
99

10-
When you load an asset, all the manifests in the manifest store are validated and any [failure codes](https://c2pa.org/specifications/specifications/1.4/specs/C2PA_Specification.html#_failure_codes) are assigned to the `validation_status` array. Inspect the array to find the validation errors. Validation returns ONLY error codes; success is not explicitly indicated.
10+
When you load an asset, all the manifests in the manifest store are validated and any [failure codes](https://c2pa.org/specifications/specifications/1.4/specs/C2PA_Specification.html#_failure_codes) are assigned to the `validation_status` array. Inspect the array to find the validation errors.
11+
12+
:::tip
13+
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.
14+
:::
1115

1216
Manifest validation errors can occur, for example, when:
1317

0 commit comments

Comments
 (0)