feat: Update region of interest assertion to 2.1 spec #545
Conversation
This file contains 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
ok-nick
changed the title
scouten-adobe
changed the title
|
This was updated as part of e4dce31 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changes in this pull request
Some of the fixtures in c2pa-rs and c2patool assume the
identifiedregion of interest field exists, but it only exists in the 2.1 spec. This PR adds the new fields and changes to region of interest assertion in the 2.1 draft spec.https://c2pa.org/specifications/specifications/2.1/specs/C2PA_Specification.html#_regions_of_interest
Checklist
TO DOitems (or similar) have been entered as GitHub issues and the link to that issue has been included in a comment.