Re: [Tzdist-bis] draft-tzdist-geolocate tz associated to the point

Daniel Migault <daniel.migault@ericsson.com> Sun, 04 November 2018 03:38 UTC

Return-Path: <mglt.ietf@gmail.com>
X-Original-To: tzdist-bis@ietfa.amsl.com
Delivered-To: tzdist-bis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F394128B14 for <tzdist-bis@ietfa.amsl.com>; Sat, 3 Nov 2018 20:38:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level:
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 5z7Tflx_JcNg for <tzdist-bis@ietfa.amsl.com>; Sat, 3 Nov 2018 20:38:18 -0700 (PDT)
Received: from mail-lj1-f179.google.com (mail-lj1-f179.google.com [209.85.208.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 335B212777C for <tzdist-bis@ietf.org>; Sat, 3 Nov 2018 20:38:18 -0700 (PDT)
Received: by mail-lj1-f179.google.com with SMTP id e5-v6so897115lja.4 for <tzdist-bis@ietf.org>; Sat, 03 Nov 2018 20:38:18 -0700 (PDT)
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:cc; bh=OQs14tLFE66uloJsIrC2Yei8gzeGh8Hx+/UnYT3b75k=; b=aJPOS7ee+xwDxXPBarcC/GqS9PmiV8VNP2l7wte5Tr0EvAFNjijoPGgEiBEAdAwEMq F7Cg6103HZMPAyzVtynbiGHpauFBZo/jXK3Wyh9NgHZo4dKe3JTfiDd+HL7MXYPEt/QO RMKdCCBzksgbI3eBUqnyv8mnvut+P1QlGZ5SEVU3vvap2MurbWEZAzeR4VnYf5ZTEvo9 /lMocQ9KSIqyqsEF8rFO8ydAH6cPIqYIatt4uMBxai15cBuZWk89Z7i4nDyav4xE1lzT q9pS3nMtR6D7TjCDVmJJscT2jKCN1cXDdRBRhCOCg3hE/OkOjxymFtGMT468SaxiObeP yJhA==
X-Gm-Message-State: AGRZ1gKKxKBDgJWdTZQ6QWoSyQlIUMmqnfaJQDOtGZo6fCZXEf9VWRBx koha1mqG+EYXT+g6b3ZqJdnvNMhNJMy/2uJj+cM=
X-Google-Smtp-Source: AJdET5fc+6yqXEHumOLcMXCfuNVXwUn+awGrD1Jecz0ADIxf3FQDk+lqrnbKiFa3qmi9H0Fc2tz40tp29Ze/Yw6qpK8=
X-Received: by 2002:a2e:9059:: with SMTP id n25-v6mr8137436ljg.155.1541302696283; Sat, 03 Nov 2018 20:38:16 -0700 (PDT)
MIME-Version: 1.0
References: <CADZyTkmRBgEvxrnmtjKXSy23McUccE=hHt9bsrdUFq+ZC7UioA@mail.gmail.com> <7581deaa-b386-56af-21a9-7bbd0e7ed983@cs.ucla.edu>
In-Reply-To: <7581deaa-b386-56af-21a9-7bbd0e7ed983@cs.ucla.edu>
From: Daniel Migault <daniel.migault@ericsson.com>
Date: Sat, 03 Nov 2018 23:38:03 -0400
Message-ID: <CADZyTkm1CQv3sy8=K0DsSn2pxg92f1DM+ZdAQ27=Bo_Yf+nZAA@mail.gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: tzdist-bis@ietf.org
Content-Type: multipart/alternative; boundary="000000000000b411e30579ce7f98"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tzdist-bis/Es3Ljw6evgCvgRRfikwIiBJ7GMY>
Subject: Re: [Tzdist-bis] draft-tzdist-geolocate tz associated to the point
X-BeenThere: tzdist-bis@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Extensions to Time Zone Data Distribution Service <tzdist-bis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tzdist-bis>, <mailto:tzdist-bis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tzdist-bis/>
List-Post: <mailto:tzdist-bis@ietf.org>
List-Help: <mailto:tzdist-bis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tzdist-bis>, <mailto:tzdist-bis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Nov 2018 03:38:20 -0000

Hi,

Of course, taken the example of the draft here is the response:

When the client is located in America/New_York the suggestion was
to indicate that America/New_York is the time zone associated to
the location of the point (coordinates provided in the request with
uncertainty set to 0 ) while America/Toronto is the zone in the
50m neighborhood. The response could be for example as follows:

   >> Request <<

   GET /tzdist/zones?location=geo:43.0799,-79.0747;u=50 HTTP/1.1
   Host: tz.example.com
 >> Response <<

   HTTP/1.1 200 OK
   Date: Thu, 09 Nov 2017 13:58:07 GMT
   Content-Type: application/json; charset="utf-8"
   Content-Length: xxxx

   {
     "synctoken": "2860088640-1510059107",
     "timezones": [
       {
         "tzid": "America/New_York",
         "etag": "6602582-1510059107",
         "last-modified": "2017-11-07T12:51:47Z",
         "publisher": "IANA Time Zone Database",
         "version": "2017c",
         "aliases": [
           "US/Eastern"
         ],

         "Is-geoloc-coordinates" : True // tz corresponding to
geo:43.0799,-79.0747

       },
       {
         "tzid": "America/Toronto",
         "etag": "3297806-1510059107",
         "last-modified": "2017-11-07T12:51:47Z",
         "publisher": "IANA Time Zone Database",
         "version": "2017c",
         "aliases": [
           "America/Montreal",
           "Canada/Eastern"
         ],
         "Is-geoloc-coordinates" : False // tz corresponding to the neighborhood
       }
     ]
   }

The discussion should be whether we believe that is useful and maybe
how to tag the parameter.

Yours,

Daniel


On Sat, Nov 3, 2018 at 3:42 PM Paul Eggert <eggert@cs.ucla.edu> wrote:

> Daniel Migault wrote:
> > I believe the last point that needs to be discussed is whether the WG
> > believe we should indicate which time zones are related to the point or
> > not.
>
> Sorry, I've lost context. Could you give an example query and set of
> possible
> results, and use it to illustrate the issue that needs to be discussed?
>
> _______________________________________________
> Tzdist-bis mailing list
> Tzdist-bis@ietf.org
> https://www.ietf.org/mailman/listinfo/tzdist-bis
>