Re: [w3c/manifest] Multiple authors / developers (#630)

Package.json is a good option also. The use case why I actually got this
idea for credits is indeed to show this information in an app store (the
Blockstack Browser).

In contrary to package.json it is safe to assume that manifest.json is
publicly accessible. Also the key idea is that it is not just for developer
attribution but also to give designers, copy writers and others their
deserved credits in a computer readable standard format.

2017-12-04 13:06 GMT+08:00 Marcos Cáceres <notifications@github.com>:

> For anything that resembles credits, it's best handled within the
> application itself.
>
> The utility of something like this would need to show some value via the
> user agent, OS, search engine, or app store (i.e., what demonstrable value
> is there to users?).
>
> In the last decade, we've made various attempts to add "author" type info
> to various manifest formats, but have found it to be of limited utility.
>
> For developer facing attribution, package.json files are probably better
> suited to record this information.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/w3c/manifest/issues/630#issuecomment-348861651>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/AAYEhpLXTwCu-vpUKZrysoCmO7V4ss-rks5s833HgaJpZM4Qzvwd>
> .
>


-- 
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/630#issuecomment-348862430