Re: [w3c/manifest] Add optional `translations` member (#676)

Thanks @aarongustafson for putting together that proposal! Super helpful. 

I'd be supportive of having the straight `translations` member, but would not be in favor of having separate resources for languages (i.e., no to "an external reference to a json file containing the keys"). The problem with that it adds significant complexity: 

 * additional fetch(es)
 * having to deal with network errors (what if some fail, some ok) 
 * having to deal with validation errors... what if the linked JSON is invalid. 
 * potentially having to deal with import loops.
 
Thus, I'd be in favor of just keeping it simple and allowing translations to override - at least for now. We can look at enhancing the behavior if we need to in the future. 

-- 
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/676#issuecomment-817617728