Translating ISO 23386:2020 BIM property dictionaries is not a matter of choosing an attractive English label for a construction parameter. A property name can sound correct while its identifier, unit, data type or definition points to a different engineering quantity. Readers looking for BIM property translation, multilingual construction data dictionary mapping, IFC property terminology, building information modelling attribute translation or construction specification translation need to preserve machine-readable identity as well as human-readable meaning.
ISO 23386:2020 is the published methodology for describing, authoring and maintaining properties in interconnected data dictionaries used in construction. It supplies a governance approach to property descriptions and mapping; it does not itself distribute a universal dictionary containing every conceivable building-product attribute. When translating a manufacturer’s property record or a cross-border BIM data exchange, the task is to distinguish the source dictionary’s formal definition from a display label, then preserve the field’s identifier, permitted values and source authority.
Quick decisions for translating BIM property records: retain persistent identifiers; keep names distinct from definitions; preserve units, quantities and data types; distinguish declared, measured and derived values; document language and country scope; track property versions and requests; separate a proposed mapping from an approved mapping; never confuse a family of properties with an individual property; keep expert and applicant roles distinct; and verify that an export still points to the same technical concept after translation.
The practical answer: keep the meaning and the evidence together
This article solves a narrow reader problem: translate ISO 23386:2020 BIM property dictionaries, construction property names, data dictionary identifiers and multilingual property mappings. It is written for construction translators, BIM coordinators, specification writers, quantity surveyors and software-localisation reviewers. A translation is successful when someone who sees only the target-language file can identify the same object, evidence, responsible person, date and qualification that an informed reader would identify in the source. That test is more demanding than sounding natural. In BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, the wording carries practical consequences: a receiving designer may compare unlike attributes, an installer may order the wrong component, or a software importer may place a number into the wrong field.
ISO 23386:2020 sets out a methodology for describing, authoring and maintaining construction properties and groups of properties in interconnected data dictionaries. It addresses governance and mapping methodology, not a ready-made dictionary of every product property. The official catalogue establishes the published edition and its public scope, but the normative standard must be obtained through legitimate channels if a binding technical or conformity decision depends on exact requirements. The worked examples below are fictional learning cases, not extracts from a purchased standard or real audit, project or incident file.
There is one especially important limit: A translated property label does not establish that two database fields are semantically identical. The actual controlling property definition, identifier, unit, value type, version and mapping decision must travel together. If the source uses an undefined term, an absent number or a disputed label, the translator should record the question rather than complete the record through guesswork. Fluency must never become a covert technical decision. When several roles touch the document, preserve who wrote, checked, approved and issued each statement.
Definition lock: how to read each kind of sentence
Requirement
A requirement is an obligation attached to an identified authority, contract, standard or internal rule. Its force depends on that source, not on how stern the translated sentence sounds. Preserve the modal verb, applicable subject and exceptions. If the original says may, a translated must creates a duty that the source did not create. In BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, this distinction matters because readers may mistake the grammatical confidence of a sentence for the confidence of its evidence. Translate the source’s statement type first; improve style only after that function is secure.
Observation
An observation states what a named person, instrument or record actually showed in a bounded context. Keep the who, where, when and method. Never treat one sample, interview or database row as an unrestricted claim about an entire organization or population. In BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, this distinction matters because readers may mistake the grammatical confidence of a sentence for the confidence of its evidence. Translate the source’s statement type first; improve style only after that function is secure.
Interpretation
An interpretation explains how observed evidence relates to a criterion or professional judgment. It can be provisional, disputed, qualified or conditional. Maintain the link to the source evidence and do not quietly strip may, appears, subject to or pending review. In BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, this distinction matters because readers may mistake the grammatical confidence of a sentence for the confidence of its evidence. Translate the source’s statement type first; improve style only after that function is secure.
Decision
A decision records an authorized conclusion or action. Identify the decision maker, effective date, scope and status. A request submitted by a worker, supplier or analyst is not automatically the same thing as the approving authority’s final decision. In BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, this distinction matters because readers may mistake the grammatical confidence of a sentence for the confidence of its evidence. Translate the source’s statement type first; improve style only after that function is secure.
Instruction
An instruction tells someone to do something, often within a specified time or set of conditions. Preserve triggers, sequence, responsibility, warning strength, exclusions and contact routes. Clear English should make the action easier to perform without changing what action is required. In BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, this distinction matters because readers may mistake the grammatical confidence of a sentence for the confidence of its evidence. Translate the source’s statement type first; improve style only after that function is secure.
Description
A description is information about a product, situation or process. It may be promotional, explanatory or technical. Do not upgrade a descriptive label to a test result, official authorization, legal assurance or certification unless the source supplies that evidence. In BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, this distinction matters because readers may mistake the grammatical confidence of a sentence for the confidence of its evidence. Translate the source’s statement type first; improve style only after that function is secure.
Start with the document, not the dictionary
Read the title, issuer, revision, reporting period, page headers, tables, appendices and footnotes before touching isolated terms. Build a document map: identify the audience; mark each field as instruction, measured value, status or narrative comment; trace annex references; and note which sentences are quotations from another authority. In a multilingual project, the source may already contain translated snippets that are not current. Use the controlling source record rather than assuming the first familiar English phrase is authoritative.
A useful preliminary worksheet has columns for source wording, location, intended meaning, proposed translation, evidence reference, reviewer and status. For ISO 23386:2020, this worksheet should also show which factual claims come directly from the record and which are editorial explanations. A good translator can write a clear sentence and still leave a warning that some technical point requires validation. Do not hide unresolved questions in the final PDF footnotes where the responsible reviewer will never see them.
Keep a versioned glossary with term, definition, approved target expression, forbidden near-synonym, example, approving specialist and date. The glossary should be narrow enough to serve the actual report. It does not have to become an encyclopedia, and it should not compete with any broad language-learning resource. Its function is to prevent the same important concept from being translated differently in captions, tables, charts, safety notices and contracts.
Twenty-six technical translation decisions, explained in context
1. Property
Property means an individually defined characteristic of an object or process that can be represented as structured construction information. In BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, it is not simply a decorative technical word; it tells readers what kind of information they are seeing and what they can reasonably do with it. Before choosing the target-language expression, look at the sentence’s subject and the nearby fields. Does it refer to a particular record, an individual, a quantity, a workflow state or a defined category? Those contextual clues determine whether a familiar translation is genuinely faithful.
A common mistranslation would replace a characteristic with the name of the product carrying it. That mistake is consequential because a receiving designer may compare unlike attributes, an installer may order the wrong component, or a software importer may place a number into the wrong field. The safer decision is to translate the characteristic without changing the property being described. This also means preserving the difference between what the document explicitly says and what a knowledgeable reader might infer. If the original leaves a matter unresolved, the target version should not resolve it by changing the adjective, strengthening the verb or dropping a qualification merely to read more smoothly.
Consider this fictional teaching situation: A door record lists fire resistance alongside width and manufacturer. The translator should first label the source statement as evidence, instruction, definition or proposal; then check the supporting document and the exact scope of the phrase. A reviewer can test the result by asking a colleague to reconstruct the source claim from the translation alone. Compare the source noun, its modifier and its referenced record; a similar phrase elsewhere is not sufficient if the technical referent changes. If the colleague reaches a stronger, broader or different conclusion, revise the translation and record the reasoning.
2. Property group
Property group means a named collection that organizes related properties without merging them into a single measurement. In BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, it is not simply a decorative technical word; it tells readers what kind of information they are seeing and what they can reasonably do with it. Before choosing the target-language expression, look at the sentence’s subject and the nearby fields. Does it refer to a particular record, an individual, a quantity, a workflow state or a defined category? Those contextual clues determine whether a familiar translation is genuinely faithful.
A common mistranslation would treat the group heading as a single measurable attribute. That mistake is consequential because a receiving designer may compare unlike attributes, an installer may order the wrong component, or a software importer may place a number into the wrong field. The safer decision is to keep the group relationship and preserve the identity of each member property. This also means preserving the difference between what the document explicitly says and what a knowledgeable reader might infer. If the original leaves a matter unresolved, the target version should not resolve it by changing the adjective, strengthening the verb or dropping a qualification merely to read more smoothly.
Consider this fictional teaching situation: A façade group contains thermal transmittance and acoustic performance as separate entries. The translator should first label the source statement as evidence, instruction, definition or proposal; then check the supporting document and the exact scope of the phrase. A reviewer can test the result by asking a colleague to reconstruct the source claim from the translation alone. Keep the source document available at the precise page or field location so an authorized specialist can check the result without searching an entire report. If the colleague reaches a stronger, broader or different conclusion, revise the translation and record the reasoning.
3. Data dictionary
Data dictionary means a governed collection of property definitions, identifiers and metadata. In BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, it is not simply a decorative technical word; it tells readers what kind of information they are seeing and what they can reasonably do with it. Before choosing the target-language expression, look at the sentence’s subject and the nearby fields. Does it refer to a particular record, an individual, a quantity, a workflow state or a defined category? Those contextual clues determine whether a familiar translation is genuinely faithful.
A common mistranslation would use dictionary to mean an ordinary bilingual word list. That mistake is consequential because a receiving designer may compare unlike attributes, an installer may order the wrong component, or a software importer may place a number into the wrong field. The safer decision is to indicate that it is a structured reference dataset with controlled concepts. This also means preserving the difference between what the document explicitly says and what a knowledgeable reader might infer. If the original leaves a matter unresolved, the target version should not resolve it by changing the adjective, strengthening the verb or dropping a qualification merely to read more smoothly.
Consider this fictional teaching situation: An exporter cites Dictionary B and its property identifier. The translator should first label the source statement as evidence, instruction, definition or proposal; then check the supporting document and the exact scope of the phrase. A reviewer can test the result by asking a colleague to reconstruct the source claim from the translation alone. Where a number is involved, verify the decimal separator, unit, denominator, date, sample identity and the meaning of any inequality symbol. If the colleague reaches a stronger, broader or different conclusion, revise the translation and record the reasoning.
4. Interconnected dictionaries
Interconnected dictionaries means different governed datasets linked through explicit mappings rather than one centralized universal list. In BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, it is not simply a decorative technical word; it tells readers what kind of information they are seeing and what they can reasonably do with it. Before choosing the target-language expression, look at the sentence’s subject and the nearby fields. Does it refer to a particular record, an individual, a quantity, a workflow state or a defined category? Those contextual clues determine whether a familiar translation is genuinely faithful.
A common mistranslation would claim that all connected dictionaries automatically use identical definitions. That mistake is consequential because a receiving designer may compare unlike attributes, an installer may order the wrong component, or a software importer may place a number into the wrong field. The safer decision is to preserve each source dictionary and record the relationship between them. This also means preserving the difference between what the document explicitly says and what a knowledgeable reader might infer. If the original leaves a matter unresolved, the target version should not resolve it by changing the adjective, strengthening the verb or dropping a qualification merely to read more smoothly.
Consider this fictional teaching situation: A national library and a supplier library link two insulation attributes. The translator should first label the source statement as evidence, instruction, definition or proposal; then check the supporting document and the exact scope of the phrase. A reviewer can test the result by asking a colleague to reconstruct the source claim from the translation alone. Where roles are involved, separate the person who reports a condition from the person authorized to verify, accept or reject it. If the colleague reaches a stronger, broader or different conclusion, revise the translation and record the reasoning.
5. Property identifier
Property identifier means the stable code or other unique key assigned to a property definition. In BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, it is not simply a decorative technical word; it tells readers what kind of information they are seeing and what they can reasonably do with it. Before choosing the target-language expression, look at the sentence’s subject and the nearby fields. Does it refer to a particular record, an individual, a quantity, a workflow state or a defined category? Those contextual clues determine whether a familiar translation is genuinely faithful.
A common mistranslation would translate or prettify a code because it resembles a word. That mistake is consequential because a receiving designer may compare unlike attributes, an installer may order the wrong component, or a software importer may place a number into the wrong field. The safer decision is to copy the identifier exactly unless a documented migration has occurred. This also means preserving the difference between what the document explicitly says and what a knowledgeable reader might infer. If the original leaves a matter unresolved, the target version should not resolve it by changing the adjective, strengthening the verb or dropping a qualification merely to read more smoothly.
Consider this fictional teaching situation: A property key PR-0041 appears in an export and an approval log. The translator should first label the source statement as evidence, instruction, definition or proposal; then check the supporting document and the exact scope of the phrase. A reviewer can test the result by asking a colleague to reconstruct the source claim from the translation alone. Where an action is involved, preserve proposed, approved, started, completed and verified states as different points in time. If the colleague reaches a stronger, broader or different conclusion, revise the translation and record the reasoning.
6. Preferred label
Preferred label means the authorized human-readable name used for presenting a property in one language. In BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, it is not simply a decorative technical word; it tells readers what kind of information they are seeing and what they can reasonably do with it. Before choosing the target-language expression, look at the sentence’s subject and the nearby fields. Does it refer to a particular record, an individual, a quantity, a workflow state or a defined category? Those contextual clues determine whether a familiar translation is genuinely faithful.
A common mistranslation would substitute a popular marketing term for the approved display name. That mistake is consequential because a receiving designer may compare unlike attributes, an installer may order the wrong component, or a software importer may place a number into the wrong field. The safer decision is to translate naturally while retaining the underlying formal definition. This also means preserving the difference between what the document explicitly says and what a knowledgeable reader might infer. If the original leaves a matter unresolved, the target version should not resolve it by changing the adjective, strengthening the verb or dropping a qualification merely to read more smoothly.
Consider this fictional teaching situation: A French preferred label describes nominal panel thickness. The translator should first label the source statement as evidence, instruction, definition or proposal; then check the supporting document and the exact scope of the phrase. A reviewer can test the result by asking a colleague to reconstruct the source claim from the translation alone. Where evidence is limited, state the boundary in the same passage rather than relying on a distant general disclaimer. If the colleague reaches a stronger, broader or different conclusion, revise the translation and record the reasoning.
7. Definition
Definition means the statement that fixes what a property means and distinguishes it from related concepts. In BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, it is not simply a decorative technical word; it tells readers what kind of information they are seeing and what they can reasonably do with it. Before choosing the target-language expression, look at the sentence’s subject and the nearby fields. Does it refer to a particular record, an individual, a quantity, a workflow state or a defined category? Those contextual clues determine whether a familiar translation is genuinely faithful.
A common mistranslation would treat a short label as a complete technical definition. That mistake is consequential because a receiving designer may compare unlike attributes, an installer may order the wrong component, or a software importer may place a number into the wrong field. The safer decision is to carry the meaning and limitations of the full definition. This also means preserving the difference between what the document explicitly says and what a knowledgeable reader might infer. If the original leaves a matter unresolved, the target version should not resolve it by changing the adjective, strengthening the verb or dropping a qualification merely to read more smoothly.
Consider this fictional teaching situation: A thickness field states whether a protective coating is included. The translator should first label the source statement as evidence, instruction, definition or proposal; then check the supporting document and the exact scope of the phrase. A reviewer can test the result by asking a colleague to reconstruct the source claim from the translation alone. Compare the source noun, its modifier and its referenced record; a similar phrase elsewhere is not sufficient if the technical referent changes. If the colleague reaches a stronger, broader or different conclusion, revise the translation and record the reasoning.
8. Alternative label
Alternative label means an accepted synonym or search label that does not replace the primary property identifier. In BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, it is not simply a decorative technical word; it tells readers what kind of information they are seeing and what they can reasonably do with it. Before choosing the target-language expression, look at the sentence’s subject and the nearby fields. Does it refer to a particular record, an individual, a quantity, a workflow state or a defined category? Those contextual clues determine whether a familiar translation is genuinely faithful.
A common mistranslation would promote a synonym to an additional formal property. That mistake is consequential because a receiving designer may compare unlike attributes, an installer may order the wrong component, or a software importer may place a number into the wrong field. The safer decision is to flag it as an alias, not a new measured characteristic. This also means preserving the difference between what the document explicitly says and what a knowledgeable reader might infer. If the original leaves a matter unresolved, the target version should not resolve it by changing the adjective, strengthening the verb or dropping a qualification merely to read more smoothly.
Consider this fictional teaching situation: A catalogue offers an abbreviated and a full English field label. The translator should first label the source statement as evidence, instruction, definition or proposal; then check the supporting document and the exact scope of the phrase. A reviewer can test the result by asking a colleague to reconstruct the source claim from the translation alone. Keep the source document available at the precise page or field location so an authorized specialist can check the result without searching an entire report. If the colleague reaches a stronger, broader or different conclusion, revise the translation and record the reasoning.
9. Language tag
Language tag means a metadata code specifying which language a text label or definition uses. In BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, it is not simply a decorative technical word; it tells readers what kind of information they are seeing and what they can reasonably do with it. Before choosing the target-language expression, look at the sentence’s subject and the nearby fields. Does it refer to a particular record, an individual, a quantity, a workflow state or a defined category? Those contextual clues determine whether a familiar translation is genuinely faithful.
A common mistranslation would confuse source and target languages or overwrite the original language field. That mistake is consequential because a receiving designer may compare unlike attributes, an installer may order the wrong component, or a software importer may place a number into the wrong field. The safer decision is to preserve the tag alongside each localized text value. This also means preserving the difference between what the document explicitly says and what a knowledgeable reader might infer. If the original leaves a matter unresolved, the target version should not resolve it by changing the adjective, strengthening the verb or dropping a qualification merely to read more smoothly.
Consider this fictional teaching situation: An export stores English and German labels against one property ID. The translator should first label the source statement as evidence, instruction, definition or proposal; then check the supporting document and the exact scope of the phrase. A reviewer can test the result by asking a colleague to reconstruct the source claim from the translation alone. Where a number is involved, verify the decimal separator, unit, denominator, date, sample identity and the meaning of any inequality symbol. If the colleague reaches a stronger, broader or different conclusion, revise the translation and record the reasoning.
10. Country or jurisdiction
Country or jurisdiction means the geographic or legal scope associated with a definition or reference. In BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, it is not simply a decorative technical word; it tells readers what kind of information they are seeing and what they can reasonably do with it. Before choosing the target-language expression, look at the sentence’s subject and the nearby fields. Does it refer to a particular record, an individual, a quantity, a workflow state or a defined category? Those contextual clues determine whether a familiar translation is genuinely faithful.
A common mistranslation would assume a label used in one market has universal regulatory effect. That mistake is consequential because a receiving designer may compare unlike attributes, an installer may order the wrong component, or a software importer may place a number into the wrong field. The safer decision is to state the market scope separately from the language. This also means preserving the difference between what the document explicitly says and what a knowledgeable reader might infer. If the original leaves a matter unresolved, the target version should not resolve it by changing the adjective, strengthening the verb or dropping a qualification merely to read more smoothly.
Consider this fictional teaching situation: A national fire-rating term appears on an international product sheet. The translator should first label the source statement as evidence, instruction, definition or proposal; then check the supporting document and the exact scope of the phrase. A reviewer can test the result by asking a colleague to reconstruct the source claim from the translation alone. Where roles are involved, separate the person who reports a condition from the person authorized to verify, accept or reject it. If the colleague reaches a stronger, broader or different conclusion, revise the translation and record the reasoning.
11. Quantity kind
Quantity kind means the physical or other kind of measurable quantity represented by a numerical property. In BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, it is not simply a decorative technical word; it tells readers what kind of information they are seeing and what they can reasonably do with it. Before choosing the target-language expression, look at the sentence’s subject and the nearby fields. Does it refer to a particular record, an individual, a quantity, a workflow state or a defined category? Those contextual clues determine whether a familiar translation is genuinely faithful.
A common mistranslation would translate the same unit as proof that two quantities are identical. That mistake is consequential because a receiving designer may compare unlike attributes, an installer may order the wrong component, or a software importer may place a number into the wrong field. The safer decision is to verify the quantity meaning before comparing values. This also means preserving the difference between what the document explicitly says and what a knowledgeable reader might infer. If the original leaves a matter unresolved, the target version should not resolve it by changing the adjective, strengthening the verb or dropping a qualification merely to read more smoothly.
Consider this fictional teaching situation: Two fields both use metres but refer to length and elevation. The translator should first label the source statement as evidence, instruction, definition or proposal; then check the supporting document and the exact scope of the phrase. A reviewer can test the result by asking a colleague to reconstruct the source claim from the translation alone. Where an action is involved, preserve proposed, approved, started, completed and verified states as different points in time. If the colleague reaches a stronger, broader or different conclusion, revise the translation and record the reasoning.
12. Measurement unit
Measurement unit means the formal unit in which a numeric property value is recorded. In BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, it is not simply a decorative technical word; it tells readers what kind of information they are seeing and what they can reasonably do with it. Before choosing the target-language expression, look at the sentence’s subject and the nearby fields. Does it refer to a particular record, an individual, a quantity, a workflow state or a defined category? Those contextual clues determine whether a familiar translation is genuinely faithful.
A common mistranslation would convert a displayed unit but forget to convert values or limits. That mistake is consequential because a receiving designer may compare unlike attributes, an installer may order the wrong component, or a software importer may place a number into the wrong field. The safer decision is to retain unit symbols and authorize any mathematical conversion explicitly. This also means preserving the difference between what the document explicitly says and what a knowledgeable reader might infer. If the original leaves a matter unresolved, the target version should not resolve it by changing the adjective, strengthening the verb or dropping a qualification merely to read more smoothly.
Consider this fictional teaching situation: A thermal property is supplied with a unit that includes square metres. The translator should first label the source statement as evidence, instruction, definition or proposal; then check the supporting document and the exact scope of the phrase. A reviewer can test the result by asking a colleague to reconstruct the source claim from the translation alone. Where evidence is limited, state the boundary in the same passage rather than relying on a distant general disclaimer. If the colleague reaches a stronger, broader or different conclusion, revise the translation and record the reasoning.
13. Data type
Data type means the underlying format such as number, boolean, controlled text or date. In BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, it is not simply a decorative technical word; it tells readers what kind of information they are seeing and what they can reasonably do with it. Before choosing the target-language expression, look at the sentence’s subject and the nearby fields. Does it refer to a particular record, an individual, a quantity, a workflow state or a defined category? Those contextual clues determine whether a familiar translation is genuinely faithful.
A common mistranslation would convert a boolean field into a vague descriptive paragraph. That mistake is consequential because a receiving designer may compare unlike attributes, an installer may order the wrong component, or a software importer may place a number into the wrong field. The safer decision is to maintain a compatible value representation in the receiving system. This also means preserving the difference between what the document explicitly says and what a knowledgeable reader might infer. If the original leaves a matter unresolved, the target version should not resolve it by changing the adjective, strengthening the verb or dropping a qualification merely to read more smoothly.
Consider this fictional teaching situation: A yes-no fire-door field must remain a boolean value. The translator should first label the source statement as evidence, instruction, definition or proposal; then check the supporting document and the exact scope of the phrase. A reviewer can test the result by asking a colleague to reconstruct the source claim from the translation alone. Compare the source noun, its modifier and its referenced record; a similar phrase elsewhere is not sufficient if the technical referent changes. If the colleague reaches a stronger, broader or different conclusion, revise the translation and record the reasoning.
14. Enumerated values
Enumerated values means a restricted list of permissible value codes for a property. In BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, it is not simply a decorative technical word; it tells readers what kind of information they are seeing and what they can reasonably do with it. Before choosing the target-language expression, look at the sentence’s subject and the nearby fields. Does it refer to a particular record, an individual, a quantity, a workflow state or a defined category? Those contextual clues determine whether a familiar translation is genuinely faithful.
A common mistranslation would translate a code as free-form prose that software cannot recognize. That mistake is consequential because a receiving designer may compare unlike attributes, an installer may order the wrong component, or a software importer may place a number into the wrong field. The safer decision is to keep codes and localize the explanatory labels separately. This also means preserving the difference between what the document explicitly says and what a knowledgeable reader might infer. If the original leaves a matter unresolved, the target version should not resolve it by changing the adjective, strengthening the verb or dropping a qualification merely to read more smoothly.
Consider this fictional teaching situation: The opening-direction field permits a small controlled list. The translator should first label the source statement as evidence, instruction, definition or proposal; then check the supporting document and the exact scope of the phrase. A reviewer can test the result by asking a colleague to reconstruct the source claim from the translation alone. Keep the source document available at the precise page or field location so an authorized specialist can check the result without searching an entire report. If the colleague reaches a stronger, broader or different conclusion, revise the translation and record the reasoning.
15. Measured value
Measured value means a value established by an observation or test under identified conditions. In BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, it is not simply a decorative technical word; it tells readers what kind of information they are seeing and what they can reasonably do with it. Before choosing the target-language expression, look at the sentence’s subject and the nearby fields. Does it refer to a particular record, an individual, a quantity, a workflow state or a defined category? Those contextual clues determine whether a familiar translation is genuinely faithful.
A common mistranslation would make a measured result sound like a manufacturer’s target or claim. That mistake is consequential because a receiving designer may compare unlike attributes, an installer may order the wrong component, or a software importer may place a number into the wrong field. The safer decision is to preserve result, source evidence, method and measurement context. This also means preserving the difference between what the document explicitly says and what a knowledgeable reader might infer. If the original leaves a matter unresolved, the target version should not resolve it by changing the adjective, strengthening the verb or dropping a qualification merely to read more smoothly.
Consider this fictional teaching situation: A laboratory measures an acoustic quantity on a sample. The translator should first label the source statement as evidence, instruction, definition or proposal; then check the supporting document and the exact scope of the phrase. A reviewer can test the result by asking a colleague to reconstruct the source claim from the translation alone. Where a number is involved, verify the decimal separator, unit, denominator, date, sample identity and the meaning of any inequality symbol. If the colleague reaches a stronger, broader or different conclusion, revise the translation and record the reasoning.
16. Declared value
Declared value means a value asserted by a supplier or document issuer under its stated basis. In BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, it is not simply a decorative technical word; it tells readers what kind of information they are seeing and what they can reasonably do with it. Before choosing the target-language expression, look at the sentence’s subject and the nearby fields. Does it refer to a particular record, an individual, a quantity, a workflow state or a defined category? Those contextual clues determine whether a familiar translation is genuinely faithful.
A common mistranslation would make a declaration look like independent measurement. That mistake is consequential because a receiving designer may compare unlike attributes, an installer may order the wrong component, or a software importer may place a number into the wrong field. The safer decision is to retain the declaring organization and basis of the statement. This also means preserving the difference between what the document explicitly says and what a knowledgeable reader might infer. If the original leaves a matter unresolved, the target version should not resolve it by changing the adjective, strengthening the verb or dropping a qualification merely to read more smoothly.
Consider this fictional teaching situation: A supplier states nominal density in a catalogue. The translator should first label the source statement as evidence, instruction, definition or proposal; then check the supporting document and the exact scope of the phrase. A reviewer can test the result by asking a colleague to reconstruct the source claim from the translation alone. Where roles are involved, separate the person who reports a condition from the person authorized to verify, accept or reject it. If the colleague reaches a stronger, broader or different conclusion, revise the translation and record the reasoning.
17. Derived value
Derived value means a quantity calculated from other inputs using a stated rule. In BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, it is not simply a decorative technical word; it tells readers what kind of information they are seeing and what they can reasonably do with it. Before choosing the target-language expression, look at the sentence’s subject and the nearby fields. Does it refer to a particular record, an individual, a quantity, a workflow state or a defined category? Those contextual clues determine whether a familiar translation is genuinely faithful.
A common mistranslation would translate a calculated result as directly measured. That mistake is consequential because a receiving designer may compare unlike attributes, an installer may order the wrong component, or a software importer may place a number into the wrong field. The safer decision is to keep the calculation status and any referenced inputs visible. This also means preserving the difference between what the document explicitly says and what a knowledgeable reader might infer. If the original leaves a matter unresolved, the target version should not resolve it by changing the adjective, strengthening the verb or dropping a qualification merely to read more smoothly.
Consider this fictional teaching situation: A software schedule computes total area from geometry. The translator should first label the source statement as evidence, instruction, definition or proposal; then check the supporting document and the exact scope of the phrase. A reviewer can test the result by asking a colleague to reconstruct the source claim from the translation alone. Where an action is involved, preserve proposed, approved, started, completed and verified states as different points in time. If the colleague reaches a stronger, broader or different conclusion, revise the translation and record the reasoning.
18. Reference document
Reference document means a cited specification, standard, contract or source defining a property’s meaning. In BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, it is not simply a decorative technical word; it tells readers what kind of information they are seeing and what they can reasonably do with it. Before choosing the target-language expression, look at the sentence’s subject and the nearby fields. Does it refer to a particular record, an individual, a quantity, a workflow state or a defined category? Those contextual clues determine whether a familiar translation is genuinely faithful.
A common mistranslation would remove edition and reference detail to shorten a field. That mistake is consequential because a receiving designer may compare unlike attributes, an installer may order the wrong component, or a software importer may place a number into the wrong field. The safer decision is to keep title, edition, clause reference where given and source authority. This also means preserving the difference between what the document explicitly says and what a knowledgeable reader might infer. If the original leaves a matter unresolved, the target version should not resolve it by changing the adjective, strengthening the verb or dropping a qualification merely to read more smoothly.
Consider this fictional teaching situation: A property cites a dated project specification. The translator should first label the source statement as evidence, instruction, definition or proposal; then check the supporting document and the exact scope of the phrase. A reviewer can test the result by asking a colleague to reconstruct the source claim from the translation alone. Where evidence is limited, state the boundary in the same passage rather than relying on a distant general disclaimer. If the colleague reaches a stronger, broader or different conclusion, revise the translation and record the reasoning.
19. Revision and version
Revision and version means the particular state of a definition or dictionary at a moment in time. In BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, it is not simply a decorative technical word; it tells readers what kind of information they are seeing and what they can reasonably do with it. Before choosing the target-language expression, look at the sentence’s subject and the nearby fields. Does it refer to a particular record, an individual, a quantity, a workflow state or a defined category? Those contextual clues determine whether a familiar translation is genuinely faithful.
A common mistranslation would silently upgrade historic field meanings to newer versions. That mistake is consequential because a receiving designer may compare unlike attributes, an installer may order the wrong component, or a software importer may place a number into the wrong field. The safer decision is to preserve both historical and current identifiers in separate records. This also means preserving the difference between what the document explicitly says and what a knowledgeable reader might infer. If the original leaves a matter unresolved, the target version should not resolve it by changing the adjective, strengthening the verb or dropping a qualification merely to read more smoothly.
Consider this fictional teaching situation: A project froze dictionary version 2.1 for procurement. The translator should first label the source statement as evidence, instruction, definition or proposal; then check the supporting document and the exact scope of the phrase. A reviewer can test the result by asking a colleague to reconstruct the source claim from the translation alone. Compare the source noun, its modifier and its referenced record; a similar phrase elsewhere is not sufficient if the technical referent changes. If the colleague reaches a stronger, broader or different conclusion, revise the translation and record the reasoning.
20. Approval status
Approval status means a workflow state recording whether a definition or mapping is proposed, reviewed or accepted. In BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, it is not simply a decorative technical word; it tells readers what kind of information they are seeing and what they can reasonably do with it. Before choosing the target-language expression, look at the sentence’s subject and the nearby fields. Does it refer to a particular record, an individual, a quantity, a workflow state or a defined category? Those contextual clues determine whether a familiar translation is genuinely faithful.
A common mistranslation would translate submitted as approved or approved as implemented. That mistake is consequential because a receiving designer may compare unlike attributes, an installer may order the wrong component, or a software importer may place a number into the wrong field. The safer decision is to retain the exact workflow status and date. This also means preserving the difference between what the document explicitly says and what a knowledgeable reader might infer. If the original leaves a matter unresolved, the target version should not resolve it by changing the adjective, strengthening the verb or dropping a qualification merely to read more smoothly.
Consider this fictional teaching situation: An applicant’s request is pending expert review. The translator should first label the source statement as evidence, instruction, definition or proposal; then check the supporting document and the exact scope of the phrase. A reviewer can test the result by asking a colleague to reconstruct the source claim from the translation alone. Keep the source document available at the precise page or field location so an authorized specialist can check the result without searching an entire report. If the colleague reaches a stronger, broader or different conclusion, revise the translation and record the reasoning.
21. Applicant or requester
Applicant or requester means the person or organization proposing or requesting a property definition. In BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, it is not simply a decorative technical word; it tells readers what kind of information they are seeing and what they can reasonably do with it. Before choosing the target-language expression, look at the sentence’s subject and the nearby fields. Does it refer to a particular record, an individual, a quantity, a workflow state or a defined category? Those contextual clues determine whether a familiar translation is genuinely faithful.
A common mistranslation would assign the requester’s proposal to the approving authority. That mistake is consequential because a receiving designer may compare unlike attributes, an installer may order the wrong component, or a software importer may place a number into the wrong field. The safer decision is to make authorship and decision roles explicit. This also means preserving the difference between what the document explicitly says and what a knowledgeable reader might infer. If the original leaves a matter unresolved, the target version should not resolve it by changing the adjective, strengthening the verb or dropping a qualification merely to read more smoothly.
Consider this fictional teaching situation: A product association submits a new fire-performance property. The translator should first label the source statement as evidence, instruction, definition or proposal; then check the supporting document and the exact scope of the phrase. A reviewer can test the result by asking a colleague to reconstruct the source claim from the translation alone. Where a number is involved, verify the decimal separator, unit, denominator, date, sample identity and the meaning of any inequality symbol. If the colleague reaches a stronger, broader or different conclusion, revise the translation and record the reasoning.
22. Expert reviewer
Expert reviewer means a person appointed to assess the suitability and clarity of a proposed definition. In BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, it is not simply a decorative technical word; it tells readers what kind of information they are seeing and what they can reasonably do with it. Before choosing the target-language expression, look at the sentence’s subject and the nearby fields. Does it refer to a particular record, an individual, a quantity, a workflow state or a defined category? Those contextual clues determine whether a familiar translation is genuinely faithful.
A common mistranslation would translate an expert’s question as a final rejection. That mistake is consequential because a receiving designer may compare unlike attributes, an installer may order the wrong component, or a software importer may place a number into the wrong field. The safer decision is to retain the nature of the review comment and any pending response. This also means preserving the difference between what the document explicitly says and what a knowledgeable reader might infer. If the original leaves a matter unresolved, the target version should not resolve it by changing the adjective, strengthening the verb or dropping a qualification merely to read more smoothly.
Consider this fictional teaching situation: A reviewer asks whether water absorption is by mass or volume. The translator should first label the source statement as evidence, instruction, definition or proposal; then check the supporting document and the exact scope of the phrase. A reviewer can test the result by asking a colleague to reconstruct the source claim from the translation alone. Where roles are involved, separate the person who reports a condition from the person authorized to verify, accept or reject it. If the colleague reaches a stronger, broader or different conclusion, revise the translation and record the reasoning.
23. Commission of experts
Commission of experts means a governing expert group involved in review and decision making. In BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, it is not simply a decorative technical word; it tells readers what kind of information they are seeing and what they can reasonably do with it. Before choosing the target-language expression, look at the sentence’s subject and the nearby fields. Does it refer to a particular record, an individual, a quantity, a workflow state or a defined category? Those contextual clues determine whether a familiar translation is genuinely faithful.
A common mistranslation would refer to any informal project team as the formal commission. That mistake is consequential because a receiving designer may compare unlike attributes, an installer may order the wrong component, or a software importer may place a number into the wrong field. The safer decision is to preserve the actual decision-making body and its recorded action. This also means preserving the difference between what the document explicitly says and what a knowledgeable reader might infer. If the original leaves a matter unresolved, the target version should not resolve it by changing the adjective, strengthening the verb or dropping a qualification merely to read more smoothly.
Consider this fictional teaching situation: A minutes record lists commission feedback on a duplicate property. The translator should first label the source statement as evidence, instruction, definition or proposal; then check the supporting document and the exact scope of the phrase. A reviewer can test the result by asking a colleague to reconstruct the source claim from the translation alone. Where an action is involved, preserve proposed, approved, started, completed and verified states as different points in time. If the colleague reaches a stronger, broader or different conclusion, revise the translation and record the reasoning.
24. Duplicate candidate
Duplicate candidate means a proposed definition that may already exist under another label or identifier. In BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, it is not simply a decorative technical word; it tells readers what kind of information they are seeing and what they can reasonably do with it. Before choosing the target-language expression, look at the sentence’s subject and the nearby fields. Does it refer to a particular record, an individual, a quantity, a workflow state or a defined category? Those contextual clues determine whether a familiar translation is genuinely faithful.
A common mistranslation would create two equivalent fields because their translated names differ. That mistake is consequential because a receiving designer may compare unlike attributes, an installer may order the wrong component, or a software importer may place a number into the wrong field. The safer decision is to check definitions and identifiers before accepting duplication. This also means preserving the difference between what the document explicitly says and what a knowledgeable reader might infer. If the original leaves a matter unresolved, the target version should not resolve it by changing the adjective, strengthening the verb or dropping a qualification merely to read more smoothly.
Consider this fictional teaching situation: A proposed sound-insulation field resembles an existing property. The translator should first label the source statement as evidence, instruction, definition or proposal; then check the supporting document and the exact scope of the phrase. A reviewer can test the result by asking a colleague to reconstruct the source claim from the translation alone. Where evidence is limited, state the boundary in the same passage rather than relying on a distant general disclaimer. If the colleague reaches a stronger, broader or different conclusion, revise the translation and record the reasoning.
25. Mapping relation
Mapping relation means an explicit relationship between a property in one dictionary and one in another. In BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, it is not simply a decorative technical word; it tells readers what kind of information they are seeing and what they can reasonably do with it. Before choosing the target-language expression, look at the sentence’s subject and the nearby fields. Does it refer to a particular record, an individual, a quantity, a workflow state or a defined category? Those contextual clues determine whether a familiar translation is genuinely faithful.
A common mistranslation would call every related field an exact equivalence. That mistake is consequential because a receiving designer may compare unlike attributes, an installer may order the wrong component, or a software importer may place a number into the wrong field. The safer decision is to specify whether the relationship is exact, partial or still under review. This also means preserving the difference between what the document explicitly says and what a knowledgeable reader might infer. If the original leaves a matter unresolved, the target version should not resolve it by changing the adjective, strengthening the verb or dropping a qualification merely to read more smoothly.
Consider this fictional teaching situation: Two dictionaries use similar labels but different reference temperatures. The translator should first label the source statement as evidence, instruction, definition or proposal; then check the supporting document and the exact scope of the phrase. A reviewer can test the result by asking a colleague to reconstruct the source claim from the translation alone. Compare the source noun, its modifier and its referenced record; a similar phrase elsewhere is not sufficient if the technical referent changes. If the colleague reaches a stronger, broader or different conclusion, revise the translation and record the reasoning.
26. Mapping evidence
Mapping evidence means the recorded justification used to connect property definitions across dictionaries. In BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, it is not simply a decorative technical word; it tells readers what kind of information they are seeing and what they can reasonably do with it. Before choosing the target-language expression, look at the sentence’s subject and the nearby fields. Does it refer to a particular record, an individual, a quantity, a workflow state or a defined category? Those contextual clues determine whether a familiar translation is genuinely faithful.
A common mistranslation would state that a mapping is verified solely because labels match. That mistake is consequential because a receiving designer may compare unlike attributes, an installer may order the wrong component, or a software importer may place a number into the wrong field. The safer decision is to retain expert decision, scope and any unresolved issue. This also means preserving the difference between what the document explicitly says and what a knowledgeable reader might infer. If the original leaves a matter unresolved, the target version should not resolve it by changing the adjective, strengthening the verb or dropping a qualification merely to read more smoothly.
Consider this fictional teaching situation: A mapping note compares units and tests before approval. The translator should first label the source statement as evidence, instruction, definition or proposal; then check the supporting document and the exact scope of the phrase. A reviewer can test the result by asking a colleague to reconstruct the source claim from the translation alone. Keep the source document available at the precise page or field location so an authorized specialist can check the result without searching an entire report. If the colleague reaches a stronger, broader or different conclusion, revise the translation and record the reasoning.
27. Exchange representation
Exchange representation means the serialized field structure received by software or collaborators. In BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, it is not simply a decorative technical word; it tells readers what kind of information they are seeing and what they can reasonably do with it. Before choosing the target-language expression, look at the sentence’s subject and the nearby fields. Does it refer to a particular record, an individual, a quantity, a workflow state or a defined category? Those contextual clues determine whether a familiar translation is genuinely faithful.
A common mistranslation would translate machine keys and break the import while improving readability. That mistake is consequential because a receiving designer may compare unlike attributes, an installer may order the wrong component, or a software importer may place a number into the wrong field. The safer decision is to localize display text but leave machine keys subject to schema governance. This also means preserving the difference between what the document explicitly says and what a knowledgeable reader might infer. If the original leaves a matter unresolved, the target version should not resolve it by changing the adjective, strengthening the verb or dropping a qualification merely to read more smoothly.
Consider this fictional teaching situation: A JSON export carries a code, an English label and a numeric value. The translator should first label the source statement as evidence, instruction, definition or proposal; then check the supporting document and the exact scope of the phrase. A reviewer can test the result by asking a colleague to reconstruct the source claim from the translation alone. Where a number is involved, verify the decimal separator, unit, denominator, date, sample identity and the meaning of any inequality symbol. If the colleague reaches a stronger, broader or different conclusion, revise the translation and record the reasoning.
Twelve worked translation cases: what a reviewer should actually do
Worked case 1: A concrete performance declaration
Source situation: A supplier uses compressive strength in a product datasheet while the project dictionary uses characteristic compressive strength. An attractive but unsafe rewrite would be: An editor treats both phrases as automatically equivalent. The faithful approach is different: Retain the two definitions and ask whether statistic, method and reference conditions match. This example is deliberately fictional, but the reasoning transfers to a real bilingual report. The translator is not there to remove awkward facts or finish an investigation. The translator is there to make the same bounded claim accessible in another language.
Why the difference matters: A shared engineering word does not resolve a methodological difference. A reviewer should read the source and target next to the governing evidence, underline every number and status word, and ask what practical action a reader would take after each version. Would the reader order a product, escalate a concern, close an audit item or send a customer notice on a different basis? If the answer changes, the translation is not equivalent. Keep a review note that names the unresolved decision and the specialist authorized to make it.
Worked case 2: An old label on a new export
Source situation: A project document cites a property code first used in an earlier dictionary release. An attractive but unsafe rewrite would be: The translator silently inserts the latest description without a revision note. The faithful approach is different: Preserve the referenced edition and annotate any authorized migration separately. This example is deliberately fictional, but the reasoning transfers to a real bilingual report. The translator is not there to remove awkward facts or finish an investigation. The translator is there to make the same bounded claim accessible in another language.
Why the difference matters: A project needs to reconstruct its historic design basis. A reviewer should read the source and target next to the governing evidence, underline every number and status word, and ask what practical action a reader would take after each version. Would the reader order a product, escalate a concern, close an audit item or send a customer notice on a different basis? If the answer changes, the translation is not equivalent. Keep a review note that names the unresolved decision and the specialist authorized to make it.
Worked case 3: A number without a unit
Source situation: A panel list contains value 0.035 beside a short translated property title. An attractive but unsafe rewrite would be: The translation adds W per metre kelvin because it sounds plausible. The faithful approach is different: Leave the value unconverted and request the source unit before publishing. This example is deliberately fictional, but the reasoning transfers to a real bilingual report. The translator is not there to remove awkward facts or finish an investigation. The translator is there to make the same bounded claim accessible in another language.
Why the difference matters: Two physical properties can carry similar-looking numbers. A reviewer should read the source and target next to the governing evidence, underline every number and status word, and ask what practical action a reader would take after each version. Would the reader order a product, escalate a concern, close an audit item or send a customer notice on a different basis? If the answer changes, the translation is not equivalent. Keep a review note that names the unresolved decision and the specialist authorized to make it.
Worked case 4: A marketing synonym
Source situation: A vendor calls a window soundproof in a brochure but supplies a measurable sound-insulation field elsewhere. An attractive but unsafe rewrite would be: The target dictionary stores soundproof as the formal property name. The faithful approach is different: Translate the brochure claim separately and retain the measurable field definition. This example is deliberately fictional, but the reasoning transfers to a real bilingual report. The translator is not there to remove awkward facts or finish an investigation. The translator is there to make the same bounded claim accessible in another language.
Why the difference matters: Marketing copy and structured evidence have different authority. A reviewer should read the source and target next to the governing evidence, underline every number and status word, and ask what practical action a reader would take after each version. Would the reader order a product, escalate a concern, close an audit item or send a customer notice on a different basis? If the answer changes, the translation is not equivalent. Keep a review note that names the unresolved decision and the specialist authorized to make it.
Worked case 5: Two names for one field
Source situation: English and Spanish labels are attached to the same property identifier. An attractive but unsafe rewrite would be: The receiving software creates two separate parameters. The faithful approach is different: Keep the common identifier and store the labels as language variants. This example is deliberately fictional, but the reasoning transfers to a real bilingual report. The translator is not there to remove awkward facts or finish an investigation. The translator is there to make the same bounded claim accessible in another language.
Why the difference matters: Multilingual text is not proof of two different characteristics. A reviewer should read the source and target next to the governing evidence, underline every number and status word, and ask what practical action a reader would take after each version. Would the reader order a product, escalate a concern, close an audit item or send a customer notice on a different basis? If the answer changes, the translation is not equivalent. Keep a review note that names the unresolved decision and the specialist authorized to make it.
Worked case 6: Units and conversion
Source situation: A received model states thickness in millimetres while a report expects metres. An attractive but unsafe rewrite would be: The translated label is updated but 150 remains 150. The faithful approach is different: Convert the numerical value only with authorized calculation and precision rules. This example is deliberately fictional, but the reasoning transfers to a real bilingual report. The translator is not there to remove awkward facts or finish an investigation. The translator is there to make the same bounded claim accessible in another language.
Why the difference matters: A unit swap without numerical conversion changes physical meaning. A reviewer should read the source and target next to the governing evidence, underline every number and status word, and ask what practical action a reader would take after each version. Would the reader order a product, escalate a concern, close an audit item or send a customer notice on a different basis? If the answer changes, the translation is not equivalent. Keep a review note that names the unresolved decision and the specialist authorized to make it.
Worked case 7: Conditional applicability
Source situation: A fire property applies only to a specified element configuration. An attractive but unsafe rewrite would be: The translation removes the configuration condition to make a shorter label. The faithful approach is different: Preserve the condition adjacent to the value and approval evidence. This example is deliberately fictional, but the reasoning transfers to a real bilingual report. The translator is not there to remove awkward facts or finish an investigation. The translator is there to make the same bounded claim accessible in another language.
Why the difference matters: The recipient could apply evidence to a different construction product. A reviewer should read the source and target next to the governing evidence, underline every number and status word, and ask what practical action a reader would take after each version. Would the reader order a product, escalate a concern, close an audit item or send a customer notice on a different basis? If the answer changes, the translation is not equivalent. Keep a review note that names the unresolved decision and the specialist authorized to make it.
Worked case 8: Proposed mapping in a meeting
Source situation: Meeting notes suggest connecting two insulation properties across dictionaries. An attractive but unsafe rewrite would be: The final translation calls the link validated interoperability. The faithful approach is different: State that the mapping was proposed and record who must assess it. This example is deliberately fictional, but the reasoning transfers to a real bilingual report. The translator is not there to remove awkward facts or finish an investigation. The translator is there to make the same bounded claim accessible in another language.
Why the difference matters: Suggestion and approval are separate governance events. A reviewer should read the source and target next to the governing evidence, underline every number and status word, and ask what practical action a reader would take after each version. Would the reader order a product, escalate a concern, close an audit item or send a customer notice on a different basis? If the answer changes, the translation is not equivalent. Keep a review note that names the unresolved decision and the specialist authorized to make it.
Worked case 9: The missing datatype
Source situation: An exporter expects a boolean for an installed-state parameter. An attractive but unsafe rewrite would be: The target description says yes in free text and adds contextual comments in the value cell. The faithful approach is different: Preserve the boolean payload and put explanation in a supported note field. This example is deliberately fictional, but the reasoning transfers to a real bilingual report. The translator is not there to remove awkward facts or finish an investigation. The translator is there to make the same bounded claim accessible in another language.
Why the difference matters: A well-written label cannot repair a schema-invalid value. A reviewer should read the source and target next to the governing evidence, underline every number and status word, and ask what practical action a reader would take after each version. Would the reader order a product, escalate a concern, close an audit item or send a customer notice on a different basis? If the answer changes, the translation is not equivalent. Keep a review note that names the unresolved decision and the specialist authorized to make it.
Worked case 10: A duplicate definition request
Source situation: A contractor proposes a pressure property that seems identical to one already governed. An attractive but unsafe rewrite would be: The editor publishes a new translated ID without a duplicate review. The faithful approach is different: Keep the proposal status and send it to the dictionary owner for comparison. This example is deliberately fictional, but the reasoning transfers to a real bilingual report. The translator is not there to remove awkward facts or finish an investigation. The translator is there to make the same bounded claim accessible in another language.
Why the difference matters: Duplication creates incompatible schedules and ambiguous equipment selection. A reviewer should read the source and target next to the governing evidence, underline every number and status word, and ask what practical action a reader would take after each version. Would the reader order a product, escalate a concern, close an audit item or send a customer notice on a different basis? If the answer changes, the translation is not equivalent. Keep a review note that names the unresolved decision and the specialist authorized to make it.
Worked case 11: Cross-border reference
Source situation: A product requirement cites a national document and a local fire classification. An attractive but unsafe rewrite would be: The English translation substitutes a superficially similar international category. The faithful approach is different: Retain the jurisdiction and cited edition and request expert interpretation. This example is deliberately fictional, but the reasoning transfers to a real bilingual report. The translator is not there to remove awkward facts or finish an investigation. The translator is there to make the same bounded claim accessible in another language.
Why the difference matters: Regulatory categories should not be equated by resemblance. A reviewer should read the source and target next to the governing evidence, underline every number and status word, and ask what practical action a reader would take after each version. Would the reader order a product, escalate a concern, close an audit item or send a customer notice on a different basis? If the answer changes, the translation is not equivalent. Keep a review note that names the unresolved decision and the specialist authorized to make it.
Worked case 12: Final machine import
Source situation: A localization vendor updates field labels but also edits internal property keys. An attractive but unsafe rewrite would be: A building model import rejects records or maps values to the wrong elements. The faithful approach is different: Protect keys, test imports and compare IDs before and after translation. This example is deliberately fictional, but the reasoning transfers to a real bilingual report. The translator is not there to remove awkward facts or finish an investigation. The translator is there to make the same bounded claim accessible in another language.
Why the difference matters: Readable English and machine integrity must be tested separately. A reviewer should read the source and target next to the governing evidence, underline every number and status word, and ask what practical action a reader would take after each version. Would the reader order a product, escalate a concern, close an audit item or send a customer notice on a different basis? If the answer changes, the translation is not equivalent. Keep a review note that names the unresolved decision and the specialist authorized to make it.
A twelve-stage professional review workflow
1. Confirm the exact document and edition
Record the full ISO 23386:2020 designation, issuer, source-language version and scope. Do not substitute another edition even when newer documentation exists; a historical record must still be traceable. For BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, the reviewer should document one concrete pass-or-fail check before allowing this stage to close. A check that has no named reviewer or preserved evidence is not a reliable safeguard. Keep the test small and repeatable so a later translator can reconstruct what was reviewed.
2. Identify the intended use
Ask whether the target is a public explanation, internal working translation, customer notice, contractual attachment or machine-import field. The same vocabulary can demand different layout and verification controls without changing its underlying meaning. For BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, the reviewer should document one concrete pass-or-fail check before allowing this stage to close. A check that has no named reviewer or preserved evidence is not a reliable safeguard. Keep the test small and repeatable so a later translator can reconstruct what was reviewed.
3. Separate statement types
Mark definitions, requirements, observations, interpretations, reported views, proposed actions and approved decisions before drafting. These categories prevent accidental upgrades from tentative language to definitive claims. For BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, the reviewer should document one concrete pass-or-fail check before allowing this stage to close. A check that has no named reviewer or preserved evidence is not a reliable safeguard. Keep the test small and repeatable so a later translator can reconstruct what was reviewed.
4. Lock identifiers and numbers
Copy reference numbers, record IDs, units, dates, mathematical operators and controlled codes into a protected review sheet. When conversion is approved, retain both the source value and calculation record. For BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, the reviewer should document one concrete pass-or-fail check before allowing this stage to close. A check that has no named reviewer or preserved evidence is not a reliable safeguard. Keep the test small and repeatable so a later translator can reconstruct what was reviewed.
5. Build the specialist glossary
Approve terms in context rather than translating isolated words. Add the forbidden near-synonym and explain why its meaning differs. Confirm consistent use in diagrams, tables, headings, form fields and narrative text. For BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, the reviewer should document one concrete pass-or-fail check before allowing this stage to close. A check that has no named reviewer or preserved evidence is not a reliable safeguard. Keep the test small and repeatable so a later translator can reconstruct what was reviewed.
6. Draft for comprehension
Write direct, natural sentences and keep one technical assertion per paragraph where possible. The source may be awkward, but grammar can be improved without inventing a requirement, finding, status or cause. For BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, the reviewer should document one concrete pass-or-fail check before allowing this stage to close. A check that has no named reviewer or preserved evidence is not a reliable safeguard. Keep the test small and repeatable so a later translator can reconstruct what was reviewed.
7. Check the chain of evidence
Follow every conclusion back to its cited record or described source. Preserve document roles and evidence confidence; never make a supplier’s statement, worker allegation or author’s inference look externally certified. For BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, the reviewer should document one concrete pass-or-fail check before allowing this stage to close. A check that has no named reviewer or preserved evidence is not a reliable safeguard. Keep the test small and repeatable so a later translator can reconstruct what was reviewed.
8. Validate units and comparisons
Audit formulas, denominators, thresholds, selected populations, sample sizes and reporting periods. If the document provides no target value, do not manufacture one from a guideline or outside source. For BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, the reviewer should document one concrete pass-or-fail check before allowing this stage to close. A check that has no named reviewer or preserved evidence is not a reliable safeguard. Keep the test small and repeatable so a later translator can reconstruct what was reviewed.
9. Conduct an independent bilingual review
Use a second reviewer with access to both versions, ideally with technical competence. Ask them to compare claims and possible actions, not merely grammar and punctuation. For BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, the reviewer should document one concrete pass-or-fail check before allowing this stage to close. A check that has no named reviewer or preserved evidence is not a reliable safeguard. Keep the test small and repeatable so a later translator can reconstruct what was reviewed.
10. Escalate unresolved questions
Create a numbered question log containing exact source excerpt, proposed handling, issue owner, resolution and approval date. An unanswered question should remain visibly unanswered in the working version. For BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, the reviewer should document one concrete pass-or-fail check before allowing this stage to close. A check that has no named reviewer or preserved evidence is not a reliable safeguard. Keep the test small and repeatable so a later translator can reconstruct what was reviewed.
11. Perform format and accessibility checks
Compare tables, page breaks, symbols, language tags, legends, hyperlinks and right-to-left handling where relevant. A correct phrase in a clipped cell or misaligned chart can still mislead the reader. For BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, the reviewer should document one concrete pass-or-fail check before allowing this stage to close. A check that has no named reviewer or preserved evidence is not a reliable safeguard. Keep the test small and repeatable so a later translator can reconstruct what was reviewed.
12. Release with version control
Record approval, intended audience, date, file checksum or version, and distribution restrictions. If a source record changes after translation, issue a controlled update rather than silently replacing the earlier evidence. For BIM property dictionary exports, property-definition requests and cross-platform construction data exchanges, the reviewer should document one concrete pass-or-fail check before allowing this stage to close. A check that has no named reviewer or preserved evidence is not a reliable safeguard. Keep the test small and repeatable so a later translator can reconstruct what was reviewed.
How a reader can check the finished translation independently
Cover the source text and ask a target-language reader to describe what was measured or reported, who made the statement, what remains uncertain and what decision is permitted. Then reveal the source and compare. The most useful errors are not spelling mistakes; they are changes in scope, status, authority and time. Test at least one table, one numerical statement, one conditional instruction, one version reference and one statement with restricted confidence.
Next, do the reverse: start with a source-language reader who has not seen the translation. Have each reader answer a short set of questions: Which objects or people are covered? What happened, and when? Is this result measured, declared, proposed or verified? What evidence would be needed to act? Are any important terms undefined? If the two readers give materially different answers, do not resolve the difference by voting on whichever English sentence sounds nicer. Trace the disagreement to the controlling field.
The final quality check should name what the translation cannot do. It cannot replace a licensed standard, issue a certification, validate an engineering model, rule on an allegation, or impose a water utility target merely by changing languages. Its value is practical clarity within the documented limits. That restraint is what makes technical translation trustworthy.
Frequently asked questions
Can I translate the BIM property identifier?
Normally no. Treat a stable identifier as data, not a sentence, unless the dictionary owner has formally migrated it. For a real ISO 23386:2020 document, consult the applicable source edition and an authorized domain reviewer before treating a translated phrase as a formal determination.
Does ISO 23386:2020 supply every construction-property name?
No. It gives a methodology for describing and governing properties and their interconnection. For a real ISO 23386:2020 document, consult the applicable source edition and an authorized domain reviewer before treating a translated phrase as a formal determination.
Are similar English labels enough to prove two properties match?
No. Compare definition, quantity, unit, applicable object, reference and version. For a real ISO 23386:2020 document, consult the applicable source edition and an authorized domain reviewer before treating a translated phrase as a formal determination.
Should a translator convert units?
Only under an approved conversion rule that preserves the original value, precision and audit trail. For a real ISO 23386:2020 document, consult the applicable source edition and an authorized domain reviewer before treating a translated phrase as a formal determination.
What if an approved property changes during translation?
Flag the revision and coordinate with the dictionary owner; do not silently rewrite the engineering baseline. For a real ISO 23386:2020 document, consult the applicable source edition and an authorized domain reviewer before treating a translated phrase as a formal determination.
Can translation certify a BIM model?
No. Language review supports interoperability; it cannot replace technical validation, contractual approval or data exchange testing. For a real ISO 23386:2020 document, consult the applicable source edition and an authorized domain reviewer before treating a translated phrase as a formal determination.
Official references and connected learning
The public scope and edition details can be checked in the official ISO catalogue entry for ISO 23386:2020. This independent educational article paraphrases publicly available scope information and uses original fictional scenarios. It does not reproduce protected requirements, provide a compliance certificate or replace professional review.
For general translation method, return to the existing Master Art of Translation, governed in the site architecture by EDKSG-TRANS-MASTER-WORLD-000. For systematic terminology development use the Vocabulary Learning Hub. For grammar, source interpretation and written meaning, use How English Works — Translation and Meaning Across Languages. The longform teaching and reading layout follows the established eduKateSG educational article format, but this article owns only the precise specialist subject stated in its title.
A strong translation makes difficult information more accessible without making it more certain than the source permits. Retain identifiers and boundaries, check claims against evidence, invite the right specialist to resolve genuine ambiguities, and release a version the next reader can trust. The larger language-learning architecture remains the place for general instruction; this page solves one focused document-translation task.