I’m glad the minutes for the 21st March meeting were found; I’ll copy and paste them below since I want to comment on them.
I remember the discussion on item #1 a little differently; after discussing the IBM specialization and hearing people comment that it addressed 95% of most use cases, we started talking about the following possible changes to the task information type:
· A troubleshooting element that could be used within a <step> element
· A troubleshooting section that would be be parallel to <context>, <steps>, <postreq>
Are we back to discussing whether to advocate a new troubleshooting topic type, or simply exploring the HP model?
If the IBM specialization is too specific, is it worth considering writing a constraint to simplify it? (I really just don’t want us to create new info types if we can use or constrain existing ones.)
Also, two embedded actions items in the minutes:
1. Gershon to discuss the troubleshooting elements in Cisco's task model specialization.
2. Someone (JoAnn?) to send reference for Hans van der Meij's article on troubleshooting
Should we try and gather information about what other companies are doing vis-à-vis troubleshooting?
Best regards,
Kris
Kristen James Eberlein l DITA Architect and Technical Specialist l SDL Structured Content Technologies Division l (t) + 1 (919) 682-2290 l keberlein@sdl.com
Please consider the environment before printing this e-mail
Minutes for DITA Technical Communication Subcommittee meeting
21 March 2011, 11 am to 12 noon ET
Roll call 11:00 - Quorum
Attending: Kristen James Eberlein, PaulG, Mariana Alupului, JoAnn Hackos, Rob Hanna, Bruce Nevin, Gershon Joseph,
Regrets
Next meeting: 18 April 2011, 11:00am to 12:00pm ET
Approved Minutes:
7 March 2011. JoAnn moved, Rob seconded
Brief review of Open Action items
Business
1. ITEM -- Troubleshooting specialization. Troubleshooting information type.
Discussion: perhaps the current IBM specialization is too specific. could be looser. BizDocs SC
also has several ideas of a new design.
JoAnn can provide an illustration of the HP model
Gershon will discuss the troubleshooting elements in Cisco's task model specialization.
Send reference for Hans van der Meij's article on troubleshooting--explains value of labeling the
"trouble" information.
Rob interested in the questions of criticality and frequency.
RelTable for Troubleshooting links
Possible proposal for the DITA 1.3 specification
Kris--any objections to new elements in task. Good examples in spec/supporting article
Gershon -- TS use cases on April 4
Action --set up a wiki page for the use cases
2. ITEM: Release Management -- JoAnn provide link to the release management webinar
Gershon -- add change control wiki
add use cases on change control
Adjourn 12:00 noon ET.
To: DITA Tech Comm SC (dita-techcomm@lists.oasis-open.org)
Subject: [dita-techcomm] Minutes of the 21 March 2011 meeting
JoAnn T. Hackos, PhD
President
Comtech Services Inc.
710 Kipling Street, Suite 400
Denver, CO 80215
joann.hackos@comtech-serv.com
skype joannhackos
