Skip to content

Clarify DID document term definition throughout spec #915

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.

Sign up for GitHub

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

Open
wip-abramson wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Clarify DID document term definition throughout spec #915

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
77daa15
update did-core to did
wip-abramson Feb 25, 2025
3a8d90a
Merge remote-tracking branch 'upstream/main' into fix-editor-draft-links
wip-abramson Jan 9, 2026
e5d288f
remove language around DID document describing a DID subject
wip-abramson Jan 9, 2026
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
12 changes: 7 additions & 5 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -857,9 +857,10 @@ <h2>Terminology</h2>
<dt><dfn class="export" data-lt="DID documents">DID document</dfn></dt>

<dd>
A set of data describing the [=DID subject=], including mechanisms, such as
cryptographic public keys, that the [=DID subject=] or a [=DID delegate=] can
use to [=authentication|authenticate=] itself and prove its association with the
A set of data that enables cryptographically verifiable interactions with a
[=DID subject=]. This includes mechanisms, such as cryptographic public keys,
that a [=DID subject=] or a [=DID delegate=] can use to
[=authentication|authenticate=] itself and prove its association with a
[=DID=]. A DID document might have one or more different [=representations=] as
defined in <a href="#representations"></a> or in the W3C [[[DID-EXTENSIONS]]].
</dd>
Expand Down Expand Up @@ -994,7 +995,8 @@ <h2>Terminology</h2>
resource, in a format that can be readily communicated via the protocol. A
representation consists of a set of representation metadata and a potentially unbounded
stream of representation data." A [=DID document=] is a representation of
information describing a [=DID subject=]. See <a href="#representations"></a>.
information which enables cryptographically verifiable interactions with a
[=DID subject=]. See <a href="#representations"></a>.
</dd>

<dt><dfn data-lt="representation-specific entry|non-representation-specific
Expand Down Expand Up @@ -3991,7 +3993,7 @@ <h2>Referring to the DID document</h2>
the [=DID subject=] and does not have a [=URI=] separate from the
[=DID=]. Rather the [=DID document=] is an artifact of [=DID
resolution=] controlled by the [=DID controller=] for the purpose of
describing the [=DID subject=].
enabling cryptographically verifiable interactions with a [=DID subject=].
</p>
<p>
This distinction is illustrated by the graph model shown below.
Expand Down