Diskussion:Mobile Tagging: Unterschied zwischen den Versionen
Zur Navigation springen
Zur Suche springen
Stefan (Diskussion | Beiträge) (→POIs) |
Stefan (Diskussion | Beiträge) Keine Bearbeitungszusammenfassung |
||
| Zeile 1: | Zeile 1: | ||
== Agenda Kickoff Kaywa-HSR-Teams 25. March 2008 == | |||
* Welcome notes from Mr. Fischer and Mr. Keller | |||
* Introduction of everybody | |||
* Short proposal of main ideas behind DOKODARE (Mr. Fischer?) | |||
* State of work (KAYWA and HSR team) | |||
* Discussion of DOKODARE / Issues General: usage scenarios for Dokodare | |||
* Issues HSR project related | |||
** What is crucial? How to organize work? Next steps? | |||
== Issues == | |||
=== Issues DOKODARE General === | |||
* Different usage scenarios for Dokodare? | |||
* Visuals for the place and presence tag? => Oliver, Chragi? | |||
* DOKODARE and it's components (Place, ID, Events, Activities...)? | |||
* Fixed definition of place type and subtype in english and german | |||
(Examples: map.search.ch, plazes, any map or tourist travel book etc.) | |||
* Public relations/Events: | |||
** How to spread it internationally? | |||
** Ars Electronica. | |||
** Eric from Usgang.ch: tagging clubs and bars in Switzerland. | |||
=== DOKODARE usage scenarios === | |||
We use navigational flow diagrams and user stories. | |||
Navigational flow sequence 'presence code': | |||
# Scan presence code => I'm visible and I'm at place X | |||
# Get info about POI => see Navigational flow sequence 'Info about POI' | |||
# Get info about friends nearby / communities => see Navigational flow sequence 'Info about friends nearby' | |||
Navigational flow sequence 'place code': | |||
# Scan place code => Where am I? What's nearby? => see Navigational flow sequence 'Info about POI' | |||
Navigational flow sequence 'Info about POI': | |||
# POI Screen | |||
## Info (text) about current POI | |||
## Map | |||
## Related keywords | |||
## Search what? (keyword search engine?) | |||
# Map Screen => Show Map with POIs a,b,c,... (similar - but better - than [http://www.beetagg.com/de/anwendungen/local/beetagg-local-augmented-location-based-96.html]) | |||
# Result List: Show result list of 'related keywords' or 'Search what?' | |||
Navigational flow sequence 'Info about friends nearby': | |||
# Map Screen => Show Map with friends nearby | |||
=== Issues HSR project related === | |||
* Business Architecture Sketch showing components, servers and APIs | |||
== POIs == | == POIs == | ||
=== Proposal 1 === | === POI Proposal 1 === | ||
Take map.search.ch as a german example. | Take map.search.ch as a german example. | ||
| Zeile 41: | Zeile 93: | ||
** Tankstelle | ** Tankstelle | ||
=== Proposal 2 === | === POI Proposal 2 === | ||
Folksonomy approach blended with supervision ('poi admins' and 'system tags'). Users can add multiple categories/keywords (don't confuse barcode tags with keyword tags). POI admins ensure that every POI get's at least one system category/keyword. | Folksonomy approach blended with supervision ('poi admins' and 'system tags'). Users can add multiple categories/keywords (don't confuse barcode tags with keyword tags). POI admins ensure that every POI get's at least one system category/keyword. | ||
| Zeile 50: | Zeile 102: | ||
* Top five main categories from [http://gis.hsr.ch/wiki/Rappi_Info] (german): 1. Essen, Trinken und Übernachten; 2. Freizeit und Kultur; 3. Shopping; 4. Verkehr; 5. Öffentliche Gebäude | * Top five main categories from [http://gis.hsr.ch/wiki/Rappi_Info] (german): 1. Essen, Trinken und Übernachten; 2. Freizeit und Kultur; 3. Shopping; 4. Verkehr; 5. Öffentliche Gebäude | ||
System keywords | 'System keywords': | ||
* 5 to 7 main system keywords... | * 5 to 7 main system keywords... | ||
* Additional important keywords | * Additional important keywords | ||
| Zeile 56: | Zeile 108: | ||
** nice => nice foot path/route | ** nice => nice foot path/route | ||
* ... | * ... | ||
Open questions regarding keywords, categories, tags: | |||
* Englisch and/or native? => allow native words but maintain 'system keywords'. | |||
* Umlauts? => allow umlauts | |||
* Keyword separator? => take comma as separator in order to allow multiple words | |||
* Singular/Plural? => prefer plural | |||
== Weblinks == | |||
* | |||
Version vom 16. März 2008, 13:07 Uhr
Agenda Kickoff Kaywa-HSR-Teams 25. March 2008
- Welcome notes from Mr. Fischer and Mr. Keller
- Introduction of everybody
- Short proposal of main ideas behind DOKODARE (Mr. Fischer?)
- State of work (KAYWA and HSR team)
- Discussion of DOKODARE / Issues General: usage scenarios for Dokodare
- Issues HSR project related
- What is crucial? How to organize work? Next steps?
Issues
Issues DOKODARE General
- Different usage scenarios for Dokodare?
- Visuals for the place and presence tag? => Oliver, Chragi?
- DOKODARE and it's components (Place, ID, Events, Activities...)?
- Fixed definition of place type and subtype in english and german
(Examples: map.search.ch, plazes, any map or tourist travel book etc.)
- Public relations/Events:
- How to spread it internationally?
- Ars Electronica.
- Eric from Usgang.ch: tagging clubs and bars in Switzerland.
DOKODARE usage scenarios
We use navigational flow diagrams and user stories.
Navigational flow sequence 'presence code':
- Scan presence code => I'm visible and I'm at place X
- Get info about POI => see Navigational flow sequence 'Info about POI'
- Get info about friends nearby / communities => see Navigational flow sequence 'Info about friends nearby'
Navigational flow sequence 'place code':
- Scan place code => Where am I? What's nearby? => see Navigational flow sequence 'Info about POI'
Navigational flow sequence 'Info about POI':
- POI Screen
- Info (text) about current POI
- Map
- Related keywords
- Search what? (keyword search engine?)
- Map Screen => Show Map with POIs a,b,c,... (similar - but better - than [1])
- Result List: Show result list of 'related keywords' or 'Search what?'
Navigational flow sequence 'Info about friends nearby':
- Map Screen => Show Map with friends nearby
- Business Architecture Sketch showing components, servers and APIs
POIs
POI Proposal 1
Take map.search.ch as a german example.
Menu-Inhalte: (* = Hauptmenupunkt)
- Communities
- Tourismus
- Verkehr
- Bergbahn
- Parkhaus
- Tram/Bus
- Zug
- Verkehrsinfo
- Mobility
- Gastronomie
- Bar
- Café
- Hotel
- Restaurant
- Kultur/Freizeit
- Kino
- Museum
- Theater
- Touren
- Spielplatz
- Badeanstalt
- Sports
- Öffentl. Gebäude
- Kirche
- Polizei
- Schule, Hochschule
- Spital
- Verwaltung
- Public Toilets
- Shopping/Service
- Apotheke/Drogerie
- Geldautomat
- Post
- Shop
- Tankstelle
POI Proposal 2
Folksonomy approach blended with supervision ('poi admins' and 'system tags'). Users can add multiple categories/keywords (don't confuse barcode tags with keyword tags). POI admins ensure that every POI get's at least one system category/keyword.
See also:
- OpenStretMap
- Free Map Prototype or Geonames (w/POI edit and history).
- Top five main categories from [2] (german): 1. Essen, Trinken und Übernachten; 2. Freizeit und Kultur; 3. Shopping; 4. Verkehr; 5. Öffentliche Gebäude
'System keywords':
- 5 to 7 main system keywords...
- Additional important keywords
- wheelchair => for wheelchair friendly POIs e.g. restaurant/bar, park lot, public toilet.
- nice => nice foot path/route
- ...
Open questions regarding keywords, categories, tags:
- Englisch and/or native? => allow native words but maintain 'system keywords'.
- Umlauts? => allow umlauts
- Keyword separator? => take comma as separator in order to allow multiple words
- Singular/Plural? => prefer plural