Orie Steele

JWS Suite Needs to be added

1

https://github.com/decentralized-identity/claims-credentials/tree/main/work_items Owners, meeting time, deliverables, etc...

https://www.w3.org/TR/did-imp-guide/#additional-guidelines link to https://www.w3.org/reports/did-sec-priv-criteria-overview-public.pdf is 404. Yet it is in the repo here: https://github.com/w3c/did-imp-guide/blob/main/reports/did-sec-priv-criteria-overview-public.pdf Ideally we can point to this documented hosted on a remote server.

FPWD is due in 2 weeks

2

1 week for content 1 week for editorial

Do an editorial pass

3

- [ ] Wrap terms in `a` tag, such as DID and DID Document (https://github.com/w3c/did-imp-guide/pull/12#discussion_r686214151) - [ ] Remove parens (https://github.com/w3c/did-imp-guide/pull/12#discussion_r686216993) - [ ] Title case all H2's (https://github.com/w3c/did-imp-guide/pull/12#discussion_r686215692) -...

Get a static version that can be voted on for publishing

5

see FPWD https://github.com/w3c/did-use-cases/ 1. run pubrules [1] using this link for the Rubric: https://labs.w3.org/spec-generator/?type=respec&url=https://w3c.github.io/did-imp-guide/?specStatus=FPWG-NOTE 2. fix any pubrules errors 3. run link checker: https://validator.w3.org/checklink 4. fix any broken links 5....

Ambiguity regarding PATH and DID URLs

20

This recent PR on the did web method highlights the challenges we introduced by reserving `PATH` in did URLs but not making any real use of it... in the core...

When should did parameters be dropped?

68

Consider: `did:example:123?q1=1&q2=2#fragment` => did document. should didDocument.id === `did:example:123?q1=1&q2=2` or `did:example:123` ? this is particularly concerning for interactions with the `initial-state` parameter used by sidetree and didcomm... if its dropped...

Address claiming inactive did methods

2

GitHub has a good policy on this, worth reading: https://docs.github.com/en/github/site-policy/github-username-policy > GitHub prohibits account name squatting, and account names may not be reserved or inactively held for future use. Accounts...

Originally raised in: https://github.com/w3c/did-spec-registries/pull/360#discussion_r744282634 We are not sure if there should be additional required fields associated with registry entries. Today, we require: "name", "identifier", "specification". Tomorrow, we might require contactEmail,...

Raising the quality bar for registry changes

9

@iherman I would like to require mandatory PR approvals from all codeowners before a PR can be merged, and have all editors listed as code owners in the repo. This...