One instance of Domain Communication Knowledge in Technical Orders is
the structure of Required Conditions and Follow-on
Maintenance. Required Conditions occurs at the very beginning
of 
and includes all the conditions that have to hold before
or one of its subprocedures executes; Follow-on
Maintenance occurs at the very end of 
and includes all
the follow-on maintenance actions, even if they concern only one of
's subprocedures.
Clearly, the way these conditions are expressed does not belong to
general communication knowledge, that concerns the macro structure of
text. Moreover, it does not belong to domain knowledge
either. Consider Required Conditions. In our process
representation, conditions that affect different transitions, or
different nets, are associated with the corresponding transition or
net. Note in fact that it is wrong to associate all the conditions
belonging to Required Conditions with the global 
, as
some of these conditions are mutually exclusive, namely, they can't
hold at the same time. In the example on page 
,
one of the conditions that applies to
Removal and Installation ( Aircraft defueled) clearly can't be
true simultaneously with one of the conditions relative to Checkout
( Aircraft fueled to approximately 2500 pounds). Thus, the
discourse planner will have to collect the appropriate conditions from
the process representation and group them in the same portion of
the text; this is analogous to, in [KKR91] example of
marine weather reports, rendering the dangerous weather
conditions as warnings that all appear at the beginning of the
report.