Re: [dispatch] GeoJSON question

Sean Gillies <sean.gillies@gmail.com> Fri, 24 July 2015 08:13 UTC

MIME-Version: 1.0
In-Reply-To: <F84146BE-EDB2-4A9B-BA3F-4E1DD083F71A@gmail.com>
References: <F84146BE-EDB2-4A9B-BA3F-4E1DD083F71A@gmail.com>
Date: Fri, 24 Jul 2015 10:12:59 +0200
Message-ID: <CAOodmJqhSo0_FO5YHh06d9Y9hmz-Atj0K73FJLgt1CnJRV0Dvg@mail.gmail.com>
From: Sean Gillies <sean.gillies@gmail.com>
To: DISPATCH list <dispatch@ietf.org>
Content-Type: multipart/alternative; boundary="047d7bf0ef187276a4051b9a92f0"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/6sGVLInUvyl232IYF0x8Aahz34Y>
Subject: Re: [dispatch] GeoJSON question
Precedence: list

On Wed, Jul 22, 2015 at 10:09 AM, James Winterbottom <
a.james.winterbottom@gmail.com> wrote:

> It feels like the question is the target of the location ever going to be
> conveyed with the location information?
>

Are you asking if it's possible to convey, say, phone numbers and locations
of the the phones and the semantics needed to track the devices and their
users together in GeoJSON? This would require a protocol or framework
external to the GeoJSON format. GeoJSON specifies that Features should have
an "id" property and that it should uniquely identify the feature within
its collection. There's no requirement or implication that the id
identifies the thing described by the Feature. GeoJSON's "id" is no more
than Atom's Entry "id" (RFC 4287 has had a major influence on GeoJSON).
Semantics such as what it would mean to use, eg, "tel:867-5309" as a
feature id are not defined by GeoJSON.

-- 
Sean Gillies

[dispatch] GeoJSON question James Winterbottom
Re: [dispatch] GeoJSON question Sean Gillies
Re: [dispatch] GeoJSON question James Winterbottom