Fwd: A structured format for dates?

iain hill <iainardernhill@gmail.com> Thu, 25 August 2022 18:47 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E676FC15271B for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 25 Aug 2022 11:47:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.761
X-Spam-Level:
X-Spam-Status: No, score=-2.761 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 xQ41troYrdth for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 25 Aug 2022 11:47:13 -0700 (PDT)
Received: from lyra.w3.org (lyra.w3.org [128.30.52.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99263C147920 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 25 Aug 2022 11:46:55 -0700 (PDT)
Received: from lists by lyra.w3.org with local (Exim 4.94.2) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1oRHqI-00FlyQ-A0 for ietf-http-wg-dist@listhub.w3.org; Thu, 25 Aug 2022 18:44:38 +0000
Resent-Date: Thu, 25 Aug 2022 18:44:38 +0000
Resent-Message-Id: <E1oRHqI-00FlyQ-A0@lyra.w3.org>
Received: from titan.w3.org ([128.30.52.76]) by lyra.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <iainardernhill@gmail.com>) id 1oRHqG-00FlxS-Rt for ietf-http-wg@listhub.w3.org; Thu, 25 Aug 2022 18:44:36 +0000
Received: from mail-wm1-x32b.google.com ([2a00:1450:4864:20::32b]) by titan.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from <iainardernhill@gmail.com>) id 1oRHqF-004lc2-I9 for ietf-http-wg@w3.org; Thu, 25 Aug 2022 18:44:36 +0000
Received: by mail-wm1-x32b.google.com with SMTP id s23so10637082wmj.4 for <ietf-http-wg@w3.org>; Thu, 25 Aug 2022 11:44:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:to:references :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc; bh=sQEa3WjHkBhueNkvF2YviikYSQ3gStQxCY+s8/V9pg0=; b=f/xCwTgtidpeqkyoqKQMqXxkPcdiAFCvEoE3YY73RvXAC/NUULIksdlvSZdcPjuY7m CG2qddU6ESzF+w1rXbZ1ZH0w3gnu9+gtVCindeMutKlX7WrFkpWHOyjW38SGghDGDkfe lovR80SiSyi/brlW3w86XUTtJChCRU9y/CWd8Ir8xCoDlV5GqGhtxRfG4vca5ZeTdntn +gydCv/59o0BHDwZti7PHP1qh0O3p7MBcZUkin0jrbE4oNx9MEXLVJmhhnktGuE/PnsH Go/JNq8QPNXIJ/9NQLXnBNMIhSMZIMxPIAikcwR13iiVzt4jf/6h5zfjeZZZBoBP8Mm9 z9/Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:to:references :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc; bh=sQEa3WjHkBhueNkvF2YviikYSQ3gStQxCY+s8/V9pg0=; b=A/DaSuIZj3kSXRy+6xMpxWy0Tp8lZxTIM13a9Ca4fLkMjrQ1drr9tY5HzKCOf+LRRg B9yDP749vhZ4MvJF5J0+G31eSyGrNRSSxpSC3As/yRZvpyUsIb8B0wjXDIeZ6iYsi4ln W1htz/nxDKnsqrqFVHNDW0osIChic9x9PDGirhcKgTS89jSt2UWJ3ybD3vMOCg90QQff iwOPPCq4SmCdG+Do4yAj2baqejs2pXcK2PM2AXXXzs1H9ygPrhAG7QxvCuH2naMmcJ9C CIy3u1NAI7hS41xPp+d6676JNz4I0Dh/1wczURkYSaTghvehj90b74BrKkt+uDZfvFc5 zTdw==
X-Gm-Message-State: ACgBeo1y3HxVTiFOXC7TT+f8lLTXfc+0CV61G4R+5FGgAUMWI8zmrQb8 8h6c8g4kasUeryMxKgWLJHTmNVmEzcClAQ==
X-Google-Smtp-Source: AA6agR7IhL/uzbREgasd23yMcKyScEsflrAtB6bXukytVxKZvuL8I90ESocEXfp6zhJ/SVJD+ZdOow==
X-Received: by 2002:a05:600c:358f:b0:3a6:145:3500 with SMTP id p15-20020a05600c358f00b003a601453500mr3268431wmq.64.1661453064154; Thu, 25 Aug 2022 11:44:24 -0700 (PDT)
Received: from ?IPV6:2a01:cb1c:abc:de00:b10e:8cf5:3f55:c374? ([2a01:cb1c:abc:de00:b10e:8cf5:3f55:c374]) by smtp.gmail.com with ESMTPSA id o18-20020a05600c511200b003a5dde32e4bsm6394879wms.37.2022.08.25.11.44.23 for <ietf-http-wg@w3.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 25 Aug 2022 11:44:23 -0700 (PDT)
Message-ID: <952a1495-af8b-754a-8c4a-776f933ecd09@gmail.com>
Date: Thu, 25 Aug 2022 20:44:22 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0
Content-Language: en-US
References: <941e7626-5c69-4705-9bbf-ad36048b2291@gmail.com>
To: HTTP Working Group <ietf-http-wg@w3.org>
From: iain hill <iainardernhill@gmail.com>
In-Reply-To: <941e7626-5c69-4705-9bbf-ad36048b2291@gmail.com>
X-Forwarded-Message-Id: <941e7626-5c69-4705-9bbf-ad36048b2291@gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Received-SPF: pass client-ip=2a00:1450:4864:20::32b; envelope-from=iainardernhill@gmail.com; helo=mail-wm1-x32b.google.com
X-W3C-Hub-DKIM-Status: validation passed: (address=iainardernhill@gmail.com domain=gmail.com), signature is good
X-W3C-Hub-Spam-Status: No, score=-4.1
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1oRHqF-004lc2-I9 27e7a0fb8ef68366c68b66bcc7b4912b
X-Original-To: ietf-http-wg@w3.org
Subject: Fwd: A structured format for dates?
Archived-At: <https://www.w3.org/mid/952a1495-af8b-754a-8c4a-776f933ecd09@gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/40355
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <https://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

Oops, I meant to send this to the group, sorry for the duplicate 
Poul-Henning Kamp.


~~~

Poul-Henning Kamp writes:

> Time-nut-PHK would vote for such a proposal, but programmer-PHK would
> be firmly set against it.

If I might be so bold, HTTP is specifically used in conjunction with the 
REST thesis and consiquent paradigm, which is itself clear predisposed 
for use in very large distributed systems, as the web very much is.

I would agree that any local program can and does benefit from having a 
very precise 'local time', however any programmer of distributed 
systems, ought be well aware of the advantages of using a dynamic time 
type rather than a rigid one, as it is the only way to synchronize such 
a system.

> When it comes to computers and timekeeping, "doing it right" has not
> been an option for decades.
Babbage would be horrified; His goal was to remove human introduced 
errors from ephemera calculations.
> Given my painfully extensive experience with my own and other peoples
> time-bugs, I am now firmly in the "Call time(2), use that number,
> as a number, but dont modify it!" camp.

I seems to be the case that this subject need to be thought about far 
more carefully when educating the programming discipline. That said, 
there are still issues in comprehending this subject in the field of 
Astronomy also, so we are far from resting at the inn as yet!

We might consider that the very same issue is also very apparent in race 
conditions, within concurrent code; Seeming somehow to be steeped in 
mystery as a bug, yet in reality it is the exact same problem on a 
different scale.

We are dealing with a distributed system, not any one programmers local 
machine; Acknowledging the existence of different time types seems to me 
to be a fundamental requirement for any system, that is to be scaled, 
over any consequent space and that maintains or uses multiple runtimes.

It would seem to me that we might reasonably conclude that we are very 
far from lucidity on matters of time right now across multiple domains.

Kind regards.

Iain