Replies: 3 comments 1 reply
-
I was not definitely not aware of this information to be contained in this field. Indeed it makes really sense to track this information in this way. |
Beta Was this translation helpful? Give feedback.
-
Sorry, just reading again my post, I find a small mistake:
I wanted to say "and so a new session id". The registration should stay the same if it is the same planned session. |
Beta Was this translation helpful? Give feedback.
-
For the session ID, why do you choose the CMI5 definition rather than the one defined in the video profile ? |
Beta Was this translation helpful? Give feedback.
-
I would suggest to add a
context.registration
prop to all the templates of this profile.This would be consistent with other well known profiles such as xAPI video profile or CMI5 profile.
And this may be usefull during analytics when you want to group consecutive statements.
But the use of this property may be a bit confusing with some profiles so we should be clear about its meaning.
Let's take a common scenario and define some terms (just for a better understanding):
From my point of view, the
context.registration
prop should identify what I called the SCHEDULED SESSION. This is the session learners have registred to. So the term registration is consistent here.We may add a context extension to identify what I called the TECHNICAL SESSION, which is a number or UUID generated for the
initialized
statement, and which stays the same until theterminated
statement. When the instructor relaunches the virtual classroom, there is a newinitialized
statement, and so a newregistration
.So to summarize these 2 first points, we could have something like this, which is very consistent with the CMI5 profile:
Finally, what I called a COURSE (don't be disturbed by this term) would be identified by an activity in the
object
of the statements (sometimes in thecontextActivities.parent
). Something like:Beta Was this translation helpful? Give feedback.
All reactions