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

Make the IRI advice list be positive form advice #132

Merged
merged 2 commits into from
Jan 23, 2025
Merged

Make the IRI advice list be positive form advice #132

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
59236b8
Make the IRI advice list be positive form advice
afs Jan 16, 2025
d9605a7
Update punycode RFC reference
afs Jan 16, 2025
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
37 changes: 18 additions & 19 deletions spec/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -648,27 +648,26 @@ <h3>IRIs</h3>
Interoperability problems can be avoided by minting
only IRIs that are normalized according to
<a data-cite="rfc3987#section-5">Section 5</a>
of [[!RFC3987]]. Non-normalized forms that are best avoided
include the following:</p>
of [[!RFC3987]].
</p>

<ul>
<li>Uppercase characters in scheme names and domain names</li>
<li>Percent-encoding of characters where it is not
required by IRI syntax</li>
<li>Explicit inclusion of the HTTP default port
(<code>http://example.com:80/</code>);
<code>http://example.com/</code> is preferable</li>
<li>A completely empty path in an HTTP IRI
(<code>http://example.com</code>);
<code>http://example.com/</code> is preferable</li>
<li>“<code>/./</code>” or “<code>/../</code>” in the path
component of an IRI</li>
<li>Lowercase hexadecimal letters within percent-encoding
triplets (i.e., “<code>%3F</code>” is preferred over
“<code>%3f</code>”)</li>
<li>Punycode-encoding of Internationalized Domain Names
in IRIs [[RFC3492]]</li>
<li>IRIs that are not in Unicode [=Normalization Form C=] [[I18N-Glossary]]</li>
<li>Use lowercase characters in scheme names and domain names.</li>
afs marked this conversation as resolved.
Show resolved Hide resolved
<li>Only use percent-encoding of characters where
necessary for IRI syntax.</li>
afs marked this conversation as resolved.
Show resolved Hide resolved
<li>Omit the HTTP or HTTPS default port; <code>http://example/</code>
is preferred over <code>http://example:80/</code>.</li>
<li>Use uppercase hexadecimal letters within percent-encoding
triplets;"<code>%3F</code>" is preferred over
"<code>%3f</code>".</li>
<li>An empty path in an HTTP IRI
<code>http://example/</code> is preferred over
having no path <code>http://example</code>.</li>
<li>Normalize IRIs to remove "<code>/./</code>" and "<code>/../</code>" in the path
component of an IRI.</li>
<li>Avoid using punycode-encoding of Internationalized Domain Names
in IRIs [[RFC5890]].</li>
afs marked this conversation as resolved.
Show resolved Hide resolved
<li>Use IRIs in Unicode [=Normalization Form C=] [[I18N-Glossary]].</li>
</ul>
</div>
</section>
Expand Down
Loading