eduKateSG · Why Science?
Write a peak interpretation as a compact, testable scientific statement—while preserving ions, deltas, confidence, alternatives and source spectra
Choose the closest route, then return to the full index whenever you need the wider evidence chain.
Science learning becomes powerful when students can tell a measured pattern from a model, a statistical decision from a mechanism, and a useful lead from a finished conclusion. mzPAF is the HUPO Proteomics Standards Initiative Peak Annotation Format for describing the proposed origin of fragment-ion peaks in mass spectra, especially peptide spectra. The official PSI page records final version 1.0.1, ratified and released on 5 May 2026 after a patch to version 1.0.0. mzPAF can express ion types, neutral gains or losses, isotopes, adducts, charge, observed-minus-theoretical mass deltas, confidence and multiple possible explanations in a compact string. A well-formed annotation describes an interpretation; it does not prove that the ion assignment, peptide identification or biological conclusion is correct. This guide supports Primary Science, PSLE Science, Secondary Science, O-Level Science and STEM education as a longform evidence-reading route; it is not medical advice, a laboratory protocol, an admission promise or a career guarantee.
Related eduKate reading: mzSpecLib and open spectral libraries; ProForma and proteoform sequence notation; mzML and open mass-spectrometry data; PSI-MS and mass spectrometry vocabulary; Science Learning Hub; Education Hub; STEM Education; Careers by Subject Capability.
Primary and official sources checked on 12 October 2026: HUPO-PSI official mzPAF page, final version 1.0.1 released 5 May 2026, checked 12 October 2026; HUPO-PSI official mzPAF repository, specification and examples, checked 12 October 2026; HUPO-PSI official mzSpecLib standard page, checked 12 October 2026; 2026 Singapore–Cambridge O-Level Biology syllabus; MOE G2/G3 Lower Secondary Science teaching and learning syllabus; 2026 MOE G2 Computing syllabus. Specifications, drafts, vocabularies, tools and recommendations can change, so preserve dated documentation, exact source data and software versions.
A deeper reading route
A mass spectrum is a collection of peaks, commonly represented by mass-to-charge ratio and intensity. To explain a peak, software or a researcher may propose that it is a particular fragment ion from a peptide. Before mzPAF, tools often used local shorthand whose meaning was clear only inside one program. mzPAF supplies a shared grammar so the proposed origin can travel with the numerical peak and be parsed consistently.
The official mzPAF page says the format is focused on peptide fragment ions and is intended for spectral libraries, other fragment-describing formats and annotation software. This places it beside mzSpecLib rather than inside a raw-data container. mzML keeps acquired arrays, mzSpecLib organises reusable library spectra, and mzPAF records peak-level interpretations. Each layer should retain its own provenance.
The official examples show a compact composition. An annotation names an ion; a slash introduces the observed-minus-theoretical mass delta; an asterisk can introduce confidence; and comma-separated items can preserve alternative explanations. The grammar is case-sensitive and has no general length limit. Parsers must therefore follow the specification rather than split strings on punctuation casually.
Peptide-series ions such as a, b, c, x, y and z are only one part of the model. The specification can represent unknown ions, immonium ions, internal fragments, intact precursors, reference ions, named compounds, formulas and SMILES-based entities. Advanced notation can add neutral gains or losses, isotopes, adduct types and charge. The breadth is useful because a real spectrum is not made solely of textbook b and y ions.
A mass delta is evidence about fit between observation and theory. It can be stated in an m/z unit or in parts per million under the specification. Its sign matters because it is observed minus theoretical. A small delta supports compatibility under the instrument and calibration model, but equal or similar mass does not uniquely establish chemical identity.
Confidence belongs to the annotation, not automatically to the entire spectrum or peptide. If two explanations share a peak, each may carry its own confidence. A software score should document how it becomes a confidence value; the syntax alone does not define calibration. Values outside the method’s supported domain should remain visibly uncertain.
Multiple analytes can contribute to one spectrum, and mzPAF can distinguish analyte references. This matters for chimeric spectra, co-isolation and spectral-library records containing more than one molecular contributor. The analyst should verify that referenced analytes exist and that the annotation uses the correct sequence, modification and charge context.
Version history is scientifically relevant. The PSI page says 1.0.0 was final on 10 August 2025 and that implementation revealed minor errors and ambiguities, leading to ratified patch 1.0.1 on 5 May 2026. A record should name its specification version so another tool does not silently apply earlier grammar to a later string.
A useful audit chooses one peak and reconstructs its theoretical mass from the analyte sequence, modifications, ion type, losses, isotopes, adduct and charge. It then compares the stated delta with the observed m/z and reads any confidence or alternative. This turns a compact label into an inspectable calculation instead of decorative text above a plot.
The optimistic value is a shared conversation about peaks. Students, library builders and software developers can read the same annotation without discarding ambiguity. A standard string does not make a guess true, but it makes the guess precise enough to check, challenge and improve.
Annotation software should report whether it generated one explanation, ranked alternatives or calibrated probabilities. A confidence number without a producing model and reference set is not portable. Preserve raw score, conversion rule and any filtering threshold, then check calibration on spectra representative of the intended instrument and fragmentation method.
Round-trip tests should include simple series ions and difficult cases: multiple analytes, internal fragments, neutral losses, isotopes, adducts, embedded ProForma and alternative explanations. A parser may appear successful on common y ions while dropping precisely the syntax that motivated a shared standard. Publish the fixture and expected parsed components.
Display layers should never rewrite the scientific string silently. A plot can render subscripts, superscripts and coloured ion series for people, while the underlying mzPAF remains available for machines. If a viewer shortens an annotation, it should offer the complete value and state whether confidence or delta has been hidden for space.
Library exchange benefits from versioned dependencies. Archive the mzPAF document, PSI-MS and PSI-MOD releases, ProForma version, mzSpecLib version and any parser configuration. A later tool can first reproduce the original interpretation, then perform a clearly labelled migration to newer terminology or grammar.
Quality review can sample peaks across intensity, mass range and annotation complexity. Recalculate theoretical m/z independently, inspect unexplained high-intensity peaks and compare alternative candidates. This prevents a perfect syntax score from masking a scientifically weak annotation set.
A final reader summary should say what fraction of peaks was annotated, how confidence was produced, which ion types were allowed and what remained unknown. Those visible limits make the standard approachable without turning a dense forest of labels into false certainty.
Mass tolerance should be reported with calibration context. Parts per million is relative to theoretical m/z, while an absolute m/z delta behaves differently across the mass range. If a workflow converts between the two, retain the unrounded observation and formula. Reviewers can then tell whether a close annotation reflects instrument performance, generous tolerance or a transcription error.
Annotation review should also retain peaks that were deliberately left without a label. The unannotated set may reveal weak fragmentation, missing ion classes or overly restrictive software settings. Report total, annotated and unexplained peak counts under the same intensity threshold so coverage comparisons remain meaningful across spectra and tools.
| Stage | Question | Evidence | Responsible output |
|---|---|---|---|
| Observe | Which numerical peak is being explained? | Source spectrum, m/z, intensity and analyte context | A traceable observation |
| Annotate | Which ion or compound may produce it? | Ion type, losses, isotope, adduct and charge | A structured candidate |
| Compare | How closely does theory fit? | Observed-minus-theoretical delta and confidence | A bounded interpretation |
| Verify | Can another tool reproduce it? | Versioned grammar, parser, calculation and alternatives | A testable annotation record |
Inside this guide
1–12 · Foundations and design
- 1. Start with the peak question
- 2. Use final version 1.0.1
- 3. Preserve the exact string
- 4. Identify the analyte
- 5. Read peptide ion series
- 6. Read unknown ions
- 7. Read immonium ions
- 8. Read internal fragments
- 9. Read precursor ions
- 10. Read reference ions
- 11. Read named compounds and formulas
- 12. Read neutral losses and gains
13–24 · Models and estimation
25–36 · Diagnostics and interpretation
- 25. Separate annotation from identification
- 26. Separate identity from function
- 27. Preserve privacy and licences
- 28. Connect to Primary Science
- 29. Connect to Secondary Science
- 30. Connect to mathematics
- 31. Connect to computing
- 32. Connect to pathways
- 33. Did you know?
- 34. Write a reader-ready methods note
- 35. Build a validation ladder
- 36. Finish with a reproducible bundle
Section 1 of 36
1. Start with the peak question
Name the spectrum, analyte candidate and reason the peak needs interpretation. A label without source context cannot be audited.
Working checkpoint — mzPAF: Keep the spectrum identifier and peak coordinates beside the string. Keep source spectrum, analyte, exact string, parsed ions, deltas, confidence and alternatives together.
For a classroom model, annotate fictional peaks with clear rules.
Section 2 of 36
2. Use final version 1.0.1
The official page says version 1.0.1 was formally ratified and released on 5 May 2026.
Working checkpoint — fragment ion: Record specification version and retrieval date. Read every peak label beside observed m/z, theoretical calculation, charge and instrument context.
For future study, connect chemistry to code while checking pathways separately.
Section 3 of 36
3. Preserve the exact string
mzPAF is case-sensitive and punctuation carries grammar. Reformatting by hand can change meaning.
Working checkpoint — peak annotation: Archive original bytes and a parsed representation. Preserve unknown and competing annotations; a labelled spectrum is not the full identification evidence.
For writing, cite mzPAF version, spectrum, analyte, software, validation and limits.
Section 4 of 36
4. Identify the analyte
Fragment notation depends on the correct peptide or other analyte, including sequence and modifications.
Working checkpoint — mass delta: Resolve every analyte reference. Separate grammar validity from mass accuracy, peptide confidence and biological meaning.
For students, ask which calculation supports a fragment label.
Section 5 of 36
5. Read peptide ion series
a, b, c, x, y and z ions describe defined fragment series with numbered positions.
Working checkpoint — annotation confidence: Check series direction and index against the sequence. Treat punctuation, sign, unit and analyte references as scientific inputs: one character can change the ion.
For parents, ask whether a confident label still exposes alternatives.
Section 6 of 36
6. Read unknown ions
A question-mark ion can preserve that a peak remains unexplained instead of forcing a confident assignment.
Working checkpoint — ion series: Keep unknown peaks visible. Keep source spectrum, analyte, exact string, parsed ions, deltas, confidence and alternatives together.
For a classroom model, annotate fictional peaks with clear rules.
Section 7 of 36
7. Read immonium ions
Immonium-ion notation represents residue-related fragments and should agree with analyte chemistry.
Working checkpoint — mzPAF: Verify residue compatibility. Read every peak label beside observed m/z, theoretical calculation, charge and instrument context.
For future study, connect chemistry to code while checking pathways separately.
Section 8 of 36
8. Read internal fragments
Internal-fragment notation identifies a peptide segment that is neither simple N- nor C-terminal series.
Working checkpoint — fragment ion: Check both boundaries. Preserve unknown and competing annotations; a labelled spectrum is not the full identification evidence.
For writing, cite mzPAF version, spectrum, analyte, software, validation and limits.
Section 9 of 36
9. Read precursor ions
Precursor notation represents intact analyte-related ions and can include charge and other attributes.
Working checkpoint — peak annotation: Separate precursor evidence from fragment evidence. Separate grammar validity from mass accuracy, peptide confidence and biological meaning.
For students, ask which calculation supports a fragment label.
Section 10 of 36
10. Read reference ions
Named reference-ion notation can capture reporter or calibrant-style peaks under governed identifiers.
Working checkpoint — mass delta: Pin the referenced term and release. Treat punctuation, sign, unit and analyte references as scientific inputs: one character can change the ion.
For parents, ask whether a confident label still exposes alternatives.
Section 11 of 36
11. Read named compounds and formulas
The grammar can represent named compounds, chemical formulas and SMILES entities where appropriate.
Working checkpoint — annotation confidence: Do not treat equal formula as unique structure. Keep source spectrum, analyte, exact string, parsed ions, deltas, confidence and alternatives together.
For a classroom model, annotate fictional peaks with clear rules.
Section 12 of 36
12. Read neutral losses and gains
Added or lost compositions change theoretical ion mass and need chemically plausible notation.
Working checkpoint — ion series: Recalculate the resulting mass. Read every peak label beside observed m/z, theoretical calculation, charge and instrument context.
For future study, connect chemistry to code while checking pathways separately.
Section 13 of 36
13. Read isotopes
Isotope notation changes the expected peak position and can support envelope interpretation.
Working checkpoint — mzPAF: Check isotope index and resolution. Preserve unknown and competing annotations; a labelled spectrum is not the full identification evidence.
For writing, cite mzPAF version, spectrum, analyte, software, validation and limits.
Section 14 of 36
14. Read adducts
Adduct composition changes mass and charge relationships.
Working checkpoint — fragment ion: Validate the stated adduct against ionisation conditions. Separate grammar validity from mass accuracy, peptide confidence and biological meaning.
For students, ask which calculation supports a fragment label.
Section 15 of 36
15. Read charge
Charge affects m/z and must be applied consistently to fragment mass calculations.
Working checkpoint — peak annotation: Reject impossible or missing charge assumptions. Treat punctuation, sign, unit and analyte references as scientific inputs: one character can change the ion.
For parents, ask whether a confident label still exposes alternatives.
Section 16 of 36
16. Read mass deltas
The slash field gives observed minus theoretical difference, optionally in parts per million.
Working checkpoint — mass delta: Verify sign, unit and calculation. Keep source spectrum, analyte, exact string, parsed ions, deltas, confidence and alternatives together.
For a classroom model, annotate fictional peaks with clear rules.
Section 17 of 36
17. Read confidence
An asterisk can add a confidence value to an annotation, but calibration comes from the producing method.
Working checkpoint — annotation confidence: Name score transformation and domain. Read every peak label beside observed m/z, theoretical calculation, charge and instrument context.
For future study, connect chemistry to code while checking pathways separately.
Section 18 of 36
18. Preserve alternatives
Comma-separated annotations let one peak retain several possible explanations.
Working checkpoint — ion series: Do not report only the most convenient candidate. Preserve unknown and competing annotations; a labelled spectrum is not the full identification evidence.
For writing, cite mzPAF version, spectrum, analyte, software, validation and limits.
Section 19 of 36
19. Handle multiple analytes
Analyte references distinguish contributors when one spectrum contains more than one candidate molecule.
Working checkpoint — mzPAF: Resolve reference numbers before interpreting ions. Separate grammar validity from mass accuracy, peptide confidence and biological meaning.
For students, ask which calculation supports a fragment label.
Section 20 of 36
20. Embed ProForma carefully
The grammar can carry a ProForma-described sequence context for complex cases.
Working checkpoint — fragment ion: Validate both syntaxes and modification positions. Treat punctuation, sign, unit and analyte references as scientific inputs: one character can change the ion.
For parents, ask whether a confident label still exposes alternatives.
Section 21 of 36
21. Pair with mzSpecLib
Spectral libraries can use mzPAF annotations while retaining their own library and analyte records.
Working checkpoint — peak annotation: Keep format roles distinct. Keep source spectrum, analyte, exact string, parsed ions, deltas, confidence and alternatives together.
For a classroom model, annotate fictional peaks with clear rules.
Section 22 of 36
22. Validate syntax
A standards-aware parser should reject malformed order, punctuation, charge and delta fields.
Working checkpoint — mass delta: Keep parser version and error log. Read every peak label beside observed m/z, theoretical calculation, charge and instrument context.
For future study, connect chemistry to code while checking pathways separately.
Section 23 of 36
23. Validate round trips
Parsing and serialising should preserve the annotation’s meaning and alternatives.
Working checkpoint — annotation confidence: Compare components, not only display text. Preserve unknown and competing annotations; a labelled spectrum is not the full identification evidence.
For writing, cite mzPAF version, spectrum, analyte, software, validation and limits.
Section 24 of 36
24. Validate mass arithmetic
The stated ion and delta should reproduce the observed peak within declared precision.
Working checkpoint — ion series: Test representative annotations independently. Separate grammar validity from mass accuracy, peptide confidence and biological meaning.
For students, ask which calculation supports a fragment label.
Section 25 of 36
25. Separate annotation from identification
A plausible fragment label contributes evidence but does not by itself establish the peptide-spectrum match.
Working checkpoint — mzPAF: Review full spectrum, alternatives and thresholds. Treat punctuation, sign, unit and analyte references as scientific inputs: one character can change the ion.
For parents, ask whether a confident label still exposes alternatives.
Section 26 of 36
26. Separate identity from function
A supported peptide or modification does not prove biological mechanism or clinical relevance.
Working checkpoint — fragment ion: Require independent functional evidence. Keep source spectrum, analyte, exact string, parsed ions, deltas, confidence and alternatives together.
For a classroom model, annotate fictional peaks with clear rules.
Section 27 of 36
27. Preserve privacy and licences
Source spectra and library records can carry governed metadata or licensing conditions.
Working checkpoint — peak annotation: Check sharing rights before distribution. Read every peak label beside observed m/z, theoretical calculation, charge and instrument context.
For future study, connect chemistry to code while checking pathways separately.
Section 28 of 36
28. Connect to Primary Science
A fictional fragment-ion card helps younger learners see that an observation, a label and an explanation are different layers.
Working checkpoint — mass delta: Define every symbol and use no personal data. Preserve unknown and competing annotations; a labelled spectrum is not the full identification evidence.
For writing, cite mzPAF version, spectrum, analyte, software, validation and limits.
Section 29 of 36
29. Connect to Secondary Science
mzPAF supports lessons about molecules, evidence, models, controls and uncertainty.
Working checkpoint — annotation confidence: Trace one conclusion back to the smallest supporting record. Separate grammar validity from mass accuracy, peptide confidence and biological meaning.
For students, ask which calculation supports a fragment label.
Section 30 of 36
30. Connect to mathematics
Coordinates, masses, charges, intervals, scores and probabilities reward exact definitions and compatible units.
Working checkpoint — ion series: Recalculate one small example by hand. Treat punctuation, sign, unit and analyte references as scientific inputs: one character can change the ion.
For parents, ask whether a confident label still exposes alternatives.
Section 31 of 36
31. Connect to computing
Formal grammars, parsers and mass calculations show how compact strings can remain interoperable.
Working checkpoint — mzPAF: Break one field or reference, run a validator and repair it transparently. Keep source spectrum, analyte, exact string, parsed ions, deltas, confidence and alternatives together.
For a classroom model, annotate fictional peaks with clear rules.
Section 32 of 36
32. Connect to pathways
Peak annotation joins chemistry, instrumentation, mathematics and software and can illuminate STEM education and career pathways.
Working checkpoint — fragment ion: Verify current official education and qualification routes separately. Read every peak label beside observed m/z, theoretical calculation, charge and instrument context.
For future study, connect chemistry to code while checking pathways separately.
Section 33 of 36
33. Did you know?
mzPAF 1.0.1 was released as a ratified patch after implementation exposed minor issues in 1.0.0.
Working checkpoint — peak annotation: Explain the fact in plain language, then name the evidence boundary. Preserve unknown and competing annotations; a labelled spectrum is not the full identification evidence.
For writing, cite mzPAF version, spectrum, analyte, software, validation and limits.
Section 34 of 36
34. Write a reader-ready methods note
State format status, version, inputs, reference resources, software, validation and the narrow claim supported.
Working checkpoint — mass delta: Keep the note beside the machine-readable record. Separate grammar validity from mass accuracy, peptide confidence and biological meaning.
For students, ask which calculation supports a fragment label.
Section 35 of 36
35. Build a validation ladder
Check bytes, structure, identifiers, references, controlled meaning, scientific plausibility and a known fixture in sequence.
Working checkpoint — annotation confidence: Stop at the earliest unresolved layer. Treat punctuation, sign, unit and analyte references as scientific inputs: one character can change the ion.
For parents, ask whether a confident label still exposes alternatives.
Section 36 of 36
36. Finish with a reproducible bundle
Deliver source files or stable identifiers, format documents, reference releases, commands, validator output, hashes and limitations.
Working checkpoint — ion series: Make every published claim traceable. Keep source spectrum, analyte, exact string, parsed ions, deltas, confidence and alternatives together.
For a classroom model, annotate fictional peaks with clear rules.
Contents · Previous section · Continue to the Science Learning Hub