You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From reading the spec at https://www.w3.org/TR/vc-jose-cose, it aims at securing/formatting the VC/VP and formatting as JWT or COSE. Looking at the repository initial expectation was that these inputs (JWT/COSE) were being generated from the testcases directory. But going deeper and adding an implementation, I can see that the input is from the ./tests/input directory, containing VCs in JSON format.
Am I misunderstanding this specification?
Should the implementation also provide implementation for issuance of the input credentials (example: issue the test/input/valid-credential.json as JWT credential)?
Is this still early test-suite and it is not ready to be implemented on-top of?
Why is there config with check to run? Some verifiers don't have the notion of such fine-grained checks.
Thanks.
The text was updated successfully, but these errors were encountered:
From reading the spec at https://www.w3.org/TR/vc-jose-cose, it aims at securing/formatting the VC/VP and formatting as JWT or COSE. Looking at the repository initial expectation was that these inputs (JWT/COSE) were being generated from the
testcases
directory. But going deeper and adding an implementation, I can see that the input is from the./tests/input
directory, containing VCs in JSON format.test/input/valid-credential.json
asJWT
credential)?config
with check to run? Some verifiers don't have the notion of such fine-grained checks.Thanks.
The text was updated successfully, but these errors were encountered: