$Id: darwin2obis.xsd,v 1.12 2003/05/16 08:47:43 Wei Zhuang $ XML Schema describing the OBIS extension of Darwin Core V2 (http://tsadev.speciesanalyst.net/documentation/ow.asp?DarwinCoreV2) content model. Uses and extends data elements from the DiGIR (http://digir.sourceforge.net) protocol. ISO 8601 compliant stamp indicating the date and time in UTC(GMT) when the record was last modified. Example: "November 5, 1994, 8:15:30 am, US Eastern Standard Time" would be represented as "1994-11-05T13:15:30Z" (see W3C Note on Date and Time Formats - http://www.w3.org/TR/NOTE-datetime). A "standard" code identifier that identifies the institution to which the collection belongs. No global registry exists for assigning institutional codes. Use the code that is "standard" in your discipline. A unique alphanumeric value which identifies the collection within the institution A unique alphanumeric value which identifies an individual record within the collection. It is recommended that this value provides a key by which the actual specimen can be identified. If the specimen has several items such as various types of preparation, this value should identify the individual component of the specimen Gives the web address of the page where more information on this particular record (not on the whole dataset) can be found. The full name of lowest level taxon the Cataloged Item can be identified as a member of; includes genus name, specific epithet, and subspecific epithet (zool.) or infraspecific rank abbreviation, and infraspecific epithet (bot.) Use name of suprageneric taxon (e.g., family name) if Cataloged Item cannot be identified to genus, species, or infraspecific taxon. An abbreviation indicating whether the record represents an observation (O), living organism (L), specimen (S), germplasm/seed (G), etc. Indicates who gave the record to the data provider. Can indicate a literature citation, an electronic dataset, etc. Is used to provide credit. Indicates how this record should be attributed if used The kingdom to which the organism belongs The phylum (or division) to which the organism belongs The class name of the organism The order name of the organism The family name of the organism The genus name of the organism The subgenus name of the organism The specific epithet of the organism The sub-specific epithet of the organism The author of a scientific name. Author string as applied to the accepted name. Can be more than one author (concatenated string). Should be formatted according to the conventions of the applicable taxonomic discipline. The name(s) of the person(s) who applied the currently accepted Scientific Name to the Cataloged Item. The year portion of the date when the Collection Item was identified; as four digits [-9999..9999], e.g., 1906, 2002. The month portion of the date when the Collection Item was identified; as two digits [01..12]. The day portion of the date when the Collection Item was identified; as two digits [01..31]. Indicates the kind of nomenclatural type that a specimen represents. (This is incomplete because type status actually describes the relationship between a name and a specimen [or ternary relatiohnship between a specimen, name, and publication].) In particular, the type status may not apply to the name listed in the scientific name, i.e., current identification. In rare cases, a single specimen may be the type of more than one name. An identifying "number" (really a string) applied to specimens (in some disciplines) at the time of collection. Establishes a link between different parts/preparations of a single specimen and between field notes and the specimen. A "number" (really a string) created at collection time to identify all material that resulted from a collecting event. The name(s) of the collector(s), people or organisation(s) responsible for collecting the specimen, taking the observation, fishing the catch or doing whatever is the underlying basis of the record. The year (expressed as an integer) the sample/observation/record event occurred. The full year should be expressed (e.g. 1972 must be expressed as "1972" not "72"). Must always be a four digit integer For samples/observations/record events that were taken over time this gives the start year of the collecting event. The full year should be expressed (e.g. 1972 must be expressed as "1972" not "72"). Must always be a four digit integer For samples/observations/record events that were taken over time this gives the end year of the collecting event. The full year should be expressed (e.g. 1972 must be expressed as "1972" not "72"). Must always be a four digit integer The month of year the sample/observation/record event occurred in the field. For samples/observations/record events that were taken over time this gives the start month of the collecting event. Possible values range from 01...12 inclusive For samples/observations/record events that were taken over time this gives the end month of the collecting event. Possible values range from 01...12 inclusive The day of the month the sample/observation/record event occurred in the field. Possible value ranges from 01..31 inclusive For samples/observations/record events that were taken over time this gives the start day of the collecting event. Possible value ranges from 01..31 inclusive For samples/observations/record events that were taken over time this gives the end day of the collecting event. Possible value ranges from 01..31 inclusive The ordinal day of the year for the sample/observation/record event; i.e., the number of days since January 1 of the same year. (January 1 is Julian Day 1.). Should be an integer from one to 365, i.e. of the form (([0-3][0-9][0-9)|([0-9][0-9)|([1-9])). For samples/observations/record events that were taken over time this gives the start ordinal day of the year for the collecting event; i.e., the number of days since January 1 of the same year. (January 1 is Julian Day 1.). Should be an integer from one to 365, i.e. of the form (([0-3][0-9][0-9)|([0-9][0-9)|([1-9])). For samples/observations/record events that were taken over time this gives the end ordinal day of the year for the collecting event; i.e., the number of days since January 1 of the same year. (January 1 is Julian Day 1.). Should be an integer from one to 365, i.e. of the form (([0-3][0-9][0-9)|([0-9][0-9)|([1-9])). The time of day a specimen was collected expressed as decimal hours from midnight local time (e.g. 12.0 = mid day, 13.5 = 1:30pm) For samples/observations/record events that were taken over time this gives the start time of day of the collecting event expressed as decimal hours from midnight local time (e.g. 12.0 = mid day, 13.5 = 1:30pm) For samples/observations/record events that were taken over time this gives the end time of day of the collecting event expressed as decimal hours from midnight local time (e.g. 12.0 = mid day, 13.5 = 1:30pm) Indicates the time zone for the Time of Day measurements*Need to decide how to express: as abbreviations (e.g. GMT), as numbered time zones from 1-24. Do we allow "local" to be entered? If field is blank, should "local" be assumed? The continent or ocean from which a specimen was collected or in which the sample/observation/record event occurred. The country or major political unit from which the specimen was collected or in which the sample/observation/record event occurred. ISO 3166-1 values should be used. Full country names are currently in use. A future recommendation is to use ISO3166-1 two letter codes or the full name when searching The state, province or region (i.e. next political region smaller than Country) from which the specimen was collected or in which the sample/observation/record event occurred.. There is some suggestion to use the values described in ISO 3166-2, however these values are in a continual state of flux and it appears unlikely that an appropriate mechanism (by ISO) will be in place to manage these changes. Hence it is recommended that where possible, the full, unabbreviated name should be used for storing information. The server should optionally handle abbreviations as an access point. Note: this is a recurring theme (country and state) abbreviations. Check the existence of an attribute type to deal with abbreviations from the bib-1 profile The county (or shire, or next political region smaller than State / Province) from which the specimen was collected The locality description (place name plus optionally a displacement from the place name) from which the specimen was collected or in which the sample/observation/record event occurred. Where a displacement from a location is provided, it should be in un-projected units of measurement The longitude of the location from which the specimen was collected or in which the sample/observation/record event occurred. This value should be expressed in decimal degrees. (East & North = +; West & South = -) For samples/observations/record events better represented as line features rather than point features (e.g. extended trawls or transects) this indicates the starting longitude location from which the specimen was collected. Express in decimal degrees (East & North = +; West & South = -) For samples/observations/record events better represented as line features rather than point features (e.g. extended trawls or transects) this indicates the ending longitude location from which the specimen was collected. Express in decimal degrees (East & North = +; West & South = -) The latitude of the location from which the specimen was collected. This value should be expressed in decimal degrees (East & North = +; West & South = -) For samples/observations/record events better represented as line features rather than point features (e.g. extended trawls or transects) this indicates the starting latitude location from which the specimen was collected or in which the sample/observation/record event occurred. This value should be expressed in decimal degrees (East & North = +; West & South = -) For samples/observations/record events better represented as line features rather than point features (e.g. extended trawls or transects) this indicates the ending latitude location from which the specimen was collected or in which the sample/observation/record event occurred. This value should be expressed in decimal degrees (East & North = +; West & South = -) An estimate of how tightly the locality was specified in the Latitude and Longitude fields; expressed as a distance, in meters, that corresponds to a radius around the latitude-longitude coordinates. Use NULL where precision is unknown, cannot be estimated, or is not applicable. An estimate of how tightly the locality was specified in the Start/End Latitude and Longitude fields; expressed as a distance, in meters, that corresponds to a radius around the latitude-longitude coordinates. Use NULL where precision is unknown, cannot be estimated, or is not applicable. This access point provides a mechanism for performing searches using a bounding box. A Bounding Box element is not typically present in the database, but rather is derived from the Latitude and Longitude columns by the data provider. The minimum distance in meters above (positive) or below sea level of the collection/record locality. The maximum distance in meters above (positive) or below sea level of the collection/record locality. The minimum distance in meters below the surface of the water at which the collection/record was made; all material collected was at least this deep. Positive below the surface, negative above (e.g. collecting above sea level in tidal areas). The maximum distance in meters below the surface of the water at which the collection/record was made; all material collected was at most this deep. Positive below the surface, negative above (e.g. collecting above sea level in tidal areas). For data sets that have the depth range expressed in one field (e.g. "150-200 m") it can be entered here as free text. Separate, numeric Minimum and Maximum Depth fields are the preferred format; the Depth Range option is included for legacy data sets. The temperature recorded with the collection/record event. Is assumed to be taken at the collection depth. Expressed in degrees Celsius. The sex of a specimen or collected/observed individual(s). The domain should be a controlled set of terms (codes) based on community consensus. Proposed values: M=Male; F=Female; H=Hermaphrodite; I=Indeterminate (examined but could not be determined; U=Unkown (not examined); T=Transitional (between sexes; useful for sequential hermaphrodites); B = Both Male and Female Indicates the life stage present. Will require developing a controlled vocabulary. Can include multiple stages for a lot with multiple individuals. The type of preparation (skin. slide, etc). Probably best to add this as a record element rather than access point. Should be a list of preparations for a single collection record. The number of individuals present in the lot or container. Not an estimate of abundance or density at the collecting locality. The number of individuals (abundance) found in a collection/record event. The total biomass found in a collection/record event. Expressed as kg. The previous (fully qualified) catalog number of the Cataloged Item (or collection/record) event if the item earlier identified by another Catalog Number, either in the current catalog or another Institution / catalog. A fully qualified Catalog Number is preceded by Institution Code and Collection Code, with a space separating the each subelement. Referencing a previous Catalog Number does not imply that a record for the referenced item is or is not present in the corresponding catalog, or even that the referenced catalog still exists. This access point is intended to provide a way to retrieve this record by previously used identifier, which may used in the literature. In future versions of this schema this attribute should be set-valued. A named or coded valued that identifies the kind relationship between this Collection Item (or record event) and the referenced Collection Item. Named values include: "parasite of", "epiphyte on", "progeny of", etc. In future versions of this schema this attribute should be set-valued. The fully qualified identifier of a related Catalog Item (a reference to another specimen); Institution Code, Collection Code, and Catalog Number of the related Cataloged Item, where a space separates the three subelements. Free text notes attached to the specimen record Geographic Markup Language(GML) description of the feature for representing complex shapes such as lines and polygons, per Open GIS Consortium (OGC) standards - http://www.opengis.net/gml/01-029/GML2.html#appB. A concrete digir:listType specifying all elements available for multiCOP operations.