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

Re: A structured format for dates?

From: Mark Nottingham <mnot@mnot.net>
Date: Thu, 16 Jun 2022 14:23:30 +1000
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <623002F5-C5B7-478F-9D8F-2B71EABFD87E@mnot.net>
To: Glenn Strauss <gs-lists-ietf-http-wg@gluelogic.com>
Hi Glenn,

> On 16 Jun 2022, at 2:18 pm, Glenn Strauss <gs-lists-ietf-http-wg@gluelogic.com> wrote:
> 
> On Thu, Jun 16, 2022 at 11:54:26AM +1000, Mark Nottingham wrote:
>> I'd love to hear what people think about this issue:
>>  https://github.com/httpwg/http-extensions/issues/2162
>> 
>> In a nutshell, the idea is to define a new structured type for dates, so that instead of e.g.,
>> 
>>  SF-Date: 784072177
>> 
>> we'd have:
>> 
>>  SF-Date: @1994-11-06T08:49:37Z 
>> 
>> ...as the textual representation. Obviously, if we ever do binary structured fields, its representation there could be more efficient.
>> 
>> Thoughts?
> 
> +1 for ISO 8601 date format with 24-hour time notation (RFC 3339)
>   (without the '@' ?)

Structured fields requires a sigil character to identify a type in the textual representation -- `@` seems appropriate for a date.

Cheers,



--
Mark Nottingham   https://www.mnot.net/
Received on Thursday, 16 June 2022 04:23:50 UTC

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