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

Re: Revising Structured Fields: scope

From: Julian Reschke <julian.reschke@gmx.de>
Date: Thu, 13 Oct 2022 09:17:43 +0200
Message-ID: <a1bdde28-c8e0-e8a9-6658-a80775b75f9e@gmx.de>
To: Mark Nottingham <mnot@mnot.net>
Cc: ietf-http-wg@w3.org
Am 13.10.2022 um 07:54 schrieb Mark Nottingham:
> Hi Julian,
>
>> On 13 Oct 2022, at 4:42 pm, Julian Reschke <julian.reschke@gmx.de> wrote:
>>
>> +1 on all points, except for the one about ABNF. The referenced
>> statement is about how to define Structured Fields in other specs; it
>> doesn't really say anything about why the use of ABNF *inside* the SF
>> spec would be a bad idea.
>>
>> FWIW, as implementer of the spec the ABNF made things easier for me; I
>> understand that people who do not use ABNF a lot might feel different.
>> But if it ain't broke, don't fix it.
>
> Now I'm even more concerned -- the spec is explicit that you shouldn't be using the ABNF to implement, you should be using the algorithms.

Define "use". Is reading the ABNF a "use for implementation"?

(and yes, I followed the algorithms in my impl, and it passes the test
suite)

Best regards, Julian
Received on Thursday, 13 October 2022 07:18:01 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 28 January 2023 21:29:46 UTC