The RsaSignature2018 / proof parts are VCDM v1 and are outdated in v2... From what I gather, c2pa uses COSE Sign1, not DataIntegrityProofs, so the example is misleading.
don't include all of "http://schema.org" is a context... that will cause the JSON-LD processing to become extremely expensive... it would be better to publish a smaller C2PA context with only the terms you use, here is a similar example from physical supply chain use case: https://w3id.org/traceability
Example found here:
https://c2pa.org/specifications/specifications/1.3/specs/C2PA_Specification.html#_w3c_verifiable_credentials
There are a couple issues with this example:
The
RsaSignature2018
/proof
parts are VCDM v1 and are outdated in v2... From what I gather, c2pa uses COSE Sign1, not DataIntegrityProofs, so the example is misleading."did:nppa" is not registered here https://w3c.github.io/did-spec-registries/ ... folks who are interested in it might struggle to learn more.
don't include all of "http://schema.org" is a context... that will cause the JSON-LD processing to become extremely expensive... it would be better to publish a smaller C2PA context with only the terms you use, here is a similar example from physical supply chain use case: https://w3id.org/traceability
I mentioned potentially added better alignment for C2PA to VCDM v2 here: https://github.com/c2pa-org/specifications/issues/36
If there are changes you want to see, please don't hesitate to file issues.
If you have example credentials you want to see added to the v2 test suite, I am also happy to add them there.