Index: /reasoner/consTranslation.tex
===================================================================
--- /reasoner/consTranslation.tex	(revision 157)
+++ /reasoner/consTranslation.tex	(revision 158)
@@ -476,5 +476,5 @@
 \subsection{Constraint variables}\label{sectConstraintVariables}
 
-In IVML, the type \IVML{Constraint} exists, which allows defining variables, compound slots or containers of constraints. As for usual variables, the value of such a constraint variable can change unless frozen, i.e., the configuration process can influence the actual set of constraints to be checked on an IVML model. The important difference in translating 
+In IVML, the type \IVML{Constraint} allows defining variables that contain a constraint. The value of such a variable shall be considered during reasoning as an usual constraint. As for other variables, the value of such a constraint variable can be changed unless it is frozen, i.e., the configuration process can influence the actual set of constraints to be checked on an IVML model. If the value of a constraint variable changes during reasoning, the reasoner must adjust the constraint base accordingly, i.e., the old constraint must be disabled and the new one enabled (cf. Section \ref{sectTopLevelConstraintsRescheduling}).
 
 There are four basic translation patterns, three are shown below. The basic idea is to translate the (default) value, a constraint expression, directly into a constraint performing appropriate variable substitutions. For constraint containers, we translate the element values, which represent constraint expressions. If either pattern is nested within a compound (not shown for constraint containers below), the translation substitution must particularly replace \IVML{self} by the actual compound variable.