Hi, Not sure where to inject this, so this is as good as any other place.
On Thu, 2007-05-31 at 10:05 -0600, Joe Hildebrand wrote: > On May 31, 2007, at 9:21 AM, Ian Paterson wrote: > > >> Actually, once PEP starts to be more deployed (hopefully later > >> this year), I'd like to remove/deprecate the non-PEP parts of XEP-80. > > > > Yes. In fact maybe that should be done now - to avoid (new) > > implementations of the non-PEP parts? As things stand, if you have > > two online resources in different physical locations, then they > > will indicate that your corporeal body is in two different places > > at the same time! > > I'm ok with that, pending the outcome of this discussion. I've always thought of the specs we now view as extended presence specs to hold data formats for certain types of information. How to transport them being secondary. For example, it might be very useful to attach a location to a message that denotes the location of whatever else is sent in the same message. Maybe a photo that has been taken, and you send both a link to the photo and a location description. Like example 4.3 in version 1.3 of XEP-0080. Especially XEP-0080 defines a generic format for communicating the location of something. I agree that in PEP settings, it most useful to denote the location of the person that holds the account. I might be wrong, but I can imagine other settings, using generic pubsub and not related to persons but entities in general. Would they need to be restricted to have only one location per account/[EMAIL PROTECTED] What if the clients publishing extended presence stuff like location only did this from the primary resource? I am suggesting using RAP here. > > It might also be useful to add a second namespace to the XEP (or > > publish another XEP) that will allow resources to indicate in a > > standard way where they are (<description>Home</description>, > > <description>Office</description>, etc.). The value of the 'id' > > attribute of each pubsub <item/> could be the associated resource > > identifier string. > > Why not just use: > > <presence> > <geoloc xmlns='http://jabber.org/protocol/geoloc'> > <description>Office</description> > </geoloc> > </presence> > > This captures exactly what you want; a description of the location of > the device. Noooh, my eyes! -- Groetjes, ralphm
