Enhance DAP Resolution Endpoint to Support Multi-Domain Registries

[frankhinek]

Context

The DAP Resolution endpoint is currently specified as:

<serviceEndpoint>/daps/<local-handle>

This specification limits the ability of a single DAP registry to provide resolution services for multiple domains. As the DAP ecosystem grows, there's an increasing need for flexibility, particularly in scenarios where service providers aim to offer DAP Registry as a Service.

Proposed Change

This proposal would expand the DAP Resolution endpoint to:

<serviceEndpoint>/daps/<local-handle>/<domain>

It also requires that DAP registry implementations store the domain in a column / field to allow for querying.

This modification would enable a single DAP Registry instance to resolve DAPs for multiple domains.

Benefits

1. Improved Scalability: Service providers can manage multiple domains through a single registry instance, reducing infrastructure complexity and costs.
2. Enhanced Flexibility: Organizations can offer white-label DAP registry services, allowing clients to maintain their domain identity while leveraging shared infrastructure.
3. Future-Proofing: This change accommodates potential future scenarios where domain-specific handling might be necessary within a single registry.

Next Steps

1. Gather feedback from the community on this proposed change.
2. Draft and open a PR to update the DAP specification.
3. Coordinate with SDK maintainers to implement the changes.
4. Modify existing registry implementations to accommodate the updated endpoint.

Tracker

If adopted, this issue can be closed when the following have been updated with the changes to the endpoint:

Spec:

• https://github.com/TBD54566975/dap

SDKs:

• https://github.com/TBD54566975/dap-dart
• https://github.com/TBD54566975/dap-go
• https://github.com/TBD54566975/dap-kt
• https://github.com/TBD54566975/dap-js

Registries:

• https://github.com/TBD54566975/dap-registry-static
• https://github.com/TBD54566975/dap-registry-js