|
|
| (14 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| | {{Template:WillNotMigrate}} |
| {{Voice}} | | {{Voice}} |
| {{Moodle 1.9}}
| |
|
| |
|
| == Objective == | | == Status == |
| Adapt Moodle interface to output the needed VoiceXML so you can navigate with your voice with a VoiceXML enabled browser, such as Opera.
| | Cancelled due to Opera´s voice control not good enough in open contexts. |
|
| |
|
| == Benefits == | | == Introduction == |
| Moodle is a free software e-learning platform which is designed to help educators create online courses with rich multimedia content. Making Moodle voice enabled will help disabled people, specially blind and motor disabled, to interact with this great e-Learning tool. Not only that, but also this gives another input interface which can be used to interact faster with the application. | | Moodle Voice is a project for embedding VoiceXML support into Moodle Core. |
|
| |
|
| == Timeplan == | | == Project Status == |
| * Analysis (2 weeks : May 28th - June 10th) | | * Project stopped. |
| ** Study W3C VoiceXML 2.0
| | * The current voice recognition technology in Opera is not good enough to make the whole Moodle application Voice accesible. |
| ** Extract requirements: study Moodle output and code to choose what to make voice enabled | |
| ** Begin project webpage, documentation and logs
| |
| * Design (1 weeks : June 11 th - June 17th)
| |
| ** Make an Architectural Design
| |
| ** Make an Implementation Proposal
| |
| * Implementation (8 weeks : June 18th - August 5th)
| |
| ** Milestone X (each 2 weeks)
| |
| * Documentation (2 weeks : August 20th - August 31th)
| |
| ** Developer documentation
| |
| ** Moodle administrator documentation
| |
| ** Future roadmap and design plans
| |
|
| |
|
| == Scope == | | == Current Focus == |
| Due to the large Moodle code, the scope of what to make voice enabled will be decided in the Analysis phase, although it will be at least all navigational stuff, such as course selection, profile configuration and resource selection.
| |
|
| |
|
| == State of the Art of VoiceXML ==
| | 1. Describing the functionality to be made voice enabled within this project. |
| VoiceXML is a well known technology that has been used and supported by IVR several years. Now it has finally come to our desktop. Currently, this technology is only supported by [http://dev.opera.com/articles/voice/ Opera] in the standard browsers field, but since it is a [http://www.w3.org/TR/voicexml20/ W3C Standard], I hope it will become the defacto technology for this kind of service in all browsers. There are already plans to implement it in [http://wiki.mozilla.org/Firefox:2.0_Accessibility Firefox] and [http://www.qsos.org/sheets/webbrowser/konqueror/konqueror-3.5.5.html Konqueror]. Some examples of this technology can be found at:
| |
| * http://dev.opera.com/articles/view/add-voice-interactivity-to-your-site/
| |
| * http://dev.opera.com/articles/view/temporary-x-v-by-example/
| |
| * http://dev.opera.com/articles/view/xhtml-voice-in-action/
| |
|
| |
|
| == Architecture Description ==
| | 2. Add an experimental option called "VoiceXML" so only when this variable is checked, VoiceXML code is generated. |
| # We have the option of using [http://moodle.org/mod/forum/discuss.php?d=31895 Customized Scripts] so we will [https://docs.moodle.org/en/Developer_Overview_of_MFM_Code not interfere with normal Moodle development]. On the other hand, we can directly merge it in the current CVS.
| |
| # Our code will detect whether the user browser is VoiceXML enabled or not and send the corresponding code
| |
| # In the "future roadmap" it will be included how to embed the code in Moodle core (in case it isnt) and make a Moodle configuration option to activate voice features. (It can be done in the project if we have enough time)
| |
|
| |
|
| == Related Work == | | 3. Create a php lib for VoiceXML to put all functionality of VoiceXML and to be used by the rest of the code. |
| * [https://docs.moodle.org/en/Moodle_for_Mobiles Moodle for Mobiles] [http://moodle.cvs.sourceforge.net/moodle/contrib/patches/mobile/ CVS]
| | |
| ** Outputs [http://www.w3.org/TR/1998/NOTE-compactHTML-19980209/ Compact HTML], uses [http://moodle.org/mod/forum/discuss.php?d=31895 Customized Scripts]
| | 4. Modify weblib.php and formslib.php intensively to use the VoiceXML lib and output VoiceXML code along with the html code if the VoiceXML variable is set. |
| | |
| | 5. Create a set of tests for every function and the integration of several functions to assure that the functionality is the expected one. |
| | |
| | == Contacts == |
| | Student : [http://mayankjain20.googlepages.com Mayank Jain] |
| | |
| | Mentor : [http://moodle.org/user/view.php?id=153093&course=1 David Horat] |
| | |
| | == Suggestions == |
| | Please feel free to chip-in with your suggestions. |
| Warning: This page is no longer in use. The information contained on the page should NOT be seen as relevant or reliable.
|
Status
Cancelled due to Opera´s voice control not good enough in open contexts.
Introduction
Moodle Voice is a project for embedding VoiceXML support into Moodle Core.
Project Status
- Project stopped.
- The current voice recognition technology in Opera is not good enough to make the whole Moodle application Voice accesible.
Current Focus
1. Describing the functionality to be made voice enabled within this project.
2. Add an experimental option called "VoiceXML" so only when this variable is checked, VoiceXML code is generated.
3. Create a php lib for VoiceXML to put all functionality of VoiceXML and to be used by the rest of the code.
4. Modify weblib.php and formslib.php intensively to use the VoiceXML lib and output VoiceXML code along with the html code if the VoiceXML variable is set.
5. Create a set of tests for every function and the integration of several functions to assure that the functionality is the expected one.
Contacts
Student : Mayank Jain
Mentor : David Horat
Suggestions
Please feel free to chip-in with your suggestions.
