Re: thoughts towards a draft AR WG charter

On 8/3/2010 4:42 PM, Phil Archer wrote:

> This concept of triggers needs addressing since it keeps coming up.
>
> A location, even one that is defined relative to something else as
> opposed to a fixed point in space, is not a trigger.

+1

A location is that which is detected by one sensor (a GPS) and could 
have an orientation associated with it when another sensor (a compass) 
is also giving a reading, and another "condition" associated if the 
camera was open (another sensor) which detected something stationary in 
its field of view. And, to make things more flexible, there's also an 
associated piece of metadata which specifies the capability of the 
user's device for displaying data, should any be found which matches.

The trigger is that
> a device has arrived at that location (or that a recognisable
> object/marker has come into view, or that a time has arrived or whatever).

I don't agree. but I think we are just getting tripped up due to too few 
clear definitions.

I think there is something (a trigger) which is defined by the publisher 
and stored with the data (augmented information) which the publisher has 
made available in the standard AR data format.

When the user's device sends a bundle of data [reflecting a whole set of 
conditions in the real world  and user preferences, etc] and it matches 
the trigger, the user receives data which augments the experience.

To come back to what Rob Manson wrote on July 31 [1]:
"if we did use the "trigger" model then I'd express this as the
following RDFa style triplet:

         this [location] is a [trigger] for [this information]

POIs in this format would then become the archetypal AR relationship.

The above is a common subset of the broader relationship:

         this [sensor data bundle] is a [trigger] for [this information]

In the standard POIs case the minimum [sensor data bundle] is "lat/lon"
and then optionally "relative magnetic orientation".



<snip>
>
> I believe Point of Interest data should be thought of as static.

Hmmm, I believe that there are situations in which the data is dynamic, 
or, if it is static, points to a dynamic data source.

 From Rob Manson's post on July 29 [2]:

The data can be dynamic "such as access a data stream from a local 
sensor (e.g. camera or even a VOIP connection)."

See [3] for more discussion on this point.

Christine

[1] http://lists.w3.org/Archives/Public/public-poiwg/2010Jul/0048.html
[2] http://lists.w3.org/Archives/Public/public-poiwg/2010Jul/0046.html
[3] http://lists.w3.org/Archives/Public/public-poiwg/2010Jul/0029.html

Received on Tuesday, 3 August 2010 15:38:08 UTC