2,3c2,3
< INTERNET-DRAFT version 0.1                                    UC Irvine
< Expires February 25, 1995                                  August 20, 1994
---
> INTERNET-DRAFT                                                UC Irvine
> Expires February 24, 1995                               August 24, 1994
6a7
>                  <draft-ietf-uri-relative-url-00.txt>
34d34
<    This Internet-Draft expires February 25, 1995.
36d35
< 
236c235
<    described in terms of named sets: Never-Relative, Uses-Netloc,
---
>    described in terms of named sets: Uses-Relative, Uses-Netloc,
239c238
< 2.3.1  The Never-Relative Set
---
> 2.3.1  The Uses-Relative Set
241,242c240,241
<    The Never-Relative set includes those access schemes which are
<    never considered relative to another URL.
---
>    The Uses-Relative set includes those access schemes which are
>    allowed to use relative forms.
244c243
<       Never-Relative = {mailto, news, telnet}
---
>       Uses-Relative = {ftp, http, gopher, nntp, wais, file, prospero}
245a245,247
>    Schemes that are not in the Uses-Relative set (including any scheme
>    which is unknown to the parser) are assumed to be in absolute form.
> 
302c304
<               Never-   Uses-   Non-Hier  Uses-    Uses-    Uses-
---
>               Uses-    Uses-   Non-Hier  Uses-    Uses-    Uses-
305,314c307,316
<    ftp      |        |  XXXX  |        |  XXXX  |        |  XXXX  |
<    http     |        |  XXXX  |        |        |  XXXX  |  XXXX  |
<    gopher   |        |  XXXX  |  XXXX  |        |        |  XXXX  |
<    mailto   |  XXXX  |        |  XXXX  |        |        |        |
<    news     |  XXXX  |        |  XXXX  |        |        |  XXXX  |
<    nntp     |        |  XXXX  |        |        |        |  XXXX  |
<    telnet   |  XXXX  |  XXXX  |  XXXX  |        |        |        |
<    wais     |        |  XXXX  |  XXXX  |        |  XXXX  |  XXXX  |
<    file     |        |  XXXX  |        |        |        |  XXXX  |
<    prospero |        |  XXXX  |        |  XXXX  |        |  XXXX  |
---
>    ftp      |  XXXX  |  XXXX  |        |  XXXX  |        |  XXXX  |
>    http     |  XXXX  |  XXXX  |        |        |  XXXX  |  XXXX  |
>    gopher   |  XXXX  |  XXXX  |  XXXX  |        |        |  XXXX  |
>    mailto   |        |        |  XXXX  |        |        |        |
>    news     |        |        |  XXXX  |        |        |  XXXX  |
>    nntp     |  XXXX  |  XXXX  |        |        |        |  XXXX  |
>    telnet   |        |  XXXX  |  XXXX  |        |        |        |
>    wais     |  XXXX  |  XXXX  |  XXXX  |        |  XXXX  |  XXXX  |
>    file     |  XXXX  |  XXXX  |        |        |        |  XXXX  |
>    prospero |  XXXX  |  XXXX  |        |  XXXX  |        |  XXXX  |
406,409c408,410
<    parser.  None of the schemes in the Never-Relative set
<    (Section 2.3.1) can be used for a base URL.  There are three
<    methods for obtaining the base URL of a document, listed here in
<    order of precedence.
---
>    parser.  Only the schemes in the Uses-Relative set (Section 2.3.1)
>    can be used for a base URL.  There are three methods for obtaining
>    the base URL of a document, listed here in order of precedence.
488c489
<            the base URL or is a member of the Never-Relative set
---
>            the base URL or is not a member of the Uses-Relative set
545c546
< 5.  Examples
---
> 5.  Examples and Recommended Practice
552a554,555
> 5.1.  Normal Examples
> 
554,555d556
<       http:g     = <URL:http://a/b/c/g>
<       http:      = <URL:http://a/b/c/d>
570a572,574
> 
> 5.2.  Abnormal Examples
> 
575,576c579,582
<       g/./h      = <URL:http://a/g/h>
<       g/../h     = <URL:http://a/h>
---
>       g/./h      = <URL:http://a/b/c/g/h>
>       g/../h     = <URL:http://a/b/c/h>
>       http:g     = <URL:http://a/b/c/g>
>       http:      = <URL:http://a/b/c/d>
578c584
<    Note that, although the last six examples are not likely to occur
---
>    Note that, although the abnormal examples are not likely to occur
581a588,606
> 5.3.  Recommended Practice
> 
>    Although the relative form does allow scheme names to be used with
>    relative paths, as in the last two abnormal examples ("http:g" and
>    "http:") above, it is strongly recommended that authors not use the
>    scheme name in this manner.  Including the scheme name prevents a
>    relative URL from being usable in more than one context (e.g.,
>    simultaneous availability via "file" and "http") and requires that
>    the URL be changed if the primary access scheme is changed.
> 
>    Authors should also be aware that path names which contain a colon
>    ":" character cannot be used as the first component of a relative
>    URL path (e.g. "this:that") because they will likely be mistaken for
>    a scheme name.  It is therefore necessary to precede such cases with
>    other components (e.g., "./this:that"), or to escape the colon
>    character (e.g., "this%3Athat"), in order for them to be correctly
>    parsed.  The former solution is preferred because it has no effect
>    on the absolute form of the URL.
> 
597c622,625
<    Resource Locators as stated in [15].
---
>    Resource Locators as stated in [15].  It has benefited greatly from
>    the comments of all those participating in the URI-WG.  Particular
>    thanks go to Larry Masinter, Michael A. Dolan, and Guido van Rossum
>    for identifying problems/deficiencies in earlier drafts.
682a711,712
> 
>    This Internet-Draft expires February 24, 1995.