Skip to content

Conversation

msporny
Copy link
Member

@msporny msporny commented Aug 31, 2024

This PR is an attempt to address issue #45 by noting that no assumptions are to be made about a controller being a single individual nor only controlling a single verification method.


Preview | Diff

index.html Outdated
Comment on lines 676 to 703
While the identifier used for a [=controller=] is unique, that uniqueness does
not imply that a single individual is always the controller, nor does it imply
that the controller might not be associated by multiple identifiers. A
[=controller=] might be a single individual, or a collection of individuals,
such as a corporation. A [=controller=] might also use multiple identifiers
to refer to itself, for purposes such as privacy or delineating operational
boundaries within an organization. Similarly, a [=controller=] might control
many [=verification methods=] and so no assumptions are to be made about
a [=controller=] being a single individual nor only controlling a single
[=verification method=].
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
While the identifier used for a [=controller=] is unique, that uniqueness does
not imply that a single individual is always the controller, nor does it imply
that the controller might not be associated by multiple identifiers. A
[=controller=] might be a single individual, or a collection of individuals,
such as a corporation. A [=controller=] might also use multiple identifiers
to refer to itself, for purposes such as privacy or delineating operational
boundaries within an organization. Similarly, a [=controller=] might control
many [=verification methods=] and so no assumptions are to be made about
a [=controller=] being a single individual nor only controlling a single
[=verification method=].
While the identifier used for a [=controller=] is unique, that uniqueness does
not imply that a single entity is always the controller, nor does it imply
that the controller might not be associated by multiple identifiers. A
[=controller=] might be a single entity, or a collection of entities,
such as a corporation. A [=controller=] might also use multiple identifiers
to refer to itself, for purposes such as privacy or delineating operational
boundaries within an organization. Similarly, a [=controller=] might control
many [=verification methods=] and so no assumptions are to be made about
a [=controller=] being a single entity nor only controlling a single
[=verification method=].

Controllers also need not be persons - hence "entity" is a better word than "individual"

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I applied this in another commit due to @David-Chadwick's changes conflicting w/ these changes.

Copy link
Contributor

@David-Chadwick David-Chadwick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Subject to editorial changes.

@msporny msporny force-pushed the msporny-controllers-and-keys branch from d56184f to 5ba6f8e Compare September 6, 2024 20:59
Co-authored-by: David Chadwick <d.w.chadwick@truetrust.co.uk>
@msporny
Copy link
Member Author

msporny commented Sep 6, 2024

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

@msporny msporny merged commit deba49a into main Sep 6, 2024
1 check passed
@msporny msporny deleted the msporny-controllers-and-keys branch September 6, 2024 21:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

editorial This item is editorial in nature.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants