Absolute IRI "sec:BbsBlsSignature2020" confused with prefix "sec".

   "@mattrglobal/jsonld-signatures-bbs": "0.7.1-unstable.2673a0a",

I believe this is caused by the interaction between sec-v3-unstable...

jsonld-signatures-bbs/src/BbsBlsSignature2020.ts

Line 54 in 2673a0a

type: "sec:BbsBlsSignature2020"

imo this call to super should be with

jsonld-signatures-bbs/src/BbsBlsSignature2020.ts

Line 401 in 2673a0a

"https://w3id.org/security#BbsBlsSignature2020"

See similar approach taken here:

https://github.com/w3c-ccg/lds-jws2020/blob/master/packages/json-web-signature-2020/src/JsonWebSignature.ts#L25

@OR13 can you provide an example of when this is occuring because I believe this is correct behaviour based on the limitations of the security v2 context

This is a work around because the new sec-v3 context doesn't properly expand with the current json-ld signatures implementation due to the removal of the prefixes and moving to long form IRIs. See this issue for additional details: digitalbazaar/jsonld-signatures#118

more details here: w3c-ccg/security-vocab#80

I am attempting to get the credentials to work with only:

credentials/v2
security/v3-unstable

Reminder to fix this :

jsonld-signatures-bbs/src/BbsBlsSignature2020.ts

Line 59 in 2673a0a

type: "BbsBlsSignature2020"

Then we won't need to load sec-v3 with when cred-v2 or bbs-v1 is included.

IMO, we should just wait until the latest stable uses addresses this issue

Then add examples of linked data signatures and credentials, that replace the current sample and only use:

This issue will be addressed in the up and coming v0.8.0 release