Internet Object (IO)'s design wasn't influenced by Toon or GraphQL.
The project began back in 2017 with very different goals: reducing repeated keys,
introducing a schema-first structure, separating data from metadata, supporting a
richer type system, and keeping the format as readable as CSV while still being
expressive enough for nested data.
IO is meant to be a lean, schema-driven data serialization format - not a query
language (like GraphQL) or a minimal notation (like Toon).
Happy to explain any specific parts if you're curious.
It looks like a mix of graphql and toon.
Thanks for checking it out!
Internet Object (IO)'s design wasn't influenced by Toon or GraphQL.
The project began back in 2017 with very different goals: reducing repeated keys, introducing a schema-first structure, separating data from metadata, supporting a richer type system, and keeping the format as readable as CSV while still being expressive enough for nested data.
IO is meant to be a lean, schema-driven data serialization format - not a query language (like GraphQL) or a minimal notation (like Toon).
Happy to explain any specific parts if you're curious.