xAPI URIs
URL/URI Best Practices in xAPI Statements
Understanding Activity IDs
When creating xAPI statements, you'll encounter two types of URLs:
Standard xAPI Verbs: These are predefined by ADL (Advanced Distributed Learning) and should be used as-is:
Activity IDs: These are URIs you create to identify your activities:
Best Practices for Activity IDs
1. Structure
Use a consistent URI pattern
Include meaningful path segments
Keep IDs human-readable when possible
2. Documentation
Best practice is to make these URIs resolvable to actual documentation. For example:
If the URI is resolvable, it should lead to:
Activity description
Expected outcomes
Related skills or competencies
Usage context
Any other relevant metadata
3. Persistence
Once you define an activity ID, maintain it
Create new IDs for new versions of activities
Don't reuse IDs for different activities
4. Domain Usage
You can use:
A domain you control (preferred)
A made-up domain (acceptable)
A subdomain specific to xAPI activities
The key is consistency and uniqueness within your system, but making URIs resolvable to actual documentation is strongly recommended for better interoperability and clarity.
Remember: While non-resolvable URIs are technically valid, resolvable URLs that link to activity definitions make your xAPI implementation more maintainable and useful to others who might need to understand your learning activities.
Last updated
Was this helpful?