» mLearning Thoughts: 3 Mobile Learning Examples You Might Have Missed If you are reading this, you already know mobile learning is a hot topic. You also know that incorporating social media into mobile learning is even more of a buzz term. With the price of an iPad 2 now dropped to just $400, the prospect of implementing a smart phone or tablet-based solution across your organization is probably looking more and more attractive. But how do you know what is actually practical, and what are some examples of how mobile learning is already being used? While we all love using our fancy phones and tablets, let’s not forget to learn a lesson from the past. While tablets and phones are both often called “mobile,” we cannot lump them in the same category all the time. Perhaps the greatest danger of all is the temptation to simply recreate our beloved “click next to continue” courses on mobile devices. Need some examples of how mobile learning is already being used? 2. 3. Are you using mobile learning in your organization?
HTML 4.01 Specification W3C Recommendation 24 December 1999 This version: (plain text [794Kb], gzip'ed tar archive of HTML files [371Kb], a .zip archive of HTML files [405Kb], gzip'ed Postscript file [746Kb, 389 pages], gzip'ed PDF file [963Kb]) Latest version of HTML 4.01: Latest version of HTML 4: Latest version of HTML: Previous version of HTML 4.01: Previous HTML 4 Recommendation: Editors: Dave Raggett <dsr@w3.org> Arnaud Le Hors, W3C Ian Jacobs, W3C Copyright ©1997-1999 W3C® (MIT, INRIA, Keio), All Rights Reserved. Abstract This specification defines the HyperText Markup Language (HTML), the publishing language of the World Wide Web. HTML 4 is an SGML application conforming to International Standard ISO 8879 -- Standard Generalized Markup Language [ISO8879]. Status of this document Available languages Errata
Widgets Current Status This page summarizes the relationships among specifications, whether they are finished standards or drafts. Below, each title links to the most recent version of a document. Completed Work W3C Recommendations have been reviewed by W3C Members, by software developers, and by other W3C groups and interested parties, and are endorsed by the Director as Web Standards. Group Notes are not standards and do not have the same level of W3C endorsement. Standards Group Notes Drafts Below are draft documents: other Working Drafts . Other Working Drafts
Mobile Learning: tomografía de una tendencia en expansión A partir de la opinión de expertos internacionales, el análisis de aplicaciones y plataformas para aprendizaje móvil, la investigación de índices de mercado, y el estudio de experiencias desarrolladas en América Latina, Europa y África; exploramos la actualidad de un fenómeno formativo en crecimiento. Datos reveladores, en la primera parte de un minucioso trabajo que se complementará próximamente con la evaluación de nuevas herramientas, reflexiones y casos de éxito. La clave: seguir a la persona, no al puesto de trabajo. Cuéntenos su experiencia. A principios de 2004, desde el Instituto Tecnológico de Massachusetts (MIT) se señalaba que el mobile learning debía ser un componente de valor añadido en los modelos de aprendizaje. En esta línea se expresa Ramiro Aponte, CEO de Latined, al considerar el impacto real que está teniendo el m-learning en los procesos de formación en América Latina aún es muy limitado. “Hoy la clave es poder seguir a la persona, no al puesto de trabajo.
HTML5 This specification defines the 5th major revision of the core language of the World Wide Web: the Hypertext Markup Language (HTML). In this version, new features are introduced to help Web application authors, new elements are introduced based on research into prevailing authoring practices, and special attention has been given to defining clear conformance criteria for user agents in an effort to improve interoperability. This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the most recently formally published revision of this technical report can be found in the W3C technical reports index at If you wish to make comments regarding this document in a manner that is tracked by the W3C, please submit them via using our public bug database. Implementors should be aware that this specification is not stable. This is a work in progress!
Mobile Web for Social Development (MW4D) | The MW4D Interest Group explores how to use the potential of Information and Communication Technologies (ICTs) on Mobile phones as a solution to bridge the Digital Divide and provide minimal services (health, edu Documents and Resources The MW4D IG has published the following documents: The MW4D plans to develop a set of documents which are described in the Deliverables section of the charter. The draft version of these documents are developed collaboratively on the group’s wiki. There is also a set of ressources relevant to the activity of the MW4D and which have been developped by W3C since 2006: Reasons for joining The objective of MW4D IG is to gather all stakeholders in a global forum in order to identify the key challenges of using mobile phones as an ICT-platform in Developing regions. The targeted players are Web experts, Mobile specialists, Academics from Developed and Developing regions, NGOs with field expertise, and International organizations working on reducing the Digital Divide. technical issues related to the mean of deployment (sms, voice, web,...) The following types of actors should be able to contribute to the mission of MW4D, and learn from other participants: Teleconferences
Proposal for Supporting Mobile Themes and Browser Detection Following community feedback, our proposal has broadened. Here's v2 - Moodle Device Detection Specification IntroductionThis document proposes some additions to Moodle 2.1 to enable detection of different types of device so that additional or alternative functionality can be provided. This would, for example, allow blocks, modules, etc to take advantage of mobile functionality (cameras, geo-location, etc); make customisations for tablets or to develop modules or blocks that are only for use for particular types. It also specifies a means for different themes to be used for different types. Browser DetectionA site setting enabledevicedetection will be added and set to yes by default. The following functions would be added to lib/moodlelib.php – get_device_type() – uses regular expressions to detect whether a device is mobile, legacy, tablet or default. Moodle Themes will have an additional optional setting supporteddevicetypes that will include a comma delimited list of supported types.
SMIL This version: Latest SMIL 3 version: Latest SMIL Recommendation: Previous version: Editors: Dick Bulterman, CWI - Jack Jansen, CWI - Pablo Cesar, CWI - Sjoerd Mullender, CWI - Eric Hyche, RealNetworks - Marisa DeMeglio, DAISY Consortium - Julien Quint, DAISY Consortium - Hiroshi Kawamura, NRCD - Daniel Weck, NRCD - Xabiel García Pañeda, Universidad de Oviedo - David Melendi, Universidad de Oviedo - Samuel Cruz-Lara, INRIA - Marcin Hanclik ACCESS Co., Ltd - Daniel F. Please refer to the errata for this document, which may include some normative corrections. This document is also available in a non-normative format: single HTML file. See also translations. Copyright © 2008 W3C® (MIT, ERCIM, Keio), All Rights Reserved. This document specifies the third version of the Synchronized Multimedia Integration Language (SMIL, pronounced "smile").
Mobile Web Application Best Practices Abstract The goal of this document is to aid the development of rich and dynamic mobile Web applications. It collects the most relevant engineering practices, promoting those that enable a better user experience and warning against those that are considered harmful. Status of This Document This section describes the status of this document at the time of its publication. This is the W3C Recommendation of Mobile Web Application Best Practices. Since publication as a Proposed Recommendation on 21 October 2010, the Working Group clarified that alternative compression formats (such as EXI) referred to in section 3.4.1 Use Transfer Compression may not share some of the impediments of common compression formats. The document contains statements that may be regarded as forward-looking when this document is published (14 December 2010). Comments on this specification may be sent to public-bpwg-comments@w3.org (with public archive). List of Best Practices 1 Introduction 1.1 Purpose of the Document