layout: post title: "Jabber geeking: merge JEP-0080 and JEP-0112?" created: 1153242125 categories:
I'm in Stuttgart meeting with some clients. Lots of Drupal + Jabber integration talk, and luckily ralphm is here to bring along lots of Jabber expertise.
We've been talking a lot about geolocation notification over Jabber -- so users can indicate their location over Jabber. There are few (if any?) clients that support this today, so we'll probably support some short hand for testing purposes -- being able to type in geoloc:[lat],[lon].
So, I was looking at JEP-0080 (geoloc) and JEP-0112 (physloc). 112 is a plain text representation of physical location, and JEP 80 is the latitude / longitude. JEP 80 also has a plain text "description" field. So...why not collapse the two? physloc could replace the current JEP 80 "description" entry...every single entry is optional, so the text field in physloc can handle the current usage of the description field. It just seems wasteful to maintain two separate JEPs for what is essentially the same information.
As well, if a service already knows the physical location, it can send it along with the geoloc -- you can't derive the physical location from the geolocation, so in the current case, you would have to send two messages.
The *one* issue is the reverse: the latitude and longitude for geoloc are currently set to MUST. This means we can't send only the physical location, and leave the lat/long blank...I think this should be changed...people can send updates of either geolocation or physical location -- the server side can do a geoloc lookup if needed.
BTW, I reapplied for membership in the Jabber Software Foundation -- apparently the April voting had some issues.