XLIFF 1.2 does not have a way to represent overlapping <mrk> annotations. So all inline ITS markup that uses <mrk> cannot be represented in an overlapping condition. This is a general 1.2 issue unrelated to ITS.

its:termInfoRef is mapped to itsxlf:termInfoRef (and the value may need to be changed to point to a location accessible from the XLIFF document.)

its:termConfidence is mapped to itsxlf:termConfidence

When itsxlf:termConfidence is used, the annotated text must be contained within an element with a relevant its:annotatorsRef

Note: If needed, the value of the ITS termInfoRef attribute must be adjusted to point to a resource accessible from the XLIFF document. The location and format of this resource is decided by the tool creating the XLIFF document.

Text Analysis

Structural Elements

It is not recommended that Text Analysis be used at a structural level.

If a structural element of the original document has a Text Analysis annotation, it is recommended to represent that annotation using a <mrk> element that encloses the whole content of the <source> element.

When the Target Locale in XLIFF is Defined

Use the translate attribute (yes if the target locale applies, no if it does not).
It is also recommended to keep the original ITS attributes, so the file could potentially be re-purposed (even if it has a current target):

When the Target Locale in XLIFF is Defined

Use the <mrk> element with mtype='x-its-translate-yes' if the target does apply or mtype='protected' if it does not. It is also recommended to keep the original ITS attributes, so the file could potentially be re-purposed (even if it has a current target).

Important note to the example:
The natural carriers of the provenance info on the structural level are <source>, <target>, <trans-unit>, <group>, <file>. However, in case where the <source> and <target> elements are used within an <alt-trans> element (as opposed to <trans-unit>), the parent <alt-trans> element MUST carry all the provenance info relevant for the whole translation candidate.

Alternatively if a <its:provenanceRecords> element is not being used then:

Target Pointer

Provides a way to associate the node of a given source content (i.e. the content to be translated) and the node of its corresponding target content.
See http://www.w3.org/TR/its20/#target-pointer for more details.

This data category is not mapped to XLIFF but used by extracting and merging tools to get the source content from the original document and put back the translated content at its proper location.

Note that ITS processors working on XLIFF documents should use the following rule to locate the source and target content:

The attribute its:locQualityIssuesRef should be use to reference a <its:locQualityIssues> element when several instances of the Localization Quality Issue data category annotate the same content. For example:

Inline Elements

The ITS attributes for Localization Quality Issue may be used inline with an <mrk> within a <source>, <seg-source> or <target> elements in a <trans-unit> or a <alt-trans> element. For example for a text fragment not within an existing <mrk> element:

MT Confidence

Structural Elements

Use the ITS attribute its:mtConfidence to annotate the <target> and <bin-target> elements.

The MT Confidence score must be within the scope of a corresponding its:annotatorsRef attribute.

Note: If several MT engines are used to provide different <alt-trans><target> elements, then the its:annotatorsRef attribute must be used to differentiate the different MT engines. This can be done by annotating each candidate target element with a separate its:annotatorsRef attribute. Alternatively, one its:annotatorsRef attribute can be added at the <file>, <group>, or <trans-unit> level, with the values for the second and subsequent candidate translations set on their respective <target> elements.

Inline Elements

This data category is not mapped for inline content. However, because the segments are represented by inline markers in XLIFF, when you are annotating a segment, the mapping to XLIFF should use the ITS attributes on the <mrk mtype='seg'> element.