Add patterns

[pwalsh]

• Closes Locally caching remote or inline resources via "cache" key #243
• Closes Create a Patterns / FAQ section #321
• Closes Proposal: Translation and Language Support in JSON Table Schema #190
• Closes [jts] Handling translations of the data #171

[pwalsh]

@jheeffer see bef39e8

Would you mind contributing your concrete proposal for translations to the section I added for it? I tried to do it myself but I encountered various cases that I was not sure how you guys handle, or perhaps how they should be worded (remote/local).

[rufuspollock]

@pwalsh BTW I'm increasingly feeling we should call this section FAQs and Patterns even if url remains patterns of whatever. I think people know what an FAQ is and a bunch of stuff will be more faq like. I think patterns as solutions to (bigger) FAQs make sense so having both in naming is ok.

[pwalsh]

@rufuspollock no problem on FAQs. Any other comments before we can merge this>

[Fak3]

"data" here is a bit confusing. I initially thought it talks about the csv or other data placed in resources.

[jheeffer]

@pwalsh I'd be glad to contribute, but I have two solutions

1. The way I proposed in the translations PR Proposal: Translation and Language Support in JSON Table Schema #190 (comment)
   This is generic and supports both your inline as well as a filesystem based solution. It is however pretty verbose (and also needs an extra pair of eyes to check if it's totally unambiguous).

2. The way we store translations in our datasets at Gapminder (datapackage.json and translations folder and documentation). Has assumptions on location and format of translation files (like your inline solution does) and thus is not generic, but also a lot less verbose.

Which one are you interested in?

[pwalsh]

@jheeffer definitely solution 2. Thank you!

[rufuspollock]

@pwalsh i'd like to get this merged asap so we have less outstanding and because this is an item with no impact on specs (it is not changing anything).

wdyt?

[pwalsh]

@rufuspollock I'm happy for it to be merged now, and then @jheeffer can do his PR against the default branch

[rufuspollock]

@pwalsh merging now.

@jheeffer be great to get your pattern in here for how you handle translations as per your option 2. Just do a PR as soon as you are ready:

2. The way we store translations in our datasets at Gapminder (datapackage.json and translations folder and documentation). Has assumptions on location and format of translation files (like your inline solution does) and thus is not generic, but also a lot less verbose.