Role

This page is generated from the code and must not be edited by hand.

A relationship an entity can play inside one interpretation.

Not a theme kind, and the difference is why this record exists. A theme kind is an axis the pool can be explored along, and it is a property of a *sense*: antibody is a reagent wherever it appears. A role is a property of a *reading*: the same antibody is the treatment in one experiment, the reference standard in another, and a comparison somebody merely mentioned in a third. Nothing about the sense decides which.

Adding theme kinds can therefore never substitute for recording roles, and the temptation to try is strong because both look like labels on a term. The two are declared apart so that no later session has to disentangle them from data already written under one heading.

Declared and unpopulated. No role vocabulary ships, nothing assigns a role, and no rule may. Introducing the distinction while there is nothing to migrate costs one record and one nullable field; introducing it afterwards costs a migration and an argument.

Fields

Field	Type	Required	If left out
definition	text	yes
enabled	yes or no	no	true
name	text	yes
origin	text	no	"builtin"
schema_version	text	no	"1.23"