Skip to content

Export terms from DID Core #913

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
ottomorac wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Export terms from DID Core #913

Changes from 3 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
b301772
export out terms from DID Core
ottomorac Dec 8, 2025
8939adc
export out terms from DID Core
ottomorac Dec 8, 2025
8a14c5b
export out terms from DID Core
ottomorac Dec 9, 2025
c1c9766
Update index.html
ottomorac Dec 11, 2025
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
24 changes: 12 additions & 12 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -841,7 +841,7 @@ <h2>Terminology</h2>
subject</a>.
</dd>

<dt><dfn>DID delegate</dfn></dt>
<dt><dfn class="export">DID delegate</dfn></dt>

<dd>
An entity to whom a [=DID controller=] has granted permission to use a
Expand All @@ -864,14 +864,14 @@ <h2>Terminology</h2>
defined in <a href="#representations"></a> or in the W3C [[[DID-EXTENSIONS]]].
</dd>

<dt><dfn data-lt="DID fragments">DID fragment</dfn></dt>
<dt><dfn class="export" data-lt="DID fragments">DID fragment</dfn></dt>

<dd>
The portion of a [=DID URL=] that follows the first hash sign character
(<code>#</code>). DID fragment syntax is identical to URI fragment syntax.
</dd>

<dt><dfn class="export" data-lt="DID methods">DID method</dfn></dt>
<dt><dfn class="export" data-lt="DID methods|DID method's">DID method</dfn></dt>

<dd>
A definition of how a specific [=DID method scheme=] is implemented. A DID method is
Expand All @@ -880,7 +880,7 @@ <h2>Terminology</h2>
and deactivated. See <a href="#methods"></a>.
</dd>

<dt><dfn data-lt="DID paths">DID path</dfn></dt>
<dt><dfn class="export" data-lt="DID paths">DID path</dfn></dt>

<dd>
The portion of a [=DID URL=] that begins with and includes the first forward
Expand All @@ -890,7 +890,7 @@ <h2>Terminology</h2>
See <a href="#path"></a>.
</dd>

<dt><dfn data-lt="DID queries">DID query</dfn></dt>
<dt><dfn class="export" data-lt="DID queries">DID query</dfn></dt>

<dd>
The portion of a [=DID URL=] that follows and includes the first question
Expand All @@ -908,15 +908,15 @@ <h2>Terminology</h2>
defined in [[?DID-RESOLUTION]].
</dd>

<dt><dfn class="export" data-lt="DID resolvers">DID resolver</dfn></dt>
<dt><dfn class="export" data-lt="DID resolvers|DID resolver's">DID resolver</dfn></dt>

<dd>
A [=DID resolver=] is a software and/or hardware component that performs the
[=DID resolution=] function by taking a [=DID=] as input and producing a
conforming [=DID document=] as output.
</dd>

<dt><dfn data-lt="DID schemes|DID method scheme">DID scheme</dfn></dt>
<dt><dfn class="export" data-lt="DID schemes|DID method scheme">DID scheme</dfn></dt>

<dd>
The formal syntax of a [=decentralized identifier=]. The generic DID scheme
Expand All @@ -927,15 +927,15 @@ <h2>Terminology</h2>
the second colon, e.g., <code>did:example:</code>
</dd>

<dt><dfn data-lt="DID subjects">DID subject</dfn></dt>
<dt><dfn class="export" data-lt="DID subjects">DID subject</dfn></dt>

<dd>
The entity identified by a [=DID=] and described by a [=DID document=].
Anything can be a DID subject: person, group, organization, physical thing,
digital thing, logical thing, etc.
</dd>

<dt><dfn data-lt="DID URLs">DID URL</dfn></dt>
<dt><dfn class="export" data-lt="DID URLs|DID URL">DID URL</dfn></dt>

<dd>
A [=DID=] plus any additional syntactic component that conforms to the
Expand All @@ -945,7 +945,7 @@ <h2>Terminology</h2>
(with its leading <code>#</code> character).
</dd>

<dt><dfn>DID URL dereferencing</dfn></dt>
<dt><dfn class="export">DID URL dereferencing</dfn></dt>

<dd>
The process that takes as its input a [=DID URL=] and a set of input
Expand All @@ -960,7 +960,7 @@ <h2>Terminology</h2>
[[?DID-RESOLUTION]].
</dd>

<dt><dfn data-lt="DID URL dereferencers">DID URL dereferencer</dfn></dt>
<dt><dfn class="export" data-lt="DID URL dereferencers">DID URL dereferencer</dfn></dt>

<dd>
A software and/or hardware system that performs the [=DID URL dereferencing=]
Expand Down Expand Up @@ -1014,7 +1014,7 @@ <h2>Terminology</h2>
services, file storage services, and verifiable credential repository services.
</dd>

<dt><dfn data-lt="service endpoints">service endpoint</dfn></dt>
<dt><dfn class="export" data-lt="did service endpoints" data-local-lt="service endpoint">did service endpoint</dfn></dt>
Copy link
Contributor

@wip-abramson wip-abramson Dec 11, 2025

Choose a reason for hiding this comment

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

Why has this changed to "did service endpoint"?

Copy link
Author

@ottomorac ottomorac Dec 11, 2025

Choose a reason for hiding this comment

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

Thanks Will. As mentioned in the call, "service endpoint" is too generic and might conflict with other specs. One suggestion would be "did service endpoint", whilst still keeping a local alias within the spec for "service endpoint".


<dd>
A network address, such as an HTTP URL, at which [=services=] operate on
Expand Down