Franz Liedke

Most likely that it can be implemented by classes that already extend from other classes, I suppose?

My previous endeavors with writing JSON-API libraries have shown me that supporting both the building and parsing of JSON-API payloads is actually quite useful, i.e. for filtering valid attributes when...

Well, I have had a good experience with defining my entities in one place and using that for both serializing and parsing. Doing both would also mean we can focus...

Sure. It's Ruby, so it is pretty close to pseudo-code anyway ;) ~~~rb entity do type 'discussions' writable attribute('title') { description 'The discussion title' type String } writable attribute('text') {...

@tobscure Sorry for the long silence, this lay around on my todo list forever. :disappointed: That said, you seem to have figured it out, looks like a good attempt. These...

`json-api-schema` kind of describes the scope quite well, given you omit the routing (which, on the other hand, would be quite thin - yet useful - if it only deals...

And lastly, assuming that @f3ath's [json-api-php/json-api](https://github.com/json-api-php/json-api) package is complete, we could simply build on top of it to provide the schema / server stuff. (You might even want to join...

I am slightly worried about performance, though. (The serialization of lots of resources on lots of endpoints is somewhat critical to performance.) @tobscure Do you still have your benchmark code...

@f3ath With v1 you mean current `tobscure/json-api`? What about his v2? It's supposedly even faster.

@tobscure Is any of this online? I'm quite interested - I have built a similar tool in Ruby at work in the last few months. ;)