Christian Bormann

I quickly glanced over that implementation and it seems to not share this problem. I just wanted to make you aware of this problem if this library is already used...

> Either way custom mapping logic of vct values makes it difficult to determine whether the credential's type matches with eu.europa.ec.eudi.pid.1. That check is one of the basic checks the...

> I understand your points and I do agree that there needs to be separate issuer and member state specific metadata documents that describe the custom nuances of each issuer's...

> > > I understand your points and I do agree that there needs to be separate issuer and member state specific metadata documents that describe the custom nuances of...

> Hmm. I did not know we needed to consider worldwide PIDs. I thought EU PID was the root namespace. Worldwide PID namespace certainly makes credential_type case trickier. I don't...

We discussed this a bit and i like the idea to use a domain name, e.g. - did:indy:sovrin.org:abc - did:indy:idunion.org:abc We could still use a github repository governed by hyperledger...

The proposed alterntive `publicKeyMultibase` seems to be not fianlized yet: https://datatracker.ietf.org/doc/draft-multiformats-multibase/

I will create a PR draft so we can discuss what our DID Doc examples should look like. My current approach would be to start with w3c did-core and try...

That would be for didcommv2, we need a context for didcommv1 according to https://github.com/hyperledger/aries-rfcs/blob/main/features/0067-didcomm-diddoc-conventions/README.md (type `did-communication` instead of `DIDCommMessaging`)