Toby Zerner

More changes: * Static Document/Relationship constructors [inspired](https://github.com/json-api-php/json-api/blob/master/src/Document/Document.php) by @f3ath * Rename meta/link methods (still a bit unsure about these...) * Remove error *handling* stuff - I think it's just slightly...

Further changes: * Add internal `ResourceIdentifier` and `ResourceObject` classes so that all serialization is done via `JsonSerializable`. This change means that theoretically @f3ath's [new json-api library](https://github.com/json-api-php/json-api) could be pulled in...

@franzliedke @f3ath Thoughts on renaming the `ResourceInterface` methods as follows: `getId` → `getResourceId` `getType` → `getResourceType` `getAttributes` → `getResourceAttributes` `getLinks` → `getResourceLinks` `getMeta` → `getResourceMeta` `getRelationship` → `getResourceRelationship` This would...

getAttributes at least, possibly getRelationship? Or does Eloquent use getRelation...

Fair call. It's probably bad to encourage coupling of the Resource to the Model anyway. My only question then is: do we really need ResourceInterface, or can we just get...

But what does the interface offer that the abstract class does not? Sorry, I'm still a bit naive on the philosophical and practical differences between interfaces/abstracts :/

Right, understood. But then that leads me back to the method naming... I feel like the methods as they are will be pretty likely to conflict if implemented into an...

By the logic you've argued, should we also be using a RelationshipInterface?

I think technically, yes, it should be an interface. Because there are two separate concerns: 1. Representing the relationship information in the context of a tree of resources (this is...

json-api-response could work... especially since we have the Parameters utility which aids in the construction of a document in response to a request