Re: [dita] Issues noticed with taskbody content model in various task types

[Kristen James Eberlein <kris@eberleinconsulting.com>]

The troubleshooting topic is fine; however, the machinery task topic does NOT contain <tasktroubleshooting>.


Best,
Kris

Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)

On 7/2/2016 8:26 PM, Joann Hackos wrote:

Obviously we have to fix he troubleshooting topic because task troubleshooting is crucial to the design. We were unaware that we had to update the machine industry task to get this to work. Do you want to work with Bob and me to get the fixes in place?

JoAnn

Sent from my iPad

JoAnn Hackos

President

Comtech Services Inc

710 Kipling Street Suite 400

Lakewood CO 80215

303-232-7586

 

Join The Center for Information-Development Management at the Content Management Strategies/DITA North America Conference on April 4-6, 2016. More information at:https://cm-strategies.com

On Jul 2, 2016, at 4:49 AM, Robert D Anderson <robander@us.ibm.com> wrote:

I noticed an oddity with taskbody when reviewing the generated content model tables.

Specifically, it does not allow the new <tasktroubleshooting> element, because the machinery taskbody constraint was not updated to account for it. I assume this was an oversight in 1.3 (probably related to the fact that the original owners of the Machinery Task are no longer participating at the TC).

This led to a few discoveries in the text:

• There is a normative concept topic about the machinery task that specifically describes the contents - also missing the element. This means both our grammar files and our normative text do not allow for the element.
  http://docs.oasis-open.org/dita/dita/v1.3/os/part2-tech-content/archSpec/technicalContent/dita-machinerytask-topic.html
• In the same topic, the element <prelreqs> does not use the new XML mention domain. This should be fixed in the errata. I am very happy to say this is the first instance I've seen where markup made it into the final spec without using that domain.
• There is a similar concept describing general task, which mentions every section in the general task. It does not list tasktroubleshooting. In this case, the grammar files that allow the element are normative, so I think this is clearly an errata item - the concept should be updated to list the element.
  http://docs.oasis-open.org/dita/dita/v1.3/os/part2-tech-content/archSpec/technicalContent/dita-generic-task-topic.html
• The same issue exists in the concept for strict task, which lays out the sections that can be used, in order. As with the general task, this looks like an errata item - the concept should be updated to list the element.
  http://docs.oasis-open.org/dita/dita/v1.3/os/part2-tech-content/archSpec/technicalContent/dita-task-topic.html
  

  Regards, Robert D. Anderson DITA-OT lead and Co-editor DITA 1.3 specification, Digital Services Group	<ecblank.gif>
  E-mail: robander@us.ibm.com Digital Services Group	<0C170704.gif>
  11501 BURNET RD,, TX, 78758-3400, AUSTIN, USA