CMI 5 Working Group Meeting Minutes December 5th, 2014 - AICC/CMI-5_Spec_Current GitHub Wiki
CMI 5 Working Group Meeting Minutes - December 5th, 2014
Attendees
- William A. McDonald – Boeing Flight Services
- Bernard Bouyt - Airbus
- Andy Johnson – ADL
- Peter Berking - ADL
- Art Werkenthin - RISC
- Henry Ryng – INXSOL
- Ray Lowery – Pratt & Whitney
- Ben Clark – Rustici Software
- Dan Lopez – ApprenNet
- Daniel Pfeifer – Float Mobile
- Chris Handorf – Pearson
Notes
New Mailing List Postponed
Due to some technical difficulties with the new (ADL sponsored) CMI-5 mailing list – we will continue to use [email protected] until we get them resolved.
New Meeting Conferencing
We are now using the ADL sponsored GotoMeeting Webinar to replace WebEX. Today was the first meeting using the new system?
Should you have technical difficulties with accessing the new conferencing system please contact the ADL.
Alternative Launch Environments
The group continued to investigate how the launch mechanism would work outside of web browser environments. Daniel Pfeifer was invited to explain how mobile apps (iOS and Android) can be launched by a URL and if there are any differences that need be considered in a non-browser environment.
After much discussion, it appears that one launch mechanism using a single URL will work for multiple environments.
An LMS should be able to launch “non-browser” applications using an application specific protocol in the URL. As follows:
<application>://<URL to content>
The application protocol has to be registered for the specific application on the OS/Device.
This is common practice for iOS, Android, and Windows.
Mac OS and Linux should have the same functionality but this will need to be investigated.
The group further examined what additional language would be needed for the CMI-5 URL specification in the Course Structure specification to accommodate both browser and non-browser environments.
The following was generally agreed (for Course Structure – AU URL requirements):
- Relative URLs will use HTTP/S protocol (Normal Browser launch)
- Wrapper web pages can be used negotiate application launching in most cases (normal HTTP/S browser launch - no spec change needed for this)
- If the URL to the content contains a Query String, it must be merged with the URL launch parameters at launch time. (similar to how AICC/HACP works)
- You can use your own application specific protocol in a URL – but the remaining portion of the URL must follow HTTP/S conventions.
Next Meeting
Dec 12th, 2014 – 10:30am US Eastern Time
All Previous CMI-5 Meeting Minutes
https://github.com/AICC/CMI-5_Spec_Current/wiki
CMI-5 on GitHub: