Skip to content
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

Relationship between controller property and DID controller #326

Merged
merged 1 commit into from
Jul 3, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 14 additions & 3 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -1830,10 +1830,8 @@ <h2>

<p>
A DID document MAY include a <code>controller</code> property to indicate
that there are <a>DID controller(s)</a> other than the <a>DID subject</a>.
If so:
the <a>DID controller(s)</a>. If so:
</p>

<dl>
<dt><dfn>controller</dfn></dt>
<dd>
Expand All @@ -1844,6 +1842,19 @@ <h2>
</dd>
</dl>

<p class="note" title="Determining the DID controller">
If the <code>controller</code> property is not present, the
<a>DID controller</a> can be determined by consulting the respective
<a>DID method</a> specification. It cannot be assumed that the
<a>DID subject</a> is also the controller of its own <a>DID</a>, nor
can it be assumed that <em>only</em> entities identified by <a>DIDs</a>
present in the value of <code>controller</code> are capable of exerting
control over the <a>DID</a> in question. Similarly, <a>DID methods</a> are not
obliged to respect the value of <code>controller</code> and can specify means
for updating the <a>DID document</a> that are unrelated to the
<code>controller</code> property.
</p>

<p>
Each <a>DID method</a> MUST define how authorization and delegation are
implemented, including any necessary cryptographic operations.
Expand Down