Follow-up from external review on #607 (adds octoploid, allotetraploid, allohexaploid, segmental allotetraploid; closes #605).
@ccaio and Jie Wang (https://orcid.org/0000-0002-3895-8527) suggested a fuller structure for the ploidy branch. Two axes interact:
- Origin: autopolyploid, allopolyploid, segmental polyploid (and segmental splits into segmental auto- and segmental allo-, since "segmental" describes degree of differentiation and meiotic pairing, not origin).
- Ploidy level: triploid, tetraploid, pentaploid, hexaploid, and so on.
Proposed shape:
polyploid
autopolyploid (autotriploid, autotetraploid, ...)
allopolyploid (allotriploid, allotetraploid, ...)
segmental polyploid
segmental autopolyploid (segmental autotriploid, ...)
segmental allopolyploid (segmental allotriploid, ...)
Open question raised by the reviewers: each numerical level recurs under every origin category, e.g. triploid (autotriploid, allotriploid, segmental autotriploid, segmental allotriploid). How should PATO best manage that recurrence? Multiple inheritance across the two axes, a design pattern, or something else?
Not a blocker for PR #607, which only adds the four requested terms. Recording the reviewers' suggestion so it is not lost. @ccaio offered to help develop it further.
Follow-up from external review on #607 (adds octoploid, allotetraploid, allohexaploid, segmental allotetraploid; closes #605).
@ccaio and Jie Wang (https://orcid.org/0000-0002-3895-8527) suggested a fuller structure for the ploidy branch. Two axes interact:
Proposed shape:
Open question raised by the reviewers: each numerical level recurs under every origin category, e.g.
triploid (autotriploid, allotriploid, segmental autotriploid, segmental allotriploid). How should PATO best manage that recurrence? Multiple inheritance across the two axes, a design pattern, or something else?Not a blocker for PR #607, which only adds the four requested terms. Recording the reviewers' suggestion so it is not lost. @ccaio offered to help develop it further.