> JSON not only mixes key/values and lacks schema; it mixes data and headers (or metadata for that matter) too. There is no concept of headers in JSON. And nei

> JSON not only mixes key/values and lacks schema; it mixes data and headers (or metadata for that matter) too. There is no concept of headers in JSON. And neither is there in the proposed Internet Object. The (ugly?) example of https://internetobject.org/the-story/ https://internetobject.org/the-story/ can be written in any data format (thinking of Yaml) and obviously also in the "Internet Object". There are reasons to blame JSON for, such as the lack of comments. But the lack of schema is plain wrong -- there is JSONschema and there are validators which can be perfectly used when recieving data over the web, for instance.