Re: [httpapi] Towards a hal+json RFC

Mike Kelly <mikekelly321@gmail.com> Tue, 03 October 2023 12:18 UTC

Return-Path: <mikekelly321@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 1FD5AC193334 for <httpapi@ietfa.amsl.com>; Tue, 3 Oct 2023 05:18:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.854
X-Spam-Level:
X-Spam-Status: No, score=-1.854 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=gmail.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 pBY-ot0Z5I2i for <httpapi@ietfa.amsl.com>; Tue, 3 Oct 2023 05:18:11 -0700 (PDT)
Received: from mail-io1-xd2d.google.com (mail-io1-xd2d.google.com [IPv6:2607:f8b0:4864:20::d2d]) (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 301BBC193333 for <httpapi@ietf.org>; Tue, 3 Oct 2023 05:18:11 -0700 (PDT)
Received: by mail-io1-xd2d.google.com with SMTP id ca18e2360f4ac-79fb8f60374so6766539f.1 for <httpapi@ietf.org>; Tue, 03 Oct 2023 05:18:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1696335490; x=1696940290; 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=PPOaJYF5aWEpysTL957ykgCVPihbq8rOy9Ecm5FGhPc=; b=S3ZxI+iYZqABsG/ID8UuHqhw7SrOOrlklobDA/XmVaadaEEzEK5lOog52+zXhnRecm KeNx0up4NaB8nb55OH8Z0c18B1NCqUBY06qrEhU5MrfdF+kT+5w+TtV+oVF9zs1+2Qz1 SDPO55o6ueD1Ic7gRfvYRyuBzeHLB1mtRCfJGQwk0DZkpr0bj4ob77gV+ZEzpHzwUEHv Jy+Ahog1SuFsUF8GJGMDvp6eH/Cakn84i1SQSzLxbEAEi98LoIUZaH707cvU/kPzeQOm 4RVKH0tjVaFMjcy0EdE+nFuCQtPyRc2YB3fllCfWGLUsaCMJyy5HPxp81ry/DiOjl/N9 ThNg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696335490; x=1696940290; 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=PPOaJYF5aWEpysTL957ykgCVPihbq8rOy9Ecm5FGhPc=; b=SGz3jw0vhezMS2uWJRII6J4r3ODB114wP6awuZuL5YiflKi8Bd9vM+BRuTaEQm9Ma7 5viiOfROxTe+3A3FPVIIaQPxqVeczvrg7n7AKntzkRrBOVWl/dA/9AmUc9/RBHWjJAF4 dG0oTdhnQ1A8N+JosoMKLU8Mbt+xtOG5UIbLQHSzlObUNcmbAPgsbpZv9FlMu3Orkagb Vs+bbngkCENz4YtW+NrH5z2XTawh7Y6M25McXAnZ+vVoPXHZROcFmCPHOeVT663gy0Xh sUTGD7wPbPmyWcT0g6p5cgHOAJ9mKClnLJOdTF+HidqXCNYL9yVhyhPRu3Tjr8SSaJYD bD3Q==
X-Gm-Message-State: AOJu0YwgXmITRdw5QUzhF8LoTowtLxHdTkjf62CeeSYWKYabS1nJW6SZ PO/pDIfuoE4IWtZQIOGF0jws6dvVSgOUe4EP5CcifSMxee4=
X-Google-Smtp-Source: AGHT+IFlFSN5xN2TIeD9C5UjbEhbuFmjmu2cOTrcG3FoMw0sYInLIUJLOAPFkiobf09ZEaZQmAClPWclUfuh/51lZ9o=
X-Received: by 2002:a05:6e02:ca3:b0:352:a3f5:6314 with SMTP id 3-20020a056e020ca300b00352a3f56314mr72502ilg.0.1696335490142; Tue, 03 Oct 2023 05:18:10 -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> <CAPBurBsM+DX8kEHgxgVt1B00idb6Zb1ZTB6pK1UWD39pFOaYNQ@mail.gmail.com> <6ab7add0-b459-569b-1a4b-7c84500e8c1a@pdmlab.com>
In-Reply-To: <6ab7add0-b459-569b-1a4b-7c84500e8c1a@pdmlab.com>
From: Mike Kelly <mikekelly321@gmail.com>
Date: Tue, 03 Oct 2023 13:17:57 +0100
Message-ID: <CANqiZJbymVM_3-vWE-ofdsqp9kFActOrDM8WBeSpq3E=7zu+Jw@mail.gmail.com>
To: Alexander Zeitler <alexander.zeitler@pdmlab.com>
Cc: "httpapi@ietf.org" <httpapi@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004f56de0606cee2bc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/x9IHv9WIRoY2c-G-DmV72eTnfN0>
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 12:18:15 -0000

Hi Alexander,

Is there a reason that the HAL-FORMS media type isn't sufficient for your
purposes?

Cheers,
M

On Tue, Oct 3, 2023 at 1:15 PM Alexander Zeitler <
alexander.zeitler@pdmlab.com> wrote:

> I would find this extension useful too
>
> On 03.10.23 13:48, Graham Cox wrote:
>
> 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 mailing list
> httpapi@ietf.org
> https://www.ietf.org/mailman/listinfo/httpapi
>