Re: [Geopriv] Progressing the draft draft-thomson-geopriv-confidence-03

Martin Thomson <martin.thomson@gmail.com> Sat, 03 August 2013 13:05 UTC

Return-Path: <martin.thomson@gmail.com>
X-Original-To: geopriv@ietfa.amsl.com
Delivered-To: geopriv@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B7D021F9E34 for <geopriv@ietfa.amsl.com>; Sat, 3 Aug 2013 06:05:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.475
X-Spam-Level:
X-Spam-Status: No, score=-2.475 tagged_above=-999 required=5 tests=[AWL=0.125, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6tI-LOPd7a5y for <geopriv@ietfa.amsl.com>; Sat, 3 Aug 2013 06:05:16 -0700 (PDT)
Received: from mail-we0-x236.google.com (mail-we0-x236.google.com [IPv6:2a00:1450:400c:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 5C9B821F9E48 for <geopriv@ietf.org>; Sat, 3 Aug 2013 06:05:16 -0700 (PDT)
Received: by mail-we0-f182.google.com with SMTP id u55so1274800wes.41 for <geopriv@ietf.org>; Sat, 03 Aug 2013 06:05:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=qiymSxnnF8XE+yCT9njlmFsGKtLjaSlIYXaazRz7kNg=; b=OsIuotZqsuslhGORuC5KU7+HiSpYoasGKegArOW4L/gRKan/Lwbtb7LEh4bx2+/kJp C/FMuxs2iUKFdGZtXC7ut0K3IhQyxHWzSq9qjQShL6tqdrJnzJwyjbOEBV3IrzweBi9B +GeeBZ9sUSZL1zilcNWpKw64tp28xSPCyi6DIybkdxceln8GnhXPysHirJ5mx7vwjfzR ttjW6DNQz+QHbnG7ieRa9jecWflqz2NOCwgnP5WSLeSQhNYshIvcGhHRa+wNJkI3lzbX S7Yjn2rQt/M/llL5Z0Atg10xsmplXxLC8XEcOvvgmd7AGoXDeenzrEJ/SaTkCeHJA6KT Yv/Q==
MIME-Version: 1.0
X-Received: by 10.194.110.6 with SMTP id hw6mr8104599wjb.3.1375535115412; Sat, 03 Aug 2013 06:05:15 -0700 (PDT)
Received: by 10.194.60.46 with HTTP; Sat, 3 Aug 2013 06:05:15 -0700 (PDT)
In-Reply-To: <FBD5AAFFD0978846BF6D3FAB4C892ACC3A4CAF@SEA-EXMB-2.telecomsys.com>
References: <CACWXZj3kKwXTx85NLWMcum-21foHcESNKaiYSUELNfwM8UP5Vg@mail.gmail.com> <CABkgnnXGT5jaGrMaA_6+DEJW2Nq3VVFALFH3HC6aoQFhJWrX9Q@mail.gmail.com> <CAOPrzE2dFNocXg_1OY1_rq0ZRznsMBzLKpviLphUOmfgtXBCNQ@mail.gmail.com> <CABkgnnWs-XzzX6gh5J3NUfFBYvAVbr-F7+UmM_az3tZipy0qhw@mail.gmail.com> <CAOPrzE24CXRAfJtNtekLcbR7RiGqDjqAMvt7ftYR9=r8mBvomg@mail.gmail.com> <CABkgnnU+jcVx6=+i=OuA8=8U32HYpr92tJDXNPjXDhYBua1CDw@mail.gmail.com> <F58BBB12-65FC-44B8-AB8B-DB5FCB7B2F7B@cs.columbia.edu> <CABkgnnVu4mB0956+QRcgJCRCMWsFCYUq2zwR-Xu2BpRDnfZeUA@mail.gmail.com> <CABkgnnUC57BuOGYesnkxxpMwsYjFAoFfMQ8xe=uYTpSsS1UESA@mail.gmail.com> <7273FCC2-82ED-48DD-8FBF-E8D8A8085244@cs.columbia.edu> <CABkgnnX5AJRe+yneouGQ0dWkPfOcxgj=2baxku6tfkvU6c-vmw@mail.gmail.com> <FBD5AAFFD0978846BF6D3FAB4C892ACC3A4CAF@SEA-EXMB-2.telecomsys.com>
Date: Sat, 03 Aug 2013 15:05:15 +0200
Message-ID: <CABkgnnXGP6ZkojE-iEd8HeMgHLqJ7yvHe4yNQzDdagke=jHPsg@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: GEOPRIV WG <geopriv@ietf.org>, Brian Rosen <br@brianrosen.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [Geopriv] Progressing the draft draft-thomson-geopriv-confidence-03
X-BeenThere: geopriv@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 03 Aug 2013 13:05:17 -0000

On 31 July 2013 18:32, Roger Marshall <RMarshall@telecomsys.com> wrote:
> I support these two drafts moving forward.  And, rather than having to figure out some ideal way to display confidence as a gating factor right now, once we have real values conveyed, we can likely figure out something useful .
>
> These two drafts promote the ability to report actual numeric values.  That's a good place to start.  Leaving the value(s) as implied or assumed just doesn't make for good engineering.

Roger makes a good point.  However, having spoken with Brian, I think
that it is important to highlight the implications of expressing
confidence, with an appropriate amount of discouragement.  This is
really only for cases where it's difficult to get location with a high
confidence.

I've done a little editing, though I don't know if this is actually
going to make sense, since it was all done on the train, and I don't
remember the entire journey because I was so tired, but here's what
I'm proposing to add to the draft.

2.2.  Consuming and Presenting Confidence

   The inclusion of confidence that is anything other than 95% presents
   a potentially difficult usability for applications that use location
   information.  Effectively communicating the probability that a
   location is incorrect to a user can be difficult.

   It is inadvisable to simply display locations of any confidence, or
   to display confidence in a separate or non-obvious fashion.  If
   locations with different confidence levels are displayed such that
   the distinction is subtle or easy to overlook - such as using fine
   graduations of color or transparency for graphical uncertainty
   regions, or displaying uncertainty graphically, but providing
   confidence as supplementary text - a user could fail to notice a
   difference in the quality of the location information that might be
   significant.

   Depending on the circumstances, different ways of handling confidence
   might be appropriate.  [I-D.thomson-geopriv-uncertainty] describes
   techniques that could be appropriate for consumers that use automated
   processing as well as background on the issue.

   Providing that the full implications of any choice for the
   application are understood, some amount of automated processing could
   be appropriate.  In a simple example, applications could choose to
   discard or suppress the display of location information if confidence
   does not meet a pre-determined threshold.

   In settings where there is an opportunity for user training, some of
   these problems might be mitigated by defining different operational
   procedures for handling location information at different confidence
   levels.

Now that I look at it, it's a lot of text, so it can probably be cut
down, but I think that it conveys the right sentiment.