Documentation for the URI encoding changes.

diff --git a/doc/design/pathnames/jar-pathnames.markdown b/doc/design/pathnames/jar-pathnames.markdown
--- a/doc/design/pathnames/jar-pathnames.markdown
+++ b/doc/design/pathnames/jar-pathnames.markdown
@@ -3,7 +3,7 @@
 
     Mark Evenson
     Created:  09 JAN 2010
-    Modified: 10 APR 2010
+    Modified: 26 NOV 2010
 
 Notes towards an implementation of "jar:" references to be contained
 in Common Lisp `PATHNAME`s within ABCL.
@@ -66,8 +66,7 @@
 Status
 ------
 
-As of svn r125??, all the above goals have been implemented and
-tested.
+All the above goals have been implemented and tested.
 
 
 Implementation
@@ -92,7 +91,8 @@
 Otherwise the the DEVICE PATHAME denotes the PATHNAME of the JAR file.
 
 The DEVICE PATHNAME list of enclosing JARs runs from outermost to
-innermost.
+innermost.  The implementaion currently limits this list to have at
+most two elements.
     
 The DIRECTORY component of a JAR PATHNAME should be a list starting
 with the :ABSOLUTE keyword.  Even though hierarchial entries in jar
diff --git a/doc/design/pathnames/url-pathnames.markdown b/doc/design/pathnames/url-pathnames.markdown
--- a/doc/design/pathnames/url-pathnames.markdown
+++ b/doc/design/pathnames/url-pathnames.markdown
@@ -3,7 +3,7 @@
 
     Mark Evenson
     Created:  25 MAR 2010
-    Modified: 11 APR 2010
+    Modified: 26 NOV 2010
 
 Notes towards an implementation of URL references to be contained in
 Common Lisp `PATHNAME` objects within ABCL.
@@ -18,10 +18,8 @@
 URL vs URI
 ----------
 
-We use the term URL to describe the URL Pathnames, even though RFC3986
-notes that its use should be obsolete because in the context of Common
-Lisp Pathnames all need a lookup mechanism to be resolved or they
-wouldn't be of much use.
+We use the term URL to describe the URL Pathnames, even though the
+corresponding encoding is more akin to RFC2396 encoding.
 
 Goals
 -----
@@ -34,7 +32,7 @@
 
 3.  Use URL schemes that are understood by the java.net.URL object.
 
-    A file specified by URL
+    Example of a Pathname specified by URL:
     
         #p"http://example.org/org/armedbear/systems/pgp.asd"
     
@@ -55,8 +53,7 @@
 
 9.  Enable the loading of ASDF2 systems referenced by a URL pathname.
 
-10.  The reserved URL characters (`~`, `/`, `?`, etc.) shall be
-encoded in the proper manner on construction of the Pathname.
+10.  Inputs to the 
 
 11.  The "file" scheme will continue to be represented by an
 "ordinary" Pathname.
@@ -119,4 +116,10 @@
 Status
 ------
 
-This design is a proposal.
+This design has been implemented.
+
+History
+-------
+
+26 NOV 2010 Changed implemenation to use URI encodings for "jar" and
+  "file" schemes.
