RE: ISSUE-237 (Define Mobile Web Applications): What is the definition of a "Mobile Web Application" for the purposes of BP2? [Mobile Web Applications Best Practices]

Kai,
As I said on the call, the underlying environment in which a web
application runs in should not be a limiting factor. MIDP is an
execution environment for example, similar to a native OS in that it
provides application support services such as API's for network access.
There are popular web browsers that run under MIDP, and these should be
also in scope. 

Our intent is to provide practical guidance to developers of web
technology based applications in general as you have defined them, i.e.
that provide a content presentation and interaction experience for
users. 

I don't see the value of limiting this to specific "types" of
applications or execution environments (e.g. one in which DOM is the
main way of interacting with the environment), but I do see the value of
using the browser as a typical/example frame in which to discuss best
practices that are more widely applicable (this was specifically the
resolution in the Nov F2F).

Best regards,
Bryan Sullivan | AT&T | Service Standards
bryan.sullivan@att.com
-----Original Message-----
From: public-bpwg-request@w3.org [mailto:public-bpwg-request@w3.org] On
Behalf Of Scheppe, Kai-Dietrich
Sent: Thursday, February 21, 2008 9:02 AM
To: Mobile Web Best Practices Working Group WG
Subject: RE: ISSUE-237 (Define Mobile Web Applications): What is the
definition of a "Mobile Web Application" for the purposes of BP2?
[Mobile Web Applications Best Practices]


A web application exposes some sort of interface to the user.
This interface may be an application running in the browser itself or it
may be an application running on the server, but display some GUI with
which the user may interact.

Moving this into a mobile context, a web application must run without
any additions, such as plugins or Java.

-- Kai


Please make note of my new email address:
k.scheppe@telekom.de
 

> -----Original Message-----
> From: public-bpwg-request@w3.org
> [mailto:public-bpwg-request@w3.org] On Behalf Of Mobile Web Best 
> Practices Working Group Issue Tracker
> Sent: Thursday, February 21, 2008 5:43 PM
> To: public-bpwg@w3.org
> Subject: ISSUE-237 (Define Mobile Web Applications): What is the 
> definition of a "Mobile Web Application" for the purposes of BP2? 
> [Mobile Web Applications Best Practices]
> 
> 
> ISSUE-237 (Define Mobile Web Applications): What is the definition of 
> a "Mobile Web Application" for the purposes of BP2? [Mobile Web 
> Applications Best Practices]
> 
> http://www.w3.org/2005/MWI/BPWG/Group/track/issues/
> 
> Raised by: Daniel Appelquist
> On product: Mobile Web Applications Best Practices
> 
> We have a number of different (but I would say converging) views on 
> what constitutes a Mobile Web Application.  My view is that we are 
> talking about applications for which the user interface element 
> executes in the browser/web technologies context. I would specifically

> put device APIs out of scope. I would specifically put widgets out of 
> scope. I would specifically put non-"web" technologies such as flash 
> and silverlight out of scope. Jo has suggested we could use the 
> criterion of whether or not the technology uses the underlying 
> technology of the DOM to define "Web technologies."  As agreed on 
> today's call, this is an important enough issue to pull out from the 
> discussion on scope and give it its own issue.  I want to come back to

> this issue on next week's call and take a resolution on this point so 
> we can get this out of the way before the next F2f.
> 
> Discuss!
> 
> Dan
> 
> 
> 
> 
>

Received on Thursday, 21 February 2008 17:54:14 UTC