The document discusses developing a location-based service app that would aggregate point of interest (POI) data from sources like Foursquare and Google, and enrich each POI with additional details to provide more dynamic responses to users' location-based queries and requests. It outlines two milestones - the first being a static search and results feature, and the second incorporating more dynamic answers by linking to full POI profiles. Addressing the duplication of POIs from different sources is also mentioned as an issue to resolve.

1. LBS on mobile
Chris Park, Founder
Lechuck Park, Technical Co-Founder
TBD, Co-Founder, System engineer
TBD, Marketing & Communication
TBD, Product Design

2. LBS app:
Foursquare, Gowalla, etc.
game, addiction & competition btw friends is good
in terms of getting traction.
bit of life logging.
then what. what do I get?
discount, coupons..

3. LBS app:
Localmind, loqly, etc
4sqr’s user data for ‘localmind’.
rely on immediacy. have to WAIT. otherwise...
rely only on conversation.

4. QnA : Quora, Namesake..
following knowledge (Quora) - brilliant idea.
excellent community management.
good QnA platform but it’s not LBS....yet.

5. POI aggregating
life logging.
bit of bragging. (twitter, facebook, blog, etc.)

6. input POI data
provide life logging methods.
users can make diary with location info. and media like picture.
‘Cold Noodle’.

7. mesh up
fetch poi data from 4sqr, gowalla, google, etc

8. poi #1
poi #2
poi #3
poi #4
POIs from
input POI data 3rd parties

9. value up POI list
data aggregating in a systematic manner

10. POI entity
A poi has multiple sections, that includes;
name, contact point, address, open hour, wireless
internet, parking, menu, stylist, etc.
sections can bee added or modified.

11. POI entity
name
address
contact
open hour
menu
wireless internet
parking
stylist
category

12. POI entity
Aggregate data
Foursquare data +
take POI’s name & coordinates from 3rd party
.
.
.
and make more detailed POI entity.
avoid duplicated POI by blrp* algorithm

13. 1st milestone. static
server
search
“nearby Japanese
restaurant still open?”
result
“Sukiyaki, 200meters
away from you.”
Server :
gather data from
POI entities
&
generate results

14. 1st milestone : static
server
search
“nearby Japanese gather data from
restaurant still open?” POI entities
&
result generate results
“Sukiyaki, 200meters
away from you.”

15. dynamic answer using poi entity
server
ask noti
“nearby Japanese
restaurant still open?”
result decide poi
“Sukiyaki, 200meters “Sukiyaki”
away from you.”

16. ANSWER
POI entity
name
select specific tag from poi
send link of the chosen tag address
contact
“nearby Japanese
restaurant still open?”
open hour “here you are”
follow the link and see all
POI data
menu
wireless internet
parking
stylist
category

17. 2nd milestone. X
POI entity
link
.
.
.

18. issue
• bothering vs. structured POI.

19. address poi duplication issue
starbucks @ timesquare