The learning systems we are building toward.
None of these connections is live yet. They are the standards Techcopter is implementing, listed so you can see where your platform sits before anyone promises you a date.
- Planned
SCORM 1.2
Packaged module with completion and score reporting.
- Planned
SCORM 2004
Sequencing and richer status reporting.
- Planned
LTI 1.3
Launch from your LMS with roles and grade passback.
- Planned
xAPI
Statement-level activity underneath everything else.
- Planned
Web Embed
One responsive iframe snippet, no plugin.
- Planned
REST API
Provision users, assign modules, pull records.
- Planned
SSO
SAML and OIDC, so a seat is a named person.
Two constraints we state before promising anything
WebXR inside an iframe needs allow="xr-spatial-tracking". Some LMS platforms strip iframe attributes or block it by content security policy, so headset delivery is verified per platform before it is promised.
Model files requested by a browser can be captured from its network tab. The public catalogue is served openly, and deliberately so. An asset behind an account is served only to a signed-in session, which stops a shared link but not a determined viewer: there is no signed-URL or domain-allowlist layer today. An asset that must not be redistributable is not one to embed until there is.
Support for a standard means Techcopter implements and tests against it. It does not mean a conformance certification has been issued by a certifying body.