Skip to content

Dids & paths for human-readable URLs in a local-frist world #1210

Open

Description

@joepio

Initial atomic data was purely HTTP based, which also mean we often had nice, clean, human-readable URLs.

https://example.com/people/joep

But now we're migrating to did identifiers. Great that they rely on cryptography instead of trust, but they look like gibberish:

did:ad:awidonwaunsbg389n82n3tn1891

So would we still be able to share our did resources with a nice human-readable URL? Well, yeah I think we should.

We could introduce a new special path property, which we check for drive-scoped uniqueness, and we use that to resolve using HTTP.

If a user opens example.com/people/joep we find the path property and resolve it to the resource.

However, note that this requires one drive per domain. We could also add a drive-specific namespace in front of the path, or we could use a subdomain.

Activity

  1. changed the title [-]Dids & paths[/-] [+]Dids & paths for human-readable URLs in a local-frist world[/+] on Jun 2, 2026
  2. joepio commented on Sep 12, 2026

    @joepio
    MemberAuthor

    Backlog consolidation requested by the maintainer. Consolidating the older URL path-constraint proposal (#725) here. Preserve the question of semantic/human-readable paths and their relationship to class constraints and parent hierarchies. Current DID identity is separate from routing; closing the old proposal does not declare path policy implemented. Security/admission issue #556 remains open separately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions