Learning delivery workshop / 5 MIN READ
Keep the meaning of a learning statement when its label changes
Build a semantic identifier ledger and test the consumer’s grouping against defined meaning rather than display text.
AI-assisted research and analysis for the SNS Creative Fieldbook
Sources checked 2026-11-07
Two learning records can display the same word while referring to different defined actions. Conversely, translated labels can describe one shared action. A report that groups only by the visible word can quietly change what the learning evidence means.
What you will leave with: Build a semantic identifier ledger and test the consumer’s grouping against defined meaning rather than display text.
Use this when
- An xAPI learning feed combines several content producers.
- A multilingual learning report groups records by action labels.
Not a generic analytics migration or evidence that a stored statement proves course completion.
Lock the semantic contract and version
ADL’s xAPI 1.0.3 data specification assigns a verb’s meaning to its IRI and treats display text as a human-readable label, not a grouping key. That historical protocol version was checked on 7 November 2026; this lesson does not claim it is the latest xAPI specification or automatically applies every newer profile rule.
List the exact protocol version, applicable learning profile and intended action meaning for the feed. For each action, record the agreed identifier and the evidence that warrants emitting it. An action called completed could concern an exercise, a video or an entire assignment. The label alone does not settle that scope. Ask the producer and report owner to agree on the activity being described before approving any aggregate.
Prepare two contrasts that reveal label-based grouping
Create synthetic records for one defined action with two language labels. Then create another pair with the same visible label but different defined actions or scopes. State which records should be grouped and which should remain distinct under the agreed profile. Use fictional activity references and no actual learner information.
Inspect the consumer’s output, not just the submitted data. If the two translated records split into separate measures, the report may be grouping by words. If distinct actions merge because their labels match, the report may imply a common outcome that the producers never agreed to express. Neither problem is fixed by changing every display label to English; the grouping needs to follow the semantic contract.
Verify the activity and profile context beside the verb
Read a representative record as a complete claim: a synthetic actor performed this defined action on this activity under this applicable context. Confirm that the activity is the intended unit of reporting. A correct verb identifier attached to the wrong activity can still produce a misleading course-level total.
Keep profile-specific requirements separate from the base data format. A technically acceptable statement is not automatically a valid cmi5 completion or evidence that an LMS should award a course result. Ask the implementation owner which profile validation and business interpretation apply. When two suppliers use different definitions, preserve that difference or agree on a documented translation; do not merge them merely because a stakeholder wants one simple number.
Keep labels editable without rewriting meaning
Review how the interface presents translations, tense and explanatory text while preserving the underlying action identity. A language correction should not silently create a new metric category. Conversely, a materially different action definition should not reuse an established identifier simply to retain a familiar dashboard line.
Retain the ledger with its producer, consumer and profile versions, plus the two contrast fixtures. Recheck after a localization change or a new content supplier joins the feed. Keep any unresolved mapping visible as an evidence limitation rather than coercing it into a convenient default. Acceptance means the consumer preserves the agreed meaning through display and aggregation. It does not establish that all reported learning occurred as claimed, that profiles are universally interchangeable or that a particular statement constitutes professional certification.
Make the reasoning concrete.
A fictional academy receives two feeds whose reports both display completed. One refers to finishing a practice card and the other to satisfying an assigned course. A combined dashboard adds them together as course completions.
Group the visible word
Opening: Combine every row whose display label reads completed.
Hypothesis: The report produces a simple total.
Risk: The measure mixes different actions and activity scopes.
Group the defined claim
Opening: Check verb identifiers, activity scope and the agreed profile before combining records.
Hypothesis: The report retains the distinction between practice and assignment outcomes.
Risk: Some feeds may need separate measures or an explicit mapping.
The team separates the measures and verifies that translated labels for the same defined action still group together.
Take the questions into your next brief.
Use these prompts in your own notes. Nothing is submitted from this page.
Version
Which xAPI version and learning profile govern the feed?
Meaning
What action and activity scope does each identifier actually describe?
Translation
Do different labels for one defined action remain grouped?
Collision
Do identical labels for distinct actions remain separate?
Consumer
What evidence shows the reporting system uses the agreed semantics?
Watch for the wrong conclusion.
- Grouping statements by display words alone.
- Treating every completed label as course completion.
- Assuming base-format validity establishes profile-specific meaning.
Your next action
Build one same-meaning/different-label pair and one same-label/different-meaning pair, then inspect how the intended consumer groups them.
Sources & scope
Workflows, worksheets and fictional examples are original editorial analysis, not supplier implementation instructions or measured business results. Sources support only the specifically attributed platform facts. Supplier controls, contracts and local requirements can change; verify the actual placement and current provider guidance before implementation.
- ADL: xAPI1.0.3 Data specification, Verb section →Primary technical specification · Supports: Supports verb IRI meaning versus display-label semantics; profile and aggregation acceptance fixtures are editorial.