Interfacing with WISE
Turadg Aleahmad is working on a WISE Project -> SAIL Curnit tool chain. WISE doesn't organize data in the manner described above but it can be mapped to it.
Curnit
A WISE project would be a curnit.
CurnitRole
WISE projects and step types know teacher, workgroup and occasionally individual learner. (The last is used only in pre-/post-tests which are technically outside of the project, but a SAIL Curnit could include them in the normal flow.)
Pod
Each step in WISE is supposed to be self-contained wrt/ its learner-generated data. Thus each step maps well to a pod. Most steps hack in some way to reach to other steps. For example, the draw tool records images to a filename that is unique per-project. In this way, a later step can recall the drawing in an earlier step. This could be accomplished via a rim link.
Rims
It would be up to each step type to define the rims that it requires in its podule manifestation. A Display Page step would require no rims. A Notes step would require as many rims as the author defined note items.
Offering
WISE calls these Project Runs, though in WISE they don't permeate through the data storage. Effectively, WISE limits each account to participating in at most one run of any project.
Agent
In WISE, every user has a workgroup for a project. It may be a group of 1 but it's usually 2. Learner work in WISE is stored keyed to this groupID.
In SAIL, this groupID would be an Agent.