EDIT

## Vergleich TCS – Berlin Model

TCS has 6 slots (Meta_Data, Specimen, Publications, Taxon_Names, Taxon_Concepts, Taxon_Relationship_Assertions)

### taxonNames

|	|BM	|TCS|

|Nomenclatural_Code 	|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 <CanonicalName><Simple>|

|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	|

|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)	| |combinationAuthorship	|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