![]() |
Translations enable different software applications to
filter and transform data into a format understandable to another
application. For example, a translation can transform and filter data
from a format within Explore for use in a third party tool, and from a
third party tool to Explore. The integrations framework translates property names, units of measure (UOM), property values, and class names. The topics covered in this section are: |
![]() |
Translations are necessary for property names because many tools have restrictions on the case or the alphabet of permissible characters that might be used. In addition, property names in one tool are usually different for the equivalent characteristic or attribute within another tool. |
![]() |
Translations are necessary for units of measure because many tools hold data in specific units that might differ from other tools for the equivalent property. Translations of Units of Measure include translations of the unit of measure and transformation of the property value into the new unit of measure. For example, a property value of 10 mA in one tool can be transformed into a property value of 0.01A in another tool. |
![]() |
Translations of property values are rare, but might be necessary in cases where the format of the value must be changed, for example, from ?Yes/No? to ?1/0.? |
![]() |
Translations of class names usually map several classes in one tool onto one class in another tool. |