-
Notifications
You must be signed in to change notification settings - Fork 11
Note that controllers do not need to be single individuals. #83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
index.html
Outdated
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=]. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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"
There was a problem hiding this comment.
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.
There was a problem hiding this 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.
d56184f
to
5ba6f8e
Compare
Co-authored-by: David Chadwick <d.w.chadwick@truetrust.co.uk>
Editorial, multiple reviews, changes requested and made, no objections, merging. |
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