Orie Steele

@iherman please help! :) https://www.w3.org/pubrules/?url=https%3A%2F%2Fw3c.github.io%2Fdid-imp-guide%2F&profile=WG-NOTE&validation=simple-validation&noRecTrack=false&informativeOnly=false&echidnaReady=false&patentPolicy=pp2020 I am trying to ensure the document is ready for a stable version to be reviewed, not sure what I have to do, but pub...

@iherman thanks! I have tested it a few times, and I still can't get Pub Rules to stop complaining. I think I must be missing something obvious... there are 0...

@TallTed would you mind resolving all change suggestions that have been addressed? or lmk if you feel this is good from your perspective?

See https://medium.com/transmute-techtalk/linked-data-proofs-vs-jose-why-not-both-1594393418cc Its necessary for interoperability between linked data signatures and "vanilla jose"... small price to pay, and it should only need to be paid once now.

also... we defintly don't want to remove `id` because the value might not be equivalent to `kid`... and `kid` might not be a valid URI... and also `publicKey`s might not...

If we want to represent `publicKey` as vanilla JWKs, we can do so by creating and registering a property `jwks` in the core registry... not all keys in the `publicKey`...

I think we need to provide better examples of DID Methods that use JWKs... this will make this clearer.

Here is an example in the did core registry: https://w3c.github.io/did-core-registry/#ecdsasecp256k1verificationkey2019

related to JsonWebKey2020: https://github.com/w3c-ccg/lds-jws2020#supported-jws-algs We need `id` and `type` for keys that are not JWKs... but we should do our best to align these values with `kty` and `crv` when...

recommend closing, we have discussed this many times. we need both `id` and `type` and `publicKeyJwk` / `publicKeyBase58`...