The problem with the conventional curnits for ucwise is the lack of a well defined containment boundary like Project-Activity-Step. Curnits make sense for PAS because a user wants to download a project at a time. For ucwise, users only want to download material relevant for that lab day. There is no predefined 'project' that a user can download.
My plan is to have very small curnits that only describes a small part of a LearnerNode hierarchy. For example, there may be curnits that hold single steps, or a larger curnit for holds several related steps. When our VLE needs a LearnerNode hierarchy, it will query our metadata service to figure out a set of curnits to download and piece them together. Comments or suggestions? -jerry --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SAIL-Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/SAIL-Dev?hl=en -~----------~----~----~----~------~----~------~--~---
