Hey. Is this the right list for comments on this XEP? For example, Section 10.1 refers to the wrong namespace and Example 7 contains some extraneous ''s. I'm also confused by the presence of a (mandatory) timestamp in Example 2. If it's indeed a geocoder (which that section mostly seems to describe), there's no relevant timestamp to return.
This is quite interesting though. When Blaine and I built out Fire Eagle's PubSub service, we intentionally decided not to use XEP-0080, as we considered it lossy and not the best fit for this application. I'll revisit that and try to remember specifically why that was the case; my initial reaction is that multiple levels of precision didn't fit and there was no room for additional elements like WOEIDs (although I suppose that could fit in the URI field). Does anyone have client or server implementations of this yet (or intend to)? If so, we should talk. seth On Wed, Dec 17, 2008 at 10:39 AM, Peter Saint-Andre <[email protected]>wrote: > FYI. > > Version 0.2 of XEP-0255 (Location Query) has been released. > > Abstract: This specification defines an XMPP protocol extension for > querying a compliant server for information about the geographical or > physical location of an entity." > > Changelog: [See revision history] (ht) > > Diff: > http://svn.xmpp.org:18080/browse/XMPP/trunk/extensions/xep-0255.xml?%40diffMode=u&%40diffWrap=s&r1=2501&r2=2576&u=3&ignore=&k= > > URL: http://www.xmpp.org/extensions/xep-0255.html > > >
