W3C home > Mailing lists > Public > public-poiwg@w3.org > September 2010

Re: POI based Open AR proposal

From: Jens de Smit <jens.desmit@surfnet.nl>
Date: Fri, 03 Sep 2010 16:51:51 +0200
Message-ID: <4C810B87.9030100@surfnet.nl>
To: Thomas Wrobel <darkflame@gmail.com>
CC: roBman@mob-labs.com, Alex Hill <ahill@gatech.edu>, "Public POI @ W3C" <public-poiwg@w3.org>
On 03/09/2010 13:27, Thomas Wrobel wrote:
> "But pointers are just one very simple type of input sensor.  I'm sure
> we'd all agree that eye tracking, head tracking, limb/body tracking and
> other more abstract gestural tracking will soon be flooding into our
> systems from more than one point of origin."
> Just a little idea here. Again, maybe beyond our scope, but it could
> make things easier.
> Rather then ever defining precise (pointer/cursor) input methods,
> maybe a general form could be;
> X/Y/Z + Radius   which would cover most pointer input types, and
> radius would simply by a gauge of their accuracy?

The point you raise here is an interesting one and one that has been
addressed in passing by current appliations such as Junaio and Layar but
I have not seen come up here yet: the issue of accuracy.

We all agree (I think) that a critical component of AR is the ability to
relate digital content to the real world and present that information
_in context_. To do this, we need to first take a measure of the world
around the user, such as through a GPS reading or visual recognition.
The accuracy of this information is quite important for the quality of
the experience, and some applications are impossible to realize when
accuracy is too low. For instance, GPS is generally not accurate enough
to point a user to the door of a room, making it useless for, for
instance, an augmented tour of university campus (I know there are other
problems with GPS indoors, but just for the sake of example...).

I think for the foreseeable future this issue will extend to any sensor
input we collect: it is known that almost any measuring device has a
certain inaccuracy, and this accuracy can vary with environmental
conditions such as light, temperature, humidity, amount of GPS
sattelites etc. It may be prudent for content providers and/or AR
clients to adjust the experience they offer based on the level of
accuracy that has been registered.

My question is: do we need to take this issue, that I believe is
inherent in any digital-reality mixing application and therefore very
relevant to AR, into account when doing our work?


Received on Friday, 3 September 2010 14:52:25 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:48:25 UTC