Re: [httpapi] Towards a hal+json RFC
Erik Wilde <erik.wilde@dret.net> Tue, 03 October 2023 09:35 UTC
Return-Path: <erik.wilde@dret.net>
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 E4174C1519B7 for <httpapi@ietfa.amsl.com>; Tue, 3 Oct 2023 02:35:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.091, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ypHzeqLdB0ga for <httpapi@ietfa.amsl.com>; Tue, 3 Oct 2023 02:35:19 -0700 (PDT)
Received: from mxout017.mail.hostpoint.ch (mxout017.mail.hostpoint.ch [IPv6:2a00:d70:0:e::317]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91918C14CE30 for <httpapi@ietf.org>; Tue, 3 Oct 2023 02:35:18 -0700 (PDT)
Received: from [10.0.2.45] (helo=asmtp012.mail.hostpoint.ch) by mxout017.mail.hostpoint.ch with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.96 (FreeBSD)) (envelope-from <erik.wilde@dret.net>) id 1qnboB-000FBa-33; Tue, 03 Oct 2023 11:35:15 +0200
Received: from [185.189.200.50] (helo=[10.200.8.127]) by asmtp012.mail.hostpoint.ch with esmtpa (Exim 4.96 (FreeBSD)) (envelope-from <erik.wilde@dret.net>) id 1qnboB-0001HF-2U; Tue, 03 Oct 2023 11:35:15 +0200
X-Authenticated-Sender-Id: erik.wilde@dret.net
Message-ID: <db12ee22-6816-e3e8-cb0d-6d9d1b85197d@dret.net>
Date: Tue, 03 Oct 2023 10:35:15 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.15.1
Content-Language: en-US
To: Mike Kelly <mikekelly321@gmail.com>, httpapi@ietf.org
References: <CANqiZJYb7iiRnkMXyVKXDTuqVCyuutzoArRxg_h653V8nzE+Tg@mail.gmail.com>
From: Erik Wilde <erik.wilde@dret.net>
In-Reply-To: <CANqiZJYb7iiRnkMXyVKXDTuqVCyuutzoArRxg_h653V8nzE+Tg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Vs-State: 0
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/nZjcsFuGyEcnPBcNkg2OrwCg7tk>
Subject: Re: [httpapi] Towards a hal+json RFC
X-BeenThere: httpapi@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 03 Oct 2023 09:35:24 -0000
hello. On 2023-10-03 11:25, Mike Kelly wrote: > I think hal+json has been around long enough and seen enough usage that > it's reasonable to establish it as an RFC. I've had many requests from > third parties to make this happen. > My aim is to get this to RFC without making any changes that would break > existing deployments. > If this is not appropriate for this group, I'd appreciate some pointers > on the most time efficient way I can get this to RFC status. i think this is appropriate and generally speaking, i am in favor. i am sufficiently much in favor that i started an effort a little while ago, the remnants of which can be found here: https://github.com/dret/I-D/tree/master/Abandoned/web-hal the issue i was addressing is that there are problematic areas in HAL from an interop perspective and that it would be useful to point these out to potential adopters. in the end there wasn't enough interest to take this forward, but if there is now then maybe that's some interesting context. cheers, dret. > > Many thanks, > Mike > -- Erik Wilde | mailto:erik.wilde@dret.net | | https://youtube.com/ErikWilde |
- [httpapi] Towards a hal+json RFC Mike Kelly
- Re: [httpapi] Towards a hal+json RFC Erik Wilde
- Re: [httpapi] Towards a hal+json RFC Mike Kelly
- Re: [httpapi] Towards a hal+json RFC Graham Cox
- Re: [httpapi] Towards a hal+json RFC Mike Kelly
- Re: [httpapi] Towards a hal+json RFC Darrel Miller
- Re: [httpapi] Towards a hal+json RFC Mike Kelly
- Re: [httpapi] Towards a hal+json RFC Darrel Miller
- Re: [httpapi] Towards a hal+json RFC Mike Kelly
- Re: [httpapi] Towards a hal+json RFC Darrel Miller
- Re: [httpapi] Towards a hal+json RFC Mike Kelly
- Re: [httpapi] Towards a hal+json RFC Mike Kelly
- Re: [httpapi] Towards a hal+json RFC Kévin Dunglas
- Re: [httpapi] Towards a hal+json RFC Mike Kelly
- Re: [httpapi] Towards a hal+json RFC Darrel Miller
- Re: [httpapi] Towards a hal+json RFC Mike Kelly
- Re: [httpapi] Towards a hal+json RFC Darrel Miller
- Re: [httpapi] Towards a hal+json RFC Mike Kelly
- Re: [httpapi] Towards a hal+json RFC Darrel Miller
- Re: [httpapi] Towards a hal+json RFC Mike Kelly
- Re: [httpapi] Towards a hal+json RFC Alexander Zeitler
- Re: [httpapi] Towards a hal+json RFC Mike Kelly