Skip to content

Instantly share code, notes, and snippets.

@scritur
Forked from nichtich/notes.md
Created April 27, 2016 13:17
Show Gist options
  • Save scritur/b3bc5f1c5323efc68ba67cea910cc27c to your computer and use it in GitHub Desktop.
Save scritur/b3bc5f1c5323efc68ba67cea910cc27c to your computer and use it in GitHub Desktop.
Notes about the confusion between instance and subclass relationship

Research question

In data modeling and knowledge organization we often find the need to connect item as subclasses or instances of each other. These two types of relationships are often confused, but why?

Background

Where does subclass and instance come from? Object oriented modeling? Artificial Intelligence? Knowledge Organization? Plato? ...

Some influental sources should be identified.

Knowledge Organization

See http://marciazeng.slis.kent.edu/Z3919/43hierarchy.htm on hierarchical relationships. Traditional thesauri don't differentiate Generic Relationships and Instance Relationships but just support Hierarchical Relationships.

Data modeling

Teorey et al (1986) extend the Entity-Relationship Model with hierachies to support generalization but the idea can be trace back further

Object Oriented Modeling was very influental starting in the 1990s.

Knowledge Representation

See https://en.wikipedia.org/wiki/Class_%28knowledge_representation%29.

Confusion

Where has the confusion been studied before?

Assumed result

There is no objective rule when to use subclass and when to use instance relationship because these categories are artificial. It all depends on...

Description logic does not work to describe reality.

Probably it has already been said by Kent (1978).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment