ProDBWiki/DeveloperDocumentation/MzDataImportSpecification: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
imported>KaiRunte No edit summary |
||
Line 6: | Line 6: | ||
mzData is an XML exchange format for mass-spectrometry data and is created and maintained by the [http://psidev.sourceforge.net Proteomics Standards Initiative]. The format is defined by an XML schema and an ontology. The ontology defines legal values for so-called cvParam elements to provide flexibility concerning new mass-spectrometers and their componentry. | mzData is an XML exchange format for mass-spectrometry data and is created and maintained by the [http://psidev.sourceforge.net Proteomics Standards Initiative]. The format is defined by an XML schema and an ontology. The ontology defines legal values for so-called cvParam elements to provide flexibility concerning new mass-spectrometers and their componentry. | ||
An mzData format importer for | An mzData format importer for ProDB needs to consider two different mapping problems. The first one is a relatively simple one: XML elements/attributes need to be mapped onto ProDB object attributes. The second kind of mapping is a little bit more difficult: we need to map ontology-controlled cvParam elements onto ProDB object attributes. An example: |
Revision as of 12:26, 16 February 2005
= mzData Import Specification =
== Introduction ==
mzData is an XML exchange format for mass-spectrometry data and is created and maintained by the Proteomics Standards Initiative. The format is defined by an XML schema and an ontology. The ontology defines legal values for so-called cvParam elements to provide flexibility concerning new mass-spectrometers and their componentry.
An mzData format importer for ProDB needs to consider two different mapping problems. The first one is a relatively simple one: XML elements/attributes need to be mapped onto ProDB object attributes. The second kind of mapping is a little bit more difficult: we need to map ontology-controlled cvParam elements onto ProDB object attributes. An example: