eduKateSG · Why Science?
The same quantity can be measured in different ways—and the difference matters
Choose the closest question, or read the guide from the beginning. Each chapter keeps its explanation, example and next step visible.
Two students measure the same paper shape. One follows the edge with a ruler; the other counts squares in a photograph. Their answers may both look sensible, yet they have taken different routes from object to number. The Measurement Method Ontology, or MMO, gives those routes a shared naming layer in clinical and phenotype research. Why learn Science? Because understanding the route helps us decide what an answer can—and cannot—show.
The OBO Foundry describes MMO as representing methods for qualitative and quantitative clinical and phenotype measurements, including work with model organisms. The official repository identifies RGD as the maintainer. This article owns measuring-process identity and review. It does not replace the broader eduKate guides on experiments or assays, and it is not a clinical protocol or a guide to operating specialist equipment.
Primary Science and PSLE Science learners can begin with safe objects and fair measurement. Secondary Science readers can extend the discussion to uncertainty and controls. The advanced route concerns method mapping and dataset reuse. All numerical cases are fictional teaching examples; suggested record designs are editorial recommendations, not official MMO requirements or promises of examination results.
Follow the connected evidence: Ontology for Biomedical Investigations; BioAssay Ontology; Evidence and Conclusion Ontology. For education and school-choice guidance, use the Education Hub; for possible work directions, continue to Careers by Subject Capability. These routes are separate from the specialist topic here.
| Layer | Question | Record | Boundary |
|---|---|---|---|
| Measurement type | What quantity is the target? | Quantity definition and unit | Not a method |
| Method class | Which kind of measuring process? | MMO identifier and definition | Not the complete protocol |
| Implementation | What was actually done? | Instrument, settings, preparation and operator | Not guaranteed performance |
| Performance | How well did it work here? | Reference checks, repeats and uncertainty | Not supplied by the vocabulary |
Inside this guide
Chapters 1–10 · Meaning and evidence
- 1. Did You Know? A method name is not a performance certificate
- 2. Distinguish the target from the route
- 3. Find the method through its definition
- 4. Method class and protocol are complementary
- 5. Describe the principle without confusing it with a device
- 6. Preparation can change what is measured
- 7. Calibration asks about a reference relationship
- 8. Repeated readings test one kind of consistency
- 9. Operators are part of the process
- 10. Automated does not mean assumption-free
Chapters 11–20 · Comparison and learning
- 11. Shared methods do not guarantee shared conditions
- 12. A method comparison needs paired questions
- 13. Worked case: a consistent offset
- 14. Worked case: a scale-dependent difference
- 15. Worked case: agreement only under easy conditions
- 16. Keep a release and mapping history
- 17. Build an accessible Science learning activity
- 18. Use small-group discussion to reveal hidden steps
- 19. Connect methods literacy to future capability
- 20. Write a method note someone else can use
CHAPTER 1 OF 20 · Understand the method
1. Did You Know? A method name is not a performance certificate
MMO supplies vocabulary for describing measurement methods. It does not certify an instrument, calibrate equipment or prove that a method worked well in one study. The useful distinction is between naming a process and assessing its performance. A well-labelled measurement can still be poor evidence if the implementation was unsuitable or important checks were missing. Source: the OBO Foundry MMO overview.
Think of a recipe title. It tells you the family of procedure, but it does not reveal the ingredient quantities, oven setting or what happened on the day. A method class works similarly: it helps people recognise the process without replacing the detailed record.
Start a review with two questions rather than one: “Which method was used?” and “What evidence shows that it was suitable here?” Keeping them separate makes the review more constructive. You can accept the vocabulary mapping while asking for better performance evidence, or reject the mapping while acknowledging that the underlying experiment may still be valuable.
CHAPTER 2 OF 20 · Understand the method
2. Distinguish the target from the route
The target quantity and the measuring method have different jobs. A quantity describes what you want to know; a method describes the process used to estimate or classify it. One target can have several methods, and one method family can be applied to several targets. A database should not squeeze those dimensions into one ambiguous label.
In a fictional classroom exercise, length is the target. A ruler reading and an image-based estimate are two routes. Both might use centimetres, but sharing a unit does not make the methods equivalent. One route depends on endpoint placement and scale reading; the other also depends on image scale and analysis choices.
Recommended record design uses separate fields for measurement type, method class and protocol reference. This lets readers compare quantities without hiding process differences. It also supports better questions: are the results inconsistent because the objects differ, because the methods differ, or because one method was implemented differently? Naming each layer is the first step towards finding out.
CHAPTER 3 OF 20 · Understand the method
3. Find the method through its definition
Scientific method labels often become shorthand. Local laboratories may use the same name for different implementations, or different names for closely related procedures. Map the procedure to MMO by comparing its actual description with the official term definition. Do not select a class merely because the words look familiar in a search result.
A recommended review note records the source method description, selected identifier, ontology version, mapping scope and unresolved details. Preserve the original wording. If the source only says “imaging”, do not invent the acquisition technology, preparation or analytical procedure. A broad mapping may be the most truthful result.
For students, ask partners to describe how they measured an object without using the instrument's brand name. The explanation should reveal the principle and steps. Then compare their descriptions. This activity shows why methods are more than labels: the procedure's meaning has to survive when a new reader, database or device uses different vocabulary.
CHAPTER 4 OF 20 · Understand the method
4. Method class and protocol are complementary
A controlled vocabulary makes recurring processes searchable. A protocol explains the local implementation in enough detail for review and, where appropriate, repetition. Neither should replace the other. A method-class identifier without a protocol can be too broad; a protocol without shared terminology can be difficult to discover across projects.
Recommended protocol metadata includes version, instrument configuration, sample preparation, timing, acquisition, analysis and quality-control decisions. Not every field applies to every method. The goal is to preserve the details that could change the result, not to create a long form full of irrelevant blanks.
When a protocol changes, record whether the method class remains the same and whether comparability needs reassessment. A new software threshold may leave the vocabulary label unchanged while altering the output. That is why versioning should follow the whole measurement chain. The method name helps organise the record; the protocol history explains what actually changed.
CHAPTER 5 OF 20 · Understand the method
5. Describe the principle without confusing it with a device
An instrument is one implementation of a measurement principle. Model number and software version can be important, but they do not substitute for explaining what signal was observed and how it became a result. Conversely, a method label does not identify the actual instrument used. Keep principle and device information side by side.
In a fictional example, a photograph is used to estimate area. The record should state that pixels were related to a known scale, explain the boundary selection and identify the image and software settings. Saying only “digital measurement” hides the reasoning. Saying only the camera model hides it too.
This is a helpful learning move for advanced students: draw the chain from object to signal to calculation to result. Mark each conversion. Ask where an error could enter and what check could detect it. The drawing is not a substitute for a real protocol; it is a way to understand which pieces the protocol must make visible.
CHAPTER 6 OF 20 · Inspect the measuring process
6. Preparation can change what is measured
Before a measurement begins, an object or sample may be positioned, cleaned, stored, divided or processed. Those choices can affect the quantity observed. A method comparison should therefore review preparation, not just the final instrument step. This is an editorial review recommendation, not a claim that one MMO identifier encodes every preparation detail.
Use safe classroom materials to illustrate the point. A folded paper strip and the same strip laid flat do not present the same geometry to a ruler. If the question concerns original strip length, flattening is part of the procedure. If it concerns the folded object's dimensions, flattening changes the target.
The important question is whether preparation preserves or changes the property of interest. Keep the answer in the protocol. Where specialist biological samples are involved, follow authorised procedures and qualified guidance rather than adapting a classroom analogy. The analogy teaches the reasoning boundary; it does not authorise handling or experimenting with sensitive material.
CHAPTER 7 OF 20 · Inspect the measuring process
7. Calibration asks about a reference relationship
NIST explains that calibration and reference comparisons can help identify or reduce bias. This does not mean calibration eliminates every error. Its guidance also warns that environmental effects may remain even when equipment is calibrated. A method record should therefore distinguish instrument calibration from evidence that the whole process was suitable for the intended question. Source: NIST bias and accuracy.
For a fictional exercise, compare a ruler's reading of a known reference strip with the assigned reference length. Then measure another strip using the same endpoint rule. Record both the comparison and any correction, rather than silently editing the result until it looks right.
Ask what the reference check covers and what it leaves untested. It may reveal a scale offset while saying little about how consistently different students choose an endpoint. Good measurement review is layered. One successful check should give confidence in the part it tested, not in every step that happens to share the same method name.
CHAPTER 8 OF 20 · Inspect the measuring process
8. Repeated readings test one kind of consistency
Repeated measurements under similar conditions can reveal short-term variation. They do not automatically describe variation across operators, instruments or days. NIST's variability guidance explicitly distinguishes short-term behaviour from longer-term changes in environment and handling. The method record should state what was repeated and which conditions were held stable. Source: NIST variability.
Suppose one student measures the same paper edge five times without moving the paper. Another student repeats the entire positioning and reading process five times. Both have five readings, but the second exercise includes additional procedural variation. The record should make that difference clear before comparing spreads.
A useful report describes the repetition unit, time interval and relevant changes. Do not use a vague sentence such as “the method was reproducible” when only one narrow repetition exercise was performed. Explain the conditions. Students learn more from that precise sentence because they can see how to design the next, broader consistency check.
CHAPTER 9 OF 20 · Inspect the measuring process
9. Operators are part of the process
Human judgement can enter through positioning, timing, boundary selection, classification or exclusion. That does not make the method unscientific. It makes operator decisions part of the evidence chain. Describe the rules, training and review process where judgement could materially change the result. A vocabulary term cannot make those decisions disappear.
For a fictional image exercise, three learners outline the same irregular paper shape. Compare their boundaries before calculating area. Differences near the edge may explain different results even though everyone used the same image and software. A clear boundary rule can reduce disagreement, while some uncertainty may remain.
Recommended practice is to review operator agreement on representative cases, including difficult ones. Keep disputed cases and explain how they were resolved. In teaching, rotate roles between measurer and reviewer. This makes checking a normal scientific activity rather than a personal criticism. The goal is a process another person can understand and improve.
CHAPTER 10 OF 20 · Inspect the measuring process
10. Automated does not mean assumption-free
Software can apply a rule consistently, but the rule still comes from choices. Image thresholds, filters, rounding, model settings and exclusion criteria can alter measurement output. Store software version and parameter settings beside the method reference. Preserve raw inputs where authorised and practical so an updated analysis can be compared with the original.
A fictional image pipeline classifies pixels above a chosen brightness as belonging to an object. Raising the threshold changes the measured boundary. The calculation may be perfectly executed while the scientific result changes because the operational rule changed. Do not describe that as a new biological observation.
Recommended validation includes representative inputs with expected outputs, awkward edge cases and intentional failures. A pipeline should report unsupported inputs rather than produce plausible-looking numbers for everything. Students can explore the idea with a spreadsheet rule: automation saves effort, but understanding the rule protects meaning. MMO helps name the method family; local validation keeps its implementation accountable.
CHAPTER 11 OF 20 · Review a method change
11. Shared methods do not guarantee shared conditions
Two studies may use the same MMO class while differing in specimen state, temperature, timing or treatment. Method identity and experimental context remain separate dimensions. This article concentrates on the route from signal to result; the accompanying Experimental Condition Ontology article concentrates on the circumstances under which that route was used.
A fictional ruler method applied to a paper strip on a flat surface differs from one applied while the strip is curled. The method family is recognisable in both records, yet the condition changes what the operator can observe. A useful comparison should state which circumstances were aligned and which were not.
Recommended method-change reviews therefore include a context matrix, not just a vocabulary match. Check that paired measurements concern the same object state and time window. If those differ, report the limitation or redesign the comparison. This keeps the three questions distinct: same quantity, same method and same conditions. Agreement on one does not settle the other two.
CHAPTER 12 OF 20 · Review a method change
12. A method comparison needs paired questions
When replacing a method, ask whether the new process answers the same operational question, over the same intended range, with acceptable uncertainty for the actual purpose. Do not begin with “Which device is better?” Better depends on what needs to be decided. A process suitable for broad classification may not support a very small numerical distinction.
Recommended study design uses appropriate reference materials or paired observations where possible, specifies the comparison rule in advance and preserves failures as well as successful readings. Report the sampled range. A method comparison based only on easy middle-range examples may miss problems at the edges.
This is a reason to learn Science beyond memorising facts: we learn to make “better” measurable. Students can compare two safe length-estimation methods using a varied set of paper strips. Before collecting data, state whether the goal is speed, closeness to a reference, consistency or accessibility. Each goal produces a different evaluation, and no single score needs to hide the others.
CHAPTER 13 OF 20 · Review a method change
13. Worked case: a consistent offset
Fictional teaching dataset: a reference procedure gives 10, 20 and 30 units for three objects. A candidate procedure gives 12, 22 and 32 units. The candidate preserves the ordering and is consistently two units higher. That pattern suggests a difference worth investigating; it does not by itself reveal the cause or justify a universal correction.
Ask whether the endpoint rule, calibration, unit definition or calculation could create the offset. Check the source records and obtain appropriate additional measurements. If a correction is adopted for the teaching exercise, document its derivation and tested range. Do not quietly subtract two from every future observation.
The lesson is that a method can produce a neat pattern without agreeing with the reference. A shared MMO mapping would make the process searchable, while the comparison evidence exposes its local behaviour. Report both. The vocabulary and the performance assessment are partners: one names what was done; the other shows how it behaved in this particular investigation.
CHAPTER 14 OF 20 · Review a method change
14. Worked case: a scale-dependent difference
Fictional teaching dataset: a reference gives 10, 20 and 30 units; a candidate gives 11, 22 and 33 units. Here the difference grows with the value rather than staying constant. A fixed correction of one unit would align the first pair and leave the others misaligned. The structure of the discrepancy matters.
Students can calculate the differences, draw candidate against reference and compare the pattern with the previous chapter. Describe the result as a teaching pattern, not as proof of a particular instrument defect. Several procedural explanations may remain possible. The next step is to inspect definitions, conversion rules and implementation details.
Recommended method review reports the relationship across the tested range rather than only one average difference. If the intended application extends beyond that range, obtain further evidence before generalising. This is a useful bridge to algebra: an additive correction and a multiplicative correction are different models, and choosing between them is a scientific decision, not just an arithmetic convenience.
CHAPTER 15 OF 20 · Review a method change
15. Worked case: agreement only under easy conditions
Fictional classroom case: ruler and image estimates agree for straight, clearly edged strips but disagree for curled strips with shadowed boundaries. The easy cases did not establish that the methods were interchangeable for every object. Their agreement was conditional on the features included in the test set.
Keep the difficult records rather than excluding them merely to improve the summary. Ask whether curling changed the target, whether the photograph represented the relevant dimension and whether the boundary rule remained usable. The review may conclude that one method is suitable only under a narrower condition. That is a meaningful result.
A recommended validation set includes realistic variation, not just ideal specimens. State the acceptance boundary and document what happens outside it. For students, this turns a disappointing disagreement into an interesting question. The method's limits become visible, and the next experiment can be designed to explore them rather than repeat the same easy demonstration.
CHAPTER 16 OF 20 · Learn, practise and communicate
16. Keep a release and mapping history
The official MMO repository offers ontology files and a public process for requesting new terms or changes. Preserve the term identifier, version and mapping rationale used in an analysis. A display label can change without the local protocol changing, while an improved definition can reveal that an earlier mapping was too broad or wrong. Source: the RGD MMO repository.
Recommended migration checks include unknown identifiers, obsolete terms, changed parent groupings and local labels mapped to several possible classes. Rerun saved query tests before updating a live system. Retain old mapping decisions so a historical analysis can still be explained.
Version the protocol separately from the ontology. A vocabulary update and a laboratory implementation update are different events and should not share one vague date. This distinction also helps classroom projects: a student can revise the method description without rewriting the original observations. The history shows learning in action while preserving what was actually done at each stage.
CHAPTER 17 OF 20 · Learn, practise and communicate
17. Build an accessible Science learning activity
Use a safe object and two clearly described measuring routes. Let students state the target, list steps, collect fictional or non-sensitive observations and compare outcomes. The point is not to teach a specialist ontology file to a beginner. It is to make method identity, implementation and checking visible through ordinary materials.
For Primary Science, focus on consistent positioning and fair comparison. For Secondary Science, add a reference check, repeated readings and a graph. For advanced learners, create a method dictionary and a proposed mapping, clearly marking it as an exercise until verified against official definitions. These are teaching suggestions, not claims about compulsory syllabus coverage.
The verified Science Learning Hub offers level-based continuation. Parents can ask the student to explain why two routes might disagree, then choose one assumption to test. That keeps the conversation curious and manageable. A precise next question is often more helpful than giving the learner a longer list of method names to memorise.
CHAPTER 18 OF 20 · Learn, practise and communicate
18. Use small-group discussion to reveal hidden steps
In a three-person learning exercise, one learner follows the procedure, one records each decision and one checks whether the record would allow another person to repeat it. Rotate the roles. This structure can expose steps that experienced users skip when describing a familiar method: where to place zero, when to stop timing or how to choose a boundary.
Ask reviewers to point to the missing instruction rather than judge the measurer. “The endpoint rule is unclear” is useful feedback. “You are careless” is not a method review. Clear language protects both the evidence and the learner's confidence.
After revision, let another learner try the written procedure without extra spoken hints. Compare what changed. The aim is not perfect uniformity or a claim that all uncertainty can be removed. It is a more intelligible measuring process. This is the eduKate learning lens: find the exact gap, make the next step visible, and check whether the repair actually worked.
CHAPTER 19 OF 20 · Learn, practise and communicate
19. Connect methods literacy to future capability
Understanding a measuring process draws on scientific concepts, mathematical checks, practical judgement and clear communication. Those capabilities are relevant to many kinds of research and technical work, but an MMO article is not a professional credential. It should help students explore what kinds of tasks interest them rather than promise a predetermined career.
A useful portfolio project might compare two safe estimation methods, explain the operational question, preserve raw records and report where agreement breaks down. Include the method descriptions and a version history. The project shows how the learner reasons about evidence, not merely how attractively they draw the final chart.
Use Careers by Subject Capability for broader exploration and the Education Hub for school-choice questions. When a real course or regulated role becomes relevant, check its current official requirements separately. Method vocabulary can open an interesting conversation about work; it cannot decide admission, qualification or suitability on its own.
CHAPTER 20 OF 20 · Learn, practise and communicate
20. Write a method note someone else can use
A reader-ready method note should identify the target quantity, MMO class and release, source protocol and version, specimen preparation, implementation, relevant conditions, quality checks, uncertainty and provenance. This is a recommended structure, not an official mandatory MMO form. Tailor it to the process and keep unsupported fields explicitly unknown.
Add an ordinary-language summary: “We estimated this quantity using this process, checked it in these ways and found these limits.” If a method was changed, say what changed and which evidence supports continued comparison. Do not let a new device name conceal a changed endpoint or software rule.
Why Science? Because a result is more trustworthy when we understand the path that produced it. MMO contributes shared method meaning. Reference checks, careful implementation and honest review give that meaning substance. Begin with one procedure you can explain fully. Then use the explanation to ask a better question, improve the record and make the next measurement more useful.
Back to contents · Previous chapter · Continue to the Science Learning Hub
Sources and scope
Official and primary sources checked on 15 October 2026: OBO Foundry: Measurement Method Ontology; RGD: official MMO repository; NIST: measurement-process characterisation; NIST: bias and accuracy; NIST: variability. Project descriptions above are attributed to their named sources. Worked datasets are fictional; record designs, review checklists and teaching activities are editorial recommendations, not official ontology requirements. No search-volume, clinical, admission or career-outcome claim is made.