Re: [httpapi] Towards a hal+json RFC
Graham Cox <graham@grahamcox.co.uk> Tue, 03 October 2023 11:48 UTC
Return-Path: <graham@grahamcox.co.uk>
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 D1B31C17EE12 for <httpapi@ietfa.amsl.com>; Tue, 3 Oct 2023 04:48:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.903
X-Spam-Level:
X-Spam-Status: No, score=-6.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=grahamcox-co-uk.20230601.gappssmtp.com
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 QIe092Vlr97f for <httpapi@ietfa.amsl.com>; Tue, 3 Oct 2023 04:48:34 -0700 (PDT)
Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com [IPv6:2607:f8b0:4864:20::42e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 4420AC17EE11 for <httpapi@ietf.org>; Tue, 3 Oct 2023 04:48:33 -0700 (PDT)
Received: by mail-pf1-x42e.google.com with SMTP id d2e1a72fcca58-690ba63891dso587777b3a.2 for <httpapi@ietf.org>; Tue, 03 Oct 2023 04:48:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=grahamcox-co-uk.20230601.gappssmtp.com; s=20230601; t=1696333713; x=1696938513; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=zD7Kz32aItWSxlt4IDm9j0SB47DDmbVsPou1UBwmS+s=; b=tncZm1aAMGz/hpNQr8yG8XryKaw5aHXWOXKotJ+tiuu5UupD9suJtzSPu3e6PylKql 3InrifKakQOjV8x/Sm91b6oBqgg1/f9nm9DrIBoKh8cP1z86zi5Ep5UiZyCRoZCmTZwS 4n1C8HGlD7OHiLS1OQLuUIaTFWNIrrB8Jbe3CAnJoeQiZWkZAlU43noqEWOZq6NWNsNE ZdXledpymYaCiaxlB5GR8a4iidABIgrMh4p8w/ASGawaBJYNQQwgLZBNrFsBWmQ7HhZE UoaLxKV6Z1cSZE/sF4EjMB5l5sCMszKlQBbRjODkmeQFAssgkKDxOx1hvvOIxMe2AsVJ TwXw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696333713; x=1696938513; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=zD7Kz32aItWSxlt4IDm9j0SB47DDmbVsPou1UBwmS+s=; b=ZdnJOQj+x1izhJpzvRkxhqbnMxQ0zuPJWpTX7A/LPDGDCeak3XQq6mHa/pCCmMMIos KmVXCpc036rKmr2guXBNr7yjygqklAHPKqCCIGLkwRMqUrk92jgV/Q+F++raxxFX+TOH CVvu3FTLLPEgcjiZKSIbOOmQBPWD9tGDHhXMaDsFYfKSFtKXO/bDW0tPvNeuRWXQYYp9 AOxfdnBMkeRLiAxCy7MfbX8bRF+fimiv9RdrkujmI1DVqJCWMDe/4eSNB5InwUQlJBHz srWf2Vkz4uxNL0Y5+ye+/cyZn0DGn9Q+KX3ilIaNpqKF1DztHn4qkirap+MkKyzRmMMx sphg==
X-Gm-Message-State: AOJu0Yx6Sx+bQ2jOLvCd7wBx5bwsB3P+2vCgmdkKguza6LijoTX19nJV EYKHddJsV/9zc4wvoea4CHdDoY15B5Oi5W5IPAXtUHpXG8GCmsV1
X-Google-Smtp-Source: AGHT+IGDy1Hz6Lt08rZEdgMnPy5DbNOHsKKfnY3hoHa/H79zYH1KXNktAb90j1ojtlFWfJQAQDecJp8j8nvrPhOpuJI=
X-Received: by 2002:a05:6a00:13a7:b0:690:c75e:25d7 with SMTP id t39-20020a056a0013a700b00690c75e25d7mr14508368pfg.18.1696333713077; Tue, 03 Oct 2023 04:48:33 -0700 (PDT)
MIME-Version: 1.0
References: <CANqiZJYb7iiRnkMXyVKXDTuqVCyuutzoArRxg_h653V8nzE+Tg@mail.gmail.com> <db12ee22-6816-e3e8-cb0d-6d9d1b85197d@dret.net> <CANqiZJY4hYhvG3SPPM9gicevP0fonaQtWZD2o5nNMEa+CSdehg@mail.gmail.com>
In-Reply-To: <CANqiZJY4hYhvG3SPPM9gicevP0fonaQtWZD2o5nNMEa+CSdehg@mail.gmail.com>
From: Graham Cox <graham@grahamcox.co.uk>
Date: Tue, 03 Oct 2023 12:48:23 +0100
Message-ID: <CAPBurBsM+DX8kEHgxgVt1B00idb6Zb1ZTB6pK1UWD39pFOaYNQ@mail.gmail.com>
To: Mike Kelly <mikekelly321@gmail.com>
Cc: Erik Wilde <erik.wilde@dret.net>, httpapi@ietf.org
Content-Type: multipart/alternative; boundary="0000000000006391000606ce7887"
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/g7hiXzLfFMvjvHe0II-CcU2PS3s>
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 11:48:37 -0000
This may well be out of scope, but would there be any interest in pulling something like HAL-FORMS into the core HAL spec? ( https://rwcbook.github.io/hal-forms/) One of the hugely beneficial parts of hypermedia (IMO) is for the server to indicate to the client what actions can be performed, and how to do so. This is the major thing that pure HAL is lacking, but could be relatively easily folded in by the inclusion of the "_templates" entries, and could be seen as a non-breaking change - it's only a concern if existing HAL implementations happen to be using this key as a private response field. Cheers On Tue, 3 Oct 2023, 10:46 Mike Kelly, <mikekelly321@gmail.com> wrote: > Hi Erik, > > Thanks for this, it's useful background. > > The latest version of the I-D addresses the curies vs CURIEs issue by > removing reference to the CURIEs standard altogether and providing a > standalone definition of "curies" within the hal specification. This seems > the best way to keep aligned with the set of existing behaviour in the > wild, and is in keeping with the design goals of hal of simplicity and > cogency. > > Cheers, > M > > On Tue, Oct 3, 2023 at 10:35 AM Erik Wilde <erik.wilde@dret.net> wrote: > >> 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 mailing list > httpapi@ietf.org > https://www.ietf.org/mailman/listinfo/httpapi >
- [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