DITA Learning 29 MAR 2012 minutes
Attendees:
John Hunt
Scott Hudson
Amber Swope
Mark Myers
Eliot Kimber
Troy Klukewich
Minutes:
Robert Anderson to join next week to discuss the “kosher-ness” of the proposed content model.
John attended the TC meeting last week and we now have an official feature proposal (#13106) that will be considered for DITA 1.3 (see http://wiki.oasis-open.org/dita/DITA_1.3_Proposals-triage ). Full proposal:
http://www.oasis-open.org/apps/org/workgroup/dita-learningspec/download.php/45396/proposal-13nnn-learning-new-interaction.html
Would like to get this in draft state by next Thursday for discussion with Robert. Also hope to present the more complete proposal back to the TC in a few weeks.
Q: Why can’t we just add multiple paragraphs to the existing model?
A: We boxed ourselves in by specializing off of fig. It is the specializing of lcQuestion and lcFeedback on p, which cannot be nested.
Use Cases:
Amber to pull example use cases into the proposal.
Benefits:
Mark to review the Benefits section and add any additional info.
Costs:
Q: will there be an impact to the DITA-OT?
A: possibly. should discuss this with Robert Anderson next week
Q: do we need to create new samples and sample processing?
Eliot to create additional samples if needed.
Need to emphasize that this proposal does not replace the existing Learning specialization, but adds an extension/additional support for more complex learning interactions (i.e., multiple paragraphs, etc).
John to revise cost section.
Technical requirements:
Q: what about already existing elements? Can we re-use them, or do we have to duplicate with a “2” in the name.
A: no one prefers adding duplicate.
A: it’s an either/or situation, so if you are in an lcQuestion2, you would only see the lcX2 choices, not see both lcAsset and lcAsset2 (for example).
A: possible backwards compatibility issue if the common elements have to be pulled into a separate domain that each of these reference.
ALL: think about naming of elements and suggest any changes to the list.
GOAL is to have proposal updated or posted to the list by Tues (4/3) so that the draft can be updated by next Thurs (4/5).
|
Meeting - OASIS DITA Learning and Training sub-committee (Conference Call)