Darwin Core: An Evolving Community-Developed Biodiversity Data Standard — TEI-tagged view

John Wieczorek, David Bloom, Robert Guralnick, Stan Blum, Markus Döring, Renato Giovanni, Tim Robertson, David Vieglais · 2012 · biodiversity-science · doi:10.1371/journal.pone.0029715 · TEI xml · tagged edition · index · concepts · authors
Where this record's text came from. 2026-09-07 schema-0.3 pass: every quote verified as an exact substring of the staged text and anchored at merge time; concept terms verified present; every edge endpoint an existing node.
Other fields define these differently the same word, defined another way in another discipline
consensus 6 fields · interoperability 6 fields · data quality 5 fields · ontology 4 fields · categories 3 fields · adaptability 2 fields · and 2 more →
Tags on this paper every tag the record carries, whether or not the words occur in the text below — a number is how many papers in the corpus carry that tag; a tag with no number is unique to this paper
Biodiversity data2 standardized view interoperability9 common terms Darwin Core data standard biodiversity information Simple Darwin Core relational Darwin Core common language clearly defined semantics people3 machines nine categories seven categories of terms Dublin Core authoritative form Resource Description Framework technical implementation encoding schemes Darwin Core Archives star schema Integrated Publishing Toolkit entity-relationship modeling normalized database structure ASC model ontological description Species Analyst Z39.50 protocol loose federation of databases ABCD minimal flat flexibility4 adaptability3 community driven consensus13 data quality5 fitness for use common vocabularies dictionaries of synonymous terms semantic web2 ontology5 Darwin Core Extension GNA Profile Audubon Core MIxS aggregation tools REBIOMA Map of Life living standard lack of a coordinated publishing and integration system data repositories2 Heterogeneity in meaning and content of terms obstacles in every aspect of data integration and use simple definitions of terms creation and publication of Darwin Core Archives relatively simple limited availability of data value and re-use standard for sharing data about biodiversity set of terms standard for encoding the semantic structure of web-based resources open-source software development project earlier guidelines A variety of tools standard format for biodiversity data practice-report11
Method, as described: define stable shared terms independently of encoding technology, publish records and archives, govern changes by open consensus, and extend the standard for new domains

Colour legend

PLoS ONE<title level="j">A work — the journal / venue title.
2012<date>A year or date.

John WieczorekpersName, David BloompersName, Robert GuralnickpersName, Stan BlumpersName, Markus DöringpersName, Renato GiovannipersName, Tim RobertsonpersName, David VieglaispersName (2012date). “Darwin Core: An Evolving Community-Developed Biodiversity Data Standard.” PLoS ONEtitle·j.

Object of study — Darwin Coreterm as a community-developed standard for publishing, sharing, and integrating biodiversity dataterm

Research question — how Darwin Coreterm defines a common semanticterm·var language, is implemented and governed, and evolves across biodiversity research communities

Contribution — an account of Darwin Coreterm's semanticterm·var structure, history, implementation patterns, governance, extensions, and knowledge-producing infrastructure

Cross-disciplinary analysis
content-tags & facets: phenomenon · claim-type · cross-domain-transfer · mechanism · claim-relation · replication-status · limitation — grounded in the full text
phenomenoninteroperability and integration of heterogeneous biodiversity information — “A general challenge of biodiversity data that is shared with many other information domains is the lack of a coordinated publishing and integration system; data repositories tend to be isolated from each other in the absence of standards for data and communication protocols. Heterogeneity in meaning and content of terms creates obstacles in every aspect of data integration and use, including discovery, comparison, and quality assessment. Information communities, especially Library Information Sciences, have a long history of meeting these challenges through the creation and maintenance of standards.”
claim-typemethod — “Biodiversity data derive from myriad sources stored in various formats on many distinct hardware and software platforms. An essential step towards understanding global patterns of biodiversity is to provide a standardized view of these heterogeneous data sources to improve interoperability. Fundamental to this advance are definitions of common terms. This paper describes the evolution and development of Darwin Core, a data standard for publishing and integrating biodiversity information. We focus on the categories of terms that define the standard, differences between simple and relational Darwin Core, how the standard has been implemented, and the community processes that are essential for maintenance and growth of the standard. We present case-study extensions of the Darwin Core into new research communities, including metagenomics and genetic resources. We close by showing how Darwin Core records are integrated to create new knowledge products documenting species distributions and changes due to environmental perturbations.”
method — evidence — “TDWG, as with other information standards bodies, has a history of developing data sharing standards that are bound to specific technologies, such as eXtensible Markup Language (XML). While Darwin Core is currently maintained in RDF, the enduring value of the standard lies in simple definitions of terms and their relationships to other terms, independent of technical implementation. As with Dublin Core, the idea is to promote use of the common terms in every appropriate context, and to leave the implementation details to specific applications. Data can be shared using Darwin Core in a variety of encoding schemes (Comma Separated Values, XML, JavaScript Object Notation, RDF, etc.). To aid in using Darwin Core in different contexts, there are documents with recommendations on how to share information as Darwin Core using various technologies.”
object of study — evidence — “Biodiversity data derive from myriad sources stored in various formats on many distinct hardware and software platforms. An essential step towards understanding global patterns of biodiversity is to provide a standardized view of these heterogeneous data sources to improve interoperability. Fundamental to this advance are definitions of common terms. This paper describes the evolution and development of Darwin Core, a data standard for publishing and integrating biodiversity information. We focus on the categories of terms that define the standard, differences between simple and relational Darwin Core, how the standard has been implemented, and the community processes that are essential for maintenance and growth of the standard. We present case-study extensions of the Darwin Core into new research communities, including metagenomics and genetic resources. We close by showing how Darwin Core records are integrated to create new knowledge products documenting species distributions and changes due to environmental perturbations.”
research question — evidence — “In this paper, we describe the Darwin Core standard, its history, status, relationship to other standards, and prospects for further evolution. We also discuss how data sets are brought into Darwin Core compliance and how Darwin Core records are currently shared in a distributed publishing platform. We will demonstrate how Darwin Core continues to extend beyond its original formulation for natural history collections and will present, via use cases, how the standard continues to be reshaped and extended through new collaborations. We close by discussing innovative computational and informatics approaches to improving the scale, scope, and usability of networks that rely on Darwin Core compliant records.”
contribution — evidence — “In this paper, we describe the Darwin Core standard, its history, status, relationship to other standards, and prospects for further evolution. We also discuss how data sets are brought into Darwin Core compliance and how Darwin Core records are currently shared in a distributed publishing platform. We will demonstrate how Darwin Core continues to extend beyond its original formulation for natural history collections and will present, via use cases, how the standard continues to be reshaped and extended through new collaborations. We close by discussing innovative computational and informatics approaches to improving the scale, scope, and usability of networks that rely on Darwin Core compliant records.”
mechanismsemantic standardization A standardized view and definitions of common terms make heterogeneous biodiversity sources interoperable. — “Biodiversity data derive from myriad sources stored in various formats on many distinct hardware and software platforms. An essential step towards understanding global patterns of biodiversity is to provide a standardized view of these heterogeneous data sources to improve interoperability. Fundamental to this advance are definitions of common terms. This paper describes the evolution and development of Darwin Core, a data standard for publishing and integrating biodiversity information. We focus on the categories of terms that define the standard, differences between simple and relational Darwin Core, how the standard has been implemented, and the community processes that are essential for maintenance and growth of the standard. We present case-study extensions of the Darwin Core into new research communities, including metagenomics and genetic resources. We close by showing how Darwin Core records are integrated to create new knowledge products documenting species distributions and changes due to environmental perturbations.”mechanisms[0]
mechanismcommon-language sharing A common language permits biodiversity data sharing while reusing metadata standards from other domains. — “The primary purpose of Darwin Core is to create a common language for sharing biodiversity data that is complementary to and reuses metadata standards from other domains wherever possible. Creating this common language has been particularly challenging, since natural history data curation practices have been developed locally and organically over hundreds of years, have varied between disciplines as well as institutions, and have had limited culture of data sharing.”mechanisms[1]
mechanismdefined-term interpretation Clearly defined semantics let people and machines interpret records and determine appropriate data uses. — “Fundamentally, Darwin Core is a set of terms having clearly defined semantics that can be understood by people or interpreted by machines, making it possible to determine appropriate uses of the data encoded therein. The terms are organized into nine categories (often referred to as “classes”, Figure 2 ), six of which cover broad aspects (event, location, geological context, occurrence, taxon, and identification) of the biodiversity domain. The remaining categories cover relationships to other resources, measurements, and generic information about records. Especially for the record level, Darwin Core recommends the use of a number of terms from Dublin Core (type, modified, language, rights, rightsHolder, accessRights, bibliographicCitation, references). The full set of current Darwin Core terms with their descriptions is available in the Quick Reference Guide ( http://rs.tdwg.org/dwc/terms/ ).”mechanisms[2]
mechanismimplementation independence Stable term definitions can be reused across CSV, XML, JSON, RDF, and other technical contexts. — “TDWG, as with other information standards bodies, has a history of developing data sharing standards that are bound to specific technologies, such as eXtensible Markup Language (XML). While Darwin Core is currently maintained in RDF, the enduring value of the standard lies in simple definitions of terms and their relationships to other terms, independent of technical implementation. As with Dublin Core, the idea is to promote use of the common terms in every appropriate context, and to leave the implementation details to specific applications. Data can be shared using Darwin Core in a variety of encoding schemes (Comma Separated Values, XML, JavaScript Object Notation, RDF, etc.). To aid in using Darwin Core in different contexts, there are documents with recommendations on how to share information as Darwin Core using various technologies.”mechanisms[3]
mechanismarchive semantics A small XML descriptor connects CSV columns and record relationships in a Darwin Core Archive. — “The Simple Darwin Core ( http://rs.tdwg.org/dwc/terms/simple/index.htm ) document explains the capacity to share records with properties that do not repeat, as simple text files or XML. There is also an XML Guide with reference XML schemas for highly structured data and a Text Guide explaining the construction of Darwin Core Archives (a combination of CSV files and a simple XML document describing the semantics of the data file columns and their relationships to each other). Darwin Core Archives can support structured data that conform to a star schema (a single core set of records in one or more files, with one-to-one or one-to-many relationships to records in other files). The Darwin Core Archive is becoming ever more popular as an easy means for data sharing, largely due to the release of supporting tools, in particular the next-generation data publishing system – the Integrated Publishing Toolkit ( http://www.gbif.org/informatics/infrastructure/publishing ) – an open source application developed by the Global Biodiversity Information Facility discussed in further detail below. Darwin Core Archives have been adopted by Pensoft® ( http://www.pensoft.net/journals/ ) as the preferred form for data appendices to taxonomic publications in MycoKeys, PhytoKeys, and ZooKeys.”mechanisms[4]
mechanismopen consensus governance Public discussion, change requests, review, and versioning adapt the standard without abandoning compatibility. — “Darwin Core development is community driven and follows the process published in the Darwin Core Namespace Policy ( http://rs.tdwg.org/dwc/2009-09-23/terms/namespace/index.htm ). Open commentaries on issues related to Darwin Core are expressed through a public forum (at tdwg-content@lists.tdwg.org ) to which any subscriber may contribute. Discussions that result in consensus for change (new terms, new definitions, new relationships, changes in documentation) are submitted as change requests using templates requesting the appropriate information on the issue tracker of the Darwin Core Project site ( http://code.google.com/p/darwincore/wiki/SubmittingIssues ). Sometimes this process is reversed, with a submitted issue being copied to the discussion forum for elaboration and consensus before refining the issue as submitted. All changes undergo a 30-day public review, announced on the listserv. Changes are reviewed by TDWG's Technical Architecture Group (TAG: http://www.tdwg.org/activities/tag/ ), a set of volunteer members with broad interest and expertise in web-based interoperability. The TAG determines if the proposed changes are compatible with Darwin Core and that they do not reinvent existing standards. Changes that pass this review process are made as version changes to the affected documents, the latest of which always constitute the current standard.”mechanisms[5]
mechanismsynonym normalization A dictionary can map voucher and sample to PreservedSpecimen so applications substitute terms and improve discovery. — “Data quality and fitness for use are primary concerns in the biodiversity community [42] , where information comes from heterogeneous sources spanning the globe over hundreds of years. Both data discovery and data quality assessment are hampered by this heterogeneity. Part of the solution depends on the use of common vocabularies, part on dictionaries of synonymous terms, and a great deal on applications that can facilitate discovery and assessment in place of or to aid in otherwise labor-intensive “cleanups”. For example, having a dictionary that equates “voucher” and “sample” with an accepted term “PreservedSpecimen” would allow applications to make this substitution automatically and allow users to discover relevant data using any of the synonyms regardless of how they were stored in the original data.”mechanisms[6]
mechanismapplication-level validation The standard recommends constraints while applications enforce them only where the collaboration requires. — “Darwin Core makes recommendations about constraints on data content, whether about data types, valid values, or controlled vocabularies. For example, decimalLatitude is recommended to be a floating-point number falling between 90 and −90, inclusive; countryCode is recommended to be a value from ISO 3166-1-alpha-2 (two-letter country codes). Though these recommendations are made in the standard, the philosophy is to relegate enforcement to applications where they make sense. For example, in a collaboration where the purpose is to automate data quality improvement on shared data, it is essential to be able to share the warts-and-all data that need to be investigated and improved.”mechanisms[7]
mechanismpublishing and registry coupling The IPT produces archives and metadata while a registry enables global discovery and retrieval. — “The Integrated Publishing Toolkit (IPT; http://www.gbif.org/informatics/infrastructure/publishing/ ) is an open-source software development project, led by GBIF, designed to address the challenges of sharing biodiversity data. By producing and providing easy access to Darwin Core Archives and resource metadata in Ecological Markup Language [44] , the IPT works in tandem with a Global Biodiversity Resources Discovery System (GBRDS), a data registry, to facilitate discovery and retrieval of shared data throughout the world. The IPT complements other tools that have been created to assist data users to explore, organize, and mobilize data sets. A range of spreadsheet and archive creators and validators has been developed by GBIF and others. These tools can be accessed via the GBIF Publishing Software web page ( http://www.gbif.org/informatics/standards-and-tools/publishing-data/publishing-software/ ).”mechanisms[8]
mechanismaggregation and indexing Thematic networks ingest Darwin Core files into stores indexed for high-performance querying. — “Whereas tools such as the IPT facilitate data mobilization using Darwin Core data, other tools build on these sources to integrate and index biodiversity data. These aggregators are thematic networks with either geographic (e.g., Atlas of Living Australia, http://www.ala.org.au/ ) or taxonomic focus (e.g., VertNet, http://vertnet.org ). Developing these systems to work sustainably and at large scales is an area of active research. For example, VertNet ( http://vertnet.org/ ), an aggregation of vertebrate specimen and observation data into a cloud-based data store, makes use of the Simple Darwin Core in comma separated value (.csv) files with header rows containing Darwin Core term names. These files are published to the data store where the records are indexed for high-performance querying.”mechanisms[9]
mechanismextension lifecycle Specialized terms are tested outside the core namespace and incorporated after broader utility and consensus are established. — “Because Darwin Core aims to cover the common ground in biodiversity, it inevitably lacks terms that are of interest to more specialized groups. A Darwin Core Extension consists of additional terms describing a complementary, related domain, or guidance on the use of Darwin Core within a specific sub-domain of biodiversity. Over the last decade, Darwin Core has evolved by means of extensions, some of which have been incorporated in the standard. For example, the terms of a paleontology extension related to an earlier, pre-standard version of Darwin Core became the terms of the current GeologicalContext class. Similarly, terms originating from an early version of the Darwin Core created for the Ocean Biogeographic Information System (OBIS; http://www.iobis.org/ ) have also been added to Darwin Core. Going forward, specific projects or disciplines may find it convenient to extend the scope of Darwin Core outside the existing namespace and governance process for proof-of-concept research. Once the understanding of the new terms has been tested and proven of utility in a broader context, incorporation into the standard can be accomplished through community consensus.”mechanisms[10]
mechanismbidirectional standards harmonization Complementary Darwin Core and MIxS terms support reciprocal reuse plus domain-specific reporting requirements. — “Currently, Darwin Core and GSC developers are collaborating (supported by NSF-RCN4GSC) to harmonize Darwin Core and MIxS to aid the growing field of sequence-based diversity research. Darwin Core and GSC developers have concluded that the standards are conceptually similar and that the distinct sets of terms are complementary. This allows the development of a bi-directional (see Figure 2 ) solution, where in the future the GSC will be able to incorporate terms from Darwin Core and add GSC-specific reporting requirements, while Darwin Core will be able to offer a genomics extension using the results of this activity.”mechanisms[11]
mechanismstandardized conservation workflow REBIOMA standardizes, mobilizes, aggregates, vets, and models distributed occurrence data. — “Though predated by examples of the effective use of Darwin Core for distribution modeling, influence of natural area preservation, and estimates of climate change impact [53] , the utility of data shared using Darwin Core is illustrated by two recent examples. First, the University of California, Berkeley, and the Wildlife Conservation Society have collaborated to create Réseau de la Biodiversité de Madagascar (REBIOMA, http://www.rebioma.net/ ).The effort seeks to make biodiversity data about Madagascar available via a single web-based resource. Primary data on biodiversity in Madagascar come from researchers and institutions all over the world. REBIOMA works with each collection to standardize the data using the Darwin Core, to mobilize and aggregate the data, and to vet the data for quality, completeness, and fitness for use. Data passing automated quality checks and review by a board of taxonomic experts are analyzed in combination with environmental data to produce maps showing models of where species might occur. The success of this project has made it possible for researchers, policy makers, government officials, and conservationists to capture a wealth of data to address issues of Malagasy biodiversity. The simplicity and flexibility of Darwin Core has made it possible for REBIOMA to provide immediate access to high-quality data and tools for monitoring and assessing conservation efforts.”mechanisms[12]
mechanismknowledge-base integration Map of Life combines Darwin Core occurrence points with ranges, checklists, habitat data, and models to produce distribution products. — “A second example of innovative use of Darwin Core data is the Map of Life Project ( http://www.mappinglife.org/ ), and sister projects such as LifeMapper ( http://www.lifemapper.org/ ) [54] , which aggregate and mobilize sources of species distribution information and provide tools to visualize and analyses those data. In Map of Life, species occurrence data points formatted as Darwin Core are queried and brought into the application with related data sources such as range maps, assemblage checklists, and habitat preference data. Integration of these data types and modeling will lead to summary products describing species distributions and provide the basis for distribution change assessments in the face of human-induced global changes [55] . The Map of Life will be a knowledge base of hundreds of thousands of high-resolution species distribution maps covering a wide range of taxa and geographic locations.”mechanisms[13]
builds-on Dublin Core Metadata Initiative — “Though the scope and governance of Darwin Core are distinct from Dublin Core [26] , readers will recognize the ancestry of Darwin Core in their shared traits: mission, principles of operation, and inherited terms. Indeed, if words were nucleotides, the Darwin Core mission is the same as that of Dublin Core except for one base-pair addition (in bold), namely, “to provide simple standards to facilitate the finding, sharing and management of biodiversity information.” This relationship is not accidental. The Dublin Core Metadata Initiative (DCMI) has done a very good job of maintaining the metadata specifications at the core of web-based resources. The success of DCMI encouraged TDWG to adopt similar policies for the specific domain of biodiversity through the Darwin Core. This process, in turn, acts as the basis for the development of data standards for even more specific sub-disciplines (e.g., plant genetic resources) as well as a basis for collaboration with complementary related domains (e.g., metagenomics).”claim_relations[0]
contrasts-with Access to Biological Collections Data — “Darwin Core was developed in parallel with efforts in Europe to establish a comprehensive model for biological collections information — Access to Biological Collections Data (ABCD) [39] . The philosophies of the two approaches were distinct, even if they both had the goal of promoting sharing of biodiversity information. Darwin Core was designed to be minimal (only terms shared in common throughout natural history collections) and flat (no relational structure), while ABCD was highly structured and sought to capture the wide variety of biodiversity data and their relationships. Both groups defined their data models in XML schemas. ABCD was ratified as a standard by TDWG in 2005. Darwin Core departed from defining the standard in XML schema and followed the DCMI model, incorporating the experience of the previous decade to establish a set of terms in wide use in practice for data sharing.”claim_relations[1]
supports biodiversity-data interoperability — “Biodiversity data derive from myriad sources stored in various formats on many distinct hardware and software platforms. An essential step towards understanding global patterns of biodiversity is to provide a standardized view of these heterogeneous data sources to improve interoperability. Fundamental to this advance are definitions of common terms. This paper describes the evolution and development of Darwin Core, a data standard for publishing and integrating biodiversity information. We focus on the categories of terms that define the standard, differences between simple and relational Darwin Core, how the standard has been implemented, and the community processes that are essential for maintenance and growth of the standard. We present case-study extensions of the Darwin Core into new research communities, including metagenomics and genetic resources. We close by showing how Darwin Core records are integrated to create new knowledge products documenting species distributions and changes due to environmental perturbations.”claim_relations[2]
extends Darwin Core beyond natural-history collections — “Darwin Core continues to be integrated into new research communities. For example, the Nordic Genetic Resource Center (NordGen; http://www.nordgen.org ) and Bioversity International (formerly IPGRI) ( http://www.bioversityinternational.org ) have sought to take advantage of Darwin Core on behalf of the European plant genetic resources and genebank community and, at the same time, share rich discipline-specific genetic resource information. A careful review was made of Darwin Core and a set of additional terms that did not overlap or conflict with existing Darwin Core terms was proposed to meet the community's needs. The new terms, modeled directly from FAO/IPGRI Multi-Crop Passport Descriptors [45] (2001) and the proposed EPGRIS3 trait data standard for characterization and evaluation data [46] , were expressed and published openly in an XML schema for germplasm data (DwC-germplasm, http://code.google.com/p/darwincore-germplasm/ ) [47] , resulting in the first successfully deployed extension to the Darwin Core Standard.”claim_relations[3]
qualifies semantic-web use of Darwin Core — “Though the Darwin Core is defined in an RDF document, integration of biodiversity data in the semantic web is in its early stages. One of the major challenges for Darwin Core in the semantic web context is the lack of a well-defined ontology - a formal definition of relationships between terms in a defined domain. An ontology would define the relationships between concepts such as biological entities, the events that document where and when they occurred, and the processes through which they are identified as being representative of a taxonomic concept. Without rigorous relationships between concepts and the properties that define them, connections between biodiversity data and related semantically rich information, such as literature and genomes, are difficult to traverse. This creates obstacles to cross-disciplinary semantic inquiry, such as in the Linked Data distributed data community ( http://linkeddata.org/ ). Current research is trying to address this gap (see TaxonConcept Knowledge Base, http://www.taxonconcept.org/ and BiSciCol, http://biscicol.blogspot.com/ ), active discussions on various aspects of the challenge take place regularly on the Darwin Core public forum ( http://lists.tdwg.org/mailman/listinfo/tdwg-content ), and an RDF task group has been established within TDWG “to adapt TDWG vocabularies for use as RDF classes and properties and to integrate those resources with other well-known vocabularies and ontologies outside TDWG for use in describing biodiversity resources.” [43]”claim_relations[4]
demonstrates Darwin Core's research and conservation utility — “Though predated by examples of the effective use of Darwin Core for distribution modeling, influence of natural area preservation, and estimates of climate change impact [53] , the utility of data shared using Darwin Core is illustrated by two recent examples. First, the University of California, Berkeley, and the Wildlife Conservation Society have collaborated to create Réseau de la Biodiversité de Madagascar (REBIOMA, http://www.rebioma.net/ ).The effort seeks to make biodiversity data about Madagascar available via a single web-based resource. Primary data on biodiversity in Madagascar come from researchers and institutions all over the world. REBIOMA works with each collection to standardize the data using the Darwin Core, to mobilize and aggregate the data, and to vet the data for quality, completeness, and fitness for use. Data passing automated quality checks and review by a board of taxonomic experts are analyzed in combination with environmental data to produce maps showing models of where species might occur. The success of this project has made it possible for researchers, policy makers, government officials, and conservationists to capture a wealth of data to address issues of Malagasy biodiversity. The simplicity and flexibility of Darwin Core has made it possible for REBIOMA to provide immediate access to high-quality data and tools for monitoring and assessing conservation efforts.”claim_relations[5]
complements MIxS genomic-data standard — “Currently, Darwin Core and GSC developers are collaborating (supported by NSF-RCN4GSC) to harmonize Darwin Core and MIxS to aid the growing field of sequence-based diversity research. Darwin Core and GSC developers have concluded that the standards are conceptually similar and that the distinct sets of terms are complementary. This allows the development of a bi-directional (see Figure 2 ) solution, where in the future the GSC will be able to incorporate terms from Darwin Core and add GSC-specific reporting requirements, while Darwin Core will be able to offer a genomics extension using the results of this activity.”claim_relations[6]
senseDarwin Core - sharing standard: common terms for biodiversity occurrence and environmental-association data — “Darwin Core [20] is a standard for sharing data about biodiversity – the occurrence of life on earth and its associations with the environment. Darwin Core first emerged around 1999 as a loosely defined set of terms, and progressed through several iterations by different groups resulting in many different variants [21] . A formal set of terms and processes to manage changes were necessary to ensure utility for data integration. These aspects were developed within the Darwin Core Task Group [22] of the Taxonomic Databases Working Group (TDWG; www.tdwg.org ) and ratified as a standard in October 2009. The philosophy for Darwin Core development has been to keep the standard as simple and open as possible and to develop terms only when there is shared demand. Darwin Core has a relatively long history of community development and is deployed widely [23] – [24] . For example, the Global Biodiversity Information Facility currently indexes approximately 300 million Darwin Core-formatted records published by more than 340 organizations in 43 countries. Increasingly, Darwin Core is being incorporated in communities beyond that of natural history collections ( Figure 1 ), in which the standard has its roots.”senses[0]
senseDarwin Core - semantic resource: a set of terms with human- and machine-interpretable meanings — “Fundamentally, Darwin Core is a set of terms having clearly defined semantics that can be understood by people or interpreted by machines, making it possible to determine appropriate uses of the data encoded therein. The terms are organized into nine categories (often referred to as “classes”, Figure 2 ), six of which cover broad aspects (event, location, geological context, occurrence, taxon, and identification) of the biodiversity domain. The remaining categories cover relationships to other resources, measurements, and generic information about records. Especially for the record level, Darwin Core recommends the use of a number of terms from Dublin Core (type, modified, language, rights, rightsHolder, accessRights, bibliographicCitation, references). The full set of current Darwin Core terms with their descriptions is available in the Quick Reference Guide ( http://rs.tdwg.org/dwc/terms/ ).”senses[1]
senseDarwin Core - living standard: a community process that adapts terms and relationships to new needs — “Darwin Core is a living standard. Although its roots were planted in the vertebrate natural history collections community, Darwin Core continues to grow to serve the needs of biodiversity research. This growth, over the relatively short period of a decade, speaks both to the need for such a standard and to the efforts of its champions to increase its utility through a community development process in order to meet increasing demand. Darwin Core greatly increases the value and re-use of freely available and accessible biodiversity data so that they can be effectively mobilized, integrated, and incorporated into other “grand challenge” scientific endeavors.”senses[2]
senseSimple Darwin Core - flat-record sense: nonrepeating properties in text or XML — “The Simple Darwin Core ( http://rs.tdwg.org/dwc/terms/simple/index.htm ) document explains the capacity to share records with properties that do not repeat, as simple text files or XML. There is also an XML Guide with reference XML schemas for highly structured data and a Text Guide explaining the construction of Darwin Core Archives (a combination of CSV files and a simple XML document describing the semantics of the data file columns and their relationships to each other). Darwin Core Archives can support structured data that conform to a star schema (a single core set of records in one or more files, with one-to-one or one-to-many relationships to records in other files). The Darwin Core Archive is becoming ever more popular as an easy means for data sharing, largely due to the release of supporting tools, in particular the next-generation data publishing system – the Integrated Publishing Toolkit ( http://www.gbif.org/informatics/infrastructure/publishing ) – an open source application developed by the Global Biodiversity Information Facility discussed in further detail below. Darwin Core Archives have been adopted by Pensoft® ( http://www.pensoft.net/journals/ ) as the preferred form for data appendices to taxonomic publications in MycoKeys, PhytoKeys, and ZooKeys.”senses[3]
senseDarwin Core Archive - star-schema sense: core records plus one-to-one or one-to-many extension records — “The Simple Darwin Core ( http://rs.tdwg.org/dwc/terms/simple/index.htm ) document explains the capacity to share records with properties that do not repeat, as simple text files or XML. There is also an XML Guide with reference XML schemas for highly structured data and a Text Guide explaining the construction of Darwin Core Archives (a combination of CSV files and a simple XML document describing the semantics of the data file columns and their relationships to each other). Darwin Core Archives can support structured data that conform to a star schema (a single core set of records in one or more files, with one-to-one or one-to-many relationships to records in other files). The Darwin Core Archive is becoming ever more popular as an easy means for data sharing, largely due to the release of supporting tools, in particular the next-generation data publishing system – the Integrated Publishing Toolkit ( http://www.gbif.org/informatics/infrastructure/publishing ) – an open source application developed by the Global Biodiversity Information Facility discussed in further detail below. Darwin Core Archives have been adopted by Pensoft® ( http://www.pensoft.net/journals/ ) as the preferred form for data appendices to taxonomic publications in MycoKeys, PhytoKeys, and ZooKeys.”senses[4]
senseconstraint - recommendation sense: guidance whose enforcement belongs to applications — “Darwin Core makes recommendations about constraints on data content, whether about data types, valid values, or controlled vocabularies. For example, decimalLatitude is recommended to be a floating-point number falling between 90 and −90, inclusive; countryCode is recommended to be a value from ISO 3166-1-alpha-2 (two-letter country codes). Though these recommendations are made in the standard, the philosophy is to relegate enforcement to applications where they make sense. For example, in a collaboration where the purpose is to automate data quality improvement on shared data, it is essential to be able to share the warts-and-all data that need to be investigated and improved.”senses[5]
senseextension - specialist sense: complementary terms or use guidance for a biodiversity sub-domain — “Because Darwin Core aims to cover the common ground in biodiversity, it inevitably lacks terms that are of interest to more specialized groups. A Darwin Core Extension consists of additional terms describing a complementary, related domain, or guidance on the use of Darwin Core within a specific sub-domain of biodiversity. Over the last decade, Darwin Core has evolved by means of extensions, some of which have been incorporated in the standard. For example, the terms of a paleontology extension related to an earlier, pre-standard version of Darwin Core became the terms of the current GeologicalContext class. Similarly, terms originating from an early version of the Darwin Core created for the Ocean Biogeographic Information System (OBIS; http://www.iobis.org/ ) have also been added to Darwin Core. Going forward, specific projects or disciplines may find it convenient to extend the scope of Darwin Core outside the existing namespace and governance process for proof-of-concept research. Once the understanding of the new terms has been tested and proven of utility in a broader context, incorporation into the standard can be accomplished through community consensus.”senses[6]
sensedata quality - fitness-for-use sense: contextual suitability assessed across heterogeneous sources — “Data quality and fitness for use are primary concerns in the biodiversity community [42] , where information comes from heterogeneous sources spanning the globe over hundreds of years. Both data discovery and data quality assessment are hampered by this heterogeneity. Part of the solution depends on the use of common vocabularies, part on dictionaries of synonymous terms, and a great deal on applications that can facilitate discovery and assessment in place of or to aid in otherwise labor-intensive “cleanups”. For example, having a dictionary that equates “voucher” and “sample” with an accepted term “PreservedSpecimen” would allow applications to make this substitution automatically and allow users to discover relevant data using any of the synonyms regardless of how they were stored in the original data.”senses[7]
noteDublin Core Metadata Initiative — Darwin Core inherits mission, operating principles, terms, and governance ideas from Dublin Core. — “Though the scope and governance of Darwin Core are distinct from Dublin Core [26] , readers will recognize the ancestry of Darwin Core in their shared traits: mission, principles of operation, and inherited terms. Indeed, if words were nucleotides, the Darwin Core mission is the same as that of Dublin Core except for one base-pair addition (in bold), namely, “to provide simple standards to facilitate the finding, sharing and management of biodiversity information.” This relationship is not accidental. The Dublin Core Metadata Initiative (DCMI) has done a very good job of maintaining the metadata specifications at the core of web-based resources. The success of DCMI encouraged TDWG to adopt similar policies for the specific domain of biodiversity through the Darwin Core. This process, in turn, acts as the basis for the development of data standards for even more specific sub-disciplines (e.g., plant genetic resources) as well as a basis for collaboration with complementary related domains (e.g., metagenomics).”claim_relations[0]
weightDublin Core Metadata Initiative — 0.95 — “Though the scope and governance of Darwin Core are distinct from Dublin Core [26] , readers will recognize the ancestry of Darwin Core in their shared traits: mission, principles of operation, and inherited terms. Indeed, if words were nucleotides, the Darwin Core mission is the same as that of Dublin Core except for one base-pair addition (in bold), namely, “to provide simple standards to facilitate the finding, sharing and management of biodiversity information.” This relationship is not accidental. The Dublin Core Metadata Initiative (DCMI) has done a very good job of maintaining the metadata specifications at the core of web-based resources. The success of DCMI encouraged TDWG to adopt similar policies for the specific domain of biodiversity through the Darwin Core. This process, in turn, acts as the basis for the development of data standards for even more specific sub-disciplines (e.g., plant genetic resources) as well as a basis for collaboration with complementary related domains (e.g., metagenomics).”claim_relations[0]
noteAccess to Biological Collections Data — The paper explicitly contrasts Darwin Core's minimal flat approach with ABCD's highly structured model. — “Darwin Core was developed in parallel with efforts in Europe to establish a comprehensive model for biological collections information — Access to Biological Collections Data (ABCD) [39] . The philosophies of the two approaches were distinct, even if they both had the goal of promoting sharing of biodiversity information. Darwin Core was designed to be minimal (only terms shared in common throughout natural history collections) and flat (no relational structure), while ABCD was highly structured and sought to capture the wide variety of biodiversity data and their relationships. Both groups defined their data models in XML schemas. ABCD was ratified as a standard by TDWG in 2005. Darwin Core departed from defining the standard in XML schema and followed the DCMI model, incorporating the experience of the previous decade to establish a set of terms in wide use in practice for data sharing.”claim_relations[1]
weightAccess to Biological Collections Data — 0.95 — “Darwin Core was developed in parallel with efforts in Europe to establish a comprehensive model for biological collections information — Access to Biological Collections Data (ABCD) [39] . The philosophies of the two approaches were distinct, even if they both had the goal of promoting sharing of biodiversity information. Darwin Core was designed to be minimal (only terms shared in common throughout natural history collections) and flat (no relational structure), while ABCD was highly structured and sought to capture the wide variety of biodiversity data and their relationships. Both groups defined their data models in XML schemas. ABCD was ratified as a standard by TDWG in 2005. Darwin Core departed from defining the standard in XML schema and followed the DCMI model, incorporating the experience of the previous decade to establish a set of terms in wide use in practice for data sharing.”claim_relations[1]
notebiodiversity-data interoperability — Common definitions and a standardized view are presented as the basis for integration. — “Biodiversity data derive from myriad sources stored in various formats on many distinct hardware and software platforms. An essential step towards understanding global patterns of biodiversity is to provide a standardized view of these heterogeneous data sources to improve interoperability. Fundamental to this advance are definitions of common terms. This paper describes the evolution and development of Darwin Core, a data standard for publishing and integrating biodiversity information. We focus on the categories of terms that define the standard, differences between simple and relational Darwin Core, how the standard has been implemented, and the community processes that are essential for maintenance and growth of the standard. We present case-study extensions of the Darwin Core into new research communities, including metagenomics and genetic resources. We close by showing how Darwin Core records are integrated to create new knowledge products documenting species distributions and changes due to environmental perturbations.”claim_relations[2]
weightbiodiversity-data interoperability — 0.95 — “Biodiversity data derive from myriad sources stored in various formats on many distinct hardware and software platforms. An essential step towards understanding global patterns of biodiversity is to provide a standardized view of these heterogeneous data sources to improve interoperability. Fundamental to this advance are definitions of common terms. This paper describes the evolution and development of Darwin Core, a data standard for publishing and integrating biodiversity information. We focus on the categories of terms that define the standard, differences between simple and relational Darwin Core, how the standard has been implemented, and the community processes that are essential for maintenance and growth of the standard. We present case-study extensions of the Darwin Core into new research communities, including metagenomics and genetic resources. We close by showing how Darwin Core records are integrated to create new knowledge products documenting species distributions and changes due to environmental perturbations.”claim_relations[2]
noteDarwin Core beyond natural-history collections — A deployed germplasm extension carries the standard into genetic-resource research. — “Darwin Core continues to be integrated into new research communities. For example, the Nordic Genetic Resource Center (NordGen; http://www.nordgen.org ) and Bioversity International (formerly IPGRI) ( http://www.bioversityinternational.org ) have sought to take advantage of Darwin Core on behalf of the European plant genetic resources and genebank community and, at the same time, share rich discipline-specific genetic resource information. A careful review was made of Darwin Core and a set of additional terms that did not overlap or conflict with existing Darwin Core terms was proposed to meet the community's needs. The new terms, modeled directly from FAO/IPGRI Multi-Crop Passport Descriptors [45] (2001) and the proposed EPGRIS3 trait data standard for characterization and evaluation data [46] , were expressed and published openly in an XML schema for germplasm data (DwC-germplasm, http://code.google.com/p/darwincore-germplasm/ ) [47] , resulting in the first successfully deployed extension to the Darwin Core Standard.”claim_relations[3]
weightDarwin Core beyond natural-history collections — 0.95 — “Darwin Core continues to be integrated into new research communities. For example, the Nordic Genetic Resource Center (NordGen; http://www.nordgen.org ) and Bioversity International (formerly IPGRI) ( http://www.bioversityinternational.org ) have sought to take advantage of Darwin Core on behalf of the European plant genetic resources and genebank community and, at the same time, share rich discipline-specific genetic resource information. A careful review was made of Darwin Core and a set of additional terms that did not overlap or conflict with existing Darwin Core terms was proposed to meet the community's needs. The new terms, modeled directly from FAO/IPGRI Multi-Crop Passport Descriptors [45] (2001) and the proposed EPGRIS3 trait data standard for characterization and evaluation data [46] , were expressed and published openly in an XML schema for germplasm data (DwC-germplasm, http://code.google.com/p/darwincore-germplasm/ ) [47] , resulting in the first successfully deployed extension to the Darwin Core Standard.”claim_relations[3]
notesemantic-web use of Darwin Core — The missing formal ontology limits traversable links to semantically rich resources. — “Though the Darwin Core is defined in an RDF document, integration of biodiversity data in the semantic web is in its early stages. One of the major challenges for Darwin Core in the semantic web context is the lack of a well-defined ontology - a formal definition of relationships between terms in a defined domain. An ontology would define the relationships between concepts such as biological entities, the events that document where and when they occurred, and the processes through which they are identified as being representative of a taxonomic concept. Without rigorous relationships between concepts and the properties that define them, connections between biodiversity data and related semantically rich information, such as literature and genomes, are difficult to traverse. This creates obstacles to cross-disciplinary semantic inquiry, such as in the Linked Data distributed data community ( http://linkeddata.org/ ). Current research is trying to address this gap (see TaxonConcept Knowledge Base, http://www.taxonconcept.org/ and BiSciCol, http://biscicol.blogspot.com/ ), active discussions on various aspects of the challenge take place regularly on the Darwin Core public forum ( http://lists.tdwg.org/mailman/listinfo/tdwg-content ), and an RDF task group has been established within TDWG “to adapt TDWG vocabularies for use as RDF classes and properties and to integrate those resources with other well-known vocabularies and ontologies outside TDWG for use in describing biodiversity resources.” [43]”claim_relations[4]
weightsemantic-web use of Darwin Core — 0.95 — “Though the Darwin Core is defined in an RDF document, integration of biodiversity data in the semantic web is in its early stages. One of the major challenges for Darwin Core in the semantic web context is the lack of a well-defined ontology - a formal definition of relationships between terms in a defined domain. An ontology would define the relationships between concepts such as biological entities, the events that document where and when they occurred, and the processes through which they are identified as being representative of a taxonomic concept. Without rigorous relationships between concepts and the properties that define them, connections between biodiversity data and related semantically rich information, such as literature and genomes, are difficult to traverse. This creates obstacles to cross-disciplinary semantic inquiry, such as in the Linked Data distributed data community ( http://linkeddata.org/ ). Current research is trying to address this gap (see TaxonConcept Knowledge Base, http://www.taxonconcept.org/ and BiSciCol, http://biscicol.blogspot.com/ ), active discussions on various aspects of the challenge take place regularly on the Darwin Core public forum ( http://lists.tdwg.org/mailman/listinfo/tdwg-content ), and an RDF task group has been established within TDWG “to adapt TDWG vocabularies for use as RDF classes and properties and to integrate those resources with other well-known vocabularies and ontologies outside TDWG for use in describing biodiversity resources.” [43]”claim_relations[4]
noteDarwin Core's research and conservation utility — The REBIOMA case shows standardization leading to quality-controlled occurrence models and conservation access. — “Though predated by examples of the effective use of Darwin Core for distribution modeling, influence of natural area preservation, and estimates of climate change impact [53] , the utility of data shared using Darwin Core is illustrated by two recent examples. First, the University of California, Berkeley, and the Wildlife Conservation Society have collaborated to create Réseau de la Biodiversité de Madagascar (REBIOMA, http://www.rebioma.net/ ).The effort seeks to make biodiversity data about Madagascar available via a single web-based resource. Primary data on biodiversity in Madagascar come from researchers and institutions all over the world. REBIOMA works with each collection to standardize the data using the Darwin Core, to mobilize and aggregate the data, and to vet the data for quality, completeness, and fitness for use. Data passing automated quality checks and review by a board of taxonomic experts are analyzed in combination with environmental data to produce maps showing models of where species might occur. The success of this project has made it possible for researchers, policy makers, government officials, and conservationists to capture a wealth of data to address issues of Malagasy biodiversity. The simplicity and flexibility of Darwin Core has made it possible for REBIOMA to provide immediate access to high-quality data and tools for monitoring and assessing conservation efforts.”claim_relations[5]
weightDarwin Core's research and conservation utility — 0.95 — “Though predated by examples of the effective use of Darwin Core for distribution modeling, influence of natural area preservation, and estimates of climate change impact [53] , the utility of data shared using Darwin Core is illustrated by two recent examples. First, the University of California, Berkeley, and the Wildlife Conservation Society have collaborated to create Réseau de la Biodiversité de Madagascar (REBIOMA, http://www.rebioma.net/ ).The effort seeks to make biodiversity data about Madagascar available via a single web-based resource. Primary data on biodiversity in Madagascar come from researchers and institutions all over the world. REBIOMA works with each collection to standardize the data using the Darwin Core, to mobilize and aggregate the data, and to vet the data for quality, completeness, and fitness for use. Data passing automated quality checks and review by a board of taxonomic experts are analyzed in combination with environmental data to produce maps showing models of where species might occur. The success of this project has made it possible for researchers, policy makers, government officials, and conservationists to capture a wealth of data to address issues of Malagasy biodiversity. The simplicity and flexibility of Darwin Core has made it possible for REBIOMA to provide immediate access to high-quality data and tools for monitoring and assessing conservation efforts.”claim_relations[5]
noteMIxS genomic-data standard — The communities concluded that the standards have distinct, complementary term sets. — “Currently, Darwin Core and GSC developers are collaborating (supported by NSF-RCN4GSC) to harmonize Darwin Core and MIxS to aid the growing field of sequence-based diversity research. Darwin Core and GSC developers have concluded that the standards are conceptually similar and that the distinct sets of terms are complementary. This allows the development of a bi-directional (see Figure 2 ) solution, where in the future the GSC will be able to incorporate terms from Darwin Core and add GSC-specific reporting requirements, while Darwin Core will be able to offer a genomics extension using the results of this activity.”claim_relations[6]
weightMIxS genomic-data standard — 0.95 — “Currently, Darwin Core and GSC developers are collaborating (supported by NSF-RCN4GSC) to harmonize Darwin Core and MIxS to aid the growing field of sequence-based diversity research. Darwin Core and GSC developers have concluded that the standards are conceptually similar and that the distinct sets of terms are complementary. This allows the development of a bi-directional (see Figure 2 ) solution, where in the future the GSC will be able to incorporate terms from Darwin Core and add GSC-specific reporting requirements, while Darwin Core will be able to offer a genomics extension using the results of this activity.”claim_relations[6]
noteDarwin Core —is-a→ standard for sharing data about biodiversity — Categorical class relation. — “Darwin Core [20] is a standard for sharing data about biodiversity – the occurrence of life on earth and its associations with the environment. Darwin Core first emerged around 1999 as a loosely defined set of terms, and progressed through several iterations by different groups resulting in many different variants [21] . A formal set of terms and processes to manage changes were necessary to ensure utility for data integration. These aspects were developed within the Darwin Core Task Group [22] of the Taxonomic Databases Working Group (TDWG; www.tdwg.org ) and ratified as a standard in October 2009. The philosophy for Darwin Core development has been to keep the standard as simple and open as possible and to develop terms only when there is shared demand. Darwin Core has a relatively long history of community development and is deployed widely [23] – [24] . For example, the Global Biodiversity Information Facility currently indexes approximately 300 million Darwin Core-formatted records published by more than 340 organizations in 43 countries. Increasingly, Darwin Core is being incorporated in communities beyond that of natural history collections ( Figure 1 ), in which the standard has its roots.”concept_edges[0]
relationDarwin Core —is-a→ standard for sharing data about biodiversity — Darwin Core is explicitly defined as a standard for sharing biodiversity data. — “Darwin Core [20] is a standard for sharing data about biodiversity – the occurrence of life on earth and its associations with the environment. Darwin Core first emerged around 1999 as a loosely defined set of terms, and progressed through several iterations by different groups resulting in many different variants [21] . A formal set of terms and processes to manage changes were necessary to ensure utility for data integration. These aspects were developed within the Darwin Core Task Group [22] of the Taxonomic Databases Working Group (TDWG; www.tdwg.org ) and ratified as a standard in October 2009. The philosophy for Darwin Core development has been to keep the standard as simple and open as possible and to develop terms only when there is shared demand. Darwin Core has a relatively long history of community development and is deployed widely [23] – [24] . For example, the Global Biodiversity Information Facility currently indexes approximately 300 million Darwin Core-formatted records published by more than 340 organizations in 43 countries. Increasingly, Darwin Core is being incorporated in communities beyond that of natural history collections ( Figure 1 ), in which the standard has its roots.”concept_edges[0]
noteDarwin Core —is-a→ set of terms — Categorical class relation. — “Fundamentally, Darwin Core is a set of terms having clearly defined semantics that can be understood by people or interpreted by machines, making it possible to determine appropriate uses of the data encoded therein. The terms are organized into nine categories (often referred to as “classes”, Figure 2 ), six of which cover broad aspects (event, location, geological context, occurrence, taxon, and identification) of the biodiversity domain. The remaining categories cover relationships to other resources, measurements, and generic information about records. Especially for the record level, Darwin Core recommends the use of a number of terms from Dublin Core (type, modified, language, rights, rightsHolder, accessRights, bibliographicCitation, references). The full set of current Darwin Core terms with their descriptions is available in the Quick Reference Guide ( http://rs.tdwg.org/dwc/terms/ ).”concept_edges[1]
relationDarwin Core —is-a→ set of terms — Darwin Core is explicitly defined as a set of semantically defined terms. — “Fundamentally, Darwin Core is a set of terms having clearly defined semantics that can be understood by people or interpreted by machines, making it possible to determine appropriate uses of the data encoded therein. The terms are organized into nine categories (often referred to as “classes”, Figure 2 ), six of which cover broad aspects (event, location, geological context, occurrence, taxon, and identification) of the biodiversity domain. The remaining categories cover relationships to other resources, measurements, and generic information about records. Especially for the record level, Darwin Core recommends the use of a number of terms from Dublin Core (type, modified, language, rights, rightsHolder, accessRights, bibliographicCitation, references). The full set of current Darwin Core terms with their descriptions is available in the Quick Reference Guide ( http://rs.tdwg.org/dwc/terms/ ).”concept_edges[1]
noteResource Description Framework —is-a→ standard for encoding the semantic structure of web-based resources — Categorical class relation. — “The authoritative form of the Darwin Core is a downloadable archive [25] , which contains various documents that are also available via web pages ( http://rs.tdwg.org/dwc/ ). Key among the documents is http://rs.tdwg.org/dwc/rdf/dwctermshistory.rdf . This document includes descriptions of all terms, their histories, the relationships among them, and the relations between them and terms from other standards, all in a single file. The document is written in the Resource Description Framework (RDF) format, which is a standard for encoding the semantic structure of web-based resources. The same information is rendered in human-readable form on web pages (Quick Reference Guide, Type Vocabulary, Complete History, Mapping to ABCD, and Mapping to Old Versions). The standard also includes recommendations for implementation ( Introduction , Simple Darwin Core, XML Guide, and Text Guide), a document describing how the standard is to be maintained (Namespace Policy), and a document describing the rationale behind any changes that are made to the standard (Decision History). In addition to the authoritative standard, Darwin Core consists of non-normative documents, commentaries, and tools tracked separately ( http://code.google.com/p/darwincore/ ).”concept_edges[2]
relationResource Description Framework —is-a→ standard for encoding the semantic structure of web-based resources — RDF is explicitly described as a standard for encoding semantic structure. — “The authoritative form of the Darwin Core is a downloadable archive [25] , which contains various documents that are also available via web pages ( http://rs.tdwg.org/dwc/ ). Key among the documents is http://rs.tdwg.org/dwc/rdf/dwctermshistory.rdf . This document includes descriptions of all terms, their histories, the relationships among them, and the relations between them and terms from other standards, all in a single file. The document is written in the Resource Description Framework (RDF) format, which is a standard for encoding the semantic structure of web-based resources. The same information is rendered in human-readable form on web pages (Quick Reference Guide, Type Vocabulary, Complete History, Mapping to ABCD, and Mapping to Old Versions). The standard also includes recommendations for implementation ( Introduction , Simple Darwin Core, XML Guide, and Text Guide), a document describing how the standard is to be maintained (Namespace Policy), and a document describing the rationale behind any changes that are made to the standard (Decision History). In addition to the authoritative standard, Darwin Core consists of non-normative documents, commentaries, and tools tracked separately ( http://code.google.com/p/darwincore/ ).”concept_edges[2]
noteIntegrated Publishing Toolkit —is-a→ open-source software development project — Categorical class relation. — “The Integrated Publishing Toolkit (IPT; http://www.gbif.org/informatics/infrastructure/publishing/ ) is an open-source software development project, led by GBIF, designed to address the challenges of sharing biodiversity data. By producing and providing easy access to Darwin Core Archives and resource metadata in Ecological Markup Language [44] , the IPT works in tandem with a Global Biodiversity Resources Discovery System (GBRDS), a data registry, to facilitate discovery and retrieval of shared data throughout the world. The IPT complements other tools that have been created to assist data users to explore, organize, and mobilize data sets. A range of spreadsheet and archive creators and validators has been developed by GBIF and others. These tools can be accessed via the GBIF Publishing Software web page ( http://www.gbif.org/informatics/standards-and-tools/publishing-data/publishing-software/ ).”concept_edges[3]
relationIntegrated Publishing Toolkit —is-a→ open-source software development project — The IPT is explicitly described as an open-source software development project. — “The Integrated Publishing Toolkit (IPT; http://www.gbif.org/informatics/infrastructure/publishing/ ) is an open-source software development project, led by GBIF, designed to address the challenges of sharing biodiversity data. By producing and providing easy access to Darwin Core Archives and resource metadata in Ecological Markup Language [44] , the IPT works in tandem with a Global Biodiversity Resources Discovery System (GBRDS), a data registry, to facilitate discovery and retrieval of shared data throughout the world. The IPT complements other tools that have been created to assist data users to explore, organize, and mobilize data sets. A range of spreadsheet and archive creators and validators has been developed by GBIF and others. These tools can be accessed via the GBIF Publishing Software web page ( http://www.gbif.org/informatics/standards-and-tools/publishing-data/publishing-software/ ).”concept_edges[3]
noteseven categories of terms —part-of→ Simple Darwin Core — Categorical containment relation. — “Darwin Core Categories: Simple Darwin Core is comprised of seven categories of terms (green). This subset of Darwin Core terms represents descriptive data about organisms that can be represented in one file with one row per record and one column per term. Two additional categories (orange) expand Darwin Core with concepts that require a more complex data structure, such as multiple measurements from a single specimen, and cannot be represented easily in Simple Darwin Core.”concept_edges[4]
relationseven categories of terms —part-of→ Simple Darwin Core — Simple Darwin Core is explicitly comprised of these seven categories. — “Darwin Core Categories: Simple Darwin Core is comprised of seven categories of terms (green). This subset of Darwin Core terms represents descriptive data about organisms that can be represented in one file with one row per record and one column per term. Two additional categories (orange) expand Darwin Core with concepts that require a more complex data structure, such as multiple measurements from a single specimen, and cannot be represented easily in Simple Darwin Core.”concept_edges[4]
auditDarwin Core —distinct-from→ Dublin Core — Audit 2026-09-28: DOUBTFUL - read against its full span and kept, but the span says the SCOPE and governance are distinct while stressing shared ancestry; distinct-from is loose. — “Though the scope and governance of Darwin Core are distinct from Dublin Core [26] , readers will recognize the ancestry of Darwin Core in their shared traits: mission, principles of operation, and inherited terms. Indeed, if words were nucleotides, the Darwin Core mission is the same as that of Dublin Core except for one base-pair addition (in bold), namely, “to provide simple standards to facilitate the finding, sharing and management of biodiversity information.” This relationship is not accidental. The Dublin Core Metadata Initiative (DCMI) has done a very good job of maintaining the metadata specifications at the core of web-based resources. The success of DCMI encouraged TDWG to adopt similar policies for the specific domain of biodiversity through the Darwin Core. This process, in turn, acts as the basis for the development of data standards for even more specific sub-disciplines (e.g., plant genetic resources) as well as a basis for collaboration with complementary related domains (e.g., metagenomics).”concept_edges[5]
noteDarwin Core —distinct-from→ Dublin Core — Flat distinction statement. — “Though the scope and governance of Darwin Core are distinct from Dublin Core [26] , readers will recognize the ancestry of Darwin Core in their shared traits: mission, principles of operation, and inherited terms. Indeed, if words were nucleotides, the Darwin Core mission is the same as that of Dublin Core except for one base-pair addition (in bold), namely, “to provide simple standards to facilitate the finding, sharing and management of biodiversity information.” This relationship is not accidental. The Dublin Core Metadata Initiative (DCMI) has done a very good job of maintaining the metadata specifications at the core of web-based resources. The success of DCMI encouraged TDWG to adopt similar policies for the specific domain of biodiversity through the Darwin Core. This process, in turn, acts as the basis for the development of data standards for even more specific sub-disciplines (e.g., plant genetic resources) as well as a basis for collaboration with complementary related domains (e.g., metagenomics).”concept_edges[5]
relationDarwin Core —distinct-from→ Dublin Core — Their scope and governance are explicitly distinct despite shared ancestry. — “Though the scope and governance of Darwin Core are distinct from Dublin Core [26] , readers will recognize the ancestry of Darwin Core in their shared traits: mission, principles of operation, and inherited terms. Indeed, if words were nucleotides, the Darwin Core mission is the same as that of Dublin Core except for one base-pair addition (in bold), namely, “to provide simple standards to facilitate the finding, sharing and management of biodiversity information.” This relationship is not accidental. The Dublin Core Metadata Initiative (DCMI) has done a very good job of maintaining the metadata specifications at the core of web-based resources. The success of DCMI encouraged TDWG to adopt similar policies for the specific domain of biodiversity through the Darwin Core. This process, in turn, acts as the basis for the development of data standards for even more specific sub-disciplines (e.g., plant genetic resources) as well as a basis for collaboration with complementary related domains (e.g., metagenomics).”concept_edges[5]
weightDarwin Core —distinct-from→ Dublin Core — 0.95 — “Though the scope and governance of Darwin Core are distinct from Dublin Core [26] , readers will recognize the ancestry of Darwin Core in their shared traits: mission, principles of operation, and inherited terms. Indeed, if words were nucleotides, the Darwin Core mission is the same as that of Dublin Core except for one base-pair addition (in bold), namely, “to provide simple standards to facilitate the finding, sharing and management of biodiversity information.” This relationship is not accidental. The Dublin Core Metadata Initiative (DCMI) has done a very good job of maintaining the metadata specifications at the core of web-based resources. The success of DCMI encouraged TDWG to adopt similar policies for the specific domain of biodiversity through the Darwin Core. This process, in turn, acts as the basis for the development of data standards for even more specific sub-disciplines (e.g., plant genetic resources) as well as a basis for collaboration with complementary related domains (e.g., metagenomics).”concept_edges[5]
noteDarwin Core —contrasted-with→ earlier guidelines — Flat explicit contrast. — “The initial purpose of the Darwin Core was to facilitate the exchange of information about the geographic and temporal occurrence of organisms in the natural world and the physical existence of specimens in biological collections. In contrast to earlier guidelines, Darwin Core was not a prescription for how to manage collection information. Instead, it was designed to circumscribe a conceptual model for a research community aiming to create a loose federation of databases and advance its research capabilities through data integration. The barriers to publishing data in Darwin Core were purposefully kept as low as possible.”concept_edges[6]
relationDarwin Core —contrasted-with→ earlier guidelines — The paper explicitly contrasts Darwin Core's integration aim with earlier management prescriptions. — “The initial purpose of the Darwin Core was to facilitate the exchange of information about the geographic and temporal occurrence of organisms in the natural world and the physical existence of specimens in biological collections. In contrast to earlier guidelines, Darwin Core was not a prescription for how to manage collection information. Instead, it was designed to circumscribe a conceptual model for a research community aiming to create a loose federation of databases and advance its research capabilities through data integration. The barriers to publishing data in Darwin Core were purposefully kept as low as possible.”concept_edges[6]
weightDarwin Core —contrasted-with→ earlier guidelines — 0.95 — “The initial purpose of the Darwin Core was to facilitate the exchange of information about the geographic and temporal occurrence of organisms in the natural world and the physical existence of specimens in biological collections. In contrast to earlier guidelines, Darwin Core was not a prescription for how to manage collection information. Instead, it was designed to circumscribe a conceptual model for a research community aiming to create a loose federation of databases and advance its research capabilities through data integration. The barriers to publishing data in Darwin Core were purposefully kept as low as possible.”concept_edges[6]
noteDarwin Core —contrasted-with→ ABCD — Flat explicit contrast. — “Darwin Core was developed in parallel with efforts in Europe to establish a comprehensive model for biological collections information — Access to Biological Collections Data (ABCD) [39] . The philosophies of the two approaches were distinct, even if they both had the goal of promoting sharing of biodiversity information. Darwin Core was designed to be minimal (only terms shared in common throughout natural history collections) and flat (no relational structure), while ABCD was highly structured and sought to capture the wide variety of biodiversity data and their relationships. Both groups defined their data models in XML schemas. ABCD was ratified as a standard by TDWG in 2005. Darwin Core departed from defining the standard in XML schema and followed the DCMI model, incorporating the experience of the previous decade to establish a set of terms in wide use in practice for data sharing.”concept_edges[7]
relationDarwin Core —contrasted-with→ ABCD — The paper contrasts minimal flat Darwin Core with highly structured ABCD. — “Darwin Core was developed in parallel with efforts in Europe to establish a comprehensive model for biological collections information — Access to Biological Collections Data (ABCD) [39] . The philosophies of the two approaches were distinct, even if they both had the goal of promoting sharing of biodiversity information. Darwin Core was designed to be minimal (only terms shared in common throughout natural history collections) and flat (no relational structure), while ABCD was highly structured and sought to capture the wide variety of biodiversity data and their relationships. Both groups defined their data models in XML schemas. ABCD was ratified as a standard by TDWG in 2005. Darwin Core departed from defining the standard in XML schema and followed the DCMI model, incorporating the experience of the previous decade to establish a set of terms in wide use in practice for data sharing.”concept_edges[7]
weightDarwin Core —contrasted-with→ ABCD — 0.95 — “Darwin Core was developed in parallel with efforts in Europe to establish a comprehensive model for biological collections information — Access to Biological Collections Data (ABCD) [39] . The philosophies of the two approaches were distinct, even if they both had the goal of promoting sharing of biodiversity information. Darwin Core was designed to be minimal (only terms shared in common throughout natural history collections) and flat (no relational structure), while ABCD was highly structured and sought to capture the wide variety of biodiversity data and their relationships. Both groups defined their data models in XML schemas. ABCD was ratified as a standard by TDWG in 2005. Darwin Core departed from defining the standard in XML schema and followed the DCMI model, incorporating the experience of the previous decade to establish a set of terms in wide use in practice for data sharing.”concept_edges[7]
noteMIxS —distinct-from→ Darwin Core — Flat difference statement. — “In collaboration with the Genomic Standards Consortium (GSC; http://gensc.org/ ) [51] , Darwin Core is now being extended to cover DNA-level observations (genomes, metagenomes, and gene marker sequences). The GSC, a standards body similar in scope to Biodiversity Information Standards (TDWG), is working to “standardize the description of genomic data and promote the exchange and integration of genomic data. [52] .” Advances in technology have made sequence-based diversity assessments increasingly routine in biodiversity research. The GSC has developed the MIxS (Minimum Information about any (x) Sequence) standard containing checklists for describing genomes, metagenomes, and marker gene studies. Conceptually this approach is similar to Darwin Core in that it defines terms for the description of data, but differs in that it requires the reporting a certain minimum set of descriptors such as environmental and geographic origin and details about sample and sequencing processing in addition to any kind of genomic sequence.”concept_edges[8]
relationMIxS —distinct-from→ Darwin Core — MIxS explicitly differs by requiring a minimum descriptor set. — “In collaboration with the Genomic Standards Consortium (GSC; http://gensc.org/ ) [51] , Darwin Core is now being extended to cover DNA-level observations (genomes, metagenomes, and gene marker sequences). The GSC, a standards body similar in scope to Biodiversity Information Standards (TDWG), is working to “standardize the description of genomic data and promote the exchange and integration of genomic data. [52] .” Advances in technology have made sequence-based diversity assessments increasingly routine in biodiversity research. The GSC has developed the MIxS (Minimum Information about any (x) Sequence) standard containing checklists for describing genomes, metagenomes, and marker gene studies. Conceptually this approach is similar to Darwin Core in that it defines terms for the description of data, but differs in that it requires the reporting a certain minimum set of descriptors such as environmental and geographic origin and details about sample and sequencing processing in addition to any kind of genomic sequence.”concept_edges[8]
weightMIxS —distinct-from→ Darwin Core — 0.95 — “In collaboration with the Genomic Standards Consortium (GSC; http://gensc.org/ ) [51] , Darwin Core is now being extended to cover DNA-level observations (genomes, metagenomes, and gene marker sequences). The GSC, a standards body similar in scope to Biodiversity Information Standards (TDWG), is working to “standardize the description of genomic data and promote the exchange and integration of genomic data. [52] .” Advances in technology have made sequence-based diversity assessments increasingly routine in biodiversity research. The GSC has developed the MIxS (Minimum Information about any (x) Sequence) standard containing checklists for describing genomes, metagenomes, and marker gene studies. Conceptually this approach is similar to Darwin Core in that it defines terms for the description of data, but differs in that it requires the reporting a certain minimum set of descriptors such as environmental and geographic origin and details about sample and sequencing processing in addition to any kind of genomic sequence.”concept_edges[8]
auditsimple definitions of terms —distinct-from→ technical implementation — Audit 2026-09-28: DOUBTFUL - read against its full span and kept, but the span says the value lies in definitions INDEPENDENT of implementation; distinct-from is loose. — “TDWG, as with other information standards bodies, has a history of developing data sharing standards that are bound to specific technologies, such as eXtensible Markup Language (XML). While Darwin Core is currently maintained in RDF, the enduring value of the standard lies in simple definitions of terms and their relationships to other terms, independent of technical implementation. As with Dublin Core, the idea is to promote use of the common terms in every appropriate context, and to leave the implementation details to specific applications. Data can be shared using Darwin Core in a variety of encoding schemes (Comma Separated Values, XML, JavaScript Object Notation, RDF, etc.). To aid in using Darwin Core in different contexts, there are documents with recommendations on how to share information as Darwin Core using various technologies.”concept_edges[9]
notesimple definitions of terms —distinct-from→ technical implementation — Flat independence statement. — “TDWG, as with other information standards bodies, has a history of developing data sharing standards that are bound to specific technologies, such as eXtensible Markup Language (XML). While Darwin Core is currently maintained in RDF, the enduring value of the standard lies in simple definitions of terms and their relationships to other terms, independent of technical implementation. As with Dublin Core, the idea is to promote use of the common terms in every appropriate context, and to leave the implementation details to specific applications. Data can be shared using Darwin Core in a variety of encoding schemes (Comma Separated Values, XML, JavaScript Object Notation, RDF, etc.). To aid in using Darwin Core in different contexts, there are documents with recommendations on how to share information as Darwin Core using various technologies.”concept_edges[9]
relationsimple definitions of terms —distinct-from→ technical implementation — Enduring semantic definitions are stated to be independent of implementation technology. — “TDWG, as with other information standards bodies, has a history of developing data sharing standards that are bound to specific technologies, such as eXtensible Markup Language (XML). While Darwin Core is currently maintained in RDF, the enduring value of the standard lies in simple definitions of terms and their relationships to other terms, independent of technical implementation. As with Dublin Core, the idea is to promote use of the common terms in every appropriate context, and to leave the implementation details to specific applications. Data can be shared using Darwin Core in a variety of encoding schemes (Comma Separated Values, XML, JavaScript Object Notation, RDF, etc.). To aid in using Darwin Core in different contexts, there are documents with recommendations on how to share information as Darwin Core using various technologies.”concept_edges[9]
weightsimple definitions of terms —distinct-from→ technical implementation — 0.95 — “TDWG, as with other information standards bodies, has a history of developing data sharing standards that are bound to specific technologies, such as eXtensible Markup Language (XML). While Darwin Core is currently maintained in RDF, the enduring value of the standard lies in simple definitions of terms and their relationships to other terms, independent of technical implementation. As with Dublin Core, the idea is to promote use of the common terms in every appropriate context, and to leave the implementation details to specific applications. Data can be shared using Darwin Core in a variety of encoding schemes (Comma Separated Values, XML, JavaScript Object Notation, RDF, etc.). To aid in using Darwin Core in different contexts, there are documents with recommendations on how to share information as Darwin Core using various technologies.”concept_edges[9]
noteDarwin Core —causes→ value and re-use — Flat causal assertion. — “Darwin Core is a living standard. Although its roots were planted in the vertebrate natural history collections community, Darwin Core continues to grow to serve the needs of biodiversity research. This growth, over the relatively short period of a decade, speaks both to the need for such a standard and to the efforts of its champions to increase its utility through a community development process in order to meet increasing demand. Darwin Core greatly increases the value and re-use of freely available and accessible biodiversity data so that they can be effectively mobilized, integrated, and incorporated into other “grand challenge” scientific endeavors.”concept_edges[11]
relationDarwin Core —causes→ value and re-use — The standard is stated to greatly increase data value and reuse. — “Darwin Core is a living standard. Although its roots were planted in the vertebrate natural history collections community, Darwin Core continues to grow to serve the needs of biodiversity research. This growth, over the relatively short period of a decade, speaks both to the need for such a standard and to the efforts of its champions to increase its utility through a community development process in order to meet increasing demand. Darwin Core greatly increases the value and re-use of freely available and accessible biodiversity data so that they can be effectively mobilized, integrated, and incorporated into other “grand challenge” scientific endeavors.”concept_edges[11]
weightDarwin Core —causes→ value and re-use — 0.9 — “Darwin Core is a living standard. Although its roots were planted in the vertebrate natural history collections community, Darwin Core continues to grow to serve the needs of biodiversity research. This growth, over the relatively short period of a decade, speaks both to the need for such a standard and to the efforts of its champions to increase its utility through a community development process in order to meet increasing demand. Darwin Core greatly increases the value and re-use of freely available and accessible biodiversity data so that they can be effectively mobilized, integrated, and incorporated into other “grand challenge” scientific endeavors.”concept_edges[11]
relationDarwin Core → metadata standards from other domains — Darwin Core is complementary to and reuses metadata standards from other domains. — “The primary purpose of Darwin Core is to create a common language for sharing biodiversity data that is complementary to and reuses metadata standards from other domains wherever possible. Creating this common language has been particularly challenging, since natural history data curation practices have been developed locally and organically over hundreds of years, have varied between disciplines as well as institutions, and have had limited culture of data sharing.”unhoused_relations[0]
weightDarwin Core → metadata standards from other domains — 0.95 — “The primary purpose of Darwin Core is to create a common language for sharing biodiversity data that is complementary to and reuses metadata standards from other domains wherever possible. Creating this common language has been particularly challenging, since natural history data curation practices have been developed locally and organically over hundreds of years, have varied between disciplines as well as institutions, and have had limited culture of data sharing.”unhoused_relations[0]
relationDarwin Core → natural history collections — Darwin Core has its historical roots in the natural-history collections community. — “Darwin Core [20] is a standard for sharing data about biodiversity – the occurrence of life on earth and its associations with the environment. Darwin Core first emerged around 1999 as a loosely defined set of terms, and progressed through several iterations by different groups resulting in many different variants [21] . A formal set of terms and processes to manage changes were necessary to ensure utility for data integration. These aspects were developed within the Darwin Core Task Group [22] of the Taxonomic Databases Working Group (TDWG; www.tdwg.org ) and ratified as a standard in October 2009. The philosophy for Darwin Core development has been to keep the standard as simple and open as possible and to develop terms only when there is shared demand. Darwin Core has a relatively long history of community development and is deployed widely [23] – [24] . For example, the Global Biodiversity Information Facility currently indexes approximately 300 million Darwin Core-formatted records published by more than 340 organizations in 43 countries. Increasingly, Darwin Core is being incorporated in communities beyond that of natural history collections ( Figure 1 ), in which the standard has its roots.”unhoused_relations[1]
weightDarwin Core → natural history collections — 0.98 — “Darwin Core [20] is a standard for sharing data about biodiversity – the occurrence of life on earth and its associations with the environment. Darwin Core first emerged around 1999 as a loosely defined set of terms, and progressed through several iterations by different groups resulting in many different variants [21] . A formal set of terms and processes to manage changes were necessary to ensure utility for data integration. These aspects were developed within the Darwin Core Task Group [22] of the Taxonomic Databases Working Group (TDWG; www.tdwg.org ) and ratified as a standard in October 2009. The philosophy for Darwin Core development has been to keep the standard as simple and open as possible and to develop terms only when there is shared demand. Darwin Core has a relatively long history of community development and is deployed widely [23] – [24] . For example, the Global Biodiversity Information Facility currently indexes approximately 300 million Darwin Core-formatted records published by more than 340 organizations in 43 countries. Increasingly, Darwin Core is being incorporated in communities beyond that of natural history collections ( Figure 1 ), in which the standard has its roots.”unhoused_relations[1]
relationDarwin Core → technical contexts — The standard must remain flexible across evolving technical contexts. — “In combination with openness and consensus building (key aspects of the TDWG constitution: http://www.tdwg.org/about-tdwg/constitution/ ), two of the guiding principles behind Darwin Core are flexibility and adaptability. The standard has to be flexible to accommodate a variety of ever evolving technical contexts in which it might be used (spreadsheet columns, relational database fields, XML schemas and documents, non-SQL data stores, and semantic web resources). The standard has to be adaptable to accommodate growth (new terms, additional meanings) and interoperability (connections to related information). To thrive, the standard must have a means to adapt to changing needs.”unhoused_relations[2]
weightDarwin Core → technical contexts — 0.95 — “In combination with openness and consensus building (key aspects of the TDWG constitution: http://www.tdwg.org/about-tdwg/constitution/ ), two of the guiding principles behind Darwin Core are flexibility and adaptability. The standard has to be flexible to accommodate a variety of ever evolving technical contexts in which it might be used (spreadsheet columns, relational database fields, XML schemas and documents, non-SQL data stores, and semantic web resources). The standard has to be adaptable to accommodate growth (new terms, additional meanings) and interoperability (connections to related information). To thrive, the standard must have a means to adapt to changing needs.”unhoused_relations[2]
relationDarwin Core → changing needs — The standard must adapt to changing needs through new terms, meanings, and connections. — “In combination with openness and consensus building (key aspects of the TDWG constitution: http://www.tdwg.org/about-tdwg/constitution/ ), two of the guiding principles behind Darwin Core are flexibility and adaptability. The standard has to be flexible to accommodate a variety of ever evolving technical contexts in which it might be used (spreadsheet columns, relational database fields, XML schemas and documents, non-SQL data stores, and semantic web resources). The standard has to be adaptable to accommodate growth (new terms, additional meanings) and interoperability (connections to related information). To thrive, the standard must have a means to adapt to changing needs.”unhoused_relations[3]
weightDarwin Core → changing needs — 0.95 — “In combination with openness and consensus building (key aspects of the TDWG constitution: http://www.tdwg.org/about-tdwg/constitution/ ), two of the guiding principles behind Darwin Core are flexibility and adaptability. The standard has to be flexible to accommodate a variety of ever evolving technical contexts in which it might be used (spreadsheet columns, relational database fields, XML schemas and documents, non-SQL data stores, and semantic web resources). The standard has to be adaptable to accommodate growth (new terms, additional meanings) and interoperability (connections to related information). To thrive, the standard must have a means to adapt to changing needs.”unhoused_relations[3]
relationcommon vocabularies and synonym dictionaries → data discovery and quality assessment — Shared vocabularies and synonym mappings are parts of the proposed solution to heterogeneous-data discovery and quality problems. — “Data quality and fitness for use are primary concerns in the biodiversity community [42] , where information comes from heterogeneous sources spanning the globe over hundreds of years. Both data discovery and data quality assessment are hampered by this heterogeneity. Part of the solution depends on the use of common vocabularies, part on dictionaries of synonymous terms, and a great deal on applications that can facilitate discovery and assessment in place of or to aid in otherwise labor-intensive “cleanups”. For example, having a dictionary that equates “voucher” and “sample” with an accepted term “PreservedSpecimen” would allow applications to make this substitution automatically and allow users to discover relevant data using any of the synonyms regardless of how they were stored in the original data.”unhoused_relations[4]
weightcommon vocabularies and synonym dictionaries → data discovery and quality assessment — 0.9 — “Data quality and fitness for use are primary concerns in the biodiversity community [42] , where information comes from heterogeneous sources spanning the globe over hundreds of years. Both data discovery and data quality assessment are hampered by this heterogeneity. Part of the solution depends on the use of common vocabularies, part on dictionaries of synonymous terms, and a great deal on applications that can facilitate discovery and assessment in place of or to aid in otherwise labor-intensive “cleanups”. For example, having a dictionary that equates “voucher” and “sample” with an accepted term “PreservedSpecimen” would allow applications to make this substitution automatically and allow users to discover relevant data using any of the synonyms regardless of how they were stored in the original data.”unhoused_relations[4]
relationDarwin Core constraints → applications — The standard recommends constraints but delegates enforcement to applications. — “Darwin Core makes recommendations about constraints on data content, whether about data types, valid values, or controlled vocabularies. For example, decimalLatitude is recommended to be a floating-point number falling between 90 and −90, inclusive; countryCode is recommended to be a value from ISO 3166-1-alpha-2 (two-letter country codes). Though these recommendations are made in the standard, the philosophy is to relegate enforcement to applications where they make sense. For example, in a collaboration where the purpose is to automate data quality improvement on shared data, it is essential to be able to share the warts-and-all data that need to be investigated and improved.”unhoused_relations[5]
weightDarwin Core constraints → applications — 0.98 — “Darwin Core makes recommendations about constraints on data content, whether about data types, valid values, or controlled vocabularies. For example, decimalLatitude is recommended to be a floating-point number falling between 90 and −90, inclusive; countryCode is recommended to be a value from ISO 3166-1-alpha-2 (two-letter country codes). Though these recommendations are made in the standard, the philosophy is to relegate enforcement to applications where they make sense. For example, in a collaboration where the purpose is to automate data quality improvement on shared data, it is essential to be able to share the warts-and-all data that need to be investigated and improved.”unhoused_relations[5]
relationIntegrated Publishing Toolkit → Global Biodiversity Resources Discovery System — The publishing toolkit works in tandem with the registry to support discovery and retrieval. — “The Integrated Publishing Toolkit (IPT; http://www.gbif.org/informatics/infrastructure/publishing/ ) is an open-source software development project, led by GBIF, designed to address the challenges of sharing biodiversity data. By producing and providing easy access to Darwin Core Archives and resource metadata in Ecological Markup Language [44] , the IPT works in tandem with a Global Biodiversity Resources Discovery System (GBRDS), a data registry, to facilitate discovery and retrieval of shared data throughout the world. The IPT complements other tools that have been created to assist data users to explore, organize, and mobilize data sets. A range of spreadsheet and archive creators and validators has been developed by GBIF and others. These tools can be accessed via the GBIF Publishing Software web page ( http://www.gbif.org/informatics/standards-and-tools/publishing-data/publishing-software/ ).”unhoused_relations[6]
weightIntegrated Publishing Toolkit → Global Biodiversity Resources Discovery System — 0.95 — “The Integrated Publishing Toolkit (IPT; http://www.gbif.org/informatics/infrastructure/publishing/ ) is an open-source software development project, led by GBIF, designed to address the challenges of sharing biodiversity data. By producing and providing easy access to Darwin Core Archives and resource metadata in Ecological Markup Language [44] , the IPT works in tandem with a Global Biodiversity Resources Discovery System (GBRDS), a data registry, to facilitate discovery and retrieval of shared data throughout the world. The IPT complements other tools that have been created to assist data users to explore, organize, and mobilize data sets. A range of spreadsheet and archive creators and validators has been developed by GBIF and others. These tools can be accessed via the GBIF Publishing Software web page ( http://www.gbif.org/informatics/standards-and-tools/publishing-data/publishing-software/ ).”unhoused_relations[6]
relationDarwin Core Extension → specialized groups — Extensions supply terms and guidance missing from the common-ground core for specialized groups. — “Because Darwin Core aims to cover the common ground in biodiversity, it inevitably lacks terms that are of interest to more specialized groups. A Darwin Core Extension consists of additional terms describing a complementary, related domain, or guidance on the use of Darwin Core within a specific sub-domain of biodiversity. Over the last decade, Darwin Core has evolved by means of extensions, some of which have been incorporated in the standard. For example, the terms of a paleontology extension related to an earlier, pre-standard version of Darwin Core became the terms of the current GeologicalContext class. Similarly, terms originating from an early version of the Darwin Core created for the Ocean Biogeographic Information System (OBIS; http://www.iobis.org/ ) have also been added to Darwin Core. Going forward, specific projects or disciplines may find it convenient to extend the scope of Darwin Core outside the existing namespace and governance process for proof-of-concept research. Once the understanding of the new terms has been tested and proven of utility in a broader context, incorporation into the standard can be accomplished through community consensus.”unhoused_relations[7]
weightDarwin Core Extension → specialized groups — 0.95 — “Because Darwin Core aims to cover the common ground in biodiversity, it inevitably lacks terms that are of interest to more specialized groups. A Darwin Core Extension consists of additional terms describing a complementary, related domain, or guidance on the use of Darwin Core within a specific sub-domain of biodiversity. Over the last decade, Darwin Core has evolved by means of extensions, some of which have been incorporated in the standard. For example, the terms of a paleontology extension related to an earlier, pre-standard version of Darwin Core became the terms of the current GeologicalContext class. Similarly, terms originating from an early version of the Darwin Core created for the Ocean Biogeographic Information System (OBIS; http://www.iobis.org/ ) have also been added to Darwin Core. Going forward, specific projects or disciplines may find it convenient to extend the scope of Darwin Core outside the existing namespace and governance process for proof-of-concept research. Once the understanding of the new terms has been tested and proven of utility in a broader context, incorporation into the standard can be accomplished through community consensus.”unhoused_relations[7]
relationDarwin Core → MIxS — The standards are conceptually similar and have complementary term sets. — “Currently, Darwin Core and GSC developers are collaborating (supported by NSF-RCN4GSC) to harmonize Darwin Core and MIxS to aid the growing field of sequence-based diversity research. Darwin Core and GSC developers have concluded that the standards are conceptually similar and that the distinct sets of terms are complementary. This allows the development of a bi-directional (see Figure 2 ) solution, where in the future the GSC will be able to incorporate terms from Darwin Core and add GSC-specific reporting requirements, while Darwin Core will be able to offer a genomics extension using the results of this activity.”unhoused_relations[8]
weightDarwin Core → MIxS — 0.95 — “Currently, Darwin Core and GSC developers are collaborating (supported by NSF-RCN4GSC) to harmonize Darwin Core and MIxS to aid the growing field of sequence-based diversity research. Darwin Core and GSC developers have concluded that the standards are conceptually similar and that the distinct sets of terms are complementary. This allows the development of a bi-directional (see Figure 2 ) solution, where in the future the GSC will be able to incorporate terms from Darwin Core and add GSC-specific reporting requirements, while Darwin Core will be able to offer a genomics extension using the results of this activity.”unhoused_relations[8]
relationDarwin Core records → new knowledge products — Integrated records support new products documenting distributions and environmental change. — “Biodiversity data derive from myriad sources stored in various formats on many distinct hardware and software platforms. An essential step towards understanding global patterns of biodiversity is to provide a standardized view of these heterogeneous data sources to improve interoperability. Fundamental to this advance are definitions of common terms. This paper describes the evolution and development of Darwin Core, a data standard for publishing and integrating biodiversity information. We focus on the categories of terms that define the standard, differences between simple and relational Darwin Core, how the standard has been implemented, and the community processes that are essential for maintenance and growth of the standard. We present case-study extensions of the Darwin Core into new research communities, including metagenomics and genetic resources. We close by showing how Darwin Core records are integrated to create new knowledge products documenting species distributions and changes due to environmental perturbations.”unhoused_relations[9]
weightDarwin Core records → new knowledge products — 0.95 — “Biodiversity data derive from myriad sources stored in various formats on many distinct hardware and software platforms. An essential step towards understanding global patterns of biodiversity is to provide a standardized view of these heterogeneous data sources to improve interoperability. Fundamental to this advance are definitions of common terms. This paper describes the evolution and development of Darwin Core, a data standard for publishing and integrating biodiversity information. We focus on the categories of terms that define the standard, differences between simple and relational Darwin Core, how the standard has been implemented, and the community processes that are essential for maintenance and growth of the standard. We present case-study extensions of the Darwin Core into new research communities, including metagenomics and genetic resources. We close by showing how Darwin Core records are integrated to create new knowledge products documenting species distributions and changes due to environmental perturbations.”unhoused_relations[9]
relationDarwin Core → grand challenge scientific endeavors — Mobilized and integrated Darwin Core data can be incorporated into broader scientific programs. — “Darwin Core is a living standard. Although its roots were planted in the vertebrate natural history collections community, Darwin Core continues to grow to serve the needs of biodiversity research. This growth, over the relatively short period of a decade, speaks both to the need for such a standard and to the efforts of its champions to increase its utility through a community development process in order to meet increasing demand. Darwin Core greatly increases the value and re-use of freely available and accessible biodiversity data so that they can be effectively mobilized, integrated, and incorporated into other “grand challenge” scientific endeavors.”unhoused_relations[10]
weightDarwin Core → grand challenge scientific endeavors — 0.95 — “Darwin Core is a living standard. Although its roots were planted in the vertebrate natural history collections community, Darwin Core continues to grow to serve the needs of biodiversity research. This growth, over the relatively short period of a decade, speaks both to the need for such a standard and to the efforts of its champions to increase its utility through a community development process in order to meet increasing demand. Darwin Core greatly increases the value and re-use of freely available and accessible biodiversity data so that they can be effectively mobilized, integrated, and incorporated into other “grand challenge” scientific endeavors.”unhoused_relations[10]
relationASC model → ontological description — The ASC model was an ontological description of the biological-collections domain. — “In the early 1990's, entity-relationship modeling had become accepted as a prerequisite for designing any database serving multiple users. A normalized database structure was the primary technique for enforcing data integrity. The Association of Systematic Collections (ASC) model [30] was the result of the first group effort to create a conceptual model for biological collections that accommodated the distinct taxonomic disciplines commonly found in natural history museums. The ASC model was an ontological description of the domain, but was determined at the time to be beyond the technical capabilities to implement [31] . Eventually, this model was then used as the point of departure for several collection management applications, including Specify ( http://specifysoftware.org/ ), Biota ( http://viceroy.eeb.uconn.edu/biota ), and Arctos ( http://arctos.database.museum/ ). The emphasis at that time was to develop best practice for data capture and management, not data exchange or integration.”unhoused_relations[11]
relationlack of a coordinated publishing and integration system → data repositories — Repositories tend to be isolated when coordinated systems and standards are absent. — “A general challenge of biodiversity data that is shared with many other information domains is the lack of a coordinated publishing and integration system; data repositories tend to be isolated from each other in the absence of standards for data and communication protocols. Heterogeneity in meaning and content of terms creates obstacles in every aspect of data integration and use, including discovery, comparison, and quality assessment. Information communities, especially Library Information Sciences, have a long history of meeting these challenges through the creation and maintenance of standards.”unhoused_relations[12]
weightlack of a coordinated publishing and integration system → data repositories — 0.85 — “A general challenge of biodiversity data that is shared with many other information domains is the lack of a coordinated publishing and integration system; data repositories tend to be isolated from each other in the absence of standards for data and communication protocols. Heterogeneity in meaning and content of terms creates obstacles in every aspect of data integration and use, including discovery, comparison, and quality assessment. Information communities, especially Library Information Sciences, have a long history of meeting these challenges through the creation and maintenance of standards.”unhoused_relations[12]
relationHeterogeneity in meaning and content of terms → obstacles in every aspect of data integration and use — Semantic heterogeneity creates obstacles to discovery, comparison, quality assessment, and integration. — “A general challenge of biodiversity data that is shared with many other information domains is the lack of a coordinated publishing and integration system; data repositories tend to be isolated from each other in the absence of standards for data and communication protocols. Heterogeneity in meaning and content of terms creates obstacles in every aspect of data integration and use, including discovery, comparison, and quality assessment. Information communities, especially Library Information Sciences, have a long history of meeting these challenges through the creation and maintenance of standards.”unhoused_relations[13]
weightHeterogeneity in meaning and content of terms → obstacles in every aspect of data integration and use — 0.9 — “A general challenge of biodiversity data that is shared with many other information domains is the lack of a coordinated publishing and integration system; data repositories tend to be isolated from each other in the absence of standards for data and communication protocols. Heterogeneity in meaning and content of terms creates obstacles in every aspect of data integration and use, including discovery, comparison, and quality assessment. Information communities, especially Library Information Sciences, have a long history of meeting these challenges through the creation and maintenance of standards.”unhoused_relations[13]
relationclearly defined semantics → human and machine interpretation — Defined semantics make human understanding and machine interpretation possible. — “Fundamentally, Darwin Core is a set of terms having clearly defined semantics that can be understood by people or interpreted by machines, making it possible to determine appropriate uses of the data encoded therein. The terms are organized into nine categories (often referred to as “classes”, Figure 2 ), six of which cover broad aspects (event, location, geological context, occurrence, taxon, and identification) of the biodiversity domain. The remaining categories cover relationships to other resources, measurements, and generic information about records. Especially for the record level, Darwin Core recommends the use of a number of terms from Dublin Core (type, modified, language, rights, rightsHolder, accessRights, bibliographicCitation, references). The full set of current Darwin Core terms with their descriptions is available in the Quick Reference Guide ( http://rs.tdwg.org/dwc/terms/ ).”unhoused_relations[14]
weightclearly defined semantics → human and machine interpretation — 0.9 — “Fundamentally, Darwin Core is a set of terms having clearly defined semantics that can be understood by people or interpreted by machines, making it possible to determine appropriate uses of the data encoded therein. The terms are organized into nine categories (often referred to as “classes”, Figure 2 ), six of which cover broad aspects (event, location, geological context, occurrence, taxon, and identification) of the biodiversity domain. The remaining categories cover relationships to other resources, measurements, and generic information about records. Especially for the record level, Darwin Core recommends the use of a number of terms from Dublin Core (type, modified, language, rights, rightsHolder, accessRights, bibliographicCitation, references). The full set of current Darwin Core terms with their descriptions is available in the Quick Reference Guide ( http://rs.tdwg.org/dwc/terms/ ).”unhoused_relations[14]
relationA variety of tools → creation and publication of Darwin Core Archives relatively simple — GBIF-supported tools are intended to make archive creation and publication simpler. — “A variety of tools has been developed to simplify the mobilization and sharing of biodiversity data using the Darwin Core. Many of these tools focus on the creation or validation of Darwin Core Archives ( http://code.google.com/p/darwincore/wiki/ToolsAndApplications#Tools ). The Global Biodiversity Information Facility (GBIF), an international organization promoting the free and open access to biodiversity data online, has invested heavily in the open and collaborative development of tools ( http://tools.gbif.org/ ) to make the creation and publication of Darwin Core Archives relatively simple.”unhoused_relations[15]
weightA variety of tools → creation and publication of Darwin Core Archives relatively simple — 0.9 — “A variety of tools has been developed to simplify the mobilization and sharing of biodiversity data using the Darwin Core. Many of these tools focus on the creation or validation of Darwin Core Archives ( http://code.google.com/p/darwincore/wiki/ToolsAndApplications#Tools ). The Global Biodiversity Information Facility (GBIF), an international organization promoting the free and open access to biodiversity data online, has invested heavily in the open and collaborative development of tools ( http://tools.gbif.org/ ) to make the creation and publication of Darwin Core Archives relatively simple.”unhoused_relations[15]
no type for thisDarwin Core → metadata standards from other domains — Darwin Core is complementary to and reuses metadata standards from other domains. — “The primary purpose of Darwin Core is to create a common language for sharing biodiversity data that is complementary to and reuses metadata standards from other domains wherever possible. Creating this common language has been particularly challenging, since natural history data curation practices have been developed locally and organically over hundreds of years, have varied between disciplines as well as institutions, and have had limited culture of data sharing.”unhoused_relations[0]
no type for thisDarwin Core → natural history collections — Darwin Core has its historical roots in the natural-history collections community. — “Darwin Core [20] is a standard for sharing data about biodiversity – the occurrence of life on earth and its associations with the environment. Darwin Core first emerged around 1999 as a loosely defined set of terms, and progressed through several iterations by different groups resulting in many different variants [21] . A formal set of terms and processes to manage changes were necessary to ensure utility for data integration. These aspects were developed within the Darwin Core Task Group [22] of the Taxonomic Databases Working Group (TDWG; www.tdwg.org ) and ratified as a standard in October 2009. The philosophy for Darwin Core development has been to keep the standard as simple and open as possible and to develop terms only when there is shared demand. Darwin Core has a relatively long history of community development and is deployed widely [23] – [24] . For example, the Global Biodiversity Information Facility currently indexes approximately 300 million Darwin Core-formatted records published by more than 340 organizations in 43 countries. Increasingly, Darwin Core is being incorporated in communities beyond that of natural history collections ( Figure 1 ), in which the standard has its roots.”unhoused_relations[1]
no type for thisDarwin Core → technical contexts — The standard must remain flexible across evolving technical contexts. — “In combination with openness and consensus building (key aspects of the TDWG constitution: http://www.tdwg.org/about-tdwg/constitution/ ), two of the guiding principles behind Darwin Core are flexibility and adaptability. The standard has to be flexible to accommodate a variety of ever evolving technical contexts in which it might be used (spreadsheet columns, relational database fields, XML schemas and documents, non-SQL data stores, and semantic web resources). The standard has to be adaptable to accommodate growth (new terms, additional meanings) and interoperability (connections to related information). To thrive, the standard must have a means to adapt to changing needs.”unhoused_relations[2]
no type for thisDarwin Core → changing needs — The standard must adapt to changing needs through new terms, meanings, and connections. — “In combination with openness and consensus building (key aspects of the TDWG constitution: http://www.tdwg.org/about-tdwg/constitution/ ), two of the guiding principles behind Darwin Core are flexibility and adaptability. The standard has to be flexible to accommodate a variety of ever evolving technical contexts in which it might be used (spreadsheet columns, relational database fields, XML schemas and documents, non-SQL data stores, and semantic web resources). The standard has to be adaptable to accommodate growth (new terms, additional meanings) and interoperability (connections to related information). To thrive, the standard must have a means to adapt to changing needs.”unhoused_relations[3]
no type for thiscommon vocabularies and synonym dictionaries → data discovery and quality assessment — Shared vocabularies and synonym mappings are parts of the proposed solution to heterogeneous-data discovery and quality problems. — “Data quality and fitness for use are primary concerns in the biodiversity community [42] , where information comes from heterogeneous sources spanning the globe over hundreds of years. Both data discovery and data quality assessment are hampered by this heterogeneity. Part of the solution depends on the use of common vocabularies, part on dictionaries of synonymous terms, and a great deal on applications that can facilitate discovery and assessment in place of or to aid in otherwise labor-intensive “cleanups”. For example, having a dictionary that equates “voucher” and “sample” with an accepted term “PreservedSpecimen” would allow applications to make this substitution automatically and allow users to discover relevant data using any of the synonyms regardless of how they were stored in the original data.”unhoused_relations[4]
no type for thisDarwin Core constraints → applications — The standard recommends constraints but delegates enforcement to applications. — “Darwin Core makes recommendations about constraints on data content, whether about data types, valid values, or controlled vocabularies. For example, decimalLatitude is recommended to be a floating-point number falling between 90 and −90, inclusive; countryCode is recommended to be a value from ISO 3166-1-alpha-2 (two-letter country codes). Though these recommendations are made in the standard, the philosophy is to relegate enforcement to applications where they make sense. For example, in a collaboration where the purpose is to automate data quality improvement on shared data, it is essential to be able to share the warts-and-all data that need to be investigated and improved.”unhoused_relations[5]
no type for thisIntegrated Publishing Toolkit → Global Biodiversity Resources Discovery System — The publishing toolkit works in tandem with the registry to support discovery and retrieval. — “The Integrated Publishing Toolkit (IPT; http://www.gbif.org/informatics/infrastructure/publishing/ ) is an open-source software development project, led by GBIF, designed to address the challenges of sharing biodiversity data. By producing and providing easy access to Darwin Core Archives and resource metadata in Ecological Markup Language [44] , the IPT works in tandem with a Global Biodiversity Resources Discovery System (GBRDS), a data registry, to facilitate discovery and retrieval of shared data throughout the world. The IPT complements other tools that have been created to assist data users to explore, organize, and mobilize data sets. A range of spreadsheet and archive creators and validators has been developed by GBIF and others. These tools can be accessed via the GBIF Publishing Software web page ( http://www.gbif.org/informatics/standards-and-tools/publishing-data/publishing-software/ ).”unhoused_relations[6]
no type for thisDarwin Core Extension → specialized groups — Extensions supply terms and guidance missing from the common-ground core for specialized groups. — “Because Darwin Core aims to cover the common ground in biodiversity, it inevitably lacks terms that are of interest to more specialized groups. A Darwin Core Extension consists of additional terms describing a complementary, related domain, or guidance on the use of Darwin Core within a specific sub-domain of biodiversity. Over the last decade, Darwin Core has evolved by means of extensions, some of which have been incorporated in the standard. For example, the terms of a paleontology extension related to an earlier, pre-standard version of Darwin Core became the terms of the current GeologicalContext class. Similarly, terms originating from an early version of the Darwin Core created for the Ocean Biogeographic Information System (OBIS; http://www.iobis.org/ ) have also been added to Darwin Core. Going forward, specific projects or disciplines may find it convenient to extend the scope of Darwin Core outside the existing namespace and governance process for proof-of-concept research. Once the understanding of the new terms has been tested and proven of utility in a broader context, incorporation into the standard can be accomplished through community consensus.”unhoused_relations[7]
no type for thisDarwin Core → MIxS — The standards are conceptually similar and have complementary term sets. — “Currently, Darwin Core and GSC developers are collaborating (supported by NSF-RCN4GSC) to harmonize Darwin Core and MIxS to aid the growing field of sequence-based diversity research. Darwin Core and GSC developers have concluded that the standards are conceptually similar and that the distinct sets of terms are complementary. This allows the development of a bi-directional (see Figure 2 ) solution, where in the future the GSC will be able to incorporate terms from Darwin Core and add GSC-specific reporting requirements, while Darwin Core will be able to offer a genomics extension using the results of this activity.”unhoused_relations[8]
no type for thisDarwin Core records → new knowledge products — Integrated records support new products documenting distributions and environmental change. — “Biodiversity data derive from myriad sources stored in various formats on many distinct hardware and software platforms. An essential step towards understanding global patterns of biodiversity is to provide a standardized view of these heterogeneous data sources to improve interoperability. Fundamental to this advance are definitions of common terms. This paper describes the evolution and development of Darwin Core, a data standard for publishing and integrating biodiversity information. We focus on the categories of terms that define the standard, differences between simple and relational Darwin Core, how the standard has been implemented, and the community processes that are essential for maintenance and growth of the standard. We present case-study extensions of the Darwin Core into new research communities, including metagenomics and genetic resources. We close by showing how Darwin Core records are integrated to create new knowledge products documenting species distributions and changes due to environmental perturbations.”unhoused_relations[9]
no type for thisDarwin Core → grand challenge scientific endeavors — Mobilized and integrated Darwin Core data can be incorporated into broader scientific programs. — “Darwin Core is a living standard. Although its roots were planted in the vertebrate natural history collections community, Darwin Core continues to grow to serve the needs of biodiversity research. This growth, over the relatively short period of a decade, speaks both to the need for such a standard and to the efforts of its champions to increase its utility through a community development process in order to meet increasing demand. Darwin Core greatly increases the value and re-use of freely available and accessible biodiversity data so that they can be effectively mobilized, integrated, and incorporated into other “grand challenge” scientific endeavors.”unhoused_relations[10]
no type for thisASC model → ontological description — The ASC model was an ontological description of the biological-collections domain. — “In the early 1990's, entity-relationship modeling had become accepted as a prerequisite for designing any database serving multiple users. A normalized database structure was the primary technique for enforcing data integrity. The Association of Systematic Collections (ASC) model [30] was the result of the first group effort to create a conceptual model for biological collections that accommodated the distinct taxonomic disciplines commonly found in natural history museums. The ASC model was an ontological description of the domain, but was determined at the time to be beyond the technical capabilities to implement [31] . Eventually, this model was then used as the point of departure for several collection management applications, including Specify ( http://specifysoftware.org/ ), Biota ( http://viceroy.eeb.uconn.edu/biota ), and Arctos ( http://arctos.database.museum/ ). The emphasis at that time was to develop best practice for data capture and management, not data exchange or integration.”unhoused_relations[11]
no type for thislack of a coordinated publishing and integration system → data repositories — Repositories tend to be isolated when coordinated systems and standards are absent. — “A general challenge of biodiversity data that is shared with many other information domains is the lack of a coordinated publishing and integration system; data repositories tend to be isolated from each other in the absence of standards for data and communication protocols. Heterogeneity in meaning and content of terms creates obstacles in every aspect of data integration and use, including discovery, comparison, and quality assessment. Information communities, especially Library Information Sciences, have a long history of meeting these challenges through the creation and maintenance of standards.”unhoused_relations[12]
no type for thisHeterogeneity in meaning and content of terms → obstacles in every aspect of data integration and use — Semantic heterogeneity creates obstacles to discovery, comparison, quality assessment, and integration. — “A general challenge of biodiversity data that is shared with many other information domains is the lack of a coordinated publishing and integration system; data repositories tend to be isolated from each other in the absence of standards for data and communication protocols. Heterogeneity in meaning and content of terms creates obstacles in every aspect of data integration and use, including discovery, comparison, and quality assessment. Information communities, especially Library Information Sciences, have a long history of meeting these challenges through the creation and maintenance of standards.”unhoused_relations[13]
no type for thisclearly defined semantics → human and machine interpretation — Defined semantics make human understanding and machine interpretation possible. — “Fundamentally, Darwin Core is a set of terms having clearly defined semantics that can be understood by people or interpreted by machines, making it possible to determine appropriate uses of the data encoded therein. The terms are organized into nine categories (often referred to as “classes”, Figure 2 ), six of which cover broad aspects (event, location, geological context, occurrence, taxon, and identification) of the biodiversity domain. The remaining categories cover relationships to other resources, measurements, and generic information about records. Especially for the record level, Darwin Core recommends the use of a number of terms from Dublin Core (type, modified, language, rights, rightsHolder, accessRights, bibliographicCitation, references). The full set of current Darwin Core terms with their descriptions is available in the Quick Reference Guide ( http://rs.tdwg.org/dwc/terms/ ).”unhoused_relations[14]
no type for thisA variety of tools → creation and publication of Darwin Core Archives relatively simple — GBIF-supported tools are intended to make archive creation and publication simpler. — “A variety of tools has been developed to simplify the mobilization and sharing of biodiversity data using the Darwin Core. Many of these tools focus on the creation or validation of Darwin Core Archives ( http://code.google.com/p/darwincore/wiki/ToolsAndApplications#Tools ). The Global Biodiversity Information Facility (GBIF), an international organization promoting the free and open access to biodiversity data online, has invested heavily in the open and collaborative development of tools ( http://tools.gbif.org/ ) to make the creation and publication of Darwin Core Archives relatively simple.”unhoused_relations[15]
limitationExisting biodiversity repositories tend to remain isolated without coordinated publishing standards and communication protocols. — “A general challenge of biodiversity data that is shared with many other information domains is the lack of a coordinated publishing and integration system; data repositories tend to be isolated from each other in the absence of standards for data and communication protocols. Heterogeneity in meaning and content of terms creates obstacles in every aspect of data integration and use, including discovery, comparison, and quality assessment. Information communities, especially Library Information Sciences, have a long history of meeting these challenges through the creation and maintenance of standards.”limitations[0]
limitationBroad-scale biodiversity analysis is impeded by data that are not accessible at the necessary spatial and temporal scales. — “The documentation of global patterns of biodiversity change is an important first step toward a wise, sustainable policy of conservation and management in the face of a changing environment [15] . Such documentation has emerged as a global priority [16] – [18] . A major impediment to creating this documentation is the lack of easily accessible data at the scope and at the scales needed. Most studies documenting biodiversity changes are limited to a few well-studied species or to small temporal and spatial scales [19] . To make effective use of existing data for broad-scale analyses, community coordination is required. Information must be in digital form, accessible, discoverable, and integrated. Each of these criteria presents distinct challenges, some of which are unique to biodiversity-related data.”limitations[1]
limitationLocally evolved curation practices vary by discipline and institution and historically lacked a data-sharing culture. — “The primary purpose of Darwin Core is to create a common language for sharing biodiversity data that is complementary to and reuses metadata standards from other domains wherever possible. Creating this common language has been particularly challenging, since natural history data curation practices have been developed locally and organically over hundreds of years, have varied between disciplines as well as institutions, and have had limited culture of data sharing.”limitations[2]
limitationSimple Darwin Core cannot easily represent repeating properties and relationships that need complex structures. — “Darwin Core Categories: Simple Darwin Core is comprised of seven categories of terms (green). This subset of Darwin Core terms represents descriptive data about organisms that can be represented in one file with one row per record and one column per term. Two additional categories (orange) expand Darwin Core with concepts that require a more complex data structure, such as multiple measurements from a single specimen, and cannot be represented easily in Simple Darwin Core.”limitations[3]
limitationDarwin Core's common-ground scope inevitably omits terms needed by specialized research groups. — “Because Darwin Core aims to cover the common ground in biodiversity, it inevitably lacks terms that are of interest to more specialized groups. A Darwin Core Extension consists of additional terms describing a complementary, related domain, or guidance on the use of Darwin Core within a specific sub-domain of biodiversity. Over the last decade, Darwin Core has evolved by means of extensions, some of which have been incorporated in the standard. For example, the terms of a paleontology extension related to an earlier, pre-standard version of Darwin Core became the terms of the current GeologicalContext class. Similarly, terms originating from an early version of the Darwin Core created for the Ocean Biogeographic Information System (OBIS; http://www.iobis.org/ ) have also been added to Darwin Core. Going forward, specific projects or disciplines may find it convenient to extend the scope of Darwin Core outside the existing namespace and governance process for proof-of-concept research. Once the understanding of the new terms has been tested and proven of utility in a broader context, incorporation into the standard can be accomplished through community consensus.”limitations[4]
limitationSemantic-web integration was early-stage and hindered by the absence of a formal ontology relating Darwin Core concepts. — “Though the Darwin Core is defined in an RDF document, integration of biodiversity data in the semantic web is in its early stages. One of the major challenges for Darwin Core in the semantic web context is the lack of a well-defined ontology - a formal definition of relationships between terms in a defined domain. An ontology would define the relationships between concepts such as biological entities, the events that document where and when they occurred, and the processes through which they are identified as being representative of a taxonomic concept. Without rigorous relationships between concepts and the properties that define them, connections between biodiversity data and related semantically rich information, such as literature and genomes, are difficult to traverse. This creates obstacles to cross-disciplinary semantic inquiry, such as in the Linked Data distributed data community ( http://linkeddata.org/ ). Current research is trying to address this gap (see TaxonConcept Knowledge Base, http://www.taxonconcept.org/ and BiSciCol, http://biscicol.blogspot.com/ ), active discussions on various aspects of the challenge take place regularly on the Darwin Core public forum ( http://lists.tdwg.org/mailman/listinfo/tdwg-content ), and an RDF task group has been established within TDWG “to adapt TDWG vocabularies for use as RDF classes and properties and to integrate those resources with other well-known vocabularies and ontologies outside TDWG for use in describing biodiversity resources.” [43]”limitations[5]
limitationSustainable operation of large-scale biodiversity aggregators remained an active research problem. — “Whereas tools such as the IPT facilitate data mobilization using Darwin Core data, other tools build on these sources to integrate and index biodiversity data. These aggregators are thematic networks with either geographic (e.g., Atlas of Living Australia, http://www.ala.org.au/ ) or taxonomic focus (e.g., VertNet, http://vertnet.org ). Developing these systems to work sustainably and at large scales is an area of active research. For example, VertNet ( http://vertnet.org/ ), an aggregation of vertebrate specimen and observation data into a cloud-based data store, makes use of the Simple Darwin Core in comma separated value (.csv) files with header rows containing Darwin Core term names. These files are published to the data store where the records are indexed for high-performance querying.”limitations[6]
limitationRecommended constraints are not enforced by the standard itself, leaving their application context-dependent. — “Darwin Core makes recommendations about constraints on data content, whether about data types, valid values, or controlled vocabularies. For example, decimalLatitude is recommended to be a floating-point number falling between 90 and −90, inclusive; countryCode is recommended to be a value from ISO 3166-1-alpha-2 (two-letter country codes). Though these recommendations are made in the standard, the philosophy is to relegate enforcement to applications where they make sense. For example, in a collaboration where the purpose is to automate data quality improvement on shared data, it is essential to be able to share the warts-and-all data that need to be investigated and improved.”limitations[7]
limitationGrowing biodiversity data combine large volume with temporal, spatial, and methodological heterogeneity. — “The President's Council of Advisors on Science and Technology (PCAST) report on sustaining environmental capital noted recently that the challenge is not only one of the volume of data, but also its heterogeneity, as traditional biotic surveying practices blend with new approaches, such as remote sensing [56] or metagenomics [57] . A key passage in that PCAST report captures the challenge perfectly: “temporal, spatial, and methodological heterogeneity leads to a depth and richness in biodiversity and ecosystems data not found in other fields. It also makes dataset interoperability a problem that is at the same time particularly challenging and highly important to solve [58] .” Darwin Core fills an essential role in describing some of these data in a standard format based on community input and demonstrated utility.”limitations[8]
Content tags
content-observations: finding · quantity · variable · definition · key-term — grounded in the full text
findingSemantic heterogeneity and isolated repositories obstruct biodiversity-data discovery, comparison, quality assessment, and integration. — “A general challenge of biodiversity data that is shared with many other information domains is the lack of a coordinated publishing and integration system; data repositories tend to be isolated from each other in the absence of standards for data and communication protocols. Heterogeneity in meaning and content of terms creates obstacles in every aspect of data integration and use, including discovery, comparison, and quality assessment. Information communities, especially Library Information Sciences, have a long history of meeting these challenges through the creation and maintenance of standards.”content_tags.findings[0]
findingDarwin Core was widely deployed, with GBIF indexing about 300 million formatted records from more than 340 organizations in 43 countries. — “Darwin Core [20] is a standard for sharing data about biodiversity – the occurrence of life on earth and its associations with the environment. Darwin Core first emerged around 1999 as a loosely defined set of terms, and progressed through several iterations by different groups resulting in many different variants [21] . A formal set of terms and processes to manage changes were necessary to ensure utility for data integration. These aspects were developed within the Darwin Core Task Group [22] of the Taxonomic Databases Working Group (TDWG; www.tdwg.org ) and ratified as a standard in October 2009. The philosophy for Darwin Core development has been to keep the standard as simple and open as possible and to develop terms only when there is shared demand. Darwin Core has a relatively long history of community development and is deployed widely [23] – [24] . For example, the Global Biodiversity Information Facility currently indexes approximately 300 million Darwin Core-formatted records published by more than 340 organizations in 43 countries. Increasingly, Darwin Core is being incorporated in communities beyond that of natural history collections ( Figure 1 ), in which the standard has its roots.”content_tags.findings[1]
findingDarwin Core organizes its terms into nine categories, six covering broad biodiversity-domain aspects and three covering relations, measurements, and record information. — “Fundamentally, Darwin Core is a set of terms having clearly defined semantics that can be understood by people or interpreted by machines, making it possible to determine appropriate uses of the data encoded therein. The terms are organized into nine categories (often referred to as “classes”, Figure 2 ), six of which cover broad aspects (event, location, geological context, occurrence, taxon, and identification) of the biodiversity domain. The remaining categories cover relationships to other resources, measurements, and generic information about records. Especially for the record level, Darwin Core recommends the use of a number of terms from Dublin Core (type, modified, language, rights, rightsHolder, accessRights, bibliographicCitation, references). The full set of current Darwin Core terms with their descriptions is available in the Quick Reference Guide ( http://rs.tdwg.org/dwc/terms/ ).”content_tags.findings[2]
findingSimple Darwin Core uses seven categories representable in one flat file, while two further categories require more complex structures. — “Darwin Core Categories: Simple Darwin Core is comprised of seven categories of terms (green). This subset of Darwin Core terms represents descriptive data about organisms that can be represented in one file with one row per record and one column per term. Two additional categories (orange) expand Darwin Core with concepts that require a more complex data structure, such as multiple measurements from a single specimen, and cannot be represented easily in Simple Darwin Core.”content_tags.findings[3]
findingThe enduring value of the standard lies in term definitions and relationships that remain independent of implementation technology. — “TDWG, as with other information standards bodies, has a history of developing data sharing standards that are bound to specific technologies, such as eXtensible Markup Language (XML). While Darwin Core is currently maintained in RDF, the enduring value of the standard lies in simple definitions of terms and their relationships to other terms, independent of technical implementation. As with Dublin Core, the idea is to promote use of the common terms in every appropriate context, and to leave the implementation details to specific applications. Data can be shared using Darwin Core in a variety of encoding schemes (Comma Separated Values, XML, JavaScript Object Notation, RDF, etc.). To aid in using Darwin Core in different contexts, there are documents with recommendations on how to share information as Darwin Core using various technologies.”content_tags.findings[4]
findingDarwin Core Archives gained adoption as an easy sharing format supported by publishing tools and taxonomic journals. — “The Simple Darwin Core ( http://rs.tdwg.org/dwc/terms/simple/index.htm ) document explains the capacity to share records with properties that do not repeat, as simple text files or XML. There is also an XML Guide with reference XML schemas for highly structured data and a Text Guide explaining the construction of Darwin Core Archives (a combination of CSV files and a simple XML document describing the semantics of the data file columns and their relationships to each other). Darwin Core Archives can support structured data that conform to a star schema (a single core set of records in one or more files, with one-to-one or one-to-many relationships to records in other files). The Darwin Core Archive is becoming ever more popular as an easy means for data sharing, largely due to the release of supporting tools, in particular the next-generation data publishing system – the Integrated Publishing Toolkit ( http://www.gbif.org/informatics/infrastructure/publishing ) – an open source application developed by the Global Biodiversity Information Facility discussed in further detail below. Darwin Core Archives have been adopted by Pensoft® ( http://www.pensoft.net/journals/ ) as the preferred form for data appendices to taxonomic publications in MycoKeys, PhytoKeys, and ZooKeys.”content_tags.findings[5]
findingStandard Darwin Core reconciled omissions and incompatibilities across earlier versions and maps obsolete terms and ABCD concepts. — “Prior to ratification, Darwin Core had a history of versions [21] , each attempting to adapt to expanding community-defined needs. The earliest versions were limited to defining terms for biological specimens in collections. Continued development in sectors of the community produced versions with added capabilities targeting observations [40] and paleontology [41] . Standard Darwin Core reconciles the omissions from, incompatibilities between, and inconsistencies within previous versions and provides mappings to the out-dated terms as well as mappings to concepts in the ABCD Schema. In addition, terms were added to enable the transmission of taxonomic name and classification data sets. The result is a relatively simple and stable specification, which serves the needs of data publishers, data consumers, and application developers to work with primary biodiversity data.”content_tags.findings[6]
findingThe draft standard received public review and was ratified by the TDWG Executive Committee in October 2009. — “Darwin Core underwent a year of document development by the Darwin Core Task Group with support from the National Science Foundation and the Global Biodiversity Information Facility. The draft standard underwent review with public commentary before being ratified by the TDWG Executive Committee in October 2009.”content_tags.findings[7]
findingDarwin Core changes proceed through public discussion, consensus, formal requests, technical review, and versioned documents. — “Darwin Core development is community driven and follows the process published in the Darwin Core Namespace Policy ( http://rs.tdwg.org/dwc/2009-09-23/terms/namespace/index.htm ). Open commentaries on issues related to Darwin Core are expressed through a public forum (at tdwg-content@lists.tdwg.org ) to which any subscriber may contribute. Discussions that result in consensus for change (new terms, new definitions, new relationships, changes in documentation) are submitted as change requests using templates requesting the appropriate information on the issue tracker of the Darwin Core Project site ( http://code.google.com/p/darwincore/wiki/SubmittingIssues ). Sometimes this process is reversed, with a submitted issue being copied to the discussion forum for elaboration and consensus before refining the issue as submitted. All changes undergo a 30-day public review, announced on the listserv. Changes are reviewed by TDWG's Technical Architecture Group (TAG: http://www.tdwg.org/activities/tag/ ), a set of volunteer members with broad interest and expertise in web-based interoperability. The TAG determines if the proposed changes are compatible with Darwin Core and that they do not reinvent existing standards. Changes that pass this review process are made as version changes to the affected documents, the latest of which always constitute the current standard.”content_tags.findings[8]
findingThe standard recommends content constraints but deliberately leaves enforcement to applications where appropriate. — “Darwin Core makes recommendations about constraints on data content, whether about data types, valid values, or controlled vocabularies. For example, decimalLatitude is recommended to be a floating-point number falling between 90 and −90, inclusive; countryCode is recommended to be a value from ISO 3166-1-alpha-2 (two-letter country codes). Though these recommendations are made in the standard, the philosophy is to relegate enforcement to applications where they make sense. For example, in a collaboration where the purpose is to automate data quality improvement on shared data, it is essential to be able to share the warts-and-all data that need to be investigated and improved.”content_tags.findings[9]
findingSemantic-web integration remained early-stage because Darwin Core lacked a well-defined ontology connecting domain concepts. — “Though the Darwin Core is defined in an RDF document, integration of biodiversity data in the semantic web is in its early stages. One of the major challenges for Darwin Core in the semantic web context is the lack of a well-defined ontology - a formal definition of relationships between terms in a defined domain. An ontology would define the relationships between concepts such as biological entities, the events that document where and when they occurred, and the processes through which they are identified as being representative of a taxonomic concept. Without rigorous relationships between concepts and the properties that define them, connections between biodiversity data and related semantically rich information, such as literature and genomes, are difficult to traverse. This creates obstacles to cross-disciplinary semantic inquiry, such as in the Linked Data distributed data community ( http://linkeddata.org/ ). Current research is trying to address this gap (see TaxonConcept Knowledge Base, http://www.taxonconcept.org/ and BiSciCol, http://biscicol.blogspot.com/ ), active discussions on various aspects of the challenge take place regularly on the Darwin Core public forum ( http://lists.tdwg.org/mailman/listinfo/tdwg-content ), and an RDF task group has been established within TDWG “to adapt TDWG vocabularies for use as RDF classes and properties and to integrate those resources with other well-known vocabularies and ontologies outside TDWG for use in describing biodiversity resources.” [43]”content_tags.findings[10]
findingGBIF tools simplify archive creation and publication, while aggregators integrate and index Darwin Core data for discovery and querying. — “A variety of tools has been developed to simplify the mobilization and sharing of biodiversity data using the Darwin Core. Many of these tools focus on the creation or validation of Darwin Core Archives ( http://code.google.com/p/darwincore/wiki/ToolsAndApplications#Tools ). The Global Biodiversity Information Facility (GBIF), an international organization promoting the free and open access to biodiversity data online, has invested heavily in the open and collaborative development of tools ( http://tools.gbif.org/ ) to make the creation and publication of Darwin Core Archives relatively simple.”content_tags.findings[11]
findingExtensions let specialized communities add terms and can later enter the standard after testing and community consensus. — “Because Darwin Core aims to cover the common ground in biodiversity, it inevitably lacks terms that are of interest to more specialized groups. A Darwin Core Extension consists of additional terms describing a complementary, related domain, or guidance on the use of Darwin Core within a specific sub-domain of biodiversity. Over the last decade, Darwin Core has evolved by means of extensions, some of which have been incorporated in the standard. For example, the terms of a paleontology extension related to an earlier, pre-standard version of Darwin Core became the terms of the current GeologicalContext class. Similarly, terms originating from an early version of the Darwin Core created for the Ocean Biogeographic Information System (OBIS; http://www.iobis.org/ ) have also been added to Darwin Core. Going forward, specific projects or disciplines may find it convenient to extend the scope of Darwin Core outside the existing namespace and governance process for proof-of-concept research. Once the understanding of the new terms has been tested and proven of utility in a broader context, incorporation into the standard can be accomplished through community consensus.”content_tags.findings[12]
findingDarwin Core and MIxS were judged conceptually similar and their distinct term sets complementary, enabling bidirectional harmonization. — “Currently, Darwin Core and GSC developers are collaborating (supported by NSF-RCN4GSC) to harmonize Darwin Core and MIxS to aid the growing field of sequence-based diversity research. Darwin Core and GSC developers have concluded that the standards are conceptually similar and that the distinct sets of terms are complementary. This allows the development of a bi-directional (see Figure 2 ) solution, where in the future the GSC will be able to incorporate terms from Darwin Core and add GSC-specific reporting requirements, while Darwin Core will be able to offer a genomics extension using the results of this activity.”content_tags.findings[13]
findingStandard formats, aggregation tools, and Darwin Core Archives helped overcome limited data availability for biodiversity questions. — “The creation of a standard format for biodiversity data, the development of aggregation tools, and the increasing use of Darwin Core Archives have helped to overcome the challenge of limited availability of data to answer questions about biodiversity. As more data become digitized and discoverable, biocollections can become a window into broader analyses of ecological, climate, niche, environmental, and biological research questions and critical issues.”content_tags.findings[14]
findingThe REBIOMA case used Darwin Core standardization, aggregation, and quality review to provide conservation data and distribution models for Madagascar. — “Though predated by examples of the effective use of Darwin Core for distribution modeling, influence of natural area preservation, and estimates of climate change impact [53] , the utility of data shared using Darwin Core is illustrated by two recent examples. First, the University of California, Berkeley, and the Wildlife Conservation Society have collaborated to create Réseau de la Biodiversité de Madagascar (REBIOMA, http://www.rebioma.net/ ).The effort seeks to make biodiversity data about Madagascar available via a single web-based resource. Primary data on biodiversity in Madagascar come from researchers and institutions all over the world. REBIOMA works with each collection to standardize the data using the Darwin Core, to mobilize and aggregate the data, and to vet the data for quality, completeness, and fitness for use. Data passing automated quality checks and review by a board of taxonomic experts are analyzed in combination with environmental data to produce maps showing models of where species might occur. The success of this project has made it possible for researchers, policy makers, government officials, and conservationists to capture a wealth of data to address issues of Malagasy biodiversity. The simplicity and flexibility of Darwin Core has made it possible for REBIOMA to provide immediate access to high-quality data and tools for monitoring and assessing conservation efforts.”content_tags.findings[15]
findingThe authors characterize Darwin Core as a living standard that increases the value and reuse of accessible biodiversity data. — “Darwin Core is a living standard. Although its roots were planted in the vertebrate natural history collections community, Darwin Core continues to grow to serve the needs of biodiversity research. This growth, over the relatively short period of a decade, speaks both to the need for such a standard and to the efforts of its champions to increase its utility through a community development process in order to meet increasing demand. Darwin Core greatly increases the value and re-use of freely available and accessible biodiversity data so that they can be effectively mobilized, integrated, and incorporated into other “grand challenge” scientific endeavors.”content_tags.findings[16]
quantityapproximately 300 million Darwin Core-formatted records — records indexed by GBIF at the time described — “Darwin Core [20] is a standard for sharing data about biodiversity – the occurrence of life on earth and its associations with the environment. Darwin Core first emerged around 1999 as a loosely defined set of terms, and progressed through several iterations by different groups resulting in many different variants [21] . A formal set of terms and processes to manage changes were necessary to ensure utility for data integration. These aspects were developed within the Darwin Core Task Group [22] of the Taxonomic Databases Working Group (TDWG; www.tdwg.org ) and ratified as a standard in October 2009. The philosophy for Darwin Core development has been to keep the standard as simple and open as possible and to develop terms only when there is shared demand. Darwin Core has a relatively long history of community development and is deployed widely [23] – [24] . For example, the Global Biodiversity Information Facility currently indexes approximately 300 million Darwin Core-formatted records published by more than 340 organizations in 43 countries. Increasingly, Darwin Core is being incorporated in communities beyond that of natural history collections ( Figure 1 ), in which the standard has its roots.”content_tags.quantities[0]
quantitymore than 340 organizations — organizations publishing the indexed Darwin Core records — “Darwin Core [20] is a standard for sharing data about biodiversity – the occurrence of life on earth and its associations with the environment. Darwin Core first emerged around 1999 as a loosely defined set of terms, and progressed through several iterations by different groups resulting in many different variants [21] . A formal set of terms and processes to manage changes were necessary to ensure utility for data integration. These aspects were developed within the Darwin Core Task Group [22] of the Taxonomic Databases Working Group (TDWG; www.tdwg.org ) and ratified as a standard in October 2009. The philosophy for Darwin Core development has been to keep the standard as simple and open as possible and to develop terms only when there is shared demand. Darwin Core has a relatively long history of community development and is deployed widely [23] – [24] . For example, the Global Biodiversity Information Facility currently indexes approximately 300 million Darwin Core-formatted records published by more than 340 organizations in 43 countries. Increasingly, Darwin Core is being incorporated in communities beyond that of natural history collections ( Figure 1 ), in which the standard has its roots.”content_tags.quantities[1]
quantity43 countries — country coverage of the indexed records — “Darwin Core [20] is a standard for sharing data about biodiversity – the occurrence of life on earth and its associations with the environment. Darwin Core first emerged around 1999 as a loosely defined set of terms, and progressed through several iterations by different groups resulting in many different variants [21] . A formal set of terms and processes to manage changes were necessary to ensure utility for data integration. These aspects were developed within the Darwin Core Task Group [22] of the Taxonomic Databases Working Group (TDWG; www.tdwg.org ) and ratified as a standard in October 2009. The philosophy for Darwin Core development has been to keep the standard as simple and open as possible and to develop terms only when there is shared demand. Darwin Core has a relatively long history of community development and is deployed widely [23] – [24] . For example, the Global Biodiversity Information Facility currently indexes approximately 300 million Darwin Core-formatted records published by more than 340 organizations in 43 countries. Increasingly, Darwin Core is being incorporated in communities beyond that of natural history collections ( Figure 1 ), in which the standard has its roots.”content_tags.quantities[2]
quantitynine categories — total categories organizing Darwin Core terms — “Fundamentally, Darwin Core is a set of terms having clearly defined semantics that can be understood by people or interpreted by machines, making it possible to determine appropriate uses of the data encoded therein. The terms are organized into nine categories (often referred to as “classes”, Figure 2 ), six of which cover broad aspects (event, location, geological context, occurrence, taxon, and identification) of the biodiversity domain. The remaining categories cover relationships to other resources, measurements, and generic information about records. Especially for the record level, Darwin Core recommends the use of a number of terms from Dublin Core (type, modified, language, rights, rightsHolder, accessRights, bibliographicCitation, references). The full set of current Darwin Core terms with their descriptions is available in the Quick Reference Guide ( http://rs.tdwg.org/dwc/terms/ ).”content_tags.quantities[3]
quantityseven categories of terms — categories comprising Simple Darwin Core — “Darwin Core Categories: Simple Darwin Core is comprised of seven categories of terms (green). This subset of Darwin Core terms represents descriptive data about organisms that can be represented in one file with one row per record and one column per term. Two additional categories (orange) expand Darwin Core with concepts that require a more complex data structure, such as multiple measurements from a single specimen, and cannot be represented easily in Simple Darwin Core.”content_tags.quantities[4]
quantityTwo additional categories — categories requiring more complex data structures — “Darwin Core Categories: Simple Darwin Core is comprised of seven categories of terms (green). This subset of Darwin Core terms represents descriptive data about organisms that can be represented in one file with one row per record and one column per term. Two additional categories (orange) expand Darwin Core with concepts that require a more complex data structure, such as multiple measurements from a single specimen, and cannot be represented easily in Simple Darwin Core.”content_tags.quantities[5]
quantityone row per record — flat-file record cardinality in Simple Darwin Core — “Darwin Core Categories: Simple Darwin Core is comprised of seven categories of terms (green). This subset of Darwin Core terms represents descriptive data about organisms that can be represented in one file with one row per record and one column per term. Two additional categories (orange) expand Darwin Core with concepts that require a more complex data structure, such as multiple measurements from a single specimen, and cannot be represented easily in Simple Darwin Core.”content_tags.quantities[6]
quantityone column per term — flat-file field cardinality in Simple Darwin Core — “Darwin Core Categories: Simple Darwin Core is comprised of seven categories of terms (green). This subset of Darwin Core terms represents descriptive data about organisms that can be represented in one file with one row per record and one column per term. Two additional categories (orange) expand Darwin Core with concepts that require a more complex data structure, such as multiple measurements from a single specimen, and cannot be represented easily in Simple Darwin Core.”content_tags.quantities[7]
quantityOctober 2009 — month of Darwin Core ratification — “Darwin Core underwent a year of document development by the Darwin Core Task Group with support from the National Science Foundation and the Global Biodiversity Information Facility. The draft standard underwent review with public commentary before being ratified by the TDWG Executive Committee in October 2009.”content_tags.quantities[8]
quantitymore than a decade — development span described for Darwin Core — “Darwin Core's development spans more than a decade, but rests on the earlier work of academic societies that addressed how to document or catalog specimens in natural history collections. Those societies put forward prescriptive guidelines about how to catalog specimens properly, first on paper and later in computer databases [27] – [29] . The purpose was to promote completeness in capture and consistency in representation or encoding. Actual data exchange and integration was anticipated as a future capability, but these guidelines preceded the Internet and World Wide Web.”content_tags.quantities[9]
quantity30-day public review — public review period for standard changes — “Darwin Core development is community driven and follows the process published in the Darwin Core Namespace Policy ( http://rs.tdwg.org/dwc/2009-09-23/terms/namespace/index.htm ). Open commentaries on issues related to Darwin Core are expressed through a public forum (at tdwg-content@lists.tdwg.org ) to which any subscriber may contribute. Discussions that result in consensus for change (new terms, new definitions, new relationships, changes in documentation) are submitted as change requests using templates requesting the appropriate information on the issue tracker of the Darwin Core Project site ( http://code.google.com/p/darwincore/wiki/SubmittingIssues ). Sometimes this process is reversed, with a submitted issue being copied to the discussion forum for elaboration and consensus before refining the issue as submitted. All changes undergo a 30-day public review, announced on the listserv. Changes are reviewed by TDWG's Technical Architecture Group (TAG: http://www.tdwg.org/activities/tag/ ), a set of volunteer members with broad interest and expertise in web-based interoperability. The TAG determines if the proposed changes are compatible with Darwin Core and that they do not reinvent existing standards. Changes that pass this review process are made as version changes to the affected documents, the latest of which always constitute the current standard.”content_tags.quantities[10]
quantitybetween 90 and −90, inclusive — recommended value range for decimalLatitude — “Darwin Core makes recommendations about constraints on data content, whether about data types, valid values, or controlled vocabularies. For example, decimalLatitude is recommended to be a floating-point number falling between 90 and −90, inclusive; countryCode is recommended to be a value from ISO 3166-1-alpha-2 (two-letter country codes). Though these recommendations are made in the standard, the philosophy is to relegate enforcement to applications where they make sense. For example, in a collaboration where the purpose is to automate data quality improvement on shared data, it is essential to be able to share the warts-and-all data that need to be investigated and improved.”content_tags.quantities[11]
quantitythree centuries — historical span of biodiversity information being digitized — “The demand for Darwin Core data is increasing. The corpus of information spanning three centuries of biodiversity exploration is being digitized at an increasing rate. Major efforts such as the new US National Science Foundation program Advancing Digitization of Biological Collections ( http://nsf.gov/funding/pgm_summ.jsp?pims_id=503559&org=DBI&from=home ) and the Atlas of Living Australia ( http://www.ala.org.au ) are two recent examples. A flood of qualitatively new global biodiversity data is also being generated through the application of high-throughput gene sequencing of environmental samples.”content_tags.quantities[12]
variablesemantics (meaning assigned to shared data terms for human and machine interpretation) — “Fundamentally, Darwin Core is a set of terms having clearly defined semantics that can be understood by people or interpreted by machines, making it possible to determine appropriate uses of the data encoded therein. The terms are organized into nine categories (often referred to as “classes”, Figure 2 ), six of which cover broad aspects (event, location, geological context, occurrence, taxon, and identification) of the biodiversity domain. The remaining categories cover relationships to other resources, measurements, and generic information about records. Especially for the record level, Darwin Core recommends the use of a number of terms from Dublin Core (type, modified, language, rights, rightsHolder, accessRights, bibliographicCitation, references). The full set of current Darwin Core terms with their descriptions is available in the Quick Reference Guide ( http://rs.tdwg.org/dwc/terms/ ).”content_tags.variables[0]
variablecategories (grouping structure for Darwin Core terms) — “Fundamentally, Darwin Core is a set of terms having clearly defined semantics that can be understood by people or interpreted by machines, making it possible to determine appropriate uses of the data encoded therein. The terms are organized into nine categories (often referred to as “classes”, Figure 2 ), six of which cover broad aspects (event, location, geological context, occurrence, taxon, and identification) of the biodiversity domain. The remaining categories cover relationships to other resources, measurements, and generic information about records. Especially for the record level, Darwin Core recommends the use of a number of terms from Dublin Core (type, modified, language, rights, rightsHolder, accessRights, bibliographicCitation, references). The full set of current Darwin Core terms with their descriptions is available in the Quick Reference Guide ( http://rs.tdwg.org/dwc/terms/ ).”content_tags.variables[1]
variabletechnical implementation (technology-specific realization deliberately separated from stable term definitions) — “TDWG, as with other information standards bodies, has a history of developing data sharing standards that are bound to specific technologies, such as eXtensible Markup Language (XML). While Darwin Core is currently maintained in RDF, the enduring value of the standard lies in simple definitions of terms and their relationships to other terms, independent of technical implementation. As with Dublin Core, the idea is to promote use of the common terms in every appropriate context, and to leave the implementation details to specific applications. Data can be shared using Darwin Core in a variety of encoding schemes (Comma Separated Values, XML, JavaScript Object Notation, RDF, etc.). To aid in using Darwin Core in different contexts, there are documents with recommendations on how to share information as Darwin Core using various technologies.”content_tags.variables[2]
variableencoding schemes (alternative serializations in which Darwin Core data can be shared) — “TDWG, as with other information standards bodies, has a history of developing data sharing standards that are bound to specific technologies, such as eXtensible Markup Language (XML). While Darwin Core is currently maintained in RDF, the enduring value of the standard lies in simple definitions of terms and their relationships to other terms, independent of technical implementation. As with Dublin Core, the idea is to promote use of the common terms in every appropriate context, and to leave the implementation details to specific applications. Data can be shared using Darwin Core in a variety of encoding schemes (Comma Separated Values, XML, JavaScript Object Notation, RDF, etc.). To aid in using Darwin Core in different contexts, there are documents with recommendations on how to share information as Darwin Core using various technologies.”content_tags.variables[3]
variablecommunity-defined needs (source of demand driving version and term changes) — “Prior to ratification, Darwin Core had a history of versions [21] , each attempting to adapt to expanding community-defined needs. The earliest versions were limited to defining terms for biological specimens in collections. Continued development in sectors of the community produced versions with added capabilities targeting observations [40] and paleontology [41] . Standard Darwin Core reconciles the omissions from, incompatibilities between, and inconsistencies within previous versions and provides mappings to the out-dated terms as well as mappings to concepts in the ABCD Schema. In addition, terms were added to enable the transmission of taxonomic name and classification data sets. The result is a relatively simple and stable specification, which serves the needs of data publishers, data consumers, and application developers to work with primary biodiversity data.”content_tags.variables[4]
variabledata types (one class of recommended content constraint) — “Darwin Core makes recommendations about constraints on data content, whether about data types, valid values, or controlled vocabularies. For example, decimalLatitude is recommended to be a floating-point number falling between 90 and −90, inclusive; countryCode is recommended to be a value from ISO 3166-1-alpha-2 (two-letter country codes). Though these recommendations are made in the standard, the philosophy is to relegate enforcement to applications where they make sense. For example, in a collaboration where the purpose is to automate data quality improvement on shared data, it is essential to be able to share the warts-and-all data that need to be investigated and improved.”content_tags.variables[5]
variablevalid values (one class of recommended content constraint) — “Darwin Core makes recommendations about constraints on data content, whether about data types, valid values, or controlled vocabularies. For example, decimalLatitude is recommended to be a floating-point number falling between 90 and −90, inclusive; countryCode is recommended to be a value from ISO 3166-1-alpha-2 (two-letter country codes). Though these recommendations are made in the standard, the philosophy is to relegate enforcement to applications where they make sense. For example, in a collaboration where the purpose is to automate data quality improvement on shared data, it is essential to be able to share the warts-and-all data that need to be investigated and improved.”content_tags.variables[6]
variablecontrolled vocabularies (one class of recommended content constraint and quality aid) — “Darwin Core makes recommendations about constraints on data content, whether about data types, valid values, or controlled vocabularies. For example, decimalLatitude is recommended to be a floating-point number falling between 90 and −90, inclusive; countryCode is recommended to be a value from ISO 3166-1-alpha-2 (two-letter country codes). Though these recommendations are made in the standard, the philosophy is to relegate enforcement to applications where they make sense. For example, in a collaboration where the purpose is to automate data quality improvement on shared data, it is essential to be able to share the warts-and-all data that need to be investigated and improved.”content_tags.variables[7]
variablefitness for use (context-sensitive data-quality criterion) — “Data quality and fitness for use are primary concerns in the biodiversity community [42] , where information comes from heterogeneous sources spanning the globe over hundreds of years. Both data discovery and data quality assessment are hampered by this heterogeneity. Part of the solution depends on the use of common vocabularies, part on dictionaries of synonymous terms, and a great deal on applications that can facilitate discovery and assessment in place of or to aid in otherwise labor-intensive “cleanups”. For example, having a dictionary that equates “voucher” and “sample” with an accepted term “PreservedSpecimen” would allow applications to make this substitution automatically and allow users to discover relevant data using any of the synonyms regardless of how they were stored in the original data.”content_tags.variables[8]
definitionDarwin Core — “Darwin Core [20] is a standard for sharing data about biodiversity – the occurrence of life on earth and its associations with the environment. Darwin Core first emerged around 1999 as a loosely defined set of terms, and progressed through several iterations by different groups resulting in many different variants [21] . A formal set of terms and processes to manage changes were necessary to ensure utility for data integration. These aspects were developed within the Darwin Core Task Group [22] of the Taxonomic Databases Working Group (TDWG; www.tdwg.org ) and ratified as a standard in October 2009. The philosophy for Darwin Core development has been to keep the standard as simple and open as possible and to develop terms only when there is shared demand. Darwin Core has a relatively long history of community development and is deployed widely [23] – [24] . For example, the Global Biodiversity Information Facility currently indexes approximately 300 million Darwin Core-formatted records published by more than 340 organizations in 43 countries. Increasingly, Darwin Core is being incorporated in communities beyond that of natural history collections ( Figure 1 ), in which the standard has its roots.”content_tags.definitions[0]
definitionSimple Darwin Core — “Darwin Core Categories: Simple Darwin Core is comprised of seven categories of terms (green). This subset of Darwin Core terms represents descriptive data about organisms that can be represented in one file with one row per record and one column per term. Two additional categories (orange) expand Darwin Core with concepts that require a more complex data structure, such as multiple measurements from a single specimen, and cannot be represented easily in Simple Darwin Core.”content_tags.definitions[1]
definitionDarwin Core Archives — “The Simple Darwin Core ( http://rs.tdwg.org/dwc/terms/simple/index.htm ) document explains the capacity to share records with properties that do not repeat, as simple text files or XML. There is also an XML Guide with reference XML schemas for highly structured data and a Text Guide explaining the construction of Darwin Core Archives (a combination of CSV files and a simple XML document describing the semantics of the data file columns and their relationships to each other). Darwin Core Archives can support structured data that conform to a star schema (a single core set of records in one or more files, with one-to-one or one-to-many relationships to records in other files). The Darwin Core Archive is becoming ever more popular as an easy means for data sharing, largely due to the release of supporting tools, in particular the next-generation data publishing system – the Integrated Publishing Toolkit ( http://www.gbif.org/informatics/infrastructure/publishing ) – an open source application developed by the Global Biodiversity Information Facility discussed in further detail below. Darwin Core Archives have been adopted by Pensoft® ( http://www.pensoft.net/journals/ ) as the preferred form for data appendices to taxonomic publications in MycoKeys, PhytoKeys, and ZooKeys.”content_tags.definitions[2]
definitionnormalized database structure — “In the early 1990's, entity-relationship modeling had become accepted as a prerequisite for designing any database serving multiple users. A normalized database structure was the primary technique for enforcing data integrity. The Association of Systematic Collections (ASC) model [30] was the result of the first group effort to create a conceptual model for biological collections that accommodated the distinct taxonomic disciplines commonly found in natural history museums. The ASC model was an ontological description of the domain, but was determined at the time to be beyond the technical capabilities to implement [31] . Eventually, this model was then used as the point of departure for several collection management applications, including Specify ( http://specifysoftware.org/ ), Biota ( http://viceroy.eeb.uconn.edu/biota ), and Arctos ( http://arctos.database.museum/ ). The emphasis at that time was to develop best practice for data capture and management, not data exchange or integration.”content_tags.definitions[3]
definitionontology — “Though the Darwin Core is defined in an RDF document, integration of biodiversity data in the semantic web is in its early stages. One of the major challenges for Darwin Core in the semantic web context is the lack of a well-defined ontology - a formal definition of relationships between terms in a defined domain. An ontology would define the relationships between concepts such as biological entities, the events that document where and when they occurred, and the processes through which they are identified as being representative of a taxonomic concept. Without rigorous relationships between concepts and the properties that define them, connections between biodiversity data and related semantically rich information, such as literature and genomes, are difficult to traverse. This creates obstacles to cross-disciplinary semantic inquiry, such as in the Linked Data distributed data community ( http://linkeddata.org/ ). Current research is trying to address this gap (see TaxonConcept Knowledge Base, http://www.taxonconcept.org/ and BiSciCol, http://biscicol.blogspot.com/ ), active discussions on various aspects of the challenge take place regularly on the Darwin Core public forum ( http://lists.tdwg.org/mailman/listinfo/tdwg-content ), and an RDF task group has been established within TDWG “to adapt TDWG vocabularies for use as RDF classes and properties and to integrate those resources with other well-known vocabularies and ontologies outside TDWG for use in describing biodiversity resources.” [43]”content_tags.definitions[4]
definitionIntegrated Publishing Toolkit — “The Integrated Publishing Toolkit (IPT; http://www.gbif.org/informatics/infrastructure/publishing/ ) is an open-source software development project, led by GBIF, designed to address the challenges of sharing biodiversity data. By producing and providing easy access to Darwin Core Archives and resource metadata in Ecological Markup Language [44] , the IPT works in tandem with a Global Biodiversity Resources Discovery System (GBRDS), a data registry, to facilitate discovery and retrieval of shared data throughout the world. The IPT complements other tools that have been created to assist data users to explore, organize, and mobilize data sets. A range of spreadsheet and archive creators and validators has been developed by GBIF and others. These tools can be accessed via the GBIF Publishing Software web page ( http://www.gbif.org/informatics/standards-and-tools/publishing-data/publishing-software/ ).”content_tags.definitions[5]
definitionDarwin Core Extension — “Because Darwin Core aims to cover the common ground in biodiversity, it inevitably lacks terms that are of interest to more specialized groups. A Darwin Core Extension consists of additional terms describing a complementary, related domain, or guidance on the use of Darwin Core within a specific sub-domain of biodiversity. Over the last decade, Darwin Core has evolved by means of extensions, some of which have been incorporated in the standard. For example, the terms of a paleontology extension related to an earlier, pre-standard version of Darwin Core became the terms of the current GeologicalContext class. Similarly, terms originating from an early version of the Darwin Core created for the Ocean Biogeographic Information System (OBIS; http://www.iobis.org/ ) have also been added to Darwin Core. Going forward, specific projects or disciplines may find it convenient to extend the scope of Darwin Core outside the existing namespace and governance process for proof-of-concept research. Once the understanding of the new terms has been tested and proven of utility in a broader context, incorporation into the standard can be accomplished through community consensus.”content_tags.definitions[6]
definitionliving standard — “Darwin Core is a living standard. Although its roots were planted in the vertebrate natural history collections community, Darwin Core continues to grow to serve the needs of biodiversity research. This growth, over the relatively short period of a decade, speaks both to the need for such a standard and to the efforts of its champions to increase its utility through a community development process in order to meet increasing demand. Darwin Core greatly increases the value and re-use of freely available and accessible biodiversity data so that they can be effectively mobilized, integrated, and incorporated into other “grand challenge” scientific endeavors.”content_tags.definitions[7]
Concepts
terms this paper carries, each with the sentence it was cut from — the layer that joins one paper to another. Terms with no quote yet are on CONCEPTS.html.
conceptBiodiversity data — not defined in this paper's own words; heterogeneous observations and records about biological diversity — “Biodiversity data derive from myriad sources stored in various formats on many distinct hardware and software platforms. An essential step towards understanding global patterns of biodiversity is to provide a standardized view of these heterogeneous data sources to improve interoperability. Fundamental to this advance are definitions of common terms. This paper describes the evolution and development of Darwin Core, a data standard for publishing and integrating biodiversity information. We focus on the categories of terms that define the standard, differences between simple and relational Darwin Core, how the standard has been implemented, and the community processes that are essential for maintenance and growth of the standard. We present case-study extensions of the Darwin Core into new research communities, including metagenomics and genetic resources. We close by showing how Darwin Core records are integrated to create new knowledge products documenting species distributions and changes due to environmental perturbations.”concepts[0]
conceptstandardized view — not defined in this paper's own words; common representation across heterogeneous sources — “Biodiversity data derive from myriad sources stored in various formats on many distinct hardware and software platforms. An essential step towards understanding global patterns of biodiversity is to provide a standardized view of these heterogeneous data sources to improve interoperability. Fundamental to this advance are definitions of common terms. This paper describes the evolution and development of Darwin Core, a data standard for publishing and integrating biodiversity information. We focus on the categories of terms that define the standard, differences between simple and relational Darwin Core, how the standard has been implemented, and the community processes that are essential for maintenance and growth of the standard. We present case-study extensions of the Darwin Core into new research communities, including metagenomics and genetic resources. We close by showing how Darwin Core records are integrated to create new knowledge products documenting species distributions and changes due to environmental perturbations.”concepts[1]
conceptinteroperability — not defined in this paper's own words; ability of heterogeneous biodiversity sources to be combined and used — “Biodiversity data derive from myriad sources stored in various formats on many distinct hardware and software platforms. An essential step towards understanding global patterns of biodiversity is to provide a standardized view of these heterogeneous data sources to improve interoperability. Fundamental to this advance are definitions of common terms. This paper describes the evolution and development of Darwin Core, a data standard for publishing and integrating biodiversity information. We focus on the categories of terms that define the standard, differences between simple and relational Darwin Core, how the standard has been implemented, and the community processes that are essential for maintenance and growth of the standard. We present case-study extensions of the Darwin Core into new research communities, including metagenomics and genetic resources. We close by showing how Darwin Core records are integrated to create new knowledge products documenting species distributions and changes due to environmental perturbations.”concepts[2]
conceptcommon terms — not defined in this paper's own words; shared vocabulary entries carrying agreed meanings — “Biodiversity data derive from myriad sources stored in various formats on many distinct hardware and software platforms. An essential step towards understanding global patterns of biodiversity is to provide a standardized view of these heterogeneous data sources to improve interoperability. Fundamental to this advance are definitions of common terms. This paper describes the evolution and development of Darwin Core, a data standard for publishing and integrating biodiversity information. We focus on the categories of terms that define the standard, differences between simple and relational Darwin Core, how the standard has been implemented, and the community processes that are essential for maintenance and growth of the standard. We present case-study extensions of the Darwin Core into new research communities, including metagenomics and genetic resources. We close by showing how Darwin Core records are integrated to create new knowledge products documenting species distributions and changes due to environmental perturbations.”concepts[3]
conceptDarwin Core — not defined in this paper's own words; community-developed standard for biodiversity information — “Darwin Core [20] is a standard for sharing data about biodiversity – the occurrence of life on earth and its associations with the environment. Darwin Core first emerged around 1999 as a loosely defined set of terms, and progressed through several iterations by different groups resulting in many different variants [21] . A formal set of terms and processes to manage changes were necessary to ensure utility for data integration. These aspects were developed within the Darwin Core Task Group [22] of the Taxonomic Databases Working Group (TDWG; www.tdwg.org ) and ratified as a standard in October 2009. The philosophy for Darwin Core development has been to keep the standard as simple and open as possible and to develop terms only when there is shared demand. Darwin Core has a relatively long history of community development and is deployed widely [23] – [24] . For example, the Global Biodiversity Information Facility currently indexes approximately 300 million Darwin Core-formatted records published by more than 340 organizations in 43 countries. Increasingly, Darwin Core is being incorporated in communities beyond that of natural history collections ( Figure 1 ), in which the standard has its roots.”concepts[4]
conceptdata standard — not defined in this paper's own words; specification used to publish and integrate biodiversity information — “Biodiversity data derive from myriad sources stored in various formats on many distinct hardware and software platforms. An essential step towards understanding global patterns of biodiversity is to provide a standardized view of these heterogeneous data sources to improve interoperability. Fundamental to this advance are definitions of common terms. This paper describes the evolution and development of Darwin Core, a data standard for publishing and integrating biodiversity information. We focus on the categories of terms that define the standard, differences between simple and relational Darwin Core, how the standard has been implemented, and the community processes that are essential for maintenance and growth of the standard. We present case-study extensions of the Darwin Core into new research communities, including metagenomics and genetic resources. We close by showing how Darwin Core records are integrated to create new knowledge products documenting species distributions and changes due to environmental perturbations.”concepts[5]
conceptbiodiversity information — not defined in this paper's own words; records of life's occurrence and environmental associations — “Darwin Core [20] is a standard for sharing data about biodiversity – the occurrence of life on earth and its associations with the environment. Darwin Core first emerged around 1999 as a loosely defined set of terms, and progressed through several iterations by different groups resulting in many different variants [21] . A formal set of terms and processes to manage changes were necessary to ensure utility for data integration. These aspects were developed within the Darwin Core Task Group [22] of the Taxonomic Databases Working Group (TDWG; www.tdwg.org ) and ratified as a standard in October 2009. The philosophy for Darwin Core development has been to keep the standard as simple and open as possible and to develop terms only when there is shared demand. Darwin Core has a relatively long history of community development and is deployed widely [23] – [24] . For example, the Global Biodiversity Information Facility currently indexes approximately 300 million Darwin Core-formatted records published by more than 340 organizations in 43 countries. Increasingly, Darwin Core is being incorporated in communities beyond that of natural history collections ( Figure 1 ), in which the standard has its roots.”concepts[6]
conceptSimple Darwin Core — not defined in this paper's own words; flat subset whose properties do not repeat — “Darwin Core Categories: Simple Darwin Core is comprised of seven categories of terms (green). This subset of Darwin Core terms represents descriptive data about organisms that can be represented in one file with one row per record and one column per term. Two additional categories (orange) expand Darwin Core with concepts that require a more complex data structure, such as multiple measurements from a single specimen, and cannot be represented easily in Simple Darwin Core.”concepts[7]
conceptrelational Darwin Core — not defined in this paper's own words; more structured use of Darwin Core terms and relationships — “Biodiversity data derive from myriad sources stored in various formats on many distinct hardware and software platforms. An essential step towards understanding global patterns of biodiversity is to provide a standardized view of these heterogeneous data sources to improve interoperability. Fundamental to this advance are definitions of common terms. This paper describes the evolution and development of Darwin Core, a data standard for publishing and integrating biodiversity information. We focus on the categories of terms that define the standard, differences between simple and relational Darwin Core, how the standard has been implemented, and the community processes that are essential for maintenance and growth of the standard. We present case-study extensions of the Darwin Core into new research communities, including metagenomics and genetic resources. We close by showing how Darwin Core records are integrated to create new knowledge products documenting species distributions and changes due to environmental perturbations.”concepts[8]
conceptcommon language — not defined in this paper's own words; shared terminology for publishing biodiversity data — “The primary purpose of Darwin Core is to create a common language for sharing biodiversity data that is complementary to and reuses metadata standards from other domains wherever possible. Creating this common language has been particularly challenging, since natural history data curation practices have been developed locally and organically over hundreds of years, have varied between disciplines as well as institutions, and have had limited culture of data sharing.”concepts[9]
conceptclearly defined semantics — not defined in this paper's own words; explicit meanings enabling human and machine interpretation — “Fundamentally, Darwin Core is a set of terms having clearly defined semantics that can be understood by people or interpreted by machines, making it possible to determine appropriate uses of the data encoded therein. The terms are organized into nine categories (often referred to as “classes”, Figure 2 ), six of which cover broad aspects (event, location, geological context, occurrence, taxon, and identification) of the biodiversity domain. The remaining categories cover relationships to other resources, measurements, and generic information about records. Especially for the record level, Darwin Core recommends the use of a number of terms from Dublin Core (type, modified, language, rights, rightsHolder, accessRights, bibliographicCitation, references). The full set of current Darwin Core terms with their descriptions is available in the Quick Reference Guide ( http://rs.tdwg.org/dwc/terms/ ).”concepts[10]
conceptpeople — not defined in this paper's own words; human interpreters of Darwin Core semantics — “Fundamentally, Darwin Core is a set of terms having clearly defined semantics that can be understood by people or interpreted by machines, making it possible to determine appropriate uses of the data encoded therein. The terms are organized into nine categories (often referred to as “classes”, Figure 2 ), six of which cover broad aspects (event, location, geological context, occurrence, taxon, and identification) of the biodiversity domain. The remaining categories cover relationships to other resources, measurements, and generic information about records. Especially for the record level, Darwin Core recommends the use of a number of terms from Dublin Core (type, modified, language, rights, rightsHolder, accessRights, bibliographicCitation, references). The full set of current Darwin Core terms with their descriptions is available in the Quick Reference Guide ( http://rs.tdwg.org/dwc/terms/ ).”concepts[11]
conceptmachines — not defined in this paper's own words; computational interpreters of Darwin Core semantics — “Fundamentally, Darwin Core is a set of terms having clearly defined semantics that can be understood by people or interpreted by machines, making it possible to determine appropriate uses of the data encoded therein. The terms are organized into nine categories (often referred to as “classes”, Figure 2 ), six of which cover broad aspects (event, location, geological context, occurrence, taxon, and identification) of the biodiversity domain. The remaining categories cover relationships to other resources, measurements, and generic information about records. Especially for the record level, Darwin Core recommends the use of a number of terms from Dublin Core (type, modified, language, rights, rightsHolder, accessRights, bibliographicCitation, references). The full set of current Darwin Core terms with their descriptions is available in the Quick Reference Guide ( http://rs.tdwg.org/dwc/terms/ ).”concepts[12]
conceptnine categories — not defined in this paper's own words; top-level organization of Darwin Core terms — “Fundamentally, Darwin Core is a set of terms having clearly defined semantics that can be understood by people or interpreted by machines, making it possible to determine appropriate uses of the data encoded therein. The terms are organized into nine categories (often referred to as “classes”, Figure 2 ), six of which cover broad aspects (event, location, geological context, occurrence, taxon, and identification) of the biodiversity domain. The remaining categories cover relationships to other resources, measurements, and generic information about records. Especially for the record level, Darwin Core recommends the use of a number of terms from Dublin Core (type, modified, language, rights, rightsHolder, accessRights, bibliographicCitation, references). The full set of current Darwin Core terms with their descriptions is available in the Quick Reference Guide ( http://rs.tdwg.org/dwc/terms/ ).”concepts[13]
conceptseven categories of terms — not defined in this paper's own words; categories comprising the Simple Darwin Core subset — “Darwin Core Categories: Simple Darwin Core is comprised of seven categories of terms (green). This subset of Darwin Core terms represents descriptive data about organisms that can be represented in one file with one row per record and one column per term. Two additional categories (orange) expand Darwin Core with concepts that require a more complex data structure, such as multiple measurements from a single specimen, and cannot be represented easily in Simple Darwin Core.”concepts[14]
conceptDublin Core — not defined in this paper's own words; cross-domain metadata standard reused by Darwin Core — “Though the scope and governance of Darwin Core are distinct from Dublin Core [26] , readers will recognize the ancestry of Darwin Core in their shared traits: mission, principles of operation, and inherited terms. Indeed, if words were nucleotides, the Darwin Core mission is the same as that of Dublin Core except for one base-pair addition (in bold), namely, “to provide simple standards to facilitate the finding, sharing and management of biodiversity information.” This relationship is not accidental. The Dublin Core Metadata Initiative (DCMI) has done a very good job of maintaining the metadata specifications at the core of web-based resources. The success of DCMI encouraged TDWG to adopt similar policies for the specific domain of biodiversity through the Darwin Core. This process, in turn, acts as the basis for the development of data standards for even more specific sub-disciplines (e.g., plant genetic resources) as well as a basis for collaboration with complementary related domains (e.g., metagenomics).”concepts[15]
conceptauthoritative form — not defined in this paper's own words; downloadable archive containing the normative Darwin Core documents — “The authoritative form of the Darwin Core is a downloadable archive [25] , which contains various documents that are also available via web pages ( http://rs.tdwg.org/dwc/ ). Key among the documents is http://rs.tdwg.org/dwc/rdf/dwctermshistory.rdf . This document includes descriptions of all terms, their histories, the relationships among them, and the relations between them and terms from other standards, all in a single file. The document is written in the Resource Description Framework (RDF) format, which is a standard for encoding the semantic structure of web-based resources. The same information is rendered in human-readable form on web pages (Quick Reference Guide, Type Vocabulary, Complete History, Mapping to ABCD, and Mapping to Old Versions). The standard also includes recommendations for implementation ( Introduction , Simple Darwin Core, XML Guide, and Text Guide), a document describing how the standard is to be maintained (Namespace Policy), and a document describing the rationale behind any changes that are made to the standard (Decision History). In addition to the authoritative standard, Darwin Core consists of non-normative documents, commentaries, and tools tracked separately ( http://code.google.com/p/darwincore/ ).”concepts[16]
conceptResource Description Framework — not defined in this paper's own words; format used for semantic web-resource structure — “The authoritative form of the Darwin Core is a downloadable archive [25] , which contains various documents that are also available via web pages ( http://rs.tdwg.org/dwc/ ). Key among the documents is http://rs.tdwg.org/dwc/rdf/dwctermshistory.rdf . This document includes descriptions of all terms, their histories, the relationships among them, and the relations between them and terms from other standards, all in a single file. The document is written in the Resource Description Framework (RDF) format, which is a standard for encoding the semantic structure of web-based resources. The same information is rendered in human-readable form on web pages (Quick Reference Guide, Type Vocabulary, Complete History, Mapping to ABCD, and Mapping to Old Versions). The standard also includes recommendations for implementation ( Introduction , Simple Darwin Core, XML Guide, and Text Guide), a document describing how the standard is to be maintained (Namespace Policy), and a document describing the rationale behind any changes that are made to the standard (Decision History). In addition to the authoritative standard, Darwin Core consists of non-normative documents, commentaries, and tools tracked separately ( http://code.google.com/p/darwincore/ ).”concepts[17]
concepttechnical implementation — not defined in this paper's own words; technology-specific realization separated from enduring semantics — “TDWG, as with other information standards bodies, has a history of developing data sharing standards that are bound to specific technologies, such as eXtensible Markup Language (XML). While Darwin Core is currently maintained in RDF, the enduring value of the standard lies in simple definitions of terms and their relationships to other terms, independent of technical implementation. As with Dublin Core, the idea is to promote use of the common terms in every appropriate context, and to leave the implementation details to specific applications. Data can be shared using Darwin Core in a variety of encoding schemes (Comma Separated Values, XML, JavaScript Object Notation, RDF, etc.). To aid in using Darwin Core in different contexts, there are documents with recommendations on how to share information as Darwin Core using various technologies.”concepts[18]
conceptencoding schemes — not defined in this paper's own words; CSV, XML, JSON, RDF, and other representations for sharing data — “TDWG, as with other information standards bodies, has a history of developing data sharing standards that are bound to specific technologies, such as eXtensible Markup Language (XML). While Darwin Core is currently maintained in RDF, the enduring value of the standard lies in simple definitions of terms and their relationships to other terms, independent of technical implementation. As with Dublin Core, the idea is to promote use of the common terms in every appropriate context, and to leave the implementation details to specific applications. Data can be shared using Darwin Core in a variety of encoding schemes (Comma Separated Values, XML, JavaScript Object Notation, RDF, etc.). To aid in using Darwin Core in different contexts, there are documents with recommendations on how to share information as Darwin Core using various technologies.”concepts[19]
conceptDarwin Core Archives — not defined in this paper's own words; CSV-plus-XML packages carrying records, column semantics, and relations — “The Simple Darwin Core ( http://rs.tdwg.org/dwc/terms/simple/index.htm ) document explains the capacity to share records with properties that do not repeat, as simple text files or XML. There is also an XML Guide with reference XML schemas for highly structured data and a Text Guide explaining the construction of Darwin Core Archives (a combination of CSV files and a simple XML document describing the semantics of the data file columns and their relationships to each other). Darwin Core Archives can support structured data that conform to a star schema (a single core set of records in one or more files, with one-to-one or one-to-many relationships to records in other files). The Darwin Core Archive is becoming ever more popular as an easy means for data sharing, largely due to the release of supporting tools, in particular the next-generation data publishing system – the Integrated Publishing Toolkit ( http://www.gbif.org/informatics/infrastructure/publishing ) – an open source application developed by the Global Biodiversity Information Facility discussed in further detail below. Darwin Core Archives have been adopted by Pensoft® ( http://www.pensoft.net/journals/ ) as the preferred form for data appendices to taxonomic publications in MycoKeys, PhytoKeys, and ZooKeys.”concepts[20]
conceptstar schema — not defined in this paper's own words; core records with one-to-one or one-to-many related records — “The Simple Darwin Core ( http://rs.tdwg.org/dwc/terms/simple/index.htm ) document explains the capacity to share records with properties that do not repeat, as simple text files or XML. There is also an XML Guide with reference XML schemas for highly structured data and a Text Guide explaining the construction of Darwin Core Archives (a combination of CSV files and a simple XML document describing the semantics of the data file columns and their relationships to each other). Darwin Core Archives can support structured data that conform to a star schema (a single core set of records in one or more files, with one-to-one or one-to-many relationships to records in other files). The Darwin Core Archive is becoming ever more popular as an easy means for data sharing, largely due to the release of supporting tools, in particular the next-generation data publishing system – the Integrated Publishing Toolkit ( http://www.gbif.org/informatics/infrastructure/publishing ) – an open source application developed by the Global Biodiversity Information Facility discussed in further detail below. Darwin Core Archives have been adopted by Pensoft® ( http://www.pensoft.net/journals/ ) as the preferred form for data appendices to taxonomic publications in MycoKeys, PhytoKeys, and ZooKeys.”concepts[21]
conceptIntegrated Publishing Toolkit — not defined in this paper's own words; GBIF open-source archive and metadata publisher — “The Integrated Publishing Toolkit (IPT; http://www.gbif.org/informatics/infrastructure/publishing/ ) is an open-source software development project, led by GBIF, designed to address the challenges of sharing biodiversity data. By producing and providing easy access to Darwin Core Archives and resource metadata in Ecological Markup Language [44] , the IPT works in tandem with a Global Biodiversity Resources Discovery System (GBRDS), a data registry, to facilitate discovery and retrieval of shared data throughout the world. The IPT complements other tools that have been created to assist data users to explore, organize, and mobilize data sets. A range of spreadsheet and archive creators and validators has been developed by GBIF and others. These tools can be accessed via the GBIF Publishing Software web page ( http://www.gbif.org/informatics/standards-and-tools/publishing-data/publishing-software/ ).”concepts[22]
conceptentity-relationship modeling — not defined in this paper's own words; database-design approach used for multi-user databases — “In the early 1990's, entity-relationship modeling had become accepted as a prerequisite for designing any database serving multiple users. A normalized database structure was the primary technique for enforcing data integrity. The Association of Systematic Collections (ASC) model [30] was the result of the first group effort to create a conceptual model for biological collections that accommodated the distinct taxonomic disciplines commonly found in natural history museums. The ASC model was an ontological description of the domain, but was determined at the time to be beyond the technical capabilities to implement [31] . Eventually, this model was then used as the point of departure for several collection management applications, including Specify ( http://specifysoftware.org/ ), Biota ( http://viceroy.eeb.uconn.edu/biota ), and Arctos ( http://arctos.database.museum/ ). The emphasis at that time was to develop best practice for data capture and management, not data exchange or integration.”concepts[23]
conceptnormalized database structure — not defined in this paper's own words; database organization used to enforce data integrity — “In the early 1990's, entity-relationship modeling had become accepted as a prerequisite for designing any database serving multiple users. A normalized database structure was the primary technique for enforcing data integrity. The Association of Systematic Collections (ASC) model [30] was the result of the first group effort to create a conceptual model for biological collections that accommodated the distinct taxonomic disciplines commonly found in natural history museums. The ASC model was an ontological description of the domain, but was determined at the time to be beyond the technical capabilities to implement [31] . Eventually, this model was then used as the point of departure for several collection management applications, including Specify ( http://specifysoftware.org/ ), Biota ( http://viceroy.eeb.uconn.edu/biota ), and Arctos ( http://arctos.database.museum/ ). The emphasis at that time was to develop best practice for data capture and management, not data exchange or integration.”concepts[24]
conceptASC model — not defined in this paper's own words; conceptual model for multidisciplinary biological collections — “In the early 1990's, entity-relationship modeling had become accepted as a prerequisite for designing any database serving multiple users. A normalized database structure was the primary technique for enforcing data integrity. The Association of Systematic Collections (ASC) model [30] was the result of the first group effort to create a conceptual model for biological collections that accommodated the distinct taxonomic disciplines commonly found in natural history museums. The ASC model was an ontological description of the domain, but was determined at the time to be beyond the technical capabilities to implement [31] . Eventually, this model was then used as the point of departure for several collection management applications, including Specify ( http://specifysoftware.org/ ), Biota ( http://viceroy.eeb.uconn.edu/biota ), and Arctos ( http://arctos.database.museum/ ). The emphasis at that time was to develop best practice for data capture and management, not data exchange or integration.”concepts[25]
conceptontological description — not defined in this paper's own words; formal domain account supplied by the ASC model — “In the early 1990's, entity-relationship modeling had become accepted as a prerequisite for designing any database serving multiple users. A normalized database structure was the primary technique for enforcing data integrity. The Association of Systematic Collections (ASC) model [30] was the result of the first group effort to create a conceptual model for biological collections that accommodated the distinct taxonomic disciplines commonly found in natural history museums. The ASC model was an ontological description of the domain, but was determined at the time to be beyond the technical capabilities to implement [31] . Eventually, this model was then used as the point of departure for several collection management applications, including Specify ( http://specifysoftware.org/ ), Biota ( http://viceroy.eeb.uconn.edu/biota ), and Arctos ( http://arctos.database.museum/ ). The emphasis at that time was to develop best practice for data capture and management, not data exchange or integration.”concepts[26]
conceptSpecies Analyst — not defined in this paper's own words; early biodiversity-integration tool and distributed server project — “The first successful tool to enable data integration in the biodiversity domain came to be known as the Species Analyst. A prototype based on the Z39.50 protocol [32] , which was popular in the Library Science community at that time, was deployed in a pilot project, the Z39.50 Biology Implementers Group (ZBIG, U.S. National Science Foundation NSF-DBI-9811443). An outcome of the first meeting of that project was a list of terms with definitions to be included in the profile. The name “Darwin Core” was coined by Allen Allison and adopted at that meeting. The Species Analyst, a project developed under the NSF-funded ZBIG project at the University of Kansas [33] , led to an international deployment of data servers [34] for ornithological (NSF-DBI-9808739) and ichthyological (NSF-DEB-9985737) [35] collections.”concepts[27]
conceptZ39.50 protocol — not defined in this paper's own words; library-derived protocol used by the Species Analyst prototype — “The first successful tool to enable data integration in the biodiversity domain came to be known as the Species Analyst. A prototype based on the Z39.50 protocol [32] , which was popular in the Library Science community at that time, was deployed in a pilot project, the Z39.50 Biology Implementers Group (ZBIG, U.S. National Science Foundation NSF-DBI-9811443). An outcome of the first meeting of that project was a list of terms with definitions to be included in the profile. The name “Darwin Core” was coined by Allen Allison and adopted at that meeting. The Species Analyst, a project developed under the NSF-funded ZBIG project at the University of Kansas [33] , led to an international deployment of data servers [34] for ornithological (NSF-DBI-9808739) and ichthyological (NSF-DEB-9985737) [35] collections.”concepts[28]
conceptloose federation of databases — not defined in this paper's own words; distributed research architecture targeted by early Darwin Core — “The initial purpose of the Darwin Core was to facilitate the exchange of information about the geographic and temporal occurrence of organisms in the natural world and the physical existence of specimens in biological collections. In contrast to earlier guidelines, Darwin Core was not a prescription for how to manage collection information. Instead, it was designed to circumscribe a conceptual model for a research community aiming to create a loose federation of databases and advance its research capabilities through data integration. The barriers to publishing data in Darwin Core were purposefully kept as low as possible.”concepts[29]
conceptABCD — not defined in this paper's own words; highly structured European biological-collections model — “Darwin Core was developed in parallel with efforts in Europe to establish a comprehensive model for biological collections information — Access to Biological Collections Data (ABCD) [39] . The philosophies of the two approaches were distinct, even if they both had the goal of promoting sharing of biodiversity information. Darwin Core was designed to be minimal (only terms shared in common throughout natural history collections) and flat (no relational structure), while ABCD was highly structured and sought to capture the wide variety of biodiversity data and their relationships. Both groups defined their data models in XML schemas. ABCD was ratified as a standard by TDWG in 2005. Darwin Core departed from defining the standard in XML schema and followed the DCMI model, incorporating the experience of the previous decade to establish a set of terms in wide use in practice for data sharing.”concepts[30]
conceptminimal — not defined in this paper's own words; Darwin Core design restricted to terms shared across collections — “Darwin Core was developed in parallel with efforts in Europe to establish a comprehensive model for biological collections information — Access to Biological Collections Data (ABCD) [39] . The philosophies of the two approaches were distinct, even if they both had the goal of promoting sharing of biodiversity information. Darwin Core was designed to be minimal (only terms shared in common throughout natural history collections) and flat (no relational structure), while ABCD was highly structured and sought to capture the wide variety of biodiversity data and their relationships. Both groups defined their data models in XML schemas. ABCD was ratified as a standard by TDWG in 2005. Darwin Core departed from defining the standard in XML schema and followed the DCMI model, incorporating the experience of the previous decade to establish a set of terms in wide use in practice for data sharing.”concepts[31]
conceptflat — not defined in this paper's own words; Darwin Core design without relational structure — “Darwin Core was developed in parallel with efforts in Europe to establish a comprehensive model for biological collections information — Access to Biological Collections Data (ABCD) [39] . The philosophies of the two approaches were distinct, even if they both had the goal of promoting sharing of biodiversity information. Darwin Core was designed to be minimal (only terms shared in common throughout natural history collections) and flat (no relational structure), while ABCD was highly structured and sought to capture the wide variety of biodiversity data and their relationships. Both groups defined their data models in XML schemas. ABCD was ratified as a standard by TDWG in 2005. Darwin Core departed from defining the standard in XML schema and followed the DCMI model, incorporating the experience of the previous decade to establish a set of terms in wide use in practice for data sharing.”concepts[32]
conceptflexibility — not defined in this paper's own words; capacity to work across changing technical contexts — “In combination with openness and consensus building (key aspects of the TDWG constitution: http://www.tdwg.org/about-tdwg/constitution/ ), two of the guiding principles behind Darwin Core are flexibility and adaptability. The standard has to be flexible to accommodate a variety of ever evolving technical contexts in which it might be used (spreadsheet columns, relational database fields, XML schemas and documents, non-SQL data stores, and semantic web resources). The standard has to be adaptable to accommodate growth (new terms, additional meanings) and interoperability (connections to related information). To thrive, the standard must have a means to adapt to changing needs.”concepts[33]
conceptadaptability — not defined in this paper's own words; capacity to add meanings, terms, and connections — “In combination with openness and consensus building (key aspects of the TDWG constitution: http://www.tdwg.org/about-tdwg/constitution/ ), two of the guiding principles behind Darwin Core are flexibility and adaptability. The standard has to be flexible to accommodate a variety of ever evolving technical contexts in which it might be used (spreadsheet columns, relational database fields, XML schemas and documents, non-SQL data stores, and semantic web resources). The standard has to be adaptable to accommodate growth (new terms, additional meanings) and interoperability (connections to related information). To thrive, the standard must have a means to adapt to changing needs.”concepts[34]
conceptcommunity driven — not defined in this paper's own words; development governed by public participation and consensus — “Darwin Core development is community driven and follows the process published in the Darwin Core Namespace Policy ( http://rs.tdwg.org/dwc/2009-09-23/terms/namespace/index.htm ). Open commentaries on issues related to Darwin Core are expressed through a public forum (at tdwg-content@lists.tdwg.org ) to which any subscriber may contribute. Discussions that result in consensus for change (new terms, new definitions, new relationships, changes in documentation) are submitted as change requests using templates requesting the appropriate information on the issue tracker of the Darwin Core Project site ( http://code.google.com/p/darwincore/wiki/SubmittingIssues ). Sometimes this process is reversed, with a submitted issue being copied to the discussion forum for elaboration and consensus before refining the issue as submitted. All changes undergo a 30-day public review, announced on the listserv. Changes are reviewed by TDWG's Technical Architecture Group (TAG: http://www.tdwg.org/activities/tag/ ), a set of volunteer members with broad interest and expertise in web-based interoperability. The TAG determines if the proposed changes are compatible with Darwin Core and that they do not reinvent existing standards. Changes that pass this review process are made as version changes to the affected documents, the latest of which always constitute the current standard.”concepts[35]
conceptconsensus — not defined in this paper's own words; agreement condition for advancing standard changes — “Darwin Core development is community driven and follows the process published in the Darwin Core Namespace Policy ( http://rs.tdwg.org/dwc/2009-09-23/terms/namespace/index.htm ). Open commentaries on issues related to Darwin Core are expressed through a public forum (at tdwg-content@lists.tdwg.org ) to which any subscriber may contribute. Discussions that result in consensus for change (new terms, new definitions, new relationships, changes in documentation) are submitted as change requests using templates requesting the appropriate information on the issue tracker of the Darwin Core Project site ( http://code.google.com/p/darwincore/wiki/SubmittingIssues ). Sometimes this process is reversed, with a submitted issue being copied to the discussion forum for elaboration and consensus before refining the issue as submitted. All changes undergo a 30-day public review, announced on the listserv. Changes are reviewed by TDWG's Technical Architecture Group (TAG: http://www.tdwg.org/activities/tag/ ), a set of volunteer members with broad interest and expertise in web-based interoperability. The TAG determines if the proposed changes are compatible with Darwin Core and that they do not reinvent existing standards. Changes that pass this review process are made as version changes to the affected documents, the latest of which always constitute the current standard.”concepts[36]
conceptdata quality — not defined in this paper's own words; fitness and reliability of heterogeneous biodiversity records — “Data quality and fitness for use are primary concerns in the biodiversity community [42] , where information comes from heterogeneous sources spanning the globe over hundreds of years. Both data discovery and data quality assessment are hampered by this heterogeneity. Part of the solution depends on the use of common vocabularies, part on dictionaries of synonymous terms, and a great deal on applications that can facilitate discovery and assessment in place of or to aid in otherwise labor-intensive “cleanups”. For example, having a dictionary that equates “voucher” and “sample” with an accepted term “PreservedSpecimen” would allow applications to make this substitution automatically and allow users to discover relevant data using any of the synonyms regardless of how they were stored in the original data.”concepts[37]
conceptfitness for use — not defined in this paper's own words; suitability of data for a particular analytical purpose — “Data quality and fitness for use are primary concerns in the biodiversity community [42] , where information comes from heterogeneous sources spanning the globe over hundreds of years. Both data discovery and data quality assessment are hampered by this heterogeneity. Part of the solution depends on the use of common vocabularies, part on dictionaries of synonymous terms, and a great deal on applications that can facilitate discovery and assessment in place of or to aid in otherwise labor-intensive “cleanups”. For example, having a dictionary that equates “voucher” and “sample” with an accepted term “PreservedSpecimen” would allow applications to make this substitution automatically and allow users to discover relevant data using any of the synonyms regardless of how they were stored in the original data.”concepts[38]
conceptcommon vocabularies — not defined in this paper's own words; shared controlled terms supporting discovery and assessment — “Data quality and fitness for use are primary concerns in the biodiversity community [42] , where information comes from heterogeneous sources spanning the globe over hundreds of years. Both data discovery and data quality assessment are hampered by this heterogeneity. Part of the solution depends on the use of common vocabularies, part on dictionaries of synonymous terms, and a great deal on applications that can facilitate discovery and assessment in place of or to aid in otherwise labor-intensive “cleanups”. For example, having a dictionary that equates “voucher” and “sample” with an accepted term “PreservedSpecimen” would allow applications to make this substitution automatically and allow users to discover relevant data using any of the synonyms regardless of how they were stored in the original data.”concepts[39]
conceptdictionaries of synonymous terms — not defined in this paper's own words; mappings from alternate labels to accepted terms — “Data quality and fitness for use are primary concerns in the biodiversity community [42] , where information comes from heterogeneous sources spanning the globe over hundreds of years. Both data discovery and data quality assessment are hampered by this heterogeneity. Part of the solution depends on the use of common vocabularies, part on dictionaries of synonymous terms, and a great deal on applications that can facilitate discovery and assessment in place of or to aid in otherwise labor-intensive “cleanups”. For example, having a dictionary that equates “voucher” and “sample” with an accepted term “PreservedSpecimen” would allow applications to make this substitution automatically and allow users to discover relevant data using any of the synonyms regardless of how they were stored in the original data.”concepts[40]
conceptsemantic web — not defined in this paper's own words; linked information environment in which Darwin Core integration was immature — “Though the Darwin Core is defined in an RDF document, integration of biodiversity data in the semantic web is in its early stages. One of the major challenges for Darwin Core in the semantic web context is the lack of a well-defined ontology - a formal definition of relationships between terms in a defined domain. An ontology would define the relationships between concepts such as biological entities, the events that document where and when they occurred, and the processes through which they are identified as being representative of a taxonomic concept. Without rigorous relationships between concepts and the properties that define them, connections between biodiversity data and related semantically rich information, such as literature and genomes, are difficult to traverse. This creates obstacles to cross-disciplinary semantic inquiry, such as in the Linked Data distributed data community ( http://linkeddata.org/ ). Current research is trying to address this gap (see TaxonConcept Knowledge Base, http://www.taxonconcept.org/ and BiSciCol, http://biscicol.blogspot.com/ ), active discussions on various aspects of the challenge take place regularly on the Darwin Core public forum ( http://lists.tdwg.org/mailman/listinfo/tdwg-content ), and an RDF task group has been established within TDWG “to adapt TDWG vocabularies for use as RDF classes and properties and to integrate those resources with other well-known vocabularies and ontologies outside TDWG for use in describing biodiversity resources.” [43]”concepts[41]
conceptontology — not defined in this paper's own words; formal relationship definition for terms in a domain — “Though the Darwin Core is defined in an RDF document, integration of biodiversity data in the semantic web is in its early stages. One of the major challenges for Darwin Core in the semantic web context is the lack of a well-defined ontology - a formal definition of relationships between terms in a defined domain. An ontology would define the relationships between concepts such as biological entities, the events that document where and when they occurred, and the processes through which they are identified as being representative of a taxonomic concept. Without rigorous relationships between concepts and the properties that define them, connections between biodiversity data and related semantically rich information, such as literature and genomes, are difficult to traverse. This creates obstacles to cross-disciplinary semantic inquiry, such as in the Linked Data distributed data community ( http://linkeddata.org/ ). Current research is trying to address this gap (see TaxonConcept Knowledge Base, http://www.taxonconcept.org/ and BiSciCol, http://biscicol.blogspot.com/ ), active discussions on various aspects of the challenge take place regularly on the Darwin Core public forum ( http://lists.tdwg.org/mailman/listinfo/tdwg-content ), and an RDF task group has been established within TDWG “to adapt TDWG vocabularies for use as RDF classes and properties and to integrate those resources with other well-known vocabularies and ontologies outside TDWG for use in describing biodiversity resources.” [43]”concepts[42]
conceptDarwin Core Extension — not defined in this paper's own words; specialized terms or domain-use guidance complementing the core — “Because Darwin Core aims to cover the common ground in biodiversity, it inevitably lacks terms that are of interest to more specialized groups. A Darwin Core Extension consists of additional terms describing a complementary, related domain, or guidance on the use of Darwin Core within a specific sub-domain of biodiversity. Over the last decade, Darwin Core has evolved by means of extensions, some of which have been incorporated in the standard. For example, the terms of a paleontology extension related to an earlier, pre-standard version of Darwin Core became the terms of the current GeologicalContext class. Similarly, terms originating from an early version of the Darwin Core created for the Ocean Biogeographic Information System (OBIS; http://www.iobis.org/ ) have also been added to Darwin Core. Going forward, specific projects or disciplines may find it convenient to extend the scope of Darwin Core outside the existing namespace and governance process for proof-of-concept research. Once the understanding of the new terms has been tested and proven of utility in a broader context, incorporation into the standard can be accomplished through community consensus.”concepts[43]
conceptGNA Profile — not defined in this paper's own words; taxonomic extensions supporting rich checklist data — “A set of taxonomic extensions collectively known as the “GNA Profile” (named for the Global Names Architecture) [48] – [49] have been designed by GBIF with input from Catalogue of Life ( http://www.catalogueoflife.org/ ), Encyclopedia of Life ( http://eol.org/ ), nomenclators, and other taxonomic initiatives. These extensions ( http://rs.gbif.org/extension/gbif/1.0/ ), together with the taxonomic terms of Darwin Core, allow sharing of rich taxonomic data often found in species checklists. The extensions are designed to be used in a one-to-many relationship with core taxon records, allowing the sharing of structured data such as vernacular names, species range distributions, textual descriptions, type species and specimens, image data, and bibliographies.”concepts[44]
conceptAudubon Core — not defined in this paper's own words; proposed biodiversity multimedia-resource standard — “An effort is underway within TDWG to create a standard for biodiversity multimedia resources and collections, called the Audubon Core [50] . The proposal introduces vocabularies covering the management and content of biodiversity-related media and their taxonomic, geographic, and temporal scope. Audubon Core adopts by inclusion a number of terms from Darwin Core, which can reduce the burden on existing media publishers who may have already used Darwin Core terms for describing the media content.”concepts[45]
conceptMIxS — not defined in this paper's own words; minimum-information standard for genomes, metagenomes, and marker-gene studies — “In collaboration with the Genomic Standards Consortium (GSC; http://gensc.org/ ) [51] , Darwin Core is now being extended to cover DNA-level observations (genomes, metagenomes, and gene marker sequences). The GSC, a standards body similar in scope to Biodiversity Information Standards (TDWG), is working to “standardize the description of genomic data and promote the exchange and integration of genomic data. [52] .” Advances in technology have made sequence-based diversity assessments increasingly routine in biodiversity research. The GSC has developed the MIxS (Minimum Information about any (x) Sequence) standard containing checklists for describing genomes, metagenomes, and marker gene studies. Conceptually this approach is similar to Darwin Core in that it defines terms for the description of data, but differs in that it requires the reporting a certain minimum set of descriptors such as environmental and geographic origin and details about sample and sequencing processing in addition to any kind of genomic sequence.”concepts[46]
conceptaggregation tools — not defined in this paper's own words; systems combining distributed biodiversity records for analysis — “The creation of a standard format for biodiversity data, the development of aggregation tools, and the increasing use of Darwin Core Archives have helped to overcome the challenge of limited availability of data to answer questions about biodiversity. As more data become digitized and discoverable, biocollections can become a window into broader analyses of ecological, climate, niche, environmental, and biological research questions and critical issues.”concepts[47]
conceptREBIOMA — not defined in this paper's own words; Madagascar biodiversity integration and modeling resource — “Though predated by examples of the effective use of Darwin Core for distribution modeling, influence of natural area preservation, and estimates of climate change impact [53] , the utility of data shared using Darwin Core is illustrated by two recent examples. First, the University of California, Berkeley, and the Wildlife Conservation Society have collaborated to create Réseau de la Biodiversité de Madagascar (REBIOMA, http://www.rebioma.net/ ).The effort seeks to make biodiversity data about Madagascar available via a single web-based resource. Primary data on biodiversity in Madagascar come from researchers and institutions all over the world. REBIOMA works with each collection to standardize the data using the Darwin Core, to mobilize and aggregate the data, and to vet the data for quality, completeness, and fitness for use. Data passing automated quality checks and review by a board of taxonomic experts are analyzed in combination with environmental data to produce maps showing models of where species might occur. The success of this project has made it possible for researchers, policy makers, government officials, and conservationists to capture a wealth of data to address issues of Malagasy biodiversity. The simplicity and flexibility of Darwin Core has made it possible for REBIOMA to provide immediate access to high-quality data and tools for monitoring and assessing conservation efforts.”concepts[48]
conceptMap of Life — not defined in this paper's own words; knowledge-base project integrating distribution data and models — “A second example of innovative use of Darwin Core data is the Map of Life Project ( http://www.mappinglife.org/ ), and sister projects such as LifeMapper ( http://www.lifemapper.org/ ) [54] , which aggregate and mobilize sources of species distribution information and provide tools to visualize and analyses those data. In Map of Life, species occurrence data points formatted as Darwin Core are queried and brought into the application with related data sources such as range maps, assemblage checklists, and habitat preference data. Integration of these data types and modeling will lead to summary products describing species distributions and provide the basis for distribution change assessments in the face of human-induced global changes [55] . The Map of Life will be a knowledge base of hundreds of thousands of high-resolution species distribution maps covering a wide range of taxa and geographic locations.”concepts[49]
conceptliving standard — not defined in this paper's own words; community-maintained specification that continues to grow — “Darwin Core is a living standard. Although its roots were planted in the vertebrate natural history collections community, Darwin Core continues to grow to serve the needs of biodiversity research. This growth, over the relatively short period of a decade, speaks both to the need for such a standard and to the efforts of its champions to increase its utility through a community development process in order to meet increasing demand. Darwin Core greatly increases the value and re-use of freely available and accessible biodiversity data so that they can be effectively mobilized, integrated, and incorporated into other “grand challenge” scientific endeavors.”concepts[50]
conceptlack of a coordinated publishing and integration system — not defined in this paper's own words; absence of shared biodiversity-data infrastructure — “A general challenge of biodiversity data that is shared with many other information domains is the lack of a coordinated publishing and integration system; data repositories tend to be isolated from each other in the absence of standards for data and communication protocols. Heterogeneity in meaning and content of terms creates obstacles in every aspect of data integration and use, including discovery, comparison, and quality assessment. Information communities, especially Library Information Sciences, have a long history of meeting these challenges through the creation and maintenance of standards.”concepts[51]
conceptdata repositories — not defined in this paper's own words; stores that remain isolated without standards and protocols — “A general challenge of biodiversity data that is shared with many other information domains is the lack of a coordinated publishing and integration system; data repositories tend to be isolated from each other in the absence of standards for data and communication protocols. Heterogeneity in meaning and content of terms creates obstacles in every aspect of data integration and use, including discovery, comparison, and quality assessment. Information communities, especially Library Information Sciences, have a long history of meeting these challenges through the creation and maintenance of standards.”concepts[52]
conceptHeterogeneity in meaning and content of terms — not defined in this paper's own words; semantic variation across biodiversity sources — “A general challenge of biodiversity data that is shared with many other information domains is the lack of a coordinated publishing and integration system; data repositories tend to be isolated from each other in the absence of standards for data and communication protocols. Heterogeneity in meaning and content of terms creates obstacles in every aspect of data integration and use, including discovery, comparison, and quality assessment. Information communities, especially Library Information Sciences, have a long history of meeting these challenges through the creation and maintenance of standards.”concepts[53]
conceptobstacles in every aspect of data integration and use — not defined in this paper's own words; discovery, comparison, and quality barriers from heterogeneity — “A general challenge of biodiversity data that is shared with many other information domains is the lack of a coordinated publishing and integration system; data repositories tend to be isolated from each other in the absence of standards for data and communication protocols. Heterogeneity in meaning and content of terms creates obstacles in every aspect of data integration and use, including discovery, comparison, and quality assessment. Information communities, especially Library Information Sciences, have a long history of meeting these challenges through the creation and maintenance of standards.”concepts[54]
conceptsimple definitions of terms — not defined in this paper's own words; technology-independent semantic core of Darwin Core — “TDWG, as with other information standards bodies, has a history of developing data sharing standards that are bound to specific technologies, such as eXtensible Markup Language (XML). While Darwin Core is currently maintained in RDF, the enduring value of the standard lies in simple definitions of terms and their relationships to other terms, independent of technical implementation. As with Dublin Core, the idea is to promote use of the common terms in every appropriate context, and to leave the implementation details to specific applications. Data can be shared using Darwin Core in a variety of encoding schemes (Comma Separated Values, XML, JavaScript Object Notation, RDF, etc.). To aid in using Darwin Core in different contexts, there are documents with recommendations on how to share information as Darwin Core using various technologies.”concepts[55]
conceptcreation and publication of Darwin Core Archives relatively simple — not defined in this paper's own words; reduced publication burden attributed to GBIF tools — “A variety of tools has been developed to simplify the mobilization and sharing of biodiversity data using the Darwin Core. Many of these tools focus on the creation or validation of Darwin Core Archives ( http://code.google.com/p/darwincore/wiki/ToolsAndApplications#Tools ). The Global Biodiversity Information Facility (GBIF), an international organization promoting the free and open access to biodiversity data online, has invested heavily in the open and collaborative development of tools ( http://tools.gbif.org/ ) to make the creation and publication of Darwin Core Archives relatively simple.”concepts[56]
conceptlimited availability of data — not defined in this paper's own words; insufficient accessible information for broad biodiversity questions — “The creation of a standard format for biodiversity data, the development of aggregation tools, and the increasing use of Darwin Core Archives have helped to overcome the challenge of limited availability of data to answer questions about biodiversity. As more data become digitized and discoverable, biocollections can become a window into broader analyses of ecological, climate, niche, environmental, and biological research questions and critical issues.”concepts[57]
conceptvalue and re-use — not defined in this paper's own words; benefit increased by mobilizing and integrating accessible data — “Darwin Core is a living standard. Although its roots were planted in the vertebrate natural history collections community, Darwin Core continues to grow to serve the needs of biodiversity research. This growth, over the relatively short period of a decade, speaks both to the need for such a standard and to the efforts of its champions to increase its utility through a community development process in order to meet increasing demand. Darwin Core greatly increases the value and re-use of freely available and accessible biodiversity data so that they can be effectively mobilized, integrated, and incorporated into other “grand challenge” scientific endeavors.”concepts[58]
conceptstandard for sharing data about biodiversity — not defined in this paper's own words; specific class description given for Darwin Core — “Darwin Core [20] is a standard for sharing data about biodiversity – the occurrence of life on earth and its associations with the environment. Darwin Core first emerged around 1999 as a loosely defined set of terms, and progressed through several iterations by different groups resulting in many different variants [21] . A formal set of terms and processes to manage changes were necessary to ensure utility for data integration. These aspects were developed within the Darwin Core Task Group [22] of the Taxonomic Databases Working Group (TDWG; www.tdwg.org ) and ratified as a standard in October 2009. The philosophy for Darwin Core development has been to keep the standard as simple and open as possible and to develop terms only when there is shared demand. Darwin Core has a relatively long history of community development and is deployed widely [23] – [24] . For example, the Global Biodiversity Information Facility currently indexes approximately 300 million Darwin Core-formatted records published by more than 340 organizations in 43 countries. Increasingly, Darwin Core is being incorporated in communities beyond that of natural history collections ( Figure 1 ), in which the standard has its roots.”concepts[59]
conceptset of terms — not defined in this paper's own words; semantic units constituting Darwin Core — “Fundamentally, Darwin Core is a set of terms having clearly defined semantics that can be understood by people or interpreted by machines, making it possible to determine appropriate uses of the data encoded therein. The terms are organized into nine categories (often referred to as “classes”, Figure 2 ), six of which cover broad aspects (event, location, geological context, occurrence, taxon, and identification) of the biodiversity domain. The remaining categories cover relationships to other resources, measurements, and generic information about records. Especially for the record level, Darwin Core recommends the use of a number of terms from Dublin Core (type, modified, language, rights, rightsHolder, accessRights, bibliographicCitation, references). The full set of current Darwin Core terms with their descriptions is available in the Quick Reference Guide ( http://rs.tdwg.org/dwc/terms/ ).”concepts[60]
conceptstandard for encoding the semantic structure of web-based resources — not defined in this paper's own words; specific class description given for RDF — “The authoritative form of the Darwin Core is a downloadable archive [25] , which contains various documents that are also available via web pages ( http://rs.tdwg.org/dwc/ ). Key among the documents is http://rs.tdwg.org/dwc/rdf/dwctermshistory.rdf . This document includes descriptions of all terms, their histories, the relationships among them, and the relations between them and terms from other standards, all in a single file. The document is written in the Resource Description Framework (RDF) format, which is a standard for encoding the semantic structure of web-based resources. The same information is rendered in human-readable form on web pages (Quick Reference Guide, Type Vocabulary, Complete History, Mapping to ABCD, and Mapping to Old Versions). The standard also includes recommendations for implementation ( Introduction , Simple Darwin Core, XML Guide, and Text Guide), a document describing how the standard is to be maintained (Namespace Policy), and a document describing the rationale behind any changes that are made to the standard (Decision History). In addition to the authoritative standard, Darwin Core consists of non-normative documents, commentaries, and tools tracked separately ( http://code.google.com/p/darwincore/ ).”concepts[61]
conceptopen-source software development project — not defined in this paper's own words; specific class description given for the IPT — “The Integrated Publishing Toolkit (IPT; http://www.gbif.org/informatics/infrastructure/publishing/ ) is an open-source software development project, led by GBIF, designed to address the challenges of sharing biodiversity data. By producing and providing easy access to Darwin Core Archives and resource metadata in Ecological Markup Language [44] , the IPT works in tandem with a Global Biodiversity Resources Discovery System (GBRDS), a data registry, to facilitate discovery and retrieval of shared data throughout the world. The IPT complements other tools that have been created to assist data users to explore, organize, and mobilize data sets. A range of spreadsheet and archive creators and validators has been developed by GBIF and others. These tools can be accessed via the GBIF Publishing Software web page ( http://www.gbif.org/informatics/standards-and-tools/publishing-data/publishing-software/ ).”concepts[62]
conceptearlier guidelines — not defined in this paper's own words; collection-management prescriptions contrasted with Darwin Core — “The initial purpose of the Darwin Core was to facilitate the exchange of information about the geographic and temporal occurrence of organisms in the natural world and the physical existence of specimens in biological collections. In contrast to earlier guidelines, Darwin Core was not a prescription for how to manage collection information. Instead, it was designed to circumscribe a conceptual model for a research community aiming to create a loose federation of databases and advance its research capabilities through data integration. The barriers to publishing data in Darwin Core were purposefully kept as low as possible.”concepts[63]
conceptA variety of tools — not defined in this paper's own words; GBIF-supported software for archive creation and validation — “A variety of tools has been developed to simplify the mobilization and sharing of biodiversity data using the Darwin Core. Many of these tools focus on the creation or validation of Darwin Core Archives ( http://code.google.com/p/darwincore/wiki/ToolsAndApplications#Tools ). The Global Biodiversity Information Facility (GBIF), an international organization promoting the free and open access to biodiversity data online, has invested heavily in the open and collaborative development of tools ( http://tools.gbif.org/ ) to make the creation and publication of Darwin Core Archives relatively simple.”concepts[64]
conceptstandard format for biodiversity data — not defined in this paper's own words; common representation used with aggregation tools and archives — “The creation of a standard format for biodiversity data, the development of aggregation tools, and the increasing use of Darwin Core Archives have helped to overcome the challenge of limited availability of data to answer questions about biodiversity. As more data become digitized and discoverable, biocollections can become a window into broader analyses of ecological, climate, niche, environmental, and biological research questions and critical issues.”concepts[65]

Full text — tagged

The reference list is not part of the text we hold for this paper. Our copy was extracted from the publisher's page and the bibliography did not survive that extraction, so the article below ends before its references. Nothing has been removed by us.

Darwin Coreterm: An Evolving Community-Developed Biodiversity Dataterm Standard Abstract Biodiversity dataterm derive from myriad sources stored in various formats on many distinct hardware and software platforms. An essential step towards understanding global patterns of biodiversity is to provide a standardized viewterm of these heterogeneous data sources to improve interoperabilityterm. Fundamental to this advance are definitions of common termsterm. This paper describes the evolution and development of Darwin Coreterm, a data standardterm for publishing and integrating biodiversity informationterm. We focus on the categoriesterm·var of terms that define the standard, differences between simple and relational Darwin Coreterm, how the standard has been implemented, and the community processes that are essential for maintenance and growth of the standard. We present case-study extensions of the Darwin Coreterm into new research communities, including metagenomics and genetic resources. We close by showing how Darwin Coreterm records are integrated to create new knowledge products documenting species distributions and changes due to environmental perturbations.

Introduction Concern over global loss of biodiversity [1] – [5] has resulted in widespread demand for quick, reliable access to high-quality data on the spatio-temporal occurrence of species and their relation to the environment. Initial studies have documented the response by species to diverse agents of environmental change [6] – [7] , including alarming vertebrate extinctions [8] . The signature of climate and other environmental changes and their effects on biodiversity is now well documented, and the evidence is overwhelming [9] – [14] .

The documentation of global patterns of biodiversity change is an important first step toward a wise, sustainable policy of conservation and management in the face of a changing environment [15] . Such documentation has emerged as a global priority [16] – [18] . A major impediment to creating this documentation is the lack of easily accessible data at the scope and at the scales needed. Most studies documenting biodiversity changes are limited to a few well-studied species or to small temporal and spatial scales [19] . To make effective use of existing data for broad-scale analyses, community coordination is required. Information must be in digital form, accessible, discoverable, and integrated. Each of these criteria presents distinct challenges, some of which are unique to biodiversity-related data.

A general challenge of biodiversity dataterm that is shared with many other information domains is the lack of a coordinated publishing and integration systemterm; data repositoriesterm tend to be isolated from each other in the absence of standards for data and communication protocols. Heterogeneity in meaning and content of termsterm creates obstacles in every aspect of data integration and useterm, including discovery, comparison, and quality assessment. Information communities, especially Library Information Sciences, have a long history of meeting these challenges through the creation and maintenance of standards.

Darwin Coreterm [20] is a standard for sharing data about biodiversityterm – the occurrence of life on earth and its associations with the environment. Darwin Coreterm first emerged around 1999 as a loosely defined set of termsterm, and progressed through several iterations by different groups resulting in many different variants [21] . A formal set of termsterm and processes to manage changes were necessary to ensure utility for data integration. These aspects were developed within the Darwin Coreterm Task Group [22] of the Taxonomic Databases Working Group (TDWG; www.tdwg.org ) and ratified as a standard in October 2009. The philosophy for Darwin Coreterm development has been to keep the standard as simple and open as possible and to develop terms only when there is shared demand. Darwin Coreterm has a relatively long history of community development and is deployed widely [23] – [24] . For example, the Global Biodiversity Informationterm Facility currently indexes approximately 300 million Darwin Core-formatted records published by more than 340 organizations in 43 countries. Increasingly, Darwin Coreterm is being incorporated in communities beyond that of natural history collections ( Figure 1 ), in which the standard has its roots.

Scope of Darwin Coreterm: The Standard, deriving from previous standards work (e.g., Dublin Coreterm), describes core sets (e.g., organismal, taxonomic) of characteristics of biodiversity, which are applicable in many biological domains (e.g., Paleontology, Botany). The standard can be extended to cover details of specific sub-disciplines (e.g., Genetic Resources, Herbaria, Taxonomic Checklists). Collaborations with other standards organizations (Genomics Standards Consortium (GSC) extend Darwin Coreterm for new disciplines (Genomics, Metagenomics, Gene Marker Sequences.

In this paper, we describe the Darwin Coreterm standard, its history, status, relationship to other standards, and prospects for further evolution. We also discuss how data sets are brought into Darwin Coreterm compliance and how Darwin Coreterm records are currently shared in a distributed publishing platform. We will demonstrate how Darwin Coreterm continues to extend beyond its original formulation for natural history collections and will present, via use cases, how the standard continues to be reshaped and extended through new collaborations. We close by discussing innovative computational and informatics approaches to improving the scale, scope, and usability of networks that rely on Darwin Coreterm compliant records.

Methods Defining Darwin Coreterm The primary purpose of Darwin Coreterm is to create a common languageterm for sharing biodiversity dataterm that is complementary to and reuses metadata standards from other domains wherever possible. Creating this common languageterm has been particularly challenging, since natural history data curation practices have been developed locally and organically over hundreds of years, have varied between disciplines as well as institutions, and have had limited culture of data sharing.

Fundamentally, Darwin Coreterm is a set of termsterm having clearly defined semanticsterm that can be understood by peopleterm or interpreted by machinesterm, making it possible to determine appropriate uses of the data encoded therein. The terms are organized into nine categoriesterm (often referred to as “classes”, Figure 2 ), six of which cover broad aspects (event, location, geological context, occurrence, taxon, and identification) of the biodiversity domain. The remaining categoriesterm·var cover relationships to other resources, measurements, and generic information about records. Especially for the record level, Darwin Coreterm recommends the use of a number of terms from Dublin Coreterm (type, modified, language, rights, rightsHolder, accessRights, bibliographicCitation, references). The full set of current Darwin Coreterm terms with their descriptions is available in the Quick Reference Guide ( http://rs.tdwg.org/dwc/terms/ ).

Darwin Coreterm Categoriesterm·var: Simple Darwin Coreterm is comprised of seven categories of termsterm (green). This subset of Darwin Coreterm terms represents descriptive data about organisms that can be represented in one file with one row per record and one column per term. Two additional categoriesterm·var (orange) expand Darwin Coreterm with concepts that require a more complex data structure, such as multiple measurements from a single specimen, and cannot be represented easily in Simple Darwin Coreterm.

The authoritative formterm of the Darwin Coreterm is a downloadable archive [25] , which contains various documents that are also available via web pages ( http://rs.tdwg.org/dwc/ ). Key among the documents is http://rs.tdwg.org/dwc/rdf/dwctermshistory.rdf . This document includes descriptions of all terms, their histories, the relationships among them, and the relations between them and terms from other standards, all in a single file. The document is written in the Resource Description Frameworkterm (RDF) format, which is a standard for encoding the semantic structure of web-based resourcesterm. The same information is rendered in human-readable form on web pages (Quick Reference Guide, Type Vocabulary, Complete History, Mapping to ABCDterm, and Mapping to Old Versions). The standard also includes recommendations for implementation ( Introduction , Simple Darwin Coreterm, XML Guide, and Text Guide), a document describing how the standard is to be maintained (Namespace Policy), and a document describing the rationale behind any changes that are made to the standard (Decision History). In addition to the authoritative standard, Darwin Coreterm consists of non-normative documents, commentaries, and tools tracked separately ( http://code.google.com/p/darwincore/ ).

Though the scope and governance of Darwin Coreterm are distinct from Dublin Coreterm [26] , readers will recognize the ancestry of Darwin Coreterm in their shared traits: mission, principles of operation, and inherited terms. Indeed, if words were nucleotides, the Darwin Coreterm mission is the same as that of Dublin Coreterm except for one base-pair addition (in bold), namely, “to provide simple standards to facilitate the finding, sharing and management of biodiversity informationterm.” This relationship is not accidental. The Dublin Coreterm Metadata Initiative (DCMI) has done a very good job of maintaining the metadata specifications at the core of web-based resources. The success of DCMI encouraged TDWG to adopt similar policies for the specific domain of biodiversity through the Darwin Coreterm. This process, in turn, acts as the basis for the development of data standardsterm for even more specific sub-disciplines (e.g., plant genetic resources) as well as a basis for collaboration with complementary related domains (e.g., metagenomics).

Implementation Guidelines TDWG, as with other information standards bodies, has a history of developing data sharing standards that are bound to specific technologies, such as eXtensible Markup Language (XML). While Darwin Coreterm is currently maintained in RDF, the enduring value of the standard lies in simple definitions of termsterm and their relationships to other terms, independent of technical implementationterm. As with Dublin Coreterm, the idea is to promote use of the common termsterm in every appropriate context, and to leave the implementation details to specific applications. Data can be shared using Darwin Coreterm in a variety of encoding schemesterm (Comma Separated Values, XML, JavaScript Object Notation, RDF, etc.). To aid in using Darwin Coreterm in different contexts, there are documents with recommendations on how to share information as Darwin Coreterm using various technologies.

The Simple Darwin Coreterm ( http://rs.tdwg.org/dwc/terms/simple/index.htm ) document explains the capacity to share records with properties that do not repeat, as simple text files or XML. There is also an XML Guide with reference XML schemas for highly structured data and a Text Guide explaining the construction of Darwin Core Archivesterm (a combination of CSV files and a simple XML document describing the semanticsterm·var of the data file columns and their relationships to each other). Darwin Core Archivesterm can support structured data that conform to a star schematerm (a single core set of records in one or more files, with one-to-one or one-to-many relationships to records in other files). The Darwin Core Archiveterm is becoming ever more popular as an easy means for data sharing, largely due to the release of supporting tools, in particular the next-generation data publishing system – the Integrated Publishing Toolkitterm ( http://www.gbif.org/informatics/infrastructure/publishing ) – an open source application developed by the Global Biodiversity Informationterm Facility discussed in further detail below. Darwin Core Archivesterm have been adopted by Pensoft® ( http://www.pensoft.net/journals/ ) as the preferred form for data appendices to taxonomic publications in MycoKeys, PhytoKeys, and ZooKeys.

Results Development and Ratification as a Standard Darwin Coreterm's development spans more than a decade, but rests on the earlier work of academic societies that addressed how to document or catalog specimens in natural history collections. Those societies put forward prescriptive guidelines about how to catalog specimens properly, first on paper and later in computer databases [27] – [29] . The purpose was to promote completeness in capture and consistency in representation or encoding. Actual data exchange and integration was anticipated as a future capability, but these guidelines preceded the Internet and World Wide Web.

In the early 1990's, entity-relationship modelingterm had become accepted as a prerequisite for designing any database serving multiple users. A normalized database structureterm was the primary technique for enforcing data integrity. The Association of Systematic Collections (ASC) model [30] was the result of the first group effort to create a conceptual model for biological collections that accommodated the distinct taxonomic disciplines commonly found in natural history museums. The ASC modelterm was an ontological descriptionterm of the domain, but was determined at the time to be beyond the technical capabilities to implement [31] . Eventually, this model was then used as the point of departure for several collection management applications, including Specify ( http://specifysoftware.org/ ), Biota ( http://viceroy.eeb.uconn.edu/biota ), and Arctos ( http://arctos.database.museum/ ). The emphasis at that time was to develop best practice for data capture and management, not data exchange or integration.

The first successful tool to enable data integration in the biodiversity domain came to be known as the Species Analystterm. A prototype based on the Z39.50 protocolterm [32] , which was popular in the Library Science community at that time, was deployed in a pilot project, the Z39.50 Biology Implementers Group (ZBIG, U.S. National Science Foundation NSF-DBI-9811443). An outcome of the first meeting of that project was a list of terms with definitions to be included in the profile. The name “Darwin Coreterm” was coined by Allen Allison and adopted at that meeting. The Species Analystterm, a project developed under the NSF-funded ZBIG project at the University of Kansas [33] , led to an international deployment of data servers [34] for ornithological (NSF-DBI-9808739) and ichthyological (NSF-DEB-9985737) [35] collections.

The initial purpose of the Darwin Coreterm was to facilitate the exchange of information about the geographic and temporal occurrence of organisms in the natural world and the physical existence of specimens in biological collections. In contrast to earlier guidelinesterm, Darwin Coreterm was not a prescription for how to manage collection information. Instead, it was designed to circumscribe a conceptual model for a research community aiming to create a loose federation of databasesterm and advance its research capabilities through data integration. The barriers to publishing data in Darwin Coreterm were purposefully kept as low as possible.

The informal Darwin Coreterm terms developed for Species Analystterm were further refined under the NSF-funded Mammal Networked Information System project (MaNIS, NSF-DBI-0108161, http://manisnet.org ) [36] and the Ornithological Information System project (ORNIS NSF-DBI-0345448, http://ornisnet.org ) [37] . Major goals of the MaNIS project were to employ HTTP as the transport protocol instead of the less widely used Z39.50, to create a message protocol to support web-based distributed queries (Distributed Generic Information Retrieval – DiGIR), and to enhance the set of termsterm to include information such as georeferences based on guidelines that address the capture of data qualityterm metrics [38] . The goal under ORNIS was to make sure that the Darwin Coreterm underwent the process of becoming a formal standard.

Darwin Coreterm was developed in parallel with efforts in Europe to establish a comprehensive model for biological collections information — Access to Biological Collections Data (ABCDterm) [39] . The philosophies of the two approaches were distinct, even if they both had the goal of promoting sharing of biodiversity informationterm. Darwin Coreterm was designed to be minimalterm (only terms shared in common throughout natural history collections) and flatterm (no relational structure), while ABCDterm was highly structured and sought to capture the wide variety of biodiversity dataterm and their relationships. Both groups defined their data models in XML schemas. ABCDterm was ratified as a standard by TDWG in 2005. Darwin Coreterm departed from defining the standard in XML schema and followed the DCMI model, incorporating the experience of the previous decade to establish a set of termsterm in wide use in practice for data sharing.

Prior to ratification, Darwin Coreterm had a history of versions [21] , each attempting to adapt to expanding community-defined needsterm·var. The earliest versions were limited to defining terms for biological specimens in collections. Continued development in sectors of the community produced versions with added capabilities targeting observations [40] and paleontology [41] . Standard Darwin Coreterm reconciles the omissions from, incompatibilities between, and inconsistencies within previous versions and provides mappings to the out-dated terms as well as mappings to concepts in the ABCDterm Schema. In addition, terms were added to enable the transmission of taxonomic name and classification data sets. The result is a relatively simple and stable specification, which serves the needs of data publishers, data consumers, and application developers to work with primary biodiversity dataterm.

Darwin Coreterm underwent a year of document development by the Darwin Coreterm Task Group with support from the National Science Foundation and the Global Biodiversity Informationterm Facility. The draft standard underwent review with public commentary before being ratified by the TDWG Executive Committee in October 2009.

Maintenance and Evolution In combination with openness and consensusterm building (key aspects of the TDWG constitution: http://www.tdwg.org/about-tdwg/constitution/ ), two of the guiding principles behind Darwin Coreterm are flexibilityterm and adaptabilityterm. The standard has to be flexible to accommodate a variety of ever evolving technical contexts in which it might be used (spreadsheet columns, relational database fields, XML schemas and documents, non-SQL data stores, and semantic webterm resources). The standard has to be adaptable to accommodate growth (new terms, additional meanings) and interoperabilityterm (connections to related information). To thrive, the standard must have a means to adapt to changing needs.

Darwin Coreterm development is community driventerm and follows the process published in the Darwin Coreterm Namespace Policy ( http://rs.tdwg.org/dwc/2009-09-23/terms/namespace/index.htm ). Open commentaries on issues related to Darwin Coreterm are expressed through a public forum (at tdwg-content@lists.tdwg.org ) to which any subscriber may contribute. Discussions that result in consensusterm for change (new terms, new definitions, new relationships, changes in documentation) are submitted as change requests using templates requesting the appropriate information on the issue tracker of the Darwin Coreterm Project site ( http://code.google.com/p/darwincore/wiki/SubmittingIssues ). Sometimes this process is reversed, with a submitted issue being copied to the discussion forum for elaboration and consensusterm before refining the issue as submitted. All changes undergo a 30-day public review, announced on the listserv. Changes are reviewed by TDWG's Technical Architecture Group (TAG: http://www.tdwg.org/activities/tag/ ), a set of volunteer members with broad interest and expertise in web-based interoperabilityterm. The TAG determines if the proposed changes are compatible with Darwin Coreterm and that they do not reinvent existing standards. Changes that pass this review process are made as version changes to the affected documents, the latest of which always constitute the current standard.

Data Qualityterm and Constraining Darwin Coreterm Data qualityterm and fitness for useterm are primary concerns in the biodiversity community [42] , where information comes from heterogeneous sources spanning the globe over hundreds of years. Both data discovery and data qualityterm assessment are hampered by this heterogeneity. Part of the solution depends on the use of common vocabulariesterm, part on dictionaries of synonymous termsterm, and a great deal on applications that can facilitate discovery and assessment in place of or to aid in otherwise labor-intensive “cleanups”. For example, having a dictionary that equates “voucher” and “sample” with an accepted term “PreservedSpecimen” would allow applications to make this substitution automatically and allow users to discover relevant data using any of the synonyms regardless of how they were stored in the original data.

Darwin Coreterm makes recommendations about constraints on data content, whether about data typesterm·var, valid valuesterm·var, or controlled vocabulariesterm·var. For example, decimalLatitude is recommended to be a floating-point number falling between 90 and −90, inclusive; countryCode is recommended to be a value from ISO 3166-1-alpha-2 (two-letter country codes). Though these recommendations are made in the standard, the philosophy is to relegate enforcement to applications where they make sense. For example, in a collaboration where the purpose is to automate data qualityterm improvement on shared data, it is essential to be able to share the warts-and-all data that need to be investigated and improved.

Discussion Frontiers Though the Darwin Coreterm is defined in an RDF document, integration of biodiversity dataterm in the semantic webterm is in its early stages. One of the major challenges for Darwin Coreterm in the semantic webterm context is the lack of a well-defined ontologyterm - a formal definition of relationships between terms in a defined domain. An ontologyterm would define the relationships between concepts such as biological entities, the events that document where and when they occurred, and the processes through which they are identified as being representative of a taxonomic concept. Without rigorous relationships between concepts and the properties that define them, connections between biodiversity dataterm and related semantically rich information, such as literature and genomes, are difficult to traverse. This creates obstacles to cross-disciplinary semanticterm·var inquiry, such as in the Linked Data distributed data community ( http://linkeddata.org/ ). Current research is trying to address this gap (see TaxonConcept Knowledge Base, http://www.taxonconcept.org/ and BiSciCol, http://biscicol.blogspot.com/ ), active discussions on various aspects of the challenge take place regularly on the Darwin Coreterm public forum ( http://lists.tdwg.org/mailman/listinfo/tdwg-content ), and an RDF task group has been established within TDWG “to adapt TDWG vocabularies for use as RDF classes and properties and to integrate those resources with other well-known vocabularies and ontologies outside TDWG for use in describing biodiversity resources.” [43] Tools and Infrastructure for Publishing Darwin Coreterm Data A variety of toolsterm has been developed to simplify the mobilization and sharing of biodiversity dataterm using the Darwin Coreterm. Many of these tools focus on the creation or validation of Darwin Core Archivesterm ( http://code.google.com/p/darwincore/wiki/ToolsAndApplications#Tools ). The Global Biodiversity Informationterm Facility (GBIF), an international organization promoting the free and open access to biodiversity dataterm online, has invested heavily in the open and collaborative development of tools ( http://tools.gbif.org/ ) to make the creation and publication of Darwin Core Archives relatively simpleterm.

The Integrated Publishing Toolkitterm (IPT; http://www.gbif.org/informatics/infrastructure/publishing/ ) is an open-source software development projectterm, led by GBIF, designed to address the challenges of sharing biodiversity dataterm. By producing and providing easy access to Darwin Core Archivesterm and resource metadata in Ecological Markup Language [44] , the IPT works in tandem with a Global Biodiversity Resources Discovery System (GBRDS), a data registry, to facilitate discovery and retrieval of shared data throughout the world. The IPT complements other tools that have been created to assist data users to explore, organize, and mobilize data sets. A range of spreadsheet and archive creators and validators has been developed by GBIF and others. These tools can be accessed via the GBIF Publishing Software web page ( http://www.gbif.org/informatics/standards-and-tools/publishing-data/publishing-software/ ).

Whereas tools such as the IPT facilitate data mobilization using Darwin Coreterm data, other tools build on these sources to integrate and index biodiversity dataterm. These aggregators are thematic networks with either geographic (e.g., Atlas of Living Australia, http://www.ala.org.au/ ) or taxonomic focus (e.g., VertNet, http://vertnet.org ). Developing these systems to work sustainably and at large scales is an area of active research. For example, VertNet ( http://vertnet.org/ ), an aggregation of vertebrate specimen and observation data into a cloud-based data store, makes use of the Simple Darwin Coreterm in comma separated value (.csv) files with header rows containing Darwin Coreterm term names. These files are published to the data store where the records are indexed for high-performance querying.

Extensions Because Darwin Coreterm aims to cover the common ground in biodiversity, it inevitably lacks terms that are of interest to more specialized groups. A Darwin Core Extensionterm consists of additional terms describing a complementary, related domain, or guidance on the use of Darwin Coreterm within a specific sub-domain of biodiversity. Over the last decade, Darwin Coreterm has evolved by means of extensions, some of which have been incorporated in the standard. For example, the terms of a paleontology extension related to an earlier, pre-standard version of Darwin Coreterm became the terms of the current GeologicalContext class. Similarly, terms originating from an early version of the Darwin Coreterm created for the Ocean Biogeographic Information System (OBIS; http://www.iobis.org/ ) have also been added to Darwin Coreterm. Going forward, specific projects or disciplines may find it convenient to extend the scope of Darwin Coreterm outside the existing namespace and governance process for proof-of-concept research. Once the understanding of the new terms has been tested and proven of utility in a broader context, incorporation into the standard can be accomplished through community consensusterm.

Integration of Darwin Coreterm with New Research Communities Darwin Coreterm continues to be integrated into new research communities. For example, the Nordic Genetic Resource Center (NordGen; http://www.nordgen.org ) and Bioversity International (formerly IPGRI) ( http://www.bioversityinternational.org ) have sought to take advantage of Darwin Coreterm on behalf of the European plant genetic resources and genebank community and, at the same time, share rich discipline-specific genetic resource information. A careful review was made of Darwin Coreterm and a set of additional terms that did not overlap or conflict with existing Darwin Coreterm terms was proposed to meet the community's needs. The new terms, modeled directly from FAO/IPGRI Multi-Crop Passport Descriptors [45] (2001) and the proposed EPGRIS3 trait data standardterm for characterization and evaluation data [46] , were expressed and published openly in an XML schema for germplasm data (DwC-germplasm, http://code.google.com/p/darwincore-germplasm/ ) [47] , resulting in the first successfully deployed extension to the Darwin Coreterm Standard.

The success of DwC-germplasm has encouraged other communities to supplement or work in parallel with Darwin Coreterm to meet specific needs. For example, the Apiary Project ( http://www.apiaryproject.org/ ) extended the Darwin Coreterm to capture basic specimen information along with detailed annotation data (e.g., annotatedBy, dateAnnotated) found on herbarium sheets. Other communities are focusing on providing guidelines on how to use Darwin Coreterm within a discipline without the need for extensions. The Apple Core Initiative ( http://code.google.com/p/applecore/wiki/Introduction ), organized by Canadensys, ( http://www.canadensys.net/ ), is aimed at providing guidance on best practices for the content of Darwin Coreterm terms for vascular plant specimens.

A set of taxonomic extensions collectively known as the “GNA Profileterm” (named for the Global Names Architecture) [48] – [49] have been designed by GBIF with input from Catalogue of Life ( http://www.catalogueoflife.org/ ), Encyclopedia of Life ( http://eol.org/ ), nomenclators, and other taxonomic initiatives. These extensions ( http://rs.gbif.org/extension/gbif/1.0/ ), together with the taxonomic terms of Darwin Coreterm, allow sharing of rich taxonomic data often found in species checklists. The extensions are designed to be used in a one-to-many relationship with core taxon records, allowing the sharing of structured data such as vernacular names, species range distributions, textual descriptions, type species and specimens, image data, and bibliographies.

An effort is underway within TDWG to create a standard for biodiversity multimedia resources and collections, called the Audubon Coreterm [50] . The proposal introduces vocabularies covering the management and content of biodiversity-related media and their taxonomic, geographic, and temporal scope. Audubon Coreterm adopts by inclusion a number of terms from Darwin Coreterm, which can reduce the burden on existing media publishers who may have already used Darwin Coreterm terms for describing the media content.

In collaboration with the Genomic Standards Consortium (GSC; http://gensc.org/ ) [51] , Darwin Coreterm is now being extended to cover DNA-level observations (genomes, metagenomes, and gene marker sequences). The GSC, a standards body similar in scope to Biodiversity Informationterm Standards (TDWG), is working to “standardize the description of genomic data and promote the exchange and integration of genomic data. [52] .” Advances in technology have made sequence-based diversity assessments increasingly routine in biodiversity research. The GSC has developed the MIxSterm (Minimum Information about any (x) Sequence) standard containing checklists for describing genomes, metagenomes, and marker gene studies. Conceptually this approach is similar to Darwin Coreterm in that it defines terms for the description of data, but differs in that it requires the reporting a certain minimum set of descriptors such as environmental and geographic origin and details about sample and sequencing processing in addition to any kind of genomic sequence.

Currently, Darwin Coreterm and GSC developers are collaborating (supported by NSF-RCN4GSC) to harmonize Darwin Coreterm and MIxSterm to aid the growing field of sequence-based diversity research. Darwin Coreterm and GSC developers have concluded that the standards are conceptually similar and that the distinct sets of terms are complementary. This allows the development of a bi-directional (see Figure 2 ) solution, where in the future the GSC will be able to incorporate terms from Darwin Coreterm and add GSC-specific reporting requirements, while Darwin Coreterm will be able to offer a genomics extension using the results of this activity.

Scope and Scale of Darwin Coreterm for Biodiversity Science The creation of a standard format for biodiversity dataterm, the development of aggregation toolsterm, and the increasing use of Darwin Core Archivesterm have helped to overcome the challenge of limited availability of dataterm to answer questions about biodiversity. As more data become digitized and discoverable, biocollections can become a window into broader analyses of ecological, climate, niche, environmental, and biological research questions and critical issues.

Though predated by examples of the effective use of Darwin Coreterm for distribution modeling, influence of natural area preservation, and estimates of climate change impact [53] , the utility of data shared using Darwin Coreterm is illustrated by two recent examples. First, the University of California, Berkeley, and the Wildlife Conservation Society have collaborated to create Réseau de la Biodiversité de Madagascar (REBIOMAterm, http://www.rebiomaterm.net/ ).The effort seeks to make biodiversity dataterm about Madagascar available via a single web-based resource. Primary data on biodiversity in Madagascar come from researchers and institutions all over the world. REBIOMAterm works with each collection to standardize the data using the Darwin Coreterm, to mobilize and aggregate the data, and to vet the data for quality, completeness, and fitness for useterm. Data passing automated quality checks and review by a board of taxonomic experts are analyzed in combination with environmental data to produce maps showing models of where species might occur. The success of this project has made it possible for researchers, policy makers, government officials, and conservationists to capture a wealth of data to address issues of Malagasy biodiversity. The simplicity and flexibilityterm of Darwin Coreterm has made it possible for REBIOMAterm to provide immediate access to high-quality data and tools for monitoring and assessing conservation efforts.

A second example of innovative use of Darwin Coreterm data is the Map of Lifeterm Project ( http://www.mappinglife.org/ ), and sister projects such as LifeMapper ( http://www.lifemapper.org/ ) [54] , which aggregate and mobilize sources of species distribution information and provide tools to visualize and analyses those data. In Map of Lifeterm, species occurrence data points formatted as Darwin Coreterm are queried and brought into the application with related data sources such as range maps, assemblage checklists, and habitat preference data. Integration of these data typesterm·var and modeling will lead to summary products describing species distributions and provide the basis for distribution change assessments in the face of human-induced global changes [55] . The Map of Lifeterm will be a knowledge base of hundreds of thousands of high-resolution species distribution maps covering a wide range of taxa and geographic locations.

Conclusions The demand for Darwin Coreterm data is increasing. The corpus of information spanning three centuries of biodiversity exploration is being digitized at an increasing rate. Major efforts such as the new US National Science Foundation program Advancing Digitization of Biological Collections ( http://nsf.gov/funding/pgm_summ.jsp?pims_id=503559&org=DBI&from=home ) and the Atlas of Living Australia ( http://www.ala.org.au ) are two recent examples. A flood of qualitatively new global biodiversity dataterm is also being generated through the application of high-throughput gene sequencing of environmental samples.

The President's Council of Advisors on Science and Technology (PCAST) report on sustaining environmental capital noted recently that the challenge is not only one of the volume of data, but also its heterogeneity, as traditional biotic surveying practices blend with new approaches, such as remote sensing [56] or metagenomics [57] . A key passage in that PCAST report captures the challenge perfectly: “temporal, spatial, and methodological heterogeneity leads to a depth and richness in biodiversity and ecosystems data not found in other fields. It also makes dataset interoperabilityterm a problem that is at the same time particularly challenging and highly important to solve [58] .” Darwin Coreterm fills an essential role in describing some of these data in a standard format based on community input and demonstrated utility.

Darwin Coreterm is a living standardterm. Although its roots were planted in the vertebrate natural history collections community, Darwin Coreterm continues to grow to serve the needs of biodiversity research. This growth, over the relatively short period of a decade, speaks both to the need for such a standard and to the efforts of its champions to increase its utility through a community development process in order to meet increasing demand. Darwin Coreterm greatly increases the value and re-useterm of freely available and accessible biodiversity dataterm so that they can be effectively mobilized, integrated, and incorporated into other “grand challenge” scientific endeavors.

Interpretive notes.
• Highlighted spans are tagged entities: persName (author), title (venue), placeName (place), date (year), and term (a key concept: domain / ai / method).
• Eponymous or retrospective terms (e.g. “Nash equilibrium”, “segregation”) do not appear in the original source and so are not highlighted — a deliberate choice (see Report 4).
• Some entries begin with a word in capitals. EVIDENCE CORRECTED means the finding still stands and it was our quotation that was wrong — it has been replaced. RETRACTED means the entry itself was wrong; it stays on the page, marked, with its reason, rather than being deleted. WITHDRAWN AND REPLACED means a corrected version of it appears in the entries below. Each mark carries its own reason, because the reasons differ from one entry to the next. An entry we have WITHDRAWN is removed from this page and kept in the record, with its reason. A line reading Audit and a date is a later re-reading of the entry against its whole sentence: DOUBTFUL means it was kept, and the reason says what is loose about it.
• Quotation marks inside the tagger's sentence. Where a tag is the tagger's own sentence, a phrase in quotation marks inside it is borrowed from the paper — the tagger's wording around it is not. The paper's own sentence is the evidence quote shown on the same row, so the borrowing can be checked against the thing borrowed from without leaving this page. Nothing inside quotation marks anywhere on this page is ours: if it is quoted, it is the paper's. Whose words a concept carries. A concept entry records a term the paper itself uses, so the term, the sense given for it, and its evidence are the paper's own words, quoted where the paper fixes them. This is the opposite of a sense entry in the tag table, which is the tagger's sentence about how the paper uses a term. Where a concept entry could not be grounded in the paper's words, the entry says so on its own row.
• Counts: 1 work · 1 date.
Meta-Tagging Project · record wieczorek2012-darwin-core-evolving-community-biodiversity-data-standard.
© 2026 Shir Sivroni