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

Phillip Hallam-Baker <hallam@gmail.com> Wed, 07 May 2014 02:16 UTC

Return-Path: <hallam@gmail.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 6A2361A04BA for <json@ietfa.amsl.com>; Tue, 6 May 2014 19:16:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 wVNtoZROpQkP for <json@ietfa.amsl.com>; Tue, 6 May 2014 19:16:19 -0700 (PDT)
Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) by ietfa.amsl.com (Postfix) with ESMTP id AA5C31A0479 for <json@ietf.org>; Tue, 6 May 2014 19:16:18 -0700 (PDT)
Received: by mail-lb0-f180.google.com with SMTP id p9so413335lbv.39 for <json@ietf.org>; Tue, 06 May 2014 19:16:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=UABl1wLaQG3G+ox2+JWy/wMKcckTmOm0WrEUtavlpxs=; b=bxdPCdlJC9CzHzr6ocDBvAaWuQNYhauyzIpsgt6KlU3KAQJ42Vlur/kk5Mb7OPRXPD fM3PI6U8elSWePy1EGmKEfHhAlYjvGjinsLhk9uFZBOkv/Z7uVtZPNicDW1aGRvgctyT 0ZkF0GQMqxbtMPNb3i1sfLaUNDfaMIxgDVA+7VQpvGHIPEueENPSrWUrq4QnENPfL2kf MdeOU72Wem2RRssV5ubK3d+4cOnwpzO7nZYjfOCpcl9GVE1LoP/fCPtYBy4wlxw7tJqP MDHgAyYLtS36VWJFfOid5ce3LivfAu9CuRD9Ptr2Dm0cqBI3X7P4CwCnyltOjskWHRLC 6Zaw==
MIME-Version: 1.0
X-Received: by 10.112.218.74 with SMTP id pe10mr11119055lbc.3.1399428974013; Tue, 06 May 2014 19:16:14 -0700 (PDT)
Received: by 10.112.234.229 with HTTP; Tue, 6 May 2014 19:16:13 -0700 (PDT)
In-Reply-To: <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> <255B9BB34FB7D647A506DC292726F6E11545BD241D@WSMSG3153V.srv.dir.telstra.com>
Date: Tue, 06 May 2014 22:16:13 -0400
Message-ID: <CAMm+LwgYus3covb8CXxGJeMSgWsGDR5+B3qg-AuJH5=iUERRhA@mail.gmail.com>
From: Phillip Hallam-Baker <hallam@gmail.com>
To: "Manger, James" <James.H.Manger@team.telstra.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/json/HilOofei_U5UMV8i7TByQviXR3A
Cc: Nico Williams <nico@cryptonector.com>, 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:16:20 -0000

We do? Ooops.

Didn't see the other draft.


I think the discussion moved on a bit from Nico's. He has a lot of
discussion I think we have solid reasons to make decisions on.

Importing WD-logfile tags seems like a win to me (but I might be biased).


On Tue, May 6, 2014 at 10:05 PM, Manger, James
<James.H.Manger@team.telstra.com> wrote:
>> 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



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