Difference between revisions of "Cross Model"
Jump to navigation
Jump to search
(Default pattern example added) |
(→Cross Model: : default cross action explained (use of symbols and variables)) |
||
Line 3: | Line 3: | ||
== Cross Model == |
== Cross Model == |
||
=== Default cross action === |
|||
By default, the <code>apertium-crossdics</code> tool uses a simple cross model (<code>schemas/cross-model.xml</code>) defining only a default pattern-action rule. |
By default, the <code>apertium-crossdics</code> tool uses a simple cross model (<code>schemas/cross-model.xml</code>) defining only a default pattern-action rule. |
||
Line 35: | Line 36: | ||
</cross-model> |
</cross-model> |
||
In the example above: |
|||
* <code>$cat</code> is a variable that can store just one element (for example, <code><s n="adj"/></code>). In this example we use a variable because we need to use the value in the <code>action</code> element. Besides that, we force the value of the first <code><s n="..."/></code> element to be the same. There is another symbol (<code>?</code>) that can be used if we don't want to use the value afterwards. |
|||
* the symbol <code>*</code> is a sequence of 0 or more <code><s n="..."/></code> elements. |
|||
* <code>@tailA</code> and <code>@tailC</code> are also sequences of 0 or more <code><s n="..."/></code> elements, but, in this particular case, we store the value in a variable because we need to use it afterwards (in the <code>action</code> element). |
|||
How to use these symbols (<code>?</code>,<code>*</code>) and variables (<code>$</code>, <code>@</code>) will be explained in a new section. |
|||
More specific cross actions might be needed in order to cross certain language pairs correctly. Defining a new '''cross schema''' with concrete '''pattern-action''' elements solves this problem. |
|||
These patterns and actions are described in XML, as follows: |
These patterns and actions are described in XML, as follows: |
Revision as of 09:32, 8 February 2008
- Main article: Crossdics
Contents
Cross Model
Default cross action
By default, the apertium-crossdics
tool uses a simple cross model (schemas/cross-model.xml
) defining only a default pattern-action rule.
<cross-model> <cross-action id="default" a="ebenimeli"> <description>Default pattern</description> <pattern> <e> $lt;p> <l>$lemmaA</l> <r>$lemmaB</r>
</e> <e> $lt;p> <l>$lemmaB</l> <r>$lemmaC</r>
</e> </pattern> <action-set> <action> <e> $lt;p> <l>$lemmaA</l> <r>$lemmaC</r>
</e> </action> </action-set> </cross-action> </cross-model>
In the example above:
$cat
is a variable that can store just one element (for example,
). In this example we use a variable because we need to use the value in theaction
element. Besides that, we force the value of the first
element to be the same. There is another symbol (?
) that can be used if we don't want to use the value afterwards.- the symbol
*
is a sequence of 0 or more
elements. @tailA
and@tailC
are also sequences of 0 or more
elements, but, in this particular case, we store the value in a variable because we need to use it afterwards (in theaction
element).
How to use these symbols (?
,*
) and variables ($
, @
) will be explained in a new section.
More specific cross actions might be needed in order to cross certain language pairs correctly. Defining a new cross schema with concrete pattern-action elements solves this problem.
These patterns and actions are described in XML, as follows:
<!DOCTYPE cross-model SYSTEM "crossmodel.dtd"> <cross-model> <cross-action id="pattern-1" a="author"> <pattern>...</pattern> <action-set>...</action-set> </cross-action> ... <cross-action id="pattern-n" a="author"> <pattern>...</pattern> <action-set>...</action-set> </cross-action> </cross-model>
Click on each element in the schema above or read more about cross model elements.
Example of pattern-action
Pattern
<cross-action id="pattern-1" a="ebenimeli"> <description>Pattern 1</description> <pattern> <e> <p> <l>$lemmaA</l> <r>$lemmaB</r>
</e> <e r="RL"> <p> <l>$lemmaB</l> <r>$lemmaC</r>
</e> </pattern> <action-set> <action> <e> <p> <l>$lemmaA</l> <r>$lemmaC</r>
</e> </action> </action-set> </cross-action>
Example of how this cross action could be applied.
See also
External links
- Full example of cross model.
- Cross model DTD