Re: Questiona about timezones

Grahame Grieve <grahame@healthintersections.com.au> Wed, 26 September 2018 11:01 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 0D663130E82 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 26 Sep 2018 04:01:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.651
X-Spam-Level:
X-Spam-Status: No, score=-2.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=healthintersections-com-au.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2GSh7qMaQS6V for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 26 Sep 2018 04:01:45 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [IPv6:2603:400a:ffff:804:801e:34:0:38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12E1D130E81 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 26 Sep 2018 04:01:44 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.89) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1g57XI-0001ve-RE for ietf-http-wg-dist@listhub.w3.org; Wed, 26 Sep 2018 10:59:16 +0000
Resent-Date: Wed, 26 Sep 2018 10:59:16 +0000
Resent-Message-Id: <E1g57XI-0001ve-RE@frink.w3.org>
Received: from mimas.w3.org ([2603:400a:ffff:804:801e:34:0:4f]) by frink.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <grahameg@gmail.com>) id 1g57XC-0001ux-VP for ietf-http-wg@listhub.w3.org; Wed, 26 Sep 2018 10:59:10 +0000
Received: from mail-io1-xd29.google.com ([2607:f8b0:4864:20::d29]) by mimas.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from <grahameg@gmail.com>) id 1g57XB-0003LX-LM for ietf-http-wg@w3.org; Wed, 26 Sep 2018 10:59:10 +0000
Received: by mail-io1-xd29.google.com with SMTP id y10-v6so22869638ioa.10 for <ietf-http-wg@w3.org>; Wed, 26 Sep 2018 03:58:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=healthintersections-com-au.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=5PGdQ/XeRBFJM+f98Mh1/CMjYdPcenpllc4654ZJDlo=; b=s1XQ+3kkSNHHqAnvvnYkvtujPyX3s46urmJb7+j95pMUZGoGhggxTz+uvMjWv+Ipe7 PMkKACPbFPPFsFwwhmcvbvVLlnnQDeLoVgBxBl0qCTqalvEk39SsgFBGRTxN8Z3M9BSN /O6G89KgzAWdvPGb+sQPc8okufzCqdorYVJGko49XHfx9UEm5l7SHklXUponqElHzHDg fpFuXzRgZpg0dxF81GJN4tscgNQeLXoV6EX2sWQPotRz4DpGrXiT+0qu2MFWCykrENSt pYumPwA9VezzMYCx4yqyZWyJj/rggZOhq2P8y27swoHBif6WGpuS9SMawsRoKu7l828n kKRw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=5PGdQ/XeRBFJM+f98Mh1/CMjYdPcenpllc4654ZJDlo=; b=VcenUztPvwIfiG5zLg/hCQdUZOLcaMo5FWksXQgsMvY43JPAizyTnYToBxiajrvgy7 6u6UThM+4z/nGep780rIordoEyFmciEvl99h5UgoIXbqJZgk5Q8zV8tgMQsrICl/X6AJ j01mYVNpSx3wuh9/PgdMgegY8s9T64A0hmobgdWsLdZ7Qxkhh7f1Q5jheCVYKkGROnZL aXR2x9uzsWzClmn0IPeRwXHK1poEbEmpAz93kERrsw2aXFchg56J+idEj2RlvhMl5zVy 7Kcqw0J+uaHIWDnOucy7d6P21ypfyt0uwrJNzOzIlZHrkmo7qTy144xOAUcthqVc58/f uP7g==
X-Gm-Message-State: ABuFfohetefkMC1O6AyXb9eAASQJlza5kKTwS2Ad0R2ZxuJnRa9+RvSh UR45b9DxqDuAlxatHf9dzwpMn7QnN1uiWFr2v8A=
X-Google-Smtp-Source: ACcGV61A4nJMRwdDsKaZnrvZpcZRLpW/430/xHlbT3GYGpnZvj0aI5gatOM1DirDZo0vcNiLPNqkCDoW5yAhyhoUeF4=
X-Received: by 2002:a6b:c744:: with SMTP id x65-v6mr4477028iof.208.1537959528670; Wed, 26 Sep 2018 03:58:48 -0700 (PDT)
MIME-Version: 1.0
References: <CAG47hGZ+CMTqqLf86kjSdsxgUtM1cLYS12TasPLOJNrOieqe0g@mail.gmail.com> <0aaebac2-f2b3-66f7-5cf2-58a46192bc16@cisco.com> <CAG47hGbyjS+ge0y0xMFJjzuT3yU1StWNq=MPmQmH4-TN9dN5sw@mail.gmail.com> <19e6e5f6-eec1-3b1c-fea0-800611089713@cisco.com>
In-Reply-To: <19e6e5f6-eec1-3b1c-fea0-800611089713@cisco.com>
From: Grahame Grieve <grahame@healthintersections.com.au>
Date: Wed, 26 Sep 2018 20:58:36 +1000
Message-ID: <CAG47hGZCkLP=uSShwbwN3B72dgsy8NF+G_uW=tcEwYwh-hM-AQ@mail.gmail.com>
To: lear@cisco.com, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="00000000000062ac450576c41b0b"
X-W3C-Hub-Spam-Status: No, score=-2.7
X-W3C-Hub-Spam-Report: AWL=1.708, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, W3C_AA=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1g57XB-0003LX-LM fc153927630f9afbb73c977649cfa086
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Questiona about timezones
Archived-At: <https://www.w3.org/mid/CAG47hGZCkLP=uSShwbwN3B72dgsy8NF+G_uW=tcEwYwh-hM-AQ@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/35930
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>

whoops - slipped off the list :-(

> How do the system libraries dig out the information?
>
> For TZ information about one's own host, can you not use
> Intl.DateTimeFormat().resolvedOptions().timeZone gets you the
> information to pass in a form? and then on the server side there's
> datetime/DateTime (python/PHP, respectively) that you can build into
> HTML to be passed to client JS.  But again, that's HTML/JS that would
> have to be layered on top whatever JSON API you were building.
>

form variables. We could put it in the json.. but this degrades the
stability
of the json with what is context information

Some one else asked: geolocation - when correct - is not reliable anyway.
The web server might be a facade located differently from the actual
clinical
system, but the actual clinical system might also be located in multiple
timezones (e.g. multi-homed).

> We believe that we need a way for the client and server to communicate
> > with each other about their timezones, and we think that it should be
> > in the http headers. We're surprised that this hasn't come up more
> > widely...
>
> Ok.  That draft, of course, only goes in one direction


yes we would probably use it in both...

thanks
Grahame