The mzTab data exchange format: communicating mass-spectrometry-based proteomics and metabolomics experimental results to a wider audience.

The HUPO Proteomics Standards Initiative has developed several standardized data formats to facilitate data sharing in mass spectrometry (MS)-based proteomics. These allow researchers to report their complete results in a unified way. However, at present, there is no format to describe the final qualitative and quantitative results for proteomics and metabolomics experiments in a simple tabular format. Many downstream analysis use cases are only concerned with the final results of an experiment and require an easily accessible format, compatible with tools such as Microsoft Excel or R. We developed the mzTab file format for MS-based proteomics and metabolomics results to meet this need. mzTab is intended as a lightweight supplement to the existing standard XML-based file formats (mzML, mzIdentML, mzQuantML), providing a comprehensive summary, similar in concept to the supplemental material of a scientific publication. mzTab files can contain protein, peptide, and small molecule identifications together with experimental metadata and basic quantitative information. The format is not intended to store the complete experimental evidence but provides mechanisms to report results at different levels of detail. These range from a simple summary of the final results to a representation of the results including the experimental design. This format is ideally suited to make MS-based proteomics and metabolomics results available to a wider biological community outside the field of MS. Several software tools for proteomics and metabolomics have already adapted the format as an output format. The comprehensive mzTab specification document and extensive additional documentation can be found online.

Mass spectrometry (MS) has become a major analysis tool in the life sciences (1). It is currently used in different modes for several “omics” approaches, proteomics and metabolomics being the most prominent. In both disciplines, one major burden in the exchange, communication, and large-scale (re-) analysis of MS-based data is the significant number of software pipelines and, consequently, heterogeneous file formats used to process, analyze, and store these experimental results, including both identification and quantification data. Publication guidelines from scientific journals and funding agencies' requirements for public data availability have led to an increasing amount of MS-based proteomics and metabolomics data being submitted to public repositories, such as those of the ProteomeXchange consortium (2) or, in the case of metabolomics, the resources from the nascent COSMOS (Coordination of Standards in Metabolomics) initiative (3).

In the past few years, the Human Proteome Organization Proteomics Standards Initiative (PSI) has developed several vendor-neutral standard data formats to overcome the representation heterogeneity. The Human Proteome Organization PSI promotes the usage of three XML file formats to fully report the data coming from MS-based proteomics experiments (including related metadata): mzML (4) to store the “primary” MS data (the spectra and chromatograms), mzIdentML (5) to report peptide identifications and inferred protein identifications, and mzQuantML (6) to store quantitative information associated with these results.

Even though the existence of the PSI standard data formats represents a huge step forward, these formats cannot address all use cases related to proteomics and metabolomics data exchange and sharing equally well. During the development of mzML, mzIdentML, and mzQuantML, the main focus lay on providing an exact and comprehensive representation of the gathered results. All three formats can be used within analysis pipelines and as interchange formats between independent analysis tools. It is thus vital that these formats be capable of storing the full data and analysis that led to the results. Therefore, all three formats result in relatively complex schemas, a clear necessity for adequate representation of the complexity found in MS-based data.

An inevitable drawback of this approach is that data consumers can find it difficult to quickly retrieve the required information. Several application programming interfaces (APIs) have been developed to simplify software development based on these formats (7–9), but profound proteomics and bioinformatics knowledge still is required in order to use them efficiently and take full advantage of the comprehensive information contained.

The new file format presented here, mzTab, aims to describe the qualitative and quantitative results for MS-based proteomics and metabolomics experiments in a consistent, simpler tabular format, abstracting from the mass spectrometry details. The format contains identifications, basic quantitative information, and related metadata. With mzTab's flexible design, it is possible to report results at different levels ranging from a simple summary or subset of the complete information (e.g. the final results) to fairly comprehensive representation of the results including the experimental design. Many downstream analysis use cases are only concerned with the final results of an experiment in an easily accessible format that is compatible with tools such as Microsoft Excel® or R (10) and can easily be adapted by existing bioinformatics tools. Therefore, mzTab is ideally suited to make MS proteomics and metabolomics results available to the wider biological community, beyond the field of MS.

mzTab follows a similar philosophy as the other tab-delimited format recently developed by the PSI to represent molecular interaction data, MITAB (11). MITAB is a simpler tab-delimited format, whereas PSI-MI XML (12), the more detailed XML-based format, holds the complete evidence. The microarray community makes wide use of the format MAGE-TAB (13), another example of such a solution that can cover the main use cases and, for the sake of simplicity, is often preferred to the XML standard format MAGE-ML (14). Additionally, in MS-based proteomics, several software packages, such as Mascot (15), OMSSA (16), MaxQuant (17), OpenMS/TOPP (18, 19), and SpectraST (20), also support the export of their results in a tab-delimited format next to a more complete and complex default format. These simple formats do not contain the complete information but are nevertheless sufficient for the most frequent use cases.

mzTab has been designed with the same purpose in mind. It can be used alone or in conjunction with mzML (or other related MS data formats such as mzXML (21) or text-based peak list formats such as MGF), mzIdentML, and/or mzQuantML. Several highly successful concepts taken from the development process of mzIdentML and mzQuantML were adapted to the text-based nature of mzTab.

In addition, there is a trend to perform more integrated experimental workflows involving both proteomics and metabolomics data. Thus, we developed a standard format that can represent both types of information in a single file.

EXPERIMENTAL PROCEDURES

The development of mzTab was influenced by existing text-based output formats from several search engines and analysis pipelines. Development of the model started at the beginning of 2011, after the finalization of mzIdentML 1.1. The complete mzTab specification document (version 1.0) can be found online (http://mztab.googlecode.com), along with example files demonstrating the use of mzTab for several scenarios.

mzTab aims to

be simpler than the XML-based standard formats to make MS-based proteomics/metabolomics results accessible to researchers outside the respective fields;

be accessible using standard software such as Microsoft Excel® or Open Office Spreadsheet;

allow the reporting of results at different levels of detail, ranging from the summarized final results to a detailed representation of the results including the experimental design;

safeguard/require a minimal level of information about a proteomics/metabolomics study's results to be used as a standard documentation format for “supplementary material” sections of publications;

support export from mzIdentML and mzQuantML;

support efficient import into statistical tools such as R, SIMCA®, or SPSS®;

make MS-derived results easily accessible to scripting languages;

be suitable as an output format for Web-based services; and

support references back to more detailed sources.

Although mzTab can be used to report a detailed view on data, it explicitly does not aim to capture the whole complexity and evidence trail of a proteomics study. Even the most complex mzTab files still include simplifications/assumptions of the experimental results. This, for instance, is the case in identification (e.g. protein inference/grouping is only supported to a limited extent) and quantification results (e.g. the coordinates for isotope patterns in quantified two-dimensional “features” cannot be fully reported). This missing information can be reported using the existing PSI standard formats mzIdentML and mzQuantML.

The model was developed as a tab-delimited file accompanied by controlled vocabulary (CV) terms and definitions as part of the PSI-Mass Spectrometry CV, also used in other PSI formats and actively maintained by the PSI-Mass Spectrometry and PSI-Proteomics Informatics working groups (22).

mzTab Overview

mzTab is a tab-delimited text file format that can store protein, peptide, peptide-spectrum match (PSM), small-molecule identification, and basic quantification data, as well as different levels of metadata related to the processed samples, experimental design, and used experimental methods. The data are stored in five different sections: “metadata,” “protein,” “peptide,” “PSM,” and “small molecule” (Fig. 1). Every line in an mzTab file starts with a three-letter code indicating the type of information captured in the line: “MTD” for lines from the metadata section, “PRH” for the “protein” section header, “PRT” for protein identifications, “PEH” for the “peptide” section header, “PEP” for peptide identifications, “PSH” for the “PSM” section header, “PSM” for PSMs, “SMH” for the “small molecule” section header, “SML” for small molecule identifications, and “COM” for a comment line. The “metadata” section is mandatory; every other section is optional but must not be present more than once in a single file.

Fig. 1.

A diagrammatic representation of the data model for mzTab.

There are two types of mzTab files: identification and quantification. This is specified in the mandatory metadata field “mzTab-type.” Identification files can be used to report peptide, protein, and small molecule identifications. Quantification files can be used for quantification results, which optionally may contain identification results about the quantified protein/peptide or small molecules.

In addition, there are two levels of detail (called “modes”) of reporting data in mzTab files: “summary” and “complete.” The “summary” mode can be used to report the final results, putting together data coming from, for example, different replicates. The “complete” mode is used if detailed information for each individual assay/replicate is provided. The mode is specified in the mandatory metadata field “mzTab-mode.” This flexible design was needed to support as many different experimental scenarios as possible in a single, relatively simple file format.

Similar to mzIdentML and mzQuantML, mzTab files do not contain the underlying MS data but may contain references to the spectra in external files. mzTab uses exactly the same method to reference external spectra as do mzIdentML and mzQuantML. Additionally, each identification reported in an mzTab file can be linked to its original source.

Modeling an Experimental Design in mzTab

mzTab supports the reporting of technical/biological replicates within experimental designs using an adaptation of the system originally developed for mzQuantML. This is made up of four components:

(i) Study variable. Study variables represent the core final results of the study (e.g. inflammatory response versus control). Often, these will have been derived by averaging the results of a group of replicate measurements (assays). In files where assays are reported, study variables have references to assays. The same concept could be called an “experimental factor.”

(ii) MS run. An MS run is effectively one run (or set of runs on prefractionated samples) on an MS instrument and is referenced from the assay in different contexts.

(iii) Assay—the application of a measurement of the sample (in this case through MS) producing values about small molecules, peptides, or proteins. One assay is typically mapped to one MS run in the case of label-free MS analysis, or multiple assays are mapped to one MS run for multiplexed techniques (e.g. iTRAQ or SILAC), along with a description of the label or tag applied.

(iv) Sample—a biological material that has been analyzed, to which descriptors of species such as cell/tissue type can be attached. In all mzTab files, these can be reported in the metadata section as “sample[1-n]-description.” Samples are not mandatory in mzTab, as many software packages cannot determine what type of sample was analyzed (e.g. whether biological or technical replication was performed).

Metadata Section

The “metadata” section in mzTab was deliberately kept flexible, and the majority of fields are optional. Therefore, it is possible to report different levels of experimental annotation depending on the interest of the producer of the files, ranging from basic annotations to the complete metadata defined by the Human Proteome Organization PSI as the minimum information about a proteomics experiment (MIAPE) (23) or the core information for metabolomics reporting (CIMR) guidelines (24).

Whereas the “protein,” “peptide,” “PSM,” and “small molecule” sections are classical table-based structures with a header line, the “metadata” section contains one tab-separated key-value pair per row. This layout was chosen because the “metadata” section can contain considerably more fields than other sections, and this arrangement helps the files remain more readable.

The “metadata” section can hold basic information about the study—for example, a title, a human readable description, contact information, publication references, false discovery rates, basic properties of the analyzed sample(s), assays, MS runs, and study variables. The protocol can be described using CV terms for individual steps. Information about the mass spectrometer(s) used can be stored, as well as details about the software tool(s) (including settings) used to generate the data. Furthermore, it is possible to specify the quantification method used together with the reagents. Similar to the additional columns in the table-based sections (see below), it is possible to specify custom fields in the metadata. These can hold any kind of information as CV or user parameters. Several example snippets are present throughout the manuscript to facilitate the comprehension of the format. Nevertheless, these are not comprehensive examples of mzTab files. Complete examples meant to be taken as references can be found online (http://mztab.googlecode.com). Below is an excerpt from the “metadata” section.

Peptide and Protein Identification Results

Protein/peptide identifications are reported in the “protein” and “PSM” sections, respectively. As mentioned above, the “peptide” section is used to report aggregated quantification data based on several PSMs. Its use is not recommended in identification files. In the “PSM” section, peptide identifications are linked to proteins by the “accession” column. It is also possible to report peptides that do not reference any protein by setting the protein accession to “null”.

Next to the protein accession, the “protein” section can hold a human-readable description (generally the protein's name), the species, and the source protein database. As an overview, three kinds of values can be reported in order to indicate how many PSMs support a protein identification: the total number of PSMs, the number of distinct peptides (based on both the sequence and modifications), and the number of unique peptides (distinct number of peptides that can be unambiguously assigned to the given protein in the sequence database). Furthermore, it is possible to provide the coverage of the protein sequence by the identified peptides; the search engine(s) used, including scores that identified the protein; and a reliability score of the protein identification. In addition, gene ontology terms that are used to annotate the protein (25) can be reported in this section. Below is an example from the “protein” section.

In the “PSM” section, it is possible to indicate whether the peptides were unambiguously assigned to a given protein. Additionally, for proteins, information about the sequence database and the search engines used for the identification can be included. Furthermore, MS-specific information, such as the precursor's m/z ratio, charge state, and retention time, can be stored. Every PSM can be linked to a spectrum in an external MS data file and can be given a reliability score (see below).

In current proteomics pipelines, it has become a common procedure to process the MS data using multiple search engines (26, 27) and post-processing software. mzTab explicitly supports this use case by allowing peptide and protein identifications to be associated with multiple search engines and search engine scores. Thus, the information that a given peptide was, for example, identified by three search engines whereas another peptide was identified by only a single search engine, as well as a possible overall score, can be reported explicitly. Search engine scores are reported in one column per score (search_engine_score[1-n]). The type of score reported in the different sections is defined in the “metadata” section using a CV parameter. Below is an example from the “PSM” section.

It is common that an identified peptide sequence cannot be unambiguously attributed to a single protein and may originate from several proteins—the so-called protein inference problem (28). It is not possible to model detailed protein inference data without a significant level of complexity, as in mzIdentML (5). Therefore, as a compromise, it was decided to model protein inference in a simple way in mzTab, excluding detailed information on how ambiguity was resolved. Protein entries in mzTab files contain the column “ambiguity_members.” The protein accessions listed in this field should identify proteins that were also identified through the same set of peptides or spectra, or proteins supported by a largely overlapping set of evidence, and could also be a viable candidate for the “true” identification of the entity reported. Therefore, the definition of “indistinguishable proteins” and thus also of the “ambiguity_members” is up to the generating software and will vary between mzTab files generated by different resources. The mapping of a single PSM to multiple accessions is supported through the reporting of the same PSM on multiple rows of the PSM section, as exemplified below.

Metabolomics Identification Results

There is currently no widely used standardized file format available to store MS-based metabolomics data. The COSMOS initiative (3) aims to address this issue and is working on the development of the exchange formats and terminological artifacts needed to describe, exchange, and query both metabolomics data and experimental metadata. In addition, mzQuantML has been designed to capture such data in a detailed manner, but its formalization is ongoing. We therefore added explicit structures to mzTab that can hold MS-based metabolomics identifications and quantification results. Small molecules are specified through an identifier in mzTab. These identifiers should generally be entries in compound databases used in the respective field—for example, Human Metabolome Database entries (29) or identifiers from Chemical Entities of Biological Interest (30), PubChem (31), LipidHome (32), or LIPID MAPS (33). Apart from these unique identifiers, small molecules can be assigned a chemical formula; Simplified Molecular-input Line-entry System (SMILES) and/or IUPAC International Chemical Identifier identifiers; or a human-readable description together with MS-related information such as m/z value, charge state, retention time, source database, and search engine, including, potentially, several scores. Furthermore, every small-molecule identification can also be linked to a source spectrum and given a reliability score based on an agreement from the Metabolomics Standards Initiative (24, 34) (see below). Below is an example from the “small molecule” section.

Use of Controlled Vocabulary

Because the use of CVs and ontologies has proved to be effective in other PSI formats, the same principle was applied for mzTab. CV terms help to make the stored data machine-comprehensible and comparable. Therefore, mzTab also makes use of CV terms to flexibly report several pieces of information and uses the same CVs that are being constantly enhanced for use with mzIdentML and mzQuantML (e.g. PSI-Mass Spectrometry).

In mzTab, CV parameters are reported using the simple structure [CV label, accession, name, value]—for example, [MS, MS:1001364, pep:global FDR, 0.1]. If a value cannot be represented using a CV term, the data producers must contact PSI to have the terms added to the CV in order to guarantee the integrity of the reported data. However, an alternative mechanism exists: so-called user parameters can be reported, and in this case reporting of the CV label and accession is not mandatory. This is useful, for example, when a new technology is introduced that is not yet represented in the respective CV or ontology. These parameters are not machine-comprehensible but at least provide the possibility of storing the data in human-readable form. The names of user parameters should be chosen by the user to describe the semantics of the reported value.

Identification Reliabilities

All protein, peptide, PSM, and small-molecule identifications reported in an mzTab file can be assigned a reliability score (“reliability” column in all tables).

The reliability is reported as an integer between 1 and 3 for proteomics results and should be interpreted as follows:

1: high reliability

2: medium reliability

3: poor reliability

For metabolomics (“small molecule” section), according to the current Metabolomics Standards Initiative agreement, the reliability should be reported as an integer between 1 and 4 and should be interpreted as follows:

1: identified metabolites

2: putatively annotated compounds

3: putatively characterized compound classes

4: unknown compounds

These abstract quality metrics were chosen over others to highlight the fact that scores from different sources and/or pipelines are not directly comparable, even if they are represented as p or e values. Thus, this score makes it apparent that any scoring approach is completely dependent on the data producer.

The idea behind this score was to mimic the general concept of “resource-based trust” and complement the rather complex search engine scores with a simple score accessible to non-proteomics experts. If resources/researchers now report their reliabilities using these metrics and document how their metric is generated, users can base their own interpretation of the results on their trust in the resource or research group.

Reporting Modifications

Modifications are modeled using a specific modification object with the following format: {position}{Parameter}-{Modification or Substitution identifier} {neutral loss}.

{position} is optional depending on the section where the modification is reported, as it might not be applicable to all types of small molecules. N- and C-terminal modifications in proteins and peptides are reported with the position set at zero or the amino acid length plus one, respectively. This element also allows modifications to be assigned to ambiguous locations and can be used to report reliabilities for every potential location using CV parameters. mzTab is thus the first PSI file format that explicitly models ambiguous modification positions as well as position-based scores. Neutral losses can also be reported using CV parameters. They may be either reported as separate modifications or associated with an existing one by appending it to the modification object.

For proteins and peptides, modifications should be reported using either Unimod (35) or the PSI-MOD (36) identifiers as {Modification identifier}. Because these two ontologies are not applicable to small molecules, so-called CHEMMODs were suggested for mzTab. Two types of CHEMMODs are allowed: specifying a chemical formula and specifying a mass shift. CHEMMODs must not be used for protein/peptide modifications if the respective entry is present in either the PSI-MOD or the Unimod ontology. Furthermore, mass differences must not be reported if the given difference can be expressed through a known and unambiguous chemical formula.

Quantitative Data

There are multiple quantification techniques available for MS-based experiments that often result in different types of data. The goal of mzTab was to provide a generic view on quantitative MS-based identification data. This is achieved using quantitation mzTab files. Additionally, the “complete” files allow reporting on the experimental design, a key point in every quantification study. The “peptide” section is used to aggregate quantification data on a per-peptide level.

Quantification techniques generally result in a numerical abundance measurement of an analyte. Some techniques allow or require multiple samples to be multiplexed and analyzed in a single MS run. When several biological samples are multiplexed, these samples are referred to as “assays” in mzTab. For every assay, an abundance value must be reported for each peptide, protein, or small-molecule identification (with nulls or zeros allowed if an entity is not measured or measured with a zero value in any given replicate). The used quantification method, metric units, and, for example, label reagent for a specific assay should be reported in the “metadata” section. Study variables can be included that encompass multiple assays and for which standard deviation and standard error should be reported.

The results of quantitative measurements are reported in additional columns that are appended after the mandatory columns in the respective section. The assay and/or study variables' I.D.s are part of the column name (for example, protein_abundance_assay[1] or protein_abundance_study_variable[1]).

It is not expected that these numbers will be comparable across multiple mzTab files, as different quantitative methods can generally not be compared directly. This method of reporting quantification data is used in exactly the same way for proteins, peptides, and small molecules. There are several example files online (http://mztab.googlecode.com) that exemplify how quantitative data can be reported in mzTab files including different approaches such as SILAC, iTRAQ, or label-free quantification. There is also an example from a quantitative lipidomics experiment. Below is an example corresponding to one SILAC experiment.

Comments on Specific Use Cases

Additional Columns to Report Additional Custom Information

It is desirable to be able to report information not included in the “core model” of any data format. For this reason, additional columns can be added to mzTab files to hold such custom data. Additional columns can be added to the end of the existing columns in all the table-based sections (“protein,” “peptide,” “PSM,” and “small molecule”). These column headers must start with the prefix “opt_” or “opt_global” (see details in the specification document) and can be used to store resource-dependent information. It is recommended that one use CV parameter accessions as optional column names and thereby explicitly define their contents. These column names follow the format opt_cv_{accession}_{parameter name} (for example, opt_cv_MS:1001975_delta_m/z to report the “delta m/z” for each peptide identification, or opt_cv_MS:1002217_decoy_peptide to identify decoy peptide identifications).

Referencing External Resources

All identifications reported in an mzTab file can reference external resources that contain detailed evidence supporting the identification. This link is stored in the “URI” column present in each of the table-based sections. The target that these universal resource identifiers point to is dependent on the resource that generated the mzTab file. If, for example, PeptideAtlas was exporting data in the mzTab format, the universal resource identifier would be expected to point to the identification's entry within the respective PeptideAtlas build. mzTab files originating from an mzIdentML file, for example, can reference the mzIdentML file using the “URI” column. When quantitative values are reported coming from an mzQuantML file, the mzQuantML file should be referenced, as it contains the reference to the underlying mzIdentML file. Thus, the simplified data represented in an mzTab file can easily be connected to the complete underlying evidence.

Referencing External Spectra

In mzTab, peptides and small molecules can be linked to source spectra in external files. This is accomplished through the “ms-run[1-n]-location” field in the “metadata” section, which holds all characteristics of a specific source file. The “spectra_ref” column in the appropriate tables is then used to unambiguously link to specific spectra within these source files.

Software Implementations

Several software implementations already exist for mzTab that can be used by developers and end-users (Table I). The mzTab schema was constantly tested during its development through various implementations. The jmzTab Java API is the current reference implementation for mzTab (37). It supports reading and writing of mzTab files and automatically checks their structural validity. The API provides functionality to convert PRIDE XML files to mzTab.

Table I

Software implementations of mzTab (by June 2014)

In addition, several popular proteomics software tools can already use mzTab files. OpenMS (19) offers an infrastructure for the development of MS-related software. Together with the OpenMS Proteomics Pipeline (18), it provides a full-featured proteomics and metabolomics data processing pipeline that can directly write mzTab files from version 1.11 on. In the MaxQuant software (17), a converter to mzTab format will be available from version 1.4.2 onward. The converter is implemented as a plugin for the Perseus software package.

mzTab read and write support has also been added to the R/Bioconductor package MSnbase (38), from version 1.5.6. It can seamlessly import data stored in mzTab files, including quantitative data and metadata, into flexible object classes to subsequently apply contemporary state-of-the-art statistical procedures readily available through the R statistical programming environment. The package provides ample documentation and examples on how to import from and export to mzTab.

The LipidDataAnalyzer (39), a tool for analyzing lipidomics LC-MS data developed at the Graz University of Technology, is the first non-proteomics tool to fully support mzTab export using the jmzTab API (from version 1.6.0). The LipidDataAnalyzer is able to export identified molecules from related experiments in one mzTab file including quantitative information extracted from MS data.

Apart from these tools, the new PRIDE submission tool, PRIDE Converter 2 (40), can convert multiple search engine output files to mzTab files and can also read quantitative and gel-based data from mzTab files to include them in the generated PRIDE XML files. PRIDE Converter 2 uses the jmzTab API to process mzTab files, allowing the inclusion of quantification information into PRIDE XML. Finally, a library of Java routines has been created for mzQuantML that contains a converter from mzQuantML to mzTab files.

To make the development of applications supporting mzTab as easy as possible, we created an additional document specifically targeted at developers: The 20 Minute Guide to mzTab. This is a quick introduction to the basics of mzTab and explains the format using examples rather than words. Additionally, it includes a comprehensive list of all fields and columns found in mzTab. This document, as well as the comprehensive specification document, can be found online (http://mztab.googlecode.com). We also created a comparison of the main features of mzIdentML, mzQuantML, and mzTab (supplemental Table S1) and a size comparison between different mzTab and PRIDE XML files (supplemental Table S2).

Additional Use Cases

One of the main goals of mzTab is to share and communicate MS-based proteomics and metabolomics results with researchers from other biological sciences. mzTab can provide a standardized summary of data submissions to proteomics repositories. mzTab is used in the context of the ProteomeXchange consortium data workflow. The ProteomeXchange consortium aims to promote standard submission and data-sharing policies among the main MS-based proteomics data repositories, including PRIDE and PeptideAtlas. At present, summary mzTab files are generated for each MS/MS “complete” submission to ProteomeXchange via PRIDE and are made available for download.

Laboratory information management systems often do not need to and cannot store the complete information acquired during a proteomics experiment. Still, researchers require a quick overview of previously performed experiments in their laboratory information management systems. mzTab might thus be an ideal basis for the development of laboratory information management systems that need to store basic proteomics/metabolomics results. The flexibility of the format and the possibility of adding custom fields make it suitable for storing highly heterogeneous data. Through the addition of optional columns after the mandatory fields, mzTab can be tailored for the specific needs of each research group.

For metabolomics, the development of mzTab might be even more helpful because, to the best of our knowledge, there is no widely accepted data format for MS-based results yet. mzIdentML was not developed with this use case in mind and cannot be easily adapted to support non-proteomics data. mzQuantML aims to store quantification information for small molecules, but the mechanism still needs to be formalized. At present, mzTab can report results from lipidomics approaches, as demonstrated by the implementation in the LipidDataAnalyzer (39). The MetaboLights repository (41) at the European Bioinformatics Institute for metabolomics experiments has so far used a version of mzTab that contains the “small molecule” section but not a fully compliant “metadata” section. However, for streamlining data submissions, it is planned to fully comply with the final version of the format specification.

We also envisage that the format will become a way to standardize the supplementary information provided by authors to scientific journals. In the case of proteomics, there are different reporting policies depending on the journal. Molecular & Cellular Proteomics, an early adopter in terms of guidelines, developed the so-called Paris guidelines for reporting proteomics data (42), which include a requirement to provide different metrics related to the published data. The reliability score could be used by the authors or the journal to report which proportion of the reported data in a manuscript met the quality criteria (if any) for each identification. Level 1 (high reliability) would mean “criteria passed,” whereas 3 (poor reliability) would mean the opposite, and 2 (medium reliability) would be reserved for borderline cases that are not straightforward to assess. Also, as mentioned before, different reporting requirements can be supported thanks to the flexibility of the format.

CONCLUSIONS

mzTab was developed to bridge the gap between the high level of detail found in existing XML-based standards formats, required in order to model complete proteomics data, and the need to easily report proteomics and metabolomics final results. The format was developed by members of the PSI Proteomics Informatics working group and other collaborators representing a wide array of academic research groups and projects. The complete development process was based around the mzTab Google Code page, which also hosts the complete format specification and the official software implementation jmzTab. The concept behind mzTab has previously been successfully applied in other bioinformatics fields (for instance, MAGE-TAB and MITAB).

After the standardization process is finished, mzTab will be a stable format. However, if needed, extensions to the proposed structure can be made in a flexible way. For instance, new optional sections in addition to the existing ones (“metadata,” “protein,” “peptide,” “PSM,” and “small molecule”) could be added without breaking existing software. However, alterations to the schema that would break existing parsing code will not be made without the format being reentered into the standardization process. We expect that the release of mzTab will increase data sharing for MS-based proteomics and metabolomics. We also envisage that the format could be extended to support other uses cases, such as peptide or small-molecule spectral clusters (43), or adapted to report selected reaction monitoring transitions, including the related quantification results.

We encourage readers to provide further input on the standard by contacting the authors, joining the PSI mailing list via the Google Code page, or attending a PSI meeting.