Arbital "parent" relationship

by Alexei Andreev Apr 1 2015 updated Sep 20 2017

Parent-child relationship between pages implies a strong, inseparable connection.

Most pages in Arbital can be connected. We call these connections relationships. Parent-child relationship is one of the multiple relationship types and is the tightest way to connect pages on Arbital. This relationship is used to indicate that the child is a critical component of the parent, or that the parent is the sum of its children. For example, the [SI_units SI units] parent page will have [kilogram], [second], [meter], etc… as children pages.

It's perfectly fine for a page not to have any parents or children. It can still be found by searching, and can be used as a tag, requisite, or link.

When to create a parent-child relationship

When the child doesn't make sense outside of the context of the parent. For example:

When there is some well-known, established hierarchy. For example:

When the parent is defined as the sum of some parts. For example:

More generally the parent-child relationship suggest a "is-a" or a "is-a-part-of" connetion. Sometimes it's also simply used for organizing pages in a hierarchy to make it easier to find them.

When not to create a parent-child relationships

Just because two concepts are often associated. For example:

Just because two concepts are closely related. For example:

Sometimes it can be unclear if the pages should have a parent-child relationship. If you run into a case you can't clearly resolve, please post it here, so we can discuss it, learn from it, and refine these definitions.


Eric Bruylant

This gives a few clear examples, but does not help much with slightly less clear judgements (e.g. should Nick Bostrom be a child of People or just tagged with it?). Classification systems are tricky and often subjective, probably worth taking a close look at Wikidata and other similar projects for inspiration when we want to work out detailed guidelines for this.