Jason Harmon

@luki343 you said "a few wrong pins", but only specified the PC15->PB15 (which has been corrected. Did you find any other incorrect mappings?

It's worth noting that RAML take on this, 'traits' (really not much different from the proposed structure). http://raml.org/developers/raml-200-tutorial#traits

The examples on http://jsonapi.org are pretty self-descriptive of this issue (and apply to HAL and potentially other message formats): http://jsonapi.org/

Just brainstorming here: JSON Schema for json-api is here: http://jsonapi.org/schema We could define an `allOf` to inherit from that model: ``` yaml allOf: - $ref: 'Pet.yaml' - $ref: 'http://jsonapi.org/schema' ```...

@webron the point is that if `Pet.json` and `http://jsonapi.org/schema` both define `items`, how are those fields merged? Clearly the intent is that `Pet.json/items` overrides `http://jsonapi.org/schema/items`, but there's really no way...

Link to meta #566

I see that the @blondak fork was merged back in March...it would be great to get a new DEB release. I'm still experiencing this after installing from DEB as recommended.

On links: the only trouble with your example is that there is not a consistent link structure to rely on, as proposed. Resource a passion structures as in stormpath.com don't...

I could see the following scenario: An API only responds with `200` for happy path and errors (which produces all the niceness of the aforementioned `4xx`, `5xx` statuses). These things...

I'd agree @webron that it's probably an issue that's trending down in public APIs. However, I have concern that as internal APIs are being built more and more (often with...