This specification describes interoperable runtime communication between Conference website and LRS.
The scope of this specification is limited to the following:
- Launch content by an conference website
- Launch and runtime environment used by conference website
- Reporting requirements for the conference website.
This specification references how to use the xAPI specification within this scope.
For purposes of this specification, the following terms and definitions apply:
- Assignable Unit (AU): A learning content presentation launched from an conference website. The AU is the unit of tracking and management. The AU collects data on the learner and sends it to the LMS.
- Experience API (xAPI): A runtime data communication specification for learning content (AU) to send and receive data to a Learning Record Store (LRS). The xAPI specification referenced by this document is used to define the data transport and the data model.
- Internationalized Resource Identifier (IRI): A unique identifier according to RFC 3987. The IRI may be an IRL. IRLs SHOULD be defined within a domain controlled by the person creating the IRL. Note that IRI’s in this spec MUST be fully qualified and not IRI References.
- Learning Records Store (LRS): As defined in the xAPI specification.
- Registration: An sign up instance of a learner in a conference website. (a registration ID uniquely identifies this).
- Session: A period of time marked by the user login until its termination (or abandonment).
Conformance to this specification is defined in this section.
In this specification:
- "MUST" is to be interpreted as a requirement on an implementation.
- "MUST NOT" is to be interpreted as a prohibition.
- "SHOULD" is to be interpreted as a recommendation for implementation.
- "SHOULD NOT" is to be interpreted as the converse of "SHOULD".
- "MAY" is to be interpreted as a course of action that is permissible within the limits of the specification.
- "NEED NOT" is to be interpreted as a course of action that is not required.
AU Requirements. An Assignable Unit MUST conform to all requirements as specified in the xAPI specification.
Conference Website. The Conference Website MUST conform to all LRS requirements as specified in the xAPI specification.
The Conference Website MUST have an account which is able to retrieve all Resource data about another distinct user across multiple sessions for that user.
Synopsis of the Conference profile model:
- An Conference website include content, which may contain one or more AUs.
- A learner authenticates with an conference website.
- A learner launches an AU from the conference webisteusing an interface.
- The conference website writes launch data to the integrated LRS.
- The user views the AU content and performs the learning. During this time, the AU MAY request data from, and store data to, the website.
- The learner exits the AU.
Responsibilities of the Assignable Unit:
- Parse the parameters from the launching environment to determine where the website location is and initiate communication with the website.
- Format all data according to the defined data types and vocabularies that are defined in this specification.
- Send a "terminate" statement prior to terminating the AU's execution.
Responsibilities of the website:
- Create and maintain content structures.
- Format all data according to the defined data types and vocabularies that are defined in this specification.
- Launch the specified AU contained in the courses within the defined environment(s).
Each statement has unique statement id
The Actor property must be defined as per the xAPI Specification.
When user logged in to conference website it has unique user id, this id should be proceed as Actor in the statement
One of these is required for every page.
“Required” Verb
Every time a page is “launched” from website verb launched must be sent to the xAPI Learning Record Store (LRS).
- Initialized - Indicates the actor logged in to the conference website.
- Launched - Indicates that the actor open page.
- Attended – indicates the actor click on presentation link
- Commented – Indicate the actor commented any content - click on send comment button. Result reponse is comment text
- Rated – Used to rate presentation, result is in range (1,5).
Video
- Initialized
An "Initialized" statement is used to indicate that the video has been fully initialized or launched.
- Played
Used when the actor generally played a video or clicked the play button.
- Paused
Indicates that the actor temporary or permanently stopped experiencing the recorded media object.
- Seeked
Used in combination with time-from and time-to extensions when the Actor moves the progress bar forward or backward to a specific time in the video.
Id: https://w3id.org/xapi/video/verbs/seeked - Interacted
Used to express that the actor interacted with the player (except play, pause, seek). e.g. mute, unmute, change resolution, change player size, etc.
Id: http://adlnet.gov/expapi/verbs/interacted
- Completed
Used to express that the actor completed a video by watching all parts of the video at least once.
Id: http://adlnet.gov/expapi/verbs/completed
- Terminated
Used to express that the actor ended a video.
Id: http://adlnet.gov/expapi/verbs/terminated
An Object with objectType "Activity" MUST be present, as specified in the xAPI Spec.
The Object represents the page, presentation, video, comment consumed by the Actor.
Object definition MAY contain name, description and other details of the media, as per the xAPI Spec.
Only commented and rated verbs have object result parts: for commented text of the comment is stored in the response and for the rated score is stored in the score raw.