I appreciate your hardwork on this.
My personal preference would be to avoid app specific media types. It is not helpful as far as I can tell.
I do think that a Google Service Discovery Document can describe the full protocol that an app may require.
That protocol will require some Hypermedia capability, so we need something like Siren (or HAL for that matter)
The JSON schema could be derived from a Siren profile, I guess (assuming a JSON encoding)
I am not sure I truly understand , sorry! but found a good discussion here: http://www.mnot.net/blog/2012/04/17/profiles
So I guess my vote, today, could be:
application/json; profile="http://example.com/orders"; describedby="schema.rnc"
Does this help at all?
On Aug 6, 2012, at 9:58 PM, Kevin Swiber <kswi...@gmail.com> wrote: