W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2009

Re: [cors] Web application

From: Mark Nottingham <mnot@yahoo-inc.com>
Date: Wed, 17 Jun 2009 16:51:00 +1000
Cc: WebApps WG <public-webapps@w3.org>
Message-Id: <A46A449F-6816-4343-8D6B-43925897D02F@yahoo-inc.com>
To: Anne van Kesteren <annevk@opera.com>
Anne,

Might I suggest that it seems more logical because you work for a  
browser vendor, and are steeped in the client-side application world?

A "Web service" means many different things to many different people  
(SOAP, WSDL, REST, etc.) and generally refers to an exposed API, not a  
web application.

As far examples:
   http://en.wikipedia.org/wiki/Web_application_framework
   http://www.scripting.com/davenet/2000/03/12/ 
whatIsAWebApplication.html
   http://www.webappsec.org/
   http://java.sun.com/javaee/technologies/webapps/

... and that's just from the first page of search results.

Note that I'm not disputing that what's in-scope here *could* be  
called a Web Application -- just that it's a very broad and muddy term  
that may mislead people who come at this document from a different  
angle.

Anyway, it was just a suggestion, not a big deal.

Cheers,



On 16/06/2009, at 3:05 AM, Anne van Kesteren wrote:

> Mark,
>
> You said Web application has been traditionally used to refer to  
> server-side applications. Is there any reference for this? It seems  
> more logical to call those Web services to me. Also, the name of  
> this group suggests Web applications is pretty much client-side so  
> I'm thinking of simply removing "client-side" within CORS.
>
> Cheers,
>
>
> -- 
> Anne van Kesteren
> http://annevankesteren.nl/

--
Mark Nottingham       mnot@yahoo-inc.com
Received on Wednesday, 17 June 2009 06:53:13 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:31 GMT