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

Re: structured headers "why not JSON" FAQ

From: Julian Reschke <julian.reschke@gmx.de>
Date: Wed, 13 Jun 2018 10:53:28 +0200
To: Mark Nottingham <mnot@mnot.net>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <2d8fac53-0a7d-679c-acf9-2705e02319f1@gmx.de>
On 2018-06-13 10:38, Mark Nottingham wrote:
> 
> 
>> On 13 Jun 2018, at 6:33 pm, Julian Reschke <julian.reschke@gmx.de> wrote:
>>
>> On 2018-06-13 10:01, Mark Nottingham wrote:
>>> ...
>>>> Please elaborate. What are the difficulties, and how is this different in structured headers?
>>> How can you use ABNF to define the allowable structures in JFV? See the editors' draft of SH for an example there (a work in progress).
>>
>> Precisely which part?
> 
> https://httpwg.org/http-extensions/draft-ietf-httpbis-header-structure.html#specify

Ah. There are two things here.

1) Overall header field syntax: this is not needed for JFV, because it's 
always the same, see ABNF at the end of 
<https://greenbytes.de/tech/webdav/draft-reschke-http-jfv-08.html#data-model-and-format>.

2) Constraints on specific field values - that could be done the same 
way as in structured headers.

> ...

Best regards, Julian
Received on Wednesday, 13 June 2018 08:54:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:15:21 UTC