IETF Logo Mail Archive

Re: [Json] JSON Log file encoding JSON-L

"Manger, James" <James.H.Manger@team.telstra.com> Wed, 07 May 2014 02:05 UTC

Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FCBF1A053B for <json@ietfa.amsl.com>; Tue, 6 May 2014 19:05:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.202
X-Spam-Level:
X-Spam-Status: No, score=-0.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RCVD_IN_DNSWL_NONE=-0.0001, RELAY_IS_203=0.994] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O9U0OD_ALTbK for <json@ietfa.amsl.com>; Tue, 6 May 2014 19:05:29 -0700 (PDT)
Received: from ipxbno.tcif.telstra.com.au (ipxbno.tcif.telstra.com.au [203.35.82.204]) by ietfa.amsl.com (Postfix) with ESMTP id 24B401A0538 for <json@ietf.org>; Tue, 6 May 2014 19:05:28 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.97,1000,1389704400"; d="scan'208";a="7446909"
Received: from unknown (HELO ipcani.tcif.telstra.com.au) ([10.97.216.200]) by ipobni.tcif.telstra.com.au with ESMTP; 07 May 2014 11:57:02 +1000
X-IronPort-AV: E=McAfee;i="5600,1067,7430"; a="172419441"
Received: from wsmsg3707.srv.dir.telstra.com ([172.49.40.81]) by ipcani.tcif.telstra.com.au with ESMTP; 07 May 2014 12:05:11 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by wsmsg3707.srv.dir.telstra.com ([172.49.40.81]) with mapi; Wed, 7 May 2014 12:05:11 +1000
From: "Manger, James" <James.H.Manger@team.telstra.com>
To: Nico Williams <nico@cryptonector.com>, Phillip Hallam-Baker <hallam@gmail.com>
Date: Wed, 07 May 2014 12:05:10 +1000
Thread-Topic: [Json] JSON Log file encoding JSON-L
Thread-Index: Ac9piYYghbprsq1jQ1GDUqEL5Bj/KQAAJPaw
Message-ID: <255B9BB34FB7D647A506DC292726F6E11545BD241D@WSMSG3153V.srv.dir.telstra.com>
References: <CAMm+LwjB-51z4GoeC0riehmJg1HAddmLAyfMsVOCVM80i=RiMA@mail.gmail.com> <B9D8B85D-EF2C-4B3A-90A4-873C714C06FA@tzi.org> <CAK3OfOhGpUatFotCPwpHw=wu4zphxWOAk6dvX2UOZJRzw23JEA@mail.gmail.com> <CAK3OfOh1R851pBETEJtzM7_rCvrhxedCn5v5==nHumstE9VSRA@mail.gmail.com>
In-Reply-To: <CAK3OfOh1R851pBETEJtzM7_rCvrhxedCn5v5==nHumstE9VSRA@mail.gmail.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/json/ZgFAMhBKi0QfgBWzuftlM0HootU
Cc: JSON WG <json@ietf.org>
Subject: Re: [Json] JSON Log file encoding JSON-L
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/json/>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 May 2014 02:05:31 -0000

> Thank you Carsten.  I think I'll do the following: a) add RS to the
whitespace list for JSON text sequence separators, b) RECOMMEND
surrounding JSON texts with RS in log-like sequences.  Then JSON
sequences will be meet the needs of logs.

Don’t do that. Surely no one uses RS anymore; and certainly no one who uses JSON. It doesn't make much sense to use SEPARATOR TWO without using ONE, THREE and FOUR.

[RS = Record Separator = U+001E = INFORMATION SEPARATOR TWO]


We now have Nico’s JSON Text Sequences [draft-williams-json-text-sequence],
and Phillip’s JSON Log Format (JSON-L) [draft-hallambaker-jsonl].

They are basically the same. Can we just keep one? Probably the more generic JSON Text Sequences. 
A JSON-L is a JSON Text Sequences where each item is an object.
If a specific log spec is necessary (eg want to standardise log entry elements like "time") it could say "a JSON-L log is a JSON Text Sequence, where the items MUST be objects and these common elements are defined: time, ...".

--
James Manger

v2.23.0 | Report a Bug | By Email