TCS » History » Revision 4
« Previous |
Revision 4/19
(diff)
| Next »
Andreas Müller, 07/26/2007 11:25 AM
Vergleich TCS – Berlin Model¶
TCS has 6 slots (Meta_Data, Specimen, Publications, Taxon_Names, Taxon_Concepts, Taxon_Relationship_Assertions)
Taxon_Names¶
| |BM |TCS|
|Nomenclatural_Code |Not existing ( or existing in Reference as “NomStandardâ€) |Existing as an attribute|
|is_Anamorphic |Not existing Existing as an attribute (use for some fungus)
|Simple NameCache /FullNameCache Both existst (“NameCache†is to be found in
|Rank |Foreign Key to a controlled voc. String or code (controlled voc.)
|Uninomial / Suprageneric|Suprageneric only used for taxa above genus rank Uninomial used for genus and above
|Genus |genus |genus (to be used for genus rank??)
|Genus_Subdivision_Epi |GenusSubdivisionEpi (not together with SpeciesEpi) |InfragenericEpithet (not together with SpecificEpithet)
|Specific_Epithet |SpeciesEpi |SpecificEpithet
|Infraspecific_Epithet |InfraSpeciesEpi |InfraspecificEpithet
|Cultivar_Name(Group) |CultivarName and CultivarNameGroup |Only CultivarNameGroup
|Simple Authorship |Not existing |obligate
|Authorship |Author, ExAuthor, BasAuthor, ExBasAuthor |Authorship or (BasionymAuthorship and CombinationAuthorship). |Combination_Authorship |might be neglected as usual in zoology (but against code).
|Authorship - Year |Not existing (except for EDIT version) |Facultative
|Authorship - Agent_Names |Facultative, detailed information |Facultative, String, role and link, no more information
|NomRef NomRefFk to a PublishedIn (as a link e.g. to an publication) and MicroReference and Year
|Typification Not really existing yet TypeVouchers and TypeNames
TypeVouchers For species and below:
typeOfType (attribute),
VoucherReference,
LectotypePublication,
LectotypeMicroReference
TypeName Above species:
NameReference,
LectotypePublication,
LectotypeMicroReference
RelName and NomStatus RelName and NomStatus are stored in 2 tables SpellingCorrectionOf, Basionym, ConservedAgainst, LaterHomonymOf, SpellingCorrectionOf, BasedOn (?), Sanctioned, ReplacementNameFor, PublicationStatus
All relations have the following facultative attributes: rule considered, note, related name, reference + microreference
This differs from BM as in BM we don’t use the rule considered but the string expression used for the relation (e.g. nom. nov.) that may point to different rules
ProviderLink NameSourceRefFk (Link?) ProviderLink
ProviderSpecificData Not existing ProviderSpecificData
Homotypic Synonyms only Only on name level by using basionym or ReplacementNameFor relationship
Updated by Andreas Müller over 16 years ago · 4 revisions