- From: CVS User clieske <cvsmail@w3.org>
- Date: Thu, 28 Feb 2013 06:13:05 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv7715/drafts/its20
Modified Files:
its20.odd
Log Message:
Update according to resolution for [ISSUE-75] - Domain - 2.a. [ACTION-434] - Note related to "domainMapping" in "multi-engine" scenarios
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/02/27 19:48:26 1.326
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/02/28 06:13:05 1.327
@@ -3042,6 +3042,18 @@
<att>domainMapping</att> allows for using IRIs too. For the mapping, they are
regarded as ordinary string values.</p>
</note>
+ <note>
+ <p>
+ Although the focus of ITS 2.0, and some of the usage scenarios addressed in <loc href="http://www.w3.org/International/multilingualweb/lt/wiki/Use_cases_-_high_level_summary#ITS_2.0_Metadata:_Work-In-Context_Showcase">ITS 2.0 High-level Usage Scenarios</loc>) is on “single engine” environments, ITS 2.0 - for example in the context of the <ref target="#domain">Domain</ref> data category - can accommodate "workflow/multi engine" scenarios.</p>
+<p>Example:</p>
+<list type="unordered">
+
+<item><p>A scenario involves Machine Translation (MT) engines A and B. The domain labels used by engine A follow the naming scheme A_123, the one for engine B follow the naming scheme B_456.</p></item>
+<item><p>A <att>domainMapping</att> like the following is in place: domainMapping="'sports law' Legal, 'property law' Legal"</p></item>
+<item><p>Engine A maps 'Legal' to A_4711, Engine B maps 'Legal' to B_42.</p></item>
+</list>
+<p>Thus, ITS does not encode a process or workflow (like "Use MT engine A with domain A_4711, and use MT engine B with domain A_42"). Rather, it encodes information that can be used in workflows.</p>
+ </note>
<exemplum xml:id="EX-domain-1">
<head>The <gi>domainRule</gi> element</head>
<p>The <gi>domainRule</gi> element expresses that the content of the HTML
Received on Thursday, 28 February 2013 06:13:06 UTC