Orie Steele

+1 @dlongley ... IMO it was a mistake to "seperate the proof" before normalization... the complexity of this that the container semantics for proof are brutal.... ``` "proof": { "@id":...

Here is the code we used for the merkle proof suite... https://github.com/transmute-industries/merkle-disclosure-proof-2021/blob/main/src/merkle/normalization/urdna2015.ts IMO, proof should be handled along with the document... not separately from it... only the attributes of the...

@dlongley yes, I have been weighing the trade offs wrt that... IMO, this not the appropriate place to address multi-signature formats... that work should be handled in a work item...

@swcurran https://github.com/decentralized-identity/bbs-signature/issues/10#issuecomment-939546272 > Can a credential schema or a presentation request be designed to avoid the issue? yes, but such a credential cannot have any "blank nodes"...

This is currently working: https://did.key.transmute.industries/did:key:z5TcF54ZLL5RVaKcvfPbaX2aBFJbXPcc5wG8bomgt4jyap1wVhtHtWVD2gDwD4jXsbEE1PSMeNfEUxkeVjd2R1fvJiaAmrEc2cQsvBe3UmVS7F3FT18mig8PnN2SRRGRsrMva7QPdBSQajC6JkPN2G2Aye3PAgbcjXdFknvCLbaGCBpDCqyyPh6EU7GxJkvmciNk4onHR I have general concerns with the approach digital bazaar is taking with documentLoaders... they are either a resolver or a dereferencer... I have been treating...

https://github.com/transmute-industries/verifiable-data/blob/main/packages/bbs-bls12381-signature-2020/src/BbsBlsSignature2020.ts#L48 ^ this implementation supports it... feel free to help port it here.

The function is required by digital bazaar, the context url is in the form we agreed to use during the did WG. On Sat, Apr 2, 2022, 2:11 PM Karim...

probably you have too many contexts in your JSON-LD... and they both define the same term, `Ed25519Signature2018`

Past the example you are trying to sign.

@cre8 I am not sure, but I would guess you would need to downgrade `jsonld-signatures` in order to avoid this issue.