101 ;;Quote: use data records for efficiency; a data record is not a natural model

102 ;;Quote: much of the meaning of a data record is supplied by users and procedures

102 ;;Quote: records imply everything has only one type with a rigid structure

103 ;;Quote: name of a relationship is not part of a data record; nor is the type of an entity

107 ;;Quote: data records work best when all entities of a type have the same characteristics

108 ;;Quote: unstructured information by 'comments' field

109 ;;Quote: represent relationships within one thing's record or as a separate record

114 ;;Quote: CLIENT_ADDRESS_EMPLOYER relation is a combination of RESIDES and EMPLOYED relations; the original relationships and roles are lost

124 ;;Quote: concepts of record, relationship and entity are mixed up

127 ;;Quote: distinct entities do not need to be distinguished, e.g., several vacant jobs

131 ;;Quote: objects with qualified names should be entities independent of the qualifier

133 ;;Quote: composite names convey additional information; e.g., state and country for a city

135 ;;Quote: data records useful for providing a view of data and for providing authorized access to a data subset

138 ;;Quote: every relation is a table, but a table may be a relationship, an entity, or attribute list

138 ;;Quote: the relational model defines relationships in two ways: by symbol matching in joins and by coexistence in a tuple

139 ;;Quote: joins match symbols (e.g., employee number) instead of entities (e.g., an employee)

153 ;;Quote: a reducible record can be decomposed such that the reconstruction does not introduce spurious data

158 ;;Quote: if a relationship is an entity then should have an object for the relationship

159 ;;Quote: in pseudo-binary model; relationships are nodes and arcs are roles

164 ;;Quote: named relationships hides their representation from the user

166 ;;Quote: with named relationships can not follow paths implicitly defined by the data

168 ;;Quote: can model ordered sequences by a sequence number or a precedes relationship

169 ;;Quote: define existence by membership in an existence list for some type

172 ;;Quote: system can detect existence of objects (surrogate, representative, thing) and can interrelate them

172 ;;Quote: objects are simple, symbols, relationships, or executables

173 ;;Quote: the type of an object (simple, symbol, etc) is stored with the object

173 ;;Quote: the UserInterface between computer and user consists of symbols, i.e., character strings

174 ;;Quote: is the arc between a relationship node and an object node also a relationship?

174 ;;Quote: use executables for semantic constraints on roles and relationships

176 ;;Quote: a link requires the continued existence of its objects; what happens when object is deleted

176 ;;Quote: executable objects in a database can enforce constraints or generate implications

176 ;;Quote: an executable object should be distinct from its source text

177 ;;Quote: an executable object should be connected into the web of information

180 ;;Quote: typing by has-type relationship to objects of type TYPE

181 ;;Quote: naming by two objects, a nameless object which is a surrogate for a real one and a symbolic object which is its name

181 ;;Quote: a thing does not have to have a unique name or any name at all

181 ;;Quote: babies do not have names right after birth but data still gets recorded about them

184 ;;Quote: existence by membership in list of objects referenced by symbols

190 ;;Quote: the existence of all entities, symbols, relationships should be explicitly asserted

191 ;;Quote: a data model includes symbols, an alphabet, numbers, orderings, equality, type conversions, data type acceptance tests

192 ;;Quote: data descriptions and data should reside in the same repository

193 ;;Quote: theories distinguish phenomena but tools get a job done by intermixing fragments of phenomena

193 ;;Quote: theories tend to be complete but tools only incorporate what is useful

194 ;;Quote: tools are available, cost-effective, efficient, reliable, easy to use, and guaranteed

195 ;;Quote: different data models probably arise from different ways of perceiving information

196 ;;Quote: life and reality are amorphous, inconsistent, non-rational

196 ;;Quote: rational views of the universe are idealized models which approximate reality

198 ;;Quote: to many animals, smell defines the existence and nature of a thing

201 ;;Quote: Hopi call insect, airplane and aviator the same; but Eskimos have many words for snow

202 ;;Quote: though no two people perceive reality the same, views overlap enough to allow cooperative work

202 ;;Quote: there is no absolute definition of truth and beauty; but for purposes of daily living, we reconcile divergent views

203 ;;Quote: modern systems interact with many people for many purposes, need correct assumptions