Conversation
✅ Deploy Preview for cai-open-source ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
🚀 Deployed on https://deploy-preview-306--cai-open-source.netlify.app |
|
|
||
| ### Configuration in SDK settings | ||
|
|
||
| Configure the settings file with the created assertions like this: |
There was a problem hiding this comment.
To confirm: The below settings make the SDK create all assertions with those labels into created assertions?
There was a problem hiding this comment.
Yes and also the assertion versions. So "c2pa.actions" will include c2pa.actions.v2 also. An assertion can also be set as created in the manifest definition with created: true
timmurphydev
left a comment
There was a problem hiding this comment.
This looks good, Rand. I think you explained it really well.
My overall comment on the subject of created vs. gathered assertions is that they need to be configured intentionally and reflect the actual claim generating environment. Some assertions may be commonly be configured as created, but that doesn't mean it will be true for all claim generators.
|
|
||
| ### Configuration in SDK settings | ||
|
|
||
| Configure the settings file with the created assertions like this: |
There was a problem hiding this comment.
Yes and also the assertion versions. So "c2pa.actions" will include c2pa.actions.v2 also. An assertion can also be set as created in the manifest definition with created: true
|
|
||
| * “This image was generated using Adobe Firefly” | ||
| * “This video was edited in Premiere Pro” | ||
| * Custom metadata like author name, title, or usage rights |
There was a problem hiding this comment.
Is this referring to custom assertions?
Some info from Discord: https://discord.com/channels/983153151341371422/1403049797023174828/1471361096094056613 with additional context etc.
New section: https://deploy-preview-306--cai-open-source.netlify.app/docs/manifest/writing/assertions-actions#created-versus-gathered-assertions