But you haven't yet answered Akamel's question of why this exists, with comparisons to the existing standards (OData in this case).
Everything I've seen just says that this is simply a subset of OData's functionality. And the features that are being asked for by users commenting on the OP are ones already provided by the existing standard.
And what about querying the data? There have already been questions elsewhere in this thread about how this would work. OData already provides very rich query support, including document projection (returning a subset of a document) through to complex queries navigating multiple relationships (I easily could ask, through a GET query string, to return all the actors who have starred in films that belong to the comedy genre - navigating 3 collections, actors,films,genres). If queries are out of the scope, then fine, but its clear people want to query their data.
So please answer what this offers over existing standards if you want to compete.
Oh, and in response to your earlier post of what OData JSON looks like, you're much better served by linking to v4, not v2 as you did:
Everything I've seen just says that this is simply a subset of OData's functionality. And the features that are being asked for by users commenting on the OP are ones already provided by the existing standard.
And what about querying the data? There have already been questions elsewhere in this thread about how this would work. OData already provides very rich query support, including document projection (returning a subset of a document) through to complex queries navigating multiple relationships (I easily could ask, through a GET query string, to return all the actors who have starred in films that belong to the comedy genre - navigating 3 collections, actors,films,genres). If queries are out of the scope, then fine, but its clear people want to query their data.
So please answer what this offers over existing standards if you want to compete.
Oh, and in response to your earlier post of what OData JSON looks like, you're much better served by linking to v4, not v2 as you did:
http://docs.oasis-open.org/odata/odata-json-format/v4.0/cspr...
That doesn't look so dissimilar.