#Qaiku

Kunhan Äteritsiputeritsipuolilaudatsijänkä mahtuu. ;-)

"Äteritsiputeritsipuolilautatsijänkä, Lappi, Finland" olis siis vissiin pisin suomalainen oikea paikannimi. :)

What about those Qaikuing from Taumatawhakatangihangakoauauotamateapokaiwhenuakitanatahu (New Zealand), Llanfairpwllgwyngyllgogerychwyrndrobwllllantysiliogogogoch (Wales) or Krungthepmahanakornamornratanakosinmahintarayutthayamahadilokphopnopparatrajathaniburiromudomrajaniwesmahasatharnamornphimarnavatarnsathitsakkattiyavisanukamprasit (Thailand)

@bergie, would you be surprised to hear that the geolocation system doesn't regocnize the longer two, nor the Finnish one? :)

@mandrl luckily GeoNames is editable so you can fix that :-P

concerning location, there is also the issue between "correct" information and "relevant" information. there in fact are many ways to formulate a location, all of which potentially useful for some purpose.

for a "correct" location 255 chars may not be enough. quoting Schegloff (1972: 81):

"Were I now to formulate where my notes are, it would be correct to say that they are: right in front of me, next to the telephone, on the desk, in my office, in the office, in Room 213, in Lewisohn Hall, on campus, at school, at Columbia, in Morningside Heights, on the upper West Side, in Manhattan, in New York City, in New York State, in the North east, on the Eastern seaboard, in the United States, etc. Each of these terms could in so in some sense be correct.. "

@ekurvine internally we support all XEP-0080 location data fields so you wouldn't need to cram all that in one text field. But now the UI only provides access to the text property

@bergie i see an element for room #, but no "next to the telephone" ;)