Enabling Consumption of Learning Experiences

[vrayulu]

The discovery and order APIs in the current DSEP/Beckn specifications facilitate the discovery and subscription of learning experiences within the ONEST network. However, the existing fulfilment APIs, in their current state, may not comprehensively support the entire fulfilment process for learning experiences, particularly in terms of enabling consumption and tracking. Here are some critical factors necessary to enable the consumption of learning experiences within the ONEST network:

1. Mode of Learning Experience Playback: Determining how end-users can consume learning experiences (both free and paid) on a BAP app is crucial. There are multiple ways in which BPPs can support this:
   • Remote play: Redirecting users to a URL provided by the BPP.
   • Embedded play: Incorporating a player provided by the BPP within the BAP app.
   • Custom play: Developing a custom player within the BAP app, with the BPP providing the content or stream to be played.

ONEST should establish specifications to define these modes and to share relevant data to facilitate the chosen mode of play.

2. Secure Access to Learning Experiences: Ensuring that only subscribed users can access and consume learning experiences, particularly when they are not free/open. ONEST should provide specifications for BAPs to access learning experiences with valid authentication tokens and for BPPs to verify these tokens.

3. Sharing User Details: BPPs need to identify the users accessing the learning experiences for validation purposes (e.g., verifying user subscriptions) and to track consumption progress. ONEST should define specifications for sharing user details between BAPs and BPPs at various stages of the workflow.

4. Sharing Consumption Telemetry: When learning resources are consumed within the BAP app, it becomes necessary for the BAP to transmit relevant telemetry events to BPPs for tracking purposes. ONEST should outline specifications for the telemetry events to be generated by BAPs and the interfaces to be implemented by BPPs to receive this telemetry data.

These additional factors could be implemented by layering additional specifications on top of the core Beckn protocol used by the ONEST network. Alternatively, if these specifications are deemed valuable across other Beckn networks, they could be incorporated into the DSEP/Beckn framework.

Request the community to contribute their inputs and ideas to enable this workflow within the ONEST network.