On Mar 3, 2009, at 10:21 AM, Helge Timenes wrote:
Actually, I meant the local ethernet (MAC) address of your active
network connection(s). There are network elements that keep track
of the ethernet addresses they have seen, and can glean location
information from that connectivity information. Imagine that your
switch's ARP map was query-able, and you knew where each switch
port was punched down in a given office. Also imagine a network of
wireless access points that can triangulate on you, given your
ethernet address.
I will come back to you on that one when i have fully understood
what you meant (can't really think in the bus I'm sitting in ATM ;-)
To be clear, what I'm asking for is the addition of an "ethernet"
reference type, which is the ethernet address of a NIC on the user's
machine.
1) Need a "discovering support" section. I might want to find a
location service using disco#items/disco#info, as implied by "run
as a component on the same or a different machine from the XMPP
server itself".
Yes that makes sense. Will add to TODO list.
Thanks.
2) For components outside your core XMPP service, it would be nice
to direct a presence to them first, so that they get notified when
you go offline.
If a location server provide location upon request, I'm not sure if
online/offline presence adds much...?
The use case I've got is that the location server wants to know when
your device is no longer a source of location. Unavailable presence
is a great indicator for that. If you direct a presence to the
location server, then it will always get notified when you go offline,
in much the same way that a XEP-45 chat room does.
3) Some location services may be able to publish your XEP-80
location to PEP on your behalf. If so, they should return an empty
result:
<iq from='location.shakespeare.lit'
id='q01'
to='[email protected]/phone'
type='result'
xml:lang='en-US'/>
If I understand you correctly, that is indeed what is specified (see
Example 6)
Whoops, sorry. Missed that, perhaps because it wasn't clear to me
that Example 7 was coming from the location service. Perhaps there
needs to be a little more expository text between the examples.
