Guide to the UPOV Code System
1. Purpose
1.1 The main purpose of the UPOV Code System is to enhance the usefulness of the UPOV-ROM Plant Variety Database ("UPOV-ROM") by overcoming the problem of synonyms for plant taxa. That is achieved by attributing each taxa a code according to the UPOV Code System ("UPOV code"); synonyms for the same plant taxa are attributed the same UPOV code.
1.2 The UPOV Code System is employed in the GENIE database, which has been developed to provide, for example, online information on the status of protection (see document C/40/6), cooperation in examination (see document C/40/5), experience in DUS testing (see document TC/43/4), and existence of UPOV Test Guidelines (see document TC/43/2) for different GENera and spec IEs (hence GENIE), and is also used to generate the relevant Council and Technical Committee (TC) documents concerning that information.
2. UPOV code construction
2.1 General basis
2.1.1 In general, the following UPOV code construction is used for the UPOV Code System:
(a) an alphabetic element of five letters (e.g. XXXXX) indicating the genus ("genus element");
(b) a three-letter element (e.g. YYY) indicating the species ("species element");
(c) where relevant, a further element of up to three characters (e.g. ZZ1) indicating a sub- specific unit ("sub-species element");
thus, XXXXX_YYY_ZZ1
2.1.2 In all cases, the five-letter genus element is to be provided, but the three-letter species element and the sub-specific element are only provided where necessary.
2.1.3 As far as possible, the elements try to follow the first letters of the botanical name of that element, e.g.:
Prunus PRUNU_
Prunus armeniaca PRUNU_ARM
2.1.4 In some cases, it is necessary to improvise to ensure that similar taxa have different UPOV codes (e.g. Platycodon = "PLTYC_" and Platymiscium = "PLTYM_"). In cases where the name is shorter than the UPOV code, the last letter of the name is repeated e.g. Poa = POAAA.
2.1.5 In the case of the sub-specific element, the UPOV code is used in a more flexible way to contain more than one level of ranking, thereby avoiding the need for extra elements in the UPOV code.
2.2 Inter-generic and inter-specific hybrids
2.2.1 The letter "x" is not used in the UPOV code to indicate hybrids.
(Background note: the multiplication sign ‘x’ is used in botany as an optional device to indicate hybridity, but is not part of a name in any sense and may or may not be applied according to the wishes and opinions of a botanical author or editor. What one person considers a hybrid, may not be so considered by another, thus we may see Solanum tuberosum or Solanum x tuberosum if the writer of the second version understands the potato species to be of hybrid origin.)
2.2.2 In the case of a genus which is formed as a hybrid between other genera, but which is taxonomically recognized in its own right (e.g. ×Triticosecale [= Triticum x Secale]), the "genus element" of the UPOV code is based on the taxonomically recognized "hybrid" genus. For example, ×Triticosecale has the UPOV code "TRITL".
2.2.3 In the case of a genus which is formed as a hybrid between two genera and which is not taxonomically recognized as a genus in its own right ("hybrid genus"), a UPOV code is created for the new "hybrid genus". The genus element of the UPOV code is produced by combining the first two letters of the female parent genus and the first three letters of the male parent genus. For example, a "hybrid genus" which was formed as a hybrid between Carlus (UPOV code: CARLU) x Phillipus (UPOV code: PHILL) would have the UPOV code "CAPHI".
2.2.4 In the case of a species which is formed as a hybrid between two species and which is not taxonomically recognized as a species in its own right ("hybrid species"), a UPOV code is created for the new "hybrid species". The species element of the UPOV code is produced by combining the first letter of the female parent species and the first two letters of the male parent species. For example, a "hybrid species" which was formed as a hybrid between Alpha one (UPOV code: ALPHA_ONE) x Alpha two (UPOV code: ALPHA_TWO) would have the UPOV code "ALPHA_OTW".
2.2.5 In the case of a hybrid genus (or species) which is formed as a hybrid between more than two genera (or species) and which is not taxonomically recognized as a genus in its own right, the same general approach is followed as for a hybrid between two genera (or species); the sequence of letters used in the UPOV code is based on the order of female parent followed by male parent.
2.2.6 The approach for introducing UPOV codes for hybrid genera and species, as set out in paragraphs 2.2.3 to 2.2.5, means that the UPOV code will distinguish between two hybrids produced using the same parents, but with the male and female parents reversed, e.g.:
ALPHA_OTW: Alpha one (ALPHA_ONE)) x Alpha two (ALPHA_TWO)
ALPHA_TON: Alpha two (ALPHA_TWO) x Alpha one (ALPHA_ONE))
2.2.7 In the case of "hybrid" genus (or species) (i.e. which is not taxonomically recognized as a genus (or species) in its own right), the GENIE database contains a link between the "parent" genera (or species) and the "hybrid" genus or species. Thus, when searching in GENIE, it is possible to search on a UPOV code, but to choose to also receive the results on all "linked" UPOV codes:
Example: Hybrid genus formed between Carlus x Phillipus
Genus UPOV Code
Carlus CARLU_(linked to CAPHI_)
Phillipus PHILL_(linked to CAPHI_)
Carlus x Phillipus CAPHI_(linked to CARLU_ and PHILL_)
A search on "CARLU" (Carlus) could be made to provide all varieties of Carlus and the hybrid genus Carlus x Phillipus. A search on "PHILL" (Phillipus) could be made to provide all varieties of Phillipus and the hybrid genus Carlus x Phillipus. A search on "CAPHI" (Carlus x Phillipus) could be made to provide all varieties of Carlus, Phillipus and the hybrid genus Carlus x Phillipus.
2.3 Grouping classification: Brassica and Beta
A grouping classification is used for UPOV codes within Beta vulgaris and part of Brassica oleracea. To indicate that a grouping classification is being used for those two species, the first letter of the third element of the UPOV code starts with "G". A summary of the structuring of the species is presented below:
|
UPOV code |
Botanical name |
Common name |
|
BETAA_VUL |
Beta vulgaris L. |
|
|
BETAA_VUL_GV |
Beta vulgaris L. ssp. vulgaris |
Beet |
|
BETAA_VUL_ GVA |
Beta vulgaris L. ssp. vulgaris var. alba DC. |
Fodder beet |
|
BETAA_VUL_ GVC |
Beta vulgaris L. ssp. vulgaris var. conditiva Alef. |
Beetroot |
|
BETAA_VUL_ GVF |
Beta vulgaris L. ssp. vulgaris var. flavescens DC. |
Leaf beet |
|
BETAA_VUL_ GVS |
Beta vulgaris L. ssp. vulgaris var. saccharifera Alef. |
Sugar beet |
|
BRASS_OLE_GA |
Brassica oleracea L. convar. acephala (DC.) Alef. |
Kale |
|
BRASS_OLE_ GAM |
Brassica oleracea L. convar. acephala (DC.) Alef. var. medullosa Thell. |
Marrow-stem kale |
|
BRASS_OLE_ GAR |
Brassica oleracea L. var. ramosa DC. |
Catjang |
|
BRASS_OLE_ GAS |
Brassica oleracea L. convar. acephala (DC.) Alef. var. sabellica L. |
Curly kale |
|
BRASS_OLE_ GAV |
Brassica oleracea L. convar. acephala (DC.) Alef. var. viridis L. |
Fodder kale |
|
BRASS_OLE_GB |
Brassica oleracea L. convar. botrytis (L.) Alef. |
|
|
BRASS_OLE_ GBB |
Brassica oleracea L. convar. botrytis (L.) Alef. var. botrytis |
Cauliflower |
|
BRASS_OLE_ GBC |
Brassica oleracea L. convar. botrytis (L.) Alef. var. cymosa Duch. |
Broccoli |
|
BRASS_OLE_GC |
Brassica oleracea L. convar. capitata (L.) Alef. var. capitata (L.) Alef. |
Cabbage |
|
BRASS_OLE_ GCA |
Brassica oleracea L. convar. capitata (L.) Alef. var. capitata L. f. alba DC. |
White cabbage |
|
BRASS_OLE_ GCR |
Brassica oleracea L. convar. capitata (L.) Alef. var. capitata L. f. rubra (L.) Thell. |
Red cabbage |
|
BRASS_OLE_ GCS |
Brassica oleracea L. convar. capitata (L.) Alef. var. sabauda L. |
Savoy cabbage |
|
BRASS_OLE_GGM |
Brassica oleracea L. convar. oleracea var. gemmifera DC. |
Brussels sprout |
|
BRASS_OLE_GGO |
Brassica oleracea L. convar. acephala (DC.) Alef. var. gongylodes L. |
Kohlrabi |
2.4 Variety Types
The basis of the UPOV code is a "vertical" botanical classification and, therefore, the UPOV code is limited in its scope to differentiate, in a "horizontal" way, types of variety (e.g. fruit varieties and ornamental varieties) which have the same botanical classification. However, it is possible to identify such "types" within the GENIE database. Thus, if types are created within a UPOV code within the GENIE database, it would be possible, for example, to search "MALUS" for all information related to apple, but also to refine the search, for example for all information which is specifically indicated as relating to fruit varieties only.
3. Procedure for the introduction and amendment of UPOV codes
3.1 Responsibility for the UPOV Code System
The Office of the Union (Office) is responsible for the UPOV Code System and the individual UPOV codes.
3.2 Repository of UPOV Codes
The definitive collection of UPOV codes exists exclusively in the GENIE database.
3.3 Introduction of New UPOV Codes / Amendments to UPOV Codes
(a) In the first instance, the Office will create a UPOV code on the basis of the Germplasm Resources Information Network (GRIN) database [1] , or other suitable references if the species concerned are not included in the GRIN database.
(b) Where the Office is aware of relevant experts for the genus or species concerned, or is advised of such experts, for example by the proposer of a new UPOV code, it will, wherever possible, check its proposals with those experts before creating the UPOV code.
(c) New UPOV codes might be proposed by any party, but it is expected that the majority of proposals will be made by contributors to the Plant Variety Database. Where the Office receives such proposals, it will respond by updating the GENIE database with the new UPOV codes in a timely manner and, in particular, will seek to ensure that new UPOV codes are available to allow their use for the forthcoming edition of the Plant Variety Database. In addition, the Office will add new UPOV codes where it identifies a need.
(d) In general, amendments to UPOV codes will not be made as a result of taxonomic developments unless these result in a change to the genus classification of a species. The "Explanatory notes on variety denominations under the UPOV Convention" (document UPOV/INF/12/1) contain UPOV variety denomination classes; for genera and species not covered by the List of Classes in Annex I to document UPOV/INF/12/1, the general rule ("one genus / one class") is that a genus is considered to be a class (see document UPOV/INF/12/1, Section 2.5.2 and its Annex I). Therefore, it is important that the first element of the UPOV code can be used to sort species into the correct genus. The UPOV codes will also be amended if there are consequences for the content of a variety denomination class where the list of classes applies. Amendments to UPOV codes will be handled by the same procedure as the introduction of new UPOV codes as in paragraphs (a) and (b), above. However, in addition, all members of the Union and contributors of data to the Plant Variety Database will be informed of any amendments.
(e) New and amended UPOV codes will be presented to the relevant Technical Working Parties (TWP(s)) for comment at their first available session. If the TWP recommends any change, this will be treated as an amendment according to paragraph (d), above.
(f) Checking by Technical Working Party(ies): the Office determines the relevant TWP(s) for checking each UPOV code on the basis of available information.
(g) Checking by all authorities: all the experts of the relevant TWP(s) to be invited to check the UPOV codes where:
(i) many authorities (e.g. 10 or more) have practical experience in DUS testing (based on GENIE database / document TC/xx/4 (e.g. TC/43/4)), have provided interested experts in the drafting of relevant Test Guidelines and/or have protected varieties (based on Plant Variety Database (UPOV-ROM)); or
(ii) they concern genera or species for which a wide review is considered appropriate by the Office (e.g. because it concerns a proposal for a species or sub-species not previously recognized within the genus, or a proposal for restructuring of the UPOV code).
(h) Checking by specific authorities: in cases not covered by (g) above, the experts of the relevant TWP(s) of specific authorities will be invited to check the UPOV codes. The specific authorities being those which have practical DUS testing experience, have provided interested experts in the drafting of relevant Test Guidelines, or which have granted protection for varieties covered by the relevant UPOV code.
3.4 Updating of Information Linked to UPOV Codes
(a) UPOV codes might need to be updated to take account of, for example, changes in taxonomic classification, new information on common names, etc. In the case of changes of taxonomic classification, this might, although it is emphasized that this is not necessarily the case (see section 3.3 (d), above), result in a need to change the UPOV code. In such cases, the procedure is as explained in section 3.3, above. In other cases, the Office will amend the information linked to the existing UPOV code as appropriate.
(b) The TC, the TWPs and individual communications from members and observers of these bodies will be the principal routes by which the Office will update its information.
4. Publication of UPOV Codes
4.1 As explained in Section 3.2, all UPOV codes can be accessed in the GENIE database, which is made available on the freely accessible area of the UPOV website.
4.2 In addition, the UPOV codes, together with their relevant botanical and common names, variety denomination class and linked hybrid/parent UPOV codes, as contained in the GENIE database, are published on the first restricted area of the UPOV website (see http://www.upov.int/restrict/en/upov_rom_upov_code_system/index.htm). That information is published in a form that facilitates electronic downloading of the UPOV codes for use by contributors to the UPOV-ROM.
[1] USDA, ARS, National Genetic Resources Program. Germplasm Resources Information Network - (GRIN) [Online Database]. National Germplasm Resources Laboratory, Beltsville, Maryland.
URL: http://www.ars-grin.gov/cgi-bin/npgs/html/tax_search.pl
