[GH Request] Add xAPI activity to adlnet openedx profile

[felipemontoya]

Firm Name

edunext

Urgency

Low (2 weeks)

Problem/Request

Please add the custom activity used by openedx-ai-extensions to the openedx profile at adlnet

Reasoning

In openedx-ai-framework, we are sending xAPI events with a custom activity and some custom extensions.

XAPI_ACTIVITY_AI_WORKFLOW = "https://w3id.org/xapi/openedx/activity/ai-workflow"

As per @bmtcril:

Normally this would be a thing that we would want to add to the openedx profile at adlnet before using it, but unfortunately the profile server has been down for quite a while and so may be defunct. It doesn't hurt anything in the usage, but allows people to find the definitions of the extensions and understand how to use them.

openedx/openedx-ai-extensions#24 (comment)

[github-actions]

Thank you for your report! @openedx/axim-oncall will triage within a business day. Simple requests usually take 2-3 business days to resolve; more complex requests could take longer.

[bmtcril]

As of now it seems that the xAPI 1 profile server is defunct, it's been unresponsive for at least the last two weeks. This is likely due to the handoff of xAPI governance from ADL to the IEEE, who are working on the v2 spec. It seems like going forward we will want to host our own profile that describes the OeX / event-routing-backends use of xAPI. I'll be reviewing the IEEE docs over vacation and will hopefully have some recommendations when I get back. Specifically I'll be reviewing these area:

• New top level xAPI page: https://xapi.ieee-saopen.org
• New base standard docs: https://opensource.ieee.org/xapi/xapi-base-standard-documentation/-/blob/main/9274.1.1%20xAPI%20Base%20Standard%20Overview.md?ref_type=heads
• New profile docs: https://opensource.ieee.org/ltsc/xapi-profiles-staging/-/blob/main/xapi-profiles-about.md#part-one

[bmtcril]

Hi @felipemontoya, I'm going to close this since it's currently impossible. I've opened an issue in event-routing-backends and put on the Data WG board to capture (what I think is) the work to move us to xAPI 2.0 when profiles become usable. It's a big move with questionable value for us right now, so I wouldn't expect movement on it unless / until there is proven adoption of the new standard or someone in the community wants to push it forward.

openedx/event-routing-backends#537