Orie Steele

@jsong1230 please open a PR to add your contact info.

There is also https://datatracker.ietf.org/doc/draft-ietf-httpbis-unprompted-auth/ which is worth considering. > The Concealed HTTP authentication scheme allows a client to > authenticate to an origin server while guaranteeing freshness and > without...

I agree, we should provide an example (not ION, but similar structure) and a note.

Needs PR to add explicit warning about how DID params are dropped from the did document and may be present in resolver meta data.... needs PR.

I worry that folks don't realize how this impacts Verifiable Credentials.... this means that when you resolve: "did:example:123?version-id=1#key-0" and you get back a did document with verificationMethod: "did:example:123#key-0" You will...

@msporny its rather that there is no algorithm in ANY spec, that handles this properly... including the VC Data Model (does not elaborate on query parameters) and JWT/JWS (which does...

I think this belongs in did core, since did core is defining dereferencing... we either define how parameters are or are not present in the resulting documents... or we stop...

@peacekeeper regarding query parameters.... they are NOT allowed in the `id` field of a did document. Are they allowed in the `id` field of a verificationMethod?

@dlongley @peacekeeper @msporny @dhh1128 @kdenhartog This is one of the most important parts of the whole specification. It's the link between did core and all assertion formats that use identifiers,...

If you are using JSON-LD, the identifiers from the credential are expected to match the document returned by the resolver... JSON-LD has a whole section of the spec dedicated to...