# DIFFS of version 5.3 vs. 5.2

Larry Masinter (masinter@parc.xerox.com)
Thu, 28 Jul 1994 20:35:57 PDT

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Clifford Neuman: "ftp ambiguity"
- Previous message: Chris Weider: "New URN draft"

    To: uri@bunyip.com

    Subject: DIFFS of version 5.3 vs. 5.2

    From: Larry Masinter <masinter@parc.xerox.com>

    Message-Id: <94Jul28.203604pdt.2760@golden.parc.xerox.com>

    Date: 	Thu, 28 Jul 1994 20:35:57 PDT

2,3c24,25
< interim draft 5.2 L. Masinter
< Expires February 27, 1995 M. McCahill

    ---
    > interim draft 5.3                                            L. Masinter
    > Expires February 28, 1995                                    M. McCahill
    5c27
    <                                                            July 27, 1994

    ---
    >                                                            July 28, 1994
    28c50
    <      This Internet Draft expires February 27, 1995.

    ---
    >      This Internet Draft expires February 28, 1995.
    69c91
    <        URL:<scheme>:<scheme-specific-part>

    ---
    >        <scheme>:<scheme-specific-part>
    71,78c93,95
    <    A URL starts with a constant prefix "URL:".  This prefix is used to
    <    identify the URL and distinguish it from other possible protocol
    <    elements. The part of the URL after the initial prefix is known as
    <    the URL body.
    <
    <    The body of the URL contains the name of the scheme being used
    <    (<scheme>) followed by a colon and then a string (the
    <    <scheme-specific-part>) whose interpretation depends on the scheme.

    ---
    >    A the URL contains the name of the scheme being used (<scheme>)
    >    followed by a colon and then a string (the <scheme-specific-part>)
    >    whose interpretation depends on the scheme.
    217,219c234,235
    <    FTP URLs follow the syntax described in Section 3.1.  The port
    <    number, if present, gives the port of the FTP server if not the FTP
    <    default (21).

    ---
    >    A FTP URL follow the syntax described in Section 3.1.  If <port>
    >    is not supplied, it defaults to 21.
    264a281,289
    >    For example, the URL <URL:ftp://myname@host.dom/%2fetc/motd> is
    >    interpreted by FTP-ing to "host.dom", logging in as "myname"
    >    (prompting for a password if it is asked for), and then executing
    >    "CWD /etc" and then "RETR motd". This has a different meaning from
    >    <URL:ftp://myname@host.dom/etc/motd> which would "CWD etc",
    >    relative to the default directory for "myname", or <URL:ftp:
    >    //myname@host.dom//etc/motd>, which would "CWD " with a null
    >    argument and then "RETR motd".
    >
    302c327
    <    The body of an HTTP URL takes the form:

    ---
    >    An HTTP URL takes the form:
    332c357
    <    The body of a Gopher URL takes the form:

    ---
    >    A Gopher URL takes the form:
    385,392c410,427
    <    <tab> and the gopher+ commands after the gopher selector (and the
    <    <tab> and search string in the case of a gopher search item). If a
    <    Gopher+ URL does not refer to a Gopher search type, the Gopher
    <    client sends to the server the gopher selector string, followed by
    <    a tab, followed by the gopher+ commands. If the Gopher+ URL refers
    <    to a Gopher search type, the client sends to the gopher server the
    <    gopher selector string, followed by a tab, followed the search
    <    string, followed by a tab, followed by the gopher+ commands.

    ---
    >    <tab> and the gopher+ commands after the gopher selector  and the
    >    <tab> and search string, when <gophertype>=7, identifying a gopher
    >    search item).
    >
    >    To retrieve the data associated with a Gopher+ URL, a client will
    >    connect to the server and send the gopher selector, followed
    >    optionally by a tab and the search string, followed by a tab and
    >    the Gopher+ commands.
    >
    >    More explicitly, if the Gopher+ URL refers to a Gopher search type
    >    (that is, if the Gopher type is 7), the client sends to the gopher
    >    server the gopher selector string, followed by a tab, followed the
    >    search string, followed by a tab, followed by the gopher+ commands.
    >
    >    If the Gopher+ URL does _not_ refer to a Gopher search (when the
    >    Gopher type is not 7), the Gopher client sends to the server the
    >    gopher selector string, followed by a tab, followed by the gopher+
    >    commands.
    474c509
    <    The body of a mailto URL takes the form:

    ---
    >    A mailto URL takes the form:
    495c530
    <    The body of a news URL takes one of two forms:

    ---
    >    A news URL takes one of two forms:
    521c556
    <    The body of a nntp URL take the form:

    ---
    >    A nntp URL take the form:
    544c579
    <    The body of a telnet URL takes the form:

    ---
    >    A telnet URL takes the form:
    559,560c594,595
    <    or individual documents available from a WAIS database.  The WAIS
    <    protocol is specified in RFC1625 [19].

    ---
    >    or individual documents available from a WAIS database. WAIS is
    >    described in [6]; the WAIS protocol is specified in RFC1625 [19].
    562c597
    <    The body of a WAIS URLs takes one the following forms:

    ---
    >    A WAIS URLs takes one the following forms:
    577c612
    <    the "type" of a object prior to retrieval, the type being returned

    ---
    >    the "type" of an object prior to retrieval, the type being returned
    579c614
    <    This type has been included the path part of the URL in order to

    ---
    >    This type has been included in the path part of the URL in order to
    582,584c617,621
    <    The <wpath> of a WAIS URL consists of the WAIS document-id, as
    <    defined in [6], suitably encoded, as described in Section 2.2.
    <

    ---
    >    The <wpath> of a WAIS URL consists of the WAIS document-id,
    >    suitably encoded as described in Section 2.2. The WAIS document-id
    >    is treated opaquely; while many WAIS document-ids may match the
    >    structure described in [6], this structure is not parsed or
    >    constructed by WAIS clients.
    593c630
    <    The body of a file URL takes the form:

    ---
    >    A file URL takes the form:
    623c660
    <    The body of a prospero URLs takes the form:

    ---
    >    A prospero URLs takes the form:
    646c683,687
    <    structure is not guaranteed.

    ---
    >    structure is not guaranteed. Note that many <hsoname>s begin with a
    >    slash, in which case the host or port will be followed by a double
    >    slash: the slash from the URL syntax, followed by the initial slash
    >    from the <hsoname>. (E.g., <URL:prospero://host.dom//pros/name>
    >    designates a <hsoname> of "/pros/name".
    702,707c743,747
    <    url            = "URL:" urlbody
    <    urlbody        = httpbody | ftpbody | newsbody |
    <                     nntpbody | telnetbody | gopherbody |
    <                     waisbody | mailtobody | filebody |
    <                     prosperobody | otherbody
    <    otherbody      = scheme ":" schemepart

    ---
    >    url            = httpurl | ftpurl | newsurl |
    >                     nntpurl | telneturl | gopherurl |
    >                     waisurl | mailtourl | fileurl |
    >                     prosperourl | otherurl
    >    otherurl       = scheme ":" schemepart
    720c760
    <    ftpbody        = "ftp://" login [ "/" fpath [ ";type=" ftptype ]]

    ---
    >    ftpurl         = "ftp://" login [ "/" fpath [ ";type=" ftptype ]]
    725c765
    <    filebody       = "file://" host [ "/" fpath ]

    ---
    >    fileurl        = "file://" host [ "/" fpath ]
    727c767
    <    httpbody       = "http://" hostport [ "/" hpath [ "?" search ]]

    ---
    >    httpurl        = "http://" hostport [ "/" hpath [ "?" search ]]
    732c772
    <    gopherbody     = "gopher://" hostport [ / [ gtype [ selector

    ---
    >    gopherurl      = "gopher://" hostport [ / [ gtype [ selector
    738c778
    <    mailtobody     = "mailto:" encoded822addr

    ---
    >    mailtourl      = "mailto:" encoded822addr
    741c781
    <    newsbody       = "news:" grouppart

    ---
    >    newsurl        = "news:" grouppart
    746c786
    <    nntpbody       = "nntp://" hostport "/" group [ "/" digits ]

    ---
    >    nntpurl        = "nntp://" hostport "/" group [ "/" digits ]
    748c788
    <    telnetbody     = "telnet://" login [ "/" ]

    ---
    >    telneturl      = "telnet://" login [ "/" ]
    750c790
    <    waisbody       = waisdatabase | waisindex | waisdoc

    ---
    >    waisurl        = waisdatabase | waisindex | waisdoc
    758c798
    <    prosperobody   = "prospero://" hostport "/" ppath *[ fieldspec ]

    ---
    >    prosperourl    = "prospero://" hostport "/" ppath *[ fieldspec ]
    854c894
    < APPENDIX: URLs in Plain Text

    ---
    > APPENDIX: Recommendations for URLs in Context
    856,858c896,905
    <    URIs, including URLs, will ideally be transmitted though protocols
    <    which accept them and data formats which define a context for them.
    <    In practice, there are many occasions when URLs are included in

    ---
    >    URIs, including URLs, are intended to be transmitted though
    >    protocols which provide a context for their interpretation.
    >
    >    In some cases, it will be necessary to distinguish URLs from other
    >    possible data structures in a syntactic structure. In this case, is
    >    recommended that URLs be preceeded with a prefix consisting of the
    >    characters "URL:". For example, this prefix may be used to
    >    distinguish URLs from other kinds of URIs.
    >
    >    In addition, there are many occasions when URLs are included in
    862,865c909,913
    <    separates it from the rest of the text.
    <
    <    It is recommended that angle brackets (less than "<" and greater
    <    than ">") be used to delimit the boundaries of the URL.

    ---
    >    separates it from the rest of the text. For this purpose, is
    >    recommended that angle brackets ("<" and ">"), along with the
    >    prefix "URL:", be used to delimit the boundaries of the URL.  This
    >    wrapper does not form part of the URL and should not be used in
    >    contexts in which delimiters are already specified.
    870c918,919
    <    URL, the identifier would be placed within the brackets as well.

    ---
    >    URL (following a "#"), the identifier would be placed within the
    >    brackets as well.
    872,875d920
    <    These wrappers do not form part of the URL and should not be used
    <    in contexts in which delimiters are already specified (e.g., SGML
    <    parameters, HTTP requests.)
    <
    878,881c923,926
    <    Yes, Jim, I found it under <URL:ftp://info.cern.ch/pub/www/doc> but
    <    you can probably pick it up from <URL:ftp://ds.internic.net/rfc>.
    <    Note the warning in <URL:http://ds.internic.net/instructions
    <    /overview.html#WARNING>.

    ---
    >    Yes, Jim, I found it under <URL:ftp://info.cern.ch/pub/www/doc
    >    ;type=d> but you can probably pick it up from <URL:ftp://ds.inter
    >    nic.net/rfc>.  Note the warning in <URL:http://ds.internic.net/
    >    instructions/overview.html#WARNING>.
    995d1039
    <

     Next message: Clifford Neuman: "ftp ambiguity"
     Previous message: Chris Weider: "New URN draft"