W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2022

Re: Draft for Resumable Uploads

From: Martin J. Dürst <duerst@it.aoyama.ac.jp>
Date: Wed, 6 Apr 2022 08:04:47 +0900
Message-ID: <3111bf76-152f-90ac-db9c-2f8f0372a91e@it.aoyama.ac.jp>
To: Mark Nottingham <mnot@mnot.net>, Guoye Zhang <guoye_zhang@apple.com>
Cc: "Julian F. Reschke" <julian.reschke@gmx.de>, Eric J Bowman <mellowmutt@zoho.com>, ietf-http-wg <ietf-http-wg@w3.org>

On 2022-04-06 07:17, Mark Nottingham wrote:
>> On 6 Apr 2022, at 5:22 am, Guoye Zhang <guoye_zhang@apple.com> wrote:
>> I was exaggerating a bit, but I have no idea how to PATCH a resource after reading RFC5789, it just introduces a general concept and leaves nearly everything open to implementations. That’s why I believe we need further standards for any concrete use.
> PATCH intentionally leaves everything up to the media type of the PATCH request, not the implementation. With hindsight, at least one or two well-defined PATCH media types should have been defined at the same time as 5789 - their absence (especially JSON's) created a lot of confusion.

Has that confusion now cleared, or is there a way to clear it?

Regards,   Martin.

> Cheers,
> --
> Mark Nottingham   https://www.mnot.net/
Received on Tuesday, 5 April 2022 23:05:06 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:44:07 UTC