IETF Logo Mail Archive

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

Jonathan Beri <jmberi@gmail.com> Thu, 11 June 2020 21:51 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 8DF9D3A0A85 for <t2trg@ietfa.amsl.com>; Thu, 11 Jun 2020 14:51:17 -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 gSrHSzjhqx87 for <t2trg@ietfa.amsl.com>; Thu, 11 Jun 2020 14:51:15 -0700 (PDT)
Received: from mail-vs1-xe35.google.com (mail-vs1-xe35.google.com [IPv6:2607:f8b0:4864:20::e35]) (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 BADA83A0A84 for <t2trg@irtf.org>; Thu, 11 Jun 2020 14:51:15 -0700 (PDT)
Received: by mail-vs1-xe35.google.com with SMTP id j13so4239669vsn.3 for <t2trg@irtf.org>; Thu, 11 Jun 2020 14:51:15 -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; bh=UGPrjEDya7m0PQ3TSUnjQz4M8CR1weYsTzlN8c6lGf4=; b=Ai//wqrRpqUaYS5o5yjlqzHRU1p54SDmH1s8HFWReGHxBNHd5/FnEmN/iF/wgT2uFP qcQqGMP16DMuTd6zoazsd3VsPVk4dmTAXk4qGTpXVJS8wLBmeQegGWAWh4swki+L0ann rsqiJpUH1biUD6ZC0OvjWvlx2PkkW1kF7wi591gt0tE+d5TREtNTZr8Zi/z+n1emxDxG ahcxgSnDmv60IoN9DLNy5HaibJXlJOnpHPg/MoLbG3cPb4fgHR7RGXFb/9PtujgeCLA3 vHLBhScOzt9v5biJRXA8tB9YDr+OIbS7+cNbgF6J6ZrTKYJl2gyV0uzOlKHJbAA9WWs+ ysBg==
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; bh=UGPrjEDya7m0PQ3TSUnjQz4M8CR1weYsTzlN8c6lGf4=; b=XCsaKJixGcWsvhNHakYx/JRn2Az74nx4bJEfHwSiTmktFON39YrGJZgn/nkUSIIg5v yahhtSsAJr05Eaul3PssbSPsMj5LQ6OKbSsoA5HfVRbVJes0zWleJoOiMrWpVjvyM4E9 XAKOCz7L776L1ptA73ygNjEucEkzemr30ROcG2WtZp0S4gW++g6lnqtsQJSrf8EOOT0w oYRNxsRQQ6PoO8XhimYJeRMXyefd3HWH3ScXGLZekYiMXODe8i5x7pBiGXPeuEqmkkdx uOIDbutOJh7equfNPGcb36K19kVtobImpQLVeSVaYzh3ysMBb2bz6TxLll4wt0QmP3/w JCGQ==
X-Gm-Message-State: AOAM531pgHrsyv3P0yD64LhSQqdY6pACip3+gvQlnxto4eoqBA07HJQf Oh0shKOQ+8ldgm+8YUMycTQORMEb3x5bJnjfme5Wvk7f
X-Google-Smtp-Source: ABdhPJxAJPuHpBrYoEG3Kq8JMAN9eD1BcfSNugqEZW8Cd08iapGZAzifExMpkTwa7+Y39w0iPwwk8wLBC8q/2KrM3u0=
X-Received: by 2002:a67:2c4c:: with SMTP id s73mr8418233vss.233.1591912274131; Thu, 11 Jun 2020 14:51:14 -0700 (PDT)
MIME-Version: 1.0
References: <CANcmUPGaobBb0kXbUeTkXm7WGqB4gXuC08kdmFmhcSNv_bTRHA@mail.gmail.com>
In-Reply-To: <CANcmUPGaobBb0kXbUeTkXm7WGqB4gXuC08kdmFmhcSNv_bTRHA@mail.gmail.com>
From: Jonathan Beri <jmberi@gmail.com>
Date: Thu, 11 Jun 2020 14:50:39 -0700
Message-ID: <CANcmUPF-WVUEJcGfVQNew8C-tgSKRQF-9aFXRX=J_Y1MOouUjQ@mail.gmail.com>
To: t2trg@irtf.org
Content-Type: multipart/alternative; boundary="0000000000009cfe7405a7d5f5d8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/r5-CzpCA563_euAqz70ycNkykSc>
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: Thu, 11 Jun 2020 21:51:18 -0000

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) and AsyncAPI (
> asyncapi.com) 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://www.linkedin.com/in/jonathanberi/>
>


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

v2.23.0 | Report a Bug | By Email