Index: /reasoner/consTranslation.tex
===================================================================
--- /reasoner/consTranslation.tex	(revision 214)
+++ /reasoner/consTranslation.tex	(revision 215)
@@ -450,12 +450,14 @@
 \subsection{Annotations}\label{sectAnnotationDefaults}
 
-IVML annotations are orthogonal typed variables that can be attached to a variable. However, annotations cannot be further annotated~\cite{IVML-LS}. Reasoning must consider two cases, namely the creation of assignment constraints for annotation default values (not directly handled by Algorithm \ref{algTranslateDeclaration}) and the translation of annotation assignments (except for nested constraints handled for top-level by Algorithms \ref{algTranslateConstraints} line \ref{algTranslateConstraintsTopLevelAnnotationConstraints} and for compounds by Algorithm \ref{algTranslateCompoundContent}, line \ref{algTranslateCompoundDeclarationAll}). The related transformation patterns are:
+IVML annotations are orthogonal typed variables that can be attached to a variable. According to~\cite{IVML-LS}, annotations cannot be annotated. In most cases, access to annotations is qualified through the underlying variable, i.e., the constraint contains some sub-expression \IVML{v.a} denoting annotation \IVML{a} of variable \IVML{v}. However, the constraint translation must consider two specific cases arising due to implicit qualification of annotations illustrated below:
 
 \grayPara{
-   \patternDerivation{\IVML{annotate } a = deflt \IVML{ to } *\IVML{;} T \text{ } v\IVML{;}}{access(v.a) = deflt}
-   \patternDerivation{\IVML{assign (} a = deflt \IVML{) to \{} T~v\IVML{;} \IVML{ assign} \ldots \IVML{\}}}{access(v.a) = deflt \ldots}
+   \patternDerivationLabel{\IVML{annotate } a = deflt \IVML{ to } *\IVML{;} T \text{ } v\IVML{;}}{access(v.a) = deflt}{fAnnotDeflt}
+   \patternDerivationLabel{\IVML{assign (} a = deflt \IVML{) to \{} T~v\IVML{;} \IVML{ assign} \ldots \IVML{\}}}{access(v.a) = deflt \ldots}{fAnnotAssngBlock}
 }
 
-The first transformation pattern for annotation default value expressions was already introduced in Section \ref{sectTranslationDeclarationTypesDefaults}, but deferred to this section. There, Algorithm \ref{algTranslateDeclaration} implements the generic instantiation of default value expressions and calls for the currently processed variable $v$ the algorithms in this section, which in turn call Algorithm \ref{algTranslateDeclaration} for the annotations of $v$ with annotation-specific accessor expressions. The second pattern targets annotation assignments. An annotation assignment is syntactic sugar for assigning the same annotation value (usually differs from the default value of the annotation declaration) at once to a set of decision variables. Annotation assignments can be nested to indicate orthogonal sets of variables that are annotated with the same (combination of multiple annotations and their) values. To avoid accidental re-assignments, only the innermost value(s) shall ultimatly be assigned to the listed variables and annotations~\cite{IVML-LS}.
+Pattern \ref{fAnnotDeflt} refers to the declaration of annotations with default values, which are instantiated akin to Section \ref{sectTranslation}, i.e., by creating assignment constraints for the (annotation) default values and by substituting the annotation variable by a specific accessor expression. Pattern \ref{fAnnotDeflt} (listed here for completeness) was already discussed as Pattern \ref{forVarDeclAnnotation} in Section \ref{sectTranslation} and the translation was realized as part of Algorithm \ref{algTranslateDeclaration}.
+
+Annotation assignment blocks are specific syntactic sugar to ease the declaration of annotations and their default values. An assignment block specifies the default value (given in the parentheses between \IVML{assign} and \IVML{to} in Pattern \ref{fAnnotAssngBlock}) for all  variables declared within the assignment block. Thus, an assignment block represents a mass-declaration of annotation default values. For more complex situations, annotation assignment blocks can be nested to enable assignment of default values to multiple annotations. To avoid accidental re-assignments, only the innermost nested value(s) shall ultimately be assigned to the listed variables and annotations~\cite{IVML-LS}. As indicated by Pattern \ref{fAnnotAssngBlock}, we translate annotation assignment blocks through the creation of a series of annotation assignment constraints, i.e., for all assigned annotations and all variables declared in the block (and nested blocks)\footnote{As we do not have a 'name' for the assignment block in Pattern \ref{fAnnotAssngBlock}, the '$\ldots$' on the right side indicate the creation of similar constraints for all variables declared in the block and all nested blocks with their respective default expressions.}. 
 
 \begin{algorithm}[H]