enable_sid_based_alignment | Determines whether segment IDs (SIDs) are used during the alignment process if they are available. If both segments contain SID values, SIDs must match in order for the segments to be aligned. | true |
enable_sid_lookup | Determines whether to leverage available SIDs for SPICE matches. | true |
enable_standard_ice_lookup | Determines whether standard ICE matching will be supported. If you set this property to false, you disable the standard ICE mechanism and operate only on SPICE matches. For example, you might want to do this when processing Java property files. The option only affects the leverage process. ICE lookup methods in the SDK will still return standard ICE matches. | true |
prefer_previously_matched_asset | Determines whether the matching algorithm should prefer matches from an asset that provided a previous match, on condition that the position of the segment is the same in both assets. This option prefers obtaining matches from a common source. In most cases, it operates with minimal confusion. However, it can cause strange results when used in sub-optimal TM group configurations. | true |
prefer_sid_over_ice_matches | Determines whether SID matches should have a higher priority than ICE matches. If you set this property to true, a SID-Preferred ICE (SPICE) match is sought before looking up standard ICE matches. Otherwise, the ICE match is sought before looking for a SPICE match. If all content contains a SID or if no content contains SIDs, the impact of this setting is minimal. This option has an impact for customer data that is a mix of SID and non-SID based content. Preferring SPICE matches over ICE matches suggests that global (SID) definitions should be preferred over the more localized context as defined for ICE matches. Setting the value to false suggests that SPICE matches should be used in the absence of a more localized context match. ICE matching derives its context from the asset and surrounding segments, while SPICE matching derives its context solely from the segment identifier.
Note: This option is relevant only when both SPICE and ICE matches are being sought and requires that both enable_standard_ice_lookup and enable_sid_lookup be enabled.
| true |
require_asset_match_for_ice | Determines whether the ICE condition will require that the TM entry match the TM AIS context of the asset being translated. If this option is enabled, then no segments for new assets will be ICE matched. Note that path normalization will affect how the TM identifies assets, and therefore can affect ICE results when this option is enabled.
Note: This option does not apply to SPICE matches and requires that the enable_standard_ice_lookup property be enabled.
| false |
require_metadata_match_for_ice | Determines whether the ICE condition will require the TM entry to have the same attribute values as the corresponding mapped AIS properties. If enabled, all mapped attributes much match their AIS property counterparts.
Note: This option does not affect SPICE matches and requires that the enable_standard_ice_lookup property be enabled.
| false |
require_full_usage_context_for_ice | Determines whether a full usage context is required for all ICE matches. For a full usage context, the TM match must have been translated between segments having the same content as those around the asset segment being translated. This option does not affect SPICE matches.
Note: This option does not affect SPICE matches and requires that the enable_standard_ice_lookup property be enabled.
| false |
require_non_null_context_for_partial_ice | Determines whether a null context should be enough to register a partial ICE match. This does not affect full context defined by a previous and next segment being null, as is the case for single segment documents.
Note: This option requires that the enable_standard_ice_lookup property be enabled.
| true |
require_asset_match_for_single_segment_asset_ice | Determines whether the ICE condition will require that the TM entry match the TM AIS context of the asset being translated when the asset only contains a single segment. If this option is enabled, then a single segment asset can only be ICEd if it has been previously translated. Note that path normalization will impact how the TM identifies assets, and therefore can impact ICE results when this option is enabled.
Note: This option does not apply to SPICE matches and requires that the enable_standard_ice_lookup property be enabled.
| true |
search_all_tms_in_group_for_ice | Determines whether or not all the TMs in the group will be searched unless an ICE match has been found. As TMs is groups are ordered and prioritized, WorldServer will by default accept 100% matches found in higher priority TMs above ICE matches found in lower priority TMs. Enabling this option will force WorldServer to continue searching lower priority TMs until an ICE match has been found or all TMs have been searched. Enabling this could impact the performance of the leverage process depending on the TM group and the nature of the data stored within it. | false |