Why does Frame add to automatically?

Hello,

During our recent DITA migration, some authors use tools other than FrameMaker and the question of child elements within <li> elements keeps coming up.

Is there a reason why Frame add child <p> tags to the following?

• <li>
• <stepxmp>
• <stepresult>
• <info>

For me, this seems to make sense as it helps to maintain consistent tagging when multiple paragraphs exist in one of these tags. For example:

<ul>

     <li>

          <p>Feature name</p>

          <p>Feature description para 1</p>

          <p>Feature description para 2</p>

     </li>

     <li>

          <p> Feature name</p>

     </li>

</ul>

Personally, I feel that removing the first <p> tag in <li>1 looks inconsistent:

<ul>

     <li>Feature name

          <p>Feature description para 1</p>

          <p>Feature description para 2</p>

     </li>

     <li>Feature name</li>

</ul>

A table <entry> seems a better example, although Frame does not automatically insert a <p>

<row>

     <entry>

          <p> Feature name</p>

     </entry>

     <entry>

          <p>Feature description para 1</p>

          <p>Feature description para 2</p>

     </entry>

</row>

Without the <p> tags, the first paragraph is not wrapped consistently.

<row>

     <entry>Feature name</entry>

     <entry>Feature description para 1

          <p>Feature description para 2</p>

     </entry>

</row>

Are there any best practices or explanations why FrameMaker chose to force <p> elements in some occasions and not others? Are there any best practices as to when a <p> element is required as a child?

Thanks,

Mike