Re: A non AR use case: Check in

Your recommendation is likely spot on but I think this is one is critical
that we make sure that the POI can easily be used in this scenario

On Fri, Nov 5, 2010 at 8:06 AM, Thomas Wrobel <darkflame@gmail.com> wrote:

> Does all this really need to be in the POI itself though?, rather then
> just letting a POI (which contains the locational trigger) link to a
> separate piece of data of various forms ver a URI
> Rather then trying to cover absolutely everything inline in the POI,
> this lets us just link a POI to, say, a, calender, or a RSS feed, or a
> website.
>
> I still think we need extensibility, but I think the separation of
> trigger and content is a useful one, and we shouldn't lose it.
>
>
> On 5 November 2010 11:51, Marengo Marco <marco.marengo@telecomitalia.it>
> wrote:
> >
> > Il giorno 05/nov/2010, alle ore 11.44, Andy Braun ha scritto:
> >
> >> Should a POI definition capture something from the checkin use case in
> the main spec.
> >>
> >> I see the generic use case encompassing the following steps.
> >>
> >> 1) Being within a certain distance from Anchor of the site I am able to
> check in the site.
> >> 2) I am able to retrieve a list of social activity associated with the
> POI
> >> 3) I am able to view a leader board of the user with most social
> activity
> >> 4) I am able to retrieve a prize or other offer
> >> 5) I am able to discovery if any temporal event is currently occurring
> such as some sort of flash mob.
> >
> >
> > +1 to support this use case.
> >
> > This is imho another valid reason why we must target extensibility in the
> spec.
> >
> > Marco
> >
> > Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle
> persone indicate. La diffusione, copia o qualsiasi altra azione derivante
> dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora
> abbiate ricevuto questo documento per errore siete cortesemente pregati di
> darne immediata comunicazione al mittente e di provvedere alla sua
> distruzione, Grazie.
> >
> > This e-mail and any attachments is confidential and may contain
> privileged information intended for the addressee(s) only. Dissemination,
> copying, printing or use by anybody else is unauthorised. If you are not the
> intended recipient, please delete this message and any attachments and
> advise the sender by return e-mail, Thanks.
> >
> >
> >
>