Group:
type inheritance
Topic:
absolute vs. relative names
Topic:
access by current position
Topic:
access to components of a data object
Topic:
access to objects by a path
Topic:
alias names
Topic:
binding of names to objects
Topic:
context
Topic:
declaration scope
Topic:
environment variables
Topic:
evaluation in an environment
Topic:
hierarchical naming
Topic:
local declaration of data
Topic:
localized understanding
Topic:
meaning vs. reference
Topic:
names as rigid designators
Topic:
namespace
Topic:
naming by pointing or recognition
Topic:
object-defined names
Topic:
objects without names
Topic:
pronoun reference
Topic:
unique names
Topic:
unique numeric names as surrogates
Topic:
using a description as a name
Topic:
using an address as a name
| |
Summary
Names distinguish objects within a context. If context is ignored, a name is ambiguous. Similarly the meaning of a number depends on its context. A qualified name (e.g., the employee's children) specifies one name in terms of another.
How does contextual names relate to names as rigid designators? (cbb 12/00)
Subtopic: names depend on context 
| Quote: symbols have multiple, complex meanings and denotations, often varying from one context to another [»kentW6_1991]
| | Quote: names depend on context to resolve ambiguity [»hauzBM10_1986]
| | Quote: nonunique representations commonly occur in data; discriminated by local conventions [»kentW1_1984]
| | Quote: whether a symbol is one of the handles of some object, depends on the current scope; the denoted object may change with scope [»kentW6_1991]
| | Quote: Subtext labels depend on the human ability to disambiguate labels by their context; labels are not unique [»edwaJ10_2005]
|
Subtopic: environment names
| Quote: implement dynamic variables via set and use statements that allocate from the stack; 'use' searches the 'set' variables for a match [»hansDR6_2001]
| | Quote: use environmental variables for conditions that effect the way a program runs; e.g., traffic load; use brainstorming [»musaJD3_1993]
| | Quote: in SL5, identifiers are attributes of an environment; a record is an environment [»hansDR3_1978a]
| | Quote: a non-local or public identifier in an environment is assigned a constant value when the environment is created [»hansDR5_1978]
| | Quote: environments in SL5 serve as both data structures and procedures [»hansDR3_1978a]
|
Subtopic: bound vs. free
| Quote: a bound variable or parameter is symbol independent, while a free variable depends on context [»landPJ_1966, OK]
|
Subtopic: ambiguous names
| Quote: the telephone clearinghouse require clients to resolve ambiguities [»oppeDC7_1983]
|
Subtopic: contextual names
| Quote: in a localized context, only need names to distinguish those members that might be accessed [»robeJD10_1981]
| | Quote: refer to most things by a combination of pointing, noun phrases, and context [»kentW1_1984]
| | Quote: representation of some entities derived from context, e.g., the name of the home team [»kentW1_1984]
| | Quote: a name can be meaningless unless you know its category, e.g., Colt [»kentW_1978]
| | Quote: one word of context is sufficient to disambiguate 75% of word senses; two words disambiguate 90% [»chouY7_1985]
| | Quote: people can often disambiguate words with only a few words of context, and frequently, only one word is needed [»krovR4_1992]
| | Quote: a proper name refers without presupposing a context; demonstratives and singular, referring expressions assume a context [»searJR_1958]
|
Subtopic: qualified names
| Quote: qualified names resolves ambiguities by defining context; scope can be nested [»kentW_1978]
| | Quote: qualified names, e.g., an employee's children, has problems of uniqueness, singularity, no qualifier, changing qualifier [»kentW_1978, OK]
| | Quote: some entities are only known via a related entity, e.g., the 1980 election [»kentW1_1984]
| | Quote: objects with qualified names should be entities independent of the qualifier [»kentW_1978]
|
Subtopic: relational data
| Quote: data in relational database addressed by relation name, attribute name, and primary key [»coddEF2_1982]
|
Subtopic: path name
| Quote: a local name is an encoding of an access path from one actor to another [»hewiC8_1977]
| | Quote: access remote data by a chain of pointers; e.g., ABC is the name of A->B->C [»knowK8_1966, OK]
| | Quote: in Simula, fishdeath.cause.countermeasure.cost yields a value according to class methods [»palmJ5_1973, OK]
| | Quote: form name for a subprogram by concatenating all embedded names [»boocG1_1982]
|
Subtopic: local name
| Quote: a name-graph consists of objects with global ids at nodes; colored arcs indicate the local name in the context of the object [»robeJD10_1981]
| | Quote: stock market displays allow dealers to refer to stock in terms of its current price [»jiroM12_1993]
| | Quote: a number represents an entity if we know the symbol type, i.e., naming universe [»kentW1_1984]
| | Quote: every function in HyperTalk sets 'it' implicitly; turns expressions into a sequence of statements [»myerBA_1992]
|
Subtopic: composite name
| Quote: composite names convey additional information; e.g., state and country for a city [»kentW_1978]
|
Subtopic: context-sensitive mouse
| Quote: KMS has a context sensitive mouse with button labels attached to the cursor [»akscRM7_1988a]
| | Quote: button labels for a mouse used by novices to learn a system and by experts subliminally
| | Quote: Pygmalion uses a three button mouse that depends on context; for cursor positioning and moving values [»smitDC6_1975, OK]
|
Related Topics
Group: type inheritance (13 topics, 394 quotes)
Topic: absolute vs. relative names (12 items)
Topic: access by current position (7 items)
Topic: access to components of a data object (4 items)
Topic: access to objects by a path (13 items)
Topic: alias names (39 items)
Topic: binding of names to objects (19 items)
Topic: context (8 items)
Topic: declaration scope (16 items)
Topic: environment variables (5 items)
Topic: evaluation in an environment (35 items)
Topic: hierarchical naming (28 items)
Topic: local declaration of data (11 items)
Topic: localized understanding (43 items)
Topic: meaning vs. reference (49 items)
Topic: names as rigid designators (43 items)
Topic: namespace (19 items)
Topic: naming by pointing or recognition (13 items)
Topic: object-defined names (15 items)
Topic: objects without names (7 items)
Topic: pronoun reference (23 items)
Topic: unique names (58 items)
Topic: unique numeric names as surrogates (67 items)
Topic: using a description as a name (21 items)
Topic: using an address as a name
(22 items)
|
