Proposal to Allow learningContentRef to nest: Alternative Solution

[Eliot Kimber <ekimber@reallysi.com>]

The requirement I have is to be able to use a map to create compound
learning content components where the output result is a single artifact,
e.g., a leaf HTML page for SCORM output.

Our original solution was to simpley allow L&T topicrefs to nest themselves
and set the default @chunk value to "to-content".

However, I noticed that the 1.5M17 build does not behave as I expected if
every level in a topicref tree specifies chunk="to-content", in that it
chunks each level separately, rather than only chunking the highest-level
topic.

I have asked on the TC list if this behavior is correct or not, but the fact
that it might be correct suggests that my suggestion to set
chunk="to-content" as a default may not work.

As an alternative, I would like to propose a new topicref type, allowed only
within learningContentRef, called learningContentRefComponent (or something
similar).

The learningContentRef type would still set the default value of chunk to
"to-content" but learningContentRefComponent would not.

This would ensure the correct SCORM result by default while avoiding any
complications from nested specifications of chunk=.

Are there any concerns with this proposal?

Thanks,

Eliot

----
Eliot Kimber | Senior Solutions Architect | Really Strategies, Inc.
email:  ekimber@reallysi.com <mailto:ekimber@reallysi.com>
office: 610.631.6770 | cell: 512.554.9368
2570 Boulevard of the Generals | Suite 213 | Audubon, PA 19403
www.reallysi.com <http://www.reallysi.com>  | http://blog.reallysi.com
<http://blog.reallysi.com> | www.rsuitecms.com <http://www.rsuitecms.com>