The IA Files 004 – Taxonomies

In my previous post in the IA Files, we took a look at definitions – those things you typically find in dictionaries or, perhaps more commonly today, when you type ‘define <word>‘ in a Google search.

A definition states the meaning of a concept and distinguishes it from all others, thus preserving the logical order of a concept’s hierarchical interdependence. 1

Such a hierarchy can be expressed in a model that Information Architects like to call a taxonomy. Taxonomies are quintessential to information architecture and very well worth a pause for deeper reflection. So, before we go flingin’ the term around like we know what we’re doing, let’s take that pause now…

What is a taxonomy?

Carl Linnaeus, the father of modern taxonomy.

The term taxonomy is ancient Greek for “arrangement method“. In the strictest sense, taxonomy refers to the conception, naming, and classification of biological organisms. In this sense, the term is heavily associated with Carl Linnaeus, the father of modern taxonomy, and the dude who originally came up with the formal system of naming species using the two-part Latin word scheme known as binomial nomenclature (e.g. Psittacus alexandri, Turdus migratorius, Tradescantia virginiana). Information Architects tend to use the term in a more general sense to refer to just about any kind of hierarchical ordering of items into groups based on similarities and/or differences.

Some IA’s use the term to describe the navigational structure of a website, although I prefer to call that site architecture. One case where I do often use the word taxonomy is when referring to a controlled vocabulary of terms used for describing content. In IBM’s Web Content Manager, for example, taxonomies are used to represent hierarchical collections of terms called categories. Content authors can apply these categories as a way to describe the subject and nature of their content. Menus and search components are then used to retrieve and display content based on the categories applied to the content items. This allows us to do cool things like render dynamic lists of hyperlinks that are relevant and related to the content item being viewed.

Taxonomy Categories in IBM Web Content Manager

Formal versus informal taxonomies

Understanding the difference between formal and informal taxonomies is essential. A formal taxonomy is one in which the associations between the taxons or categories are formally defined.

A common formal classification scheme expresses the “is a (type of)” relationship. In such a scheme, the child concepts under a given parent are said to be a type of the parent. A simple test for following the rule is to use the concepts in a sentence where the child is the subject, “is a” or “is a type of” is used as the predicate, and the parent as the object.

Subject
Predicate
Object
DOG IS A MAMMAL
MOZARRELLA IS A CHEESE TOPPING

Because these sentences logically evaluate to TRUE, we can rest assured that we have not broken the rule, which makes our taxonomy formal.

This is important because a taxonomy that is intended to be formal should be formal throughout. Otherwise, it will not serve its purpose effectively. If most of the taxonomy adheres to the rule of formality, but some of it does not, then this can cause confusion amongst users.

Best Practice

The defined relationship between concepts in a formal taxonomy should be uniformly applied throughout the entire taxonomy.

Now, I am not saying that all taxonomies must be formal. I am just saying that when they are intended to be formal, their rule of relation must be explicitly defined and adhered to. Otherwise, they are not formal or they are simply incorrect.

Most navigation systems on websites and portals are informal. They typically always express increasing levels of specificity as one goes deeper into the structure, but specificity is not a rule of relationship between concepts. It is a general characteristic of all taxonomies. As we go down into the branches of a taxonomy tree, we find increasing levels of detail. As we move up towards the trunk, we’re moving through increasing levels of abstraction. That’s a fundamental principal of the function and purpose of taxonomy as a classification tool, but it is not itself the classification scheme.

Which brings us to an interesting question…

If there are no “rules” for an informal taxonomy such as a website navigation system, then how do we go about building one properly – one that we can say is good?

Rest assured, there are best practices and “rules of thumb” for building effective website navigation systems and in the next installment of the IA Files, I’ll begin to share some things my colleagues and I have learned from our experiences, so please stay tuned.

Next: The IA Files 005 – Navigation Breadth and Depth

Notes:

  1. Rand, Ayn. Introduction to Objectivist Epistemology: Expanded Second Edition, ‘Definitions’, page 40.