Skip to content

Conversation

@ottomorac
Copy link

@ottomorac ottomorac commented Dec 8, 2025

In order to address w3c/did-resolution#232 we will first need to export out some terms from DID Core as well as add some aliases for some of the terms. After this PR is merged, the changes in DID resolution to remove duplicate terms can be done.


Preview | Diff

</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

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

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".

@w3cbot
Copy link

w3cbot commented Dec 11, 2025

This was discussed during the #did meeting on 11 December 2025.

View the transcript

w3c/did#913

otto: This PR is attempting to solve issue about duplicate terms between DID Core and DID Resolution, before we do the PR for DID Resolution, we need to export some terms from DID Core to make it possible to refer to them in DID Resolution. Proposed terms, most of them use DID prefix so they won't conflict, but there are some (resources/services that could work w/ local alias) . Just trying to export terms, once this PR is merged, there will be another PR

for DID Resolution.

Wip: Service endpoint is too generic?

otto: Could avoid conflits by using DID Service Endpoint.

manu: there is a way to deconflict the terms when using them (specify which spec they come from)
… we are contemplating reusing "serviceEndpoint" in CID

<Zakim> JoeAndrieu, you wanted to mention CIDs

manu: so I would not make it specific to DIDs.
… But this looks like a good PR, I will review it.

JoeAndrieu: We should also look at CID spec and see what we need to synchronize there -- service endpoint might not be owned by DID. We can't change CID spec. We should figure out impact.


Co-authored-by: Will Abramson <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants