There are several JSON-LD input documents where the proof property does not adhere to the spec data model requirements of a data integrity proof outlined in https://www.w3.org/TR/vc-data-integrity/#proofs. Here's an illustrative example in example1.jsonld (which is meant to be correct)
But the following properties are mandated (MUST) by the spec:
verificationMethod
proofPurpose
Looking at the spec for the proof type RsaSignature2018 I can't see where/if it defines an alternative data model - https://w3c-ccg.github.io/lds-rsa2018/ and when looking at the context
This isn't the case for all of the examples, for instance example-5.jsonld has the correct construction:
Could y'all point me to where the schema for this is defined that means that the values aren't required? And if they are required should we update the input documents?
There are several JSON-LD input documents where the
proof
property does not adhere to the spec data model requirements of a data integrity proof outlined in https://www.w3.org/TR/vc-data-integrity/#proofs. Here's an illustrative example inexample1.jsonld
(which is meant to be correct)But the following properties are mandated (MUST) by the spec:
Looking at the spec for the proof type
RsaSignature2018
I can't see where/if it defines an alternative data model - https://w3c-ccg.github.io/lds-rsa2018/ and when looking at the contextThis isn't the case for all of the examples, for instance
example-5.jsonld
has the correct construction:Could y'all point me to where the schema for this is defined that means that the values aren't required? And if they are required should we update the input documents?