Remove `hl` (hashlink) parameter #262

msporny · 2025-12-18T15:25:17Z

This PR is an attempt to address issue #229 and #209 by removing the hashlink parameter from the specification.

Merge PR #261 before merging this PR.

TallTed · 2025-12-18T23:39:21Z

index.html

-			(e.g., `contentType`, proof, versioning) which an application can use to validate a user's cryptographic keys, 
-			service endpoints, or status. 
+			By invoking a <a>DID resolver</a> using the standard <code>resolve(did, resolutionOptions)</code> interface (as defined in
+			the <a href="#resolving">DID Resolution section</a>) one can obtain a <a>DID document</a> and accompanying metadata


Suggested change

the <a href="#resolving">DID Resolution section</a>) one can obtain a <a>DID document</a> and accompanying metadata

the <a href="#resolving">DID Resolution section</a>), one can obtain a <a>DID document</a> and accompanying metadata

TallTed · 2025-12-18T23:40:56Z

index.html

+			For example, a wallet app could resolve <code>did:example:123?versionTime=2021-05-10T17:00:00Z</code>
+			using the `versionTime` parameter to retrieve the state of that DID at a past time, or a client could
+			dereference a DID URL
+			 like <code>did:example:123?service=files&relativeRef=/resume.pdf</code>
+			 (see <a href="#example-dereferencing-to-service-endpoint-url">here for detailed example</a>)
+			 to fetch a user's resume stored via a service declared in the DID document.


Suggested change

For example, a wallet app could resolve <code>did:example:123?versionTime=2021-05-10T17:00:00Z</code>

using the `versionTime` parameter to retrieve the state of that DID at a past time, or a client could

dereference a DID URL

like <code>did:example:123?service=files&relativeRef=/resume.pdf</code>

(see <a href="#example-dereferencing-to-service-endpoint-url">here for detailed example</a>)

to fetch a user's resume stored via a service declared in the DID document.

For example, a wallet app could resolve `did:example:123?versionTime=2021-05-10T17:00:00Z`

using the `versionTime` parameter to retrieve the state of that DID at a past time, or a client could

dereference a DID URL

like `did:example:123?service=files&relativeRef=/resume.pdf`

(see <a href="#example-dereferencing-to-service-endpoint-url">here for detailed example</a>)

to fetch a user's resume stored via a service declared in the DID document.

TallTed · 2025-12-18T23:41:18Z

index.html

-			the <a href="#resolving">DID Resolution section</a>) one can obtain a <a>DID document</a> and accompanying metadata 
-			(e.g., `contentType`, proof, versioning) which an application can use to validate a user's cryptographic keys, 
-			service endpoints, or status. 
+			By invoking a <a>DID resolver</a> using the standard <code>resolve(did, resolutionOptions)</code> interface (as defined in


Suggested change

By invoking a <a>DID resolver</a> using the standard <code>resolve(did, resolutionOptions)</code> interface (as defined in

By invoking a <a>DID resolver</a> using the standard `resolve(did, resolutionOptions)` interface (as defined in

TallTed · 2025-12-18T23:41:45Z

index.html

-			service endpoints, or status. 
+			By invoking a <a>DID resolver</a> using the standard <code>resolve(did, resolutionOptions)</code> interface (as defined in
+			the <a href="#resolving">DID Resolution section</a>) one can obtain a <a>DID document</a> and accompanying metadata
+			(e.g., `contentType`, proof, versioning) which an application can use to validate a user's cryptographic keys,


Suggested change

(e.g., `contentType`, proof, versioning) which an application can use to validate a user's cryptographic keys,

(e.g., `contentType`, proof, versioning), which an application can use to validate a user's cryptographic keys,

TallTed · 2025-12-18T23:43:16Z

index.html

-			normative MUSTs and error conditions (such as invalid DIDs, deactivated DIDs, unsupported methods, 
-			relative URL expansion, etc.) to ensure that client applications can reliably depend on correct resolution behavior 
+			Further, the specification's <a href="#dereferencing-algorithm">DID URL dereferencing algorithm</a> shows how
+			a client can follow a fragment (e.g., <code>#key-1</code>) to extract a particular verification method from


Suggested change

a client can follow a fragment (e.g., <code>#key-1</code>) to extract a particular verification method from

a client can follow a fragment (e.g., `#key-1`) to extract a particular verification method from

TallTed · 2025-12-18T23:43:54Z

index.html

 A decentralized address book: By using DIDs as identifiers for people and organizations
 within an address book, the controllers of those DIDs can independently update the contents of
-their DID documents. Through DID resolution these DIDs can be resolved to obtain the 
+their DID documents. Through DID resolution these DIDs can be resolved to obtain the


Suggested change

their DID documents. Through DID resolution these DIDs can be resolved to obtain the

their DID documents. Through DID resolution, these DIDs can be resolved to obtain the

TallTed · 2025-12-18T23:46:41Z

index.html

+Within the credential, if issuers and holders are identified using a DID, the verifier can
 use DID resolution to resolve the DID documents of the identified issuer and holder to obtain
 the verification material necessary to verify the signatures on the Verifiable Presentation.


Suggested change

Within the credential, if issuers and holders are identified using a DID, the verifier can

use DID resolution to resolve the DID documents of the identified issuer and holder to obtain

the verification material necessary to verify the signatures on the Verifiable Presentation.

By using DIDs to identify issuers and holders within a credential, an issuer enables a verifier to

use DID resolution to resolve the DID documents of the identified issuers and holders to obtain

the verification material necessary to verify the signatures on the Verifiable Presentation.

TallTed · 2025-12-18T23:47:28Z

index.html

-at a specific point in time or for a specific version. This can be used to audit the historical 
-verifiable actions of a DID controller. For example, the issuance of a verifiable receipt or the 
+at a specific point in time or for a specific version. This can be used to audit the historical
+verifiable actions of a DID controller. For example, the issuance of a verifiable receipt or the


Suggested change

verifiable actions of a DID controller. For example, the issuance of a verifiable receipt or the

verifiable actions of a DID controller; for example, the issuance of a verifiable receipt or the

TallTed · 2025-12-18T23:48:20Z

index.html

 			</li>
 			<li>
 DID URL based resource retrieval: A DID controller can add service endpoints to their DID document
 that point to resources they control, for example a profile picture. By referencing these resources


Suggested change

that point to resources they control, for example a profile picture. By referencing these resources

that point to resources they control; for example, a profile picture. If DID URLs are used to reference

TallTed · 2025-12-18T23:50:08Z

index.html

+using a DID URL, a web application can use DID resolution and DID URL dereferencing to retrieve the
 current version of the resource. The DID URL can act as a persistent, dereferencable identifier
 for this resource, while the DID controller can independently change the resource over time.


Suggested change

using a DID URL, a web application can use DID resolution and DID URL dereferencing to retrieve the

current version of the resource. The DID URL can act as a persistent, dereferencable identifier

for this resource, while the DID controller can independently change the resource over time.

these resources, web applications can use DID resolution and DID URL dereferencing to retrieve the

current version of the resource(s). The DID URL can be used as a persistent, dereferenceable identifier

for these resources, while the DID controller can independently change the resource over time.

msporny added 2 commits December 18, 2025 10:19

Remove trailing spaces.

31f78b5

Remove hl parameter from specification.

01b19d2

msporny requested review from ChristopherA, danpape, dmitrizagidulin, mccown and peacekeeper as code owners December 18, 2025 15:25

This was referenced Dec 18, 2025

Address reference to internet draft [HASHLINK] #229

Open

Specify the algorithm for processing the hl DID parameter. #209

Open

TallTed reviewed Dec 18, 2025

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Remove `hl` (hashlink) parameter #262

Remove `hl` (hashlink) parameter #262

Uh oh!

msporny commented Dec 18, 2025 •

edited by pr-preview bot

Loading

Uh oh!

TallTed Dec 18, 2025

Uh oh!

TallTed Dec 18, 2025

Uh oh!

TallTed Dec 18, 2025

Uh oh!

TallTed Dec 18, 2025

Uh oh!

TallTed Dec 18, 2025

Uh oh!

TallTed Dec 18, 2025

Uh oh!

TallTed Dec 18, 2025

Uh oh!

TallTed Dec 18, 2025

Uh oh!

TallTed Dec 18, 2025 •

edited

Loading

Uh oh!

TallTed Dec 18, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

	the <a href="#resolving">DID Resolution section</a>) one can obtain a <a>DID document</a> and accompanying metadata
	the <a href="#resolving">DID Resolution section</a>), one can obtain a <a>DID document</a> and accompanying metadata

	By invoking a <a>DID resolver</a> using the standard <code>resolve(did, resolutionOptions)</code> interface (as defined in
	By invoking a <a>DID resolver</a> using the standard `resolve(did, resolutionOptions)` interface (as defined in

	(e.g., `contentType`, proof, versioning) which an application can use to validate a user's cryptographic keys,
	(e.g., `contentType`, proof, versioning), which an application can use to validate a user's cryptographic keys,

	a client can follow a fragment (e.g., <code>#key-1</code>) to extract a particular verification method from
	a client can follow a fragment (e.g., `#key-1`) to extract a particular verification method from

	their DID documents. Through DID resolution these DIDs can be resolved to obtain the
	their DID documents. Through DID resolution, these DIDs can be resolved to obtain the

	verifiable actions of a DID controller. For example, the issuance of a verifiable receipt or the
	verifiable actions of a DID controller; for example, the issuance of a verifiable receipt or the

	that point to resources they control, for example a profile picture. By referencing these resources
	that point to resources they control; for example, a profile picture. If DID URLs are used to reference

Remove hl (hashlink) parameter #262

Are you sure you want to change the base?

Remove hl (hashlink) parameter #262

Uh oh!

Conversation

msporny commented Dec 18, 2025 • edited by pr-preview bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

TallTed Dec 18, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Remove `hl` (hashlink) parameter #262

Remove `hl` (hashlink) parameter #262

msporny commented Dec 18, 2025 •

edited by pr-preview bot

Loading

TallTed Dec 18, 2025 •

edited

Loading