| 
|
Topic: absolute vs. relative names
topics >
access by current position
Topic:
access to objects by a path
Topic:
hierarchical naming
Topic:
information retrieval by location
Topic:
local vs. global
Topic:
names defined by context
Topic:
object-defined names
Topic:
proper names
Topic:
special relativity
Topic:
unique names
Summary
A relative name is a hierarchical name relative to the current directory or context. This allows you to join and split naming universes.A relative name is insensitive to reorganization. An absolute name may be used for external references. (cbb 12/00)
Subtopic: advantage of relative names
Quote: even though relative naming is simpler, absolute naming has clear advantages [»oppeDC7_1983] Quote: every Clearinghouse object has an absolute, distinguished name [»oppeDC7_1983] Quote: an absolute name means the same thing when given to another client [»oppeDC7_1983] Quote: absolute references compress better than hierarchical references; encode gaps between successive occurrences [»wittIH_1991]
Subtopic: labels avoid knowledge of absolute address
Quote: relative names allow hierarchical representation of documents; links are independent of the physical or logical location [»bernT8_1994] Quote: a manuscript should refer to files through indirect symbolic names; prevents dependence on a particular installation [»reidBK_1980] Quote: use relative references to preserve internal links when moving a collection of documents [»ashmH9_2000] Quote: colons separate directory names, * indicates the parent, a leading : indicates a relative path from the working directory [»daleRC_1965]
Subtopic: private names vs. shared names
Quote: use labels to avoid knowledge of absolute position within a list [»maclBJ_1987]
Subtopic: need flexibility
Quote: Smalltalk names objects within a private address space while Unix uses a shared file system; Unix has many more organizational productivity tools [»coxBJ7_1983]
Quote: should be able to join naming universes, e.g., north america merged via area codes [»oppeDC7_1983] Quote: inflexible namespaces lead to conflicts; avoid flat namespaces requiring conventions, package conflicts, restricted scoping, static services
[»acheF9_2000]
Topic: access by current position (7 items)
Topic: access to objects by a path (13 items)
Topic: hierarchical naming (28 items)
Topic: information retrieval by location (21 items)
Topic: local vs. global (29 items)
Topic: names defined by context (36 items)
Topic: object-defined names (15 items)
Topic: proper names (35 items)
Topic: special relativity (73 items)
Topic: unique names
(58 items)