# urn doc diffs

Karen R. Sollins (sollins@lcs.mit.edu)
Mon, 17 Oct 1994 19:05:34 -0400

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Patrik Faltstrom: "Re: Uniform Resource Names - almost draft"
- Previous message: Olle Jarnefors: "Re: response to your 'last call' comments"

    Date: Mon, 17 Oct 1994 19:05:34 -0400

    Message-Id: <199410172305.TAA02469@lysithea.lcs.mit.edu>

    From: "Karen R. Sollins" <sollins@lcs.mit.edu>

    To: uri@bunyip.com

    Subject: urn doc diffs

3,5c3,5
< draft-ietf-uri-urn-req-00.txt L. Masinter
< Replaces draft-sollins-urn-01.txt Xerox Corporation
< Expires March 10, 1995 September 10, 1994

    ---
    > draft-ietf-uri-urn-req-01.txt				    L. Masinter
    > Replaces draft-ietf-uri-urn-req-00.txt		      Xerox Corporation
    > Expires April 19, 1995				       October 19, 1994
    8c8
    <   	      Requirements for Uniform Resource Names

    ---
    >        Functional Requirements for Uniform Resource Names
    12,14c12,29
    <    This memo provides information for the Internet community. This memo
    <    does not specify an Internet standard of any kind. Distribution of
    <    this memo is unlimited.

    ---
    > This document is an Internet-Draft.  Internet-Drafts are working documents
    > of the Internet Engineering Task Force (IETF), its Areas, and its Working
    > Groups.  Note that other groups may also distribute working documents as
    > Internet-Drafts.
    >
    > Internet-Drafts are working documents valid for a maximum of six months.
    > Internet-Drafts may be updated, replaced, or obsoleted by other documents
    > at any time.  It is not appropriate to use Internet-Drafts as reference
    > material or to cite them other than as a ``working draft' or ``work in
    > progress.''
    >
    > To learn the current status of any Internet-Draft, please check the
    > 1id-abstracts.txt listing contained in the Internet-Drafts Shadow
    > Directories on ds.internic.net, nic.nordu.net, ftp.isi.edu, or
    > munnari.oz.au.
    >
    > Distribution of this document is unlimited.  Please send comments to the
    > discussion list uri@bunyip.com.
    18,32c33,66
    <    This document sets out the requirements for Uniform Resource Names
    <    (URNs) within a larger Internet information architecture, which in
    <    turn is composed of, additionally, Uniform Resource Characteristics
    <    (URCs), and Uniform Resource Locators (URLs).  URNs are used for
    <    identification, URCs for including meta-information, and URLs for
    <    locating or finding resources.  It is provided as a basis for
    <    evaluating standards for URNs.  The discussions of this work have
    <    occurred on the mailing list uri@bunyip.com and at the URI Working
    <    Group sessions of the IETF.
    <
    <    The requirements for uniform resource names (URNs) fit within the
    <    overall architecture of Uniform Resource Identification.  In order to
    <    build applications in the most general case, the user must be able to
    <    discover and identify the information, objects, or what we will call
    <    in this architecture resources, on which the application is to

    ---
    >    This document specifies a minimum set of requirements for a kind of
    >    Internet resource identifier known as Uniform Resource Names
    >    (URNs).  URNs fit within a larger Internet information
    >    architecture, which in turn is composed of, additionally, Uniform
    >    Resource Characteristics (URCs), and Uniform Resource Locators
    >    (URLs).  URNs are used for identification, URCs for including
    >    meta-information, and URLs for locating or finding resources.  It
    >    is provided as a basis for evaluating standards for URNs.  The
    >    discussions of this work have occurred on the mailing list
    >    uri@bunyip.com and at the URI Working Group sessions of the IETF.
    >
    >    The requirements described here are not necessarily exhaustive; for
    >    example, there are several issues dealing with support for
    >    replication of resources and with security that have been
    >    discussed; however, the problems are not well enough understood at
    >    this time to include specific requirements in those areas here.
    >
    >    Within the general area of distributed object systems design, there
    >    are many concepts and designs that are discussed under the general
    >    topic of "naming". The URN requirements here are for a facility
    >    that addresses a different (and, in general, more stringent) set of
    >    needs than are frequently the domain of general object naming.
    >
    >
    > Sollins & Masinter						[Page 1]
    >
    > INTERNET-DRAFT	Requirements for Uniform Resource Names	    Oct. 19,1994
    >
    >
    >    The requirements for Uniform Resource Names fit within the overall
    >    architecture of Uniform Resource Identification.  In order to build
    >    applications in the most general case, the user must be able to
    >    discover and identify the information, objects, or what we will
    >    call in this architecture resources, on which the application is to
    34c68
    <    define "resource."  As the network and interconnectivity grow, the

    ---
    >    define "resource."  As the network and interconnectivity grow, the
    38,49c72,83
    <    activities where one of the primary constraints is human utility and
    <    facility and those in which human involvement is small or nonexistent.
    <    Human naming must have such characteristics as being both mnemonic and
    <    short.  Humans, in contrast with computers, are good at heuristic
    <    disambiguation and wide variability in structure.  In order for
    <    computer and network based systems to support global naming and
    <    access to resources that have perhaps an indeterminate lifetime, the
    <    flexibility and attendant unreliability of human-friendly names
    <    should be translated into a naming infrastructure more appropriate
    <    for the underlying support system.  It is this underlying support
    <    system that the Internet Information Infrastructure Architecture
    <    (IIIA) is addressing.

    ---
    >    activities where one of the primary constraints is human utility
    >    and facility and those in which human involvement is small or
    >    nonexistent.  Human naming must have such characteristics as being
    >    both mnemonic and short.  Humans, in contrast with computers, are
    >    good at heuristic disambiguation and wide variability in structure.
    >    In order for computer and network based systems to support global
    >    naming and access to resources that have perhaps an indeterminate
    >    lifetime, the flexibility and attendant unreliability of
    >    human-friendly names should be translated into a naming
    >    infrastructure more appropriate for the underlying support system.
    >    It is this underlying support system that the Internet Information
    >    Infrastructure Architecture (IIIA) is addressing.
    56,62d89
    <
    <
    < Sollins & Masinter						[Page 1]
    <
    < INTERNET-DRAFT	Requirements for Uniform Resource Names	   Sept. 10,1994
    <
    <
    87a115,120
    >
    > Sollins & Masinter						[Page 2]
    >
    > INTERNET-DRAFT	Requirements for Uniform Resource Names	    Oct. 19,1994
    >
    >
    112,121d144
    <
    <
    <
    <
    <
    < Sollins & Masinter						[Page 2]
    <
    < INTERNET-DRAFT	Requirements for Uniform Resource Names	  Sept. 10, 1994
    <
    <
    123,125c146,150
    <      legacy naming systems.  For example, ISBN numbers, ISO public
    <      identifiers, UPC product codes and the like are naming schemes
    <      which should be allowed to be embedded within the URN system.

    ---
    >      legacy naming systems, insofar as they satisfy the other
    >      requirements described here. For example, ISBN numbers, ISO
    >      public identifiers, and UPC product codes seem to satisfy the
    >      functional requirements, and allow an embedding that satisfies
    >      the syntactic requirements described here.
    152a178,183
    >
    > Sollins & Masinter						[Page 3]
    >
    > INTERNET-DRAFT	Requirements for Uniform Resource Names	    Oct. 19,1994
    >
    >
    170,178d200
    <
    <
    <
    <
    < Sollins & Masinter						[Page 3]
    <
    < INTERNET-DRAFT	Requirements for Uniform Resource Names   Sept. 10, 1994
    <
    <
    215a238,243
    >
    > Sollins & Masinter						[Page 4]
    >
    > INTERNET-DRAFT	Requirements for Uniform Resource Names	    Oct. 19,1994
    >
    >
    233,239d260
    <
    <
    < Sollins & Masinter						[Page 4]
    <
    < INTERNET-DRAFT	Requirements for Uniform Resource Names	  Sept. 10, 1994
    <
    <
    277a299,305
    >
    >
    > Sollins & Masinter						[Page 5]
    >
    > INTERNET-DRAFT	Requirements for Uniform Resource Names	    Oct. 19,1994
    >
    >
    289,300d316
    <
    <
    <
    <
    <
    <
    <
    < Sollins & Masinter						[Page 5]
    <
    < INTERNET-DRAFT	Requirements for Uniform Resource Names	  Sept. 10, 1994
    <
    <
    312c328
    < Author's Address

    ---
    > Authors' Addresses
    321,331d336
    <
    <
    <
    <
    <
    <
    <
    <
    <
    <
    <

     Next message: Patrik Faltstrom: "Re: Uniform Resource Names - almost draft"
     Previous message: Olle Jarnefors: "Re: response to your 'last call' comments"