Re: [w3ctag/design-reviews] Proliferation of manifests at W3C (#423)

Taking @tantek 's comment a different way.

Perhaps instead of collapsing and reducing the number of Manifests, maybe we should recognize that there are different use cases and requirements and we should have a structured taxonomy of Manifests.  Each Manifest would be for a specific set of use cases and we would explain in the taxonomy why we need multiples (e.g. the size of the objects might be different, the frequency that snippets are sent around might be different).  Notionally, it could look something like:

Manifest Level 1.  For WebApps.... description of canonical use case.
Manifest Level 2.  For Payments
Manifest Level 3.  For AudioBooks
Manifest Level 4.  For Publications.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/423#issuecomment-543736694