Bidirectional data normalization

On various platforms and in relational databases (RDBMS), data can be stored in different bidirectional layouts. When data is transferred from one system to another or is used in data comparison, it must first be transformed to one common layout. Otherwise the logic based on data manipulation might provide incorrect results.

When moving data from one database or platform to another, transformations are performed using the following five attributes:

A combination of specific values for the preceding five attributes constitutes a bidirectional layout.

Each time data is retrieved from an external RDBMS that uses a layout different from the Integration Composer Bidi layout, it must be transformed to the Integration Composer Bidi layout. This transform must be done before the user can work with it in Integration Composer.

Consequently, when you define a new data source or data schema, you must define the attributes for transforming the data in the data source to the formats needed in Integration Composer.

The following table describes the default values specified for the bidirectional attributes and the options available for Integration Composer.

Table 1. Bidirectional layout formats for Integration Composer
Attribute Default Possible Values
Ordering Scheme Implicit Implicit: (also known as Logical) The text is stored in the same order as it is spoken and, usually, entered.

Visual: The text is stored ready for presentation.

Text Orientation LTR (This feature is also known as Base Direction.)

Left-to-Right: The directional runs are laid out from left to right. This direction is appropriate for text that is mostly written with left-to-right scripts but might contain words or phrases written in right-to-left scripts. The default alignment is set to left.

Right-to-Left: The directional runs are laid out from right to left. This direction is appropriate for text that is mostly written with right-to-left scripts but might contain numbers, words, or phrases written in left-to-right scripts. The default alignment is set to right.

Contextual Left-to-Right: The required direction of the text is determined based on the text itself. If the first strong character belongs to a left-to-right script, the direction resolves to Left-to-Right. If the first strong character belongs to a right-to-left script, the direction resolves to Right-to-Left. If there is no strong character in the text, the direction resolves to Left-to-Right.

Contextual Right-to-Left: The required direction of the text is determined based on the text itself as described for the preceding Contextual Left-to-Right value. However, in this case, if there is no strong character in the text, the direction resolves to Right-to-Left.

Symmetric Swapping Yes Yes: Replace characters with their symmetric equivalent in right-to-left runs.

No: Do not replace characters with their symmetric equivalent in right-to-left runs.

Text Shaping Nominal Nominal: Arabic letters are encoded with intrinsic code points (in the "06xx" range for Unicode).

Shaped: Arabic letters are encoded as presentation forms which can be Initial, Middle, Final, or Isolated.

Initial Shaping: Arabic letters encoded with intrinsic code points must be transformed to Initial shapes for presentation.

Middle Shaping: Arabic letters encoded with intrinsic code points must be transformed to Middle shapes for presentation.

Final Shaping: Arabic letters encoded with intrinsic code points must be transformed to Final shapes for presentation.

Isolated Shaping: Arabic letters encoded with intrinsic code points must be transformed to Isolated shapes for presentation.

Numerals Nominal (This feature is also known as Numeric Shaping.)

Nominal: Display digits as Arabic-European digits.

National: Display regular digits as Arabic-Indic digits (National format).

Contextual: Display regular digits as Arabic-Indic digits if following Arabic letters. Otherwise, display as Arabic-European digits.



Feedback