The terms in the "value" part of PATO should only mean one
thing. Right now a mix-and-match approach can be used,
with only some
values constrained to be used with certain attributes.
For example, "irregular" means different things when
applied to shape
and frequency. I propose two separate value terms here.
If values can be made univocal, then EAV becomes
redundant and can be
represented as EA without any loss of information.
Univocity is worth pursuing in its own right,
regardless of whether we
switch EAV to EA.
WHEN: phase 3. May affect annotation - conversion to
new univocal terms
should be automatable
Log in to post a comment.