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

Re: [cors] Web application

From: Anne van Kesteren <annevk@opera.com>
Date: Wed, 17 Jun 2009 09:11:05 +0200
To: "Mark Nottingham" <mnot@yahoo-inc.com>
Cc: "WebApps WG" <public-webapps@w3.org>
Message-ID: <op.uvnp8rdo64w2qv@annevk-t60>
On Wed, 17 Jun 2009 08:51:00 +0200, Mark Nottingham <mnot@yahoo-inc.com> wrote:
> 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.

Leaving it the same is no problem either.

I realize a Web service is just an API on the server, but it seemed to me that any kind of other Web application would have some kind of UI part rendered in a Web browser. But yeah, given that this specification deals with requests I can see how it might be confusing if you don't know about e.g. XMLHttpRequest.


-- 
Anne van Kesteren
http://annevankesteren.nl/
Received on Wednesday, 17 June 2009 07:11:48 GMT

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