DITA Technical Communication SC

Hi folks.   I am very sorry for having to abruptly drop off the call at the bottom of the hour.   Here are the notes I took for the first half. If someone will send me the second half, I’ll upload them to the OASIS site.   Thank you, -seth     Roll Call: see the calendar for official tally     SUMMARY OF ACTIONS   1.Dave Helfensitein to review 13096, 13086, 13098   2.JoAnn to remind M. Priestley that 13097 depends on the ability to reuse "steps" from the task content model, which is one use case for a more generic cross-module reuse feature being considered for 1.3.   3.Seth to set up recurring meeting for SC conference calls in 2013. (done)   4. Seth: reminded to take care of standing action items, namely cleaning up the "change tracking" wiki (move pharma requirements to release mgmt page).   5.Everyone: collect examples of troubleshooting     DISCUSSION TOPIC 1. What to do the rest of the year?   Ideas: * articles, whitepapers, examples on troubleshooting * troubleshooting spec changes     Rob: Create outline for the troubleshooting guidelines articles. (possible webinar opportunity); should answer questions such as when to do "inline" troubleshooting vs standalone topic.   JoAnn: ask Robert Anderson to add "troubleshooting and release management" to the agenda of the April CIDM DITA 1.3 preview.

HI Seth, There is not much to add to your minutes except to get them into the right form and saved as Meeting Minutes Rob Hanna mentioned a new topic as a possible 1.3 proposal. That is: keyref fallback content for variable content using something like the alt title attribute to record fallback content in the case that no key file is included in a map. Came back to a statement that "change tracking is really most important" in terms of DITA requirements. JoAnn JoAnn T. Hackos, PhD President Comtech Services Inc. 710 Kipling Street, Suite 400 Denver, CO 80215 Joann.hackos@comtech-serv.com 303-232-7586 From: Seth Park < R01164@freescale.com > Date: Monday, January 7, 2013 12:23 PM To: DITA Tech Comm SC < dita-techcomm@lists.oasis-open.org > Subject: [dita-techcomm] Notes from Today Hi folks.   I am very sorry for having to abruptly drop off the call at the bottom of the hour.   Here are the notes I took for the first half. If someone will send me the second half, I’ll upload them to the OASIS site.   Thank you, -seth     Roll Call: see the calendar for official tally     SUMMARY OF ACTIONS   1.Dave Helfensitein to review 13096, 13086, 13098   2.JoAnn to remind M. Priestley that 13097 depends on the ability to reuse "steps" from the task content model, which is one use case for a more generic cross-module reuse feature being considered for 1.3.   3.Seth to set up recurring meeting for SC conference calls in 2013. (done)   4. Seth: reminded to take care of standing action items, namely cleaning up the "change tracking" wiki (move pharma requirements to release mgmt page).   5.Everyone: collect examples of troubleshooting     DISCUSSION TOPIC 1. What to do the rest of the year?   Ideas: * articles, whitepapers, examples on troubleshooting * troubleshooting spec changes     Rob: Create outline for the troubleshooting guidelines articles. (possible webinar opportunity); should answer questions such as when to do "inline" troubleshooting vs standalone topic.   JoAnn: ask Robert Anderson to add "troubleshooting and release management" to the agenda of the April CIDM DITA 1.3 preview.

Here is a link to the template for stage 3 proposals: https://www.oasis-open.org/apps/org/workgroup/dita/download.php/46780/latest And here is a link to an example of very simple stage 3 proposal: https://www.oasis-open.org/committees/download.php/46783/13008appid-stage3.html And a link to the master DITA 1.3 Wiki page, from which all of these pages can be accessed: https://wiki.oasis-open.org/dita/DITA%201.3 What you need to keep in mind is that a stage three proposal MUST contain ALL of the new or changed content for the specification, for example: A completed reference topic for each new element All completed concept topics for the architectural spec It also must contain the changes to the DTDs and XSDs. The expectation is that proposal champion or champions will draft the proposal, and then work through revisions with the DITA TC reviewers. At today's call, the following folks volunteered to be reviewers: David Helfinstine Stan Doherty Eliot Kimber Kris Eberlein Let me know if you all have any questions -- I'd be glad to try and answer them Best, Kris Kristen James Eberlein Principal consultant, Eberlein Consulting Co-chair, OASIS DITA Technical Committee Charter member, OASIS DITA Adoption Committee www.eberleinconsulting.com +1 919 682-2290; kriseberlein (skype)