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

updated introduction to focus on verification of proofs #102

Closed
wants to merge 8 commits into from
37 changes: 29 additions & 8 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -296,9 +296,9 @@
<body>
<section id='abstract'>
<p>
A [=controller document=] is a set of data that specifies one or more
relationships between a [=controller=] and a set of data, such as a set of
public cryptographic keys.
A [=controller document=] contains cryptographic material and identifies
service endpoints that can be used to verify proofs from, and interact
with, the [=controller=] of an identifier.
</p>
</section>

Expand All @@ -309,11 +309,32 @@
<section class="informative">
<h2>Introduction</h2>
<p>
A [=controller document=] is a set of data that specifies one or more
relationships between a [=controller=] and a set of data, such as a set of
public cryptographic keys. The [=controller document=] contains [=verification
relationships=] that explicitly permit the use of certain [=verification
methods=] for specific purposes.
A [=controller document=] contains cryptographic material and identifies
service endpoints that can be used to verify proofs from, and interact
with, the [=controller=] of an identifier.
</p>
<p>
[=Controller documents=] enable the verification of proofs created
by the controller of an identifier. They provide [=verification methods=]
that express public cryptographic material, such as public keys, which
can be used to verify proofs created by the controller of the
identifier for specific purposes, such as
authentication, attestation, key agreement (for encryption), and capability invocation
and delegation.
</p>
<p>
Controller Documents can also identify [=services=] related to the identifier;
for example, a service from which to request additional information for
verification.
</p>
<p>
In other words, the
controller document contains the information necessary to communicate
with, and/or prove that specific actions were taken by, the controller
of an identifier,
including material for
cryptographic proofs and service endpoints for additional
communications.
</p>
<p>
It is expected that other specifications, such as [[[?DID-CORE]]], will profile
Expand Down