Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Guide spec authors to use one manifest (web app manifest) #95

Open
travisleithead opened this issue Apr 7, 2018 · 2 comments

Comments

@travisleithead
Copy link
Contributor

commented Apr 7, 2018

We should provide guidelines on what to do if you want to create some data that should be in a manifest. We would like to avoid a proliferation of manifest files.

E.g., Assume you should integrate into web-app-manifest. If you can't for [good reason here] then [do this alternat thing].

See also w3ctag/design-reviews#231 (comment) which motivated the opening of this issue (among other previous discussions).

@hober

This comment has been minimized.

Copy link

commented Mar 21, 2019

@BigBlueHat

This comment has been minimized.

Copy link

commented Sep 26, 2019

The Web App Manifest doesn't actually (on it's own) "manifest" anything. It points to icons and metadata to be used in launcher icon creation and application discovery. It then points to a ServiceWorker for actually "manifestation" of the Web App and to a "scope" for limiting navigation within the constrained navigation environment (i.e. "standalone" browser environment).

Other manifest formats (like Audiobooks and Publication Manifest) encode a (deliberately) static, non-procedural list of resources--as one would do in a physical manifest document (i.e. the list of things to include + metadata about that list).

The Publication WG did look into Web App Manifest as a foundation, but it's dependency on ServiceWorkers (and therefore JavaScript) to do the actually manifestation brought in a new significant requirement that actually made a publication (or audiobook's) construction less dependable and more fragile and subjective (vs. a consistently structured, static list of resources).

Hopefully that clears up some of the confusion caused by the varied use of the word "manifest" among current W3C specifications.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.