29882 2016-09-29 14:46:45 +0000 [SER31] Definition of HTML element 2016-10-14 13:28:31 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Serialization 3.1 Candidate Recommendation PC Windows NT RESOLVED FIXED P2 editorial --- 1 tim cmsmcq andrew_coleman mike public-qt-comments oldest_to_newest 127601 0 tim 2016-09-29 14:46:45 +0000 The square brackets delimiting the definition of an HTML element are a bit odd. [Definition: An element node is recognized as an HTML element by the XHTML output method if] 127602 1 mike 2016-09-29 15:11:41 +0000 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. 127605 2 tim 2016-09-29 15:20:53 +0000 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] 127791 3 andrew_coleman 2016-10-14 13:28:31 +0000 Fixed this in three places. Thanks