the
scientific
landscape
 modeling 
representation
(models, semantics)
 semiotics 
logic &
reasoning
complexity & metrics sets & numbers
categories
relations
objects
wholes & levels
meaning
meta
linguistic
glossary
formalization
& symbol
manipulation
components & datatypes relations
truth & reality algebras
Location: http://www.cs.mun.ca/~ulf/gloss/rels.html. By Ulf Schünemann since 2002. Please mail any comments.

Relations

See the status of relations
  1. What Is A Part Relation And What Is Not?
  2. What's an "Intensional Relation"?
  3. Comprehensive Taxonomy
  4. Taxonomy Proposals
[Ass] Donald G Firesmith, B Henderson-Sellers: Clarifying Specialized Forms of Association in UML and OML; JOOP 11(2) 1998.
[BSpec] Haim Kilov: Business specifications: the key to successful software engineering; Prentice-Hall 1999.
[Caus] Paolo Terenziani: Towards a causal ontology coping with the temporal constraints between causes and effects; 847-863: Int J Human-Computer Studies 43; 1995.
[COMMA] Brian Henderson-Sellers, Donald G Firesmith: COMMA: Proposed Core Model; JOOP 9(8) Jan 1997.
[CompoAD] Franco Civello: Roles for composite objects in object-oriented analysis and design; OOPSLA'93.
[FO] Nicola Guarino: Formal ontology, conceptual analysis and knowledge representation; 625-640: Int J Human-Computer Studies 43; 1995.
[Kolp] M Kolp: A Metaobject Protocol for Integrating Full-Fledged Relationships into Reflective Systems; PhD thesis; INFODOC, Universite Libre de Bruxelles, Belgium; 1999.
[Midwinter] Peter Gerstl, Simone Pribbenow: Midwinters, end games, and body parts: a classification of part-whole relations; 865-889: Int J Human-Computer Studies 43; Academic 1995.
[NatSR] Roger Chaffin, Douglas J Herrmann: The nature of semantic relations: a comparison of two approaches; 289-334: in Martha Walton Evens: Relational models of the lexicon: representing knowledge in semantic networks; Cambridge 1988. [OML] B Henderson-Sellers, Donald G Firesmith, Ian M Graham: OML metamodel: Relationships and state modeling; JOOP 10(1) 1997.
[OML/RR] Donald G Firesmith, B Henderson-Sellers: Upgradig OML to Version 1.1: Referential Relationships; JOOP 11(3) 1998.
[OPEN/CC] B Henderson-Sellers: OPEN Relationships - Composition and Containments; JOOP Nov/Dec 1997.
[OPEN/R] B Henderson-Sellers: OPEN Relationships - Associations, Mappings, Dependencies, and Uses; JOOP 10(9) 1998.
[OSA] David W Embley, Barry D Kurtz, Scott N Woodfield: Object-Oriented Szstems Analysis: A Model-Driven Approach; Yourdon 1992.
[ProbPW] Madelyn Anne Iris, Bonnie E Litowitz, Martha Evens: Problems of the part-whole relation; 261-288: in Martha Walton Evens: Relational models of the lexicon: representing knowledge in semantic networks; Cambridge 1988. [TaxPW] Morton E Winston, Douglas Herrmann: A Taxonomy of Part-Whole Relations; 417-444: Cognitive Science 11; Ablex 1987.
[UML] OMG Unified Modeling Language Specification 1.4; 2001.

What Is A Part Relation and What Is Not?

«Some authors list kinds of association that are easily confused with aggregation but should not be modeled as such (e.g. topological inclusion, classification inclusion, attribution, attachment and ownership ...). For example, Finger belongs to Hand is an aggregation, but Ring belongs to Finger is not.» [ORM8].
«The relationship of a whole to its proper parts is importantly different from that of a set to its members, though David Lewis has recently argued that a set may be regarded as the mereological sum of its unit subsets» [x].

However, it is fact that "part" is used in language not only for "real" part relations, but also for class inclusion. [ProbPW] made an analysis of Webster's Seventh Collegiate Dictionary: «[T]wo major types of part-whole relation appear very directly in the dictionary definitions of nouns: functional part and segmented whole. ... Two additional types of part-whole relationships appear in the definitions: collection-element and set-subset. These tend to be expressed by some other term such as member, or, when focus is on the whole, by including, comprising, or containing»

[TaxPW] compared the three inclusion relations class inclusion, merological (part-whole) inclusion, and topological inclusion. There seems to be a logical ordering of the different inclusion relations, so that syllogisms with mixed inclusion relations have to conclude with the "smaller" relation: class > merological > topologic [TaxPW]:
class + mero => mero: Wings are parts of birds + Birds are creatures => Wings are parts of creatures.
class + mero => mero: Pies are a kind of dessert + Desserts are partly sugar => Pies are partly sugar.
mero + topo => topo: The wheel is part of the bike + The bike is in the garage => The wheel is in the garage.
class + topo => topo: Socrates is in Athens + Athens is a city => Socrates is in a city.

Some cases of relationships could be class inclusion as well as meronymy: frying is part of / a type of cooking. Honesty is part of / a type of virtue. A chair is a kind of furniture / an item of furniture [TaxPW]
But not: A robin is part of a bird. A wheel is a kind of car [TaxPW].
Note that also not: My-yesterday's-frying is a type of my-yesterday's-cooking.

[NatSR] present two studies where subjects had to sort examples of semantic relations into groups by similiarity. [NatSR]'s first study comprised undergraduates and 31 semantic relations. The major division was between contrast and non-contrast relations. The divisions on proximity level 0-10% were
contrast relations
separates at 5% proximity
attribute similars
... see below
ca 2.5%
proximity
"logic"
(based on property)
separates at
5% proximity
class inclusion, see below
similarity
separates at 8% proximity
necessary & invited attribute
... see below
"pragmantic"
separates at
7% proximity
case relations, see below
part-of relations
separates at 9% proximity
measure & ingredients
... see below
In a second study, [NatSR] asked 35 subjects to sort (examples of) 31 relations similar to part/whole relations.
ca.
8%
ca.
10%
ca.
11%
representation & plan, separates at 25% proximity
  • actitity-plan: banquet-menu, meeting-agenda, course-outline
  • object-representation: person-portrait, wiring-diagram, event-report
  • class inclusion, separates at 31% proximity -> see below
    meronymic
    ca. 13%
    stuff (constituency) separates at 20% proximity -> see below
    separates
    at 17%
    mass-portion (homeomerous) separates at 23%
  • mass-measured portion: pie-slice, loot-cut, land-parcel
  • mass-natural tiny pieces: salt-grain, snow-flake, wood-sliver
  • ca.
    19%
  • measure-unit: mile-yard, gallon-pint, pound-ounce
  • ca.
    21%
    organizational separates at 22%
  • organization-unit: UN-delegation, army-batallion, college-registry
  • membership, separates at 29% proximity -> see below
  • spatial, separates at 23% proximity -> see below
    ca.
    21%
  • object-relational location: room-corner, box-side, mountain-foot
  • integral object- component
    separates at 22%
    spatial
    integral
    separates
    at 23%
    functional location-component: kitchen-refrigerator, classroom-desk, store-cash register
    mobile object-component, separates at 27% (the two artefacts at 29%) into:
  • living thing-component: ivy-leaf, tulip-petal, lion-mane
  • telephone-dial, typewriter-key, camera-lens
  • cup-handle, pencil-eraser, fork-prong
  • dramatic event, separates at 23% into
  • dr. ev.-section: book-chapter, symphony-movement, opera-act
  • dr. ev.-content: joke-punchline, story-plot, film-climax
  • event-feature, separates at 22% into
  • event-actor: rodeo-cowboy, wedding-bride, trial-defendant
  • event-prop: banquet-food, birthday-present, Halloween-candy
  • named time-occasion: Easter-Good Friday, February-Valentine Day, summer-July 4th
  • stages
    non-"has"
    separates
    at 13%
  • process-phase: launch-liftoff, moon-full, growing up-adolescence
  • actitivity-phase, separates at 34% into
    • continuous activity: driving-steering, cycling-pedaling, swimming-kicking
    • discrete activity: shopping-buying, traveling-arriving, gardening-digging
  • object-attribute: tower-height, food-taste, bed-comfort
  • disposition-stuff: burn-coal, curdle-milk, evaporate-water
  • [NatSR] reports of a third study, where 15 subjects had to form sentences with thirty-one part-terms and then sorted by 45 subjects by similarity.
    15% stages (part of process): "phase" vs. "stage" (37% similar)
    17% part of scripts describing an event: "role"
    part of place
    27-28%
  • "zone", "region", "area" (38-40% similar)
  • "section"
  • "division"
  • 19% homeomerous
    21%
  • "segment"
  • 24-25%
  • "fraction"
  • 29-30%
  • "fragment"
  • "chip"
  • "piece", "slice" (37% similar)
  • "scrap", "limp", ("grain" ~ "drop") ~ ("sliver" ~ "bit") (33-37% similar)
  • measurement: "portion", "percentage", "share" (25% similar)
    non-homeomerous
    27-28%
    "part", "member", "item", "feature", "element" ~ "factor" (28%), "ingredient" ~ "component" (32%) (similarity increasing from 21% to 25%)


    What's an "Intensional Relation"?

    The term "intensional relation" occurs in several contexts for different(?) things:

    Comprehensive Taxonomy

    The following taxonomy combines several classifications of relations into one single structure. It includes [TaxPW]'s and [Midwinter]'s proposals, [Parts]'s considerations, [NatSR]'s similarity experiments, [ProbPW]'s dictionary data, and the relations provided by object-oriented modeling techniques [UML, OML]. Classes proposed by different authors where merged to one based on their identity or close similarity (based on the examples provided).

    1. effective relations, action/event/change-based relations (coupling/binding/organic/existential relations, case relations, causal relations, flow or transitional relationships)
    2. dependency relations (abstraction, realization, refinement, derivation, usage, ...)
    3. semiotic relations (pragmatic relations, semantic relations, syntactic relations)
    4. mediated/subjective/conventional/habitual relations (representation relations (meaning, model, plan), ownership)
    5. topological & morphological relations (attachment, containment, overlap, ...)
    6. property-based relations (contrast relations, attribution, logical relations: similarity relations, class inclusion: member/class, generalization)
    7. mereologic inclusion, parthood, part/whole (made-of: stuff, is-a-part-of (aggregation, configuration, membership ...); selection/segment)

    All underlining is added emphasis.

    1. Effective relations, action/event/change-based relations
        navigation bar: Coupling
      1. coupling relations / bonds
      2. quantity-dependency system view
      3. object change propagation systems
      4. object constraint programming
      5. [MB3 261] «Definition 5.32 Two different things are bonded (or linked or coupled) together iff at least one of them acts upon the other. In symbols: If x and y are things, then
        Bxy =df x |> y or y |> x
        where «x acts on y, or x |> y for short, iff, for some state function H determining the trajectory h(y|x), h(y|x) =/= h(y)» [MB3 258],
        where h(y) = {<t,G(t)> | t S(f) }
        and h(y|x) = {<t,H(t)> | t S(f) }
        with state function G relative to a reference frame f whose time-scope is S(f), and a state function H that depends on y's own state function G as well as on x's own state function F.
        [MB3 262] «In principle [the set of bonds] includes couplings of all n-arities - dyadic, triadic, and so on. In practice the dyadic or binary bonds are by far the most important.»
      6. Coupling relations / Bonds = Organic relations = Existential relations between things
        [MB3 101f] «The relation of being greater (or older or richer or worse) than is "external" to its relata in the sense that it does not alter them and does nothing to keep them together or even apart. Similarly with all the spatiotemporal relations such as those of contiguity, betweenness, precendence, and simulataneity: they do not affect their relata. In general, all comparative (order) relations and all equivalence relations are of this kind, i.e. nonbinding. Not so the hydrogen bond or a relation of econmic bondage or of cultural influcence: these "make a difference" to the individuals so related: they are in a way "internal" to them. This distinction, ignored by Hume and his followers, was pointed out by Peirce (c. 1909, 6.318), who wrote of "existential relations" or relationships in contrast to mere relations. It was also a favorite with Whitehead (1929) and Woodger (1929) who called them `organic relations' ...
        Binding relations, i.e. those that "make a difference" to the relata, may be characterized as follows. Two entities x, y S are bound (or connected or coupled) iff some changes in x are accompanied (or preceded or followed) by some changes in y. ...
        One mistake stemming from overlooking the above distinction concerns the relation between being connected and being a part. Clearly any two things with a common part are connected. But ... things need not overlap in order to be coupled. For example, the feudal baron and his serf are connected without having any common part.»

      7. Case relations cluster [NatSR] I between agent | action | object
        navigation bar: Dataflow
      8. agent/thing relation
      9. dataflow system models
      10. dataflow models of computation
      11. pipes & filters architecture
      12. ca. 12%
        proximity
        actions
        separates at
        28% proximity
      13. action/instrument: cut/knife, drink/cup
      14. action/recipient: sit/chair, hunt/prey
      15. agent
        separates at
        20% proximity
      16. agent/action: dog/bark, artist/paint
      17. agent/thing, separated at 34% proximity into:
        - agent/instrument: farmer/tractor, soldier/gun
        - agent/object: baker/bread, sculptor/clay
      18. navigation bar: State-Transition
      19. transitional relationship
      20. state/event system models
      21. Flow [UML] = transitional relationship [OML] between states | snapshots - temporal sequence of an object's states / of snapshots of an object.
        OML: The transition from state A (before) to B (after).
        UML: «become» between snapshots of the same object at different times
        UML: «copy» between objects ???

        NB: Flow relationships are not causal relations - the cause for a transition is the input, the effect is the output; even epsilon transitions mean non-deterministic behavior, and not that the pre-state causes the post-state.

      22. Causal relations [Caus] between situations | states | events - connect causes with effects.
        They can be classified by the temporal relation between cause and effect:
        1. general causation: cause before effect
          • without threshold (started-by, starts, equal, finshed-by, mets, overlaps, contains, or before)
          • with threshold (finished-by, meets, overlaps, contains, before)
        2. one-shot causation: the cause allows the effect to begin, and the effect can outlast the cause
          I ran a mile in less than 4 minutes CAUSED I received a prize
          • without threshold (starts, meets, overlaps, before): water-drop-formation : rain : water-on-soil
          • with threshold (overlaps, meets, before)
          • culminated event causation (meets, before): switch-light-on : light-on
          • production causes product: droplet-formation : droplets, cloud-formation : clouds
        3. continuous causation: presence of the cause is require in order to begin and sustain the effect
          • without threshold (started-by, equal, finished-by, contains): sun-radiation : evaporation, warm-air : air-raise, steam-condensation : droplet-formation
          • process with threshold (finished-by, contains): air-cooling : steam-condensation, droplet-formation : cloud-formation, running : lactic-acid-production
          • mutually sustaining causation = cause and effect are contemporaneous (equal): evaporation : water-steam-formation, air-rise : air-expansion, air-expansion : adiabatic-cooling

      23. Indexical sign meaning relation between things | processes - a kind of causal relation???: smoke-fire

    2. Dependency [UML] (is this the "dynamic branch" of referential relationships in [OPEN/CC]?):
    3. Semiotic relations
      1. Pragmatic relations between signs and sign-users
      2. Semantic relations between signs and what they stand for (for the sign-users)
        -
        iconic (see at similarity relations)
        - indexical (see at causal relations)
        - symbolic (see at representation relations)
      3. Syntactic relations among signs
    4. Mediated/subjective/conventional relations
      1. Ownership [TaxPW] = "has" = "belongs to" but not "part" [NatSR]:

        money/millionaire, copyright/author, bicycle/Jenny [TaxPW]
      2. Representation & Plan [NatSR] separating at 25% proximity into:
    5. Topological & Morphological relations
      1. Attachment [TaxPW] = "has [attached]"/"is attached to"
        earring/ear, antenna/chimney, hook/fishing line [TaxPW]
      2. Topological inclusion = "is-in" [TaxPW] = Containment: contents/container [OPEN/R]:
        «The contents often have an outside existence independent of their location within a container. ... [A] container can be empty ... [A] container typically does not use» the containment relationship for interacting with its contents [OML/RR].
        the wine is in the cooler, the prisoner is in the cell, the meeting is in the morning [TaxPW]
      3. Topological overlap
      4. ...

    6. Property-based relations
      1. Contrast relations cluster [NatSR] I
        ca. 5%
        proximity
        ca. 15%
        proximity
        ca. 25%
        proximity
      2. contraries and antonyms.
        The subdivisions had proximity levels 35-40%, here ordered in decreasing proximity:
        • contradictory antonyms: alive/dead, male/female
        • contrary antonyms: old/young, happy/sad
        • directional antonyms: front/back, left/right
        • reverse antonyms: attack/defend, buy/sell
        • assymmetric contraries: hot/cool, dry/moist
      3. incompatible terms: happy/morbid, frank/hypocritical
      4. pseudo-antonyms: popular/shy, believe/deny
      5. (contrast within?) attribute similars: rake/fork, painting/movie
      6. Inherence (philosophy): - The inherence relation relates properties to substance of an object.
        = Attribution [TaxPW, OML] - The attribution relation relates an object with a "descriptive attribute" [OML]
        = AttributeLink [UML]
        towers are tall, the joke was funny, coal burns [TaxPW]

        Distinguishing between attribution and whole-part association in object-oriented modeling requires attention [CompoAD]: «Are the start-point and end-point attributes or parts of a line segment? The answer depends on the context: are the delimiting points used just as information holders, to store and provide access to their coordinates, or do they have behaviour that can be invoked by their LineSegment or other objects? In the latter case the two points should be modelled as part objects.»
      7. Logical relations [NatSR] (or structural relations) «contribute to the taxonomic structure of the domain» [FO 635]. (in AI: unary: concepts, kinds, types; binary: roles, attributes, slots). Non-logical relations «provide additional information on already identified objects» (in AI: unary: properties, qualities; binary: constraints).
        1. Similarity relations cluster [NatSR]
          ca. 8%
          proximity
          ca. 18%
          proximity
        2. synonymy: car/auto, buy/purchase
        3. ca. 25%
          proximity
        4. dimensional similar: smile/laugh, annoy/torment
        5. action subordinate(similar?): talk/lecture, cook/fry
        6. ca. 17%
          proximity
        7. necessary attributes: bachelor/unmarried, tower/high
        8. invited attributes: food/tasty, cut/knife
        9. Iconic representation person-portrait, wiring-diagram - a similarity relation? - cf. representation relations
          navigation bar: Class Inclusion
        10. relations
        11. inclusion diagrams
        12. in information engineering
        13. arrows in class diagrams
        14. Class inclusion = "is-a" = "are [type/kind of]" [TaxPW] = definitional relationship [OML] (= Aristotle's essential relations? cf definitions):
          Such a relation defines some entity A based on an existing entity B [OML].
          1. Member/class (inclusion/definitional relationship between entities of different categories) «Membership in a class ... is determined by similarity to the other members on one or more intrinsic property» [TaxPW].
            by property by essence / accindent (?)
            According to [TaxPW], Wierzbicka (1984) distinguishes
            1. taxonomic classes based on overall physical similarity (bird, flower)
            2. functional classes based on similarity of function (toy, weapon)
            3. heterogeneous classes based on similarity of function and origin (vegetable, medicine)
            • Instance-of [OML] = Instance/kind [Midwinter] = "of" :
              a glas of water, hundred grams of rice, the tail of an ox, two apples [Midwinter]
              object A instance-of class B [OML]
            • conforms-to [OML]:
              class A conforms-to ???interface??? B
          2. Generalization [UML] -> induces hyponymy relation between class-names (inclusion/definitional relationship between entities of the same category):
            • Subset/set [ProbPW]: apple/fruit, fruit/food [ProbPW]
            • a-kind-of (specialization inheritance) [OML]
            • subtype (specification inheritance) [OML]
              cars are vehicles, roses are flowers, theft is-a crime, fear is-an emotion [TaxPW]
            • implementation inheritance [OML]
          The class inclusion relations cluster, distinguished by different kinds of entities [NatSR] I
          study II ca. 31% proximity
        15. states: polio/desease, fear/emotion, divorced/martial-status
        16. ca.
          33%
        17. activities: football/sport, theft/crime, ballet/art
        18. natural objects: horse/animal, rose/flower, copper/metal
        19. artifacts: car/vehicle, spoon/utensil, hammer/tool
        20. study I ca. 12%
          proximity
          ca. 27%
          proximity
          ca.
          30%
        21. actitity subordinates: chess/game, theft/crime
        22. ca.
          33%
        23. state subordinates: polio/desease, fear/emotion
        24. functional subordinates: chair/furniture, hammer/tool
        25. perceptual subordinates: horse/animal, rose/flower
        26. "geographical"
          ca. 24%
          proximity
        27. geographic subordinates [member/class]: Russia/coutry, New Jersey/state
        28. place: Hamburg/Germany, China/Asia

    7. Mereologic inclusion: parthood, part/whole [TaxPW] = "is-part" = "[part] of":
      navigation bar: Wholes and Parthood
      wholes & system composition levels part-whole relations
      different kinds of parthood and compositeness
      aggregates (concrete)
      =/= sets (conceptual)
      ontological status of wholes vs. parts
      holism, atomism (allied with reductionism), systemism
       
      «To say that something is a part is to say that it is something which is part and has some further addtional properties. It is not altogether easy to say what this 'extra' consists in ... For artefacts, something is a part when it is a component of a thing, a piece typically existing as a unit before the whole artefact assembled, capable of unitary replacement, capable of surviving dismemberment of the whole, perhaps in addition fulfilling a unitary function. For things other than aretfacts this meaning is inapplicable, and if sth is a part it may be because it is a salient or prominently delimited part, or because it is functionally unitary, like an organ. But 'part' does not normally mean 'component' where the whole is not created by assembly, or at least ... where it is not unitarily replaceable. Since, then, a component or unitary part is part of something satisfying certain further conditions, we feel entitled to follow Sharvy in saying that mereology (part-whole theory) is as such concerned with the wider or weaker notion of 'part'. The boundaries of the stronger concept (or concepts?) are harder to draw ... » [Parts 235]
      by homology by "part-of" patterns
      [Manuel Kolp: Integrating Aggregation Mechanisms into the CLOS Metaobject Protocol; 1997?]
      1. Aggregation: parts are of different kinds
      2. Association: all parts are of the same kind
      3. Recursion: all parts are of the same kind as the whole
      There are four different forms of part-of (in the context of made-of) [Part 234f]:
      "b is part of a" when b is a mass or an individual
      "b are part of a" when b is a plurality
      "b is a part of a" when b is an individual
      "b are parts of a" when each of b is a part of a
      «As Sharvy has pointed out 'are part of' is the plural of 'is part of' whereas 'are parts of' is the plural of 'is a part of'. ... The fact that we can use (1) even for singular count nouns [not just masses] suggests that, among individuals, there is some difference between the 'is part of' and the 'is a part of' relations, as these find expression in ordinary language. And indeed there is a difference: whatever is a part of something is also part of it, but not vice versa. The front half of a car ... is part of, but not a part of, the car.» [235] (continued here).

      The part/whole relations cluster [NatSR] I
      ca. 9%
      proximity
      a-part-of
      ca. 19%
      proximity
      ca. 30%
      proximity
    8. organization: admissions/college, corps/army
    9. = (individual)
      is a-part-of
      = made-of(?)
    10. functional location: stove/kitchen, dining room/house
    11. ca.
      24%
    12. functional object: car/engine, leaf/tree
    13. ca.
      29%
    14. group: singer/choir, professor/faculty
    15. collection: tree/forest, ship/fleet
    16. part-of
      ca. 12%
    17. ingredients: wood/table, cheese/pizza
    18. = (mass) is part-of
    19. measure: yard/mile, minute/hour
    20. = (individual) is part-of
      1. made-of = composed-of [Parts 232]:
        by category
        A linguistic analysis of possible categorial combinations in the common sense notion of "made-of" aka "composed-of" [Parts 232]
        category of wholeindividualmasscollection
        can be made of
        1 individual this chair/this box - is not composition but "serves-as" or "constitutes" ?some gold/one gold atom? ?committee/one person?
        individuals wall/stones gold/gold atoms pack/wolves
        1 individual+mass(es)toffee-apple/an apple+some toffee ?some martini / some gin+some vermouth+one olive? ?
        individuals+mass(es)fruit-cake/currants+some dough blood/plasma+blood cells toffee-apples/apples+some toffee (correct example?)
        mass(es) sweater/some wool dough/flower+water snowballs/some snow
        collection ? ? ? leage of clubs/several clubs
        made-of vs part: can we say "part" for what something is made-of? «What happens if we ... ask after the relation of something to what helps to make it up? In many cases it is natural to speak here of parts. A stone is part of a wall, the toffee is part of the toffee-apple, and so on. Where we have plurality, the currants are part of the cake, the bolld cells are part of the blood. Only when something consists solely of certain individuals does the word 'part' jar, simply because in natural language it means 'proper part'. The wolves are not part of the pack, but all of it. ... But because the wolves are all of the pack ... we are are not entitled to say they are (i.e. are identical with) the pack, because 'the wolves' is a simple plural term referring to just these animals, whereas 'the pack' refers to a group, and the group and plurality, while they here coincide in membership, have different identity conditions. The wolves are the matter of the pack» [Parts 233f]

        1. "(mass) is-part-of" [Parts] = Stuff [TaxPW, NatSR study II] = "[is-partly] [made-of]" [TaxPW] = Ingredients [NatSR study I]
          -- counted as configurational (structural, but not functional) by [OPEN/CC]. Splits with 20% proximity into
          1. object-stuff [NatSR] = "(mass) is-part-of (individual)": lens-glass (lens is made of glass), bike-steel (NB: bike is partly steel =/= the bike has parts of steel) [TaxPW]; table-wood, pizza-cheese [NatSR]; cake-dough [Parts]
          2. mass-stuff [NatSR] = "(mass) is-part-of (mass)": trash-paper, compost-grass, salad-lettuce [NatSR]; blood-plasma; dough-water [Parts]; water-hydrogen, martini-alcohol [TaxPW]; cappucino is partly milk [OPEN/CC];

        2. "(individual) is-a-part-of" [Parts]
          integral/configurational: parts play roles membership
          Aggregation [OSA, OPEN/CC]: The parts bear a functional and/or structural (="configurational" [OPEN/CC]) relationship to one another or to the object they constitute.
          = Component/Complex [Midwinter]:
          There are spatio-temporal and/or functional relations between part and whole (can be heterogeneous). Such relations «have in common a certain role the part plays with respect to the whole. This role is typically characterized by some notion of functionality with might pose certain requirements on the spatial and temporal location of the part within the whole»
          "[part] of": engine/car, plenary session/conference, head/department [Midwinter]
          = Component/Integral object [TaxPW]:
          «Integral objects all exhibit some kind of patterned organization or structure. Their components are also patterned and usually[!] bear specific structural and[!] functional relationships to one another and to the wholes which they compose. These structural relations define the particular natures of integral wholes and their components - components cannot be haphazardly arranged but must be arranged in a particular patterned organization within the whole which they comprise» [TaxPW].
          Membership (Member/Collection [TaxPW, ProbPW] = "belongs to" and "part of" [NatSR] = Element/Collection = uniform compositional structure [Midwinter] = Member/Association = "is-member-of" [OSA]).
          «Membership in a collection differs from componenthood by not requiring that members perform a particular function or possess a particular structural arrangement in relation to each other and to their wholes.» «Classes differ from collections in that membership in a class is determined on the basis of similarity to other members, while membership in a collection is determined on the basis of spatial proximity or by social connection» [TaxPW].
          1. Member/Group = social connection [TaxPW]:
            juror/jury [TaxPW]; student/club [OSA]; singer/choir, professor/faculty [NatSR study I]; brother/fraternity, cow/herd, don/mafia [NatSR study II];
            generic membership: fellow/group, fellow/college, engineer/military group, duke/peerage [ProbPW].
            flock of sheep, gaggle of geese, pride of lions [ProbPW]
          2. By spatial proximity (= [NatSR]'s member/collection ?): «In its simplest form this schema denotes a physical collection or aggregate of objects that are spatially close together, but have no particular structural organization» [ProbPW].
            ship/fleet, tree/forest, book/library [NatSR study I, II]
            card/deck, tree/forest (NB: a particular tree being part of a particular forest requires proximity) [TaxPW]
          3. Some of the individuals subsumed under a plural noun:
            two of the apples in the basket, one of Mary's three visits to Paris [Midwinter]
          a/b separate at 29% proximity [NatSR study I & II]
          role in the whole's function (± structure) roles in spatio-temporal structure (not in function)
          Component/Assembly [CompoAD] «In a functional [whole-part association] the part is conceptually included in the whole because of structural and functional connections that make it possible for it to contribute to the function of the whole. ... We call the parts in a functional WPA components ... We call the whole object an assembly, although no physical existence is implied» [CompoAD]
          = Functional Part/Whole [ProbPW]: «[T]the part [is viewed] as a functioning unit in a whole, such as an organ of the body or the engine of a car. The part, in this sense, contributes to the whole, not just as a structural unit but as essential to the purposeful activity of the whole» [ProbPW].
        3. [ProbPW]'s discrete (drum/machine, horn/animal, disk/plow, finger/glove, knee/leg) vs. continuous (flame/fire, flesh/fruit, green/spectrum)
        4. Where the whole is a mobile object-component it separates at 27/29% proximity into [NatSR]:
          - living thing-component: ivy-leaf, tulip-petal, lion-mane [NatSR]
          - assemblies [TaxPW]: car-wheel [TaxPW]; telephone-dial, typewriter-key, camera-lens [NatSR]
          - concrete physical wholes [TaxPW]: cup-handle[TaxPW]; pencil-eraser, fork-prong [NatSR]; toothbrush-bristles [OPEN/CC]
          1. Configuration = non-functional (obvious parts + all equal + structure (eg spatial)) [Midwinter]
            uppermost three books on a heap of books, top of the stack, first element in a chain [Midwinter]
            Why this distinction? A collection's "apples in a basket" are also spatially structured, and "visits to Paris" are temporally ordered
          2. Place/area [TaxPW, OPEN/CC] = Spatial [NatSR] -- counted as configurational (structural, but not functional) by [OPEN/CC] «Like the members of collections, places are not parts by virtue of any functional contribution to the whole» [TaxPW]. Separates at 23% proximity into
            - natural area-place [NatSR]: mountain-peak [OPEN/CC]; desert-oasis; tennis court-baseline [TaxPW]; continent-mountain range, earth-ocean [NatSR]
            - named area-place [NatSR]: Florida-Everglades [TaxPW]; Wyoming-Yellowstone, Caribbean-St Thomas [NatSR]; Texas-Austin [OPEN/CC]
          3. object-relational location [NatSR]: room-corner, box-side, mountain-foot [NatSR]
          functional or not?
          1. with 30% proximity [NatSR study I]:
            • functional location-component: kitchen-refrigerator[TaxPW], house-dining room, classroom-desk, store-cash register [NatSR]
              NB: merges with "mobile object" to "spatial integral object" at 23% proximity [NatSR study II]
            • organization-unit: admissions/college, corps/army [NatSR study I]; delegation/UN, batallion/army, registry/college [NatSR study II]
              NB: merges with "membership" to "organizational" at 22% proximity, and further with "spatial" at 21% proximity [NatSR study II]
          2. non-"has": Feature/Activity (activity-stage) [TaxPW] = process-stage [NatSR]: «is like the integral object-component relationship in that complex activities are structured by means of "scripts" which assign locations to particular subactivities or features ...», but here "X has Y" cannot be used (?"shopping has paying"?) [TaxPW].
            «The process-stage relation is expressed by "part of," but not by "has"» [NatSR].
            process-phase: launch-liftoff, moon-full, growing up-adolescence [NatSR]
            continuous activity: driving-steering, cycling-pedaling, swimming-kicking [NatSR]
            discrete activity: shopping-buying, traveling-arriving, gardening-digging [NatSR]
            dating/adolescence, paying/shopping, bidding/playing-bridge, ovulation/menstrual cycle [TaxPW]
          3. where the whole is a non-physical object:
            • dramatic event, separates at 23% into [NatSR]:
              dr. ev.-section [NatSR] = a representational object [TaxPW]: book-chapter, symphony-violapart, play-part [TaxPW]; book-chapter, symphony-movement, opera-act [NatSR]; film-scene [OPEN/CC]
              dr. ev.-content: joke-punchline[TaxPW], story-plot, film-climax [NatSR]
            • abstract object: phonology/linguistics [TaxPW]
            • organization-member: Belgium/NATO [TaxPW]
            • event-feature, separates at 22% into [NatSR]:
              event-actor: rodeo-cowboy, wedding-bride, trial-defendant [NatSR]
              event-prop: banquet-food, birthday-present, Halloween-candy [NatSR]
            • named time-occasion [NatSR]: Easter-Good Friday, February-Valentine Day, summer-July 4th [NatSR]

      2. Selection/whole = Segment/whole [ProbPW] = "(individual) is part-of"(?) [Parts]:
        An external scheme is applied to (the (atomic) parts or amorpheous substance of) a whole to pick out some selection - this selection is a part of the whole.
        «One cannot have a piece of pie before the pie exists, nor does a section of fruit exist without reference to the whole fruit» [ProbPW]
        There are many variations of this principle:
        • Natural segments: «In some cases the part has a predetermined size and shape. For example, we find naturally occuring segments, as in a grapefruit or layers of mica schist» [ProbPW].
          But how is this compatible with "selection by an external scheme"?
        • Portion/Whole [Midwinter] = generic evaluative/functional selection [ProbPW]: For wholes that have parts (unlike amorpheous wholes like "water", "gold", etc.), a portion «is constructed by using a property dimension to select parts out of the whole ...» [Midwinter]
          the red parts of a painting, the annoying parts of the evening television program, all people who are female and over fifty
          Portions of complexes may coincide with a component: the wooden part of a knife (= handle ?)
          NB: the steelen part of the bike =/= the steel of the bike (stuff) [Midwinter]
          fat is the best or richest part, elite is the choicest part, grip is the part by which sth is grasped, extension is the part constituting an addition [ProbPW]
        • Segment/Whole [Midwinter] = spatio-temporal selection [ProbPW]: A segment «is a part that results from the application of an external scheme [to any kind of object/whole] ... One characteristic of segments is that they may have vague boundaries ...» [Midwinter]
          the upper right corners of the cube [Midwinter]
          Segments of complexes may coincide with a component: The upper part of the house = roof(?). The beginning phase of the story = introduction(?) [Midwinter]
          a portion identified as significant part: gulf/ocean, knee/garment, ford/body-of-water, echo/wave, light/range [ProbPW]
          measured part of temporal/spatial sequence: episode/series, hour/day, evening/day [ProbPW]
          generic locative selection: front is forward part, interior is the inland part, height is the highest part [ProbPW]

          portion/mass [TaxPW] = homogeneous whole [Midwinter] = masses or amorphous wholes [ProbPW]:
          If the object has no obvious parts (hence often named by mass nouns), then segments are the only parts which the object can be said to have.
          Portions of unspecified masses, like "glass of water", are in instance/kind relationship (see above); the mass must be (generically) individuated to have a part-of relationship [Midwinter].
          • Piece/Whole (destructively obtained shaped portion): «Pieces are like portions of masses in having arbitrary boundaries and in lacking a functional relation to their whole. They are unlike mass-portions, however, in not always being homeomerous» [TaxPW]. «A slice of bread, although not naturally occuring, also connotes a partiuclar shape, size and thickness. A piece of pie generally implies a consistent shape and maximum size (that is, less than a quater of the whole)» [ProbPW].
            by cutting up a typewriter we obtain pieces (parts) of the typewriter [TaxPW]
            slice/pie [TaxPW]
          • shaped portion:
            this hunk is part of my clay [TaxPW]
            [actually instance/kind according to Midwinter] grain of salt, yard/mile [TaxPW]
            [actually instance/kind according to Midwinter] pile of sand, bunch of pebbles [ProbPW]
          • Quantity/Mass [Midwinter]: Selection from a mass by a quantity, no shape implied. «Masses ... can be given boundaries ... by measurement» [ProbPW].
            «Because the portions of masses are arbitrary, we can divide and apportion masses by means of standard measures such as inches, ounces, gallons, hours, and so forth» [TaxPW].
            "some amount of a certain <mass noun>": hundred grams of the rice in the saucepan, five minutes of a soccer game, the majority of the vote [Midwinter]
            [instance/kind according to Midwinter] cup of rice, pail of sand, inch of ..., ... [ProbPW]
      «These different stances with respect to aggregation [in [6KC]] are somewhat reminiscent of the different modeling positions with respect to null values. Although over twenty kinds of null have been distinguished in the literature, ...» [ORM8].

    Taxonomy Proposals

    In order not only to have a comprehensive taxonomy but also to see who contributed what and how it was called, here is the (incomplete) list of taxonomies proposed by different authors:

    [OPEN/R] "Connexions" are classified into:

    1. "definitional connexions" = generalization
    2. "referential connexions":
      1. "generic association relationships"
        • "existence dependency" (as in [K&R:IM])
        • TBD association (as in UML)
        • "containment" = topological inclusion
        • "meronymic relationships" = parthood:
          - "aggregation" = configurational parthood
          - "membership" = nonconfigurational parthood
      2. "functional dependency": refinement, trace, binding, uses/using (K&R's reference)
    3. "transitional relationships"
    4. "scenario relationships"

    [Kolp 37] Seven "Generic Relationships":

    1. Generalization relates a superclass to subclasses (e.g., person and employee)
    2. Materialization relates a class of categories (e.g., models of cars) and a class of more concrete objects (e. g., individual cars)
    3. Aggregation forms composite objects (e.g., car) from component objects (e.g., body and engine)
      «Aggregation is generally defined as an abstraction mechanism by which a relationship between objects is considered a higher-level (aggregate) object [MPM92, SS77]. In fact, two versions of aggregation coexist in the literature:
      1. the general version, through which an entity is analyzed in terms of its constituent parts. For example, a relation schema in the relational model is an aggregate of (attribute-domain) pairs.
      2. an abstraction process involving a relationship with additional specific semantics to characterize various kinds of dependencies between parts, or component objects, and aggregate, or composite objects [KL89] (...). This richer version is sometimes called part-whole [WCH87] or simply part relationship [HGP92].»
    4. Grouping relates a member class (e.g., players in a team) and a grouping class (e.g., teams)
    5. Ownership relates an owner class (e. g., persons) and a property owned (e. g., cars)
    6. Viewpoint represents partial information about a class viewed from a particular standpoint
    7. Generation represents processes that lead to the emergence of new output entities from input entities

    [BSpec] "Generic Relationships"
    «There are not too many generic relationship types. They are encountered in, and reused by, all applications» [BSpec 256].

    1. Composition (hierarchical/not, ordered/not, fixed/variable):
       [components]---[C>---[composite] 

      «A composite entity "consists-of" (or, is an "aggregat of") component entities» [BSpec 272].
      «A COMPOSITION relationship may be represented as a relation between the source type (composite) and the target type (set of component types). In this case, the source type is elementary, and the target type is not. An instance of the composite type corresponds to a set of instances for each of its component types.» [BSpec 256]
      1. Assembly «The existence of a composite instance for the ASSEMBLY implies the existence of at least one corresponding component instance» [BSpec 274].
      2. Subordination «The existence of a component instance for the SUBORDINATION implies the existence of at least one corresponding composite instance» [BSecp 274].
      3. Package «[T]he PACKAGE is is the only generic relationship for which the existence of an isntance of the relationship is not equivalent to the existence of the paricipating entity instances» [BSpec 274].
      4. List «[F]or the LIST, the existence of a component instance implies the existence of at least one corresponding composite instance, and the existence of a composite instance implies the existence of at least one correspondingin component instance» [BSpec 274].
    2. Dependency = existential dependency
       [dependent]---[D>---[parent] 

      «A DEPENDENCY relationship may be represented as a relation between the source type (parent) and the target type (dependent). Both the source and target types are elementary» [BSpec 256].
    3. Reference (ordinary, reference-for-create) = Viewpoint
       [reference]---[Ref>---[maintained] 

      «A REFERENCE relationship may be represented as a relation between the source type (maintained) and the target type (reference). Both the source and target types are elementary.» [BSpec 256]
      «Reference entity instance may be used both to validate the preconsitions for, and an[?] as information sources for, creating/updating/deleting instances of its maintained entity. Values of some properties of an instance of the maintained ennety should agree with (in the simplest case - but not always! - be equal to) values of some properties of an appropreate instance of its reference entity. When an instance of a reference entity is changed, all corresponding instances of its maintained entity will have to be examined (triggering consitions) and, if necessary, changed» [BSpec 269].
      «A REFERENCE relationship associations a reference entity with a maintained eneity. A reference entity in this relationship represents read-only [emph. added] instances used to determine properties of instance of other, maintained, entities. A reference entity has its own operations (not just read-only) within other relationships, possibly outside of the particular application area. IOW, a particular entity is a reference entity only within the context of a particular REFERENCE relationship. Operations applied to an instance of a maintained entity in a REFERENCE relationship should leave instances of its reference entity unchanged» [BSpec 269].
      Reference for create: «Aftrer the maintained entity instance was created, any change in the property values of the corresponding reference entity instance dies not affect this instance of the maintained entity. IOW, the invriant for the REFERENCE FOR CREATE relationship applies only to the version of the reference entity that existed when the maintained entity was created» [BSpec 269].
    4. Symmetric Relationship
       [participants]---[S>---[symm. relsh. object] 

      «A SYMMETRIC RELATIONSHIP may be represented as a relation between the source type (symmetric relationship object) and the target type (set of participating--regular--entity types). For this relationship (unlike, eg. the COMPOSITION relationship), the number of elements in the set must always be more than one; if it is equal to two, the SYMMETRIC RELATIONSHIP is traditionally called "binary" ...» [BSpec 256]
    5. Subtyping (exhaustive/not, overlapping/not)

    [OSA] "Relationship Sets" are classified into:

    1. Aggregation
    2. is-member-of relationship set (member/association) [OSA 46]: «We use the is member of relationship set to form a set of objects that we wish to consider as a single object.» «The object class whose objects are sets is called the set class or the association, and the object class whose objects are members is called the member class or the universe. [The universe from which the association takes a subset]» «The set class may contain more than one set with the same membership. In our school club example, a physics club and a chemistry club might consist of the same group of students. Each object in a set class has its own identity independent of the members that belong to it.»
    3. ...

    Ulf Schünemann 111201, 301202