< prev index next >

src/java.base/share/classes/java/net/URI.java

Print this page 

        
*** 81,95 ****
   *
   * <p> An <i>opaque</i> URI is an absolute URI whose scheme-specific part does
   * not begin with a slash character ({@code '/'}).  Opaque URIs are not
   * subject to further parsing.  Some examples of opaque URIs are:
   *
!  * <blockquote><table cellpadding=0 cellspacing=0 summary="layout">
!  * <tr><td>{@code mailto:java-net@java.sun.com}<td></tr>
!  * <tr><td>{@code news:comp.lang.java}<td></tr>
!  * <tr><td>{@code urn:isbn:096139210x}</td></tr>
!  * </table></blockquote>
   *
   * <p> A <i>hierarchical</i> URI is either an absolute URI whose
   * scheme-specific part begins with a slash character, or a relative URI, that
   * is, a URI that does not specify a scheme.  Some examples of hierarchical
   * URIs are:
--- 81,95 ----
   *
   * <p> An <i>opaque</i> URI is an absolute URI whose scheme-specific part does
   * not begin with a slash character ({@code '/'}).  Opaque URIs are not
   * subject to further parsing.  Some examples of opaque URIs are:
   *
!  * <blockquote><ul style="list-style-type:none">
!  * <li>{@code mailto:java-net@java.sun.com}</li>
!  * <li>{@code news:comp.lang.java}</li>
!  * <li>{@code urn:isbn:096139210x}</li>
!  * </ul></blockquote>
   *
   * <p> A <i>hierarchical</i> URI is either an absolute URI whose
   * scheme-specific part begins with a slash character, or a relative URI, that
   * is, a URI that does not specify a scheme.  Some examples of hierarchical
   * URIs are:

*** 130,150 ****
   * relative.  The path of a hierarchical URI that is either absolute or
   * specifies an authority is always absolute.
   *
   * <p> All told, then, a URI instance has the following nine components:
   *
!  * <blockquote><table summary="Describes the components of a URI:scheme,scheme-specific-part,authority,user-info,host,port,path,query,fragment">
   * <tr><th><i>Component</i></th><th><i>Type</i></th></tr>
   * <tr><td>scheme</td><td>{@code String}</td></tr>
   * <tr><td>scheme-specific-part&nbsp;&nbsp;&nbsp;&nbsp;</td><td>{@code String}</td></tr>
   * <tr><td>authority</td><td>{@code String}</td></tr>
   * <tr><td>user-info</td><td>{@code String}</td></tr>
   * <tr><td>host</td><td>{@code String}</td></tr>
   * <tr><td>port</td><td>{@code int}</td></tr>
   * <tr><td>path</td><td>{@code String}</td></tr>
   * <tr><td>query</td><td>{@code String}</td></tr>
   * <tr><td>fragment</td><td>{@code String}</td></tr>
   * </table></blockquote>
   *
   * In a given instance any particular component is either <i>undefined</i> or
   * <i>defined</i> with a distinct value.  Undefined string components are
   * represented by {@code null}, while undefined integer components are
--- 130,155 ----
   * relative.  The path of a hierarchical URI that is either absolute or
   * specifies an authority is always absolute.
   *
   * <p> All told, then, a URI instance has the following nine components:
   *
!  * <blockquote><table class="borderless">
!  * <caption style="display:none">Describes the components of a URI:scheme,scheme-specific-part,authority,user-info,host,port,path,query,fragment</caption>
!  * <thead>
   * <tr><th><i>Component</i></th><th><i>Type</i></th></tr>
+  * </thead>
+  * <tbody>
   * <tr><td>scheme</td><td>{@code String}</td></tr>
   * <tr><td>scheme-specific-part&nbsp;&nbsp;&nbsp;&nbsp;</td><td>{@code String}</td></tr>
   * <tr><td>authority</td><td>{@code String}</td></tr>
   * <tr><td>user-info</td><td>{@code String}</td></tr>
   * <tr><td>host</td><td>{@code String}</td></tr>
   * <tr><td>port</td><td>{@code int}</td></tr>
   * <tr><td>path</td><td>{@code String}</td></tr>
   * <tr><td>query</td><td>{@code String}</td></tr>
   * <tr><td>fragment</td><td>{@code String}</td></tr>
+  * </tbody>
   * </table></blockquote>
   *
   * In a given instance any particular component is either <i>undefined</i> or
   * <i>defined</i> with a distinct value.  Undefined string components are
   * represented by {@code null}, while undefined integer components are

*** 246,256 ****
   * RFC&nbsp;2396 specifies precisely which characters are permitted in the
   * various components of a URI reference.  The following categories, most of
   * which are taken from that specification, are used below to describe these
   * constraints:
   *
!  * <blockquote><table cellspacing=2 summary="Describes categories alpha,digit,alphanum,unreserved,punct,reserved,escaped,and other">
   *   <tr><th valign=top><i>alpha</i></th>
   *       <td>The US-ASCII alphabetic characters,
   *        {@code 'A'}&nbsp;through&nbsp;{@code 'Z'}
   *        and {@code 'a'}&nbsp;through&nbsp;{@code 'z'}</td></tr>
   *   <tr><th valign=top><i>digit</i></th>
--- 251,263 ----
   * RFC&nbsp;2396 specifies precisely which characters are permitted in the
   * various components of a URI reference.  The following categories, most of
   * which are taken from that specification, are used below to describe these
   * constraints:
   *
!  * <blockquote><table>
!  * <caption style="display:none">Describes categories alpha,digit,alphanum,unreserved,punct,reserved,escaped,and other</caption>
!  *   <tbody>
   *   <tr><th valign=top><i>alpha</i></th>
   *       <td>The US-ASCII alphabetic characters,
   *        {@code 'A'}&nbsp;through&nbsp;{@code 'Z'}
   *        and {@code 'a'}&nbsp;through&nbsp;{@code 'z'}</td></tr>
   *   <tr><th valign=top><i>digit</i></th>

*** 277,286 ****
--- 284,294 ----
   *           java.lang.Character#isISOControl(char) Character.isISOControl}
   *           method), and are not space characters (according to the {@link
   *           java.lang.Character#isSpaceChar(char) Character.isSpaceChar}
   *           method)&nbsp;&nbsp;<i>(<b>Deviation from RFC 2396</b>, which is
   *           limited to US-ASCII)</i></td></tr>
+  * </tbody>
   * </table></blockquote>
   *
   * <p><a id="legal-chars"></a> The set of all legal URI characters consists of
   * the <i>unreserved</i>, <i>reserved</i>, <i>escaped</i>, and <i>other</i>
   * characters.



< prev index next >