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

@marcoscaceres 

>@iherman, to your proposal: I would like to generalize some of the algorithms at some point... like "run the steps to process a string", "run the steps to process a space separated list" , etc. and you would get a lot of the security properties for free. It's what implementations do already, and would make the spec a lot smaller. Just haven't found time to do that. 

Thanks! That sounds great, and it goes in the direction I was wondering about. I believe there may be some terms in the current document that may be generic (eg, `scope`?) as well as obtaining the manifest (although, in our own discussions where we also looked at how to obtain manifests for Web Publications we went a bit further in the possibilities than what you considered, see [current PWP draft](http://w3c.github.io/dpub-pwp/#manifest_algorithm).

Exposing the manifest values through a JS API... I must admit I did not think about that before; because the manifest is in JSON, it is "just" a big object with keys and values from a JS point of view, I am not sure what it would bring. But I do not claim to be a JS programmer, so I may miss something.

---
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-227996134