IETF Logo Mail Archive

Re: [T2TRG] OpenAPI/AsyncAPI discussion from April 24th WISHI online meeting

Jonathan Beri <jmberi@gmail.com> Fri, 12 June 2020 19:40 UTC

Return-Path: <jmberi@gmail.com>
X-Original-To: t2trg@ietfa.amsl.com
Delivered-To: t2trg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B02F3A0CA1 for <t2trg@ietfa.amsl.com>; Fri, 12 Jun 2020 12:40:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 P7Ay1OPmE-zS for <t2trg@ietfa.amsl.com>; Fri, 12 Jun 2020 12:40:20 -0700 (PDT)
Received: from mail-vs1-xe31.google.com (mail-vs1-xe31.google.com [IPv6:2607:f8b0:4864:20::e31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84F013A0F0A for <t2trg@irtf.org>; Fri, 12 Jun 2020 12:39:55 -0700 (PDT)
Received: by mail-vs1-xe31.google.com with SMTP id g129so5970357vsc.4 for <t2trg@irtf.org>; Fri, 12 Jun 2020 12:39:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=aPICnSt1MsHwif/qzhV34FeNLaE0FrVz7jekgGmKQuc=; b=t8laMUMfPR7UgUzXTrjR9RpudYCvpuNX+Lr8wdacU7Qlj2gPP+f4K0rXeFzIV9tisf afDUTKjZDGUcoDiWkaOFValJ6v8U22wKC830M/mvIgVQfVvnOB0HNGZ4WeSlFQ7Dr3n7 jKlt2bIO7Ep3eH3NmmAgbqV8fZNp/rrQI+qwuE8eyuME9lmrcAr292gz72ONujcnQ76E 17Z3H6ipDGRH1imWLW/ihrxi/KGbKVUo2XVHrMTGAOEZHSU4FY7+5lzd+m9mmnABnqMZ DEj0gJvNbMzJ4J705qzWUdrbll55Y9KTaq2oB4Zzfn8Hua8e7/RmzfRXukmMhowy2Eju 8lEQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=aPICnSt1MsHwif/qzhV34FeNLaE0FrVz7jekgGmKQuc=; b=KYMZRvViPhTJl++QPGgQvcesKne26aMxfR16JYhAqYj8o2aVJhcxKj7eJ01+WsNTxL 5dcSIs0dyZQ4qQagwd7hbTTdy/p8dL25arP28c+yUAxXJNituTrK4/S4vc4K/vwz2y17 KElD+Recfs+PzuYKnNQTNwbNNO4XB7TIa9epf4jYXD8/J/RO2a17tbCwn7yYJkes1NKi QvzPAySf9rY2+vRh+ZMdGOEjR+Fx1o+voXJPa0/H9qeLe98zeaxwz/WxNF4YpfyriuIg VjU6k0J/dkTsKdQo8NvgRxQYgQuRFgjmQtOZx1he4TAggF249C+f5AUSz6++QrLlMweB cWrg==
X-Gm-Message-State: AOAM531nXFuByIe8dMlPsZ5v8Ed08oFOAuor4sRdupqEEySa04L1X71o Yae6xddyDh+xHVs/SNZym6YTtSjwRek7kHy1hBo=
X-Google-Smtp-Source: ABdhPJyndacQ1CsO65aQwXGU1f5uuTdH/9KWLrUSGDipcmUqtsmalcgmHCpkA38EsWkxpelpAkKe1S/1/EqG7mr5LXU=
X-Received: by 2002:a67:d11e:: with SMTP id u30mr12638067vsi.187.1591990794496; Fri, 12 Jun 2020 12:39:54 -0700 (PDT)
MIME-Version: 1.0
References: <CANcmUPGaobBb0kXbUeTkXm7WGqB4gXuC08kdmFmhcSNv_bTRHA@mail.gmail.com> <CANcmUPF-WVUEJcGfVQNew8C-tgSKRQF-9aFXRX=J_Y1MOouUjQ@mail.gmail.com> <F0EEEDB5-ADCB-4B93-AB84-347DDF7CAE7A@ericsson.com>
In-Reply-To: <F0EEEDB5-ADCB-4B93-AB84-347DDF7CAE7A@ericsson.com>
From: Jonathan Beri <jmberi@gmail.com>
Date: Fri, 12 Jun 2020 12:39:18 -0700
Message-ID: <CANcmUPHrrTkUsGyFiMr6HaOeMZznhwWGyPkGMq12VwOrVg4agA@mail.gmail.com>
To: Ari Keränen <ari.keranen@ericsson.com>
Cc: "t2trg@irtf.org" <t2trg@irtf.org>
Content-Type: multipart/alternative; boundary="000000000000caad2605a7e83dec"
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/eH-DWCi2KajQp35SDCvxZaZuUNA>
Subject: Re: [T2TRG] OpenAPI/AsyncAPI discussion from April 24th WISHI online meeting
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IRTF Thing-to-Thing Research Group <t2trg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/t2trg>, <mailto:t2trg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/t2trg/>
List-Post: <mailto:t2trg@irtf.org>
List-Help: <mailto:t2trg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/t2trg>, <mailto:t2trg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Jun 2020 19:40:22 -0000

Perfect! I'll have some content to share for the discussion.

On Thu, Jun 11, 2020 at 11:04 PM Ari Keränen <ari.keranen@ericsson.com>
wrote:

> Hi Jonathan,
>
>
>
> Sounds good I think a good way is to continue discussion in the next WISHI
> call. We have this on the draft agenda on the 30th:
>
> https://github.com/t2trg/wishi/wiki/Agenda-items#wishi-online-meeting
>
>
>
> We have folks from W3C WoT joining too.
>
>
>
>
>
> Cheers,
>
> Ari
>
>
>
> On 12.6.2020, 0.51, "T2TRG on behalf of Jonathan Beri" <
> t2trg-bounces@irtf.org on behalf of jmberi@gmail.com> wrote:
>
>
>
> I'd like to continue the discussion around OpenAPI & CoAP. I've been
> spending some time analyzing both CoAP (and related CoRE specs) as well as
> OpenAPI in the hopes to create a report of some sorts, as well as a few
> examples. What's the best way to connect with the other interested parties
> from previous calls, especially as it relates to WoT?
>
>
>
> On Sun, Apr 26, 2020 at 5:06 PM Jonathan Beri <jmberi@gmail.com> wrote:
>
> During the last WISHI meeting I brought up interest in exploring the
> adaptation of API specifications OpenAPI (openapis.org
> <https://protect2.fireeye.com/v1/url?k=92eadff0-cc4a3f6e-92ea9f6b-86ee86bd5107-b06f497f4b53f832&q=1&e=c0cc4f49-fb83-4cad-8754-a238f2e35cbb&u=http%3A%2F%2Fopenapis.org%2F>)
> and AsyncAPI (asyncapi.com
> <https://protect2.fireeye.com/v1/url?k=b1506c03-eff08c9d-b1502c98-86ee86bd5107-e8e3841c4ae29f7e&q=1&e=c0cc4f49-fb83-4cad-8754-a238f2e35cbb&u=http%3A%2F%2Fasyncapi.com%2F>)
> to CoAP. The discussion starts at line 164 of the notes (
> https://hackmd.io/lY_ktzBjTuSu_5oh3u20Bg?both.)
>
>
>
> Michael K. & Michael M. suggested a few action items:
>
> · Create an example Thing Description and see how semantics map to
> OpenAPI/Async
>
> · Identify use cases for developers in WoT, such as Node-Red
>
> · Document scope and overlap between different specs
>
> A few follow-ups from me:
>
> · Are others who weren't on the call interested in collaborating on this
> topic?
>
> · What should be next steps? Should we target an upcoming meeting?
>
> Many thanks.
>
>
>
> --
>
> Jonathan Beri
>
> linkedin.com/in/jonathanberi
> <https://protect2.fireeye.com/v1/url?k=9cf36e3a-c2538ea4-9cf32ea1-86ee86bd5107-8c0e24e45275cac5&q=1&e=c0cc4f49-fb83-4cad-8754-a238f2e35cbb&u=https%3A%2F%2Fwww.linkedin.com%2Fin%2Fjonathanberi%2F>
>
>
>
>
> --
>
> Jonathan Beri
>
> linkedin.com/in/jonathanberi
> <https://protect2.fireeye.com/v1/url?k=d50b335e-8babd3c0-d50b73c5-86ee86bd5107-c668b4b69ca9a23c&q=1&e=c0cc4f49-fb83-4cad-8754-a238f2e35cbb&u=https%3A%2F%2Fwww.linkedin.com%2Fin%2Fjonathanberi%2F>
>


-- 
Jonathan Beri
linkedin.com/in/jonathanberi <https://www.linkedin.com/in/jonathanberi/>

v2.23.0 | Report a Bug | By Email