RE: [dita] Revised content model options for #12011 - Generic Task Type

From
Michael Priestley <>
Date
2008-11-12T18:01:17+00:00
ID
Thread
RE: [dita] Revised content model options for #12011 - Generic Task Type
Hi JoAnn,

The rationale below is to allow <ol>
and <ul> into taskbody. In other words, if someone wants to create
a task with a simple <ol> instead of the more prescriptive <steps>,
the <process> element allows them to do so.

Michael Priestley, Senior Technical
Staff Member (STSM)

Lead IBM DITA Architect 



http://dita.xml.org/blog/25

"JoAnn Hackos"
<> 

11/12/2008 12:06 PM

To

Michael Priestley/Toronto/IBM@IBMCA,
<>

cc

Subject

RE: [dita] Revised content model options
for #12011 - Generic Task Type

Hi Michael,

The email from Alan provides
no rationale for the <process>, just shows the syntax. Let me know
if any of the minutes show the rationale or any examples. I’ve written
Alan but haven’t received a response as yet.

 

JoAnn

 

JoAnn Hackos PhD

President

Comtech Services,
Inc.



Skype joannhackos

 

From: Michael Priestley [mailto:]

Sent: Tuesday, November 11, 2008 9:22 AM

To: 

Subject: Fw: [dita] Revised content model options for #12011 - Generic
Task Type

 

Re discussion today about elements in general task - found this, which
provides a bit of background on process - will check meeting minutes from
around this time. 

Michael Priestley, Senior Technical Staff Member (STSM)

Lead IBM DITA Architect 



http://dita.xml.org/blog/25

----- Forwarded by Michael Priestley/Toronto/IBM on 11/11/2008 11:21 AM
----- 

Alan Houser <>

12/11/2007 11:01 AM

To



cc

 

Subject

[dita] Revised content model options
for #12011 - Generic Task Type

 

 
 

I submit this message for possible discussion at today's 

(11-December-2007) DITA TC meeting. Below is a summary of proposed 

content models that will support proposal #12011 -- Generic Task Type.

These content models are the result of recent discussion on the DITA TC

list.

-Alan

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

Summary:

- Optional, repeatable <note> allowed before <cmd>

- <taskbody> allows only a single <steps> element

- New <process> element to permit <ol>/<ul> constructions
in <taskbody>

Proposed content models:

taskbody:

(prereq?,

context?,

(steps | steps-unordered | process),

result?,

example?,

postreq?)

(Issue: allow <section> before and after <steps>?)

steps/steps-unordered:

Support <section> between steps:

(section?, step)+

step:

Support optional, repeatable <note> before cmd:

(note*,

cmd,

(info | substeps | tutorialinfo | stepxmp |  choicetable | choices)*,

stepresult?)

Issue: allow <itemgroup> in <step>?

process:

(section?, (ol | ul))+

Issue: this would allow multiple ol/ul elements.

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

To unsubscribe from this mail list, you must leave the OASIS TC that

generates this mail.  You may a link to this group and all your TCs
in OASIS

at:

https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php