Group: database model

Quote: existing database models are highly structured, rigid, and simplistic [»kentW_1978]

Quote: databases have either well-defined record structures, or unstructured text files [»akscRM5_1984]

Group: naming

Group: hypertext

Topic: hypertext nodes made of names

Topic: universal data type

Quote: a Clearinghouse group is a set of names (a property type) [»oppeDC7_1983]

Quote: in semantic nets, there are no primitive word concepts; everything defined in terms of other things in the memory [»quilMR_1967]

Quote: a type retract defines the interpretation (value) of each element in the universal domain [»demeA_1978]

Topic: data as a named set of data objects

Topic: attribute-value pairs as information

Topic: object-defined names

Topic: data type as constructors, selectors, and predicates

Topic: fundamental concepts such as type, attributes, relationships are all the same

Quote: much of information is the attributes of things [»kentW_1978]

Quote: quantities in the model system usually corresponds to a property of a component of the referent system [»handP_1981]

Quote: observed or measured information about an entity or relationship is expressed as a set of attribute-value pairs [»chenPP3_1976]

Quote: with attributes, can incrementally define procedures, data, etc. [»cheaTE_1979]

Quote: a record in Pascal defines a local naming scope which is opened with the dot operator [»maclBJ_1987]

Quote: Clearinghouse property names assigned by a naming authority (for ease of merging) [»oppeDC10_1981]

Quote: a Clearinghouse property has a name, a type and a value [»oppeDC7_1983]

Quote: use lookupGeneric to return names which have a property [»oppeDC10_1981]

Quote: in Clearinghouse, can get the set of properties assigned to a name [»oppeDC10_1981]

Quote: a type module is an abstraction of naming; its execution introduces new names [»hehnEC7_1975]

Quote: data in relational database addressed by relation name, attribute name, and primary key [»coddEF2_1982]

Quote: a database does not see files as character arrays; perhaps database functions should be the low level facility [»stonM7_1981]

Topic: uniform reference to data For instance function reference should have the same form as data reference since they both result in a typed value. Two possibilities are data access by an accessing function and functions as object components. Treating both functions and data as object components, removes any a prior component evaluation.

Topic: notations for object access

Topic: uniform representation of files and sequences

Topic: binding of names to objects

Quote: parameter and declaration conventions should be consistent [»tennRD_1975]

Quote: the complex numbers is an abstraction that is represented by a variety of different sets

Quote: treat large objects the same as small ones; easily created and moved; not treated as a static set of small objects [»pratV1_1983]

Quote: there should not be a distinction between data in central memory and data in peripheral files [»babeRL6_1985]

Quote: Galaxy separates syntax from semantics; f(x,y) could be a name, a constant, etc. [»beet5_1989]

Quote: allow anything to be part of a mode declaration, e.g., a field that returns the number of leading zero's [»wegbB_1971, OK]

Quote: replacement and access should be independent of it being a function or table [»shawM3_1976, OK]

Quote: programming languages treat atomic data types as values and compound ones as objects; causes unnecessary confusion [»maclBJ12_1982]

Quote: while a data object exists, it is passed around by uniform reference; procedures do not store the objects themselves

Quote: a language should include objects and a uniform means of referencing them [»ingaDH8_1981a]

Topic: relational database

Topic: database queries, joins, and relational algebra

Quote: the relational model defines relationships in two ways: by symbol matching in joins and by coexistence in a tuple [»kentW_1978]

Quote: every relation is a table, but a table may be a relationship, an entity, or attribute list [»kentW_1978]

Quote: relational model more flexible because relationships defined by joins [»smitKE10_1987]

Quote: relational model is structurally simple; gives a common understanding of data for all kinds of users [»coddEF2_1982]

Quote: in relational data bases, operations on individuals same as operations on sets; these are different in Algol-style languages [»casiRJ9_1983]

Quote: relational database handles placement of data and selection of access paths

Quote: hierarchical, relational, and network models are variations of the data record model [»kentW_1978]

Topic: personal information

Quote: an Agenda item is a single phrase or sentence that represents an idea, task, reminder, fact, etc. [»kaplSJ7_1990]

Quote: an Agenda item or category may have an attached note (additional text); accessible by pointing [»kaplSJ7_1990]

Quote: structure arises out of the grouping of similar items and intergroup relationships; and not from hypertext links between items [»kaplSJ7_1990]

Quote: an Agenda category is an ordered list of items and notes that structure the database; e.g., 'Things to read', 'Errands' [»kaplSJ7_1990]

Quote: Agenda items tend to be filed in only a few places; why filing cabinets work acceptably [»kaplSJ7_1990]

Quote: assigning an item to a category makes an assertion about the item; e.g., that Smith will write the press release

Quote: Agenda categories become the words of a language for describing information and its interrelationships [»kaplSJ7_1990]