Re: [w3c/manifest] Define "web application" (Issue #1097)

I'm not really a fan of that definition (perhaps as a general concept, but not in terms of what we want to capture here). That definition is trying to classify individual websites as "web apps" or "not web apps" (e.g. "Gmail is a web app, Wikipedia is not", or some such).

What I think we are interested in here is not a _classification_ that can be applied to site A but not site B. Rather, it's a definition of the object we create when we process a manifest. So, it's basically an object that exists in a particular set of URLs (the scope), has a unique identity (the id), and a bag of metadata (the name, icon and other properties defined in the manifest) including capabilities (e.g. file handlers). It can be installed (which creates a local client-side object mirroring the "app" object on the server) and launched (which dynamically creates a browsing context with the metadata applied).

(I'd make my definition more formal but this is the lines along which I'd like to define it.)

My definition is almost tautological: the web app is defined as, essentially, the object described by the manifest. But I think that's exactly it. We currently define the [application manifest](https://www.w3.org/TR/appmanifest/#dfn-manifest) as "a JSON document that contains startup parameters and application defaults for when a web application is launched" (without ever defining "web application"). I think we should define "web application" as the object having those parameters, and the "manifest" as the document that describes the application.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/1097#issuecomment-1704802172
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/manifest/issues/1097/1704802172@github.com>