eduKateSG · Why Science?
Name protein modifications with stable, computable meanings—while preserving residue chemistry, evidence, provenance, releases and uncertainty
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. PSI-MOD is the HUPO Proteomics Standards Initiative Protein Modifications Ontology for modified and unmodified amino-acid residues. Its official repository identifies the OBO file as the master source and supplies a derived OWL representation; the repository is actively maintained and includes annotation rules dated 3 April 2025. PSI-MOD terms provide stable MOD accessions, names, definitions and relationships that software can use across proteomics formats. An ontology term names a modification concept; it does not prove that a particular residue is modified in a sample, localise the site, establish occupancy or explain biological function. 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: ProForma and proteoform sequence notation; mzIdentML and proteomics identification results; mass spectrometry, ionisation and mass-to-charge evidence; Science Learning Hub; Education Hub; STEM Education; Careers by Subject Capability.
Primary and official sources checked on 12 October 2026: HUPO-PSI PSI-MOD official source repository, OBO and OWL deliverables, checked 12 October 2026; OBO Foundry PSI-MOD ontology record and persistent release links, checked 12 October 2026; EMBL-EBI Ontology Lookup Service PSI-MOD index, 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, vocabularies, tools and recommendations can change, so preserve dated documentation, exact source data and software versions.
A deeper reading route
Protein modifications create a naming problem because one chemical event can have synonyms, historical labels, residue-specific forms and broader parent categories. PSI-MOD gives those meanings stable identifiers and relationships. A MOD accession is more reliable for computation than matching a display name, especially when labels change or several resources use similar words differently.
The ontology covers modified and unmodified amino-acid residues. Terms can encode the source residue, chemical difference and classification. Parent-child relationships let a broad query retrieve narrower concepts, but hierarchy is not experimental evidence. Finding a term beneath phosphorylated residue does not show that one sample contains it.
Definitions matter as much as labels. A preferred name may be short for readability, while the definition and formal properties state which residue or chemical transformation is intended. Reports should resolve the accession in a dated release rather than copying a label from an undated web page.
The official repository says the OBO file is the master source and OWL is derived from it. OBO and OWL support different tools while representing the same ontology content. A conversion pipeline should preserve accessions, definitions, synonyms, relationships and obsolescence status and should record the tool that generated a derivative.
Obsolete terms are not ordinary current terms. Ontologies evolve as chemistry is corrected, concepts are merged or better identifiers appear. Software should retain the original accession for provenance, follow replacement guidance where supplied and avoid silently rewriting historical results.
Mass differences help connect a modification to spectra, but equal or near-equal masses can correspond to different chemistry. A controlled term narrows meaning only when experimental evidence supports that identity. An unknown mass shift should remain unknown rather than being forced to the most familiar term.
Residue specificity is essential. A modification may be meaningful on particular amino acids or termini. A parser should check whether the annotated position and residue are compatible with the term, while recognising that biological and artefactual chemistry can require nuanced evidence.
PSI-MOD can appear in ProForma strings, PEFF database annotations, mzIdentML results and other standards. The same accession improves interoperability, yet each surrounding format adds its own context: sequence position, database possibility, identification evidence or result hierarchy.
Synonyms support search and reading but should not be used as primary keys. One synonym may be shared casually across concepts or vary in punctuation. Store the accession, namespace and ontology release; display the preferred name for people.
Cross-references connect terms to external chemistry or modification resources. A cross-reference is a mapping claim with its own scope, not proof of perfect one-to-one equivalence. Review exact definitions before merging databases or converting accessions.
Annotation rules help curators apply consistent names, definitions and formal properties. Their dated presence is useful evidence that ontology maintenance is a process. Users should not invent production accessions locally; requests and proposed changes belong in the governed issue workflow.
Validation has several layers: syntax of the accession, existence in the chosen release, current versus obsolete status, compatible residue and position, agreement with mass or formula, and support from spectra or another experiment. Passing the ontology lookup is only the second layer.
For students, PSI-MOD is like a carefully maintained scientific dictionary in which each meaning has a permanent catalogue number and a place among related meanings. The catalogue reduces confusion, but it cannot observe the molecule for us.
A classroom activity can give several groups different synonyms for the same fictional modification. Students first fail to merge the labels, then succeed with stable IDs and definitions. A deliberately obsolete term shows why release dates and replacement notes matter.
A reproducible annotation bundle includes the original sequence, modification accession, ontology release or file hash, localisation evidence, spectral identifier, score, software and validator output. This lets later readers separate vocabulary maintenance from a new biological conclusion.
The happy value of PSI-MOD is clearer scientific conversation. Stable accessions let databases, search engines and papers refer to the same modification concept while keeping definitions inspectable. Shared vocabulary creates the conditions for evidence to travel without pretending vocabulary is evidence itself.
Ontology-aware software should resolve accessions under a pinned release and retain the original identifier even when displaying a friendlier label. If a term becomes obsolete, migration should produce a mapping receipt with old term, new term, reason and affected records. Silent replacement erases the history needed to reproduce earlier analyses.
Mass-based candidate generation needs restraint. Several modifications may share a nominal or near-identical mass, and laboratory artefacts can mimic biological changes. An annotation pipeline should keep candidates, residue compatibility and localisation evidence separate until spectra or standards justify a more precise term.
Cross-resource mapping is useful but rarely trivial. Unimod, PSI-MOD, RESID and specialised ontologies can organise concepts differently. Map exact accessions through curated cross-references and definitions, not display-name similarity. When equivalence is partial, preserve both terms and state the scope.
A reader-ready annotation shows the MOD accession, preferred name, plain-language definition, sequence position, ontology release and experimental support together. This pairing serves both machines and people: the identifier stabilises meaning, while the evidence explains why the term belongs in this particular result.
Ontology hierarchy enables useful questions such as retrieving a broad class of modified residues, but query results depend on reasoning rules and the selected release. Record whether software followed asserted parents only or inferred additional relationships. Two tools can otherwise return different term sets from the same starting accession.
Local caches improve performance but create version risk. A pipeline should log the ontology file hash loaded at run time and fail clearly if an accession is absent. Quietly falling back to a label or the latest online copy can make identical input files produce different annotations months later.
Curators sometimes refine definitions without changing the underlying accession. That is why release information remains relevant even for stable IDs. Preserve the text or ontology artifact used when a scientific claim was made, then distinguish later wording improvements from changes in experimental evidence.
Quality review benefits from two readers: a vocabulary-aware check for identifiers, relationships and status, and a domain check for chemistry and spectra. Neither replaces the other. The combination catches both data-engineering errors and scientifically implausible annotations before they become durable results.
Reports should also distinguish the ontology concept from the author’s plain-language explanation. The explanation can help students and collaborators, but it must not broaden or narrow the formal definition. Keep both views together, test that they agree, and let the accession remain the durable computational key.
A final review should resolve several representative accessions in an independent ontology browser and compare definitions, status and parents with the local file. This simple cross-check can expose a stale cache, truncated download or conversion error before publication.
| Stage | Question | Evidence | Responsible output |
|---|---|---|---|
| Name | Which modification concept is intended? | MOD accession, preferred label and definition | A stable reference |
| Relate | How does it fit the ontology? | Parents, synonyms, residue context and cross-references | Computable meaning |
| Apply | Where is it asserted? | Sequence position, file format and experimental record | A contextual annotation |
| Test | What supports the assertion? | Spectra, mass, localisation, release and validation | A bounded claim |
Inside this guide
1–12 · Foundations and design
- 1. Start with the naming problem
- 2. Record the ontology release
- 3. Use the MOD namespace
- 4. Read the preferred name
- 5. Read the definition
- 6. Read synonyms
- 7. Read parent relationships
- 8. Read residue context
- 9. Read mass information
- 10. Read formula context
- 11. Read cross-references
- 12. Read obsolescence
13–24 · Models and estimation
- 13. Use OBO as the master
- 14. Use OWL deliberately
- 15. Follow annotation rules
- 16. Request changes transparently
- 17. Apply terms in ProForma
- 18. Apply terms in identification results
- 19. Apply terms in PEFF-like databases
- 20. Validate accession syntax
- 21. Validate term existence
- 22. Validate current status
- 23. Validate residue and position
- 24. Validate mass and chemistry
25–36 · Diagnostics and interpretation
- 25. Protect sensitive findings
- 26. Separate terminology from detection
- 27. Separate modification from function
- 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 annotation note
- 35. Build a validation ladder
- 36. Finish with a reproducible bundle
Section 1 of 36
1. Start with the naming problem
Identify the residue change, evidence level and context that need a term.
Working checkpoint — PSI-MOD: Do not begin with a loose synonym. Keep accession, definition, ontology release, sequence site, experimental evidence and validation together.
For a classroom model, reconcile synonyms through fictional stable identifiers.
Section 2 of 36
2. Record the ontology release
Vocabulary content changes over time.
Working checkpoint — protein modification ontology: Pin release, retrieval date or file hash. Read every label beside its namespace, current status, residue context and source spectrum.
For future study, connect chemistry to ontologies and software while checking official pathways separately.
Section 3 of 36
3. Use the MOD namespace
Stable accessions identify concepts more safely than labels.
Working checkpoint — controlled vocabulary: Store namespace and accession. Preserve obsolete and ambiguous history; a stable term is not proof of a measured modification.
For scientific writing, cite accession, release, sequence context, evidence and validator.
Section 4 of 36
4. Read the preferred name
The current label supports people and interfaces.
Working checkpoint — post-translational modification: Do not use it as the only key. Separate controlled meaning from detection confidence, occupancy, function and clinical meaning.
For students, ask what the accession means and which evidence supports using it.
Section 5 of 36
5. Read the definition
Definitions state the intended modified-residue concept.
Working checkpoint — modified residue: Compare it with the evidence. Treat accessions, positions and mass differences as scientific inputs: one silent term substitution can change the chemistry.
For parents, ask whether shared vocabulary keeps experimental uncertainty visible.
Section 6 of 36
6. Read synonyms
Synonyms improve discovery but can be ambiguous.
Working checkpoint — ontology accession: Resolve back to one accession. Keep accession, definition, ontology release, sequence site, experimental evidence and validation together.
For a classroom model, reconcile synonyms through fictional stable identifiers.
Section 7 of 36
7. Read parent relationships
Broader and narrower terms support queries and classification.
Working checkpoint — PSI-MOD: Do not mistake hierarchy for observation. Read every label beside its namespace, current status, residue context and source spectrum.
For future study, connect chemistry to ontologies and software while checking official pathways separately.
Section 8 of 36
8. Read residue context
Many modifications are specific to residues or termini.
Working checkpoint — protein modification ontology: Check position compatibility. Preserve obsolete and ambiguous history; a stable term is not proof of a measured modification.
For scientific writing, cite accession, release, sequence context, evidence and validator.
Section 9 of 36
9. Read mass information
Mass differences aid spectrum interpretation.
Working checkpoint — controlled vocabulary: Separate equal mass from equal chemistry. Separate controlled meaning from detection confidence, occupancy, function and clinical meaning.
For students, ask what the accession means and which evidence supports using it.
Section 10 of 36
10. Read formula context
Composition can narrow chemistry without proving structure.
Working checkpoint — post-translational modification: Preserve the annotation level. Treat accessions, positions and mass differences as scientific inputs: one silent term substitution can change the chemistry.
For parents, ask whether shared vocabulary keeps experimental uncertainty visible.
Section 11 of 36
11. Read cross-references
External mappings can connect resources with different scopes.
Working checkpoint — modified residue: Check exact equivalence. Keep accession, definition, ontology release, sequence site, experimental evidence and validation together.
For a classroom model, reconcile synonyms through fictional stable identifiers.
Section 12 of 36
12. Read obsolescence
Deprecated terms may point to replacements or alternatives.
Working checkpoint — ontology accession: Keep the original for provenance. Read every label beside its namespace, current status, residue context and source spectrum.
For future study, connect chemistry to ontologies and software while checking official pathways separately.
Section 13 of 36
13. Use OBO as the master
The official repository identifies the OBO file as the source deliverable.
Working checkpoint — PSI-MOD: Archive the exact bytes. Preserve obsolete and ambiguous history; a stable term is not proof of a measured modification.
For scientific writing, cite accession, release, sequence context, evidence and validator.
Section 14 of 36
14. Use OWL deliberately
OWL is a derived representation for ontology tooling.
Working checkpoint — protein modification ontology: Record conversion and verify content. Separate controlled meaning from detection confidence, occupancy, function and clinical meaning.
For students, ask what the accession means and which evidence supports using it.
Section 15 of 36
15. Follow annotation rules
Governed curation supports consistent terms and definitions.
Working checkpoint — controlled vocabulary: Use the dated rules. Treat accessions, positions and mass differences as scientific inputs: one silent term substitution can change the chemistry.
For parents, ask whether shared vocabulary keeps experimental uncertainty visible.
Section 16 of 36
16. Request changes transparently
New concepts should enter through the maintained issue and review process.
Working checkpoint — post-translational modification: Do not mint unofficial MOD IDs. Keep accession, definition, ontology release, sequence site, experimental evidence and validation together.
For a classroom model, reconcile synonyms through fictional stable identifiers.
Section 17 of 36
17. Apply terms in ProForma
A MOD accession can identify a modification inside sequence notation.
Working checkpoint — modified residue: Keep sequence and localisation. Read every label beside its namespace, current status, residue context and source spectrum.
For future study, connect chemistry to ontologies and software while checking official pathways separately.
Section 18 of 36
18. Apply terms in identification results
mzIdentML can carry modification terms beside spectral evidence.
Working checkpoint — ontology accession: Preserve score and spectrum. Preserve obsolete and ambiguous history; a stable term is not proof of a measured modification.
For scientific writing, cite accession, release, sequence context, evidence and validator.
Section 19 of 36
19. Apply terms in PEFF-like databases
Database annotations describe searchable possibilities.
Working checkpoint — PSI-MOD: Do not promote them to observations. Separate controlled meaning from detection confidence, occupancy, function and clinical meaning.
For students, ask what the accession means and which evidence supports using it.
Section 20 of 36
20. Validate accession syntax
Namespace and numeric identifier must be well formed.
Working checkpoint — protein modification ontology: Reject informal lookalikes. Treat accessions, positions and mass differences as scientific inputs: one silent term substitution can change the chemistry.
For parents, ask whether shared vocabulary keeps experimental uncertainty visible.
Section 21 of 36
21. Validate term existence
The accession must resolve in the pinned release.
Working checkpoint — controlled vocabulary: Handle missing IDs explicitly. Keep accession, definition, ontology release, sequence site, experimental evidence and validation together.
For a classroom model, reconcile synonyms through fictional stable identifiers.
Section 22 of 36
22. Validate current status
Obsolete terms require review and documented migration.
Working checkpoint — post-translational modification: Never replace silently. Read every label beside its namespace, current status, residue context and source spectrum.
For future study, connect chemistry to ontologies and software while checking official pathways separately.
Section 23 of 36
23. Validate residue and position
The sequence site should agree with term meaning.
Working checkpoint — modified residue: Stop on impossible sites. Preserve obsolete and ambiguous history; a stable term is not proof of a measured modification.
For scientific writing, cite accession, release, sequence context, evidence and validator.
Section 24 of 36
24. Validate mass and chemistry
Observed mass, formula and term should be mutually plausible.
Working checkpoint — ontology accession: Use independent calculations. Separate controlled meaning from detection confidence, occupancy, function and clinical meaning.
For students, ask what the accession means and which evidence supports using it.
Section 25 of 36
25. Protect sensitive findings
Rare sample-specific modifications may be governed information.
Working checkpoint — PSI-MOD: Apply access controls. Treat accessions, positions and mass differences as scientific inputs: one silent term substitution can change the chemistry.
For parents, ask whether shared vocabulary keeps experimental uncertainty visible.
Section 26 of 36
26. Separate terminology from detection
A valid term does not establish that a modification was measured.
Working checkpoint — protein modification ontology: Link experimental evidence. Keep accession, definition, ontology release, sequence site, experimental evidence and validation together.
For a classroom model, reconcile synonyms through fictional stable identifiers.
Section 27 of 36
27. Separate modification from function
A detected chemical change does not prove mechanism or outcome.
Working checkpoint — controlled vocabulary: Use functional tests separately. Read every label beside its namespace, current status, residue context and source spectrum.
For future study, connect chemistry to ontologies and software while checking official pathways separately.
Section 28 of 36
28. Connect to Primary Science
Stable labels show why shared names help groups compare observations.
Working checkpoint — post-translational modification: Use fictional terms. Preserve obsolete and ambiguous history; a stable term is not proof of a measured modification.
For scientific writing, cite accession, release, sequence context, evidence and validator.
Section 29 of 36
29. Connect to Secondary Science
Modification vocabulary supports lessons about molecules, evidence and classification.
Working checkpoint — modified residue: Compare label with definition. Separate controlled meaning from detection confidence, occupancy, function and clinical meaning.
For students, ask what the accession means and which evidence supports using it.
Section 30 of 36
30. Connect to mathematics
Mass differences, positions and hierarchies build symbolic and relational reasoning.
Working checkpoint — ontology accession: Check one residue shift. Treat accessions, positions and mass differences as scientific inputs: one silent term substitution can change the chemistry.
For parents, ask whether shared vocabulary keeps experimental uncertainty visible.
Section 31 of 36
31. Connect to computing
Identifiers, graphs, OBO, OWL and validators show ontology engineering.
Working checkpoint — PSI-MOD: Resolve one accession. Keep accession, definition, ontology release, sequence site, experimental evidence and validation together.
For a classroom model, reconcile synonyms through fictional stable identifiers.
Section 32 of 36
32. Connect to pathways
Scientific vocabularies join chemistry, biology, information science and software and can illuminate STEM education and career pathways.
Working checkpoint — protein modification ontology: Verify current routes separately. Read every label beside its namespace, current status, residue context and source spectrum.
For future study, connect chemistry to ontologies and software while checking official pathways separately.
Section 33 of 36
33. Did you know?
PSI-MOD describes unmodified as well as modified amino-acid residues.
Working checkpoint — controlled vocabulary: Read the term definition, not only its name. Preserve obsolete and ambiguous history; a stable term is not proof of a measured modification.
For scientific writing, cite accession, release, sequence context, evidence and validator.
Section 34 of 36
34. Write a reader-ready annotation note
State accession, label, definition, release, sequence site, evidence and limits.
Working checkpoint — post-translational modification: Place it beside the result. Separate controlled meaning from detection confidence, occupancy, function and clinical meaning.
For students, ask what the accession means and which evidence supports using it.
Section 35 of 36
35. Build a validation ladder
Check syntax, existence, status, residue, mass, format context and experimental evidence.
Working checkpoint — modified residue: Stop at the first mismatch. Treat accessions, positions and mass differences as scientific inputs: one silent term substitution can change the chemistry.
For parents, ask whether shared vocabulary keeps experimental uncertainty visible.
Section 36 of 36
36. Finish with a reproducible bundle
Deliver strings, accessions, ontology bytes, spectra, scores, software, validator logs and hashes.
Working checkpoint — ontology accession: Make every term traceable. Keep accession, definition, ontology release, sequence site, experimental evidence and validation together.
For a classroom model, reconcile synonyms through fictional stable identifiers.
Contents · Previous section · Continue to the Science Learning Hub