IETF Logo Mail Archive

Re: [dispatch] GeoJSON question

James Winterbottom <a.james.winterbottom@gmail.com> Fri, 24 July 2015 21:47 UTC

Return-Path: <a.james.winterbottom@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BED81A88CF for <dispatch@ietfa.amsl.com>; Fri, 24 Jul 2015 14:47:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, SPF_PASS=-0.001] autolearn=ham
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 Ax68lh8ck9qj for <dispatch@ietfa.amsl.com>; Fri, 24 Jul 2015 14:47:57 -0700 (PDT)
Received: from mail-pd0-x229.google.com (mail-pd0-x229.google.com [IPv6:2607:f8b0:400e:c02::229]) (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 BF9621A88BE for <dispatch@ietf.org>; Fri, 24 Jul 2015 14:47:57 -0700 (PDT)
Received: by pdbbh15 with SMTP id bh15so19195437pdb.1 for <dispatch@ietf.org>; Fri, 24 Jul 2015 14:47:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=ZxVuTZQHtYrg/QMtxMOxc+UGpEWMGlQgoTarYqimMVg=; b=d/vQ8BzUSMXW0j7ALKCHbiircnNsA0zpvNeR/9vjyQUZ3yBZZFksTLk4gg0ROQhKki q+fdZ6w5HV0QybGc+eFL5O/OVS//uvwoPua+18azpjkM9bUkG1t0e4D8UcnW9liIc0uf o1dPBEtDH/M6aAKWupQ6wyhVvqZiegllwS1qMIvhnKbWaLPo8WvQHXb87Hiy92GoQL81 PZtPoYTcl0cYuNKsaMm+5KhVusslbt+OU4aY0pn5vMYsK/gr00jERAnrLq8by5qVenT7 6qJ6f8e8dwXHizwQ83U5R8Of9t/y1u7bciSJf51wCKQ4+FOdX6gF3lLAkn6xMgQM47bH dTmw==
X-Received: by 10.70.96.2 with SMTP id do2mr35457538pdb.67.1437774477354; Fri, 24 Jul 2015 14:47:57 -0700 (PDT)
Received: from [192.168.1.11] (124-168-131-205.dyn.iinet.net.au. [124.168.131.205]) by smtp.gmail.com with ESMTPSA id ra10sm16366615pab.19.2015.07.24.14.47.53 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 24 Jul 2015 14:47:55 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_C4E4010A-45A2-42D9-85C2-C6290351D4D1"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
From: James Winterbottom <a.james.winterbottom@gmail.com>
In-Reply-To: <CAOodmJqhSo0_FO5YHh06d9Y9hmz-Atj0K73FJLgt1CnJRV0Dvg@mail.gmail.com>
Date: Sat, 25 Jul 2015 07:47:52 +1000
Message-Id: <93B79A5A-777E-4F41-AC6F-5CE57ECB6CF9@gmail.com>
References: <F84146BE-EDB2-4A9B-BA3F-4E1DD083F71A@gmail.com> <CAOodmJqhSo0_FO5YHh06d9Y9hmz-Atj0K73FJLgt1CnJRV0Dvg@mail.gmail.com>
To: Sean Gillies <sean.gillies@gmail.com>
X-Mailer: Apple Mail (2.2098)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/JURax_mXDD1RGdBIkRDwLg7Qi2k>
Cc: DISPATCH list <dispatch@ietf.org>
Subject: Re: [dispatch] GeoJSON question
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jul 2015 21:47:59 -0000

Thanks Sean. That clarifies my question.



> On 24 Jul 2015, at 6:12 pm, Sean Gillies <sean.gillies@gmail.com> wrote:
> 
> On Wed, Jul 22, 2015 at 10:09 AM, James Winterbottom <a.james.winterbottom@gmail.com <mailto: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 mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch

v2.23.0 | Report a Bug | By Email