Re: [Json] Using JSON in log files

Tim Bray <tbray@textuality.com> writes:

> Check how XMPP skates around XML’s single-root-element rule.  Me, I’d just
> have a log file containing a sequence of JSON texts.

True. However, compared to XML, JSON has an additional issue of "value-separator" (comma) that can only appear between members. Perhaps it would be useful to allow for a comma right before the closing brace/bracket.

Lada

>
>
> On Wed, Nov 20, 2013 at 9:02 AM, Bjoern Hoehrmann <derhoermi@gmx.net> wrote:
>
>> * Phillip Hallam-Baker wrote:
>> >This is not an extension I would want to use in an on-the-wire format. But
>> >for log files it is essential. Particularly in my case where the logs are
>> >digitally signed notary records.
>>
>> I use http://yaml.org/ for such purposes. It is a superset of JSON, in
>> a way. Converters to JSON, which you would need one way or another, are
>> readily available. You could also just cheat and say "It's JSON without
>> the encapsulating []".
>> --
>> Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
>> Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
>> 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
>> _______________________________________________
>> json mailing list
>> json@ietf.org
>> https://www.ietf.org/mailman/listinfo/json
>>
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json

-- 
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: E74E8C0C