JoAnn T. Hackos, PhD President Comtech Services Inc. 710 Kipling Street, Suite 400 Denver, CO 80215 joan...@comtech-serv.com skype joannhackos

[Comtech-Logo]

Minutes for DITA Technical Communication Subcommittee meeting 30 April 2012, 11 am to 12 noon ET

Roll call 11:00 - Quorum

Attending: Tom Cihak, Rob Hanna, Sue Blaisdel, Jane Credlund, JoAnn Hackos, Bob
Thomas, Craiz Zieg, Kris Eberlein, Seth Park

Regrets: Dave Helfinstine

Next 14 May 2012, 11:00am to 12:00pm ET

Business

1. ITEM: Troubleshooting Note--

Recommendation that Open Toolkit provide generated text for the note type. Rob H moved and Jane C seconded to report this recommendation to the DITA TC

Kris -- reminded us to explain when each of the options for troubleshooting is
to be used

2. ITEM: Release management

Rob H will add information on the <rev> attribute to be used to indicate the
nature of the change -- provide additional flexibility

Seth P -- tech issues -- would be unable to filter content on <rev> if contains
this info. Wants to be able to filter on <rev>

Rob H -- presently no filtering on <rev> but coming with DITA 1.3 most likely

3. ITEM -- Troubleshooting topic

Bob T added steps-unordered. changed remedy to allow block mix to occur after
steps. Need to add to proposal.

Could specialize from this proposal to the IBM troubleshooting specialization.

<section> is intact -- conditi9on, cause,

<remedy> is more constrained because of the intro of steps or steps-unordered.

Seth - idea of cause, condition, and remedy as a domain specialization so could
be easily isolted perhaps more specializable base

Rob H -- bizdocs was loking at <policy> as a similar bse topic type

Bob and Seth agree since same structure is applicable in other areas. core info
type remedication -- remedy -- advisory as possible names

However, this would more to much into the bizdocs overall scheme, which has not
acquired support

Seth <trouble section? base for condition, cause, remedy

Topic type shell -- content model dependency in DITA 1.2

Conclusion seemed to be stay with what Bob has so far

4. ITEM Note question

Bob -- note should get generated text with "trouble"

Rob -- don't get this generated text -- could just use info > note> attribute

<trouble> is more "in you face" -= more than one way to do same thing like
abstract and context already exists in DITA. add specific wording on recommendation in the specification.

Summary: <trouble> in <step> to be used explicitly and as a reminder to writers
with the semantic tag -- should generate a Trouble icon in the OT

<info note="trouble> -- not necessarily generate a trouble icon in the OT

<tasktrouble> -- yes, generate a trouble icon -- explicitly follow-up to a task

Adjourn 12:00 noon ET.