RE: [ISSUE-75] - Domain - 2.a.

Hi Christian, all,

I’m always a bit uncomfortable with stating what a mechanism is NOT doing in a specification. It seems we should be able to define what it does do and that should be sufficient.

I would also argue that the scenario “try MT engine A, then MT engine B” can work perfectly well with what we have today. The specification provides domainMapping for some basic mappings that allow for example to point multiple keywords to a more common unique 'domain' label.

For example you have a mapping as this: domainMapping="'sports law' Legal, 'property law' Legal"
and two MT engines: they each have a user-defined table that provide additional re-direction (they are even possibly pair specific: one maps 'Legal' to 'LEGAL_EN_PT' and the other maps 'Legal' to '5242e0762354527_legal'.

Using domainMapping for more than simple grouping is bound to have quick limitations:

a) what if you add a third MT engine? You have to edit every single rules document to add the new mapping?

b) how do you map to engine that are defined per pair?

IMO the mapping to the values used to slect the MT engine belongs to the process side, not the input.


From: Lieske, Christian [] 
Sent: Tuesday, January 29, 2013 8:11 AM
Subject: [ISSUE-75] - Domain - 2.a.


One of my comments related to “domain” (see was the following:

2.a. Domain "systems" may not be harmonized across a processing chain. A Translation Memory component may for example work with different domains than a Machine Translation system that is part of the same processing chain. Since ITS 2.0 "domain" currently does not allow to capture the information "This is for component X" these scenarios cannot be addressed.

During the face-to-face in Prague, we achieved the following status (see a note should explain that “domain” (and possibly other data categories) do not accommodate what could be called multi-engine scenario.

Here is my suggestion for a note …

The focus of ITS 2.0, and some of the usage scenarios addressed in ITS 2.0 showcases (see is on “single engine” environments. Example: the Machine Translation (MT) usage scenarios do not work along the lines of process chains such as “try MT engine A, then MT engine B”. Accordingly, ITS 2.0 has few provisions to support this kind of “multi-engine” environments which for example require domain-related information such as “try MT engine A with domain ‘financials’, then try MT engine B with domain ‘healthcare’”.

Received on Tuesday, 29 January 2013 15:56:31 UTC