Subject: [Json] Updated draft to JSON-L

From: Phillip Hallam-Baker <[email-masked]>
Date: Tue, 6 May 2014 14:52:10 -0400

All,

I just updated the JSON-L draft to

* Add a security considerations (same as for JSON, i.e. don't be a doofus)

* Put in a reference to W3C extended log format so people can make use
of the same tags.

JSON does look a lot better than the W3C format when dealing with a
lot of tags per entry. But is is rather more verbose.

What I mostly want this for is to dump updates to a database to a file
for purposes of maintaining persistence etc. But being able to log in
JSON looks like a win.

If it turns out that space becomes an issue, one option would be to
use something like JSON-C which supports compression. Most log files
are going to report the same URLs over and over...

-- 
Website: http://hallambaker.com/