On Mar 5, 2009, at 5:49 AM, Pedro Melo wrote:
I don't see the usefulness of sending my own mac address. But
sending the mac address of my default gateway, then yes, I find that
very useful. That's how a lot of location aware-tools for the Mac
work for example.
It's just another source
On Mar 2, 2009, at 7:23 PM, Peter Saint-Andre wrote:
I was chatting with Joe Hildebrand about XEP-0255 and he mentioned
that
it would be good to add a reference type for an Ethernet address,
such as:
iq from='ham...@shakespeare.lit/phone'
id='q02'
to='location.shakespear.lit'
On Mar 3, 2009, at 11:17 PM, Helge Timenes wrote:
Joe Hildebrand wrote:
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
Fabio Forno wrote:
On Mon, Mar 2, 2009 at 11:15 PM, Peter Saint-Andre stpe...@stpeter.im wrote:
I meant your locally-assigned IPv4 or IPv6 address, not your MAC
address. My bad.
Penitenziagite! :D Yep, now I get the point and it makes sense
Sorry for being a bit late responding to
Joe Hildebrand wrote:
On Mar 2, 2009, at 3:15 PM, Peter Saint-Andre wrote:
Uhm.. is that meaningful? Usually for location queries external
references are more useful than your address (e.g. your MAC moves with
your notebook, so what is the purpose of doing a query with it?)
I meant your
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
On Mar 02, 2009, at 20:23, Peter Saint-Andre wrote:
I was chatting with Joe Hildebrand about XEP-0255 and he mentioned
that
it would be good to add a reference type for an Ethernet address,
such as:
It seems that we'd need this because your ethernet address might be
different from your
On Mon, Mar 2, 2009 at 8:23 PM, Peter Saint-Andre stpe...@stpeter.im wrote:
I was chatting with Joe Hildebrand about XEP-0255 and he mentioned that
[...]
It seems that we'd need this because your ethernet address might be
different from your wifi address even in the same location (e.g., where
On Mon, Mar 2, 2009 at 11:15 PM, Peter Saint-Andre stpe...@stpeter.im wrote:
I meant your locally-assigned IPv4 or IPv6 address, not your MAC
address. My bad.
Penitenziagite! :D Yep, now I get the point and it makes sense
Besides that there is one more reference we are starting using: RFID
Hi Helge,
Having worked for www.Amethon.com last year I can tell you categorically
that mobile handset ip addresses have very little location based
information.
You need a cell tower mapping system which isn't readily accessible by
the applications etc.
Ignore this problem for a few years and
-Original Message-
From: standards-boun...@xmpp.org [mailto:standards-boun...@xmpp.org] On
Behalf Of Helge Timenes
Sent: 02/13/2009 1:24 AM
To: XMPP Standards
Subject: [Standards] XEP-0255: Location Query
Just a heads up notice:
As suggested by Stephen Pendleton I plan to add
] XEP-0255: Location Query
Thanks. Will fix ;-)
Regards,
Helge Timenes
-original message-
Subject: [Standards] XEP-0255: Location Query
From: Daniel Willmann dan...@totalueberwachung.de
Date: 03/02/2009 11:24
Hi,
I just noticed an inconsistency between the query tags at
http://xmpp.org
: 02/04/2009 11:25 AM
To: XMPP Standards
Subject: Re: [Standards] XEP-0255: Location Query
I'm still thinking about this one. Granted ip address is useful in
determining location, and adding a new beacon type is a painless update. But
i feel it is a bit silly to call it a 'beacon'. Cell towers
Thanks. Will fix ;-)
Regards,
Helge Timenes
-original message-
Subject: [Standards] XEP-0255: Location Query
From: Daniel Willmann dan...@totalueberwachung.de
Date: 03/02/2009 11:24
Hi,
I just noticed an inconsistency between the query tags at
http://xmpp.org/extensions/xep-0255.html#examples
Helge Timenes wrote:
That is a good idea. And also brings up an already asked question. Would it
be better to de-generalize the beacon element into explicit cell, wifi,
bluetooth, and as suggested, ip elements?
Pros/cons anyone?
We will soon have WiMAX and then LTE-type cell-ids and...
/locationquery
iq
-Original Message-
From: standards-boun...@xmpp.org [mailto:standards-boun...@xmpp.org] On
Behalf Of Simon Tennant
Sent: 01/27/2009 9:20 AM
To: XMPP Standards
Subject: Re: [Standards] XEP-0255 (Location Query)
Helge Timenes wrote:
That is a good idea. And also brings up an already
What about adding another optional element to the query to allow the lookup
of location information based on IP address?:
iq from='ham...@shakespeare.lit/phone'
id='q02'
to='location.shakespear.lit'
type='get'
xml:lang='en-US'
locationquery xmlns='urn:xmpp:locationquery:0'
Helge Timenes wrote, On 11/26/2008 10:43 PM:
Some comments to the XEP-0255 / Location Query draft
(http://xmpp.org/extensions/xep-0255.html):
1) Beacon signal strength seems to have been forgotten in the draft specification. This is a mistake and I will correct it.
2) In the development
Helge Timenes wrote, On 12/12/2008 04:52 PM:
On Thu, 11 Dec 2008 16:15:30 -0500, Stephen Pendleton
stephenpendle...@hotmail.com wrote:
- Is Example 7 allowed in XMPP/pubsub? It looks like the component is
publishing to the entities node. I suppose there is nothing wrong with
that, I just
On Thu, 11 Dec 2008 16:15:30 -0500, Stephen Pendleton
stephenpendle...@hotmail.com wrote:
Some comments I have on 0255 during implementation:
- XEP-0080 uses lat, lon, alt instead of latitude, longitude...
so the examples need to be changed. The schema looks right though.
Have
Some comments I have on 0255 during implementation:
- XEP-0080 uses lat, lon, alt instead of latitude, longitude... so
the examples need to be changed. The schema looks right though.
- Is Example 7 allowed in XMPP/pubsub? It looks like the component is
publishing to the entities node. I
21 matches
Mail list logo
