- From: adesina iluyemi <adeiluyemi@gmail.com>
- Date: Thu, 21 May 2009 17:55:43 +0100
- To: Stephane Boyera <boyera@w3.org>
- Cc: "public-mw4d@w3.org" <public-mw4d@w3.org>
- Message-ID: <e6191d690905210955u3d560c95s51be6685bc2e56a@mail.gmail.com>
Dear All, I apologies for my absent in the last few meetings. I have been away on research trips amd meetings. I will read the thread online and looking forward to join and contribute in future meetings. Regards, Adesina 2009/5/14 Stephane Boyera <boyera@w3.org> > Dear All, > > As promised i'm launching the discussion about the document the group is > aiming to produce (aka Roadmap). > > Let me start with some background info. A summary of this work is described > in the charter of the group ( > http://www.w3.org/2007/12/MW4D/charter1.1.html) section 2.2. > The idea is to produce a document that will summarize the output of the two > workshops (the one which took place in maputo in april, and the one in > brazil last year), as well as the different discussions we had on the > mailing-list and during the teleconferences. > The aim of this document is to identify the challenges of using mobile and > web technologies to provide development-oriented services to underprivileged > populations of developing countries. > > Because we didn't made any substantial progress since we started > http://www.w3.org/2008/MW4D/wiki/roadmap i believe that i should take a > more proactive role, and lead discussions for the future teleconferences. > Thus, i'm starting with the structure of the document, to be discussed next > monday. > I believe that the structure we put in the current roadmap might not be > that appropriate. For instance, i'm not sure we should keep the first > section "Delivering Applications on Mobiles". This section has interesting > references, but should most probably be merged with the page on stories ( > http://www.w3.org/2008/MW4D/wiki/Stories ). It is very useful to know what > are existing projects, but this is probably not part of the roadmap > document, but should just be mentionned as part of references within > document. > > Therefore here is my proposal for a new structure. let's use it as basis > for discussion on monday. i will then make it in a real document, and we > could start sharing the edition of some parts. > > Introduction > @@ what we want to address in the document > > Audience > @@ there are different audiences that are targeted with this document: > -those who want today to build and deploy content and apps on mobile and > that would find what's possible today, and what are critical challenges, and > how to work around them as much as possible > -those who could launch appropriate actions to find solutions to > challenges: this includes academics, international org. such as W3C, > foundations, mobile industry (handset/operators/software makers...)... > -those who could develop training and tools, and leverage awareness in the > development sector on how to integrate mobile in the field work > > Objectives > @@objectives of the document is to present how to use mobile technologies > in the field today, and what are the key challenges that might impact the > implementation or usage of content and services. > > Challenges > @@this si one of the major section, describing what are the key challenges > when developing and deploying a mobile content or apps. > two major parts around the challenges around the specific profile of > targeted end-users, and the challenges for potential provider of mobile > content to effectively integrate this tool in their work. > > Access Challenges > @@for each of the challenge mentionned in the section, we would present the > issue, example, what should be done to provide a global solution to this > problem, and what are potential solutions existing today if one experience > the challenge > availability of content in local languages > - issue: people speaks languages that are not supported or > renderable > - long term issue: identify key elements that are necessary > to add a new language in the ICT world, and develop methodologies for making > it available > - workaround: use intermediaries (e.g. VPO) that can speak > another language, use voice applications with prompt in the local languages > Illiteracy > - how to solve that in the future: develop > technology and guidelines on how to make content available to people with > low reading skills through e.g icons+voice or other solutions > - workaround possible today if one wants to target > communities with very high level of illiteracy: use of intermediaries (e.g. > VPO), use of voice apps > > computer literacy > - issue: people being able to search and find > existing apps > - long term solution: exploring a standardized way > to announce new content and services to people like existing today with e.g. > widget and applestore > - workaround: use of portals, use of intermediaries > that are internet literate, advertisements > > > > Content provider challenges > Awareness > knowining what's possible > knowing what exists > > Expertise > > Tools > infrastructure tools > application-specific tools > > Business Model and costs > monetization of services > > regulation > censorship > > Technologies > @@ in section we will describe the different technologies, pointing to > examples of usage, existing tools for authoring and deployment, costs,... > > SMS > Voice > - classical voice apps > - web based voice apps (VoiceXML) > Mobile Web > Misc > USSD > Native J2ME > > > Stephane > > -- > Stephane Boyera stephane@w3.org > W3C +33 (0) 5 61 86 13 08 > BP 93 fax: +33 (0) 4 92 38 78 22 > F-06902 Sophia Antipolis Cedex, > France > > -- Adesina Iluyemi mHealth Innovator/Consultant SINSEPROD LLP, UK Sustainable eHealth/Telemedicine in Africa Centre for Healthcare Modelling & Informatics University of Portsmouth T: +44 (0)23 9284 6784 M: +44 (0)79 5602 6010 Skype:innovatoris W: http://www.linkedin.com/in/adesina1974
Received on Thursday, 21 May 2009 16:56:24 UTC