Re: [Geopriv] Proposal for uncertainty

"Marc Linsner (mlinsner)" <mlinsner@cisco.com> Wed, 28 May 2014 13:04 UTC

Return-Path: <mlinsner@cisco.com>
X-Original-To: geopriv@ietfa.amsl.com
Delivered-To: geopriv@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E66571A0985 for <geopriv@ietfa.amsl.com>; Wed, 28 May 2014 06:04:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level:
X-Spam-Status: No, score=-15.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 jGSssz_KDNmB for <geopriv@ietfa.amsl.com>; Wed, 28 May 2014 06:04:36 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D736D1A0982 for <geopriv@ietf.org>; Wed, 28 May 2014 06:04:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2866; q=dns/txt; s=iport; t=1401282272; x=1402491872; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=MaPByYlex8rOHK5Vou0fC7GPxhRPJPV2ju70LdazI6I=; b=cSOWmCZ827RznJCOhaEJHr1hP3fwe3Amdn2FwH1NI/dd8dkEEYegrYqr AT3hq2JzMBTJMd1wEfhkpRVREtRE4Si0lj5G0avh5JDmCQpFhSzHxAsX+ jofKvyvmj1eGvoM+Ds0Pplu5xtxH2zWWyVgNp3yXt3gi4sBcYVKOJev60 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjwFAI/ehVOtJA2E/2dsb2JhbABZgwdSWMFRUQGBCRZ0giUBAQEEeQwEAgEIEQMBAi8hER0IAgQOBYguAxEN0GcNhVEXjDyBYwgrBwIEhDoEiWiOF4F2gT2Ld4VzgzhsgUM
X-IronPort-AV: E=Sophos;i="4.98,928,1392163200"; d="scan'208";a="328533698"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by rcdn-iport-3.cisco.com with ESMTP; 28 May 2014 13:04:32 +0000
Received: from xhc-rcd-x08.cisco.com (xhc-rcd-x08.cisco.com [173.37.183.82]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id s4SD4Vx6031746 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 28 May 2014 13:04:31 GMT
Received: from xmb-rcd-x08.cisco.com ([169.254.8.59]) by xhc-rcd-x08.cisco.com ([173.37.183.82]) with mapi id 14.03.0123.003; Wed, 28 May 2014 08:04:31 -0500
From: "Marc Linsner (mlinsner)" <mlinsner@cisco.com>
To: Martin Thomson <martin.thomson@gmail.com>
Thread-Topic: Proposal for uncertainty
Thread-Index: AQHPdsNPbO+2AZnwJ0+18EbQ+rIoGZtWDfSA
Date: Wed, 28 May 2014 13:04:30 +0000
Message-ID: <CFAB4F96.59AF4%mlinsner@cisco.com>
References: <CABkgnnWHaxgEKBbb8g0b3wAC1gujZ8XQqJngM+K=gG0Xtr3wuw@mail.gmail.com>
In-Reply-To: <CABkgnnWHaxgEKBbb8g0b3wAC1gujZ8XQqJngM+K=gG0Xtr3wuw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.116.148.98]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <4941000CD58AE749B1E4A340F4BDD032@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/geopriv/PWCVu3bKmG6uWcxZ9hfhyDwxT3c
Cc: GEOPRIV WG <geopriv@ietf.org>
Subject: Re: [Geopriv] Proposal for uncertainty
X-BeenThere: geopriv@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Geographic Location/Privacy <geopriv.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/geopriv>, <mailto:geopriv-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/geopriv/>
List-Post: <mailto:geopriv@ietf.org>
List-Help: <mailto:geopriv-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/geopriv>, <mailto:geopriv-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 May 2014 13:04:38 -0000

Martin,

IMO, the draft still confuses the term uncertainty, and I believe it¹s due
to trying to cover both geo and civic locations in the same draft.

S2: You define uncertainty as the results of limitations of measurement.

S2.3: You state that accuracy is a qualitative concept, hence not part of
the quantitative uncertainty concept.

S3.3: You (re)define uncertainty as accuracy/precision wrt civic.


WRT measured location, uncertainty goes down and confidence goes up as the
size of the polygon gets bigger (less accurate).  According to S3.3 wrt to
civic the opposite is true.  Is that what you are trying to say?

-Marc-




-----Original Message-----
From: Martin Thomson <martin.thomson@gmail.com>
Date: Friday, May 23, 2014 at 4:12 PM
To: GEOPRIV WG <geopriv@ietf.org>, Marc Linsner <mlinsner@cisco.com>,
Roger Marshall <rmarshall@telecomsys.com>, Ray Bellis
<Ray.Bellis@nominet.org.uk>
Subject: Proposal for uncertainty

>I spoke about the one remaining issue with -uncertainty yesterday with
>Ray.  That conversation, along with Roger's comments regarding
>automated location determination helped me realize what I think the
>source of the disconnect here is.
>
>Based on this, I've tentatively concluded that the difference between
>civic and geodetic location is not what is at the core of the issue,
>though it's probably true that the issue only manifests with civic
>location information.  Primarily because of our better intuition
>regarding civic addresses.
>
>The core of the concern is that confidence - as a statistical measure
>- doesn't really make any sort of sense for location information that
>is a bald assertion, as opposed to locations that are generated by
>some measurement process (and here I give a nod to Carl for pointing
>out reverse geocoding as an example of a measurement process that ends
>with civic location).  For example, the assertion "I am at home" is
>verifiable and basically either correct or not, usually the former.
>
>It's only when taken in a larger context that terms like "confidence"
>even apply.  In particular, that means automated location
>determination.
>
>I've taken a stab at clarifying this in the draft.
>
>I've also permitted 100% confidence in the schema.  At the same time,
>I've retained the text describing this as impossible, but that text is
>all in the context of the statistical work, so I hope that the
>introductory material makes that clear enough.
>
>The changes are here:
>https://github.com/martinthomson/drafts/commit/c2207408af95de74d1f4bb7d790
>965d69d4b3045
>A readable copy is here:
>http://martinthomson.github.io/drafts/draft-ietf-geopriv-uncertainty.html
>
>Happy as always to take suggestions.  I'd like to think that this
>helps address Marc's concern without needing to cut Section 3.3
>entirely.