Project

General

Profile

Actions

TCS » History » Revision 2

« Previous | Revision 2/19 (diff) | Next »
Andreas Müller, 07/26/2007 11:14 AM


Vergleich TCS – Berlin Model

TCS has 6 slots (MetaData, Specimen, Publications, TaxonNames, TaxonConcepts, TaxonRelationShipAssertions)

TaxonNames

BM  TCS

NomenclaturalCode Not existing ( or existing in Reference as “NomStandard”) Existing as an attribute

isAnamorphic 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??)

GenusSubdivisionEpi GenusSubdivisionEpi (not together with SpeciesEpi) InfragenericEpithet (not together with SpecificEpithet)

SpecificEpithet SpeciesEpi SpecificEpithet

InfraspecificEpithet InfraSpeciesEpi InfraspecificEpithet

CultivarName(Group) CultivarName and CultivarNameGroup Only CultivarNameGroup

Simple Authorship Not existing obligate

Authorship Author, ExAuthor, BasAuthor, ExBasAuthor Authorship or (BasionymAuthorship and CombinationAuthorship). CombinationAuthorship might be neglected as usual in zoology (but against code).

Authorship - Year Not existing (except for EDIT version) Facultative

Authorship - AgentNames 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 · 2 revisions