@@ -1590,20 +1590,20 @@
DID Controller
1590
1590
< h3 > Identifier Restrictionsh3 >
1591
1591
< p >
1592
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.
1593
+ Controller=] cannot use query parameters or fragment identifiers.
1594
1594
Implementers are urged to pay particular attention to the list of allowable
1595
1595
characters in Section [[[#did-syntax]]] which makes this requirement clear; the
1596
1596
syntax does not include the `?` character nor the `#` character. This is in
1597
1597
contrast to identifiers used in a [=DID document=] to identify a [=verification
1598
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
1599
+ [[[#did-url-syntax]]], which do allow the use of query parameters and fragment
1600
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
1601
+ identifiers made for [=DID=] ecosystems is discouraged as it can increase the
1602
1602
complexity of [=DID resolution=] software and potentially lead to a larger
1603
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=].
1604
+ within a particular [=DID document=] and implementers are discouraged from
1605
+ reusing them to refer to different [=resources=] over time , such as two
1606
+ different [=verification methods=] within the same [=DID document=].
1607
1607
p >
1608
1608
section >
1609
1609
0 commit comments