CINXE.COM
Standards
<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>Standards</title> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <meta name="description" content="An output of the Research Data Alliance Metadata Standards Directory Working Group"> <link href="/metadata-directory/css/bootstrap.min.css" rel="stylesheet"> <link href="/metadata-directory/css/hc.css" rel="stylesheet"> <link href="http://netdna.bootstrapcdn.com/font-awesome/4.0.3/css/font-awesome.css" rel="stylesheet"> <!-- HTML5 shim, for IE6-8 support of HTML5 elements --> <!--[if lt IE 9]> <script src="http://html5shim.googlecode.com/svn/trunk/html5.js"></script> <![endif] d--> <script> (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){ (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o), m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m) })(window,document,'script','//www.google-analytics.com/analytics.js','ga'); ga('create', 'UA-59116315-1', 'auto'); ga('send', 'pageview'); </script> </head> <body> <div class="nav-toggle"><i class="fa fa-bars fa-2x"></i>Metadata Standards Directory</div> <div id = "wrapper"> <!-- Small screen navigation --> <div class="navbar navbar-default" role="navigation"> <div class="container"> <div class="navbar-header"> <button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse"> <span class="sr-only">Toggle navigation</span> <span class="icon-bar"></span> <span class="icon-bar"></span> <span class="icon-bar"></span> </button> <p class="navbar-brand">Metadata Standards Directory</p> </div> <div class="navbar-collapse collapse"> <ul class="nav navbar-nav"> <li> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/index.md">Edit this page</a> </li> <li><a href="/metadata-directory/standards/">View the standards</a></li> <li><a href="/metadata-directory/extensions/">View the extensions</a></li> <li><a href="/metadata-directory/tools/">View the tools</a></li> <li><a href="/metadata-directory/use_cases/">View the use cases</a></li> <li><a href="/metadata-directory/subjects/">Browse by subject areas</a></li> <!-- <li><a href="/metadata-directory/about/">Contribute</a></li> <li><a href="/metadata-directory/standards/add.html">Add standards</a></li> <li><a href="/metadata-directory/extensions/add.html">Add extensions</a></li> <li><a href="/metadata-directory/tools/add.html">Add tools</a></li> <li><a href="/metadata-directory/use_cases/add.html">Add use cases</a></li> --> </ul> </div><!--/.nav-collapse --> </div> </div> <!-- Sidebar --> <div id="sidebar-wrapper"> <ul class="sidebar-nav"> <li class="sidebar-brand"> <h1 class="brand"><a href="/metadata-directory/">Metadata Standards Directory</a></h1> </li> <hr /> <!-- <li> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/index.md">Edit this page</a> </li> <hr /> --> <li><a href="/metadata-directory/standards/">View the standards</a></li> <li><a href="/metadata-directory/extensions/">View the extensions</a></li> <li><a href="/metadata-directory/tools/">View the tools</a></li> <li><a href="/metadata-directory/use_cases/">View the use cases</a></li> <li><a href="/metadata-directory/subjects/">Browse by subject areas</a></li> <hr /> <li><a href="/metadata-directory/about/">How contributing worked</a></li> <!-- <li><a href="/metadata-directory/standards/add.html">Add standards</a></li> <li><a href="/metadata-directory/extensions/add.html">Add extensions</a></li> <li><a href="/metadata-directory/tools/add.html">Add tools</a></li> <li><a href="/metadata-directory/use_cases/add.html">Add use cases</a></li> --> <hr /> <div id="social-wrapper"> <li> <a href="http://www.github.com/rd-alliance/metadata-directory"><i class="fa fa-github-square"></i> github</a> </li> <li> <a href="https://twitter.com/resdatall"><i class="fa fa-twitter-square"></i> @twitter</a></li> <li> <a href="http://www.linkedin.com/profile/view?id=272003890&trk=nav_responsive_tab_profile"><i class="fa fa-linkedin-square"></i> linkedin</a> </li> <li> <a href="https://www.facebook.com/pages/Research-Data-Alliance/459608890798924"><i class="fa fa-facebook-square"></i> facebook</a></li> </div> </ul> </div> <!-- Main page content --> <div class="container"> <div class="alert alert-warning" role="alert"> <div class="media"> <div class="pull-left"> <span class="fa fa-exclamation-triangle fa-2x"></span> </div> <div class="media-body"> This directory has been superseded by the <a href="https://rdamsc.bath.ac.uk/">RDA Metadata Standards Catalog</a> and is no longer maintained. </div> </div> </div> <h2>Arts and Humanities</h2> <dl> <dt> <a href="/metadata-directory/standards/EAD.html">Encoded Archival Description (EAD)</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/EAD.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>A standard for encoding archival finding aids using XML in archival and manuscript repositories, implementing the recommendations of the International Council on Archives <a href="https://www.ica.org/en/isadg-general-international-standard-archival-description-second-edition">ISAD(G): General International Standard Archival Description</a>.</p> </dd> <dt> <a href="/metadata-directory/standards/TEI.html">TEI - Text Encoding Initiative</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/TEI.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>The guidelines of the Text Encoding Initiative make recommendations about suitable ways of representing those features of textual resources which need to be identified explicitly in order to facilitate processing by computer programs. They specify a set of XML tags in order to mark the textual metadata, text structure, relationship between images and transcriptions and other features of interest. The guidelines both describe the formal TEI encoding scheme, and document the TEI markup vocabulary. In their 30 years community driven development they have developed to a de-facto standard in the production of textual data in the humanities.</p> </dd> <dt> <a href="/metadata-directory/standards/ddi-data-documentation-initiative.html">DDI (Data Documentation Initiative)</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/ddi-data-documentation-initiative.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>A widely used, international standard for describing data from the social, behavioral, and economic sciences. Two versions of the standard are currently maintained in parallel:</p><ul><li>DDI Codebook (or DDI version 2) is the simpler of the two, and intended for documenting simple survey data for exchange or archiving. Version 2.5 was released in January 2014.</li><li>DDI Lifecycle (or DDI version 3) is richer and may be used to document datasets at each stage of their lifecycle from conceptualization through to publication and reuse. It is modular and extensible. Version 3.2 was published in March 2014.</li></ul><p>Both versions are XML-based and defined using XML Schemas. They were developed and are maintained by the DDI Alliance.</p></dd> <dt> <a href="/metadata-directory/standards/marc.html">MARC (Machine-Readable Cataloging)</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/marc.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>MARC is a standard and serialization format for representing bibliographic metadata, originally designed as a way of exchanging bibliographic records between library catalogs. Various different versions have been defined, mostly with national or regional scope, of which MARC 21 is probably the most widely used. There also exists an XML serialization of MARC 21, known as MARCXML.</p> </dd> <dt> <a href="/metadata-directory/standards/midas-heritage.html">MIDAS-Heritage</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/midas-heritage.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>A British cultural heritage standard for recording information on buildings, archaeological sites, shipwrecks, parks and gardens, battlefields, areas of interest and artefacts.</p><p>Sponsored by the Forum on Information Standards in Heritage, MIDAS Version 1.1 was released in October 2012.</p></dd> <dt> <a href="/metadata-directory/standards/oai-ore-open-archives-initiative-object-reuse-and-exchange.html">OAI-ORE (Open Archives Initiative Object Reuse and Exchange)</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/oai-ore-open-archives-initiative-object-reuse-and-exchange.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>The goal of these standards is to expose the rich content in aggregations of Web resources to applications that support authoring, deposit, exchange, visualization, reuse, and preservation. The standards support the changing nature of scholarship and scholarly communication, and the need for cyberinfrastructure to support that scholarship, with the intent to develop standards that generalize across all web-based information including the increasing popular social networks of “Web 2.0”.</p></dd> <dt> <a href="/metadata-directory/standards/ro-crate.html">RO-Crate</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/ro-crate.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>RO-Crate is a community effort to establish a lightweight approach to packaging research data with their metadata. It is based on schema.org annotations in JSON-LD, and aims to make best-practice in formal metadata description accessible and practical for use in a wider variety of situations, from an individual researcher working with a folder of data, to large data-intensive computational research environments.</p> </dd> </dl> <h2>Engineering</h2> <dl> <dt> <a href="/metadata-directory/standards/cif-crystallographic-information-framework.html">CIF (Crystallographic Information Framework)</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/cif-crystallographic-information-framework.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>A well-established standard file structure for the archiving and distribution of crystallographic information, CIF is in regular use for reporting crystal structure determinations to Acta Crystallographica and other journals.</p><p>Sponsored by the International Union of Crystallography, the current standard dates from 1997. As of July 2011, a new version of the CIF standard is under consideration.</p></dd> <dt> <a href="/metadata-directory/standards/csmd-cclrc-core-scientific-metadata-model.html">CSMD (Core Scientific Metadata Model)</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/csmd-cclrc-core-scientific-metadata-model.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>A study-data oriented model, primarily in support of the ICAT data managment infrastructure software. The CSMD is designed to support data collected within a large-scale facility’s scientific workflow; however the model is also designed to be generic across scientific disciplines.</p><p>Sponsored by the Science and Technologies Facilities Council, the latest full specification available is v 4.0, from 2013.</p></dd> <dt> <a href="/metadata-directory/standards/isa-tab.html">ISA-Tab</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/isa-tab.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>The Investigation/Study/Assay (ISA) tab-delimited (TAB) format is a general purpose framework with which to collect and communicate complex metadata (i.e. sample characteristics, technologies used, type of measurements made) from 'omics-based' experiments employing a combination of technologies.</p><p>Created by core developers from the University of Oxford, ISA-TAB v1.0 was released in November 2008.</p></dd> <dt> <a href="/metadata-directory/standards/mibbi-minimum-information-biological-and-biomedical-investigations.html">MIBBI (Minimum Information for Biological and Biomedical Investigations)</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/mibbi-minimum-information-biological-and-biomedical-investigations.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>A common portal to a group of nearly 40 checklists of Minimum Information for various biological disciplines. The MIBBI Foundry is developing a cross-analysis of these guidelines to create an intercompatible, extensible community of standards.</p><p>The concept was realized initially through the joint efforts of the Proteomics Standards Initiative, the Genomic Standards Consortium and the MGED RSBI Working Groups. The latest project to register with MIBBI is the MIABie guidelines for reporting biofilm research, as of January 2012.</p></dd> <dt> <a href="/metadata-directory/standards/nexus.html">NeXus</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/nexus.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>NeXus is an international standard for the storage and exchange of neutron, x-ray, and muon experiment data. The structure of NeXus files is extremely flexible, allowing the storage of both simple data sets, such as a single data array and its axes, and highly complex data and their associated metadata, such as measurements on a multi-component instrument or numerical simulations. NeXus is built on top of the container format HDF5, and adds domain-specific rules for organizing data within HDF5 files in addition to a dictionary of well-defined domain-specific field names.</p></dd> <dt> <a href="/metadata-directory/standards/openPMD.html">Open Standard for Particle-Mesh Data (openPMD)</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/openPMD.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>The openPMD standard provides naming and attribute conventions that allow the exchange of particle and mesh based data from scientific simulations and experiments. The primary goal is to define a minimal set/kernel of meta information that enables the sharing and exchange of data to achieve.</p> <ul> <li>portability between various applications and differing algorithms;</li> <li>a unified open-access description for scientific data (publishing and archiving);</li> <li>a unified description for post-processing, visualization and analysis.</li> </ul> <p>The standard suits any kind of hierarchical, self-describing data format, such as, but not limited to ADIOS1 (BP3), ADIOS2 (BP4), HDF5, JSON, and XML.</p> </dd> </dl> <h2>Life Sciences</h2> <dl> <dt> <a href="/metadata-directory/standards/abcd-access-biological-collection-data.html">ABCD (Access to Biological Collection Data)</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/abcd-access-biological-collection-data.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>The <a href="http://www.tdwg.org/standards/115/">Access to Biological Collections Data (ABCD) Schema</a> is an evolving comprehensive standard for the access to and exchange of data about specimens and observations (a.k.a. primary biodiversity data). The ABCD Schema attempts to be comprehensive and highly structured, supporting data from a wide variety of databases. It is compatible with several existing data standards. Parallel structures exist so that either (or both) atomised data and free-text can be accommodated.</p><p>The ABCD Schema was ratified as a standard by the Biodiversity Information Standards Taxonomic Databases Working Group (TDWG) in 2005. It was developed as a community-driven effort, with contributions from CODATA, BioCASE and GBIF among other organizations.</p></dd> <dt> <a href="/metadata-directory/standards/darwin-core.html">Darwin Core</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/darwin-core.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>A body of standards, including a glossary of terms (in other contexts these might be called properties, elements, fields, columns, attributes, or concepts) intended to facilitate the sharing of information about biological diversity by providing reference definitions, examples, and commentaries.</p><p>Sponsored by Biodiversity Information Standards (TWDG), the current standard was last modified in October 2009.</p></dd> <dt> <a href="/metadata-directory/standards/eml-ecological-metadata-language.html">EML (Ecological Metadata Language)</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/eml-ecological-metadata-language.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>Ecological Metadata Language (EML) is a metadata specification particularly developed for the ecology discipline. It is based on prior work done by the Ecological Society of America and associated efforts (Michener et al., 1997, Ecological Applications).</p><p>Sponsored by ecoinformatics.org, EML Version 2.2.0 was released in 2019.</p></dd> <dt> <a href="/metadata-directory/standards/genome-metadata.html">Genome Metadata</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/genome-metadata.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>Genome metadata on PATRIC consists of 61 different metadata fields, called attributes, which are organized into the following seven broad categories: Organism Info, Isolate Info, Host Info, Sequence Info, Phenotype Info, Project Info, and Others.</p></dd> <dt> <a href="/metadata-directory/standards/isa-tab.html">ISA-Tab</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/isa-tab.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>The Investigation/Study/Assay (ISA) tab-delimited (TAB) format is a general purpose framework with which to collect and communicate complex metadata (i.e. sample characteristics, technologies used, type of measurements made) from 'omics-based' experiments employing a combination of technologies.</p><p>Created by core developers from the University of Oxford, ISA-TAB v1.0 was released in November 2008.</p></dd> <dt> <a href="/metadata-directory/standards/mibbi-minimum-information-biological-and-biomedical-investigations.html">MIBBI (Minimum Information for Biological and Biomedical Investigations)</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/mibbi-minimum-information-biological-and-biomedical-investigations.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>A common portal to a group of nearly 40 checklists of Minimum Information for various biological disciplines. The MIBBI Foundry is developing a cross-analysis of these guidelines to create an intercompatible, extensible community of standards.</p><p>The concept was realized initially through the joint efforts of the Proteomics Standards Initiative, the Genomic Standards Consortium and the MGED RSBI Working Groups. The latest project to register with MIBBI is the MIABie guidelines for reporting biofilm research, as of January 2012.</p></dd> <dt> <a href="/metadata-directory/standards/nexus.html">NeXus</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/nexus.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>NeXus is an international standard for the storage and exchange of neutron, x-ray, and muon experiment data. The structure of NeXus files is extremely flexible, allowing the storage of both simple data sets, such as a single data array and its axes, and highly complex data and their associated metadata, such as measurements on a multi-component instrument or numerical simulations. NeXus is built on top of the container format HDF5, and adds domain-specific rules for organizing data within HDF5 files in addition to a dictionary of well-defined domain-specific field names.</p></dd> <dt> <a href="/metadata-directory/standards/observ-om.html">Observ-OM</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/observ-om.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>Observ-OM is founded on four basic concepts to represent any kind of observation: Targets, Features, Protocols (and their Applications), and Values. It is intended to lower the barrier for future data sharing and facilitate integrated search across panels and species. All models, formats, documentation, and software are available for free and open source (LGPLv3) at <a href="http://www.observ-om.org" title="http://www.observ-om.org">http://www.observ-om.org</a>.</p></dd> <dt> <a href="/metadata-directory/standards/odam-datapackage.html">ODAM Structural Metadata</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/odam-datapackage.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>Open Data for Access and Mining (ODAM) Structural Metadata is a format describing how the metadata should be formatted and what should be included to ensure ODAM compliance for a data set. To comply with this format, two metadata files in TSV format are required in addition to the data file(s). These two files describe the metadata of the dataset, which includes descriptions of measures and structural metadata like references between tables. The metadata lets non-expert users explore and visualize your data. By making data interoperable and reusable by both humans and machines, it also encourages data dissemination according to FAIR principles. The structural metadata is specified in section 'Data collection and preparation' on the website.</p></dd> <dt> <a href="/metadata-directory/standards/ome-xml-open-microscopy-environment-xml.html">OME-XML (Open Microscopy Environment XML)</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/ome-xml-open-microscopy-environment-xml.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p><a href="http://www.openmicroscopy.org/Schemas/">OME-XML</a> is a vendor-neutral file format for biological image data, with an emphasis on metadata supporting light microscopy. It can be used as a data file format in its own right, or as a way of encoding metadata within a TIFF or BigTIFF file (for which purpose there is the <a href="http://www.openmicroscopy.org/site/support/file-formats/ome-tiff/ome-tiff-specification">OME-TIFF</a> specification).</p><p>The standard is maintained by the Open Microscopy Environment Consortium, and was last updated in June 2012.</p></dd> <dt> <a href="/metadata-directory/standards/openPMD.html">Open Standard for Particle-Mesh Data (openPMD)</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/openPMD.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>The openPMD standard provides naming and attribute conventions that allow the exchange of particle and mesh based data from scientific simulations and experiments. The primary goal is to define a minimal set/kernel of meta information that enables the sharing and exchange of data to achieve.</p> <ul> <li>portability between various applications and differing algorithms;</li> <li>a unified open-access description for scientific data (publishing and archiving);</li> <li>a unified description for post-processing, visualization and analysis.</li> </ul> <p>The standard suits any kind of hierarchical, self-describing data format, such as, but not limited to ADIOS1 (BP3), ADIOS2 (BP4), HDF5, JSON, and XML.</p> </dd> <dt> <a href="/metadata-directory/standards/pdbx-mmcif.html">PDBx/mmCIF (Protein Data Bank Exchange Dictionary and the Macromolecular Crystallographic Information Framework)</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/pdbx-mmcif.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>Protein Data Bank archive (PDB) is the single worldwide archival repository of information about the 3D structures of proteins, nucleic acids, and complex assemblies, managed by the Worldwide PDB (wwPDB). The PDB Exchange Dictionary (PDBx) is used by the wwPDB to define data content for deposition, annotation and archiving of PDB entries. PDBx incorporates the community standard metadata representation, the Macromolecular Crystallographic Information Framework (mmCIF), orginally developed under the auspices of the International Union of Crystallography (IUCr). PDBx has been extended by the wwPDB to include descriptions of other experimental methods that produce 3D macromolecular structure models such as Nuclear Magnetic Resonance Spectroscopy, 3D Electron Microscopy and Tomography.</p></dd> <dt> <a href="/metadata-directory/standards/protocol-data-element-definitions.html">Protocol Data Element Definitions</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/protocol-data-element-definitions.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd>A draft set of data elements required by the National Institues of Health (U.S.) for the submission of trial information to the <a href="http://clinicaltrials.gov/ct2/home">CLincalTrials.gov</a> registry and results database.</dd> <dt> <a href="/metadata-directory/standards/repository-developed-metadata-schemas.html">Repository-Developed Metadata Schemas</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/repository-developed-metadata-schemas.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>Some repositories have decided that current standards do not fit their metadata needs, and so have created their own requirements.</p></dd> <dt> <a href="/metadata-directory/standards/ro-crate.html">RO-Crate</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/ro-crate.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>RO-Crate is a community effort to establish a lightweight approach to packaging research data with their metadata. It is based on schema.org annotations in JSON-LD, and aims to make best-practice in formal metadata description accessible and practical for use in a wider variety of situations, from an individual researcher working with a folder of data, to large data-intensive computational research environments.</p> </dd> <dt> <a href="/metadata-directory/standards/ukeof.html">UKEOF</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/ukeof.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>A metadata standard for describing environmental monitoring activities, programmes, networks and facilities published by the UK Environmental Observation Framework (UKEOF).</p></dd> </dl> <h2>Physical Sciences & Mathematics</h2> <dl> <dt> <a href="/metadata-directory/standards/agmes-agricultural-metadata-element-set.html">AgMES (Agricultural Metadata Element Set)</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/agmes-agricultural-metadata-element-set.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>A semantic standard developed by the Food and Agriculture Organization (FAO) of the United Nations, AgMES enables description, resource discovery, interoperability and data exchange of different types of information resources in all areas relevant to food production, nutrition and rural development.</p><p>The standard is maintained by AIMS (Agricultural Information Management Standards), and while it has been used in various application profiles, it is now deprecated for new uses and will no longer be updated.</p></dd> <dt> <a href="/metadata-directory/standards/avm-astronomy-visualization-metadata.html">AVM (Astronomy Visualization Metadata)</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/avm-astronomy-visualization-metadata.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>The <a href="http://www.virtualastronomy.org/avm_metadata.php">AVM</a> scheme supports the cross-searching of collections of print-ready and screen-ready astronomical imagery rendered from telescopic observations (also known as ‘pretty pictures’). The scheme is compatible with the <a href="http://www.adobe.com/products/xmp/">Adobe XMP</a> specification, so the metadata can be embedded within common image formats such as JPEG, TIFF and PNG.</p><p>Such images can combine data acquired at different wavebands and from different observatories. While the primary intent is to cover data-derived astronomical images, there are broader uses as well. Specifically, the most general subset of this schema is also appropriate for describing artwork and illustrations of astronomical subject matter.</p><p>AVM is a proposed recommendation of the International Virtual Observatory Alliance and was last updated in 2011.</p></dd> <dt> <a href="/metadata-directory/standards/cf-climate-and-forecast-metadata-conventions.html">CF (Climate and Forecast) Metadata Conventions</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/cf-climate-and-forecast-metadata-conventions.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>The CF standard was originally framed as a standard for data written in netCDF format, with model-generated climate forecast data particularly in mind. However, it is equally applicable to observational datasets, and can be used to describe other formats. It is a standard for “use metadata” that aims both to distinguish quantities (such as physical description, units, and prior processing) and to locate the data in space–time.</p><p>Sponsored by the NetCDF Climate and Forecast Metadata Convention, the current version dates from December 2011.</p></dd> <dt> <a href="/metadata-directory/standards/cif-crystallographic-information-framework.html">CIF (Crystallographic Information Framework)</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/cif-crystallographic-information-framework.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>A well-established standard file structure for the archiving and distribution of crystallographic information, CIF is in regular use for reporting crystal structure determinations to Acta Crystallographica and other journals.</p><p>Sponsored by the International Union of Crystallography, the current standard dates from 1997. As of July 2011, a new version of the CIF standard is under consideration.</p></dd> <dt> <a href="/metadata-directory/standards/cim-common-information-model.html">CIM (Common Information Model)</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/cim-common-information-model.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>The Common Information Model (<a href="https://earthsystemcog.org/projects/es-doc-models/cim">CIM</a>) describes climate data, the models and software from which they derive, the geographic grids used to calculate and project them, and the experimental processes (typically simulations) that produced them.</p><p>The CIM was originally developed by the EU-funded Metafor Project. It is now maintained and developed by Earth Science Documentation (ES-DOC). The latest release dates from 2012.</p></dd> <dt> <a href="/metadata-directory/standards/csmd-cclrc-core-scientific-metadata-model.html">CSMD (Core Scientific Metadata Model)</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/csmd-cclrc-core-scientific-metadata-model.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>A study-data oriented model, primarily in support of the ICAT data managment infrastructure software. The CSMD is designed to support data collected within a large-scale facility’s scientific workflow; however the model is also designed to be generic across scientific disciplines.</p><p>Sponsored by the Science and Technologies Facilities Council, the latest full specification available is v 4.0, from 2013.</p></dd> <dt> <a href="/metadata-directory/standards/dif-directory-interchange-format.html">DIF (Directory Interchange Format)</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/dif-directory-interchange-format.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>An early metadata initiative from the Earth sciences community, intended for the description of scientific data sets. It inlcudes elements focusing on instruments that capture data, temporal and spatial characteristics of the data, and projects with which the dataset is associated. It is defined as a W3C XML Schema.</p><p>Sponsored by the Global Change Master Directory, the DIF Writer's Guide Version 6 is from November 2010.</p></dd> <dt> <a href="/metadata-directory/standards/fgdccsdgm-federal-geographic-data-committee-content-standard-digital-ge.html">FGDC/CSDGM (Federal Geographic Data Committee Content Standard for Digital Geospatial Metadata)</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/fgdccsdgm-federal-geographic-data-committee-content-standard-digital-ge.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>A widely-used, but no longer current standard defining the information content for a set of digital geospatial data required by the US Federal Government.</p><p>CSDGM was sponsored by the US Federal Geographic Data Committee.  However, in September 2010 the FGDC endorsed ISO 19115 and began encouraging federal agencies to transition to ISO metadata.</p></dd> <dt> <a href="/metadata-directory/standards/fits-flexible-image-transport-system.html">FITS (Flexible Image Transport System)</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/fits-flexible-image-transport-system.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p><a href="http://fits.gsfc.nasa.gov/fits_home.html">FITS</a> is an image data file format for encoding astronomical data. The WCS (World Coordinate System) conventions map elements in data arrays to standard physical coordinates in the sky. FITS has provisions for image metadata encoded in an ASCII header at the beginning of files.</p></dd> <dt> <a href="/metadata-directory/standards/international-virtual-observatory-alliance-technical-specifications.html">International Virtual Observatory Alliance Technical Specifications</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/international-virtual-observatory-alliance-technical-specifications.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>The technical specifications defined by the IVOA (International Virtual Observatory Alliance) enable interoperability between and the integration of astronomical archives across the world into an international virtual observatory. They include several data models that act as metadata schemas for particular data types: for example, photometry data, simulation data, space-time coordinates, spectral lines data, spectral data, observational data, and the physical parameter space of astronomical datasets.</p><p>These data models are under active development by the IVOA Data Modelling Working Group.</p><p>Additional recommendations have been made for metadata concepts and terms necessary for the discovery and the use of astronomical data collections and services.</p></dd> <dt> <a href="/metadata-directory/standards/iso-19115.html">ISO 19115</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/iso-19115.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>An internationally-adopted schema for describing geographic information and services. It provides information about the identification, the extent, the quality, the spatial and temporal schema, spatial reference, and distribution of digital geographic data.</p><p>Sponsored by the International Standards Organisation, the first edition of ISO 19115 was published in 2003. It has since been split into parts: ISO 19115-1:2014 contains the fundamentals of the standard; ISO 19115-2:2009 contains extensions for imagery and gridded data; and ISO/TS 19115-3:2016 provides an XML schema implementation for the fundamental concepts compatible with ISO/TS 19138:2007 (Geographic Metadata XML, or GMD).</p></dd> <dt> <a href="/metadata-directory/standards/nexus.html">NeXus</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/nexus.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>NeXus is an international standard for the storage and exchange of neutron, x-ray, and muon experiment data. The structure of NeXus files is extremely flexible, allowing the storage of both simple data sets, such as a single data array and its axes, and highly complex data and their associated metadata, such as measurements on a multi-component instrument or numerical simulations. NeXus is built on top of the container format HDF5, and adds domain-specific rules for organizing data within HDF5 files in addition to a dictionary of well-defined domain-specific field names.</p></dd> <dt> <a href="/metadata-directory/standards/observations-and-measurements.html">Observations and Measurements</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/observations-and-measurements.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>This encoding is an essential dependency for the OGC Sensor Observation Service (SOS) Interface Standard. More specifically, this standard defines XML schemas for observations, and for features involved in sampling when making observations. These provide document models for the exchange of information describing observation acts and their results, both within and between different scientific and technical communities.</p></dd> <dt> <a href="/metadata-directory/standards/openPMD.html">Open Standard for Particle-Mesh Data (openPMD)</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/openPMD.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>The openPMD standard provides naming and attribute conventions that allow the exchange of particle and mesh based data from scientific simulations and experiments. The primary goal is to define a minimal set/kernel of meta information that enables the sharing and exchange of data to achieve.</p> <ul> <li>portability between various applications and differing algorithms;</li> <li>a unified open-access description for scientific data (publishing and archiving);</li> <li>a unified description for post-processing, visualization and analysis.</li> </ul> <p>The standard suits any kind of hierarchical, self-describing data format, such as, but not limited to ADIOS1 (BP3), ADIOS2 (BP4), HDF5, JSON, and XML.</p> </dd> <dt> <a href="/metadata-directory/standards/pdbx-mmcif.html">PDBx/mmCIF (Protein Data Bank Exchange Dictionary and the Macromolecular Crystallographic Information Framework)</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/pdbx-mmcif.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>Protein Data Bank archive (PDB) is the single worldwide archival repository of information about the 3D structures of proteins, nucleic acids, and complex assemblies, managed by the Worldwide PDB (wwPDB). The PDB Exchange Dictionary (PDBx) is used by the wwPDB to define data content for deposition, annotation and archiving of PDB entries. PDBx incorporates the community standard metadata representation, the Macromolecular Crystallographic Information Framework (mmCIF), orginally developed under the auspices of the International Union of Crystallography (IUCr). PDBx has been extended by the wwPDB to include descriptions of other experimental methods that produce 3D macromolecular structure models such as Nuclear Magnetic Resonance Spectroscopy, 3D Electron Microscopy and Tomography.</p></dd> <dt> <a href="/metadata-directory/standards/repository-developed-metadata-schemas.html">Repository-Developed Metadata Schemas</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/repository-developed-metadata-schemas.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>Some repositories have decided that current standards do not fit their metadata needs, and so have created their own requirements.</p></dd> <dt> <a href="/metadata-directory/standards/sdac.html">SDAC (Standard for Documentation of Astronomical Catalogues)</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/sdac.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>The Standard for Documentation of Astronomical Catalogues is a set of conventions for archiving astronomical data. As well as path, filename and data format conventions, it also specifies how to construct a plain text description file for documenting the data files. It was developed as an alternative to FITS that would be more suited to archives, permit human inspection, and allow manipulation via standard Unix command-line tools.</p> <p>SDAC was developed by CDS (Centre de Donn茅es astronomiques de Strasbourg). Version 2.0 is the most recent; it was released in February 2000.</p></dd> <dt> <a href="/metadata-directory/standards/spase-data-model.html">SPASE Data Model</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/spase-data-model.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>An information model for describing the elements of the heliophysics data environment, and a set of resource types which can be used to describe data along with its scientific context, source, provenance, content and location. It is designed to support a federated data system where data may reside at different locations and may be seperated from the metadata which describes it. The preferred expression form is XML.</p><p>The Space Physics Archive Search and Extract (SPASE) effort is implemented by the SPASE Consortium which is composed of representatives of the international Heliophysics data community. The Current Release of the data model (2.2.2) was updated in October 2012.</p></dd> <dt> <a href="/metadata-directory/standards/ukeof.html">UKEOF</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/ukeof.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>A metadata standard for describing environmental monitoring activities, programmes, networks and facilities published by the UK Environmental Observation Framework (UKEOF).</p></dd> </dl> <h2>Social and Behavioral Sciences</h2> <dl> <dt> <a href="/metadata-directory/standards/ddi-data-documentation-initiative.html">DDI (Data Documentation Initiative)</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/ddi-data-documentation-initiative.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>A widely used, international standard for describing data from the social, behavioral, and economic sciences. Two versions of the standard are currently maintained in parallel:</p><ul><li>DDI Codebook (or DDI version 2) is the simpler of the two, and intended for documenting simple survey data for exchange or archiving. Version 2.5 was released in January 2014.</li><li>DDI Lifecycle (or DDI version 3) is richer and may be used to document datasets at each stage of their lifecycle from conceptualization through to publication and reuse. It is modular and extensible. Version 3.2 was published in March 2014.</li></ul><p>Both versions are XML-based and defined using XML Schemas. They were developed and are maintained by the DDI Alliance.</p></dd> <dt> <a href="/metadata-directory/standards/midas-heritage.html">MIDAS-Heritage</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/midas-heritage.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>A British cultural heritage standard for recording information on buildings, archaeological sites, shipwrecks, parks and gardens, battlefields, areas of interest and artefacts.</p><p>Sponsored by the Forum on Information Standards in Heritage, MIDAS Version 1.1 was released in October 2012.</p></dd> <dt> <a href="/metadata-directory/standards/oai-ore-open-archives-initiative-object-reuse-and-exchange.html">OAI-ORE (Open Archives Initiative Object Reuse and Exchange)</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/oai-ore-open-archives-initiative-object-reuse-and-exchange.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>The goal of these standards is to expose the rich content in aggregations of Web resources to applications that support authoring, deposit, exchange, visualization, reuse, and preservation. The standards support the changing nature of scholarship and scholarly communication, and the need for cyberinfrastructure to support that scholarship, with the intent to develop standards that generalize across all web-based information including the increasing popular social networks of “Web 2.0”.</p></dd> <dt> <a href="/metadata-directory/standards/qudex-qualitative-data-exchange-format.html">QuDEx (Qualitative Data Exchange Format)</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/qudex-qualitative-data-exchange-format.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>The QuDEx standard/schema is a software-neutral format for qualitative data that preserves annotations of, and relationships between, data and other related objects. It can be viewed as the optimal baseline data exchange model for the archiving and interchange of data and metadata.</p></dd> <dt> <a href="/metadata-directory/standards/sdmx-statistical-data-and-metadata-exchange.html">SDMX (Statistical Data and Metadata Exchange)</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/sdmx-statistical-data-and-metadata-exchange.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>A set of common technical and statistical standards and guidelines to be used for the efficient exchange and sharing of statistical data and metadata.</p><p>Sponsoring institutions include BIS, ECB, EUROSTAT, IMF, OECD, UN, and the World Bank. Technical Specification 2.1 was amended in May 2012.</p></dd> </dl> <h2>General Research Data</h2> <dl> <dt> <a href="/metadata-directory/standards/RIF-CS.html">Registry Interchange Format - Collections and Services</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/RIF-CS.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>The Registry Interchange Format - Collections and Services (RIF-CS) schema was developed as a data interchange format for supporting the electronic exchange of collection and service descriptions. It organises information about collections and services into the format required by the Research Data Australia (RDA) Registry.</p></dd> <dt> <a href="/metadata-directory/standards/cerif.html">CERIF (Common European Research Information Format)</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/cerif.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>The Common European Research Information Format is the standard that the EU recommends to its member states for recording information about research activity. Since version 1.6 it has included specific support for recording metadata for datasets.</p></dd> <dt> <a href="/metadata-directory/standards/data-package.html">Data Package</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/data-package.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>The Data Package specification is a generic wrapper format for exchanging data. Although it supports arbitrary metadata, the format defines required, recommended, and optional fields for both the package as a whole and the resources contained within it.</p><p>A separate but linked specification provides a way to describe the columns of a data table; descriptions of this form can be included directly in the Data Package metadata.</p></dd> <dt> <a href="/metadata-directory/standards/datacite-metadata-schema.html">DataCite Metadata Schema</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/datacite-metadata-schema.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>A set of mandatory metadata that must be registered with the DataCite Metadata Store when minting a DOI persistent identifier for a dataset. The domain-agnostic properties were chosen for their ability to aid in accurate and consistent identification of data for citation and retrieval purposes.</p><p>Sponsored by the DataCite consortium, version 3.0 was recently released in 2013.</p></dd> <dt> <a href="/metadata-directory/standards/dcat-data-catalog-vocabulary.html">DCAT (Data Catalog Vocabulary)</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/dcat-data-catalog-vocabulary.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>By using DCAT to describe datasets in data catalogs, publishers increase discoverability and enable applications easily to consume metadata from multiple catalogs. It further enables decentralized publishing of catalogs and facilitates federated dataset search across sites. Aggregated DCAT metadata can serve as a manifest file to facilitate digital preservation.</p></dd> <dt> <a href="/metadata-directory/standards/dublin-core.html">Dublin Core</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/dublin-core.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>A basic, domain-agnostic standard which can be easily understood and implemented, and as such is one of the best known and most widely used metadata standards.</p><p>Sponsored by the Dublin Core Metadata Initiative, Dublin Core was published as ISO Standard 15836 in February 2009.</p></dd> <dt> <a href="/metadata-directory/standards/mods.html">MODS (Metadata Object Description Schema)</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/mods.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>The Metadata Object Description Schema (MODS) is a bibliographic metadata standard implemented in XML. It reimplements a subset of the elements of MARC (Machine Readable Cataloging) using language-based tags instead of numeric ones, and groups them somewhat differently. It is intended both as a simplified version of MARC 21 and as a richer alternative to Dublin Core for applications such as metadata syndication/harvesting and the documentation of digital information packages.</p><p>It was developed in 2002 by the Library of Congress Network Development and MARC Standards Office along with a group of interested experts.</p> </dd> <dt> <a href="/metadata-directory/standards/oai-ore-open-archives-initiative-object-reuse-and-exchange.html">OAI-ORE (Open Archives Initiative Object Reuse and Exchange)</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/oai-ore-open-archives-initiative-object-reuse-and-exchange.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>The goal of these standards is to expose the rich content in aggregations of Web resources to applications that support authoring, deposit, exchange, visualization, reuse, and preservation. The standards support the changing nature of scholarship and scholarly communication, and the need for cyberinfrastructure to support that scholarship, with the intent to develop standards that generalize across all web-based information including the increasing popular social networks of “Web 2.0”.</p></dd> <dt> <a href="/metadata-directory/standards/observations-and-measurements.html">Observations and Measurements</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/observations-and-measurements.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>This encoding is an essential dependency for the OGC Sensor Observation Service (SOS) Interface Standard. More specifically, this standard defines XML schemas for observations, and for features involved in sampling when making observations. These provide document models for the exchange of information describing observation acts and their results, both within and between different scientific and technical communities.</p></dd> <dt> <a href="/metadata-directory/standards/premis.html">PREMIS</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/premis.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>The PREMIS (Preservation Metadata: Implementation Strategies) Data Dictionary defines a set of metadata that most repositories of digital objects would need to record and use in order to preserve those objects over the long term. It has its roots in the Open Archival Information System Reference Model but has been strongly influenced by the practical experience of such repositories. While the Data Dictionary can be used with other standards to influence the creation of local application profiles, an XML Schema is provided to allow the metadata to be serialized independently.</p> <p>PREMIS was initially developed by the Preservation Metadata: Implementation Strategies Working Group, convened by OCLC and RLG, and is currently maintained by the PREMIS Maintenance Activity, lead by the Library of Congress.</p></dd> <dt> <a href="/metadata-directory/standards/prov.html">PROV</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/prov.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>Provenance is information about entities, activities, and people involved in producing a piece of data or thing, which can be used to form assessments about its quality, reliability or trustworthiness. The PROV Family of Documents defines a model, corresponding serializations and other supporting definitions to enable the inter-operable interchange of provenance information in heterogeneous environments such as the Web.</p></dd> <dt> <a href="/metadata-directory/standards/rdf-data-cube-vocabulary.html">RDF Data Cube Vocabulary</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/rdf-data-cube-vocabulary.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>The standard provides a means to publish multi-dimensional data, such as statistics, on the web in such a way that it can be linked to related data sets and concepts using the W3C RDF (Resource Description Framework) standard. The model underpinning the Data Cube vocabulary is compatible with the cube model that underlies SDMX (Statistical Data and Metadata eXchange), an ISO standard for exchanging and sharing statistical data and metadata among organizations.</p></dd> <dt> <a href="/metadata-directory/standards/repository-developed-metadata-schemas.html">Repository-Developed Metadata Schemas</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/repository-developed-metadata-schemas.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>Some repositories have decided that current standards do not fit their metadata needs, and so have created their own requirements.</p></dd> <dt> <a href="/metadata-directory/standards/ro-crate.html">RO-Crate</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/ro-crate.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>RO-Crate is a community effort to establish a lightweight approach to packaging research data with their metadata. It is based on schema.org annotations in JSON-LD, and aims to make best-practice in formal metadata description accessible and practical for use in a wider variety of situations, from an individual researcher working with a folder of data, to large data-intensive computational research environments.</p> </dd> <dt> <a href="/metadata-directory/standards/schemaorg.html">schema.org</a> <a href="https://github.com/rd-alliance/metadata-directory/edit/gh-pages/standards/schemaorg.md" class="btn btn-default btn-xs" role="button"> <span class="glyphicon glyphicon-edit"></span> Edit</a> </dt> <dd><p>Schema.org is a collaborative, community activity with a mission to create, maintain, and promote schemas for structured data on the Internet, on web pages, in email messages, and beyond. Schema.org vocabulary can be used with many different encodings, including RDFa, Microdata and JSON-LD. These vocabularies cover entities, relationships between entities and actions, and can easily be extended through a well-documented extension model. Over 10 million sites use Schema.org to markup their web pages and email messages. Many applications from Google, Microsoft, Pinterest, Yandex and others already use these vocabularies to power rich, extensible experiences. </p></dd> </dl> <hr /> <footer> The RDA Metadata Standards Directory was maintained by <a href="https://github.com/alex-ball">Alex Ball</a>, <a href="https://github.com/gugek">Sean Chen</a>, and <a href="https://github.com/katealderete">Kate Anne Alderete</a>. <br> This site uses the <a href="https://github.com/arnp/herring-cove">Herring Cove</a> theme by <a href="https://github.com/dustin-allen">Dustin Allen</a>. <br> This page was generated by <a href="http://pages.github.com">GitHub Pages</a>. </footer> </div> <!-- Bootstrap core JavaScript--> <script src="/metadata-directory/js/jquery-3.6.4.min.js"></script> <script src="/metadata-directory/js/bootstrap.min.js"></script> <script src="/metadata-directory/js/hc.js"></script> </body> </html>