OASIS Open

telecon US Toll-Free 888-426-6840, Participant code 8581755;
other countries, see https://www.teleconference.att.com/servlet/glbAccess?process=1&accessCode=8581755&accessNumber=2158616239

Attendees:

John Hunt

Doug Burgess

Mark Myers

Scott Hudson

Doug put together plugin to test the proposal

Proposal didn't specify what additional map elements would be needed.

Eliot: need to allow mapref to allow case of referencing a map that only contains keydefs. Should probably allow topicgroup as well?

Need to put in documentation that a learningObjectMap is equivalent to one specific learning object. keydefs and references should point to resources that make up the learning object.

Same issue for learningGroupMaps. A learning object group should refere to a group of learning objects.

anchor - not appropriate

anchorref - not appropriate

data - in topicmeta, so fine

data-about -  in topicmeta, so fine

keydef - keep

mapref - keep

navref - keep

topicgroup - keep

topichead - not appropriate. Navigational.

topicref - not appropriate. Navigational.

topicset - not appropriate. Navigational.

topicsetref - not appropriate. Navigational.

after the topic, reltable - keep

Recursion is permissible in the learningGroup within the learningMap. Do we need recursion implemented in the learningGroupMap as well?

YES, it would be appropriate.

Eliot: The DTD should already support it?

Eliot: when including the ditamap, it is pointing to the DITA 1.2 version, not the local version. Change it to 1.3 and it should work!

Doesn't make sense to have navtitles on maprefs.  They would not be rendered.

Doug: added just to keep the XML text human readable. It is for the benefit of the author.

navtitle - keep for authoring, but no rendering expectation

Eliot: should use map title sub-element, not navtitle attribute.

Posted to the DITA list:

This question came up in the discussion of the new learningGroupMapRef and learnhingObjectMapRef elements:

When a mapref has a navigation title, what is the processing implication? I see two options:

1. Like titles of submaps, it's ignored for the purpose of defining the navigation title hierarchy.

2. It applies to the first normal-role topicref descendant of the referenced map.

Recommendation to fix the examples to use the title rather than navtitle.

May need to take a survey of various editors to see how they are handling the navtitle vs map title. Definitely need a note to qualify the examples that the navtitles are there for authoring, not rendering expectation.

Need to get TC to approve Phase 2 proposal so we can go for Phase 3. Need to get on TC meeting calendar to propose this. Should be ready to submit for next Tuesday's meeting. Mark or Doug to submit to the OASIS DITA TC docs area (Drafts folder) and send mail to Don Day and Kristen Eberlein. 

Agenda

1) Review and prepare the Phase 3 proposal for learningObjectMap (#13089)

• Doug Burgess and Eliot Kimber are updating the proposal to add technical implementation details for the dtd/xsd models.
• They will post a review copy in advance of the meeting.
• Goal is to have the proposal ready for review as a Phase 3 proposal by the DITA TC by Tuesday, Oct. 30.
• The current draft is here - https://www.oasis-open.org/apps/org/workgroup/dita-learningspec/download.php/46600/learningObjectMapRef_proposal_v02.pdf

2) Discuss agenda topics for future meeting

• On the last call we had several suggestions for info sharing on use cases and DITA Learning and Training implementations.
• Let's pull together a list of potential topics, and plan meeting agendas for them.
• If you have topics to propose, please send a note to the L&T sub-committee email list at dita-learningspec@lists.oasis-open.org.

Thanks!

John Hunt, IBM

Chair, DITA Learning and Training subcommittee

• OASIS Open (General Membership)
• General Public
• OASIS Darwin Information Typing Architecture (DITA) TC