[httpapi] Introduction
Christoph Kappestein <christoph.kappestein@gmail.com> Sat, 09 January 2021 12:10 UTC
Return-Path: <christoph.kappestein@gmail.com>
X-Original-To: httpapi@ietfa.amsl.com
Delivered-To: httpapi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 839B53A1241 for <httpapi@ietfa.amsl.com>; Sat, 9 Jan 2021 04:10:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, 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 JG_3Xn966VOR for <httpapi@ietfa.amsl.com>; Sat, 9 Jan 2021 04:10:45 -0800 (PST)
Received: from mail-lf1-x12a.google.com (mail-lf1-x12a.google.com [IPv6:2a00:1450:4864:20::12a]) (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 2F8E33A123D for <httpapi@ietf.org>; Sat, 9 Jan 2021 04:10:45 -0800 (PST)
Received: by mail-lf1-x12a.google.com with SMTP id u25so8709454lfc.2 for <httpapi@ietf.org>; Sat, 09 Jan 2021 04:10:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=hA2LEX5me6BG6qnKfScCFGDaNYuJtWruAO2a9Ue8xKY=; b=p22xhrE0fUM2LH4Bws57P+vqbKEHplRGxloRvkTH5zbnQbcdDqkZcfSukZ2dZQ9LSO /9IIJeNfzkcCLYX82TDgYz7c9A6P8OUHHdbgg5fTTNB34JnLIdXYsXKO5yyhY6iyvg6z MgWGvvPHBvz6EE66hl0I9XSNV2iAW7PqTCwJ6zRkoIoJtp7nEx8obYN8Y6HoNUdmmp8h kL0taL7c/VLugaQEI7RyHHk70PS/jCOBnc3nfo8ysfnmZCDSqPie1OisOyBfJv4RjAYV ZUIw3HwOm2S6M5CqlBq9Z71j21TSWNTuQKQ69VYIziLvY46g4xXtYV4ciQ+/zD4x/7vD AvTQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=hA2LEX5me6BG6qnKfScCFGDaNYuJtWruAO2a9Ue8xKY=; b=ICsAEvuIJ+MdpgzVQug8sxtTpScR8K9qbDa0z0rO3GW9qLuhM7uc6OzNoDimDb7kT/ 3Ll8FdmnrI99BG4T1BAWExGt90KmPGTRRAvujwZm8GyMETcwEgvmxLcQNr8xKCkZh2jf JyjIFA7G6OCUFJ6Uzfp5n9OSKOdPw8S1ad80Q4QwF2Xd6pQxrY0FNWYWLZk/2CEEm3ye faQWkTMDWdZuLbU+aj8FrlzGvZ+eeaUKBXU1i1hIxyD3Om9CNYA6iYzjftlyn4n7mQpN tuJ37aEx5Kk3AYWmN+odfJt3SGsaKmWL1NyV2fGtsECqB7Taw/HgYhL0t+g5+BsakKyc qaBA==
X-Gm-Message-State: AOAM531qYPUktCw0Myn7gf1FbpHBYHYRIzreu9cUFj3k79J7+pmrwpp9 jpJhZIGHHfTUQG5RZJ3LvzGEiaM8r/TcqKYQDQrq0hbF
X-Google-Smtp-Source: ABdhPJwoRJjUcf7NB5k3VqWgIPFZvqjOw3RHBIY3znAbS6uQ7+0g9wBu9J9pn3ausOtkJ36e7LCp5zlEKYCTomwGubs=
X-Received: by 2002:a2e:850b:: with SMTP id j11mr3613078lji.84.1610194242735; Sat, 09 Jan 2021 04:10:42 -0800 (PST)
MIME-Version: 1.0
Received: by 2002:ab3:6f03:0:0:0:0:0 with HTTP; Sat, 9 Jan 2021 04:10:42 -0800 (PST)
From: Christoph Kappestein <christoph.kappestein@gmail.com>
Date: Sat, 09 Jan 2021 13:10:42 +0100
Message-ID: <CALcRZn4YSC9w4VA7J=UfEoUrKDLwfoTTU38GHA5CQ9xdHVPDhA@mail.gmail.com>
To: httpapi@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/a4zH4rzLjA6y0WQkNlx_Lqa4BTg>
Subject: [httpapi] Introduction
X-BeenThere: httpapi@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Building Blocks for HTTP APIs <httpapi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/httpapi>, <mailto:httpapi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/httpapi/>
List-Post: <mailto:httpapi@ietf.org>
List-Help: <mailto:httpapi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/httpapi>, <mailto:httpapi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Jan 2021 13:44:21 -0000
Hello, my name is Christoph I am a developer in the API space and I just found out about this Working-Group through this video https://www.youtube.com/watch?v=vyeEqJNKq6Y I am happy to see some process in this space. Currently we are working on a JSON format called TypeSchema (https://typeschema.org/) which describes JSON payloads and is optimized for code generation. We have started this since there is currently no great standard which describes JSON payloads and is optimized for code generation. So if this a topic which you want address I would be happy to share my experiences. In general we are also working on an open source API management product called Fusio s. https://github.com/apioo/fusio so we are also interested in other standards like i.e. the Deprecation header which we plan to implement, currently we simply issue a standard "Warning" header to inform developers that an API is deprecated, but it is great to see that there is now a dedicated header for this. I am not too familiar with the process to comment an RFC but is there in general a form where I can provide written feedback to existing specifications or is this done through this mailing list? best regards Christoph
- Re: [httpapi] Introduction Julian Reschke
- [httpapi] Introduction Christoph Kappestein
- Re: [httpapi] Introduction Salz, Rich
- Re: [httpapi] Introduction Erik Wilde
- Re: [httpapi] Introduction Christoph Kappestein
- Re: [httpapi] Introduction Salz, Rich
- Re: [httpapi] Introduction Erik Wilde