IETF Logo Mail Archive

Re: [core] draft-bormann-core-links-json: call for adoption

"Kovatsch Matthias" <kovatsch@inf.ethz.ch> Wed, 22 May 2013 11:50 UTC

Return-Path: <kovatsch@inf.ethz.ch>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0BA621F9607 for <core@ietfa.amsl.com>; Wed, 22 May 2013 04:50:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rpUjL5NQ3u3h for <core@ietfa.amsl.com>; Wed, 22 May 2013 04:50:21 -0700 (PDT)
Received: from edge20.ethz.ch (edge20.ethz.ch [82.130.99.26]) by ietfa.amsl.com (Postfix) with ESMTP id BC74D21F95E7 for <core@ietf.org>; Wed, 22 May 2013 04:50:19 -0700 (PDT)
Received: from CAS11.d.ethz.ch (172.31.38.211) by edge20.ethz.ch (82.130.99.26) with Microsoft SMTP Server (TLS) id 14.2.298.4; Wed, 22 May 2013 13:50:06 +0200
Received: from MBX20.d.ethz.ch ([fe80::81a7:b7a5:50c0:df0d]) by CAS11.d.ethz.ch ([fe80::ecc9:4e2d:b26b:1614%10]) with mapi id 14.02.0298.004; Wed, 22 May 2013 13:50:12 +0200
From: Kovatsch Matthias <kovatsch@inf.ethz.ch>
To: Carsten Bormann <cabo@tzi.org>
Thread-Topic: [core] draft-bormann-core-links-json: call for adoption
Thread-Index: AQHOVbotWGQjJnIEwEGIonasgHGRWpkQ+bvQ///p34CAAAXHAIAALlOQ
Date: Wed, 22 May 2013 11:50:11 +0000
Message-ID: <55877B3AFB359744BA0F2140E36F52B514EE765F@MBX20.d.ethz.ch>
References: <CAPRuP3mzM07-LY1c1on7iRa+dGiaSeRw-U8NGNobAM0U0DqqPg@mail.gmail.com> <55877B3AFB359744BA0F2140E36F52B514EE74B0@MBX20.d.ethz.ch> <69A59031-FB53-42EC-A61D-FBBFCF189E39@tzi.org> <4E4A7BCC-A658-4E1E-8DC8-C88D82737E8E@tzi.org>
In-Reply-To: <4E4A7BCC-A658-4E1E-8DC8-C88D82737E8E@tzi.org>
Accept-Language: en-US, de-CH
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [193.10.67.36]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "core@ietf.org" <core@ietf.org>
Subject: Re: [core] draft-bormann-core-links-json: call for adoption
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 22 May 2013 11:50:27 -0000

Thank you very much for digging that up!

> What I said:
> -- It is sad that we have different serializations for things
> -- On the backend, web-app, services side, it is quite usual these days to find
> information in JSON format
> -- It is useful to have a single [i.e., standard] way to express link-format
> information in JSON
> -- As a side-effect, we create good precedent for application developers to
> represent link-format information in the same way in different applications.
>    We make it simpler for application developers to think about link-format
> because they know how it looks like in JSON.  But that is a side effect.

Yes, that perfectly matches the experience we are currently making in a "Cloud + Internet of Things" project. There is some appeal to make this format more general, but pushing it forward within CoRE sounds good (as it is pretty simple there).

Ciao
Matthias

v2.23.0 | Report a Bug | By Email