Responded to PR review comments (round 2).

1. Used more meaningful tags in the documentation.
2. method names with "URN" in them have been camel-cased to use "Urn" instead.
3. A list of resources and a changelog has been added to the README.

Author: Matthew Lefavor

README.md

@@ -158,6 +158,9 @@ Documents specifying how URLs work:
 * [RFC 3986 - Uniform Resource Identifier (URI): Generic Syntax](http://tools.ietf.org/html/rfc3986)
 * [RFC 3987 - Internationalized Resource Identifiers (IRI)](http://tools.ietf.org/html/rfc3987)
 * [RFC 2732 - Format for Literal IPv6 Addresses in URL's](http://tools.ietf.org/html/rfc2732)
+* [RFC 2368 - The `mailto:` URL Scheme](https://www.ietf.org/rfc/rfc2368.txt)
+* [RFC 2141 - URN Syntax](https://www.ietf.org/rfc/rfc2141.txt)
+* [IANA URN Namespace Registry](http://www.iana.org/assignments/urn-namespaces/urn-namespaces.xhtml)
 * [Punycode: A Bootstring encoding of Unicode for Internationalized Domain Names in Applications (IDNA)](http://tools.ietf.org/html/rfc3492)
 * [application/x-www-form-urlencoded](http://www.w3.org/TR/REC-html40/interact/forms.html#form-content-type) (Query String Parameters) and [application/x-www-form-urlencoded encoding algorithm](http://www.whatwg.org/specs/web-apps/current-work/multipage/association-of-controls-and-forms.html#application/x-www-form-urlencoded-encoding-algorithm)
 * [What every web developer must know about URL encoding](http://blog.lunatech.com/2009/02/03/what-every-web-developer-must-know-about-url-encoding)
@@ -243,6 +246,7 @@ URI.js is published under the [MIT license](http://www.opensource.org/licenses/m
 
 ### master (will become 1.15.0)
 
+* URNs are now normalized based on the syntax given by [RFC 2141](https://www.ietf.org/rfc/rfc2141.txt)
 * fixing `URI(undefined)` to throw TypeError - ([Issue #189](https://github.com/medialize/URI.js/issues/189)) - tiny backward-compatibility-break
 
 ### 1.14.2 (February 25th 2015) ###

about-uris.html

@@ -50,16 +50,16 @@ <h2>Understanding URIs</h2>
     </p>
 
     <p>
-        URNs <i>name</i> a resource.
+        URNs <em>name</em> a resource.
         They are (supposed to) designate a globally unique, permanent identifier for that resource.
-        For example, the URN <code>urn:isbn:0201896834</code> uniquely identifies Volume 1 of Donald Knuth's <i>The Art of Computer Porgramming</i>.
+        For example, the URN <code>urn:isbn:0201896834</code> uniquely identifies Volume 1 of Donald Knuth's <em>The Art of Computer Porgramming</em>.
         Even if that book goes out of print, that URN will continue to identify that particular book in that particular printing.
-        While the term &quot;URN&quot; <i>technically</i> refers to a specific URI scheme laid out by <a href="http://tools.ietf.org/html/rfc2141">RFC 2141</a>,
+        While the term &quot;URN&quot; <em>technically</em> refers to a specific URI scheme laid out by <a href="http://tools.ietf.org/html/rfc2141">RFC 2141</a>,
         the previously-mentioned RFC 3986 indicates that in common usage &quot;URN&quot; refers to any kind of URI that identifies a resource.
     </p>
 
     <p>
-        URLs <i>locate</i> a resource.
+        URLs <em>locate</em> a resource.
         They designate a protocol to use when looking up the resource and provide an &quot;address&quot; for finding the resource within that scheme.
         For example, the URL <code><a href="http://tools.ietf.org/html/rfc3986">http://tools.ietf.org/html/rfc3986</a></code> tells the consumer (most likely a web browser)
         to use the HTTP protocol to access whatever site is found at the <code>/html/rfc3986</code> path of <code>tools.ietf.org</code>.
@@ -71,17 +71,16 @@ <h2>Understanding URIs</h2>
     <h2>URLs and URNs in URI.js</h2>
 
     <p>
-        The distinction between URLs and URNs is one of semantics.
+        The distinction between URLs and URNs is one of <strong>semantics</strong>.
         In principle, it is impossible to tell, on a purely syntactical level, whether a given URI is a URN or a URL without knowing more about its scheme.
-        Practically speaking, however, URIS that look like HTTP URLs (scheme is followed by a colon and two slashes, URI has an authority component, and paths are delimited by slashes) tend to be URLs,
+        Practically speaking, however, URIs that look like HTTP URLs (scheme is followed by a colon and two slashes, URI has an authority component, and paths are delimited by slashes) tend to be URLs,
         and URIs that look like RFC 2141 URNs (scheme is followed by a colon, no authority component, and paths are delimited by colons) tend to be URNs (in the broad sense of &quot;URIs that name&quot;).
     </p>
 
     <p>
-        So, for the purposes of URI.js, the distinction between URLs and URNs is treated as one of syntax.
-        The main functional differences between the two are that
-            1) URNs will not have an authority element and
-            2) when breaking the path of the URI into segments, the colon will be used as the delimiter rather than the slash.
+        So, for the purposes of URI.js, the distinction between URLs and URNs is treated as one of <strong>syntax</strong>.
+        The main functional differences between the two are that (1) URNs will not have an authority element and
+        (2) when breaking the path of the URI into segments, the colon will be used as the delimiter rather than the slash.
         The most surprising result of this is that <code>mailto:</code> URLs will be considered by URI.js to be URNs rather than URLs.
         That said, the functional differences will not adversely impact the handling of those URLs.
     </p>

src/URI.js

@@ -407,7 +407,7 @@
 
   for (_part in _parts) {
     URI[_part + 'PathSegment'] = generateAccessor('pathname', _parts[_part]);
-    URI[_part + 'URNPathSegment'] = generateAccessor('urnpath', _parts[_part]);
+    URI[_part + 'UrnPathSegment'] = generateAccessor('urnpath', _parts[_part]);
   }
 
   var generateSegmentedPathFunction = function(_sep, _codingFuncName, _innerCodingFuncName) {
@@ -435,11 +435,11 @@
     };
   };
 
-  // This takes place outside the above loop because we don't want, e.g., encodeURNPath functions.
+  // This takes place outside the above loop because we don't want, e.g., encodeUrnPath functions.
   URI.decodePath = generateSegmentedPathFunction('/', 'decodePathSegment');
-  URI.decodeURNPath = generateSegmentedPathFunction(':', 'decodeURNPathSegment');
+  URI.decodeUrnPath = generateSegmentedPathFunction(':', 'decodeUrnPathSegment');
   URI.recodePath = generateSegmentedPathFunction('/', 'encodePathSegment', 'decode');
-  URI.recodeURNPath = generateSegmentedPathFunction(':', 'encodeURNPathSegment', 'decode');
+  URI.recodeUrnPath = generateSegmentedPathFunction(':', 'encodeUrnPathSegment', 'decode');
 
   URI.encodeReserved = generateAccessor('reserved', 'encode');
 
@@ -998,10 +998,10 @@
   p.pathname = function(v, build) {
     if (v === undefined || v === true) {
       var res = this._parts.path || (this._parts.hostname ? '/' : '');
-      return v ? (this._parts.urn ? URI.decodeURNPath : URI.decodePath)(res) : res;
+      return v ? (this._parts.urn ? URI.decodeUrnPath : URI.decodePath)(res) : res;
     } else {
       if (this._parts.urn) {
-        this._parts.path = v ? URI.recodeURNPath(v) : '';
+        this._parts.path = v ? URI.recodeUrnPath(v) : '';
       } else {
         this._parts.path = v ? URI.recodePath(v) : '/';
       }
@@ -1733,7 +1733,7 @@
     }
 
     if (this._parts.urn) {
-      this._parts.path = URI.recodeURNPath(this._parts.path);
+      this._parts.path = URI.recodeUrnPath(this._parts.path);
       this.build(!build);
       return this;
     }

test/test.js

@@ -1587,7 +1587,7 @@
 
     equal(URI.decodeQuery('%%20'), '%%20', 'malformed URI component returned');
     equal(URI.decodePathSegment('%%20'), '%%20', 'malformed URI component returned');
-    equal(URI.decodeURNPathSegment('%%20'), '%%20', 'malformed URN component returned');
+    equal(URI.decodeUrnPathSegment('%%20'), '%%20', 'malformed URN component returned');
   });
   test('encodeQuery', function() {
     var escapeQuerySpace = URI.escapeQuerySpace;