W3C home > Mailing lists > Public > public-bpwg@w3.org > February 2008

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]

From: Holley Kevin (Centre) <Kevin.Holley@O2.com>
Date: Thu, 21 Feb 2008 17:21:14 -0000
Message-ID: <A21CF1DCE029FB4F83D44EDF747A4BFA01AC15AB@UKSTHMSX006.uk.pri.o2.com>
To: <public-bpwg@w3.org>
I am a bit new to this specific sphere but I have trouble understanding what "web" really means any more. 

A web browser opens a TCP socket over the internet and engages in http dialogue but also post dialogue and other things.  Today's web browsers can have other protocols such as ftp, rss, and so on. 

So why is a widget which is basically a cut down web browser not a web application?

What hard criteria in terms of protocol usage can we apply here?

Regards, 

Kevin


Kevin Holley
Manager, Application Standards
Group Technology
O2
Telefónica O2 Europe plc,

Direct Line: +44 1473 782214
Mobile: +44 7802 220811
Fax: +44 7711 752031
Email: kevin.holley@o2.com
IM: kevinaholley (MSN/Y!/AIM etc.)

www.o2.com


----- Original Message -----
From: public-bpwg-request@w3.org <public-bpwg-request@w3.org>
To: public-bpwg@w3.org <public-bpwg@w3.org>
Sent: Thu Feb 21 16:42:47 2008
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





This electronic message contains information from O2 which may be privileged or confidential. The information is intended to be for the use of the individual(s) or entity named above. If you are not the intended recipient be aware that any disclosure, copying distribution or use of the contents of this information is prohibited. If you have received this electronic message in error, please notify us by telephone or email (to the numbers or address below) immediately.

Switchboard: +44 (0)113 272 2000

Telefónica O2 Europe plc   Registered Office:  Wellington Street, Slough, Berkshire SL1 1YP
Registered in England and Wales:  5310128 VAT number: GB 778 6037 85

Received on Thursday, 21 February 2008 17:21:45 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:09:51 UTC