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

peter van der Stok <stokcons@xs4all.nl> Tue, 21 May 2013 08:56 UTC

Return-Path: <stokcons@xs4all.nl>
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 94EE721F9670 for <core@ietfa.amsl.com>; Tue, 21 May 2013 01:56:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.504
X-Spam-Level:
X-Spam-Status: No, score=-0.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
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 LMYzVMdOL3xc for <core@ietfa.amsl.com>; Tue, 21 May 2013 01:56:03 -0700 (PDT)
Received: from smtp-vbr15.xs4all.nl (smtp-vbr15.xs4all.nl [194.109.24.35]) by ietfa.amsl.com (Postfix) with ESMTP id 2652421F96B7 for <core@ietf.org>; Tue, 21 May 2013 01:56:02 -0700 (PDT)
Received: from roundcube.xs4all.nl (roundcube6.xs4all.net [194.109.20.204]) by smtp-vbr15.xs4all.nl (8.13.8/8.13.8) with ESMTP id r4L8u1ma005205; Tue, 21 May 2013 10:56:01 +0200 (CEST) (envelope-from stokcons@xs4all.nl)
Received: from a82-95-140-48.adsl.xs4all.nl ([82.95.140.48]) by roundcube.xs4all.nl with HTTP (HTTP/1.1 POST); Tue, 21 May 2013 10:56:01 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Date: Tue, 21 May 2013 10:56:01 +0200
From: peter van der Stok <stokcons@xs4all.nl>
To: Carsten Bormann <cabo@tzi.org>
Organization: vanderstok consultancy
Mail-Reply-To: <consultancy@vanderstok.org>
In-Reply-To: <954F147E-F9E8-471A-B973-E7A5FB9E2349@tzi.org>
References: <CAPRuP3mzM07-LY1c1on7iRa+dGiaSeRw-U8NGNobAM0U0DqqPg@mail.gmail.com> <D60519DB022FFA48974A25955FFEC08C0515CDFC@SAM.InterDigital.com> <5bc6a98b6f42ec654e7e5fd7d0675f83@xs4all.nl> <954F147E-F9E8-471A-B973-E7A5FB9E2349@tzi.org>
Message-ID: <fe7a88620a3b461d955677e9ccbd56c7@xs4all.nl>
X-Sender: stokcons@xs4all.nl (dBrDtIIFr1y6hIH+B4ZThWE+PlWpafeK)
User-Agent: XS4ALL Webmail
X-Virus-Scanned: by XS4ALL Virus Scanner
Cc: 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
Reply-To: consultancy@vanderstok.org
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: Tue, 21 May 2013 08:56:09 -0000

Starts to make sense. So, you partially agree about core-interfaces 
being the base document (informationally or not).
Will other "links-exi" documents then also be based on core-interfaces?
Or do we need still another document?
I mention this need for some generally understood structure beforehand, 
because at the moment writing a document about for example "coap based 
management" takes some thinking about which documents (just from core) 
are relevant and possibly normative.

Greetings,

peter

Carsten Bormann schreef op 2013-05-21 10:40:
> On May 21, 2013, at 09:04, peter van der Stok <stokcons@xs4all.nl> 
> wrote:
> 
>> Could the contents of links-json not be combined with 
>> core-interfaces?
> 
> Core-Interfaces is meant as an informational document describing good
> approaches, while links-json actually defines a format.
> 
>> I can imagine that we have other documents defining the json contents 
>> for different management subjects
> 
> Right, but they are on quite different timelines.
> Generally I'd expect all future documents defining a format to define
> the (or a) JSON version, if that is desired.
> links-json just fills in that gap retroactively for 6690.
> 
> Grüße, Carsten