- From: Stephane Boyera <boyera@w3.org>
- Date: Mon, 30 Jun 2008 10:56:22 +0200
- To: Raphaƫl Dard <Dard@intracen.org>
- Cc: public-mw4d@w3.org
Hi Raphael, > Now I got a bit confused when some of you told me in Sao Paulo "the > Mobile Web is much wider than what goes on the Web we use on our > PCs(HTTP). It actually also covers VoiceXML and many more". > It is then useful to read this Wikipedia abstract: "Just as HTML > documents are interpreted by a visual web browser, VoiceXML documents > are interpreted by a voice browser." let me explain my view here. I see different concepts - web content: it is content existing on the web reachable at a specific URI, through http protocol. it could be a markup language, or other type of resources like images, video, sounds,... The content exists by itself. then you access this content through an access mechanism: a browser on a desktop, a kiosk at the airport, a mobile phone, ... So there are many ways of accessing the same content, and voice, and voice applications are clearly included in this picture. At W3C for isntance, we have a whole domain called Ubiquitous Web Domain investigating the different means on accessing web content. I agree that in this context considering SMS is border line, because it is not about using http to access content. But well, i believe that given the importance of SMS today, we have to integrate it in this group scope. The mobile Web has a clear definition: it is about browsing from mobile phone: so accessing web content on a mobile phone using a browser. So in this context, my view is that mobile web is a way among few others to access web content from a mobile phone. At least, we should also consider at least voice applications, native (java, or os specific) applications, and SMS. As explained during the workshop, i strongly believe that: 1- the mobile web is the most promising technologies for the future for many reasons imho including - interoperability and operator independence - discoverability of content (search engine, portals) - low required expertise and low cost to develop content and applications 2- it is not yet a reality for many reasons including - absence of browser on low-end phones - cost (and potentially absence) of data access 3- there are issues that could be solved and make the mobile web even a better choice: - accessiblity for illeterate people - internationalization of content ... >> I do not suggest this is a bad idea, but probably in >> the longer term, not the best approach to optimizing the possibilities > of >> the mobile web. > > I agree with you that SMS has limited capacities and that we need to > try and help put the right environment in place in order to enable more > content-friendly protocols and equipment. But if I had come up with food > prices on another protocol than SMS, the exporters that I was trying to > help would have told me: "Now get me a new cellphone and a "data plan" > with one of our local telecom operators" (when available, this costs a > fortune, including because of the cost of download). As we said during > the workshop, for now, lots of it is left to the good will of the > telcos. well, i've quite a different view. If we look at the mobile telephony phenomena itself, very few people 5-10 years ago would have bet a cent on its potential to be affordable for Developing Countries, and particularly for rural communities, and low-income part of the targeted populations. But, the fact is that the cost is lower than the RoI (return on investment). People are using SMS today because there is no other choice. I believe that if all phones were equipped with a mobile browser, and if there were lots of services relevant and useful for people, they would use them. Just to say that i strongly believe in an enabling context, and i believe that this is the task of this group to identify what would be the characteristics of this enabling context. Connectivity is one (with kiosk an alternate interesting model), availabilities of useful service is another,... What is really important imho is to look at the same time on what is possible today with already present technologies like SMS, and what is a desirable future as Bill is naming it, and the way to reach it. Cheers Stephane -- Stephane Boyera stephane@w3.org W3C +33 (0) 4 92 38 78 34 BP 93 fax: +33 (0) 4 92 38 78 22 F-06902 Sophia Antipolis Cedex, France
Received on Monday, 30 June 2008 08:57:00 UTC