Standards-based representation of term translations based on XLIFF 2.1 glossary module in XLIFF 1.2

["Lieske, Christian" <christian.lieske@sap.com>]

Hi,

The example in http://docs.oasis-open.org/xliff/xliff-core/v2.1/os/xliff-core-v2.1-os.html#glossary-module indicates that translations of terms - e.g. encoded in a terminology database - can be inside an XLIFF 2.1 "trans-unit".

I wonder if the XLIFF 1.2 "trans-unit" extension point could be used in a similar vein.

With XLIFF 1.2 on could get something like

                   <trans-unit id="1">
                          <source>
                                This indicator is only necessary for
                                <mrk id="m1" mtype="term" type="term">manual depreciation</mrk>
                                .
                          </source>
                          <gls:glossary>
                                <gls:glossEntry
                                id="http://www.example.com/def/termbase/e12";
                                      ref="#m1">
                                      <gls:term
                                      source="http://www.example.com/def/termbase/t975";>manual depreciation</gls:term>
                                      <gls:translation
                                      source="http://www.example.com/def/termbase/t769";>manuelle Abschreibung</gls:translation>
                                </gls:glossEntry>
                          </gls:glossary>
                   </trans-unit>

Looking at the XLIFF 1.2 "trans-unit" specification "As content, Zero, one or more non-XLIFF elements [are allowed]" (see http://docs.oasis-open.org/xliff/v1.2/os/xliff-core.html#trans-unit), I wonder whether the use of the XLIFF 2.1 "glossary" element in XLIFF 1.2 would be OK, since one could take the position that it is an XLIFF element.

Would be great to get perspectives on this.

Cheers,
Christian