An age classification and a review score answer different questions. One can describe suitability under a named classification system; the other can express an evaluation of quality. A player interface that presents both as numbers should still preserve their meanings and sources.
XMLTV distinguishes rating fields from star-rating fields. The named system matters because a value without context can be ambiguous. Do not treat every displayed number as an age, a percentage or a universal score.
Identify the system before interpreting the value
A classification label belongs to its issuing framework and territory. Similar-looking labels can have different meanings across systems. A guide record should retain the system where available rather than presenting a bare symbol that invites a guess.
A review score also needs its scale. Four out of five and four out of ten are not the same assessment. A zero score is different from an absent score. Keep unknown metadata unknown rather than filling a blank with a value that looks convenient.
Review a household restriction setup
A displayed age badge does not prove that the application enforces a restriction. Enforcement depends on the player’s settings and implementation. Conversely, a local restriction can hide an entry even when the guide provides little classification detail. These layers need separate verification.
- Identify which metadata field and classification system the source supplies.
- Check how the player interprets that field in its documented controls.
- Review the behaviour for unrated or missing data.
- Test the intended restriction using an appropriate non-sensitive example.
- Keep the parental PIN separate from the service-account password.
Avoid treating a score as a recommendation for everyone
A high review score is not a suitability guarantee for a child or a particular household. Genre, content advisories and personal preferences can matter independently. Metadata should support a decision rather than replace it with an unexplained numerical shortcut.
When reporting an error, include the programme identity, named rating system, raw value and displayed result. If the problem concerns enforcement, describe the control and actual outcome without sharing the private PIN. That distinguishes a source classification error from an interface conversion problem or an application restriction setting.
Keep claims about a player’s family controls limited to documented and observed behaviour. The presence of fields in a format does not establish that every importer uses them or that a particular setup has been configured correctly.
Useful answers
Is a star rating an age classification?
No. It is a separate kind of evaluation.
Does an age badge prove parental restrictions are active?
No. Verify the player’s actual settings and enforcement behaviour.
Should a missing rating be replaced with zero?
No. Missing data and a genuine zero value are different states.