On 2/13/10 7:03 AM, Tuomas Koski wrote: > Hi, > > On 10 February 2010 22:44, Ilya Braude <[email protected]> wrote: >> <geoloc xmlns='http://jabber.org/protocol/geoloc' xml:lang='en'> >> <source>GPS</source> >> <lat>45.44</lat> >> <lon>12.33</lon> >> </geoloc> > > +1 > > This would help to create much smarter and more "reliable" systems who > use the data.
That seems reasonable. > On 10 February 2010 22:44, Ilya Braude <[email protected]> wrote: >> 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. > > In my humble opinion this is the trickiest part. I think there will be > crowing number of sources: GPS, manual, speedometer, Geode, Fire > Eagle, Latitude ... etc. > > Should it be just a free text field with some values like GPS to be > recommended to use? > > In the end we would have something like this, right? : > > <geoloc xmlns='http://jabber.org/protocol/geoloc' xml:lang='en'> > <source>GPS</source> > <lat>45.44</lat> > <lon>12.33</lon> > </geoloc> > <geoloc xmlns='http://jabber.org/protocol/geoloc' xml:lang='en'> > <source>Open Street Map</source> > <text>Marcon, Venezia, Veneto, Italy</text> > <country>Italy</country> > </geoloc> Do we have two things here, a source type (e.g., GPS) and the name of the provider? Peter -- Peter Saint-Andre https://stpeter.im/
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ JDev mailing list Forum: http://www.jabberforum.org/forumdisplay.php?f=20 Info: http://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: [email protected] _______________________________________________
