Container for all elements of a name record

The full name at any rank excluding the authors. Could be generated from hierarchical components. NB no point following ABCD in splitting name components for each code as I believe that is only necessitated because ABCD is for capturing the slacker use of names attached to specimens. Name providers have no excuse!

the correct spelling of the terminal element(s) at this rank. Normally a supra-specific mononomial, or an specific/infraspecific epithet but could be many words, e.g. hybrid formula, viral species name.

the spelling given by the author to terminal element if not accepted under code

These can occur at any rank and are therefore treated as an extra 'label' attached at any rank. We should develop this more fully. ABCD is also lacking in this respect. We would be doing the multi-million dollar horticultural industry a favour by capturing trade names appropriately - and the model here and in ABCD is too simplistic. Trade Names are allocated by a registering authority on a country-basis and thus the same trade name can be applied to different taxa in different countries.

It would be desirable to have this controlled by a vocabulary together with a sort code. Not sure that is achievable in an open system?  ranks are included 

two alternate mechanims. Either explicit flat hierarchy, or parent chain. Also allows infra-specific names to be captured explicity. This doesn't work elegantly. It would be better if names at all ranks were treated as part of a hierarchical chain but most systems aren't designed like that (except ours in NZ of course).

Option: fill all or principal ranks and optionally provide keys

Strictly varieties are not subordinate to species which means that successive infra-specific ranks cannot fit into a unique hiearchy. In addition the use of ranks below subspecies happens but is not governed by the codes. For bacteria and plant pathogenic fungi these tri-quadri-nomials are important. The mechanism here allows 3 level of hierarchy to species, eg puccinia alba subsp. alba var. deformans forma urticae. Might be a case here for including authors?

Option: provide a parent linking key. Not sure if I'v egot the recursive mechanism correct here?

The authors of the original name, B-P abrreviated or not for plant names, without brackets. I am usng Richard Pyles term 'protonym' for cross-code basionym equivalent.

Necessary duplication with data in citation if present. In an ideal world ... 

The page/plate in which the protologue STARTS, i.e. it is not a pagination.

name authors not same as lit authors 

Zoologists frequently have just original reference, and not combining reference. Will be duplicated if protonym reference given. Not sure how to handle this potential duplication?

All these URI's need to be allocated by a central service. However, to be pragmatic, I suggest we use a semi-semantic URI of the form, say, provider.organization.country/localkey. Where localkey should itself preferably be non-semantic to the provider. Protonym URI Provides the link required to pull together MOST unambiguous synonyms. In the case of ICBN where Protonym equals Basionym there are some subtle rules for using nom. novs. 1) the original name is illegitimate in which case the nom. nov. has itself as a basionym and the replaced name is the illegitimate name. 2) a combination would result in a homonym or tautonym, in which case the nom. nov. has itself as a basionym and the replaced name is the original valid name. 3) a combination would result in a homonym or tautonym and the author selects the next available epithet in the priginal circumscription. In this case the basionym is that later name (even tho it is heterotypic!) and the replaced name is the original name. NB In this rare case linking names on the basionym INCLUDES AMBIGUOUS SYNONYMS.

Local primary keys are probably the only thing most providers have (at least I hope they do!). This allows a data-set to be internally linked and checked for self-consistency. In the absence of a provider-driven URI, the central aggregator can issue appropriate URI's for return to the provider. I think this mechanism would also be appropriate for issuing TaxonConcept URI's where, again, most providers won't have them, but they can be generated automatically on aggregation.

Name is a nom. nov.

In the case of nom. novs. a reference for the type bearing name - this required to fully group all objective synonyms

The authors of the original name, BP abrreviated or not for plant names, and without brackets

May also be a plate/figure

The nomenclatural status of this name

The code to which name has been submitted for scrutiny. Do I need to make this 1 to many to cover ambiregnal names? Also, don't have the official abbreviations at hand.

See attributes

The article in the code in question that is commented on below

possibly need some vocabulary here, e.g. superfluous

Article numbering changes according to edition of the code

The names having priority which block the use of this name

placeholder for blocking name(s) if not referenced

nom. conf. etc

The literature used to determine the nomenclatural status.

The current status of the record from an editorial persepective

The sources of literarature used to compile the record other than protologue and those mentioned against nomenclatural status

The people who compiled the data

Notes on compilation

what sources were checked in compilation

not really nomenclatural - but useful. Should only be populated if this record is a protonym record. Not sure how to XML code that? 

The IndexHerbariorum or equivalent unique designation of the collection

The accession number of the type in the institute

See attributes. Need to be careful here. We only need type desigantions that say something about nomenclatural status - any many don't, e.g. kelptotype etc.

ISO country. Where the type was collected. Strictly a job for collection databases but many name dbs hold this data so let's use it.

This name is based on part of the same type as another name - possibly referenced below

 NB pro-parte names have this nomenclatural type-linkage that needs storing in a nomenclatural record.

i.e. this name doesn't really exist but many name providers will have them acting as placeholders for attaching data. Unfortunately an autonym is a Taxon Concept as it implies a different circumsciption to the parent name. I am not including misapplications here for the same reason, but I don't see how to avoid registering autonyms because it is a different 'string'!

Plant hybrids and grafts may be referred to by a 'nothotaxon' name for the hybrid formula. there is a need to capture the grammar of this formula, i.e. to  specify the sex and order of component names which constitute the hybrid (effectively the 'partial' objective synonyms for the hybrid).

This name is a nothotaxon name

provides mechanisms of grouping inter-hybrid names

Name applies to an anamorphic taxon: art 59 ICBN. Whilst the ICBN continues to allow two names for the same organism then we must provide a linking mechanism.

Unambiguous link between anamorph/teleomoprh names for same taxon currently allowed under ICBN

Not nomenclature but probably best placed here and many providers will have this data attached to 'names' and not concepts, largely because the national/international lists deal with names and not concepts.

Not nomenclature but also probably best placed here.

The nomenclator source of information. I suggest this refelects the non-semantic part of the providers URI. We need a mechanism for registering these.

This needs coding better - it's not saying what I want. There is a simple hierarchy of terms here.

Status in a published list, eg CITES

ISO Country

for article type equals freeform. Many name citations will be of this form

The web-based location of the article

Series are occasional book publications under a single editor/institution/title

ISO Language

Maybe imperialistic? Need a mechanism for multi-language translations.

Includes forward, appendices, index and plates/figures

year on the publication

date of publication, or year of publication if different to stated year. Need ABCD vague date format.

ISO Language

We really need BPH and TL2 as standard disctionaries to drive these titles

ISO Country

ISO 2nd level

Vernacular name in the original language

ISO Language

I guess we really need a many-language mechanism. This is a bit imperalistic! But then the international language of science is english?