Here at #w3cTPAC 2019 I’m learning that there are quite a few different manifest file format efforts by different groups for different specifications with different but often similar use-cases. Filing this design issue per @hober’s request to track the growing number of manifest formats and approaches to hopefully collapsing and reducing them.
Here is a few I know of along with their individual TAG review issues.
- Web App Manifest (W3CTAG #30)
- Payment Method Manifest (W3CTAG #162, Payment Method #27, W3CTAG #231 Payment Handler)
- Audio Book Manifest (W3CTAG #345)
- Publication Manifest (W3CTAG #344)
And one apparent need for a manifest: W3CTAG #218. There are likely others, please add more below.
From a web author, developer, publisher perspective, it would be great if we could simplify the number of manifests, ideally one, perhaps with core properties, optional properties for specific use-cases, and a method of expanding each of those by separate working groups for maximum re-use and avoiding collisions / duplication of slightly different properties.
This issue is intended as a meta-issue just to track the growing number of manifests.
For specific proposals to provide guidelines to both spec and web authors about how to create some data and provide it in a manifest file, see: W3CTAG #95 (please do not mark as duplicate, I think these serve two different purposes). Thanks for your consideration!