Date: Sat, 6 Aug 94 22:45:29 -0400
Message-Id: <9408070245.AA20555@zippy.lcs.mit.edu>
From: "Karen R. Sollins" <sollins@lcs.mit.edu>
To: uri@bunyip.com
Subject: diffs for urn requirements doc
3,5c3,5
< draft-sollins-urn-01.txt L. Masinter
< Expires January 5, 1995 Xerox Corporation
< June 30, 1994
--- > draft-ietf-uri-urn-req-00.txt L. Masinter > Replaces draft-sollins-urn-01.txt Xerox Corporation > Expires February 9, 1995 August 9, 1994 60c60 < INTERNET-DRAFT Requirements for Uniform Resource Names June 30,1994--- > INTERNET-DRAFT Requirements for Uniform Resource Names August 9,1994 84,85c84,85 < persistent identifier used both for recognition and for < access to characteristics of or access to the resource.--- > persistent identifier used both for recognition and for access > to characteristics of the resource or access to the resource. 118c118 < INTERNET-DRAFT Requirements for Uniform Resource Names June 30, 1994--- > INTERNET-DRAFT Requirements for Uniform Resource Names August 9, 1994 175c175 < INTERNET-DRAFT Requirements for Uniform Resource Names June 30, 1994--- > INTERNET-DRAFT Requirements for Uniform Resource Names August 9, 1994 176a177 > 180,181c181,184 < requirements. Some design decisions are a direct result of these < requirements:--- > requirements. We draw a set of conclusions, listed below, from > those requirements; a specification that satisfies the requirments > without meetings these conclusions is deemed acceptable, although > unlikely to occur. 187c190 < guarantee uniqueness. The name of the naming authorities--- > guarantee uniqueness. The names of the naming authorities 211a215,216 > 5. Other considerations > 224,227c229,231 < make that distinction. Furthermore, it may be that the algorithms < used by neither of these two sources of URNs for a book has a basis by < which to compare two spreadsheets. Thus, although this document < requires that any particular naming authority use one algorithm for--- > make that distinction. Furthermore, no one algorithm for testing > for equality is likely to applicable to all sorts of information. > For example, an algorithm based on testing the equality of two 232c236 < INTERNET-DRAFT Requirements for Uniform Resource Names June 30, 1994--- > INTERNET-DRAFT Requirements for Uniform Resource Names August 9, 1994 235,237c239,244 < determining whether two resources it is comparing are the same or < different, each naming authority can use a different such algorithm < and a naming authority may restrict the set of resources it chooses to--- > books is unlikely to be useful when testing the equality of two > spreadsheets. Thus, although this document requires that any > particular naming authority use one algorithm for determining > whether two resources it is comparing are the same or different, > each naming authority can use a different such algorithm and a > naming authority may restrict the set of resources it chooses to 284a292,294 > > > 287c297 < INTERNET-DRAFT Requirements for Uniform Resource Names June 30, 1994--- > INTERNET-DRAFT Requirements for Uniform Resource Names August 9, 1994 288a299 > 302,308c313,319 < Larry Masinter Karen Sollins < Xerox Palo Alto Research Center MIT Laboratory for Computer Science < 3333 Coyote Hill Road 545 Technology Square < Palo Alto, CA 94304 Cambridge, MA 02139 < masinter@parc.xerox.com sollins@lcs.mit.edu < Voice: (415) 812-4365 Voice: (617) 253-6006 < Fax: (415) 812-4333 Tel: (617) 253-2673--- > Larry Masinter Karen Sollins > Xerox Palo Alto Research Center MIT Laboratory for Computer Science > 3333 Coyote Hill Road 545 Technology Square > Palo Alto, CA 94304 Cambridge, MA 02139 > masinter@parc.xerox.com sollins@lcs.mit.edu > Voice: (415) 812-4365 Voice: (617) 253-6006 > Fax: (415) 812-4333 Tel: (617) 253-2673 318d328 < Sollins & Masinter [Page 6] 322a333,356 > > > > > > > > > > > > > > > > > > > > > > > > Sollins & Masinter [Page 6]