Re: [manifest] Support for Actionable Notifications in the manifest (#347)

Thanks @benfrancis for your comments. I understand now that the purpose of the web app manifest is primarily to support metadata pertaining to the *installing* of web apps. 

I had a few questions, which might be beyond the purview of this project, but I would be grateful if you could answer them. I like the idea of supporting an endpoint that can be used to describe the *thing* and *actions* pertaining to it. Looking at the [http://schema.org/Thing](http://schema.org/Thing) my understanding is there is no standard way of discovering more than one *potentialAction* for a given *thing* ? Is that correct ? 

Do you think support for these actions makes sense in the context of the Web Notifications API ? If the Web Notification's body exposed these types of actions, it would be awesome if the user agent supported a suitable subset (if not all) of these types of actions. 

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/347#issuecomment-88777877