> I have some JSON terms - I have to write them like this:

> {"id"     : 123,
> "author" : "erl...@gmail.com",
> "title"  : "Some title",
> "type"   : "html",
> "vsns":[{"vsn":1,
>      "time":"201200908113012",
>      "content":"<h1>This is html</h1>\n<pre>a\nb</pre>"}]
> }

> But I'd prefer to write them with far fewer quotes and with embedded
> line feeds like this:

> {id     : 123,
> author : "erl...@gmail.com",
> title  : "Some title",
> type   : html,
> vsns:[{vsn:1,
>      time:"201200908113012",
>      content:"<h1>This is html</h1>
> <pre>a
> b
> </pre>"}]
> }

> Or do any of the erlang JSON parsers handle non quoted names in object literals?

> /Joe
> _______________________________________________
> erlang-questions mailing list
> erlang-questi...@erlang.org
> http://erlang.org/mailman/listinfo/erlang-questions

> Object members without quotes is against JSON RFC. If you skip quotes
> then this is not JSON any more.

>> This is true, but it does not hold you back from choosing another
>> representation format and then converting from that format into proper JSON
>> later when you need to interact with other systems in a correct manner. Raw
>> JSON is quite hard to write due to some of the rules in the dark corners of
>> JS parsing :)

> If you don't want to parse strictly JSON, YAML is an option that will give
> you more flexibility than JSON (and the features you asked).

> There are some available Erlang wrappers for libyaml, but I haven't used
> them personally:

> https://github.com/goertzenator/yamler

> José Valim
> www.plataformatec.com.br
> Founder and Lead Developer

> _______________________________________________
> erlang-questions mailing list
> erlang-questi...@erlang.org
> http://erlang.org/mailman/listinfo/erlang-questions