I'm unsure of how to go about regenerating these two test vectors or if that would be useful. I don't know if there is functionality that these are supposed to be testing that other test vectors do not already -- other than that they depend on a non-current version of a JSON-LD context file. I don't see if it is possible or helpful to switch these to negatives tests, i.e. to require that implementers use up-to-date context files. So this PR just removes these two test vectors (similarly to #15).
OR13
commented
2 years ago
Verifiable credential test vectors 29 and 30 no longer verify as-is, because of changes in the Traceability context.
Re: https://github.com/w3c-ccg/vc-api-test-suite/pull/17#discussion_r790854661
Fix #16 Close #17
I'm unsure of how to go about regenerating these two test vectors or if that would be useful. I don't know if there is functionality that these are supposed to be testing that other test vectors do not already -- other than that they depend on a non-current version of a JSON-LD context file. I don't see if it is possible or helpful to switch these to negatives tests, i.e. to require that implementers use up-to-date context files. So this PR just removes these two test vectors (similarly to #15).