Content model options for #12011 - Generic Task Type

[Alan Houser <arh@groupwellesley.com>]

I submit this message for possible discussion at today's (27-Nov-2007) DITA TC meeting.

I've included a couple of content model options for <step>, <steps>, and <taskbody> below (intentionally presented in that order). I believe each option can be restricted to emulate the current content models.

Thanks to Deborah Pickett, Erik Hennum, Robert Anderson, Michael Priestley, and Chris Kravogel for their contributions to this discussion.

-Alan

------------

<step>
Current content model:
(cmd, (info | substeps | tutorialinfo | stepxmp | choicetable | choices)*, stepresult?)

Option 1: Add support for pre-cmd admonishments, optional <cmd>:
(note*, cmd?, (info | substeps | tutorialinfo | stepxmp |  choicetable | choices)*, stepresult?)

Option 2: Add support for specializable <itemgroup>, optional <cmd>:
(note*, cmd?, (info | substeps | tutorialinfo | stepxmp | choicetable | choices | itemgroup)*, stepresult?)

<steps>
Current content model: (step+)

Option: Add support for pre-procedure <discussion>
(discussion?, step+)

<taskbody>
Current content model:
(prereq, context, (steps | steps-unordered), result, example, postreq)

Option 1: Support generic lists, multiple <steps>, multiple <example>
(prereq, context, (steps | steps-unordered | ol | ul)*, result, example*, postreq)

Option 2: Support generic lists, multiple <section> before <steps>
(prereq | context | section)*, (steps | steps-unordered | ol | ul)*, (result | example | postreq)*

Option 3: Support multiple <steps>, multiple <section> in
any order and number. Punt on constraining order of elements in DTD.
(prereq | context | steps | steps-unordered | ol | ul | result | example | postreq | section)*