Re: [core] SenML JSON syntax (with multiple base objects)
Carsten Bormann <cabo@tzi.org> Tue, 27 October 2015 21:23 UTC
Return-Path: <cabo@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 897E21AD35D for <core@ietfa.amsl.com>; Tue, 27 Oct 2015 14:23:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.549
X-Spam-Level:
X-Spam-Status: No, score=-1.549 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001] 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 G7iwn1gjPq5v for <core@ietfa.amsl.com>; Tue, 27 Oct 2015 14:23:04 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B64171AD35A for <core@ietf.org>; Tue, 27 Oct 2015 14:23:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id t9RLMrUT014187; Tue, 27 Oct 2015 22:22:53 +0100 (CET)
Received: from nar.local (unknown [212.77.220.108]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3nlmGL3Bfpz2DbS; Tue, 27 Oct 2015 22:22:50 +0100 (CET)
Date: Wed, 28 Oct 2015 00:22:48 +0300
From: Carsten Bormann <cabo@tzi.org>
To: Alexander Pelov <alexander.pelov@telecom-bretagne.eu>
Message-ID: <etPan.562feb29.7756d8aa.168ed@nar.local>
In-Reply-To: <1191FB43-D8B3-4535-AA0A-7DB23EAC61A8@telecom-bretagne.eu>
References: <58C4BBDD-895C-4946-983A-405C6E5B760D@ericsson.com> <DAFB7C72-CF08-438E-B681-10918717A5D5@gmail.com> <20151020184630.GI5451@hephaistos.amsuess.com> <956423E0-BA70-4F4F-B0CD-6423203BC2BD@gmail.com> <3CEB5B46-504F-4F4C-B3B8-294625FAF6EA@iii.ca> <etPan.562f3207.2001ece.168ed@nar.local> <1191FB43-D8B3-4535-AA0A-7DB23EAC61A8@telecom-bretagne.eu>
X-Mailer: Airmail (329)
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="562feb29_548c87b4_168ed"
Archived-At: <http://mailarchive.ietf.org/arch/msg/core/G6Dst1WQvE6rL1Za2KRDL27__qI>
Cc: core <core@ietf.org>, "draft-jennings-core-senml@tools.ietf.org" <draft-jennings-core-senml@tools.ietf.org>, Christian Amsüss <c.amsuess@energyharvesting.at>
Subject: Re: [core] SenML JSON syntax (with multiple base objects)
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Oct 2015 21:23:05 -0000
Where, for every element: - if it is NOT an array, it is the key, and the following element is the corresponding value. - if it IS an array, its first element provides the key, and the rest of the array is the value, which is a DMM (processed recursively). (Why is the array always a DMM? Should be just any sequence of values that are in the multimap under the key given.) Sounds worthy of a CBOR tag. Do you have this written up? (I’d get rid of “deterministic”, I think the thing is just ordered.) This allows for an efficient encoding of DMM, where the keys can be of any type EXCEPT arrays. I don’t understand the last comment. If the key is an array, say for the multimap equivalent of {“a”: “b”, [1]: [2]}, you could represent it with OMM([“a”, “b”, [[1], [2]]]), where OMM is the tag for ordered multimaps. Yes, this requires a little care when encoding the keys. (There are a few other details about the data model semantics that probably need to be written down.) Grüße, Carsten
- [core] SenML JSON syntax (with multiple base obje… Ari Keränen
- Re: [core] SenML JSON syntax (with multiple base … Michael Koster
- Re: [core] SenML JSON syntax (with multiple base … Carsten Bormann
- Re: [core] SenML JSON syntax (with multiple base … Christian Amsüss
- Re: [core] SenML JSON syntax (with multiple base … Michael Koster
- Re: [core] SenML JSON syntax (with multiple base … Cullen Jennings
- Re: [core] SenML JSON syntax (with multiple base … Carsten Bormann
- Re: [core] SenML JSON syntax (with multiple base … Alexander Pelov
- Re: [core] SenML JSON syntax (with multiple base … Carsten Bormann
- Re: [core] SenML JSON syntax (with multiple base … Alexander Pelov