This group of fields completely describes the botanical name of the
record. These fields also enable the identification of cultivars and hybrids and
intermediates using either binomials or hybrid formulae, as well as qualified
identifications.
These fields enable the interchange of either the 'full' scientific
(Latin) name of a plant or the 'limited' scientific name.
2. If a 'full' taxonomic name is not required, then an abbreviated
('limited') scientific name can be used to precisely refer to the taxon. This option is
also available in HISPID3. Such a 'limited' scientific name is transferred according to
the following rules:
If only a species name is required then:
only the genus name and the specific epithet are required. The
authority is not required unless there is some possibility of confusion between this
species and a homonym.
If the record refers to an infraspecific taxon then:
only the genus name, specific epithet and the lowest level
infraspecific epithet are required. The authority is not required unless there is some
possibility of confusion between this infraspecific taxon and a homonym.
The module for the Plant Name is based on Bisby, F.A. (1994) 'Plant
names in botanical databases', Plant Taxonomic Database Standard No. 3 Version 1.00 (TDWG
/ Hunt: Pittsburgh).
Hybrids and Intergrades present considerable problems for handling of
their names in electronic storage and transfer. The system presented here differs from
ITF2, in that it does not indicate the taxonomic rank at which the hybrization or
intergradation occurs. For example, in HISPID3, if the Hybrid Flag field is filled,
then the name of the 'first' parent is transferred in the 'default' HISPID3 name fields
(eg. Genus Name, Species Epithet, Infraspecific Epithet) and the
'second' parent is transferred in the 'hybrid' name fields (eg. Genus Name Parent 2
Hybrid, Species Epithet Parent 2 Hybrid, Infraspecific Epithet Parent 2
Hybrid). Unlike ITF2, this system readily allows for the interchange of hybrids and
intergrades resulting from parents at different rank (eg. a hybrid between one species and
the variety of another species).
Although the application of vernacular (common) names is not as
rigorously controlled as scientific names, and they vary greatly and are often not unique
for individual species, institutions may wish to interchange this information. A suggested
format for interchanging these data are included (refer Vernacular Names).
The names of higher groups such as suprafamilial groups and families are
not required in the HISPID3 transfer file because each accepted genus name in the plant
kingdom is unique. However, these data may be interchanged, using the fields Suprafamilial
Group Name and Family Name.
It is not necessary to include the authorities of the species and
infraspecific names in a HISPID3 transfer file. However, the inclusion of authorities with
the botanical names prevents confusion between homonyms. If these authorities are
required, then they can be included in the transfer file. To minimise variation in the
citation of the names of authors, it is recommended that a published standard for the
citation of authorities be used. One such standard is Brummitt, R.K. & Powell, C.E.
(1992) 'Authors of plant names' (Royal Botanic Gardens: Kew)(endorsed by the International
Working Group on Taxonomic Databases for Plant Sciences - TDWG).
Mixed collections are unacceptable and must be handled by duplicate
records or, if the mixture is not significant, by a note in the Name Comments
field.
TDWG Short name: CLASS (?)
Description: The relevant suprafamilial group name of the taxon
referred to in the record.
Relevant standards: ABIS (supra generic category), ITF
Domain/Range/Values: Alpha; any valid suprafamilial group name,
with first letter in uppercase.
Comments: This field allows for material being sent for
identification, particularly when even the family may not be known.
The ABIS standard included in this field any suprageneric category
including family (see next field) and any other arbitrary grouping.
All plant groupings above the rank of genus are assigned automatically,
the name depending on the classification system employed. As each institution uses its own
classification system, in many cases different from others, this field and the next two
fields may not always be a useful part of the interchange standard. However, it is
simple to ignore this information when loading the data (if it is not required or is
unsuitable), but it may be useful when reviewing the taxonomic system under which the data
has been compiled when loading the file into a database.
TDWG Short name: FAMILY
Description: The family name appropriate to the Genus name field,
entered in full.
Relevant standards: ABIS (supra generic category), ITF
Domain/Range/Values: Alpha; any valid plant family name, with
capitalisation of the first letter only. If the name of the plant family is unknown, then
this field may contain the value UNKNOWN (in uppercase). In this case, the remaining name
fields should not be filled.
Comments: There is no universally accepted classification of
plant genera into families, and several systems are in use in herbaria. Individual
herbaria may choose to store two (or more) family fields to reflect different
classification systems.
If institutions store family names or standard nomenclature in an
abbreviated or encoded form, these must be expanded for transfer.
The ABIS standard includes this field in a suprageneric category (see
previous field).
Description: A field to indicate the rank of the suprageneric
group name of the plant.
Relevant standards: ABIS (supra generic category)
Domain/Range/Values: Alpha; any valid suprageneric group rank,
below the rank of family and above the rank of genus, capitalisation of the first letter
only.
Comments: See comments on conventions and necessity of this type
of information under Family Name and Suprafamilial Group Name fields.
This field must contain the full name of the rank of the suprageneric
group, eg. 'subfamily'.
Description: The suprageneric group name of the plant, entered in
full.
Relevant standards: ABIS (supra generic category)
Domain/Range/Values: Alpha; any valid suprageneric group name,
below the rank of family, capitalisation of the first letter only.
Comments: See comments on conventions and necessity of this type
of information under Family Name and Suprafamilial Group Name fields.
If the name of the genus of the plant is unknown, then this field does
provide a higher level of identification than does the Family Name field alone.
The interchange of hybrid formulae and intergrade names is particularly
difficult in a flatfile format because the relational nature of these data cannot be
readily maintained. Unlike ITF2 which has Hybrid Flag fields for intergeneric,
interspecific and infraspecific hybrids and intergrades, HISPID3 has only one (namely, Hybrid
Flag field, refer below). In HISPID3, the Hybrid Flag indicates the type of
hybrid, grafts, chimaera or intergrade involved, but does not describe the rank to which
it applies. If the name is a Latin or non-Latin collective name, or if the name is a graft
or chimaera, then only the standard 'default' HISPID3 name fields are required in
the transfer file. For example, the name Lonicera x tellmaniana would be
tranferred with the letter 'x' in the Hybrid Flag field, 'Lonicera' in the Genus
Name field, and 'tellmaniana' in the Species Epithet field.
The concept of 'parent 1' and 'parent 2' has been implemented in HISPID3
to handle the transfer of names in the form of hybrid formulae and intergrades.
Example 1: the intergeneric hybrid Rhododendron x Vaccinium
would transferred with the letter 'H' in the Hybrid Flag field, 'Rhododendron' in
the Genus Name field ('parent 1' - transfer code: gen) and 'Vaccinium' in
the Second Hybrid Genus Name field ('parent 2' - transfer code: genhy2).
That is:
| hyb | "H", |
| gen | "Rhododendron", |
| genhy2 | "Vaccinium", |
Example 2: the hybrid Prostanthera cuneata x Prostanthera
lasianthos var. subcoriacea would be transferred with the letter 'H' in the Hybrid
Flag field, 'Prostanthera' in the Genus Name field, 'cuneata' in the Species
Epithet field ('parent 1' - transfer code sp), 'lasianthos' in the Second
Hybrid Species Epithet field ('parent 2' - transfer code sphy2), 'var.' in the Second
Hybrid Infraspecific Rank Flag ('parent 2' - transfer code isprkhy2), and
'subcoriacea' in the Second Hybrid Infraspecific Epithet field ('parent 2' -
transfer code: isphy2). In this example, hybrid formulae which describe the results
of hybridisation at different ranks can be effectively interchanged. That is:
| hyb | "H", |
| gen | "Prostanthera", |
| sp | "cuneata", |
| sphy2 | "lasianthos", |
| isprkhy2 | "var", |
| isphy2 | "subcoriacea", |
Example 3: the hybrid Magnolia campbellii subsp. mollicomata
x Magnolia sprengeri var. diva would be transferred as:
| hyb | "H", |
| gen | "Magnolia", |
| sp | "campbellii", |
| isprk | "subsp.", |
| isp | "mollicomata", |
| sphy2 | "sprengeri", |
| isprkhy2 | "var.", |
| isphy2 | "diva", |
Description: A field to indicate whether the plant name refers to
a hybrid, graft chimaera or intergrade, without reference to rank.
Relevant standards: ITF, MFN, Bisby (1994).
Domain/Range/Values: If the accession is a hybrid, graft chimaera or intergrade, then the Hybrid field must consist of one of the characters in the table below:
| Values in Field | Nature of name in Genus Name field |
| x | A Latin collective name for a hybrid |
| G | A non-Latin collective name for a hybrid |
| H | A hybrid formula for a hybrid |
| + | A graft hybrid or graft chimaera |
| | An intergrade of non-hybrid nature |
Comments:
1. The rules associated with these values are outlined under Genus Name field.
2. For interchange and data storage purposes, the value in this field for a hybrid is a lowercase 'x' not a multiplication sign (as specified in the International Code of Botanical Nomenclature), since the multiplication sign does not occur in the ASCII character set.
3. If an 'x' is placed in this field, then the plant name must be validly published under the ICBN.
Notes: ITF includes the letter 'U' in the 'Infraspecific
Hybrid Flag' (refer ITF2) to indicate a Cultivar group name. However, HISPID3 only uses
the Cultivar Group Name field (refer below) to transfer these data.
TDWG Short name: GENUS
Description: The name of the genus of a plant or ,if part of a
hybrid formula or intergrade, then the name of the first 'parent' of that formula or
intergrade, entered in full.
Relevant standards: ABIS, ITF, MFN, Bisby (1994).
Domain/Range/Values: Alpha; any valid genus name, capitalisation
of the first letter only.
Comments: This field, combined with the following Species
Epithet and Infraspecies Epithet fields, constitute the minimum taxonomic
information for the identity of the specimen.
This field may contain an embedded hyphen, in which case the second word
is in lowercase
1. This field must contain one of the following:
1.1 A validly published generic name under the ICBN or a manuscript
name.
If the Hybrid Flag field is not filled (not transferred), then this field must contain:
1.1.2 A nonhybrid name, validly published under the ICBN or a
manuscript name.
If the name of the genus of the plant is unknown, then:
1.1.3 This field should not be filled. In this case, the remaining name
fields should also not be filled.
If the Hybrid Flag is H and the name is an intergeneric hybrid name, then:
1.1.4 This field must contain the first 'parent' of a hybrid formula for
an intergeneric hybrid name, validly published under the ICBN, eg. 'Rhododendron' for the
hybrid formula Rhododendron x Vaccinium
If the Hybrid Flag is x and the name is an intergeneric hybrid name, then:
1.1.5 This field must contain an intergeneric hybrid name, validly
published under the ICBN, eg. Halimiocistus for x Halimiocistus sahucii.
If the Hybrid Flag is + and the name is an intergeneric graft hybrid or graft chimaera, then:
1.1.6 This field must be the name of an intergeneric graft hybrid or
graft chimaera, validly published under the Cultivated Code, eg. Crataegomespilus for + Crataegomespilus
dardarii.
If the Hybrid Flag is - and the name is an intergeneric intergrade, then
1.1.7 This field must contain the name of the first 'parent' of the
intergrade.
TDWG Short name: GENUS
Description: The second name of a hybrid formula or intergrade
between two plant genera, entered in full.
Domain/Range/Values: Alpha; any valid genus name, capitalisation
of the first letter only.
Comments: Refer discussion under HYBRIDS, GRAFTS, CHIMAERA AND
INTERGRADES and compare with Genus Name field, above.
Description: The subgeneric group name of the plant, preceded by
its rank, entered in full.
Relevant standards: ITF
Domain/Range/Values: Alpha; any valid subgeneric group
name, capitalisation of the first letter only.
Comments:
1. The subgeneric group name must be a single word.
2. The first letter must be in uppercase (AZ), the rest of the word in lowercase letters (az).
3. One or two hyphens are permitted in the word; no characters other than the letters outlined above are permitted.
This field must contain a validly published subgeneric group name under
the ICBN.
This field must also contain one of the following abbreviations of the
rank of the Subgeneric Group name:
| Abbreviation | Full subgeneric group name |
| subgen. | Subgenus |
| sect. | Section |
| subsect. | Subsection |
| ser. | Series |
| subser. | Subseries |
If the name of the genus of the plant is unknown, then this field must
not be filled. In this case, the remaining name fields should also be unfilled.
If the species name of the plant is unknown, then (if filled) this field
does provide a higher level of identification than does the Genus Name field alone.
Description: This qualifier permits the Species Epithet
field to be used for normal species names, as well as names of aggregate (refer Comments
1, below) or segregate species.
Relevant standards: ITF; Bisby (1994).
Domain/Range/Values:
1. If the Species Epithet field is not filled, then this field must not be filled.
2. If the Hybrid Flag is filled and the value in that field refers to an interspecific hybrid, then this field must not be filled.
Otherwise:
3. This field must consist of one of the values in the table below,
which refers to the following situations in Species Epithet field:
Content of field Nature of Name in Species Epithet field
| agg. | An aggregate species |
| s. lat. | aggregate species (sensu lato) |
| s. str. | segregate species (sensu stricto) |
Comments:
1. If the entry is 'agg.', then the plant has been identified to an aggregate species, and not to any of the segregate microspecies within the aggregate.
2. If this field is filled, then Infraspecific Rank Flag and Infraspecific Epithet fields must not be filled.
3. The terms collective species or species groups are sometimes also used in plant names. They should be treated as for aggregate species.
4. Under the current standards, it is not possible to use the aggregate/segregate concept at levels other than the species level.
TDWG Short name: SPEPITHET
Description: The species epithet of the plant or ,if part of a
hybrid formula or intergrade, then the name of the first 'parent' of that formula or
intergrade, entered in full.
Relevant standards: ABIS, ITF, TLR, MFN, Bisby (1994).
Domain/Range/Values: Alpha; any valid species name, all
lowercase, no embedded spaces.
Comments:
1. The specific epithet must be one word (except as in the cases of Rules 1.1, 1.2, 3 and 4, below).
2. It must consist of lowercase letters (az), and may contain one or two hyphens. No other characters are permitted (except in the cases of Rules 1.1 and 1.2).
3. The field may be left unfilled if the species epithet is unknown. It must be left unfilled if the Genus name is unknown (Genus Name field) or the Family Name field has the value UNKNOWN.
4. If the specific epithet of a plant is uncertain, then the following
name fields should not be filled.
Rules:
1. If the Hybrid Flag is not filled, then this field must contain a validly published, nonhybrid specific epithet under the ICBN, except in the following special cases:
1.1 If the plant has not been identified to specific level, the field must be left unfilled, as must the following name fields. (The abbreviation sp. should not be entered in these circumstances.)
1.2 If the plant represents a new species which has not been formally described, then sp. nov., sp. A, sp. 1 (or other acceptable codes) should be entered, if possible followed by a unique identifier, such as the collector's name and number or the locality. The following Species Author field must be left unfilled.
2. If the Hybrid Flag is x and it refers to an interspecific hybrid, then the entry in the field must be a Latin Collective name for an interspecific hybrid, eg. tellmaniana for Lonicera x tellmaniana.
| hyb | "H", |
| gen | "Rhododendron", |
| sp | "dichroanthum", |
| sphy2 | "griersonianum", |
If only one parent is known, then enter the specific epithet of that parent alone (without the lower case letter 'x').
| hyb | "+", |
| gen | "Xyringa", |
| sp | "correlata", |
5. If the Species Qualifier field is agg., then the entry in the field must be a validly published specific epithet under the ICBN, used for the name of the group of species concerned. The word agg. should not be included in the entry of this field.
The abbreviation sp. is not interchanged in HISPID3 if a plant has not
been identified to the species epithet level (Rule 1.1, above).
For further information refer Comments under Genus Name
Field.
TDWG Short name: SPEPITHET
Description: The second specific epithet of a hybrid formula or
intergrade between two plant species, entered in full.
Domain/Range/Values: Alpha; any valid species name, all
lowercase, no embedded spaces (refer Species Epithet field, above).
Comments: Refer discussion under HYBRIDS, GRAFTS, CHIMAERA AND
INTERGRADES and Species Epithet field, above.
Notes: The authority of the species names are not given when the
name is a hybrid formula or intergrade.
TDWG Short name: SPAUTHOR
Description: The author citation of the species (as given in Genus
Name and Species Epithet fields, above), in standard abbreviated form
Relevant standards: TLR, MFN, Brummitt & Powell (1992), Bisby
(1994).
Domain/Range/Values: Alpha; any valid author abbreviation, initials and first letter of surname in uppercase, and other characters as described below:
1. The full name of a species (as transferred in the Species Epithet field) must include this field.
2. This field is not filled for the full name of a species aggregate (as transferred in the Species Qualifier and Species Epithet fields).
3. Alphabetic letters (A-Z, a-z), fullstops (periods), pairs of brackets, apostrophes, hyphens, ampersands (&) and spaces are all valid entries for this field.
4. For the citation of joint authors, it is recommended that the ampersand (&) is used between the last two names, not 'et' or 'and'. If more than two authors, then a comma and space (, ) are used to separate all authors except for the last two.
5. Names in languages other than the English languages should be transliterated into the roman alphabet. However, if institutions are able to receive and send other alphabetic characters (eg. if using UNICODE), then these may be included in the transfer file.
6. Parenthetical author or authors in the recommended form enclosed in
round brackets at the beginning of the field.
Comments: Since the author is unique to any accepted plant name,
it is usually not essential for this information to be interchange.
Notes: The authority of the species name is not given when the
name refers to a hybrid formula or an intergrade. Therefore, the information transferred
in this field does not refer to the Second Hybrid Species Epithet field.
TDWG Short name: INFRARANK
Description: A field to indicate the lowest infraspecific
rank for the name in the Infraspecific Epithet field. The contents of this field
are confined to the rank of the infraspecific name of non-collective, and non-cultivar
group infraspecific taxa. It also indicates the lowest infraspecific rank for the
name of the first 'parent' of a hybrid formula or intergrade.
Relevant standards: ITF (in part), MFN, Bisby (1994).
Domain/Range/Values: Alpha; if the Infraspecific Epithet
field is filled and the plant is not a Collective hybrid and is not a
cultivar, then this field must be one of the values in the table below:
| Values in field | Rank of Name in Infraspecific Epithet field (Non-hybrid names) |
| subsp. | Subspecies |
| var. | Variety |
| subvar. | Subvariety |
| f. | Form |
| subf. | Subform |
Comments: If the Infraspecific Epithet field is not
filled, then this field must not be filled.
Notes: The contents of this field represent the lowest
infraspecific rank for this name.
ITF excludes the infraspecific rank of hybrids from this field.
Guidelines:
Under the rules of the ICBN, every trinomial below the level of species
is unique. Hence, Rhododendron arboreum subsp. delavayi var. peramoemum can
be known uniquely as Rhododendron arboreum var. peramoemum. Therefore the
name can consist of the genus, the species and the lowest infraspecific taxon name,
qualified by its rank.
TDWG Short name: INFRARANK
Description: A field to indicate the lowest infraspecific
rank for the name in the Infraspecific Epithet field of the second 'parent' of a
hybrid formula or intergrade. The contents of this field are confined to the rank of the
infraspecific name of non-collective, and non-cultivar group infraspecific taxa.
Relevant standards: ITF (in part), MFN, Bisby (1994).
Domain/Range/Values: Alpha; if the Infraspecific Epithet
field is filled and the plant is not a Collective hybrid and is not a
cultivar, then this field must be one of the values in the table below:
| Values in field | Rank of Name in Infraspecific Epithet field (Non-hybrid names) |
| subsp. | Subspecies |
| var. | Variety |
| subvar. | Subvariety |
| f. | Form |
| subf. | Subform |
Comments: Refer Infraspecific Rank Flag field (above) for
further details.
Notes: The transfer code (isprkhy2), as for other hybrid
fields which are used to transfer information about the second 'parent' of the hybrid
formula or intergrade conclude with 'hy2'. This should not be confused with isp2rk which
is the transfer code for the Second Infraspecific Rank Flag and isp2rkhy2
which is used to transfer the rank of the Second Hybrid of the Second Lowest
Infraspecific Epithet when the full taxonomic name is being transferred.
TDWG Short name: INFRANAME
Description: The epithet of the lowest infraspecific rank
of the name, entered in full.
Relevant standards: ABIS, ITF, TLR, MFN, Bisby (1994).
Domain/Range/Values: Alpha; any valid infraspecific taxon
epithet, all lower case.
Comments:
1. The entry must be one word (except as outlined in Rules, below).
2. It must only consist of lowercase letters (az), and may contain one or two hyphens. No other characters are allowed (except in the case of Rules 1.1, 2, 4 and 5, below).
3. The field may be left unfilled to indicate that the plant is
not identified below the species level. It must not be filled if the species
epithet is not known. Indeterminate entries like 'subsp.', 'var.' etc., are not
permissible.
See Comments under Infraspecific Rank Flag and Species
Epithet. fields.
Rules:
1. If the Infraspecific Rank Flag is subsp. var., subvar., f. or subf., then the entry must be an epithet in the rank denoted by that field, validly published under the ICBN, except in the following special case:
1.1 Where a new infraspecific taxon has not been formally described, subsp. nov., var. nov., subvar. nov., f. nov., or subf. nov. may be entered, if possible followed by a unique identifier, such as the collector's name and number or the locality
2. If the Hybrid Flag value is 'H', then the entry must represent the first 'parent' in a hybrid formula
If the Hybrid Flag value is 'H' but only one 'parent' of a hybrid formula is known, then enter the infraspecific epithet of that parent alone
3. If the Hybrid Flag is 'x', then the entry must be a Latin collective name for an infraspecific hybrid. The name must be valid under the Cultivated Code.
4. If the Hybrid Flag value is G, then the entry must be a
non-Latin collective name. It must be valid under the Cultivated Code.
Guidelines:
Under the rules of the ICBN, every trinomial below the level of species
is unique. Hence, Rhododendron arboreum subsp. delavayi var. peramoemum can
be known uniquely as Rhododendron arboreum var. peramoemum. Therefore the
name can consist of the genus, the species and the lowest infraspecific taxon name,
qualified by its rank.
TDWG Short name: INFRANAME
Description: The epithet of the lowest infraspecific rank
of the name of the second 'parent' in a hybrid formula or intergrade, entered in full.
Relevant standards: ABIS, ITF, TLR, MFN, Bisby (1994).
Domain/Range/Values: Alpha; any valid infraspecific taxon
epithet, all lower case.
Comments: Refer the Infraspecific Epithet field for
further details (above).
Notes: The authority of the infraspecific names are not given
when the name is a hybrid formula or intergrade.
TDWG Short name: INFRAUTHOR
Description: The author citation of the lowest
infraspecific epithet, in standard abbreviated form.
Relevant standards: ITF; Bisby (1994).
Domain/Range/Values: See under Species Author field,
above.
Comments: See under Species Author field.
Notes: The authority of the infraspecific names are not given
when the name is a hybrid formula or intergrade.
Description: An additional field to indicate the rank of the second
lowest infraspecific name (as given in the Second Infraspecific Epithet field),
which is at a higher level to that of the Infraspecific Epithet field. This field
is used when a 'full' taxonomic name is required (refer Comments and Notes,
below). This field is also used when a 'full' taxonomic name is required for the first
'parent' of a hybrid formula or intergrade.
Relevant standards: ITF; Bisby (1994).
Domain/Range/Values: See under Infraspecific Rank Flag,
above. Note: these additional fields are for non-hybrid infraspecific taxa, not for
hybrids, Collective names or cultivars.
Comments: This field has been included for those
institutions who wish to transfer and/or receive a complete ('full') taxonomic name (as
defined in Notes, below) in a form which is more easily inserted into a database
than the contents of the Full Name field (p. 47). When more than one infraspecific
name is being transferred, the following fields refer to the lowest level
infraspecific name: Infraspecific Rank Flag, Infraspecific Epithet, and Infraspecific
Author; whereas the Second Infraspecific Rank Flag, Second Infraspecific
Epithet, and Second Infraspecific Author all refer to the second lowest
level of infraspecific name (eg. var. and subsp., respectively). If institutions wish to
transfer more than two levels of infraspecific names in this format, then the third
lowest level has the number 3 included in the Transfer Code identifier (eg.
isp3rk, isp3, isp3au), and so on, as appropriate.
Notes: The 'full' scientific name includes the genus and species
names, together with all infraspecific names and ranks (where relevant) and all
appropriate authorities. Such 'full' names are extremely useful, especially if the
complete taxonomic name of the taxon is required.
Description: An additional field to indicate the rank of the second
lowest infraspecific name of the second 'parent' of a hybrid formula or intergrade (as
given in the Second Hybrid of the Second Infraspecific Epithet field), which is at
a higher level to that of the Second Hybrid Infraspecific Epithet field. This field
is used when a 'full' taxonomic name is required.
Relevant standards: ITF; Bisby (1994).
Domain/Range/Values: Refer Second Infraspecific Rank Flag,
above.
Comments: Refer Second Infraspecific Rank Flag, above.
Description: An additional field for the epithet of the second
lowest infraspecific rank of the name of the plant, when a full taxonomic name is
required (refer Comments under Second Infraspecific Rank Flag field, above).
Relevant standards: ITF; Bisby (1994).
Domain/Range/Values: See under Infraspecific Epithet
field, above. Note: these additional fields are for non-hybrid infraspecific taxa, not
for hybrids, collective names or cultivars.
Comments: Refer Comments under Second
Infraspecific Rank Flag field, above.
Description: An additional field for the epithet of the second
lowest infraspecific rank of the name of the second 'parent' of a hybrid formula or
intergrade, when a full taxonomic name is required.
Relevant standards: ITF; Bisby (1994).
Domain/Range/Values: See under Infraspecific Epithet
field, above.
Comments: Refer Comments under Second
Infraspecific Rank Flag field, above.
Description: An additional field for the author citation of the second
lowest infraspecific epithet, in standard abbreviated form.
Relevant standards: ITF; Bisby (1994).
Comments: Refer under Infraspecific Author and Second
Infraspecific Rank Flag fields, above. Note: these additional fields are for
non-hybrid infraspecific taxa, not for hybrids, collective names or cultivars.
Notes: The authority of the infraspecific names are not given
when the name is a hybrid formula or intergrade.
Description: A free text field to allow for the inclusion of
vernacular (common) plant names.
Domain/Range/Values: Vernacular name followed by language of each
name in round brackets ( ).
Comments: If more than one vernacular name, then each name (and
language group) is separated by a comma and a space.
Rules for naming agricultural, forestry and horticultural plant have recently been revised in the International Code of Nomenclature for Cultivated Plants (Ed. P. Trehane, Quarterjack Publishing, 1995). Following the lead of ITF2, HISPID3 allows compatibility with this code by introducing two new fields, the Cultivar Group Name and the Trade Designation Name, in addition to the Cultivar Name field. These three fields allow for an accurate interchange of these plants, in accordance with the rules of the above code. The only names that may be used in this code are the Cultivar epithet, the Cultivar Group epithet, and the Trade Designation name (or other similar trade name).
Signs to indicate hybrids (x) or graft chimera (+) must NOT be used in any of the following three fields. Authors names are not required by the cultivated plant code, and should not be appended to the names given at any of the three ranks.
Examples (from ITF2), in HISPID3 transfer format:
1. Brassica oleracea Cauliflower Group
| gen | "Brassica", |
| sp | "oleracea", |
| culgnam | "Cauliflower", |
2. Dracaena fragrans (Deremensis Group) 'Christianne'
| gen | "Dracaena", |
| sp | "oleracea", |
| culgnam | "Deremensis", |
| culnam | "Christianne", |
3.
Salix matsudana 'Tortuosa'
| gen | "Salix ", |
| sp | "matsudana", |
| culnam | "Tortuosa", |
Description: The cultivar group name of a plant.
Relevant standards: ITF; Trehane (1995)
Domain/Range/Values: Alpha
1. An entry in this field should consist solely of the cutivar group name.
2. If the accession cannot be assigned to a cultivar group, then the field should not be filled.
Comments:
1. The cultivar group name must be a valid cultivar group name under the International Code of Nomenclature for Cultivated Plants. This field should not contain a cultivar name or trade designation name.
2. The first letter of each word of the cultivar group name should be uppercase.
3. The word 'Group' should not be appended to the cultivar group name; this is redundant in this field for transfer, or for database storage ('Group' can easily be appended to the information contained in this field in output programs).
4. The cultivar group name should not be enclosed in parentheses
(these can easily be added to the information contained in this field in output programs
if required).(refer CULTIVATED PLANT NAMES example 2, below).
Guidelines:
1. A cultivar group is an assemblage of similar, named cultivars within
a genus or species (including hybrid genera and species), eg. Lolium perenne Early
Group. Such groups are often associated with a cultivar name, and in this case the Group
Name is normally enclosed by round brackets, eg. Lolium perenne (Early Group) cv.
Devon Eaver. For further details, see Article 4 of the International Code of Nomenclature
for Cultivated Plants.
2. Under the provisions of the International Code of Nomenclature for
Cultivated Plants, cultivar group names are written in outputs as contained between round
brackets or square brackets when a cultivar name or trade designation is given; if
no cultivar or trade designation is given then these brackets are omitted. In outputs the
word 'Group' always terminates the cultivar group name: eg. Brassica oleracea
Cauliflower Group, Dracaena fragrans (Deremensis Group) 'Christianne' or Dracaena
fragrans [Deremensis Group] 'Christianne'.
Description: The cultivar name of the plant represented by this
record.
Relevant standards: ITF; Trehane (1995)
Domain/Range/Values: Alpha; any valid cultivar name. The entry
should consist solely of the cultivar name. The abbreviation 'cv.' should not be used
(except under Comments 3 below), nor should the entry be enclosed in single quotes
(these should be added in printed outputs only).
Comments:
1. The cultivar must be a valid name published under the International Code of Nomenclature for Cultivated Plants.
2. Where the cultivar name directly follows the generic name, as in Tulipa 'Apeldoorn', the fields between Genus name and this field should not be filled (namely, the fields from Subgeneric group name through to Cultivar Group Name).
3. If the record represents a cultivar of unknown name, then 'cv.'
should be entered in this field. This appears to contradict the approach with species
names, but in this case a blank, space or null does not imply that the taxon is an
unidentified cultivar.
Guidelines:
1. A cultivar is part of the variation of cultivated plants being clearly distinguished by attributes that are distinct, uniform, stable and are retained when propagated by a suitable means. For further details, see Article 2 of the International Code of Nomenclature for Cultivated Plants.
2. Under the provisions of the International Code of Nomenclature for Cultivated Plants, cultivar names are written in outputs as contained between single quotes, eg. Citrullus lanatus 'Sugar Baby'. Double quotes or the abbreviation prefix 'cv. ' are not permitted under the Cultivated Plant Code.
3 The first character of each word in a cultivar name should be in
uppercase (A-Z).
Description: The trade name of an accession, where the taxon has
a registered trade name or other similar trade designation.
Relevant standards: ITF; Trehane (1995)
Domain/Range/Values:
1. An entry in this field should consist solely of the trade designation name, if applicable.
2. If the accession does not bear a designated trade name, this field
should not be filled.
Comments: The trade name must be a valid name published under the
International Code of Nomenclature for Cultivated Plants and accepted by the International
Registration Authority for the group concerned.
Guidelines: Trade names are used in place of or additional to a
cultivar name when the accepted cultivar name is not considered suitable for marketing
purposes.
Description: The full name of the plant, including full author
citation, hybrid name, hybrid formula, collective name, cultivar name (as appropriate).
Relevant standards: ITF
Domain/Range/Values: Free text field. All previous rules, as
described under the above name fields, apply in this field.
Comments: This field allows the full taxonomic name (including
author citation), horticultural names, trade names and patents. Where there is more than
one infraspecific rank (eg. quadrinomials or pentanomials), the reduction of this plant
name to a trinomial (with only the lowest infraspecific rank cited) obscures much of the
infraspecific hierarchy (refer discussion under RECORD IDENTIFICATION GROUP above).
Description: Any comments about the name of the plant are
transferred in this field.
Domain/Range/Values: Free text field.
Comments: Although mixed collections are unacceptable in HISPID3,
this field can be used to refer to such collections when the mixture is not significant.