From 59236b8cb23e4b26639987130b685fbe16ad900b Mon Sep 17 00:00:00 2001
From: Andy Seaborne <andy@apache.org>
Date: Thu, 16 Jan 2025 19:24:49 +0000
Subject: [PATCH 1/2] Make the IRI advice list be positive form advice

---
 spec/index.html | 37 ++++++++++++++++++-------------------
 1 file changed, 18 insertions(+), 19 deletions(-)

diff --git a/spec/index.html b/spec/index.html
index 004185e..bd5ead5 100644
--- a/spec/index.html
+++ b/spec/index.html
@@ -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>
+        <li>Only use percent-encoding of characters where 
+          necessary for IRI syntax.</li>
+        <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 ][RFC3492]].</li>
+        <li>Use IRIs in Unicode [=Normalization Form C=] [[I18N-Glossary]].</li>
       </ul>
     </div>
   </section>

From d9605a7d47d471ddceb6a35c00e95a0a1518e4ff Mon Sep 17 00:00:00 2001
From: Andy Seaborne <andy@apache.org>
Date: Thu, 16 Jan 2025 21:14:03 +0000
Subject: [PATCH 2/2] Update punycode RFC reference

---
 spec/index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/spec/index.html b/spec/index.html
index bd5ead5..68e15e2 100644
--- a/spec/index.html
+++ b/spec/index.html
@@ -666,7 +666,7 @@ <h3>IRIs</h3>
         <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 ][RFC3492]].</li>
+          in IRIs [[RFC5890]].</li>
         <li>Use IRIs in Unicode [=Normalization Form C=] [[I18N-Glossary]].</li>
       </ul>
     </div>