TDWG root element: container for one or more DataSets. Data sets Berendsohn 9 Dec 2004 Root element of the schema, forming the container for one or more data sets. Allows to handle several different datasets with a single response operation A dataset containing unit data and their shared metadata elements. Data set Berendsohn 9 Dec 2004 NBN: Survey A container element for one to many unit data records and their shared metadata elements. The metadata relate to the source, provision, the ownership and rights etc. pertaining to the entire dataset. Attribute: xmlns, indicating the schema version used. A globally unique identifier for the entire data collection the present dataset was derived from. The exact format and/or semantics are still under discussion. Berendsohn 6 Mar 2005 Metadata item normally not used for end-user display. UDDI registry element for GBIF registry. Questions and feedback about availability of a provider or resource should be directed to the technical contact. This contact normally represents the Agent acting as the publisher of the datasets in the network. The element is unbounded to provide for alternative contacts (vacation etc.). Berendsohn 6 Mar 2005 UDDI registry element ("AdministrativeContact") for GBIF registry. Questions and feedback about data, or restrictions on use of the data should be directed to the adminstrative contact. This contact normally represents the agent acting as the original supplier or custodian of the dataset. If a content contact is given on the unit-level, that one should be used for end-user purposes. The element is unbounded to provide for alternative contacts (vacation etc.). Content contact Berendsohn 15 Dec 2004 Other known on-line providers of this dataset. Berendsohn 6 Mar 2005 The UUID (identifier in the UDDI registry) of another data provider known to serve this dataset. Berendsohn 6 Mar 2005 Metadata referring to the principal source of the entire data collection (the metadata scope may be wider than the objects actually contained in the data set). In its current form, this collection represents a mixture of elements useful for resource discovery (e.g. scope) with metadata actually pertaining to the received (partial) dataset. Berendsohn 6 Mar 2005 A container for one or more unit data records from the gathering Berendsohn 6 Mar 2005 A container for all data referring to a unit (specimen or observation record) Berendsohn 6 Mar 2005 Elements describing the event and site of collecting or observing a unit. A string that identifies all material or records that resulted from a collecting or observation event. Gathering code Berendsohn 01 Mar 2003 NBN: Sample_Reference. Darwin Core 2: Field Number. Date(s) and time(s) of the collecting or observation event Gathering date and time Berendsohn 01 Mar 2003 HISPID4: cdat. HISPID4: cdat2. NBN: Survey_Event_Date (3 part vague date). BioCISE Model: GDate. Darwin Core 2: Year/Month/Day collected. A container element for the agent(s) responsible for collecting or recording. Gathering agents Berendsohn 01 Mar 2003 BioCISE Model: GatheringAgent incl. LegTm1_Fk, LegTmAl_Fk, LegTmPr_Fk. Sample_Recorder. Either a single person or several persons forming a team or an organisation or (sometimes) a project name The person, or one of the persons or team(s) or organization(s) responsible for collecting or recording. Attributes: a flag indicating the primary collector, and a sequence number. Gathering agents Berendsohn 01 Mar 2003 BioCISE Model: GatheringAgent incl. LegTm1_Fk, LegTmAl_Fk, LegTmPr_Fk. Sample_Recorder. An agent (person or organisation) First Collector may be flagged by means of an attribute, which is normally a single person in charge of field book to which records are added or the team leader. It may be the person whose collection number is cited but it could be an organisation name where the collector is not known. Further collectors can be cited who were part of the team or other individuals who may have passed specimens or data onto the team. Free text alternative for individual Agent. Agent text Free text details for Agent. Neil Thomson Free text details for Agent. Agent text Free text details for Agent. Neil Thomson Agent organization name and code(s). Organization Agent organization name and code(s). Neil Thomson Agent Person details. Person Person agent name. Neil Thomson Free text representation or concatenated version of those responsible for collecting or recording. A container element for references to (or texts of) permits related to the gathering. Project information concerning the gathering event. Project Berendsohn 01 Mar 2003 BioCASE Model: Project Proj_Pk. Title of collection project Project title Berendsohn 01 Mar 2003 BioCASE Model: ProjTitle. Project name if of special importance or cited on a collection label Inventory of the Montecristo National Park Contact details for Project Officer or other person with knowledge of the project. Project contact Berendsohn 01 Mar 2003 The 'platform' from which observations or collections were made, e.g. the name of a research vessel or a remote operated vehicle. Platform name Berendsohn 01 Mar 2003 BioCISE Model: PlatformNm. ASC: PLATFORM-NAM. Refers to the 'platform' from which observations were made e.g. the name of a research vessel or a remote operated vehicle. The method (including technical means) used to make the collection or observation. Original locality data as appearing on a label or in an original entry. Locality Text The locality data from the label as a string of text HISPID Jim Croft HISPID New Caledonia, below summit region of Mt Mou. New South Wales, Central Tablelands 12 km SW or Armidale. As far as possible this field should be transcribed verbatim from the specimen label Where possible, the language of the label locality should be indicated with the language attribute. Editorial omissions for brevity, etc. should be indicated with an ellipsis (...) and interpreted or implied text should be included in square brackets [ ]. Clarification is needed as to whether this field includes the full locality information from the Continental level down, or just regional locality string excluding the higher level named areas or regions [JRC] Details of the country. Separate from NamedArea for compatibility reasons. Country Elements covering the representation of the country and its name. Brummitt 1992 HISPID4 BioCASE Model: GDate Maps to Darwin Core 2: Country through either ISO2Letter (future) or CountryName (current). Historical country names and water bodies outside the coastal zone can be entered under named area. CountryNameDerived is provided for a country name that has been derived, for example from a system supplied dictionary, by library consultation or other independent research. At least one of CountryName or ISO2 or ISO3 should be present but more are allowed. This should be the political country having jurisdiction over the collection site. Country names and ISO codes can theoretically be part of controlled enumerations but if included within the schema would blow it out to an unacceptable level; is it possible to refer to these lists externally with physically invoking them? [JRC] Atomised place names as applied to the collection or observation site; with possibility for hierarchical structuring and categorization. Atomised place name with possibility for hierarchical structuring. Attribute for sequence. Specified relationship to a named place that does not directly apply to the site of collection or observation, e. g. 10 Km South of Mytown. The nearest named place to the collection or observation location Near named place Jim Croft ABIS. AUSLIG. HISPID4: nnp. TDWG: Stanloc. Distance and directional point. Relation to nearest named place Free text description of further details pertaining to the observation, sampling, or collection locality which which did not fit into the previous elements. Area detail Berendsohn 01 Mar 2003 Additional locality details not covered by the named area or nearest named place elements Spaceholder for GML-conformant schema extension to express locality coordinates and footprint data (Geographical Markup Language) GML Type Container for GML-Standard Elements Retrieval of a boundary polygon or centroid spatial reference relating to the gathering site. URL (GET) or POST text, for Web Feature Service (OpenGIS Consortium Specification 01-023) reference. URI (e.g. web address) for the location of a boundary polygon or centroid spatial reference relating to a gathering site, according to the Web Map Services (WMS) specification of the Open GIS Consortium Web Map Service URL WMS is already common use. You can link to Microsoft's Terraserver and lots of other resources.[Reed Beaman] Container for multiple sets of coordinates indicating the site of collection or observation. Attributes for Original data and for begin and end of sequence . Composite element to allow recording multiple coordinates or same coordinate in different systems Coordinates measuring system e.g. GPS, field map reference, inferred map reference HISPID4: geosou (part). BioCASE Model: CrdMsmthMtd . ABCD Workshop 1 HISPID4: sqz. ABCD Workshop 1 HISPID4: sge (part). HISPID4: sgn (part). ABCD Workshop 1 ABCD Workshop 1 Geospatial coordinates recorded using a grid system BioCASE Model: Geospatial Coordinates GridSysNam, GridCode, GridPreQual, CrdMsmtMth. ABCD Workshop 1 Grid system name e.g. "GB OS" BioCASE Model: GrdSystTxt. ABCD Workshop 1 ABCD Workshop 1 Grid reference precision qualifier BioCASE Model: GridPrecQual. ABCD Workshop 1 Element that allows the recording of the latitude and longitude of a recording or collecting position. Could be simplified by converting many of the sub-elements into attributes. ABIS. ITF. AUSLIG. ABCD Workshop 1 Maps to Darwin Core 2: Longitude. Express in decimal degrees Darwin Core 2: Longitude. ABCD Workshop 1 Maps to Darwin Core 2: Latitude. Express in decimal degrees Darwin Core 2: Latitude. ABCD Workshop 1 Mathematical surface on which the mapping and coordinate system used for the geocodes of the record are based AS/NZS4270 spatial transfer standard, SDTS spatial transfer standard. ABCD Workshop 1 ABCD Workshop 1 Free text statement of degree of accuracy HISPID4: includes geoacy TDWG: LatAccurr, LongAccur. ABCD Workshop 1 Maps to Darwin Core 2: Coordinate Precision. An estimate of how tightly the collecting locality was specified; expressed as a distance in meters corresponding to a radius around the Lat/Long coordinates. Use NULL where precision is unknown, cannot be estimated or is not applicable. Neil Thomson 7/2002 Darwin Core 2: Coordinate Precision. The altitude of the gathering site land or floor level given as distance above (positive) or below mean sea level. Altitude Berendsohn 02 Mar 2003 Darwin Core 2: Minimum Elevation (lower value). Darwin Core 2: Maximum Elevation (upper value). Although this could be covered by a generic element for site measurements, the separate Altitude element is preserved for the sake of clarity. Note the difference to the Height and Depth elements, which are measured relative to a local surface. Vertical distance point or range measurement in relation to a ground datum such as water level, or level of the sea floor for benthic samples. Depth Berendsohn 01 Mar 2003 Darwin Core 2: Minimum Depth (lower value). Darwin Core 2: Maximum Depth (higher value). Although this could be covered by a generic element for site measurements, the separate Depth element is preserved for the sake of clarity. Positive below the surface, negative above (e.g. collecting above sea level in tidal areas). Vertical distance measure or range in relation to a ground datum, e.g. ground level. Height Berendsohn 01 Mar 2003 Darwin Core 2: Minimum Depth (lower value). Darwin Core 2: Maximum Depth (higher value). Although this could be covered by a generic element for site measurements, the separate Height element is preserved for the sake of clarity. Positive above the surface. Further measurements or facts taken at the collection locality at the time of collection, e.g. (water-) temperature, slope, weather conditions, etc. Images taken at the Gathering site A container for geological dating and rock unit names related to the site or sample locations Stratigraphy Berendsohn 01 Mar 2003 LNHM model. Allows the linking of geological dating and rock unit names to sites or sample locations. Structure allows for full analysis of stratigraphy e.g. to allow fossils in collections to be sorted by period and zone. Also allows for free text terms when their status is unknown or for more full descriptions of stratigraphy of site. An container element for citing biotope type terms (e.g. classification terms) and measurements (e.g. vegetation height, salinity, slope) related to the unit's gathering site Attribute for classification system used. Biotope classification NBN: Short_Name. Attribute for type designating ShortName, Long name, Code, or BiotopeText Biotope name NBN: Long_Name. Free text field for informal recording of Biotope Biotope text A container allowing to linking any biotope-related measurement to the site description Biotope measurements Although this could be covered by a generic element for site measurements, the separate element is preserved for the sake of clarity. Relationship of the unit gathered with other taxa at the gathering site Synecology Berendsohn 01 Mar 2003 HISPID4: asspp. Note this can be recorded as a feature of a location (e.g. as a syntaxon, or that at this site the following species are known to grow together) or can be used to record an observed relationship (e.g. caterpillar and observed food plant, parasite and host etc.) but this should better be expressed as a unit association A syntaxon name and category assigned to the gathering site. Syntaxon Berendsohn 01 Mar 2003 Free text comment on synecological features of the gathering site. Comment Other taxa observed at the gathering site Associated taxa Berendsohn 01 Mar 2003 Note that the determination of the associated taxa in this case relies on the collector's information Other taxon found at the gathering site Taxon identified Facing direction (aspect) of whole site or sample point. Aspect HISPID4: Aspect (asp). Measured in either letters (e.g. NE, SW) or Degrees (e.g. 270). Further text referring to the gathering event that does not fit one of the elements specified. Notes The application of a name (or concept), i.e. the data pertaining to an identification event and the result of the identification itself. ABCD Editorial Team HISPID, DarwinCore A complex type that supports the application of a name (or concept) to a Unit (specimen, observation, etc.), with appropriate metadata about the Identification. Also known as Determination. See component elements An Identification must include a TaxonIdentified. At least one instance of this type should be designated as the preferred identification. More than one identification could be marked as preferred, but only in cases where the same taxon has a valid name under two codes of nomenclature. Should TaxonIdentified be called TaxonomicIdentification? and the type TaxonomicIdentificationType. The result of the identification, currently either a material (substrate) or a taxon name, but in the future to be extended to include other types of identifications used in natural history collections and surveys. The Taxon (concept) or Taxonomic name assigned to the unit (or excluded, "non") in the Identification. ABCD Workshop 1 A material identified as the result of the identification event (e.g. a non-organismic substrate of a microorganism) True to designate current identification. True to designate negative identifications. True to designate the idenfication under which the entire unit is stored (in a physical collection) or otherwise preferrably referenced. Used to designate the role of the identification result (e.g. substrate, isolate, host, parasite, etc.) Atomized record of individual, team member, or organization that made the identification. Charles Copp 10/2001. ABCD Workshop . Walter Berendsohn 9/2002. HISPID4: vnam; NBN: determiner. Atomised data for the parts of the Identifier's name. Charles Copp 2001. ABCD Workshop 1 The Organisation the Identifier is affiliated with, or the Organisation (institution) acting as the identifier. Alternatve text indicating the person, person team, or Organization that made the identification. A reference which has provided the identification (and - if present - the identifier's name and/or organisation). The entire identification event was taken from the literature or comparable source given here. Note that this is not the literature (e.g. key) used to obtain the result (see IdentificationReferences). Indication of the nature of the taxonomic verification; e.g. "conf." or "det." References that were used by the identifier to provide the identification (e.g. by means of providing a key or a description of the taxon). It circumscribes the taxon identified (and thus can act as a potential taxon's sec. reference). Note: this is not the citation from which and identification was taken, see under Identifier/IdentificationSource. A reference (e.g. an article or monograph) that was used as the base for the identifier's taxon identification (e.g. by means of providing a key or a description of the taxon). It circumscribes the taxon identified (and thus can act as a potential taxon's sec. reference). Note: this is not the citation from which and identification was taken, see under Identifier/IdentificationSource. HISPID4: vlit. NBN: Source. Issue 1: I think IdentificationReference and IdentificationSource have reversed names and semantics. Source should refer to where the identification is recorded, while "reference" should refer to a publication used to make the determination, but not containing the identification. Issue 2: Should we recommend that "field tag", and "determination slip" be recorded when something "usual" is the IdentificationReference. In my experience, IdentificationReference is not recorded in cases that are typical (e.g., det.slip, field tag). The reference is recorded only when the reference is a published work and when that specimen's identity is a prominent feature of the publication. Simply being listed in the material examined section would not be significant enough to warrant the effort of entering a special IdentificationSource record. (Listing in a material examined section would warrant a general bibliographic citation for a Unit.). Done. Date of the identification event. HISPID4 : vdat and texvdat are included. NBN: determination_date (vague date ) Darwin Core 2 fields: YearIdentified, MonthIdentified, DayIdentified. See DateType for general usage. Identification dates are commonly unknown (element optional), or incompletely known. Missing information reduces precision of the date; i.e., known only to Year or Year and Month. Sometimes identification dates are inferred from a researcher's visit or duration of a loan. 1985-07-14 July 14 July 14, 1985 July 14, 1985 We probably don't need IdentificationDate to support the full range of date time elements that are present in the DateTime. It's hard to imagine a realistic case where time of day could be relevant to an identification. If year is unknown, simple text will provide the only function needed -- human readability of the existing information. (Retrieval and sorting by interval in the annual cycle, as we want to support with CollectionDate, is irrelevant in this case.) A single ISO 8061 Date field, along with an IdentificationDate text is sufficient to cover the needs around this concept. -- Blum, 2002-12-10 The method by which the identification was obtained, e.g. details of molecular analysis or acoustical procedures. Supplementary remarks about the identification. HISPID4: idcom. NBN: Comme. The level to which the identification has been verified. Different standards may use different values here. See ITF-2 for an example. The name and category of an administrative or geoecological area. Allows recording of categories for local or national subdivision levels, geomorphological units, protected areas, etc. Named area class Berendsohn 02 Mar 2003 Classification categories, which are often treated as individual elements in other standards. County District State Municipio Island Island group Water body Drainage National park Mountain Name of a geographic, geomorphological, geoecological, or administrative area. Area name Berendsohn 02 Mar 2003 Darwin Core 2: Locality. Darwin Core 2: State Province. Darwin Core 2: County. Atlantic coast Santa Cruz Weinheim Andes El Imposible Standard coding scheme the AreaCode adheres to. Area code standard Berendsohn 02 Mar 2003 The name of a standard scheme for area codes Euro+Med standard territories TDWG World Geographical Scheme for Recording Plant Distributions version 1 Abbreviation or code for area names Area code Berendsohn 02 Mar 2003 TDWG World Geographical Scheme for Recording Plant Distributions version 1 Euro+Med standard territories Data source It is presently not clear, what this reference refers to [WB] Elements for all unit-level data A globally unique identifier for the unit or the unit record. The exact format and/or semantics are still under discussion. Unique identifier (code or name) of the institution holding the original data source (first part of record identifier). In specimen collections, this is normally the institution or private holder of the collection itself. For herbaria and botanical gardens, the standard abbreviations should be used. Source institution code Berendsohn 16 Jan 2004 FAO/IPGRI multi-crop passport descriptors (MCPD) EURISCO: Institution Code An institutional abbreviation, perhaps with indication of the standard it pertains to (e.g. IH-P for Index Herbariorum and the herbarium at the MNHN in Paris. A controlled vocabulary for collection institutions, but inclusion of private collections must be made possible. For FAO/IPGRI and EURISCO, this is defined as the FAO Institute Code of the institute where the accession is maintained, which consists of the 3-letter ISO 3166 country code of the country where the institute is located plus a three-digit number. The units within the datasource are not necessarily all owned or administered by this institution Name or code of the data source (unique within the institution, second part of the record identifier) Source name ITIS*ca draft metadata May be the name of a collection if all records stem from a single collection. Together with the element SourceInstitutionCode, SourceName provides a unique identifier for the dataset's original source Mandatory second partial identifier for a dataset. A unique identifier for the unit record within the data source. Preferrably, the ID should be stable in the database, so that it also can be used to find the same record again (e.g. for data exchange purposes). Third part of the record identifier. Unit Identifier Berendsohn 14 Jan 2004 HISPID 3: Accession Identifier (=UNIQUEID, =ACCESSIONID, =accid). ITF 2: Accession Identifier (=accid). BioCISE Model: Unit_ID. NBN: Sample_KeyUnit key or Identifying number - can be multiple. Darwin Core 2: Catalog Number. EURISCO: Accession number FAO/IPGRI MCPD: Accession number. An identifier for the unit record, unique within the DataSet. Should provide the key by which a specimen or specimen component can be identified. Numeric catalogue number. Facilitates soriting of numbers. Numeric catalogue number. Where present, this allows searches on a range of catalogue numbers. Name or other indication of the person or team that created or last edited this record. BioCASE Collection Profile. Name of the person who last edited this record. Date of creation or last change of this unit record. Date last edited Berendsohn HISPID 3: -. ITF 2: -. Darwin Core 2: Catalog Number. Simple date indicating the last change of the record. The legal owner of the unit record. Note that ownership of physical specimens is handled under SpecimenUnit. If present, overrides the equivalent Ownders element on the level of dataset. Specific rights, terms and other conditions pertaining to the individual record. If present, override the equivalent statements on the level of dataset. Copyright, IPR, and ownership for the individual unit record where different from those stated under DataSet, over which they take preference Container element for one to many content contacts for the unit. If present, overrides the equivalent ContentContact on the level of dataset. Questions and feedback about data, or restrictions on use of the data should be directed to the contact given here. If present, overrides the equivalent ContentContact on the level of dataset. Reference that is the source of the information about the unit given in the record. Unit data copied from Berendsohn 6 Mar 2005 Published reference where the information on this unit originates from. Container element for references citing the unit See SourceReference for the case that the record is based on a publication. Published reference citing this unit. Unit cited in Berendsohn 6 Mar 2005 Published references citing this unit. Container element for identification events, i.e. the circumstances and result of assigning a name to the unit. In cases where more than one name applies to a single unit, several identifications should be formed and flagged as preferred. Relationships between differently identified sub-units of the unit can be specified by means of the IdentificationRole. Assignation of a scientific or vernacular name to the unit. Berendsohn This is a free text field for use when extracting data from datasources where the identification or verification history (or part of it) is a free text field. In normal circumstances the history can be constructed by sorting identification events by date and reference to the preferred identification flag HISPID4: vhist. An indication of what the unit record describes. Note that the element SourceReference provides for the case that the record is based on a publication. Physical basis of the record Berendsohn 1/2004 Darwin Core 2: Basis of Record. An abbreviation or controlled vocabulary indicating what the record represents. Has been turned into an enumerated type after ABCD v. 1.2 Part(s) of organism or class of materials represented by this unit. LNHM: specimen part Part(s) of organism represented by this specimen. whole organisms / antlers / bark / blood samples / bones / bulbs / claws / cocoons / DNA / eggs / extracts / feathers / feeding remains / fruits / galls / heads / hooves / horns / leaves / mixed / nests / pellets / pollen / roots / seeds / shells / skins / spores / teeth / wood / other Physical state-specific subtypes of the Unit A Unit subtype containing data elements specific to specimens (living, fossil, or preserved). A Unit subtype containing data elements specific to physical specimens. The legal owner or holder of the physical specimen Acquisition date, source and type. Acquisition date, source and type. Textual statement of the date of acquisition of the specimen by the institution The date that the specimen was acquired by the institution. Free text field for informal recording of acquisition source details. ITF 2: Donor (=don) Free text field for informal recording of acquisition source details. Type of acquisition. Type of acquisition. Bequest Purchase Name of person and/or organisation the unit was acquired from (e.g. depositor of a strain). Accession details. Accession details. Repeatable triple to accommodate accession number in multiple catalogues. Textual statement of the date on which the accession was recorded. BioCISE Model: AccDate. The date on which an accession was recorded in the accessions register. Identifier of an accessions catalogue or numbering scheme which contains the SpecimenUnit Identifier of an accessions catalogue or numbering scheme which contains the SpecimenUnit The institutional number applied to an accession and recorded in the accessions register. BioCISE Model: AccCode_Pk. The institutional number applied to an accession and recorded in the accessions register. Helps to link items (e.g. several specimens may share one accession number). Specimen preparation details, possibly a sequence of preparation steps Specimen preparation details. Specimen preparation details. Description of preparation type. Darwin Core 2: Preparation Type. no treatment / alcohol / deep-frozen / dried / dried and pressed / formalin / refrigerated / freeze-dried / glycerin / gum arabic / microscopic preparation / mounted / pinned / other Process used in preparing the specimen. Process used in preparing the specimen. Materials and chemicals used in the preparation of the specimen. Materials and chemicals used in the preparation of the specimen. Person and/or institution responsible for or effecting the preparation. Label text(s), writing or inscription(s). LNHM. The text of labels attached or associated to the unit, or writing or other inscription directly upon or carved into it. Label or inscription Text transcription of an inscription Position of inscription, writing or mark. Position of inscription, writing or mark. Name of person who created the label, writing or inscription. Name of person who created the label, writing or inscription. Summary, interpretation or opinion of the text. Summary, interpretation or opinion of the text. A wrapper for previous units. A container for past ID and location of this specimen. History of specimen Changes of ownership and transfers between collections by sale, splitting or merging of collections Name or code of collection previously holding this specimen. Name of collection previously holding this specimen. Identifier of specimen in previous collection. BioCISE Model: Unit_ID. ITF-2: Donor's Accession Identifier (=donac). NBN: Sample_KeyUnit key or Identifying number - can be multiple. Darwin Core 2: Previous Catalog Number. Identifier of specimen in previous collection. Dates that the specimen was held in previous collection. NBN: vaguedatestart, vaguedateend and vaguedatetype. Dates that the specimen was held in previous collection. Any further information about this specimen in its previous collection. Any further information about this specimen in its previous collection. An alternative text identifying the previous unit when no ABCD standard ID s can be assigned. Information on the type status of the specimen. Nomenclatural type designation Berendsohn 12 Jan 2004 Information on the type status of the specimen. The name based on the specimen. Typified name Berendsohn 12 Jan 2004 HISPID4: basnam. TLR. The name based on the specimen. Bauhinia divaricata L. An alternative solution to this unstructured element would be the use of the scientific name structure given under identification It has been suggested to treat the type assignation as a special case of identification. Although this is without doubt true, it would mean to introduce the entire typification structure to the identification structure (because more than on name may be directly typified by the same specimen). As nomeclatural types are only a subtype of specimens, and these are only a subtype of units, it was decided to assign the typified name in the specimen domain. If it is to be found by a normal name search, it should be repeated as an identified name under identifications. Published reference. Nomenclatural reference Berendsohn 12 Jan 2004 Published reference. Sp. Pl. ed. 1, 374. 1753./> Full term designating the status. Darwin Core 2: Type Status. Full term designating the status. Holotype Isolectotype The application of an enumeration (controlled vocabulary) for this element has to be evaluated. However, a free text field is clearly necessary to accommodate existing datasets, as shown by the following list of terms (supplied by Charles Hussey as the contents found in databases at the NHM in London): [(Syn)type (?); Allotype; Allotypes; Cotype; Cotype (?); Cotype (see note); Cotype Genotype; Cotype(s); Cotype(s) (see note); Cotypes; Cotypes (see note); former syntypic material (?); Holotype; Holotype (?); Holotype (?), desig. Lectotype; Holotype (allotype attached); Holotype (dubious); Holotype + Paratype; Holotype + Paratypes; Holotype Allotype; Holotype Allotype Paratypes; Holotype and 2 Paratypes; Holotype and 6 Paratypes; Holotype and Paratype; Holotype and Paratypes; Holotype and young phase; Holotype Paratype; Holotype Paratypes; Holotype Paratypes (2); Idiotypes; includes Holotype(?)(1881.10.26.117); Lectotype; Lectotype (?) / syntypic material; Lectotype + 2 Paralectotypes; Lectotype + Paralectotype; Lectotype and Paralectotypes; Neotype; Neotype and Paraneotype; Paralectotype; Paralectotype(s); Paralectotypes; Paratype; Paratype (?); Paratype (see note); Paratype / Topotype (?); Paratype(s); Paratypes; Paratypes (?); Paratypes (of S. pseudobrowniana); Paratypes (see note); Para[lecto]type; Para[lecto]type(s); Para[lecto]types; Parelectotype; part of type series; parts of Syntype; parts of Syntypes; Possible syntypic material; Referred material; Referred specimen in type desc; Syntype; Syntype (?); Syntype (dubious); Syntype (may be holotype); Syntype (see notes); Syntype fragment; Syntype(s); Syntypes; Syntypes (?); Syntypes (see note); syntypic material (dubious); Topotype; Topotype(s); Topotypes; Topotypes (see note);] Indication whether the type is conserved or rejected/suppressed by the Code or is proposed for conservation or suppression/rejection Indication whether the type is conserved or rejected/suppressed by the Code or is proposed for conservation or suppression/rejection Indicator for unverified type status (kind and fact). Indicator for unverified type status (kind and fact). The person assigning or verifying the type status of the specimen. The person assigning or verifying the type status of the specimen. Date of verification. Date of verification. Further information about the verification process. Further information about the verification process. Data elements specific to observation (recording) units. Note that most observation data items are site related and thus covered under Gathering. A Unit subtype containing data elements specific to observation (recording) units. Numbers or other registration mark associated with an observation record. Attribute for PreferredFlag. Separated from the equivalent AccessionNumber of specimen collections because of the more standardised approaches taken in physical collections. Numbers or other registration mark associated with an observation record. Attribute for PreferredFlag. field observer numbers grid cell numbers Collection type and/or taxonomic domain-specific schema extensions (subtypes of the Unit). Data specific to microbial and similar culture methods. Data specific to mycological and lichenological units. Data specific to herbarium specimens (incl. mycological specimens). Data specific to units in botanical live (horticultural) collections. Botanical garden unit Berendsohn HISPID 3: n/a. ITF 2: Accession data (group) Data specific to units in plant genetic resource collections, e.g. gene banks. Data specific to zoological units. Data specific to palaeontological units. Multimedia objects such as images, movies, etc. relating to (or forming) the unit. Note that RecordBasis should be set accordingly if the multimedia object actually is the unit in the collection (e.g. collections of images taken in the field, sound recordings, etc.). Relationships of this unit with other units in ABCD conformant datasets. A binary relationship or association of units. Neil Thomson 2003 A relationship or association with another unit in this dataset. host/parasite relationships parental relationships observed pollinators substrate First part of a fully qualified identifier of a related item's dataset. Second part of a fully qualified identifier of a related item's dataset. Together with AssociatedUnitID this maps to Darwin Core 2: Related Catalog Item. First part of a fully qualified identifier of a related item within a dataset. Fully qualified identifier of the related item within the specified dataset. Darwin Core 2: Related Catalog Item. Second part of a fully qualified identifier of a related item within the a dataset. Description of the association. Darwin Core 2: Relationship Type. Description of the association. Further information about an association. Further information about an association. A container for groupings of this unit with other units in this dataset by means of an additional ID. A unit assemblage handles symmetric relationships between several units. A unit assemblage handles symmetric relationships between several units. herd of animals batches of specimens Identifier for assemblage. Identifier for assemblage. Name of assemblage. Name of assemblage. Unit may belong to one or several collections or survey projects which have distinctive names and do not correspond to the SourceName. Note that this element refers to the name accepted by the specimen or data holding institution, this may or may not be different from the project name given under Gathering. Elements describing the field events that created the sampling unit and their location. A number assigned to the unit by the collector or observer. Note that the respective collector's name is found under gathering (GatheringAgents). Collector's field number Berendsohn 14 Jan 2004 Darwin Core 2: Collector Number FAO/IPGRI MCPD: Collecting number EURISCO: Collecting number Should be added to the entry (for collectors) under Gathering/GatheringAgents/../Person, if such an entry exists. However, collector and number can also be given in a single field (e.g. FAO/IPGRI MCPD), sometimes with an abbreviation for the collector. In that case, the entire string may be entered here A container for quantitative and categorical measurements (including observations) refering to the unit, e.g. counts, size measurements, colours, etc. Quantitative or categorical measurement refering to the unit. NBN: Taxon_Data. Darwin Core 2: Individual Count. General purpose measurement element that can be used to store any kind of count or measurement related to a Unit length of bill number of eggs weight pH specific gravity number of individuals in a batch, such as males, females, juveniles, total Maps to Darwin Core 2: Sex. Refers to the entire unit, which may be mixed. Note that counts can be provided in the Unit's MeasurementsOrFacts section. Sex Berendsohn 14 Jan 2004 Darwin Core 2: Sex. This is another element in need of a standard term list enforced on the database level. Examples of content found by Charles Hussey in NHM databases include the following entries: [Female; Female (5); Female(2); Male; Male (2) Female (1); 1 brooding female; 1 Male; 1 Male and 1 Female; 15 Females and 3 Males; 16 Females and 23 Males; 2 female + 1 male; 2 Females; 2 females, 1 male; 3 females, 3 males; 5 Females; 7 Females and 5 Males; Both sexes; Ephippial female; Ephypial female;]/> Age of the organism at the time of collection or observation. Note that counts for different age classes can be provied in the Unit's MeasurementsOrFacts section. Container for medata on sequences derived from this unit. Miscellaneous notes referring to the unit that do not fit elsewhere. LNHM: free text description of a specimen or similar 'Unit'. Darwin Core 2: Notes. Free text description of the unit. Any notes that do not fit elsewhere. Gives the web address of the page where more information on this particular record (not on the whole dataset) can be found. [OBIS] The extension is temporary and serves only to accommodate urgent inter-version additions to the unit-object schema [in future to the the various schemas/objects used in ABCD]. For example, if a specific community (e.g. culture collections) discover that there are elements missing in the current version of ABCD (as they did for 1.2), they communicate that to the group responsible for schema development, where it will be discussed if these elements are already accommodated in the schema, if not, if they can and should be generalized and where they should end up in the schema. IF the culture collection community needs to move rapidly (e.g. due to project pressures), they can add these elements to the current version as an extension schema under a structure that follows SDD's CustomExtensions element (CustomExtensions-CustomExtension-Any ##other). In future modular versions of ABCD, such a structure should exist in the root of every object/schema. A first proposal for this type of data. Note that this is used in the context of a collection unit and thus automatically refers to that unit. E.g. GenBank, SwissProt, etc. Use "Internal" for unpublished sequence. E.g. GenBank accession number. A description of the method used to achive the sequence. Description of the actually sequenced material (DNA/RNA/Protein, Gene or part of gene, completeness, etc.), Reference where the sequence was published. The person and/or organisation responisible and/or effecting the sequencing. Length of the sequence in basepairs Types that may be used for different domains (descriptions, taxonomy, specimen collections, etc.): Many of the types or elements within the types are resulting from attemtps to standardize usage between ABCD and SDD and many originate from Gregor Hagedorn's work on the UBIF schema. However, note that this is work in progress, so there may be considerable differences between types with the same names in UBIF/SDD and ABCD. ============================================================================== Basic generic types normalized string required to contain at least 1 character (this removes the xml string anomaly, i. e. either element/attribute may be optional, but if they are required the content may not be an empty string) normalized string restricted to 1..50 character length to be used for abbreviations (the recommended length of abbreviations is usually much shorter, but 50 characters should be a normalized string restricted to 1..255 character length (i. e. required, may not be empty string) Complex types that add attributes language or preferred to the simple types String, String255, anyURI: String (i. e. xs:string with minimum length=1) extended with language attribute String255 (i.e. xs:string with length 1-255), extended with language attribute String (i. e. xs:string with minimum length=1) extended with preferred attribute String255 (i.e. xs:string with length 1-255), extended with preferred attribute String (i. e. xs:string with minimum length=1) extended with language and preferred attribute String255 (i.e. xs:string with length 1-255), extended with language and preferred attribute xs:anyURI extended with Preferred attribute Date and Time The date and time expressed in a way conforming to a subset of ISO 8601 ISO/ANSI Date and Time A representation of the date and time of (the beginning of) an event in ISO/ANSI standard structured format. BioCASE CODATA TDWG HISPID M. Doering, A. Guentsch and W. Berendsohn 2003 ISO Standard 8601:1988 HISPID ITF Any chronologically acceptable date and time in ISO/ANSI format 1966-12-05T23:55:46 1925-02-21 1925-02 1925 --12-05T23:55:46 ---05T23:55 1966-12-05T23:55 This field is a representation of the date and time in its structured form The values are in order Year-Month-Day, separated by hyphens, followed by the letter T and the time, in order Hour:Minutes:Seconds, separated by colons Partial dates in the form of Year-Month or Year only are acceptable The year is expressed as a 4-digit value, left zero padded if necessary The year can be omitted, the month is than preceeded by two hyphens The year and the month can be omitted, the day is than preceeded by three hyphens The month of the year is expressed in as 2-digit value, left zero padded if necessary, ranging between 01 and 12 The day of the month is expressed as a 2-digit value, left zero padded if necessary, ranging between 01 and 31. Parts can be omitted from the right, whereas a year is replaced by '--' and only a day would look like '---31'. The hour is expressed as a 2-digit value, left zero padded if necessary, ranging between 01 and 24. This field will nearly always be a representation derived from the date on the specimen. The DateText field is available for recording verbatim date information for generalised or ambiguous dates. The year must be represented as four digits to avoid ambiguity between centuries. Month and Day values are left zero padded to two digits to facilitate machine readability. In the rare instances of multiple exact dates or periods those can be recorded in this DateText field. In the rare instances of dates for periods before the year 0000, BC and similar dates can be recorded in this DateText field. Parts can be omitted from the right, whereas a year is replaced by '--' and only a day would look like '---31'. In the ISO standard element, time can only be specified when there is a full date. Temporal aspects of an event or activity. Date and time or period Elements covering the date, time and duration of an event or activity. BioCASE CODATA TDWG M.D� Berendsohn BioCASE Model: VDate. 1997 1997-07 1997-07-16 --07-16 ---16 1997-07-16T19:20+01:00 1997-07-16T19:20:30+01:00 997-07-16T19:20:30.45+01:00 Examples: Year: YYYY (eg 1997) Year and month: YYYY-MM (eg 1997-07) Complete date: YYYY-MM-DD (eg 1997-07-16) Month and day only: --MM-DD (eg --07-16) Day only: ---DD (eg ---16) Complete date plus hours and minutes: YYYY-MM-DDThh:mmTZD (eg 1997-07-16T19:20+01:00) Complete date plus hours, minutes and seconds: YYYY-MM-DDThh:mm:ssTZD (eg 1997-07-16T19:20:30+01:00) Complete date plus hours, minutes, seconds and a decimal fraction of a second YYYY-MM-DDThh:mm:ss.sTZD (eg 1997-07-16T19:20:30.45+01:00) where: YYYY = four-digit year MM = two-digit month (01=January, etc.) DD = two-digit day of month (01 through 31) hh = two digits of hour (00 through 23) (am/pm NOT allowed) mm = two digits of minute (00 through 59) ss = two digits of second (00 through 59) s = one or more digits representing a decimal fraction of a second TZD = time zone designator (Z or +hh:mm or -hh:mm) See http://www.bgbm.org/tdwg/codata/Schema/DateTime.htm for a discussion of the use of ISO 8601 in this type. Can be a range or qualified as a vague date (=HISPID4: cdat) for example as a means of adding greater precision to specific groups of observations within a range event (=cdat2 in part) Dates may be duplicated and expressed in various forms in each of the available fields to facilitate query. The date in text format Date text Date text A text version of the date at which an event or action took place, for use when the date is imprecise, ambiguous or not in a form that satisfies the standard structured date format. BioCASE CODATA TDWG HISPID Jim Croft ABIS ITF Alphabetic mixed case and integer; free text. 25 [?] 1925 3/9/45 [ambiguous day month] Spring 1912 Late 1800s End of 19th Century Mid 1978 Easter 1933 Post WW2 Before June 25, 2000 After June 25, 2000 This field should be used when it is not possible to create a structured standard date from the information provided, or when in is important to record the verbatim representation of the date. This field will probably not be used very frequently but may be useful when dates to be recorded are not completely legible. For example the day and month may be decipherable but not the year; the use of this field will allow recording of partially interpreted information. This field will also be used when the date, time or period of the event is vague or ambiguous and can not be expressed in the standard structured data format. This field can be used to record generalised date ranges and irresolvable ambiguity such as different day/month order conventions (e.g. US/Europe) This field may be repeated to allow multiple dates or periods. In the rare instances of dates for periods before the year 0000, BC and similar dates can be recorded in this field. If the project or application requires verbatim representation of dates, this field can be used for that purpose, even though the date might correspond to the standard structured data format. The time zone to which the time-of-day data refer The exact date (and time) or beginning of a period, expressed in a modified ISO/ANSI 8601 standard structured format ISO/ANSI date and time or beginning of period A representation of the date and time of (the beginning of) an event in ISO standard structured date format. BioCASE CODATA TDWG M.D� Berendsohn Julian day number in the year for the exact date or for the beginning day of a period Julian Day Number The Julian Day number or the sequential day within the year BioCASE CODATA TDWG Jim Croft, M.D� Berendsohn Darwin Core 2: Julian Day Maps to Darwin Core 2: Julian Day. The year is given in ISODateTimeBegin. The content range is 1-365 for normal years, 366 for leap years. Time of day in hours from midnight for an exact point in time or for the beginning of a time period Time of day The time of day expressed in decimal hours from midnight local time. BioCASE CODATA TDWG Jim Croft Darwin Core 2: Time of Day 13.5 04.25 This field may apply to times of collecting where this is considered important Maps to Darwin Core 2: Time of Day. Note that times are decimial hours: 13.5 represents 1:30 pm, not 1:05 pm, nor 1:50 pm Time can also be expressed in the ISODateTimeElement.(WGB) The end of a period expressed in a modified ISO/ANSI 8601 standard structured format ISO/ANSI date and time for the end of period A representation of the date and time of (the beginning of) an event in ISO standard structured date format. BioCASE CODATA TDWG M.D� Berendsohn The Julian day number of the last day in a period. Julian Day Number The Julian Day number or the sequential day within the year for the last day of a period. BioCASE CODATA TDWG (Jim Croft) M.D� Berendsohn The year is given in ISODateTimeEnd. The content range is 1-365 for normal years, 366 for leap years. Time of day in hours from midnight for the end of a time period Time period end time The time of day expressed in decimal hours from midnight local time for the end of a time period. BioCASE CODATA TDWG (Jim Croft) M.D� Berendsohn 13.5 04.25 Note that times are decimal hours: 13.5 represents 1:30 pm, not 1:05 pm, nor 1:50 pm Set to True if the event takes place for the period indicated, set to false if it occurs at some point of time during the period, not filled if unknown or no period specified. Intellectual Property Rights (IPR) Text, optional Details (both free-form text) and optional URI. A concise representation of a statement, recommended to be as short as possible, but actual length is unconstrained. Optional text of unconstrained length, elaborating details of the ShortText An optional resource on the net providing details on the statement (may be used as an alternative to the long text). A sequence of statements related to Intellectual Property Rights, credit and acknoledgement. Container element for one to several statements, normally representing different language representations of the same content. Used where the IPR declaration cannot be parsed into the specific items or for forms of IPR declaration not yet covered (e.g. database rights), Container element for one to several statements, normally representing different language representations of the same content. Copyright may include the information that the data has been released to the public domain. Container element for one to several statements, normally representing different language representations of the same content. To be used if data are placed under a public license (GPL, GFDL, OpenDocument). Placing data under a public license while maintaining copyright is recommended! Container element for one to several statements, normally representing different language representations of the same content. Defines conditions under which the data may be analised, distributed or changed. "Terms of use" includes concepts like "Usage conditions" and "Specific Restrictions". Container element for one to several statements, normally representing different language representations of the same content. Disclaimer statement, e. g. concerning responsibility for data quality or legal implications. Container element for one to several statements, normally representing different language representations of the same content. A free form text acknowledging support (e. g. grant money, help, permission to reuse published material, etc.) Container element for one to several statements, normally representing different language representations of the same content. Indicates how this dataset or record should be attributed if used [OBIF 1.0] Multimedia Elements to describe digital images, sound recordings, etc. BioCASE CODATA TDWG Identifier for the multimedia object. May be a filename. BioCASE CODATA TDWG Universal Resource Identifier of the underlying multimedia file, i.e. "naked" path to electronic source of multimedia object (e.g. web address). See also BioCASE CODATA TDWG Universal Resource Identifier of an electronic source of multimedia object including HTML, Javascript or similar means deliver rendered output. The context of the object in relation to the specimen or observation. E.g. image of entire specimen, sound recording the observation is based on, image of original valid publication, etc. BioCASE CODATA TDWG Code or descriptive term for file or object format e.g. jpg, pcx, tiff for digital images; 16mm, beta video, AVI, mpg for moving images; transparency, print for photographs etc. BioCASE CODATA TDWG Image size in pixels x pixels. BioCASE CODATA TDWG Resolution expressed in dots per inch. Size in Kb of the file referred to by URI or filename. Intellectual Property Rights relating specifically to the image. BioCASE CODATA TDWG Free text of formatted text (rtf) description of the feature - not controlled length e.g. often a memo field BioCASE CODATA TDWG Date the object was created. Identifier, e.g. name or other id, of (technical) personnel who has taken the image. Does not imply copyrights or other rights. Equipment used to create this multimedia object. ## Element under discussion ## See Bob Morris' comments under http://efgblade.cs.umb.edu/twiki/bin/view/BDEI/ColorManagement Picture width in pixel Picture height in pixel Various An abbreviated designation of an institution. Unique institute designation BioCASE CODATA TDWG Berendsohn 12/2003 A globally unique designation of a collection holding institution or the name of the holder of a private collection. A standard designator for the nature of the object of the record. Sex of the organism (Male, Female, Unknown, Not applicable (e.g. for a fungus in a herbarium), MiXed. Published reference. Reference Type BioCASE CODATA TDWG Neil Thomson Formal citation for a paper or electronic publication. Reference citation Formal citation for a paper or electronic publication. BioCASE CODATA TDWG Neil Thomson Need to decide on whether a particular standard for citations should be adopted - such as the Council of Biology Editors 6th edition with the NLM Internet extensions?? Specific page, figure or illustration number(s) within the reference. Reference detail Specific page, figure or illustration number(s) within the reference. BioCASE CODATA TDWG Neil Thomson Universal Resource Identifier - Path to electronic source of document. URL Universal Resource Identifier - Path to electronic source of document. BioCASE CODATA TDWG Neil Thomson Provides a minimalized local Agent definition. Person, person team, or role name (e. g., 'head of departement') (voice phone) Minimalised local Agent definition with preferred flag Contact Type and types used therein: Contact details. BioCASE CODATA TDWG Identifies an organisation and/or a person as contact and provides addresses, telephone numbers, e-mail addresses and URLs. If a PersonName is supplied, all contact details should relate to the person. If no PersonName is supplied, they should relate to the Organisation. Organisation to contact BioCASE CODATA TDWG Person to contact BioCASE CODATA TDWG Analogue to vCard:Role: Functional contact name, e.g. "Database administrator", "The Director", etc. Title for role of person or organisation. This element can be used to provide a title such as "Database Administrator" or "Curator" when no individual person is named. Contact addresses (one preferred, different languages possible) BioCASE CODATA TDWG Set of addresses for person or organisation. PreferredFlag attribute is used to indicate preferred postal address. Contact address as string. BioCASE CODATA TDWG Address of person or organisation. PreferredFlag attribute is used to indicate preferred postal address. Telephone and fax numbers BioCASE CODATA TDWG Set of telephone or fax numbers for person or organisation. Telephone or fax number BioCASE CODATA TDWG NBN : element Contact_Number. Numbers should be provided in the ITU International Format ("+CountryCode AreaCode Number"). PreferredFlag attribute indicates preferred number. +44 9876 543210 E-mail addresses BioCASE CODATA TDWG Set of e-mail addresses for person or organisation. E-mail address for contact Valid e-mail address. PreferredFlag attribute indicates preferred e-mail address. any.person@any.org URIs for person or organisation BioCASE CODATA TDWG Set of URLs of web sites for person or organisation. URI for person or organisation Publicly available URL for person or organisation. PreferredFlag attribute indicates main URL. URL of a logo image. Logo URL URL of a logo image of the item or holding organisation which may be to give a quick visual indication of source in result sets comprising data from several datasets. BioCASE CODATA TDWG Neil Thomson Full organization or corporate name in multiple languages (en: 'Botanical Garden of ...', de: 'Botanischer Garten von ...'). vCard:Org.OrgName). The Label mechanism also supports acronyms / abbreviations (no vCard equivalent!). If the contact contains no person definition: the unit within the organization the agent represents; else a list of the various organisational units to which a person may belong. (vCard:OrgUnit) (vCard:OrgUnit) Collection of language-specific label representations Language-specific label representation [ATTR: language] Language-specific simple label, using simple formatted text Label text in a specific language. Restricted to 50 characters maximum length, including blanks (recommended to be shorter!). Label abbreviations are especially important when displaying information in a tabular format. Name of an individual person BioCASE CODATA TDWG DisplayPersonName element should contain name as normally used. SortPersonName element should be in form most appropriate for alphabetic sorting. A suggestion from Hannu Saarenmaa, which could be incorporated once such directory servers come into existence: Person should have an element "PersonCode" that would support any person identification schemes and remote namespaces. Using such identifier, all the person data that is repeated could optionally be retrieved from a directory server somewhere. Keeping track of and certying observers is important if there is no specimen to go back to for verification. A suggestion from Hannu Saarenmaa, which could be incorporated once digital signatures become more commonplace: Person should have a public key. In case someone verifies an identification, there must be a possibility to leave a digital signature with the identification. Preferred form of personal name for display as a string. BioCASE CODATA TDWG Name of person as normally used. May include titles. Professor James Hundredwidth Aylstone T. McTrace The full name with the elements in preferred sorting sequence (vCard: Sort-String). BioCASE CODATA TDWG Name in form appropriate for sorting alphabetically. Hundredwidth, James McTrace, Aylstone T. Family name first followed by a comma then a space then given names or initials separated by a space. Family names, generational names, clan name, parents/grandparents personal names, etc. This (= last name in western cultures) may be compound ('Fischer von Waldheim', 'da Selva', 'Silvano Morales'). Depending on culture it is not necessarily the name of the parents nor common to the married couple and children, thus 'family name' should be avoided even though used in vCard. (vCard:N.Family) Prefix to inherited name that should be output before name, but is usually not included in sorting. Examples: 'von', 'Lord'. Compare Title for 'Prof', 'Dr.' (vCard:N.Prefix) Suffix to name that should be output after name, regardless whether it is in sorting sequence (Inherited, Given) or not. Examples: 'Jun.', 'III.'. (vCard:N.Suffix) The name given to a person as a personal name (= first or christian name in western cultures, including 'middle initials') may contain several words ('Ana Maria', 'Jerry B.'). Applicable only to persons. (vCard:N.Given + vCard:N.Middle) May differ from the first given name: second given name, nickname ('Bob' for 'Robert'), etc. (vCard:Nickname) Type of device reached by telephone number, e.g. voice, fax, voice/fax Telephone or Fax number BioCASE CODATA TDWG NBN : element Contact_Number. Added to replace fax and telephone elements with a repeatable and more flexible structure where the element attribute TelephoneType is enumerated to allow selection between "Phone", "Fax" and "Mobile". The PreferredFlag attribute can be used to identify the first choice when multiple numbers are supplied. The TelephoneConstraint element is available to allow additional comments on the use of the number. Full number in standard international format BioCASE CODATA TDWG NBN: Number. Numbers should be provided in the ITU Recommendation E.164 international format ("+CountryCode AreaCode Number") +44 9876 543210 Free text for constraints on use e.g. "weekdays only" or "home number" BioCASE CODATA TDWG NBN: Constraints. Free text Weekdays only Home number The role of an agent or contact. Role BioCASE CODATA TDWG D.Hobern 11/2002. W.Berendsohn 12/2003. Elements specific to units from botanical gardens Minimum numbers of individuals the garden is holding under the UnitID. Accession specimen numbers BioCASE CODATA TDWG Berendsohn HISPID 3: n/a. ITF 2: AccessionSpecimenNumbers (=accspe). 1 Field definition taken from ITF 2. Accession status must not be D (dead) Current status (current or not current) of the accession in the garden. Accession status BioCASE CODATA TDWG Berendsohn HISPID 3: n/a. ITF 2: AccessionStatus (=accsta). The status may be C (current accession in the living collection), D (non-current due to death), T (non current due to transfer to another record system, normally another garden), S (stored in a dormant state), O (other accession status - different from those above). C Field definition taken from ITF 2. One or more of the following characters: C,D,T,S,O Current location of the living plant in the botanical garden. Type of material the current living accession is composed of. Accession material type BioCASE CODATA TDWG Berendsohn HISPID 3: n/a. ITF 2: AccessionStatus (=accsta). The status may be C (current accession in the living collection), D (non-current due to death), T (non current due to transfer to another record system, normally another garden), S (stored in a dormant state), O (other accession status - different from those above). C Field definition taken from ITF 2. One or more of the following characters: C,D,T,S,O A flag indicating that the accession is grown outdoors in the botanical garden. Hardiness BioCASE CODATA TDWG Berendsohn HISPID 3: n/a. ITF 2: -. A code to indicate the provenance of the accession [ITF-2]. Provenance category BioCASE CODATA TDWG Berendsohn HISPID 3:- ITF 2: Provenance Type Flag (=prot). W (Accession of wild source), Z (Propagule/s from a wild source plant in cultivation, G (Accession not of wild source), U (Insufficient data to determine which category applies). Z Field definition taken from ITF 2, see there for further description. See ITF. A code to indicate the nature of the production of the plant material being accessioned, for use in association with the element ProvenanceCategory [ITF-2] Propagation history code BioCASE CODATA TDWG Berendsohn HISPID 3:- ITF 2: Propagation History Flag (=prohis). See ITF 2. Field definition taken from ITF 2. One of the following values: I, S, SA, SB, SC, V, VA, VB, U The purpose of this element is to trace the lineage of an accession to either one or two immediate parent unit ID's. Accession lineage BioCASE CODATA TDWG Berendsohn HISPID 3:- ITF 2: Accession Lineage (=acclin). UnitIDs preceded by garden code (Heywood and Heywood). K19650056 Field definition taken from ITF 2, further specification see there. A code to indicate the type of the immediate donor from which the accession was obtained. This may not be necessarily the original collector of wild material. [ITF-2] Donor category BioCASE CODATA TDWG Berendsohn HISPID 3: - ITF 2:Donor Type Flag (=dont). Field definition taken from ITF 2. Note that the ITF-Donor field is found under AccessionSource and the Donor's Accession Number in the PreviousUnitID of first record in the UnitHistory. One or more of the following characters: E, G, B, R, S, U, H, M, N, I, O, U Allows for cultivation information to be passed as free text in order to help the receiving garden care for the transferred accession [ITF-2] or to record the garden's experience made with this accession. Allows for information about any propagation requirements to be passed as free text in order to help the receiving garden propagate the transferred accession [ITF-2] or to record the garden's experience made with this accession. A code to indicate the means of perennation, providing a means of noting living plant accessions that require regular curatorial monitoring [ITF-2]. A code to indicate the breeding system of the accession [ITF-2]. Unique number given to plant materials accessioned in conformance with the rules of the International Plant Exchange Network (see http://www.bgci.org/abs/ipen_numbers.html). Elements only used for units in culture collections "Bacteria" or "Archaea" Variety designation, epithet, authors and reference. This field excludes the pathovar name and the serovar name, which are both infrasubspecific names but are to be entered under Identification/... ../FullScientificName Container element for names under which the culture is known Reference or trade name for a microbial culture BioCASE CODATA TDWG Name and author of serovar Type and parent of mutant if strain is a mutant strain Names of chromosomal markers of the strain. Especially recommended for strains of species for which many genetically modified strains exist An alternative full text field for culture medium, atmospheric and light conditions, temperature conditions and additional remarks on the cultivation. BioCASE CODATA TDWG The growth medium for a microbial or similar culture e.g. agar BioCASE CODATA TDWG BioCASE CODATA TDWG Preferably a number - attribute gives temperature scale used BioCASE CODATA TDWG References for the culture conditions and method or for a description of the strain Attribute for RefType BioCASE CODATA TDWG Form in which the strain will be sent to the customer BioCASE CODATA TDWG BioCASE CODATA TDWG Elements only used for herbarium units Information relating this specimen to an Exsiccatum A list of collection abbreviations of the herbaria duplicates were distributed to The unique institutional loan number applied with the loan sequence number to uniquely identify a specimen on loan [HISPID3]. The sequence of a specimen within a given loan, assigned with the Loan Identification to uniquely identify a specimen on loan [HISPID3] Institution to which the loan is being sent [HISPID3] Name of botanist for whom the loan is destined [HISPID3] The means by which the loan is being despatched from the home institution [HISPID3] The date the loan is prepared and/or sent [HISPID3] Elements only used for mycological units Name of algal or cyanobacterial component of lichen BioCASE CODATA TDWG BioCASE CODATA TDWG Spore states present in the sample. Spore states present in the sample. BioCASE CODATA TDWG Paul Kirk 2002. Extension for elements only used in plant genetic resource collections. Currently, all elements represent EURISCO descriptors. BioCASE CODATA TDWG FAO/IPGRI: NICODE EURISCO: NICODE FAO Institute Code of the institute that has bred the material. Breeding Institution Code BioCASE CODATA TDWG Berendsohn 16 Jan 2004 FAO/IPGRI: EURISCO: BioCASE CODATA TDWG FAO/IPGRI: EURISCO: BioCASE CODATA TDWG FAO/IPGRI: EURISCO: BioCASE CODATA TDWG FAO/IPGRI: EURISCO: BioCASE CODATA TDWG FAO/IPGRI: EURISCO: BioCASE CODATA TDWG FAO/IPGRI: EURISCO: BioCASE CODATA TDWG FAO/IPGRI: EURISCO: BioCASE CODATA TDWG FAO/IPGRI: EURISCO: BioCASE CODATA TDWG FAO/IPGRI: EURISCO: BioCASE CODATA TDWG FAO/IPGRI: EURISCO: FAO Institute Code; the codes consist of the 3-letter ISO 3166 country code of the country where the institute is located plus a three-digit number. Code for the (propagation-)provenance of the unit. Code for the (location-) provenance of the unit. Code for the type of storage of the unit in the collection. Elements only used for palaeontological units Description of the fossil preservation of the specimen. BioCASE CODATA TDWG BioCASE CODATA TDWG articulated, disarticulated, complete, incomplete Original, mould, cast etc BioCASE CODATA TDWG internal mould, internal cast, external mould, external cast, original The sediment or mineral matrix enclosing the fossil BioCASE CODATA TDWG Form of mineralisation BioCASE CODATA TDWG silicified, phosphatised, pyritised Life position, allochthonous death assemblage, post mortem history details etc. BioCASE CODATA TDWG Known or assumed time range of a fossil BioCASE CODATA TDWG Hildoceras bifrons collected from the "condensed" Junction Bed would be given a time range of Toarcian, Bifrons Zone Elements expressing stratigraphy at the gathering site. BioCASE CODATA TDWG Chronostratigraphic dating term e.g. Jurassic Period BioCASE CODATA TDWG biostratigraphic zonation term e.g. Psiloceras planorbis zone BioCASE CODATA TDWG lithostratigraphic term describing geology e.g. Mercia Mudstone Group BioCASE CODATA TDWG Free text field for informal recording of field contents BioCASE CODATA TDWG Elements only used for zoological units Container element for the phase or stage of the individual organism or the organisms present in the unit. Note that counts can be provided in the Unit's MeasurementsOrFacts section. Combined element for phase (e.g. polyp and meduse of the Cnidaria) or stage (juvenile, nauplius, copepodite) of the organism(s) in the unit. BioCASE CODATA TDWG Details of the country Country Elements covering the representation of the country and its name. BioCASE CODATA TDWG Jim Croft 2002, W. Berendsohn 06/2003 HISPID4 Maps to Darwin Core 2: Country through either ISO2Letter (future) or CountryName (current). Historical country names and water bodies outside the coastal zone can be entered under named area. CountryNameDerived is provided for a country name that has been derived, for example from a system supplied dictionary, by library consultation or other independent research. At least one of CountryName or ISO2 or ISO3 should be present but more are allowed. This should be the political country having jurisdiction over the collection site. Country names and ISO codes can theoretically be part of controlled enumerations but if included within the schema would blow it out to an unacceptable level; is it possible to refer to these lists externally with physically invoking them? [JRC] Name of country or major region for specimen or observation Country The name of the country or major region where the specimen was collected, or the observation made, entered in full. BioCASE CODATA TDWG HISPID Jim Croft 2002 ABIS ITF TLR WGSUB ISO Brummitt (1992) Australia Commonwealth of Australia Iceland Republic of Iceland Samoa Independent State of Samoa If the name of the country where the plant was collected is unknown, then this field should contain the value 'UNKNOWN'. In this case, the ISO Code for Country of Origin field must have the entry 'XX' or 'XY'. All remaining 'location group' fields should be left unfilled. It is recommended that the spelling of the country should be that recognised by the International Standards Organisation (ISO). It is recommended that new country names be enclosed in square brackets, after the old country name, where country names or boundaries have changed. The 2 letter ISO codes in ISO Code for Country of Origin field assist updating and cross referencing country names where boundaries change. Separate fields for state/province and country are needed to adequately handle the situation with international collections. The use of this element is slightly ambiguous in that local practice might require either verbatim quote from specimen labels, or standardisation by controlled vocabulary or lookup lists This element is also covered by various geographic standards and may be better covered by reference to these. [JRC] Derived name of country or major region for specimen or observation Country Name Derived DerivedCountry The derived name of the country or major region where the specimen was collected, or the observation made, entered in full, interpreted in the light of contemporary geographical knowledge. BioCASE CODATA TDWG HISPID Jim Croft 2002 ABIS ITF TLR WGSUB ISO Brummitt (1992) Sri Lanka Taiwan Vanuatu Papua New Guinea Kiribati East Timor If the name of the country where the plant was collected is unknown, then this field should contain the value 'UNKNOWN'. In this case, the ISO Code for Country of Origin field must have the entry 'XX', 'XY', 'XXX', or 'XXY'. All remaining 'location group' fields should be left unfilled. It is recommended that the spelling of the country should be that recognised by the International Standards Organisation (ISO). The derived country names offers the opportunity to document the name under which a country is currently known, interpreted by an old or superceded names on the specimen label, such as Vanuatu for the New Hebrides, Sri Lanka for Ceylon, etc. Separate fields for state/province and country are needed to adequately handle the situation with international collections. The use of this element is slightly ambiguous in that local practice might require either verbatim quote from specimen labels, or standardisation by controlled vocabulary or lookup lists This element is also covered by various geographic standards and may be better covered by reference to these. [JRC] 2- or 3-letter (ISO3166-1) or 4-letter (ISO3166-3) code for representation of name of country or origin. 2-letter ISO country code ISO Country The 2-, 3-, or 4-letter code for the representation of the name of the country of origin of the collection or observation using the codes assigned by the International Standards Organisation (ISO). BioCASE CODATA TDWG HISPID Jim Croft 2002, Walter Berendsohn 2004 ABIS ITF ISO Brummitt (1992) AU ES FR PG US AUS ESP FRA USA DDDE This field should contain a valid entry as defined by the International Standards Organisation (ISO Standard 3166-1) Two other entries are permitted in addition to those defined by ISO. If the name of the country where the plant was collected is unknown, then this field should contain the value 'XX'; if a country name is not applicable then the field should contain the value 'XY'. In these cases, the Country field must have the entry 'UNKNOWN'. All remaining 'location group' fields should be left unfilled. Two other entries are permitted in addition to those defined by ISO. If the name of the country where the plant was collected is unknown, then this field should contain the value 'XXX'; if a country name is not applicable then the field should contain the value 'XXY'. In these cases, the Country field must have the entry 'UNKNOWN'. All remaining 'location group' fields should be left unfilled. The 'XXX' code should be used when no country of origin information is provided. The 'XXY' code sould be used for non-specific collecting localities, e.g. Africa, SouthEast Asia The ISO codes in ISO Code for Country of Origin field assist updating and cross referencing countries where boundaries change. The 'XX' code should be used when no country of origin information is provided. The 'XY' code should be used for non-specific collecting localities, e.g. Africa, SouthEast Asia See comments under Country. This element is also covered by various geographic standards and may be better covered by reference to these [JRC] Orientation, outlook or aspect of slope Aspect The orientation, outlook or aspect or direction of slope. BioCASE HISPID CODATA TDWG Jim Croft 10/2002 HISPID This information is of particular interest in relation to exposure and incident sunlight. The values in these fields are nearly always directional and restricted to mountainous or sloping ground. The value 'Open' can be used to describe flat plains or exposed ridge crests; 'Closed' can be used for valleys or ravines. The direction, orientation or aspect of slope expressed in compass points Ordination Orientation or bearing as an abbreviation of cardinal points BioCASE CODATA TDWG Jim Croft 10/2002, W. Berendsohn 05/2003 Orientation or bearing from North Compass Degrees Orientation or bearing from North, expressed in compass degrees BioCASE CODATA TDWG Jim Croft 10/2002 May be used for recording aspect of a site or as part of the dip/strike measurement in geologic records. Accuracy of aspect reading or estimation Bearing Accuracy Accuracy of the bearing measurement of Aspect. BioCASE CODATA TDWG Jim Croft 10/2002 I have no idea how this element will be applied or who will use it [JRC] Text expression of slope or aspect Aspect Text The direction of aspect or slope expressed as text. BioCASE CODATA TDWG Jim Croft 10/2002 South West facing slope Westward cliff This field will as far as possible be a verbatim quote from the specimen label. General purpose measurement and fact (descriptor) recording. BioCASE CODATA TDWG Charles Copp Oct 2002 General purpose measurement recording. Attribution of the measurement to a Person Date and/or Time the measurement was taken Duration of measurement in time. BioCASE CODATA TDWG Charles Copp Oct 2002 Duration of measurement in time. Method used to make measurement. BioCASE CODATA TDWG Charles Copp Oct 2002 Method used to make measurement. Describes type of measurement or fact, such as width, abundance, circumference, temperature etc. or color etc. BioCASE CODATA TDWG Charles Copp Oct 2002 Describes type of measure width abundance circumference Depending on the use of the type, this can further specify the actual part measured. For example, a measurement of temperature may be a surface, air or sub-surface measurement. BioCASE CODATA TDWG Charles Copp Oct 2002 . Lower or only value or fact text. BioCASE CODATA TDWG Charles Copp Oct 2002 Lower or only value. Attribute for ValueDataType.string, integer, decimal, % etc Upper value where there is a range. BioCASE CODATA TDWG Charles Copp Oct 2002 Upper value where there is a range. Attribute for Unit of Measurement. Unit of measurement. BioCASE CODATA TDWG Charles Copp Oct 2002 Named scale. centigrade Beaufort Statement of accuracy of measurement. BioCASE CODATA TDWG Charles Copp Oct 2002 Statement of accuracy of measurement. Reference (publication) where this measurement was taken from Flag indicating if the value represents the numerical result of a quantitative measurement (TRUE) or a descriptor with textual or categorical result (FALSE). Free text alternative to atomised version. BioCASE CODATA TDWG Charles Copp Oct 2002 Free text alternative to atomised version. Descriptive term. May be taken from a controlled vocabulary maintained by a third party. BioCASE CODATA TDWG Descriptive term. May be taken from a controlled vocabulary maintained by a third party. Subject area of the term list. BioCASE CODATA TDWG Subject area of the term list. Descriptive term. BioCASE CODATA TDWG Descriptive term. If the term has been drawn from a named term list or thesaurus, its name is recorded here. BioCASE CODATA TDWG If the term has been drawn from a named term list or thesaurus, its name is recorded here. Version or date of the term list or thesaurus from which the term is drawn. BioCASE CODATA TDWG Version or date of the term list or thesaurus from which the term is drawn. Free text comment. BioCASE CODATA TDWG Free text comment. LookupType extended with Language attribute Metadata referring to the principal source of the entire data collection (thus the metadata scope may be wider than the objects actually contained in the data set). If a history of the data collection (revised or expanded in various projects or at different institutions) exist, this must be reflected in the IPR statements and possibly in the list of Owners. Dublin Core conformant elements describing the content of the data source queried, representation in different languages possible The description in a specified language. Only one representation should be delivered for each language. [ATTR: language] The URI of an icon/logo symbolizing the project. Keyword lists of geographical, taxonomic, etc. scopes. In the case of projects in progress, 'scope' may define the planned or intended, rather than the achieved scope (or coverage). If scope is given, the content available should be entirely within scope, because this item is for resource discovery purposes. Compare also Coverage in DC.Description (which is language-specific). (Items from Scope may be added to DC.Coverage) A collection of terms describing the geoecological scope of the source queried by means of area names (e.g. 'Worldl', 'Germany', 'Atlantic Ocean', 'Andes', 'Mountains'. A list of recommended terms should be developed. A collection of taxon names of higher rank describing the taxonomic scope of the source queried. A list of recommended terms should be developed. Number and date of current version (particularly for citing purposes) The major version number ('1' in 1.2) as defined by the content creators. An optional minor version number ('2' in 1.2) Unconstrained text specifying status + optional number, e. g., 'beta', 'alpha', 'rc/release candidate', 'internal'. If missing, release status is assumed. Source for Dublin-Core standard element Date.Issued: Citable 'publication date' of the current version (comp. RevisionData/DateCreated and DateModified for version- independent dates). This date should be missing if the current version is not yet published! Creators, Revision status, and dates of the entire data collection from which the current dataset is derived. Entities having legal possession of the data collection content. Here defined for the entire data collection, not for individual units. If an owner statement is present on the unit level, it should override this dataset-level statement. Entitiy having legal possession of the data collection content. Copyright, terms of use, license and other IPR-related statements like disclaimer or acknowledgement. Giving a copyright statement and a (if possible public) licence is highly recommended! (=DC.Rights) Language-specific content metadata (title, description, etc.) with *required* Language attribute added. Source for Dublin-Core standard element "Title": A short, concise title. General Note on DublinCore translation: In addition to those that can bee transformed from UBIF metadata, an additional DC.Type='dataset' should be added. Source for Dublin-Core standard element "Description": Free-form text containing a longer description of the project. Source for Dublin-Core standard element "Coverage": Free-form text describing geographic, taxonomic, or other coverage aspects of terminology or descriptions available in the current project. URL pointing to an online source related to the current project, which may or may not serve an updated version of the description data. RevisionData (creators, dates, revision) for the entire project/data set or individual objects. Source for Dublin-Core standard element "Creators", i.e. Author or editor. Source for Dublin-Core standard element"Contributors": General contributors, or translators. Source for Dublin-Core standard element "Date.Created": Date/time when the intellectual content (project, term, description, etc.) was created. Applications may initially set this to the system date for new data objects, but authors must be able to change it to an earlier date if necessary. If for legacy data this is imprecisely known, it may be missing here. Earlier versions in other data formats should then be mentioned in the copyright or acknowl. statements. Source for Dublin-Core standard element Date.Modified: Date/time when the last modification of the object was made. If in online data sources the provider can not assess this, the current date/time may be substituted. For legacy data this may be set to the file date of imported data, or estimated. Scientific or informal name as a result of an identification. Full name BioCASE CODATA TDWG Wrapper element for multiple designations of higher taxa. These are higher-level classifications of the name identified, NOT a higher taxon as the sole identification. Higher taxa BioCASE CODATA TDWG Berendsohn 29 Feb 2004 The scientific name of a taxon with a rank higher than Genus which is commonly used to classify the group the unit belongs to. BioCASE CODATA TDWG Yde de Jong HISPID3: covers "Suprafamilial Group Name" (supfam), Family Name (fam), and Suprageneric Group Name (supgen). Name of the taxon identified, formed according to the different Codes of Nomenclature which apply to scientific names - with additional elements for suffixes or other expressions commonly used in taxonomic identifications. Scientific name BioCASE CODATA TDWG Berendsohn 29 Feb 2004 The outcome of an identification event that does not adhere to the rule of a Code of Nomenclature. BioCASE CODATA TDWG Any free text comments related to the name NameComments BioCASE CODATA TDWG Berendsohn 2002 HISPID4: namcom. The Code of Nomenclature that applies to the scientific name. An atomised name under the International Code of Nomenclature of Bacteria Genus name. Genus BioCASE CODATA TDWG Berendsohn Darwin Core 2: Genus. A generic name as a bacterial scientific name or as part of it. Acetobacter First letter capitalised No spaces included. Generic names are essentially the same under the different codes; however, to avoid having to place the essential parts of a name on different levels of the hierarchy, all name elements recognized under a specific code are listed in the respective section. Subgenus name. Subgenus BioCASE CODATA TDWG Berendsohn Darwin Core 2: Genus. A subgenus name as (part of) a bacterial scientific name. Gluconoacetobacter First letter capitalised No spaces included. Author team and year of the subgenus name. Author team and year of subgenus. BioCASE CODATA TDWG Berendsohn Author(s) and year of the subgenus name. Yamada and Kondo 1985 Species epithet Species epithet BioCASE CODATA TDWG Berendsohn Darwin Core 2: Species. The first epithet occurring in a bacterial name (after genus and, optionally, subgenus names) liquefaciens Maps to Darwin Core 2: Subspecies Subspecies epithet BioCASE CODATA TDWG Berendsohn Darwin Core 2: Subspecies. The second epithet of a bacterial name of subspecies rank (after Genus, optional subgenus, and species epithet). aceti Author team and Year of the basionym of a species or subspecies combination. Author team and year BioCASE CODATA TDWG Berendsohn HISPID4: has Basionym (basnam) as an element but not the author team. Author(s) of the original name for a taxon which has subsequently been revised but retains the same stem or epithet. Asai The author(s) who published the full name as it stands and its year. Author team and year BioCASE CODATA TDWG Berendsohn Author(s) for the taxonomic name combination (i.e. the author team of the new combination where there is a basionym, and the name author team where there is none). Yamada and Kondo Ames and Correll Approbation of name according to approved list, validation list,or validly published, paper in IJSB after 1980. An atomised scientific name under the International Code of Botanical Nomenclature or the International Code of Nomenclature for Cultivated Plants Genus or higher taxon name. Genus BioCASE CODATA TDWG Berendsohn HISPID: Genus Name (gen) as to content, not all rules. Darwin Core 2: Genus. A generic name as a botancal scientific name or as part of it. A generic name under one of the established nomenclatural codes, or a manuscript name, or an intergeneric hybrid name under the ICBN, without the leading multiplication sign, or the name of an intergeneric graft hybrid or graft chimaera, published under the Cultivated Code. Abies Halimiocistus Crataegomespilus First letter capitalised No spaces included. Generic names are essentially the same under the different codes; however, to avoid having to place the essential parts of a name on different levels of the hierarchy, all name elements recognized under a specific code are listed in the respective section. The first epithet in a botanical name combination (species epithet or the epithet of the subdivision of a genus. First epithet BioCASE CODATA TDWG Berendsohn HISPID 3: "Subgeneric Group Name" (subgen) but without the preceding rank abbreviation (entered under Rank). HISPID 3: "Species Epithet" (sp). Darwin Core 2: Species (included). The first epithet in a botanical name combination, i.e. the epithet of a genus subdivision or a species epithet. alba No uppercase No space The final epithet of a botanical name of infraspecific rank. Second epithet BioCASE CODATA TDWG HISPID: "Infraspecific Epithet" (isp) without the hybrid parts. Darwin Core 2: Subspecies (included). The infraspecific epithet, i.e. the epithet following the indication of the infraspecific rank in the name string (trinomial). Note that quadrinomials etc. are not supported here as names; if deemed necessary, they can be entered in the FullScientificNameString, this element should than contain the last infraspecific epitthet. No uppercase No space The rank of the name where needed to form it. BioCASE CODATA TDWG Berendsohn HISPID: covers "Infraspecific Rank Flag" (isprk) as well as the rank ("group") of a "subgeneric group name" given in that field. The rank of the name where needed to form it (i.e. in infraspecies and in names of a rank between genus and species) subgen. subsp. Flag indicating that this is a named hybrid or a graft chimaera. BioCASE CODATA TDWG Berendsohn HISPID: Hybrid Flag (hyb) . Flag indicating that this is a named hybrid or a graft chimaera. Attribute Rank defines if this applies to the generic, species, or infraspecific level. Author team of the basionym of a combination. BioCASE CODATA TDWG Berendsohn HISPID4: has Basionym (basnam) as an element but not the author team. Author(s) of the original name for a taxon which has subsequently been revised but retains the same stem or epithet. May be preceded by a sanctioning author. If possible, preceding "ex" authors should be avoided. L. Ames and Correll The author(s) who published the full name as it stands. Author team BioCASE CODATA TDWG Berendsohn Author(s) for the taxonomic name combination (i.e. the author team of the new combination where there is a basionym, and the name author team where there is none). May be preceded by a sanctioning author. If possible, preceding "ex" authors should be avoided. DC. Ames and Correll Cultivar group name Cultivar group name BioCASE CODATA TDWG Berendsohn HISPID4: culgnam ITF Trehane(1995) The name of a cultivar group as specified in the ICNCP. Granny Smith Group Cultivar name according to the ICNCP. BioCASE CODATA TDWG Berendsohn HISPID4: culnam ITF Trehane(1995) The name of a cultivar as specified in the ICNCP. Firmgold Granny Smith Sturmer Pippin For output, cultivar names must be enclosed in single quotes. Container for trade names Trade name used for a specific cultivar Trade name BioCASE CODATA TDWG Berendsohn HISPID4: tranam ITF Trehane(1995) A trade name of a cultivar as specified in the ICNCP. An atomised scientific name under the International Code of Virus Classification and Nomenclature Genus or higher taxon name formed according to the code and representing the result of the identification. E.g. Comovirus. Genus BioCASE CODATA TDWG Berendsohn Darwin Core 2: Genus. A generic name as a scientific name of a virus or as part of it. Cambarus First letter capitalised No spaces included. Generic names are essentially the same under the different codes; however, to avoid having to place the essential parts of a name on different levels of the hierarchy, all name elements recognized under a specific code are listed in the respective section. The formal name of a viral species. Examples: vaccinia virus; human herpes virus 2 (herpes simplex virus 2); poliovirus 1; Saccharomyces cerevisiae virus L-A; enterobacteria phage PRD1 [Source: ICTV]. BioCASE CODATA TDWG The accepted acronym for the Virus, e.g. PCV for Peanut Clump Virus. An atomised scientific name under the International Code of Zoological Nomenclature Genus or higher taxon name. Genus BioCASE CODATA TDWG Berendsohn Darwin Core 2: Genus. A generic name as a zoological scientific name or as part of it. Cambarus First letter capitalised No spaces included. Generic names are essentially the same under the different codes; however, to avoid having to place the essential parts of a name on different levels of the hierarchy, all name elements recognized under a specific code are listed in the respective section. Subgenus name. Subgenus BioCASE CODATA TDWG Berendsohn Darwin Core 2: Genus. A subgenus name as a zoological scientific name or as part of it. Jugicambarus First letter capitalised No spaces included. Species epithet Species epithet BioCASE CODATA TDWG Berendsohn Darwin Core 2: Species. The first epithet occurring in a zoological name (after genus and, optionally, subgenus names) monongalensis Maps to Darwin Core 2: Subspecies Subspecies epithet BioCASE CODATA TDWG Berendsohn Darwin Core 2: Subspecies. The second epithet of a zoological name of subspecies rank (after genus, optional subgenus, and species epithet). monongalensis The first person(s) who validly published a species-group name and the year of publication. Original authors and year of publication. BioCASE CODATA TDWG Berendsohn The first person(s) who validly published a species-group name and the year of publication. L. The parenthetical citation of the original author when a species-group was transferred to another genus and the year of the original publication. BioCASE CODATA TDWG Berendsohn Author(s) of the original name for a taxon which has subsequently been revised but retains the same stem or epithet and the year of the original publication. L. Set in parenthesis upon output The citation of the authors responsible for the new combination and the year of its publication. BioCASE CODATA TDWG Berendsohn The citation of the authors responsible for the new combination when a species-group is transferred to another genus and the year of publication of the transfer. L. Purely optional under the zoological code. Name of the breed of an animal A name element dependent on a genus or a species name under the bacteriological, botanical, and zoological code. Epithet BioCASE CODATA TDWG S.Blum 2003. W. Berendsohn 12/2003. alba Add existing standards [WGB]. A generic or higher taxon name (monomial) under the bacteriological, botanical, viral, and zoological code. Genus or monomial BioCASE CODATA TDWG S.Blum 12/2002. W.Berendsohn 12/2003. First character must be upper case [A-Z] Second and following characters must be lower case [a-z] May not contain any other characters except dash. The rules above should apply to generic names under all codes; if an exception is discovered, the change in constraints should be implemented as an extension [SB] A multiplication or plus sign designating a hybrid or draft chimaera in botany. Hybrid or draft chimaera indicator BioCASE CODATA TDWG .Berendsohn 12/2003. Only used for botanical names Can only be multiplication sign, plus sign, x or X The abbreviation of a taxonomic rank as used in (botanical) name strings. Rank abbreviation BioCASE CODATA TDWG W.Berendsohn 12/2003 This is the abbreviation for a rank that is used in a (botanical) infraspecific name or the subdividion of a genus, as it appears in the name. A taxonomic rank designation above the rank of genus. BioCASE CODATA TDWG D.Hobern 10/2003. W.Berendsohn 12/2003 The the fully spelled out rank value (in latin but for the "unranked" term and the "group" levels) that can be used as metadata for any name for a taxon of rank above the genus-level. Subphylum This is not the abbreviation for a rank that is used in a botanical infraspecific name, as it appears in the name [WGB]. Should this be an enumerated type, or will we have to split RankType into ICxN-specific, or even discipline-specific versions? For example, the rank "Tribe" has different positions in Entomology and Ichthyology [DH]. The controlled vocabulary must contain terms with spaces [WGB]. Name of the taxon identified, formed according to the different Codes of Nomenclature which apply to scientific names. Concatenated scientific name, preferrably formed in accordance with a Code of Nomenclature, i. e. a monomial, bionomial, or trinomial plus author(s) or author team(s) and - where relevant - year, or the name of a cultivar or cultivar group, as fully as possible. Full scientific name BioCASE CODATA TDWG Darwin Core 2: Scientific Name. Acipenser gueldenstadti Linnaeus 1758 Atomised data items of the taxon identified, with subtypes according to the different Codes of Nomenclature which apply to scientific names. Higher taxa BioCASE CODATA TDWG Berendsohn 02 Mar 2003 Mandatory (at least one) for unit identifications, but optional in other contexts (e.g. synecology). Atomised name with elements according to the International Code of Nomenclature of Prokaryotes Atomised name with elements according to the International Code of Botanical Nomenclature Atomised name with elements according to the International Code of Zoological Nomenclature Atomised name with elements according to the International Committee on Taxonomy of Viruses Name of the taxon identified, formed according to the different Codes of Nomenclature which apply to scientific names - with additional elements for suffixes or other expressions commonly used in taxonomic identifications. A term to qualify the identification of the unit when doubts have arisen as to its identity (e.g. "cf." or "aff."). If it applies to an atomised name, the attribute insertionpoint defines the name element in front of which the qualifier should be inserted (1 = before entire name, 2= before first epithet, 3 = before second epithet.) BioCASE CODATA TDWG A free-text suffix added to the taxon identified (e.g. "sensu lato"). BioCASE CODATA TDWG sensu lato, sensu stricto Taxon name used to further classify the identification result. An enumeration of the Codes of Nomenclature