Hi, Bruce:
The intent of the DITA 1.2 constraints enhancement is to make it possible for adopters to implement simplifications like block-only content within sections and list items without forcing specialization or breaking backward compatibility.
Hoping that's interesting,
Erik Hennum
"Bruce Nevin (bnevin)" <> wrote on 06/10/2008 09:22:21 AM:
>
> RE: [dita] Proposal for Consideration: Default Behavior for List Items
>
> The real issue IMO is that <li> permits #PCDATA and phrase-level
> elements. These should only be permitted in paragraph-level
> elements, and any element that permits paragraph-level or "larger"
> elements as children should not permit #PCDATA and phrase-level
> elements. This behavior seems to be a relic of the HTML standard.
>
> It is easy for OT and vendors to insert <p> by default, and if <li>
> begins with some other child element it is only a minor nuisance to
> delete <p> or insert that child ahead of <p>.
>
> This would simplify the work of rendering and remove the ambivalence
> that is the topic of this thread.
