Next in thread → Next in month →

Re: [dita] Should ditabase include troubleshooting?

From
Carlos Evia <>
Date
2015-04-09T16:06:41+00:00
ID
Thread
Re: [dita] Should ditabase include troubleshooting?
Another "yes" vote. In my limited research with the troubleshooting topic (http://www.scriptorium.com/2015/02/taking-dita-troubleshooting-topic-spin/), I was impressed by how easy it was to move new tech authors from troubleshooting to concept, task, and reference. Going from concept, task, and reference to troubleshooting had a more challenging learning curve. Troubleshooting topic needs proper recognition.

Carlos

-- 

Carlos Evia, Ph.D.

Director of Professional and Technical Writing

Associate Professor of Technical Communication

Department of English

Virginia Tech

Blacksburg, VA 24061-0112

(540)200-8201

On Thu, Apr 9, 2015 at 12:00 PM, Hackos, Joann <> wrote:

Absolutely!

Sent from my iPad

JoAnn Hackos

President

Comtech Services Inc

710 Kipling Street Suite 400

Lakewood CO 80215

303-232-7586

 

CIDM will be hosting the Content Management Strategies/DITA North America 2015 conference in Chicago, Illinois April
 20-22. More information at:

http://www.cm-strategies.com/2015/index.htm

On Apr 9, 2015, at 2:29 PM, Helfinstine, David <> wrote:

Greetings,

Adding discussion to a wider audience. I would propose/agree that troubleshooting be included.

Thanks.

-Dave H.

Dave Helfinstine



-----Original Message-----

From: Eliot Kimber [mailto:]

Sent: Wednesday, April 08, 2015 8:01 AM

To: Helfinstine, David

Subject: Re: [dita] Should ditabase include troubleshooting?

The troubleshooting proposal did not specify adding that topic type to ditabase. But it seems reasonable to include it since ditabase includes all the Tech Comm topic types.

Cheers,

E.

—————

Eliot Kimber, Owner

Contrext, LLC

http://contrext.com

On 4/7/15, 4:39 PM, "Helfinstine, David" <> wrote:

Eliot,

There is the new troubleshooting topic type based on topic. Should this

be included in the DITA 1.3 ditabase composite topic type? Is there a

reason it should  or should not?

Thanks.

-Dave H.

Dave Helfinstine

Next in thread → Next in month →