https://w3id.org/security/v3-unstable -> https://w3id.org/security/bbs/v1
OR13 opened this issue · 4 comments
I think its better to use https://w3id.org/security/bbs/v1 instead of sec-v3.... We need to move towards sec-v3 flattening common vocab from v1 and v2 and not defining suites at all.
@OR13 agree however https://w3id.org/security/bbs/v1 does not define the proof term which is required in several operations with linked data proofs. We perhaps need a seperate context definition just for that term.
I think we could add the proof property in via a scoped context so that we could move to the bbs context while still being able to keep it down to a single context. We might need to check if that term will cause redefinition issues with the vc context as well, but it would be good to figure out a way to handle it that for VCs and for general JSON-LD documents.
the v0.9.0 release in progress will address this
Closed via v0.9.0 release