You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Each phyloref definition should include a clade type. To start with, we could include all the clade types currently supported by PhyloRegnum, which includes "apomorphy-based_standard", "apomorphy-modified_crown_clade", "crown-based_total_clade", "minimum-clade_standard", "maximum-crown-clade", "maximum-total-clade", "maximum-clade_standard" and "minimum-crown-clade" (I'll get a full list from Nico when I implement this). This information could then be incorporated into generated ontologies to distinguish between crown-clades and total-clades (phyloref/phyloref-ontology#33).
The text was updated successfully, but these errors were encountered:
After discussing this on the Phyloref call on January 27, 2021, we decided to have a phylorefType field that has one of the following values:
phyloref:PhyloreferenceUsingMinimumClade for minimum-clade phylorefs.
phyloref:PhyloreferenceUsingMaximumClade for maximum-clade phylorefs.
phyloref:PhyloreferenceUsingApomorphy for apomorphy-based phylorefs.
These values would then be added to the list of superclasses for the phyloreference, so that a minimum-class phyloreference would be a subclass of phyloref:PhyloreferenceUsingMinimumClade. I've implemented this in PR #61.
This PR adds a phyloreference type (`phylorefType`) to phyloreferences as defined in #6. The value of phylorefType must be one of the following classes from the Phyloref ontology:
- `phyloref:PhyloreferenceUsingMinimumClade` for minimum-clade phylorefs.
- `phyloref:PhyloreferenceUsingMaximumClade` for maximum-clade phylorefs.
- `phyloref:PhyloreferenceUsingApomorphy` for apomorphy-based phylorefs.
Separately, we calculate the phyloreference type while we are generating the logical expression (based on the internal and external specifiers), and make the phyloreference a subclass of that class. If the provided phylorefType differs from the computed phyloref type, we will throw an error and refuse to create this phyloreference.
Closes#6.
Each phyloref definition should include a clade type. To start with, we could include all the clade types currently supported by PhyloRegnum, which includes "apomorphy-based_standard", "apomorphy-modified_crown_clade", "crown-based_total_clade", "minimum-clade_standard", "maximum-crown-clade", "maximum-total-clade", "maximum-clade_standard" and "minimum-crown-clade" (I'll get a full list from Nico when I implement this). This information could then be incorporated into generated ontologies to distinguish between crown-clades and total-clades (phyloref/phyloref-ontology#33).
The text was updated successfully, but these errors were encountered: