For info, the XSLT spec now does multi-line definitions like this (Note the open="true"):

<p><termdef id="dt-potentially-consuming" term="potentially consuming" open="true">An
   <termref def="dt-operand"/> is <term>potentially
   consuming</term> if at least one of the following conditions
                                 applies:</termdef></p>

                           <olist>
                              <item>
                                 <p>...</p>
                              </item>
                              <item>
                                 <p>....</p>
                              </item>
                           </olist>
<p role="closetermdef"/>

and I think all the DTD and stylesheet support for this is common. It's a bizarre approach but it was designed to minimize the risk of breaking things.

There is a similar problem in

[Definition: An element node is expected to be empty if it is recognized as an HTML element and if either]

Fixed this in three places. Thanks