Skip to content

Commit 6a8e0aa

Browse files
committed
Clarify restrictions on identifiers used in DID documents.
1 parent ffc61ef commit 6a8e0aa

File tree

1 file changed

+21
-0
lines changed

1 file changed

+21
-0
lines changed

index.html

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1586,6 +1586,27 @@

DID Controller

15861586

15871587
section>
15881588

1589+
<section>
1590+
<h3>Identifier Restrictionsh3>
1591+
<p>
1592+
Identifiers used in a [=DID document=] to identify a [=DID subject=] or a [=DID
1593+
Controller=] do not allow the use of query parameters or fragment identifiers.
1594+
Implementers are urged to pay particular attention to the list of allowable
1595+
characters in Section [[[#did-syntax]]] which makes this requirement clear; the
1596+
syntax does not include the `?` character nor the `#` character. This is in
1597+
contrast to identifiers used in a [=DID document=] to identify a [=verification
1598+
method=] or a [=service=], which follow the syntax rules in Section
1599+
[[[#did-url-syntax]]], which does allow the use of query parameters and fragment
1600+
identifiers. Even so, the use of query parameters in long-lived canonical
1601+
identifiers used in [=DID=] ecosystems is discouraged as it can increase the
1602+
complexity of [=DID resolution=] software and potentially lead to a larger
1603+
security attack surface. Fragment identifiers are also expected to be unique
1604+
within a particular [=DID document=] and are discouraged from being re-used
1605+
across time to refer to different [=resources=], such as two different
1606+
[=verification methods=] within the same [=DID document=].
1607+
p>
1608+
section>
1609+
15891610
section>
15901611

15911612
<section>

0 commit comments

Comments
 (0)