The Job class now structures the "_attributes" object of the response by splitting the attribute names by periods and nesting them. For example, an attribute named "location.address.street" becomes structured as { "location": { "address": { "street": [ VALUE, ... ] }}} in the "_attributes" object. The Model class validates that the names of attributes do not override one another. Example: A model with attributes "name.first" and "name.last" is valid, but a model with attributes "name" and "name.first" is invalid because "name.first" will override "name" in the "_attributes" section of the resolution response.

Closes #77