| Syntax 
   marked-section include-start condtion?
     action*
 Purpose
 
 Unlike most marked section rules, include rules are split into two sets of rules:  marked-section include-startrules andmarked-section include-endrules. This is because an include-marked section can start in the context of one element and end in the context of another ("merging" the specifications), and so can overlap the structure that ties the components of a parsed SGML document together. To avoid the complications that could result from trying to "merge" the specifications for the rules for include-marked sections with the applicableelementanddata-content, the include rules apply only to the start and end of the marked section. Clearly, marked-section include-startapplies to the start of the marked section. If no marked-section include-startrule is performed at the start of an include-marked section, then the starting markup is ignored by the OmniMark program (though not by the SGML parser).Only one marked-section include-startrule may be selected for each marked section. If more than one rule applies, then each must have a condition. It is an error for more than onemarked-section include-startrule to be selected for an include-marked section.The marked-section include-startrule is applied when the[at the end of the header of the marked section is encountered. Any comment in the header of the marked section is processed prior to the processing of themarked-section include-startrule.Only marked sections in the document are available for processing by an OmniMark program. Marked sections in the DTD are always ignored, whether or not there is a marked-sectionrule in the OmniMark program.Neither the %coperator nor thesuppressaction can be used in amarked-section include-endrule.
 The following is an example of a marked-section include-startrule:
   marked-section include-start
     do when element is (p | title)
        output " (Start of bracketed text)"
     else
        output "(Start of bracketed text)%n"
     done
 |