Standards
6 min

What Is a Polyhierarchy, and When Do You Need One?

Key takeaways

  • A polyhierarchy lets one concept have several broader parents, and all of them are correct.
  • Use it when a single parent would be wrong, not merely when placement is contested.
  • It costs you clean roll-up. Name a primary parent for reporting and record that choice.
  • SKOS expresses it directly. SHACL is where you check that nobody created a cycle.
In this article
Share

What is a polyhierarchy?

A polyhierarchy is a taxonomy in which a concept can have more than one broader parent. In a plain hierarchy every term has exactly one place. In a polyhierarchy a term can sit under two or more categories at once, and both placements are correct.

The standard illustration is a tomato. Botanically it is a fruit. In a kitchen it is a vegetable. Forcing one parent makes the taxonomy wrong for half the people using it. Letting it sit under both makes it right for everyone and slightly harder to maintain.

That trade is the whole subject. Polyhierarchy buys accuracy and costs you clean roll-up.

When do you actually need one?

The test is whether a single parent would be a lie. Inconvenient does not qualify. Debatable does not qualify. It has to be wrong.

Cases where one parent fails

  • Clinical coding. A condition can be both infectious and respiratory. SNOMED CT is polyhierarchical for exactly this reason, and the overlap carries clinical meaning.
  • Regulatory classification. A substance can be controlled under two regimes with different thresholds, and neither supersedes the other.
  • Products with dual use. An item sold into two markets sits legitimately in both catalogs.
  • Organizational matrix. A role reports into a function and a region, and both relationships are real.

What the four have in common is that the second parent is imposed from outside. A regulator, a clinical standard or a market defines it, and the business cannot dissolve the overlap by deciding to. That is the signal worth watching for. When the overlap is internal and negotiable, somebody can usually just settle it, and a single parent becomes honest again.

If none of those shapes describe your domain, you probably want a facet instead. Independent attributes that happen to cut across your tree are a faceting problem wearing a polyhierarchy costume. Hierarchical vs faceted taxonomy covers that distinction.

What does it cost you?

Three things get harder, and the first one is the one that surprises people.

CostWhat happensMitigation
Roll-up becomes ambiguousA concept under two parents gets counted twice, or once, depending on the queryName a primary parent for reporting, and record that it is a reporting convention
Navigation duplicatesUsers reach the same concept by two paths and wonder whether they are the same thingShow the other parents on the concept page so the overlap is visible
Cycles become possibleA chain of broader relationships can loop back on itselfValidate on write; most tools will not catch this for you

The double-counting problem is where polyhierarchies actually fail in production. Two reports built on the same vocabulary return different totals, both internally consistent, and the reconciliation takes longer than the modelling did. The fix is not technical. Somebody decides which parent is primary for reporting, writes that down, and the decision is honoured by every query.

How do you express it?

SKOS supports polyhierarchy directly. A concept can carry more than one skos:broader relationship, and the standard expects it.

What SKOS deliberately does not do is enforce a tree. It has no notion of a single correct parent, which means the structure you express is the structure you meant. That is a feature when the domain is genuinely overlapping and a hazard when nobody is checking, because an accidental second parent looks identical to a deliberate one.

SHACL is where the checking lives. A shape can require that every concept has at least one broader term, that no broader chain forms a cycle, and that concepts in certain branches carry exactly one parent. What is SKOS covers the vocabulary and what SHACL is covers the validation side.

What breaks in tooling?

Many taxonomy tools assume a single tree, and they do not always say so on the box.

What to test before you commit

  • Can a concept take a second parent at all? Some products allow it in the data model and not in the editing interface.
  • Does export preserve both parents? A round trip that silently drops the second relationship is worse than a tool that refuses it outright.
  • Does the tool detect cycles? Ask for the behaviour, then try to create one.
  • How does reporting treat multiple parents? If the answer is "it depends on the query", you own the double-counting problem.

The export question is the one to insist on. A polyhierarchy that cannot leave the platform with its relationships intact has become a migration project the first time anyone wants to change tools. Taxonomy management software covers what to test more broadly.

What does this look like on a real set?

Take a chemicals manufacturer classifying ten thousand products. The sales taxonomy groups by application: coatings, adhesives, lubricants. The compliance taxonomy groups by hazard class, which is set externally and has nothing to do with application.

A single tree forces a choice between them, and each choice breaks somebody's job. Sales cannot find products by what they are for, or compliance cannot answer an audit. Facets would work if hazard class were a free attribute, and it is not: it carries its own internal hierarchy of categories and subcategories that regulators define.

So the honest structure has products sitting under both an application parent and a hazard parent, each of those parents being a tree in its own right. That is a polyhierarchy, and it is the right answer here because both parent structures are real, externally defined, and neither can be demoted to an attribute.

What that team has to decide up front

  • Which parent is primary for reporting. Revenue by category needs one answer, so application wins and compliance is a secondary view.
  • Who owns each branch. Application is commercial. Hazard class is regulatory and changes when the regulator says so, not when the business wants it to.
  • What happens on conflict. When a reclassification moves a product in one tree, somebody checks whether the other tree still makes sense.

None of those are modelling questions. They are governance questions that the modelling makes unavoidable, which is the usual pattern with polyhierarchy.

Who decides when a second parent is allowed?

Left ungoverned, polyhierarchy spreads. Every disagreement about where a concept belongs resolves as "put it in both", and within a year the structure has no shape at all.

The working rule is that a second parent is a decision, with the same review as any other change to meaning. Somebody proposes it, somebody with standing in that domain approves it, and the reason is recorded alongside the concept. A term with three parents and no recorded reason for any of them is not a polyhierarchy. It is an argument nobody finished.

Taxonomy governance covers how that review is usually structured and what the trail needs to hold.

So what should I take away?

Use a polyhierarchy when a single parent would misrepresent the domain, and not merely when placement is contested. Expect to pay for it in reporting, and pay that cost deliberately by naming a primary parent for roll-up.

TopQuadrant's view is that polyhierarchy is safe when it is governed and corrosive when it is not. The structure is expressible in SKOS and checkable in SHACL, which means the question of whether a second parent was agreed can be answered from the data instead of from memory. Build it that way. Then the overlap is a decision somebody owns, and not a place where the taxonomy quietly stopped having a shape. Taxonomy management covers the surrounding discipline.

Give your AI the context it's been missing

See how the TQ Data Foundation turns your enterprise knowledge into trusted, Al-ready context.