add guidance on kid

[Sakurann]

should align with PR #144 better

issue #117.

• add pointer to the guidance on kid in rfc7515.
• clarify that kid can be present only in the header.
• mandate kid when DIDs are used (need to add reference to a DID-Core)

---

Preview | Diff

[msporny]

We need to specify the exact format that we expect here... DID URL -- but is this a relative (frament-only thing) or a fully qualified DID URL (DID URL + fragment). What issue is dealing w/ this?

[OR13]

@msporny I added a link to your comment here: #117 (comment)

To hold the issue open until its addressed.

[OR13]

@msporny I added a link to your comment here: #117 (comment)

To hold the issue open until its addressed.

[iherman]

The issue was discussed in a meeting on 2023-09-14

• no resolutions were taken

View the transcript

6.4. add guidance on kid (pr vc-jose-cose#153)

See github pull request vc-jose-cose#153.

Michael Jones: similarly simple. this simplifies one sentence and adds another one. kid must be present when issuer is expressed as a DID.
� 6 approvals no objections.

Manu Sporny: i think current text as-is is probably ok, except 2 things - we still have an issue in core data model. does not say what is the value of kid, tho seems to assume it is a DID. some assume it is a relative DID. other implementers put absolute DIDs. probably need to specify which one.
� this seem to assume absolute DID with an entire DID.

Michael Jones: from a conversation earlier where we agreed that kid is a string. so intentionally not making a decision.

Kristina Yasuda: there is a separate issued on absolute vs relative DID.
� the purpose is to address the issue in another PR.

Joe Andrieu: calling it DID URL is better. will make a suggestion.

[OR13]

@Sakurann I applied a few small suggestions, but this question remains: #153 (comment)