feature request #2949
closedSimplify TaxonName classes
0%
Description
Currently we do have 7 TaxonNameBase related classes. However only ViralName really differs much from all other classes.
Having different classes instead of pure type information from a type enum such as in Reference creates a lot of overhead for programming, therefore we should unify at least all 5 NonViralName classes.
However, the largest overhead is created by the differentation of TaxonNameBase and NonViralName as TNB is referenced e.g. by TaxonBase whereas for most operations on names we need NVN. This is also a recurring source of bugs such as Class Cast Exceptions.
As ViralNames are very rarely used, it is suggested to integrate them also within 1 (!) TaxonName class and treat incorrect handling via validation.
Also changing name types without changing uuid/id is easier this way.
Allow interfaces for correct programming such as for Reference interfaces.
NomenclaturalCode may become the type class and be persisted (see also #2615)
Related issues
Updated by Andreas Müller over 10 years ago
- Severity changed from normal to major
Updated by Andreas Müller almost 10 years ago
- Priority changed from Highest to Priority13
Updated by Andreas Müller over 8 years ago
- Target version changed from CDM UML 3.5 to CDM UML - Next major release
Move all unassigned modelling tickets to next major release
Updated by Andreas Müller about 6 years ago
- Description updated (diff)
- Target version changed from CDM UML - Next major release to CDM UML 4.7
- Private changed from Yes to No
Updated by Andreas Müller about 6 years ago
- Is duplicate of feature request #6361: [MASTER] Merge all TaxonName classes into 1 class added
Updated by Andreas Müller almost 6 years ago
- Status changed from New to Duplicate