On Wed, Feb 10, 2010 at 22:44, Ilya Braude <span dir="ltr"><<a href="mailto:ilya@drakontas.com">ilya@drakontas.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> I would like to propose the extension of the user location spec with source information, i.e. where the location information is coming from. Having discussed this topic with several people at the recent summit I think there is enough interest to make it part of the XEP.<br> <br> There are several use cases to motivate this change:<br> <br> Users may get location information from GPS, set it manually, use WiFi or cell tower triangulation, etc. Knowing source information would enable clients to display appropriate icons for the users who publish location.<br> <br> This could also be useful when updating or aggregating information from separate sources. For example, a client that is integrated with a car's systems can send location updates using GPS, and more accurate speed updates from the car's speedometer (thanks to tkoski for the use case).<br> <br> Devices with built-in digital compasses to send more accurate heading information with a different source tag (this is probably more useful if the device is mounted in a known orientation, such as in a vehicle, but still useful).<br> <br> <br> I think the way to accomplish this is to add a 'source' element as a child of the 'geoloc' element:<br> <br> <geoloc xmlns='<a href="http://jabber.org/protocol/geoloc" target="_blank">http://jabber.org/protocol/geoloc</a>' xml:lang='en'><br> <source>GPS</source><br> <lat>45.44</lat><br> <lon>12.33</lon><br> </geoloc><br> <br> <br> An alternative would be to add a 'source' attribute to the 'geoloc' element, but I don't like that as much:<br> <br> <geoloc xmlns='<a href="http://jabber.org/protocol/geoloc" target="_blank">http://jabber.org/protocol/geoloc</a>' xml:lang='en' source='GPS'><br> ...<br> </geoloc><br> <br> <br> Another issue to consider is whether to recommend well-known values for the field. GPS and manual are probably going to be the most common use cases, so standardized strings to represent them would be useful for interoperability.<br> <br> <br> Ilya<br> _______________________________________________<br> JDev mailing list<br> Forum: <a href="http://www.jabberforum.org/forumdisplay.php?f=20" target="_blank">http://www.jabberforum.org/forumdisplay.php?f=20</a><br> Info: <a href="http://mail.jabber.org/mailman/listinfo/jdev" target="_blank">http://mail.jabber.org/mailman/listinfo/jdev</a><br> Unsubscribe: <a href="mailto:JDev-unsubscribe@jabber.org" target="_blank">JDev-unsubscribe@jabber.org</a><br> _______________________________________________<br> </blockquote></div><br>That sounds sensible. On that topic it would be nice to have a tag for where mobile clients could just dump the CellIDs they see and send the stanza to the server which would then do the heavy lifting and look the position up locally or at a 3rd party service and would replace the CellID tag with the coordinates and accuracy tags.<div> <br></div><div>Cheers,</div><div><div><br>-- <br>Tobias<br> </div></div>