Re: new updated roadmap available

Thanks Stephane,

I agree that bluetooth is not really part of the mobile web

Re Sim Card / Java card - from wikipedia - "SIM operating systems come in
two main types: Native and Java Card. Native SIMs are based on proprietary,
vendor specific software whereas the Java Card SIMs are based on standards,
particularly Java Card <http://en.wikipedia.org/wiki/Java_Card> which is a
subset of the Java programming
language<http://en.wikipedia.org/wiki/Java_%28programming_language%29>specifically
targeted at embedded devices.
* Java Card allows the SIM to contain programs that are hardware independent
and interoperable.*"

This could be useful for big internet related projects around banking (like
mpesa), health records/id related projects or simply getting a set of useful
bookmarks directly onto the browser.

Regards

Rob



On Thu, Jun 4, 2009 at 4:42 PM, Stephane Boyera <boyera@w3.org> wrote:

> Hi Robert,
>
> thanks for your references, they are great, and contains lots of info. I
> added links to them from the tools section (
> http://www.w3.org/2008/MW4D/wiki/Tools ). also added a link to your blog
> from the organization section (
> http://www.w3.org/2008/MW4D/wiki/Organization )
>
> good starting point for discussions about which technologies should appear
> in the roadmap and under which sections.
> Among the technologies you mentionned the following are not in the current
> document
>
> 1- bluetooth
> for me bluetooth is a communication mechanism/network layer. it is a way to
> download and install applications and contents, but it is not a technologie
> to author and deliver content and apps. or am i missing something ?
> bluetooth is potentially a way to lower costs of delivery, and there are
> many experience to create mobile kiosk using bluetooth. but this is imho a
> bit out of the scope of this document focusing more at the application
> layers. what does other think ?
>
> 2- RSS
> RSS as a way to deliver information is indeed a great technology. i
> personnaly feel it should appear in the document in the misc section.
>
> 3- APIs for major web sites or services e.g. Twitter
> if we decide to add this bit, it should surely go in the native application
> sections, but as such it is just an api in specific languages (java, ...)
>
> 4- Sim Card, Java Card, Smart Cards
> i've to say that i don't know anything about this, can someone explain me a
> bit better what it is, particularly what is the major different with a
> classical j2me apps ?
>
> 5- Instant messaging - Mxit, Mig33, Jabber
> i've some problems with this part, like for the API in point 3. this is all
> proprietary stuff, linked to a specific IM or SN. i don't see that as a
> generic way to create content and apps. but it might be worth mentionning it
> in the misc section ?
>
> I'm adding this discussion to the next call.
>
> Stephane
>
>  When I read the roadmap I realised that I have already blogged about a few
>> things contained in it and some things I've already written may be relevant.
>> In response to a site which was mainly pushing native applications for
>> mobile I blogged the following post.
>>
>>
>> http://mainstreamingict.org/2009/04/quick-brain-dump-of-great-resources-for-the-mobile-developer/
>>
>> this covers a bunch of stuff as per section 6 of the roadmap
>> (technologies) (Apart from the native aps) - it gives a quick run through of
>> Mobile Web (Through a microbrowser), SMS, USSD, Bluetooth, J2me and voice
>> aps.
>>
>> Later I added an extra post which covers a few more technologies to look
>> at
>>
>>
>> http://mainstreamingict.org/2009/05/quick-brain-dump-of-great-resources-for-the-mobile-developer-that-i-had-previously-left-out/
>>
>> which gives a bit of info regarding tying in RSS, web 2.0 APIs, Java Card,
>> instant messaging and suitable file types for Mobile phones - *these are all
>> missing in the roadmap* but all I consider them potentially useful - maybe
>> they can fit under misc
>>
>> Regards
>>
>>
>>
>>
>> On Thu, May 28, 2009 at 4:14 PM, Stephane Boyera <boyera@w3.org <mailto:
>> boyera@w3.org>> wrote:
>>
>>    Dear All,
>>
>>    as promised, i worked a the new instance of the roadmap i presented
>>    during last call.
>>    I tried to integrate the resolution and discussions we had last week.
>>    For those who were on the call during the may 18 call, please let em
>>    know if i forgot some stuff.
>>
>>    The new version is at
>>    http://www.w3.org/2008/MW4D/wiki/roadmapv2
>>
>>    i prefered to create a plain new uri. i put a deprecated flag on the
>>    previous one (http://www.w3.org/2008/MW4D/wiki/roadmap )
>>    and link the new one from the wiki MW4D home
>>    (http://www.w3.org/2008/MW4D/wiki/MW4D ) and the Mw4D home
>>    (ressource section) http://www.w3.org/2008/MW4D/
>>
>>    all comments are welcome, and we will continue discussion during
>>    next call (June 8)
>>
>>    Cheers
>>    Stephane
>>    --    Stephane Boyera         stephane@w3.org <mailto: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
>>
>>
>>
> --
> 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
>