RE: Potential f2f topics

You could try: WBuilder Professional from www.3tl.com

Ps: we have special deals for academics


-----Original Message-----
From: www-mobile-request@w3.org [mailto:www-mobile-request@w3.org]On
Behalf Of nitin gupta
Sent: Saturday, October 06, 2001 7:24 PM
To: www-mobile@w3.org
Cc: www-mobile@w3.org
Subject: Re: Potential f2f topics


 Hi all ,
I am a WAP developer and was using WAP  toolkit 2.0 for developing my
applications for my problem report during my graduate studies.  But when the
trial period expired and I tried to download it again, I saw that the
earlier version was not avaiable for download, and it was replaced by Nokia
Mobile Internet Toolkit 3.0 which is a new J2ME version. Is it possible for
me to get hand of the previous toolkit version so that I can continue ahead
with my application .
Thanks,
regards ,
Nitin
--

On Fri, 05 Oct 2001 09:31:04
 Johan Hjelm wrote:
>Hi Mark,
>I think the scope should be more tied to current W3C activities. For
>instance, today we have "mobile profiles" from a lot of groups (CSS,
>SVG, etc). These are actually not mobile, but minimal profiles. I think
>it would be interesting to discuss how we could include mobile
>technologies, such as positioning, into the W3C specification set.
>
>I second the idea to discuss web services in a mobile perspective as
>well. At least providing requirements will be important.
>
>There is also the upcoming release 5 of the 3GPP specifications, which
>contains several things that relate to W3C specifications, that I think
>should be throroughly analyzed and understood.
>
>But remind me again: When was the F2F? Is it for the cross-WG meeting in
>february?
>
>Johan
>
>
>Mark Baker wrote:
>
>> Hi all,
>>
>> I've received a couple of inquiries offline, asking about the
>> potential topics Kaz and I were considering for the f2f.
>> The ones we discussed included;
>>
>> - how to best take advantage of "always on" over the Web.
>> Is the WAP 2.0 model of putting a micro web server on the
>> device the best choice?  What are the issues in doing this
>> for wireless?
>> - in 2.5/3G networks, how "always on" is "always on", and what
>> do we need from our protocols (if anything) to help us cope when
>> "always on" only means "mostly on".
>> - if, because of "always on", more information will be pushed
>> our way, rather than pulled, how should personalization work?
>> Is anything more needed of CC/PP, HTTP, or other parts of the
>> stack to handle this case?
>> - mobile web services; is anything special required?
>>
>> Kaz also had an interesting idea, but I'll leave it to him to
>> decide what he wants to say about it at this time.
>>
>> There you have it.  Comments and suggestions for additional topics
>> are always welcome.
>>
>> MB
>
>--
>++++++++++++++++++++++++++++++++++++
>  Johan Hjelm, Senior Specialist
>     Ericsson Research Japan
>
>  Read more about my recent book
>http://www.wireless-information.net
>************************************
>
>


Make a difference, help support the relief efforts in the U.S.
http://clubs.lycos.com/live/events/september11.asp

Received on Monday, 8 October 2001 04:42:31 UTC