A translated label can make a model property easier to read without changing the underlying concept. But similar words in two systems do not automatically refer to the same term. When a film explains shared construction data across languages, keep the concept reference separate from the text displayed to the audience.
buildingSMART's Data Dictionary overview describes hosted classes, properties, allowed values, units, translations and relationships. This supports an explanation of shared definitions rather than a claim that ordinary word substitution solves every information-exchange problem.
Choose one term with a verified relationship
Ask the client for a specific approved example and the dictionary or reference used. The film should not invent a translation mapping based on an editor's judgement that two labels sound similar. A subject-matter reviewer and appropriate language reviewer may need to consider different parts of the example.
The audience can see a stable concept reference with different readable labels. A short paired display is usually more useful than a long list of technical identifiers. Retain the exact reference in the production record for verification.
Do not imply that every term in a project has an approved translation merely because the selected example does. Keep the scope of the demonstration explicit.
Separate language from units and classification
Changing the displayed language does not necessarily change the measurement unit, classification edition or allowed value set. The graphic should not alter those elements casually to make the translated screen look familiar.
If a localised unit or value expression is required, treat it as a separate approved transformation. The film needs to preserve meaning across the complete statement, not only the property name.
Avoid flags as the only language labels. A flag can imply jurisdiction, project location or regulatory applicability, which may be unrelated to the dictionary translation being shown.
A hypothetical international project film
Imagine a team presenting a shared property definition to two language groups. The first storyboard shows one word being replaced by another and announces that the data is now equivalent across all systems.
The buyer narrows the explanation to the verified term reference and its approved labels. The film demonstrates one semantic connection without promising universal interoperability. This is a fictional commissioning scenario.
Review the sequence by asking what remains constant when the display language changes. If the viewer believes the underlying property has been replaced by a different local classification, the graphic needs clearer separation.
The production scope is to communicate the client's supported terminology relationship. It does not include building a data dictionary, certifying translations or guaranteeing regulatory equivalence. Those tasks require their own qualified owners and should not be implied by a polished language-switching animation.
Ask the terminology owner to review the translated label alongside the unchanged concept reference, not as an isolated subtitle.
Discuss the film
Contact Live Images to discuss whether this approach suits your brief and what production scope would be appropriate.
Prepared with AI assistance for Live Images. Planning guidance is general; suitability and production scope must be agreed for your project.