Re: [w3c/manifest] Define core web manifest to enable extensions (#471)

> On 21 Jun 2016, at 12:22 AM, Tzviya <notifications@github.com> wrote:
> 
> From the Digital Publishing IG:
> Would it be a more extensible architecture to define a "core" web manifest, with common terms, procedures, etc, with an extension model that could be used to define a Web App manifest and others, depending on the usage patterns? 
> Here are some examples of what this might mean for the publishing world:
> 
> Section 7.2 [1] allows for extension points, but this is listed in processing instructions and not explicit. Would it be possible to add a section clarifying the extension process? Digital Publishing will likely be interested in expanding the definition of “manifest” [https://www.w3.org/TR/appmanifest/#dfn-manifest] and possibly scope and navigation so that it is clear that a specific set of objects are contained a publication.

Sure, but we would need to understand the use cases better and any current limitations. What exactly is not clear about the extension point and where to hook into the algorithm? 

> Publishing might not require all manifest members. In this case, it would be helpful if specific members (e.g. “theme_color”) could be optional.

All members are optional in the spec. Apologies if that was not clear. 

> [1] https://www.w3.org/TR/appmanifest/#dfn-extension-point
> 
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub, or mute the thread.
> 


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