I very strongly support the addition of "source" and "provider"
information to the geoloc spec, but their addition means that we might
also have to modify the way we represent "stop commands." According to
XEP-0080:
In order to indicate that the user is no longer publishing any
location information, the user's client shall send an empty
<geoloc/> element, which can be considered a "stop command" for
geolocation.
Example Use Case: Transmit a "stop command" for a WIFI source, but
continue sending information from a GPS source.
The options are 1) include "source" and "provider" as optional
attributes of the <geoloc/> element, or 2) alter the representation of
the stop command.
By including the "source" and "provider" as optional attributes of
<geoloc/>, we can continue using an empty <geoloc/> as a stop command:
<geoloc
xmlns='http://jabber.org/protocol/geoloc'
<http://www.google.com/url?sa=D&q=http://jabber.org/protocol/geoloc%27&usg=AFQjCNEeMfdwnaV7yu2Aqox0OVKaz2IXlw>
xml:lang='en'
source='wifi'/>
I prefer, though, altering the representation by adding an explicit
termination, such as the type='stop' below:
<geoloc
xmlns='http://jabber.org/protocol/geoloc'
<http://www.google.com/url?sa=D&q=http://jabber.org/protocol/geoloc%27&usg=AFQjCNEeMfdwnaV7yu2Aqox0OVKaz2IXlw>
xml:lang='en'
type='stop'>
<source>wifi</source>
</geoloc>
Are there any other options that I'm missing?
--
Kyle Usbeck
_______________________________________________
JDev mailing list
Forum: http://www.jabberforum.org/forumdisplay.php?f=20
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: [email protected]
_______________________________________________
