igniterealtime / pade

Pàdé (Yoruba word for Meet) is a browser extension (Chrome/Edge) based unified communications desktop client for Openfire.
https://igniterealtime.github.io/pade/
Apache License 2.0
104 stars 46 forks source link

Add support for H5P content in converse.js #29

Open deleolajide opened 6 years ago

deleolajide commented 6 years ago

Use the h5p standalone renderer to implement an H5P renderer for converse.js. Intercept xAPI "completed" events and post a message back into conversaion with conversation participant's score.

deleolajide commented 6 years ago

This requires ofchat 0.9.3 Release 8

h5p_converse2

Pade is used to upload h5p files. The webmeet plugin for converse.js is used to render H5P in converse.js conversations. The Experience Learning events (xAPI) from content interaction are intecepted and injected back into the conversation.

I am now thinking an XEP might be needed to formalise how to publish/subscribe xAPI events for viewing in a dashboard like the xAPI dashboard from ADL

marclaporte commented 6 years ago

Fantastic!!

https://h5p.org brings a large number of functionality in one integration!

deleolajide commented 6 years ago

In practice, interactive content is authored in Tiki and then uploaded to Openfire to be rendered in converse.js. The xAPI experience events are published to Openfire with XMPP pubsub and can be consumed by any other XMPP endpoint for monitoring, reporting, visualization, etc

@marclaporte, are you interested in co-authoring an XEP for the publishing/subscribing of H5P experience events (xAPI) using XMPP?

marclaporte commented 6 years ago

Yes! Great idea!

falcon-git commented 6 years ago

Hi!

I am the founder of H5P. I think this is a great idea. Count me in!

Svein-Tore

deleolajide commented 6 years ago

Thank you @marclaporte and @falcon-git for becoming co-authors. The process we have to follow is documented here . I will try and get a draft started as soon as possible.

deleolajide commented 5 years ago

Sorry, it has taken a while to get back to this. We actually do not need to publish a new XEP as the following existing XEPs achieve what we need

xAPI statements (JSON) will be wrapped in XMPP using XEP-0335 and sent to the PEP node of the user who published the H5P interactive content.

marclaporte commented 5 years ago

All right! XMPP is amazing!