ABCD v.1 root element: container for one or more DataSets. Datasets BioCASE CODATA TDWG Berendsohn Mar 3 2003 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 BioCASE CODATA TDWG NBN: Survey. A container element for one to many unit data records and their shared metadata elements. The metadata relates to the source, provision, the ownership and rights etc. pertaining to the entire dataset. Attribute: xmlns, indicating the schema version used. Properties of the original data source, also providing a unique identifier for the dataset Original source BioCASE CODATA TDWG Properties of the orignal database or other datasource from which the ABCD-document is derived Notes: Many elements of this structure are directly taken from the DTD for the Integrated Taxonomic Information System, Canadian node (ITIS*ca) at: http://sis.agr.gc.ca/itis/ which was provided by Derek Munro. Unique identifier of the institution holding the original datasource (first part of dataset identifier) Source institution code BioCASE CODATA TDWG 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. The units within the datasource are not necessarily all owned or administred by this institution Name or code of the data source (unique within the institution, second part of the dataset identifier) Source name BioCASE CODATA TDWG ITIS*ca draft metadata May be the name of a collection if all records are for a stem from a single collection. Together with the element DBInstitution, DBName provides a unique identifier for the dataset's original source Mandatory second partial identifier for a dataset. Date when the content or structure of the database was last changed Date of last update of the dataset BioCASE CODATA TDWG ITIS*ca draft metadata. Date when the database was last changed, including the addition, deletion, or editing of records as well as structural changes that may influence the format or structure of ABCD-conformant output Mandatory to raise efficiency of "harvesters" and indexing engines working on datasets derived from the data source. Version of the datasource Source version BioCASE CODATA TDWG Version number or edition of the datasource URI of the original datasource Source URI BioCASE CODATA TDWG ITIS*ca draft metadata. A URL providing an access interface to the original datasource Expiry date of records from the datasource Expiry date of source dataset BioCASE CODATA TDWG ITIS*ca draft metadata. Date after which the records in the database should not anymore be used Allows databases to force update of indices etc. Number of units in the source database Number of unit records in the source dataset BioCASE CODATA TDWG Total number of unit-level records in the datasource Additional properties of the dataset as created when it is derived from the origninal source or from an already derived dataset. Additional properties of datasets Dataset derivation BioCASE CODATA TDWG Additional properties pertaining to the dataset(s) derived directly or indirectly from of the orignal source. Repeatable to form a derivation history where appropriate. Date supplied BioCASE CODATA TDWG ITIS*ca draft metadata. Supplier of the dataset. Dataset supplier BioCASE CODATA TDWG Individual or organisation who have (generated and) supplied the dataset Legal rights and ownership if different from original source Dataset rights BioCASE CODATA TDWG A container element stating the ownership and legal rights pertaining to the entire dataset. May be overuled by statements under UnitData Should always be cited together with DBRights Acknowledgements, disclaimer, credit, if different from orgininal source Dataset statements BioCASE CODATA TDWG A container element for statements of creditation or disclaimers. May be overuled by statements under UnitData Should always be cited together with DBStatements Text describing the DataSet Dataset description BioCASE CODATA TDWG A free text statement describing the dataset, including e.g. statements about selective criteria or sort order used in the generation of the dataset A container for one or more unit data records A container for all data referring to a unit (specimen or observation record) Person, person team, project or organization. Agent Type Person, person team, project or organization. BioCASE CODATA TDWG Neil Thomson Free text details for Agent. Agent text Free text details for Agent. BioCASE CODATA TDWG Neil Thomson Agent organization name and code(s). Organization Agent organization name and code(s). BioCASE CODATA TDWG Neil Thomson Person agent name. Person Person agent name. BioCASE CODATA TDWG Neil Thomson Free text alternative to structured data under the same node (in contrast to comment etc.) BioCASE CODATA TDWG Berendsohn The idea behind this type is that it actually has a "consists of" relationship with the respective atomized data items. Presently it can be treated as any other xs:string 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 intertest 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 described flat plains or exposed redge 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 Compas 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 measuremnt 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 expressedas text. BioCASE CODATA TDWG Jim Croft 10/2002 South West facing slope Westward cliff This field will as par as possible be a verbatim quote from the specimen label. 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 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: -. 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 you in association with the element ProvenanceType 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). UnitIDspreceeded by garden code (). 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. 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 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 Role of Person or Organisation in context 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 BioCASE CODATA TDWG Set of addresses for person or organisation. PreferredFlag attribute is used to indicate preferred postal address. Contact address 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 e-mail address. +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 URLs for person or organisation BioCASE CODATA TDWG Set of URLs of web sites for person or organisation. URL for person or organisation Publicly available URL for person or organisation. PreferredFlag attribute indicates main URL. Details of the country Country Elements covering the representation of the country and it 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 tghe schems 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 Organization (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 standardization 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, interpereted 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 Organization (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 standardization 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-letter ISO code for representatioin of name of country or origin 2-letter ISO country code ISO Country The 2-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 Organization (ISO). BioCASE CODATA TDWG HISPID Jim Croft 2002 ABIS ITF ISO Brummitt (1992) AUS ESP FRA USA This field should contain a valid entry as defined by the International Standards Organization (ISO Standard 3166) 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 teh field should containg the value "XY". In these cases, the Country field must have the entry 'UNKNOWN'. All remaining 'location group' fields should be left unfilled. The 2 letter 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 sould 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) 3-letter ISO code for representation of name of country of origin 3-letter ISO country code ISO Country The 2-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 Organization (ISO). BioCASE CODATA TDWG HISPID Jim Croft 2002 ABIS ITF ISO Brummitt (1992) AU ES FR PG US This field should contain a valid entry as defined by the International Standards Organization (ISO Standard 3166) 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 containg the value "XXY". In these cases, the Country field must have the entry 'UNKNOWN'. All remaining 'location group' fields should be left unfilled. The 3-letter ISO codes in ISO Code for Country of Origin field assist updating and cross referencing countries where boundaries change. 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 See comments under Country. This element is also covered by various geographic standards and may be better covered by reference to these.(JRC) Elements only used for units in culture collections Names under which the culture is known Reference or trade name for a microbial culture Charles Copp Oct. 2001 BioCASE CODATA TDWG ABCD Workshop 1 BioCASE CODATA TDWG The growth medium for a microbial or similar culture e.g. agar ABCD Workshop 1 BioCASE CODATA TDWG ABCD Workshop 1 BioCASE CODATA TDWG Preferably a number - attribute gives temperature scale used ABCD Workshop 1 BioCASE CODATA TDWG ABCD Workshop 1 BioCASE CODATA TDWG ABCD Workshop 1 BioCASE CODATA TDWG References for the culture conditions and method Attribute for RefType Neil Thomson August 2002 BioCASE CODATA TDWG 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öring, A. Güntsch and W. Berendsohn BioCASE Model: VDate. 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 fiields 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 satifies the standard structured date format. BioCASE CODATA TDWG HISPID Jim Croft ABIS ITF Alphabetic mixed case and interger; 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 Post WW2 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 filed 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 generalized date ranges and unresolvable 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 purporse, even though the date might correspond to the standard structured data format. The exact date (and time) or beginning of a period, expressed in ANSI/ISO 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öring, A. Güntsch and W. 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öring, A. Güntsch and W. 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 ANSI/ISO 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öring, A. Güntsch and W. 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öring, A. Güntsch and W. Berendsohn 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 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öring, A. Güntsch and W. Berendsohn 13.5 04.25 Note that times are decimial hours: 13.5 represents 1:30 pm, not 1:05 pm, nor 1:50 pm The date and time expressed in a way conforming to a subset of ISO 8601 ISO/ANSI Date and Time ISODateTime A representation of the date and time of (the beginning of) an event in ANSI/ISO standard structured format. BioCASE CODATA TDWG HISPID M.Döring, A. Güntsch and W. Berendsohn ISO Standard 8601:1988 HISPID ITF Any chronologically acceptable dat and time e 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 ommitted, the month is than preceeded by two hyphens The year and the month can be ommitted, 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 31. This field will nearly alway be a representaqiton dervied from the date on the specimen. The DateText field is available for recording verbatim date information for generalized 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. A name element dependent on a genus name under the bacteriological, botanical, and zoological code. BioCASE CODATA TDWG Elements describing the site and event of collecting or observing a unit. A string that identifies all material that resulted from a collecting event. Gathering code BioCASE CODATA TDWG Berendsohn 01 Mar 2003 NBN: Sample_Reference. Darwin Core 2: Field Number. Date(s) and time(s) of the gathering or observation event Gathering date and time BioCASE CODATA TDWG 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 BioCASE CODATA TDWG 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. Attribute PrimaryCollectorFlag to denote first collector. Gathering agents BioCASE CODATA TDWG 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 representation of the responsibles for collecting or recording. Project information concerning the gathering event. Project BioCASE CODATA TDWG Berendsohn 01 Mar 2003 BioCASE Model: Project Proj_Pk. Title of collection project Project title BioCASE CODATA TDWG 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 BioCASE CODATA TDWG Berendsohn 01 Mar 2003 The 'platform' from which observations or collections where made, e.g. the name of a research vessel or a remote operated vehicle Platform name BioCASE CODATA TDWG Berendsohn 01 Mar 2003 BioCISE Model: PlatformNm. ASC: PLATFORM-NAM. Refers to the 'platform' from which observations where made e.g. the name of a research vessel or a remote operated vehicle. Location at which a Gathering Event takes place. Gathering site BioCASE CODATA TDWG ITF. BioCISE Model: StatedLoc. HISPID4: Locality (loc). ASC: Locality-Nam. Element contains both geospatial and descriptive elements. Original locality data as apearing on a label. Locality Text The locality data from the label as a string of text BioCASE HISPID CODATA TDWG 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 ommisions 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 infoirmation from the Continental level down, or just regional locality string excluding the higher level named areas or regions (JRC) Name of Continent or Ocean. Separate from NamedArea for compatibility reasons. Continent or Ocean The standard name of the Continent or Ocean; the primary division of geographic locality. BioCASE CODATA TDWG Jim Croft Darwin Core 2: Continent Ocean South America Indian Ocean Asia South America Maps to Darwin Core 2: Continent Ocean. The list of available Continent and Ocean names is probably small enough that it could be handled by a controlled enumeration. Howevera this may blow out when the equivalents in mulktiple languages are included.(JRC) Details of the country. Separate from NamedArea for compatibility reasons. Country Elements covering the representation of the country and it name. BioCASE CODATA TDWG 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 tghe schems would blow it out to an unacceptable level; is it possible to refer to these lists externally with physically invoking them?(JRC) Atomized placenames with possibility for hierarchical structuring. The nearest named place to the collection or observation location Near named place BioCASE CODATA TDWG Jim Croft ABIS. AUSLIG. HISPID4: nnp. TDWG: Stanloc. Distance and directional point. Relation to nearest named place BioCASE CODATA TDWG Free text description of further details pertaining to the observation, sampling or collection locality Area detail BioCASE CODATA TDWG 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 BioCASE CODATA TDWG 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. Alternative GET or POST representation is specified by the GetPost attribute. BioCASE CODATA TDWG URI (e.g. web address) for thelocation 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 BioCASE CODATA TDWG WMS is already common use. You can link to Microsoft's Terraserver and lots of other resources.[Reed Beaman] Attribute for Original data. Composite element to allow recording multiple coordinates or same coordinate in different systems Charles Copp Oct 2001 BioCASE CODATA TDWG Coordinates measuring system e.g. GPS, field map reference, inferred map reference ABCD Workshop 1 BioCASE CODATA TDWG HISPID4: geosou (part). BioCASE Model: CrdMsmthMtd . ABCD Workshop 1 BioCASE CODATA TDWG ABCD Workshop 1 BioCASE CODATA TDWG HISPID4: sqz. ABCD Workshop 1 BioCASE CODATA TDWG HISPID4: sge (part). ABCD Workshop 1 BioCASE CODATA TDWG HISPID4: sgn (part). ABCD Workshop 1 BioCASE CODATA TDWG Geospatial coordinates recorded using a grid system ABCD Workshop 1 BioCASE CODATA TDWG BioCASE Model: Geospatial Coordinates GridSysNam, GridCode, GridPreQual,CrdMsmtMth. Grid system name e.g. "GB OS" ABCD Workshop 1 BioCASE CODATA TDWG BioCASE Model: GrdSystTxt. ABCD Workshop 1 BioCASE CODATA TDWG Grid reference precision qualifier ABCD Workshop 1 BioCASE CODATA TDWG BioCASE Model: GridPrecQual. 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. ABCD Workshop 1 BioCASE CODATA TDWG ABIS. ITF. AUSLIG. Maps to Darwin Core 2: Longitude. Express in decimal degrees Workshop 1 BioCASE CODATA TDWG Darwin Core 2: Longitude. Maps to Darwin Core 2: Latitude. Express in decimal degrees Workshop 1 BioCASE CODATA TDWG Darwin Core 2: Latitude. mathematical surface on which the mapping and coordinate system used for the geocodes of the record are based ABCD Workshop 1 BioCASE CODATA TDWG AS/NZS4270 spatial transfer standard, SDTS spatial transfer standard. ABCD Workshop 1 BioCASE CODATA TDWG Free text statement of degree of accuracy ABCD Workshop 1 BioCASE CODATA TDWG HISPID4: includes geoacy TDWG: LatAccurr, LongAccur. Maps to Darwin Core 2: Coordinate Precision. An estimate of how tightly the collecting locality was specified; expressed as a distance in metres corresponding to a radius around the Lat/Long coordinates. Use NULL where precision is unknown, cannot be estimated or is not applicable. Neil Thomson July 2002 BioCASE CODATA TDWG Darwin Core 2: Coordinate Precision. Distance above (positive) or below sea level of the collecting locality. Altitude BioCASE CODATA TDWG 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 hight and Depth elements, which are measured relative to a local surface. Vertical distance measure in relation to a ground datum, e.g. water level, which normally forms the upper limit of a possible range. Depth BioCASE CODATA TDWG 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 in relation to a ground datum, e.g. ground level, which normally forms the lower limit of a possible range. Hight BioCASE CODATA TDWG 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 Hight element is preserved for the sake of clarity. Positive above the surface. A container for geological dating and rock unit names related to the site or sample locations Stratigraphy BioCASE CODATA TDWG 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 staus is unknown or for more full descriptions of stratigraphy of site. An container element for citing biotope type terms (e.g. classification terms) and measurments (e.g. vegetation height) related to the unit's gathering site Attribute for classification system used. Biotope classification BioCASE CODATA TDWG NBN: Short_Name. Attribute for type designating ShortName, Long name, Code, or AltText Biotope name BioCASE CODATA TDWG NBN: Long_Name. Free text field for informal recording of Biotope Biotope text BioCASE CODATA TDWG A container allowing to linking any biotope-related measurement to the site description Biotope measurements BioCASE CODATA TDWG Although this could be covered by a generic element for site measurements, the separate element is preserved for the sake of clarity. A measurement (e.g. biotope area size) of the biotope at the gathering site Biotope measurement BioCASE CODATA TDWG Berendsohn 01 Mar 2003 NBN: biotope_occurrence_data. 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 BioCASE CODATA TDWG 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 pl