Proposed text for guidelines doc to implement Ian's suggestion

Here is some proposed text to accompany Ian's recent proposal for bringing the guidelines document into alignment with the URI syntax document.

Ian's proposal:

In 2.1.1 of draft-ietf-urlreg-guide-02.txt, Larry talks about '://' as a
"holy sequence" used by many schemes to indicate a top level (where
meaningful).  However, in section 3.0 of draft-fielding-uri-syntax-04, the
sequence '//' is reserved as a component of the "authority" element; IMHO
the definition of the authority element clarifies the issue of whether or
not it's appropriate to use '//'.  (That draft also separately defines the
use of ':', rather than rolling that in with '//'.)  
So, is there any objection to carrying the URI-draft reference over to the
URL guidelines draft?

Existing text for section 2.1.1 in draft-ietf-urlreg-guide-02.txt:

2.1.1 Use of initial "//" for top level

   Many proposed new URL schemes seem to use "://" as a kind of
   indicator that what follows is a URL.  However, the use of "//"
   indicates a "top level" for schemes that support relative
   URLs, and is not necessary (and just confusing) for schemes
   that have no relative forms.  URL schemes without relative
   forms (such as mailto, cid, mid) do not use an initial "//".


Proposed replacement for that text in draft-ietf-urlreg-guide-03.txt:

2.1.1 Improper of "//" following "<scheme>:"

   Contrary to some examples set in past years, the use of
   double slashes as the first component of the <scheme-specific-part>
   of a URL is not simply an artistic indicator that what follows is a
   URL:  Double slashes are used ONLY when the syntax of the URL's
   <scheme-specific-part> contains a hierarchical structure.  In such
   URLs, the use of double slashes indicates that what follows is the
   top hierarchical element for a naming authority.  (See section 3 of
   RFC [URI-SYNTAX] for more details.) URL schemes which do
   not contain a hierarchical structure in their <scheme-specific-part>
   should not use double slashes following the "<scheme>:" string.

Comments?
Rich Petke