[Json] JSON Log file encoding JSON-L

[Phillip Hallam-Baker <[e-mail]>]

This encoding is based on JSON but for reasons explained in the draft
is not pure JSON. Instead a JSON log is a sequence of JSON objects
separated by newline characters.

There is clearly a need for a way to use JSON in log files. It would
be better to have one than many ways. So probably the best next steps
would be for people to try it and then go for an independent
submission for a MIME type unless people want to do something more
formal.

This scheme does not address the other major use case raised which is
writing configuration files. Configuration files need comments. I
think that is a totally different use case to log files though.


http://datatracker.ietf.org/doc/draft-hallambaker-jsonl/

The spec itself is pretty short.


3. Specification

   A JSON-L log file consists of a sequence of zero or more JSON objects
   as specified in [RFC7159] separated by white space that includes at
   least one newline character.


           JSON-L-text = *(object x-ws)

           x-ws = *ws %x0A *ws


3.1. Resynchronization

   Since control characters are not permitted inside JSON string values
   and JSON objects MUST be separated by commas inside a JSON array, the
   sequence '}' *ws LF *ws '{' can only occur at the end of one log
   entry and the start of the next:'


           Boundary = end-object x-ws begin-object


Not got round to a security considerations yet.
-- 
Website: http://hallambaker.com/