On Mon, 25 Aug 2014 21:09:07 GMT, Jonathan Marler wrote:
Yes you are correct! ASON's semantics are dependent on the application. That's where the name "Application Specific" came from. The following features make the text "Application Specific"
- optional colons/commas
- omitting root level braces or brackets
- Nameless object fields.
I've noticed that in most applications it's unnecessary to specify the structure of the data you are representing because the application already knows what kind of data it is expecting. This concept is what makes ASON unique from other JSON variants. This is the main concept I wanted to get people's opinions on. There are advantages and disadvantages to it. Thanks for taking the time to read it and understand what makes it unique.
My question is: can we parse any ASON file without application-dependent knowledge? I we can't then it's a show-stopper for any general parser.