Guide spec authors to use one manifest (web app manifest) #95
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).
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).
Hopefully that clears up some of the confusion caused by the varied use of the word "manifest" among current W3C specifications.