[Geojson] Requests for comments on GeoJSON Events draft

Sean Gillies <sean.gillies@gmail.com> Wed, 04 January 2017 09:32 UTC

Return-Path: <sean.gillies@gmail.com>
X-Original-To: geojson@ietfa.amsl.com
Delivered-To: geojson@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5BC7127735 for <geojson@ietfa.amsl.com>; Wed, 4 Jan 2017 01:32:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ty45RQwbtztC for <geojson@ietfa.amsl.com>; Wed, 4 Jan 2017 01:32:39 -0800 (PST)
Received: from mail-yw0-x22d.google.com (mail-yw0-x22d.google.com [IPv6:2607:f8b0:4002:c05::22d]) (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 4149012945C for <geojson@ietf.org>; Wed, 4 Jan 2017 01:32:39 -0800 (PST)
Received: by mail-yw0-x22d.google.com with SMTP id v81so208153100ywb.2 for <geojson@ietf.org>; Wed, 04 Jan 2017 01:32:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=8tUHuu6psJTEPAL6OKeJMJxQdXEoxNnM+TX6zU6DAZA=; b=PnR/fXnfKKxfJ6KTnj9rcQ0HEyW7Jan0cA6lyjAfQVP4AB31/vlBV4v809YeZ3H7ff vTsB387483Hgmde7xjo/MBwSlvKWjWLj7i/6VylwI+7Mlm9HP9dDcQ2m1G+BE95LKE+k buN0iyQLXB6UjPjgy5RWr5lOlWF5wk2rrs2mGVnG5Z6tCutYlfONdAP5lrfa9eGPtAVV lMQi2GNyZhjrFsgl84YV+0mCPMHdLf0SfO0dJhrPdSnruIOhv6TDxsLsdrHw2MEAvwzM 7a3hLbZvjJtpvVI/67pJXkhBsLvn1sQruMMPboVywOErQ8d7KF2/rR3OXyT5nSdNP6T1 YwrQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=8tUHuu6psJTEPAL6OKeJMJxQdXEoxNnM+TX6zU6DAZA=; b=Gvnu3U9N+BiSMM3JzeBPs8caWP7a8HIzGb7mqYAWPyE+8Ylh1RphrwVpdYZPU9Mf9F cmzd/7ZLw0bSWKJlMj2N2sUOLAHLHlihWqUe3fPuVrjq49a6Gq9xM3lSoerM5e+u0460 2AjUZDuwGTjsvhizkoqAQDcLRbAQEyVtIBMLGG9DEIetogvMojM4q5PDy2tV7rtSPCVN JWnW71Mq1met9d7002YiIkCD2wvApPCTwwP+EZjkWFDLK1/12YSCYWWqUxiZ2XjybMXd lkkGRzYg38JoC4PLNVHOdF/IMg6iljSlZ4+5yBXpGdMZQ3T4Ve31nqkD1ymjAE+fYmlF 6aIg==
X-Gm-Message-State: AIkVDXKx8Lgj3fyGP6yrvPywfex1sk1uIcae8UBQNZwvI2rU4j+GZ67z8sMsE9ccqyRKVeDshGxj0bWm13QEhw==
X-Received: by 10.13.218.199 with SMTP id c190mr59659928ywe.270.1483522358290; Wed, 04 Jan 2017 01:32:38 -0800 (PST)
MIME-Version: 1.0
Received: by 10.129.138.129 with HTTP; Wed, 4 Jan 2017 01:32:37 -0800 (PST)
From: Sean Gillies <sean.gillies@gmail.com>
Date: Wed, 04 Jan 2017 10:32:37 +0100
Message-ID: <CAOodmJomw-0VymQYyPHLCR+Ds+dpEmFe=2j+FnZGh19bf1DUbg@mail.gmail.com>
To: geojson@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c07ef022eac6105454177aa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/geojson/1IaWaf6IhKTUv7Bs4GRL_YkKY1k>
Subject: [Geojson] Requests for comments on GeoJSON Events draft
X-BeenThere: geojson@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF GeoJSON WG <geojson.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/geojson>, <mailto:geojson-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/geojson/>
List-Post: <mailto:geojson@ietf.org>
List-Help: <mailto:geojson-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/geojson>, <mailto:geojson-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jan 2017 09:32:40 -0000

Hi and Bonne Année all,

With help from many of you, I've been working on a GeoJSON extension for
event-like features

    https://github.com/sgillies/geojson-events

and have drafted a spec:


https://sgillies.github.io/geojson-events/draft-gillies-geojson-events.html
    https://sgillies.github.io/geojson-events/

It's pared down dramatically from what we discussed in the past. Fuzzy time
periods are out and so are temporal bounding boxes because the use cases
for these are rare. GeoJSON has been doing well so far without any
representation of fuzzy geometry and I think the situation is about the
same for time.

I received an suggestion to consider ISO 8601 style time intervals. This
would allow a single string value to represent an instant or interval,

    "when": "2017-01-04/2017-01-05"

instead of

    "when": {"start": "2017-01-04", "stop": "2017-01-05"}

but this seems harder to use because support for it in parsers is rare.

I was asked about recurring intervals like "every other Friday," but I
think this isn't necessary. GeoJSON doesn't have a concept of non-literal
geometries either.

Some time ago we arrived at rough consensus that "moving objects" and
"event-like features" are either different things or very different models
of the same things. Moving objects are not specified in my draft.

I have two objectives for this draft:

* To establish a common representation for time in GeoJSON that mappers of
events, whether they are scientists or journalists or historians, can share.
* To set an example for other extension projects.

I'd love comments on how it can be improved to better meet those
objectives. Thanks!

-- 
Sean Gillies