Lock down data schema

[sumwatshade]

Context

Before a back-end solution's tooling chain has been decided upon, the definition of Roost's internal data must be established.

Tools

• jsonschema

Current State

{
 name: String,
 website: Optional<String>,
 tags: Optional<String []>,
 lat: double,
 lng: double
}

[sumwatshade]

I think we should support:

• a set of donation methods
• a set of service request options (ex. grubhub, angie's list, etc.)
• phone number

I think we should adjust:

• the data object for location. maybe

location: {
 lat: double,
 lng: double,
 address: Optional<String>
}

• maybe the attribute names? name is not specific
• assess if the typing is correct (ex. maybe some sites want to reference multiple websites, should we support that?)