>> I've chosen an inline-level content model because it allows not only >> img, but also structured inline-level elements like pre. I'm not so >> sure about that choice however. > > Hm, <pre> seems like an interesting thing to put in a <figure>[...] I > certainly could see us also allowing <figure> to label <pre><samp> and > <pre><code>.
This seems like a potentially very natural way to convert RFC2629bis' <figure> & <artwork> elements into HTML5. Ted -- Edward O'Connor [EMAIL PROTECTED] Ense petit placidam sub libertate quietem.
