INTEGRATE / COMPATIBILITY
Compatibility and migration
Not all capabilities mean the same. This table separates what P2LRN can create, open, read, preserve, and play to avoid promising a more complete migration than each format actually allows.
1. What each column means
The format is part of P2LRN's own model.
Toolkit can produce that content natively.
A package containing that profile can be opened as a project and rebuilt without losing the declared artifact.
Reader can interpret useful structure or content from that format.
P2LRN can transport the artifact even though it cannot fully edit or play it.
The Toolkit declares a complete delivery route for that profile.
For example, an external package can travel intact within P2LRN even though its edition still belongs to another tool.
2. Toolkit Compatibility Matrix
| Profile | Native | Create | Open/rebuild | Read | Preserve | Play |
|---|---|---|---|---|---|---|
| course | Yeah | Yeah | Yeah | Yeah | Yeah | no |
| web-content | Yeah | Yeah | Yeah | Yeah | Yeah | Yeah |
| native-questionnaire | Yeah | Yeah | Yeah | Yeah | Yeah | Yeah |
| native-composite | Yeah | Yeah | Yeah | Yeah | Yeah | Yeah |
| native-component | Yeah | Yeah | Yeah | Yeah | Yeah | Yeah |
| multipart | Yeah | no | Yeah | Yeah | Yeah | Yeah |
| progression | Yeah | Yeah | Yeah | Yeah | Yeah | Yeah |
| SCORM | no | no | Yeah | Yeah | Yeah | no |
| cmi5 | no | no | Yeah | Yeah | Yeah | no |
| Common Cartridge | no | no | Yeah | Yeah | Yeah | no |
| QTI | no | no | Yeah | no | Yeah | no |
| H5P | no | no | Yeah | Yeah | Yeah | no |
| Tin Can package | no | no | Yeah | Yeah | Yeah | no |
| IMS Content Package | no | no | Yeah | Yeah | Yeah | no |
| LTI / CASE / xAPI / accessibility | no | no | Yeah | Yeah | Yeah | no |
3. How to evaluate a migration
- Please check the column you need.If you want to edit, "Keep: yes" is not enough; you need a proper build or rebuild path.
- Test the resulting package.Open a real sample with the viewfinder and check resources, navigation and events.
- Check executable content.SCORM, H5P, cmi5, and other packages may require an isolated execution environment and additional resources.
- Don't assume semantic equivalence.Just because a file can be read or transported does not mean that all rules in the source LMS can be automatically converted.
4. External formats and Player
The Player has the infrastructure to run several external formats, but ultimate capability depends on whether a supported representation is included in the package and the necessary runtime environment is available. That's why the above matrix does not automatically convert "Read" or "Keep" to "Play".
For a specific integration, prepare a test package, open it with the Player and validate the entire journey before migrating content in bulk.
5. P2RLN Alpha15 Packages
P2RLN Alpha15 is a historical identity that predates P2LRN. If you receive such a package, you can repackage it with the current identifiers before continuing to work with it.
p2lrn-repack old-course.p2rln new-course.p2lrn --canonicalize-identifiersAfter converting, validate the new package and test it with Player before replacing the original.
Playback of external formats
Player runs SCORM, H5P, and other supported HTML content in an isolated environment and keeps learner state out of the package when persistence is provided by the integrating platform.
- SCORM 1.2 and SCORM 2004: the runtime offers the documented tracking and persistence APIs; each package should be checked according to the version and extensions it uses.
- H5P: Player can play compatible content using the available libraries. If content requires a non-distributed library, it must be incorporated before publishing it.
- cmi5 and HTML: They can be run in isolation when the package and environment meet the requirements described in the documentation.
- Dependencias externas: Remote services, server code, outdated technologies, or resources that do not travel with the course may require additional configuration or be unavailable.
Final compatibility depends on the specific package, browser, platform security policies, and external services you use. Always validate the actual contents in the target browsers before a deployment.
Release Compatibility
This table summarizes tested usage scenarios with the available version. It serves as an integration reference, but does not replace testing with the specific content, browsers and platforms of each organization.
| Area | Available capacity | Consideration |
|---|---|---|
| Studio and native content | Creation, editing, export, reopening, learner view, questionnaires, games and visual resources. | It is advisable to review each course in the browsers and devices that the learners will use. |
| Educational games | 2D and 3D presentations integrated into Player, with adaptation to desktop and mobile. | 3D activities depend on the graphical capabilities of the browser and device. |
| External formats | Integration with H5P, SCORM, cmi5, QTI, Common Cartridge, IMS Content Package and other documented formats. | Exact compatibility may vary depending on the source package and the extensions you use. |
| npm and CDN | Player, Toolkit, Studio, H5P Libraries and Analytics are distributed through versioned channels. | When an integration depends on a specific behavior, expressly specify the version it uses. |
| Integration with applications | P2LRN separates the portable content of identity, permissions, registration and private data from the platform. | The integrating application must provide its own access and persistence controls. |
| LMS and LTI | The same Player and format can be used on different platforms through documented integrations. | Versions, plugins and policies of each LMS must be checked in the target environment. |
It does not amount to a universal certification of all third-party content, browsers, or LMS installations. For a specific implementation, validate the real cases that your users will use.