Group:
access to data
Topic:
access to objects by a path
Topic:
communication port
Topic:
information retrieval by location
Topic:
meaning vs. reference
Topic:
name server or name directory
Topic:
names defined by context
Topic:
naming by pointing or recognition
Topic:
objects without names
Topic:
pointers to data
Topic:
routing electronic mailing
Topic:
unique numeric names as surrogates
Topic:
using a description as a name
Topic:
World-Wide Web
| |
Summary
The name or reference for an object may be the address, location, or route to the object. Such an address may be the object's only name. For example, machine code usually uses numeric addresses instead of character-based names. An object may have multiple addresses. Addresses are particularly important for locating an object as opposed to identifying an object.
With computerized data, an object may be identified by a network address plus a local identifier (e.g., a URL). In a relational database, data is identified with a table name, primary key value, and attribute.
Route addresses (e.g., UUCP "relative name") make it difficult to reorganize a network. Xanadu uses permanent, tumbler addresses with a version id and byte offset. (cbb 4/98)
Subtopic: address as a name 
| Quote: an address allows generation of route; it must be bound; e.g., a telephone number is the name of a telephone set for a person [»hauzBM10_1986]
| | Quote: machines may have multiple network addresses but objects may reside on only one machine [»oppeDC7_1983]
| | Quote: what is the meaning of a name in a program? In Bliss, it is a location. In Algol 68, it is a location that is automatically converted to a value. In C, it is a value. [»ritcDM_1996]
| | Quote: with the World-Wide Web, all items have a reference for retrieving the item
|
Subtopic: how to designate an object
| Quote: name directory should support mailbox addresses, logical addresses and descriptive addresses [»comeDE11_1986]
| | Quote: the name of a resource indicates what we seek, an address is where, and a route is how to get there [»shocJF9_1978]
| | Quote: ways to designate an object: name, address, content, owner, class, group, path, relationship [»watsRW_1981]
|
Subtopic: physical vs. logical
| Quote: distinguish physical, Clearinghouse servers from logical domain and organizational clearinghouses [»oppeDC7_1983]
|
Subtopic: address vs. ID
| Quote: check an address by checking the object's unique identifier [»oppeDC7_1983]
|
Subtopic: relative address vs. absolute name
| Quote: consider this sequence: Godfather, Paris Theater, Paris at 58th and 5th, turn left... [»martJ_1975, OK]
| | Quote: even though relative naming is simpler, absolute naming has clear advantages [»oppeDC7_1983]
| | Quote: in uucp, relative naming prevents routing optimization; disallows name forwarding [»suZS8_1982]
|
Subtopic: two-level names
| Quote: V's object identifiers consist of an object-manager-IPC-id (changes on reboot) and a local-object-id (transient name) [»cherDR3_1988]
| | Quote: a V process id consists of a logical host id and a local process index; for locating host when sending a message [»cherDR4_1984]
| | Quote: under Clearinghouse, address of object is network address plus unique id. [»oppeDC7_1983]
| | Quote: local Telesophy objects by memory pointer; remote objects by server number/local index [»caplM12_1987]
|
Subtopic: hierarchical, permanent address
| Quote: an address tumbler is a universal, unique identifier; hierarchically defined [»nelsTH1_1988]
| | Quote: an address tumbler creates a place to put things and a way to remember their location [»nelsTH_1987]
| | Quote: a humber is a variable-precision number [»nelsTH1_1988]
| | Quote: hierarchically arranged numbers, allows owner of a number to create related numbers [»nelsTH_1987]
| | Quote: an address tumbler is valid forever [»nelsTH_1987]
|
Subtopic: relational database
| Quote: data in relational database addressed by relation name, attribute name, and primary key [»coddEF2_1982]
|
Related Topics
Group: access to data (12 topics, 307 quotes)
Topic: access to objects by a path (13 items)
Topic: communication port (40 items)
Topic: information retrieval by location (21 items)
Topic: meaning vs. reference (49 items)
Topic: name server or name directory (40 items)
Topic: names defined by context (36 items)
Topic: naming by pointing or recognition (13 items)
Topic: objects without names (7 items)
Topic: pointers to data (55 items)
Topic: routing electronic mailing (12 items)
Topic: unique numeric names as surrogates (67 items)
Topic: using a description as a name (21 items)
Topic: World-Wide Web
(42 items)
|
