RE: POI Core strawman: multi-lingual

Suspect not the best idea. A POI will need to be largely atomic. Having to send a bundle of POIs just to get the language translations and transcriptions could explode the transmission sizes if we are not careful.

POI names come with the following trappings:
+ root name
+ small set of typical synonym names (DBA names)
+ multiple language presentations of that name
+ voice TTS transcriptions of the names for spoken word / hands free ops

This name proliferation is not really that rare. My guess is upwards of 30% of the standard POI sets carry multiple names. The more common and popular POIs have the most alt names. O'Hare / ORD / Ohare / O'Hare International Airport... 

_______________________________
Karl Seiler
Director Location Technology & Services
NAVTEQ - Chicago
(T)  +312-894-7231
(M) +312-375-5932
www.navteq.com


-----Original Message-----
From: public-poiwg-request@w3.org [mailto:public-poiwg-request@w3.org] On Behalf Of Raj Singh
Sent: Wednesday, May 04, 2011 1:25 PM
To: Matt Womer
Cc: public-poiwg W3C
Subject: POI Core strawman: multi-lingual

Putting every possible language into a single POI could get very cumbersome. How about putting each different linguistic representation of a single POI in it's own <poi>, and linking them with an "identity" relationship?

---
Raj
The OGC: Making location count...
http://www.opengeospatial.org/contact





The information contained in this communication may be CONFIDENTIAL and is intended only for the use of the recipient(s) named above.  If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited.  If you have received this communication in error, please notify the sender and delete/destroy the original message and any copy of it from your computer or paper files.

Received on Wednesday, 4 May 2011 19:09:10 UTC