Orie Steele

@peacekeeper hmmm, i feel like @msporny would hate the same key type being used for 2 signatures.

> The last thing we want is for people to create protocols, put a tax on them, and then try and proliferate them through the internet via W3C standards The...

We should close this issue when we have consensus documented in the html that private information will or will not be included here, and some guidance one how private information...

@msporny @dlongley related: https://github.com/multiformats/multicodec/pull/194

I like documentation all in one place, but I am fine with the context split, I proposed it and I think it has the security features developers expect. Its also...

I believe this can be closed when these PRs are merged: - https://github.com/w3c/vc-data-integrity/pull/135 - https://github.com/w3c/vc-data-integrity/pull/148

My hope was to use digital bazaar libraries here: https://github.com/transmute-industries/api.did.actor/tree/main/vc-api/facade So we could test did key and vc based interop with a toggle for selecting the vendor, but I cannot...

I suggest we create security-v3-unstable note that its unstable, and add this, and a lot of other stuff there. @msporny @dlongley thoughts?

We think the language could be improved... probably by some folks working on EDVs and DIDComm. See https://github.com/w3c-ccg/security-vocab/pull/109#issuecomment-897855539

`X25519KeyAgreementKey2019` should not "allude to key derivation"... we use this type for keys generated directly from randomness. for example, compare: - https://did.key.transmute.industries/generate/x25519?seed=d345b4ae293e8fc85dc7cb47b6a9ce2e812d545693d7885f251ab1b14c684078 - https://did.key.transmute.industries/generate/ed25519?seed=d345b4ae293e8fc85dc7cb47b6a9ce2e812d545693d7885f251ab1b14c684078