Add Use Cases and Requirements

w3c / controller-document

Controller Documents

https://w3c.github.io/controller-document/

Other

5 stars 7 forks source link

Add Use Cases and Requirements #103

Closed msporny closed 1 month ago

msporny commented 1 month ago

This PR is an attempt to partially address issue #93 and #94 by adding a Use Cases and Requirements section.

/cc @jyasskin and @hadleybeeman

Preview | Diff

iherman commented 1 month ago

The issue was discussed in a meeting on 2024-10-16

no resolutions were taken

View the transcript

#### 4.1. Add Use Cases and Requirements (pr controller-document#103) _See github pull request [controller-document#103](https://github.com/w3c/controller-document/pull/103)._ **Manu Sporny:** controller doc and did document provide different solutions to ownership. … did document has twice as many use cases as controller doc.

msporny commented 1 month ago

@iherman wrote:

All the use case seem to be (mostly) around identifiers, making it more explicit by the reference to the DID use cases. It does not really justify the usage in VCs. I believe such use case would be important with, if possible, a reference to the VC use cases as well

Done in 6ad135b7aac59637b0818de7db5108e0a12028b7.

We have a bunch of terms defined for referencing crypto keys, must notably Multikeys and JSONWebKeys. Something in the use cases should justify the creation of those here.

Done in 8dac97593e78a8efd5ac910e3c5189276d20b710.

msporny commented 1 month ago

Editorial, multiple reviews, changes requested and made, no objections, merging.