DID resolution context is not accessible

[vmidyllic]

Fetching context from https://w3id.org/did-resolution/v1 gives 404. Is it expected?

[vmidyllic]

@peacekeeper maybe you can help

[wip-abramson]

Because the DID Resolution work has been taken on the by DID WG, the spec has moved locations along with the context.

The new location for the context is: https://w3c.github.io/did-resolution/contexts/did-resolution-v1.json

My guess is we need to update the w3id mapping to direct to this new location.

[peacekeeper]

I agree the w3id mapping should be updated..

And eventually I imagine we will probably have an "official" context URI such as https://www.w3.org/ns/did-resolution/v1 or something like that.

[dlongley]

Side(-ish) note: I recommend adopting a pattern of: <baseUrl>/v1rc<release candidate number> until the spec reaches PR (or perhaps right before it when tests are passing for enough implementations in CR). This makes it easier for software that is written while the standard progresses to keep functioning properly against some pre-finalized context version.

As a concrete example, it would be better for people to use:

https://w3id.org/did-resolution/v1rc1 (or whatever base URL is desirable here)

...until another release candidate comes out:

https://w3id.org/did-resolution/v1rc2

...repeating until PR (or right before):

https://w3id.org/did-resolution/v1

[msporny]

The redirect in w3id.org has been fixed, this URL works again:

https://w3id.org/did-resolution/v1

... though, it would be good if we used a URL structure as @dlongley suggests above.

[w3cbot]

This was discussed during the #did meeting on 09 January 2025.

View the transcript

w3c/did-resolution#78

wip: This is a bug.

markus_sabadello: There's a separate JSON-LD context for DID resolution. There's one for DID core, and one for CID.
… We define two additional data structures in DID resolution: result and dereferencing.
… The JSON-LD context needs to live somewhere and uses W3 URL which is not working.
… I don't know where to raise a PR or an issue or how to fix it.
… It also raises the question about what the final context URL should be.

pchampin: If I understand correctly, what is required is a pull request on w3id.org.
… It shouldn't be too hard, but I don't know if you have to be the owner.

manu: I'll submit the PR to w3id.org. There is another question about where it lives. It should probably live under ns.w3.org.
… I know in the VC working group that we had members that were adamant that it be in the W3C space.
… Do we use a w3id.org URL or w3.org?

aaron2: Do we need a decision before publication?

manu: We don't need to wait until it's a recommendation to fix it. Historically, groups and staff have preferred to wait until the recommendation is published before the URL is published.
… There's a halfway point where we've redirected that URL to GitHub Pages, which stays dynamic until the final version is published. There are options, each with benefits and drawbacks.
… I'm fixing the bug right now.

ivan: I think that what happened in the VC is that any context file etc. that is new is put on the W3C NS.
… Whether it's put there as a redirect or physically, it's immaterial.
… If there's already a deployment using w3id.org, we leave it there.
… In VC, we agreed that any new deployments use W3C NS.
… I would favour for new ones to put in W3C and add redirection like we do for similar URLs.
… I'm not against w3id but it raises eyebrows every time we use it.

<pchampin> +1 to what ivan said

manu: It's fixed.

---