It is less human readable than JSON.
Human readibility is one of the most important aspects of JSON. Without that requirement you could use a binary serialization.
Internet Object – A JSON alternative data serialization format
31–40 of 83 posts
Re: Internet Object – A JSON alternative data serialization format
#32> age:{int, min:20},
address: {street, city, state}
Unless the space after the colon is significant it seems we have to just "know" that int introduces a type definition instead of a structure.
Also
> Schema Details JSON doesn't have built-in schema support!
seems a little disingenuous. JSON provides a name for each type of value, so there is mostly no need for the schema when viewing the data. There is a JSON Schema definition.
Re: Internet Object – A JSON alternative data serialization format
#33[deleted]
Re: Internet Object – A JSON alternative data serialization format
#34The example schema has:
> age:{int, min:20}
Re: Internet Object – A JSON alternative data serialization format
#35If you follow that link which says "Read the Story Here" they have this json example which has a list of employees and then info about the pagination of that list. The caption is this
>If you look closely, this JSON document mixes the data employees with other non-data keys (headers) such as count, currentPage, and pageSize in the same response.
But they don't explain at all how Changing the data format fixes the underlying issue of mixed concerns in one data object.
Re: Internet Object – A JSON alternative data serialization format
#36They lost me when they declared an address type.
Addresses are so varied in implementation and meaning that it’s frankly ridiculous.
Re: Internet Object – A JSON alternative data serialization format
#37> age:{int, min:20}, address: {street, city, state} Unless the space after the colon is significant it seems we have to just "know" that int introduces a type definition instead of a structure. Also > Schema Details JSON doesn't have built-in schema support! seems a little disingenuous. JSON provides a name for each type of value, so there is mostly no need for the schema when viewing the data. There is a JSON Schema…
Yeah, this format looks really badly designed
Re: Internet Object – A JSON alternative data serialization format
#38How are commas or speechmarks in strings escaped?
Re: Internet Object – A JSON alternative data serialization format
#39The example schema has: > age:{int, min:20} Why would a data serialization format bother with data validation like the minimum value here?
front and validation perhaps?
Re: Internet Object – A JSON alternative data serialization format
#40What ever the pros and cons are here... What the ** does this mean?
> Name , Email > Remain updated, we'll email you when it is available.
Why do this? Should i read that the format isn't ready? Is there going to be a mailing list of format enthusiast? Are you planning on releasing a V2022 next year and every year? More use-case specific derivatives?
All a format needs is 3 short examples, a language definition, and a link to an implementation.
Everything else lowers my expectation and its appeal.