Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix editorial issues in The Role of Human-Friendly Identifiers section. #744

Merged
merged 2 commits into from
May 29, 2021
Merged

Fix editorial issues in The Role of Human-Friendly Identifiers section. #744

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d662550
Fix editorial issues in The Role of Human-Friendly Identifiers section.
msporny May 22, 2021
cebb246
Apply suggestions to Human-Friendly Identifiers section from @dlongley.
msporny May 29, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 8 additions & 11 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4456,10 +4456,11 @@ <h2>The Role of Human-Friendly Identifiers</h2>
<p>
<a>DIDs</a> achieve global uniqueness without the need for a central
registration authority. This comes at the cost of human memorability.
The algorithms capable of generating globally unique identifiers
produce random strings of characters that have no human meaning (see also
Algorithms capable of generating globally unambiguous identifiers
produce random strings of characters that have no human meaning. This
trade-off is often referred to as
<a href="https://en.wikipedia.org/wiki/Zooko%27s_triangle">Zooko's
Triangle</a>).
Triangle</a>.
</p>

<p>
Expand All @@ -4468,14 +4469,14 @@ <h2>The Role of Human-Friendly Identifiers</h2>
name, a domain name, or a conventional address for a <a>DID controller</a>,
such as a mobile telephone number, email address, social media username, or
blog URL. However, the problem of mapping human-friendly identifiers to
<a>DIDs</a> (and doing so in a way that can be verified and trusted) is
<a>DIDs</a>, and doing so in a way that can be verified and trusted, is
outside the scope of this specification.
</p>

<p>
Solutions to this problem should be defined in separate specifications that
reference this specification. It is strongly recommended that such
specifications carefully consider the:
Solutions to this problem are defined in separate specifications, such as
[[?DNS-DID]], that reference this specification. It is strongly recommended that
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this ? still needed? Saw @brentzundel remove it on a different PR.

Copy link
Member Author

@msporny msporny May 29, 2021 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it's still needed. The question mark means "non-normative" reference and given that DNS-DID isn't an official IETF RFC, we have to make sure we reference it in that way (or it will show up in the normative references section of the specification a trigger an objection from the Director).

such specifications carefully consider the:
</p>

<ul>
Expand All @@ -4489,10 +4490,6 @@ <h2>The Role of Human-Friendly Identifiers</h2>
</li>
</ul>

<p class="note">
A draft specification for discovering a <a>DID</a> from domain names and email
addresses using DNS lookups is available at [[?DNS-DID]].
</p>
</section>

<section>
Expand Down