Skip to content

Conversation

peacekeeper
Copy link
Collaborator

@peacekeeper peacekeeper commented Jul 19, 2025

I think we can remove the "Future Work" section, since there hasn't been much content, and corresponding issues have been closed and/or moved to DID Extensions.


Preview | Diff

@ChristopherA
Copy link

I’m fine with these suggested future work items being moved to extensions.

@w3cbot
Copy link

w3cbot commented Jul 24, 2025

This was discussed during the #did meeting on 24 July 2025.

View the transcript

Remove "Future Work" section #170

w3c/did-resolution#170

Suggestion from Markus to remove this section from the spec since we haven’t had much suggestions and corresponding issues have been closed and/or moved to DID Extensions

ottomorac: this seems to have general agreement

markus_sabadello: it just made sense to me. There were three topics: JSON Pointers, Introducing Proxy Service and Introducing redirection functions.
… Those discussions, we moved these things to extensions
… Unless we want a list of future extensions, we can just remove this
… But I'm not sure we should have such a list

<ivan> +1 to remove this

<JoeAndrieu> +1 to remove

<pchampin> +1


@peacekeeper
Copy link
Collaborator Author

Merging after approvals.

@peacekeeper peacekeeper merged commit 60a17e3 into gh-pages Jul 29, 2025
2 checks passed
@peacekeeper peacekeeper deleted the peacekeeper-remove-future-work branch July 29, 2025 22:41
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.

5 participants